The Audit-Ready Trial Balance: What Your External Auditor Actually Expects to Pull

The first request the auditor makes, and what most controllers send Every external audit engagement we have observed in mid-market private companies begins with the same provided-by-client request list, and the first item on the list is always some variant of "post-closing trial balance, in Excel, with prior-year comparatives, at the account level." The request is so standard that controllers rarely think about it; the GL is queried, the export runs, the file is sent. By the time the auditor has read it, the engagement is already on a trajectory that the controller did not consciously choose. The pattern across the firms whose audit-readiness we have diagnosed is consistent. The controller's TB export is technically correct: every account is listed, the balances are accurate, the totals foot. What the export lacks is everything the auditor needs to begin testing. There is no cross-reference between the trial balance and the supporting workpapers. The account numbers do not always match the prior year because the chart of accounts was modified mid-year and no crosswalk exists. Material accounts are not tied to a reconciliation file in a way the auditor can navigate without a guided tour. The journal-entry register, when requested separately, does not include approval evidence for entries above the firm's stated threshold. The sub-ledger to GL ties exist on the senior accountant's laptop, not in a shared evidence repository. The result is a six-to-eight-week audit start in which the substantive testing has not yet begun because the auditor is still assembling the evidence the controller could have provided in the first week. The controller's team is fielding follow-up requests. The auditor is logging unresolved items. The audit committee is asking why the timeline is slipping. None of this is the auditor being difficult. It is the consequence of treating the trial balance as a deliverable rather than as the index to a package of evidence. The controllers who run audits cleanly think differently about the trial balance request. They think about it as the audit's table of contents, the document that orients the auditor to every other artifact in the engagement, ties every material account to the supporting reconciliation, journal-entry evidence, and policy reference, and turns the first two weeks of fieldwork into substantive testing rather than evidence-gathering. This guide walks through what that package actually looks like, the procedures that produce it, and the failure patterns that cause mid-market firms to land on the auditor's desk with the export-only version every year. What "audit-ready trial balance" actually means The phrase covers a package, not a file. The package has six components, each of which the controller maintains continuously as part of the close process and assembles into the audit-evidence repository at year-end. The first is the trial balance itself, exported from the GL after the year-end close is locked, in a format that includes for every account: the account number, the account name, the account type (asset, liability, equity, revenue, expense), the current-period balance, the prior-period balance, the variance in dollars and percent, the entity (for multi-entity consolidations), and a reference to the supporting reconciliation or workpaper. The reference is the load-bearing element. An export without it is a file; an export with it is the package's index. The second is the chart-of-accounts crosswalk. If the firm modified the chart of accounts during the year, added accounts, retired accounts, restructured the natural account or department dimensions, the crosswalk maps every prior-year account to its current-year equivalent and identifies any account that did not have a prior-year match. The crosswalk is reviewed and signed by the controller. Mid-market firms restructure their chart of accounts more often than they realize, particularly after acquisitions, system migrations (a NetSuite-to-Sage Intacct or QuickBooks-to-NetSuite move during the year is common), or organizational changes that affect the cost-center dimension. Without the crosswalk, the auditor's prior-year-to-current-year analytic procedures produce false-positive variances that consume audit hours. The third is the account-by-account reconciliation set. Every material account on the trial balance is tied to a reconciliation file. The reconciliation file has a standard structure: the account in question, the period, the GL balance, the supporting detail (sub-ledger, third-party statement, schedule, or analytical), the reconciling items aged and explained, and the sign-off by the preparer and reviewer. Materiality for this purpose is typically calibrated to the audit's planning materiality, accounts above one-third of planning materiality get full reconciliations; accounts below that threshold can be supported with abbreviated procedures, but no material account is left uncovered. The reconciliation set lives in the firm's account reconciliation evidence pack and is referenced from the TB index. The fourth is the journal-entry register. Every journal entry posted during the period is logged with a unique entry number, a posting date, an effective date, the user who entered it, the user who approved it (where the firm's policy requires approval above a threshold), the supporting documentation reference, and a description with sufficient specificity that an external reader can understand what was recorded and why. The register is a continuous record, not an artifact assembled at year-end. Most modern GL systems (NetSuite, Sage Intacct, Microsoft Dynamics, Oracle Cloud Financials, Workday Financial Management, even the better-configured QuickBooks Online Advanced installations) produce this register natively if the controller has configured the entry workflow to capture the required fields and approval steps. The fifth is the management-representation crosswalk. The management representation letter, signed at the end of the audit, includes specific assertions about the financial statements: completeness of liabilities, going concern, related-party transactions, subsequent events, fraud risk, and others. Each assertion is supported by procedures the firm has run during the period. The crosswalk maps every material assertion to the supporting evidence in the audit package: the search-for-unrecorded-liabilities procedure, the going-concern memo, the related-party schedule, the subsequent-events checklist. The crosswalk is the controller's protection against signing a representation letter that the underlying evidence does not support. The sixth is the policy reference index. Every material accounting policy the firm relies on, revenue recognition under ASC 606, lease accounting under ASC 842, credit losses under ASC 326, capitalization, accruals, intercompany eliminations, is listed with the current-version policy document, the date of last review, the responsible owner, and the location of the documented procedures. The index gives the auditor one place to find every policy without an email back-and-forth with the controller's office. The structure of a trial balance the auditor can actually use A trial balance designed for the auditor differs from a trial balance designed for the controller's own monthly review in three specific ways. It is flat at the natural-account level, not aggregated. The controller's review trial balance often rolls up subaccounts into reportable categories, all cash accounts to "Cash and Equivalents," all AR sub-accounts to "Accounts Receivable, net", for readability. The auditor's TB needs the underlying detail because the testing is at the natural-account level. The right structure is the leaf-level account on every row, with the rollup category as a separate column for reference. Most GLs export this natively; the controller's discipline is to send the leaf-level export, not the management-reporting view. It includes prior-period balance, current-period balance, and variance, with the variance expressed both in dollars and as a percentage. The variance column is the auditor's first analytic procedure, accounts with material variances drive the substantive testing scope. A TB that omits the comparison forces the auditor to reconstruct it from the prior-year audited financials, which produces unnecessary follow-up requests and occasionally produces tie-out errors when the prior-year final figures differ from the prior-year initial export. It includes a workpaper reference column, populated by the controller before the file is sent. Each material account references the specific reconciliation file or workpaper supporting it: "Cash 1010-100 Operating: WP A-1.1 Bank Recon Operating Account JPM-4471," "AR 1200 Trade: WP B-2.1 AR Aging and Subledger Tie," "Deferred Revenue 2400: WP C-3.1 Deferred Revenue Rollforward and Contract Tie." The reference is the navigation that turns the TB into the audit's table of contents. Without it, the auditor has to ask for the workpapers separately, in a back-and-forth that wastes both sides' time. The flat, comparative, referenced TB is roughly twice the file size of the controller's review version and ten times more useful to the audit. The discipline of producing it does not require new software; it requires structuring the GL export and the reconciliation files in a way that allows the cross-reference to be built without manual labor at year-end. The reference column is populated as part of the close, not at audit start. Journal-entry testing: what the auditor pulls and what the evidence has to show Journal-entry testing is one of the highest-risk areas of any external audit because the auditing standards (AS 2401 and the analogous AICPA standards for non-issuer audits) specifically require the auditor to examine journal entries and other adjustments for evidence of management override of controls. The procedure is mechanical: the auditor selects a sample of journal entries based on risk-weighted criteria (entries posted near period-end, entries to seldom-used accounts, round-dollar entries, entries posted by users outside the normal workflow, manual entries above a defined threshold), pulls the supporting documentation, and tests for appropriate authorization, accurate amount, correct period, and complete description. The mid-market patterns that produce findings on this procedure are consistent. Manual journal entries without approval evidence. The firm's policy requires entries above (say) twenty-five thousand dollars to be approved by the controller, but the GL workflow does not enforce the approval and the senior accountant posts the entry directly. The auditor pulls the entry, sees no approval evidence, and the finding is a controls deficiency. The remediation is to configure the GL approval workflow to enforce the policy threshold; every modern GL supports this. Until the configuration is in place, the controller's compensating control is to review and sign off on a daily journal-entry register, with the sign-off filed as evidence. Entries with thin descriptions. The entry description reads "to record adjustment per CFO" or "JE for accrual" or "reclass." The auditor cannot determine the substance of the entry from the description alone, and the supporting documentation is either insufficient or absent. The remediation is a description standard: every manual entry includes the substantive purpose ("To accrue December professional fees per Smith & Smith WIP estimate dated 1/8"), the supporting document reference, and the accounting basis ("Accrual under ASC 720; reverses 1/1"). The standard is documented in the close policy and trained in. Entries to seldom-used accounts near period-end. A journal entry posted on the last business day of the period, debiting a revenue account and crediting an account the firm uses three times a year, is the kind of entry the auditor's risk-weighted sampling will pull. The remediation is not to avoid such entries when they are legitimate but to ensure the supporting documentation is contemporaneous and substantive: the contract amendment that triggered the entry, the customer correspondence, the analytical memo. Entries that are correct but poorly documented look like the entries that are not correct; the auditor cannot tell them apart without the documentation. Round-dollar entries posted by users outside the normal close workflow. The CFO posts a one-hundred-thousand-dollar adjustment on the last day of the close. The entry is correct (a known accrual adjustment that the controller had not yet recorded), but it was posted by a user the auditor's sampling flags as outside the usual posting pattern, and the supporting documentation is an email rather than a substantive memo. The remediation is to route every CFO-initiated adjustment through the controller's approval queue with documented justification, which preserves the substance of the CFO's decision while producing the audit-evidence trail. The journal-entry register that survives the auditor's testing is one in which every entry has a substantive description, a documented approval (where the policy requires it), supporting documentation referenced and accessible, and a close-period assignment that is clear from the entry's date stamps. The register is reviewed daily by the controller during close periods and weekly otherwise, with anomalies investigated and resolved before they become audit findings. The sub-ledger to GL tie that the audit will probe first For accounts with sub-ledgers, AR, AP, fixed assets, inventory, deferred revenue, lease liability and ROU, intercompany, the audit's first substantive procedure is to test the tie between the sub-ledger total and the GL balance. The procedure is mechanical: pull the sub-ledger detail at period-end, sum it, compare to the GL, identify and explain the difference. A clean tie is the foundation of all subsequent testing in the area; a broken tie expands the audit scope into investigation that should not have been necessary. The mid-market pattern we see most often is that the ties exist but are not maintained as part of the close. The senior accountant reconciled the AR sub-ledger to the GL last quarter, the result was clean, and no one has run the tie since. By year-end, the AR aging and the GL AR balance differ by an amount the team cannot quickly explain. The auditor finds the difference, asks for it to be reconciled, and the controller's team spends a week pulling adjustments and credit memos to identify what produced the variance. Most of the variance is explainable, credit memos posted in one ledger but not the other, write-offs processed in the AR module without the corresponding GL entry, intercompany items mis-routed, but the explanation is reconstruction rather than maintenance. The fix is the sub-ledger tie as a Day 4 procedure in the 10-day close calendar, run every period, with the result documented in the reconciliation file and the variance investigated and resolved before the close is locked. The same procedure runs for AR, AP, fixed assets, inventory, the lease subledger from the ASC 842 implementation, the deferred revenue rollforward, and intercompany. The maintenance discipline produces a year-end tie that the auditor confirms in fifteen minutes; the absence of the discipline produces a year-end tie that consumes a week. For firms with high-volume sub-ledgers (a distribution business with millions of inventory transactions, a SaaS business with thousands of contracts), the tie procedure includes a transaction-level reconciliation tool, BlackLine, FloQast, or Trintech for the dedicated close-management tools, or a structured reconciliation built directly in the GL for firms running NetSuite or Sage Intacct. The tool automates the comparison, flags the variances, and routes them for investigation. The controller's discipline is to ensure the tool is used as designed and that variances are not left aging in the queue. The mid-market patterns that produce findings every year Five patterns produce the bulk of the audit findings we see in mid-market trial balance reviews. Account-mapping changes mid-year without crosswalk. The firm restructured its chart of accounts in Q3 and the prior-year comparatives in the year-end TB no longer map cleanly. The auditor's analytic procedures produce false variances; the remediation requires reconstructing the mapping under audit pressure, which often produces a separate finding about controls over the chart-of-accounts change. Missing JE approver evidence. The policy requires controller approval above a threshold, the approvals were given verbally or via email, and the GL workflow did not capture the approval. The finding is a controls deficiency that, when material, can rise to a significant deficiency and trigger expanded testing. Sub-ledger to GL ties without reconciliation. The ties exist as totals matching but no documented reconciliation exists for the variances. Auditor pulls a sample of items in the sub-ledger and traces to the GL; the trace produces unexpected mismatches that the controller's team has to investigate during fieldwork. Stale reconciliations carried forward. The bank reconciliation file shows the reconciliation was performed but the reconciling items list contains items aged six months or more. The auditor's question is why the items have not been resolved; the controller's answer often does not survive scrutiny. Insufficient evidence for non-routine entries. The Q4 restructuring charge, the goodwill impairment analysis, the inventory obsolescence reserve true-up. Each is a judgmental entry with material impact. The audit pulls the entries; the supporting evidence is a one-page memo that does not address the alternatives considered, the data inputs, or the review by the appropriate level of management. The finding is on the adequacy of documentation supporting significant judgments. The patterns share a common cause: the documentation discipline that turns a posted entry into an audit-ready entry was not built into the close process; it was reconstructed under audit pressure. The reconstruction usually works (the entries are typically substantively correct), but the reconstruction itself is the finding. What we recommend The audit-ready trial balance is built across the year, not assembled at year-end. The controllers who hand auditors a clean package have built five recurring practices into the close. Run a monthly TB package assembly that produces, in a shared evidence repository, the leaf-level TB with workpaper references, the reconciliation set, the journal-entry register with approval evidence, and the policy reference index. The package is the controller's monthly archive; at year-end, it is the audit start. Maintain the chart-of-accounts crosswalk as a continuous document. Every change to the chart, additions, retirements, hierarchy modifications, is logged with a date, a rationale, and the mapping to the prior structure. The crosswalk is reviewed by the controller annually and signed. Configure the GL approval workflow to enforce the firm's journal-entry policy thresholds. Every entry above the threshold requires documented approval before posting, with the approval captured by the system, not by email. The configuration is reviewed annually as part of the SOX-or-COSO controls assessment for firms that have one. Run the sub-ledger to GL tie for every sub-ledger every period, with the result documented and any variance resolved before the close is locked. Firms with high-volume sub-ledgers use BlackLine, FloQast, or Trintech for automation; firms with simpler portfolios use structured reconciliations in the GL. Either approach works; the absence of the procedure does not. Build the management-representation crosswalk as a year-round artifact. Every assertion in the rep letter is mapped to the supporting evidence in the audit package, with the controller verifying the support before the rep letter is signed. The crosswalk is the controller's protection against signing a representation that the evidence does not support. The audit-ready trial balance package template included as the artifact for this guide is the version we install in mid-market engagements when the firm is preparing for a first-time audit, a change of audit firm, or a remediation after a difficult prior-year audit. Cross-reference to the M365 compliance and audit-readiness practices in Purview for the document-retention and chain-of-custody discipline that supports the audit evidence repository, and to the Securem fixed-scope security review methodology for the broader controls framework the audit fits inside. The trial balance is the index. The package is the audit's substance. Build them both, and the audit starts on the right foot.