Avoid Excel-only reconciliations risk
- A finance-focused X post from MintyHawk warned controllers against running reconciliations in standalone spreadsheets, fixing breaks in chat, and editing records after close without a system trail. - The core complaint was traceability: when support lives in Excel tabs, Slack messages, and late journal fixes, teams cannot reliably reconstruct who changed what, when, or why. - That concern aligns with audit standards and securities rules requiring reliable evidence, accurate books, and internal controls over reporting. (pcaobus.org) (sec.gov)
A MintyHawk post on X zeroed in on a familiar month-end problem: reconciliations run in Excel, exceptions cleared in chat, and records edited later without a durable audit trail. (x.com) The post argued that those habits turn routine close work into opaque recordkeeping. If support for a balance sits across spreadsheet versions, message threads, and delayed fixes, the accounting file stops being easy to reconstruct. (x.com) Reconciliations are the checks finance teams use to prove one record agrees with another, such as cash in the general ledger matching a bank statement. PwC describes the process as a key internal control because it provides validation checks, responsibility mapping, and audit trails behind account balances. (pwc.ch) That matters most at month-end, when teams are finalizing revenue, accruals, journal entries, and financial statements for the prior period. Trullion, citing APQC benchmarking of more than 2,300 organizations, said the median finance team takes 6.4 calendar days to close each month. (trullion.com) A spreadsheet by itself is not automatically a control failure. The risk appears when the spreadsheet becomes the only source of support, approvals happen in side channels, and corrections are posted after the fact without linked evidence or formal review. (x.com) (pwc.ch) For auditors, the issue is evidence quality, not whether a team likes Excel. Public Company Accounting Oversight Board standard AS 1105 says audit evidence must be relevant and reliable, and AS 1215 says audit documentation includes the procedures performed, evidence obtained, and conclusions reached. (pcaobus.org 1) (pcaobus.org 2) For issuers, the legal backdrop is also broader than one close checklist. Section 13(b)(2) of the Securities Exchange Act requires companies to keep books and records that, in reasonable detail, accurately and fairly reflect transactions and to maintain internal accounting controls. (sec.gov) COSO’s internal control framework frames the same point from a governance angle: controls are meant to improve confidence in reporting and information integrity. A reconciliation that depends on memory, screenshots, or scattered file versions does the opposite. (coso.org 1) (coso.org 2) The practical fix is less dramatic than the warning. Teams need clear ownership, timely posting, documented approvals, and a system record that ties each reconciling item and adjustment back to source support. (trullion.com) (pwc.ch) MintyHawk’s point was not that Excel must disappear. It was that finance teams cannot treat spreadsheets, chat threads, and late edits as a substitute for a reconstructable close. (x.com)