Year-end close and audit readiness: what your systems must produce

Reference article · 5 min read

Every finance office knows the shape of the year-end close: several weeks of long days, a stack of reconciliations, and then months of auditor requests arriving in no predictable order. It gets harder when the close depends on knowledge that lives in one person's spreadsheet, or when the system produces a number but not the evidence behind it. The difference between a close that finishes on schedule and one that slips is usually whether the systems produce, on demand, the artifacts an auditor asks for.

This guide covers how to sequence the close and what your ledger, payroll, and supporting systems must generate, including the access listings and change logs auditors now request from IT as well as from finance.

Set the calendar backward from the issuance date

Fix the date the audited statements must be issued, then place every dependency before it. Common anchors include state filing requirements, continuing disclosure commitments on outstanding debt, and Single Audit reporting for entities expending federal awards above the applicable threshold. Those thresholds and deadlines change, so confirm current requirements with your state oversight agency and your counsel rather than reusing last year's assumptions.

• Issue cutoff instructions before year end. Purchasing, receiving, payroll, and journal entry cutoffs go to departments before the year closes, not after.
• Close subsidiary ledgers first. Payables, receivables, payroll, grants, capital assets, inventory, leases, and subscription arrangements close ahead of the general ledger.
• Name an owner and a due date for every reconciliation, including bank, cash, and interfund balances.
• Set a hard stop for post-close entries. After it, adjustments route through documented approval and land on an audit adjustment schedule.

Accruals, encumbrances, and conversion entries

Governmental funds report on the modified accrual basis, where revenue is recognized when it is measurable and available. The availability period is a policy choice that should be written down and applied consistently across funds and years. Government-wide statements then convert to full accrual, and auditors trace those conversion entries early.

• Accrual sources to sweep. Unbilled receivables, grant costs incurred but not yet drawn, goods and services received but not invoiced, compensated absences, and claims and judgments.
• Encumbrance rollover. Decide which open purchase orders carry forward and which lapse, and preserve the closing year's encumbrance balances for reporting after the roll runs.
• Scheduled reversals. Every accrual carries a reversal date, or a note explaining why it does not reverse.
• A repeatable conversion worksheet. Capital outlay, debt proceeds and principal, long-term liability activity, and internal service fund allocations should follow a documented worksheet, not yearly reconstruction.

Subledger to general ledger tie-outs

Auditors test whether the detail supports the summary. Each of these should be a standing report, produced the same way every year.

• Payables aging to the ledger liability, with timing differences identified rather than plugged.
• Payroll register to ledger salary, benefit, and withholding accounts, then payroll totals to the quarterly federal filings.
• Capital asset roll-forward: beginning balance, additions, disposals, transfers, depreciation, ending balance, tied to construction in progress detail.
• Debt roll-forward with amortization schedules and amounts due within one year.
• Grant expenditure detail tied to the ledger and to the schedule of expenditures of federal awards, by award and assistance listing number.
• Lease and subscription arrangement schedules tied to the recorded assets and liabilities.

Turn the prepared-by-client list into system outputs

Ask your audit firm for last year's request list and map each line to the report or export that produces it. Anything with no system source is your work plan. Typical items include trial balances at several stages, full-year ledger detail with drill-down to source documents, a journal entry listing showing preparer and approver, check and void registers, and vendor master change reports. Sampling populations must be complete rather than filtered, and must reconcile to the ledger.

IT general controls evidence

Auditors increasingly test the systems that produce the numbers, so plan for these requests before they arrive.

• User access listing as of a date within the period, showing roles and permissions, not just names.
• Provisioning and termination evidence tying account removal to separation dates in the HR system.
• Privileged and emergency access, including who can post directly to the database or run mass updates, and how it is logged.
• Segregation of duties analysis, such as who can both create a vendor and release a payment.
• Change management records: tickets, approvals, test evidence, and migrations of configuration and code to production.
• Hosted systems: the vendor's service auditor report covering your fiscal year, plus a bridge letter for any gap period. Make annual delivery a contract requirement, and note that the complementary user entity controls it lists are your responsibility, not the vendor's.

What to ask vendors and put in the contract

• Demonstrate the request list, not the dashboard. Ask for a live demonstration producing prepared-by-client items from a test environment.
• Self-service evidence. Confirm that access listings, permission detail, and change logs are exports staff can run without a support ticket, and ask how long those logs are retained.
• Conversion year support. Require documented opening balances, a legacy trial balance at cutover, and help for auditors testing converted data.
• Period controls. Require period locking, logged reopening, and restrictions on who may post to a closed period.
• Data rights. Require export of your data in a usable, documented format during the term and at exit.

How to start

Hold a close post-mortem within two weeks of the audit's completion and list every request that took more than a day to fulfill. Build the request-to-report map, fill gaps with saved reports rather than one-time queries, and dry-run the package at an interim month.

HQT builds and supports enterprise software and data systems for state and local government agencies, including reporting and access control work.

Frequently asked questions