Build a month-end close pack reviewers can trace

A month-end close pack is the evidence trail for the close, not the close itself. The journals, reconciliations, and judgements happen in the accounting system and schedules. The pack proves what was reviewed, which source documents supported it, and which version was retained when the period was signed off.

That distinction changes the document routine. You are not editing evidence to make it neater after the fact. You are collecting the documents a reviewer can open, placing them in a predictable order, freezing the reviewed versions, and keeping a record that will still make sense at audit time or during a year-end review.

Drive the pack from the close checklist

Start with the checklist, not a folder of files. Each line should have a task, owner, reviewer, due day, status, and evidence reference. A task called "bank" is not enough. A useful line says "Bank reconciliation for operating account", owned by a named preparer, due on working day 2, reviewed by a named reviewer, with the bank statement and reconciliation attached.

The checklist should follow the shape of the financial statements and the order in which your team closes them. Cash, receivables, payables, accruals, prepayments, fixed assets, intercompany, payroll, tax calculations, and final financial statement review may each need a line. Small companies can keep this compact, but every balance that needs review should have evidence that can be opened without asking the preparer where it came from.

Use consistent period language throughout. 2026-07 close pack is clearer than July files, especially a year later when the folder contains drafts, revised schedules, and management reports.

Build evidence a reviewer can open

A reconciliation evidence pack usually contains more than the reconciliation schedule. For a reviewer to reperform or challenge it, the pack should include the supporting document behind the balance. Typical examples are:

• Bank statements for each account reconciled to cash.
• Control account listings for receivables, payables, payroll, or tax balances.
• Accruals schedules with invoices, contracts, or calculations supporting the estimate.
• Prepayments schedules showing the opening balance, additions, releases, and remaining term.
• Fixed asset movement schedules with additions, disposals, depreciation, and supporting invoices where material.
• Intercompany confirmations or statements from the counterparty.

Name each file so the period, entity, account, and document type are obvious: 2026-07-entity-a-bank-statement-operating.pdf is dull but durable. Avoid names like final, new, or reviewed2; they become meaningless once the pack is copied into an archive.

Freeze changing schedules before sign-off

Spreadsheets are excellent working documents and poor evidence archives. Filters can hide rows, formulas can recalculate, external links can break, and a later edit can change the view that the reviewer originally approved. Before review, export the schedule to PDF so the reviewed version is fixed.

Use Excel to PDF for workbook schedules where layout, headers, and page breaks matter. For system exports or flat listings, CSV to PDF gives the reviewer a readable table without asking them to interpret delimiters or encodings. Keep the original spreadsheet where your policy requires it, but make the PDF the signed-off evidence view.

Check the export before adding it to the pack. Wide schedules may need landscape orientation, repeated header rows, smaller margins, or a split between summary and detail. A PDF that cuts off the final two columns is worse than no export, because it looks authoritative while hiding the reconciliation logic.

Combine in checklist order and number the review copy

Once every checklist line has its evidence, combine the pack in checklist order with the merge PDF tool. The order should let a reviewer move from the checklist to the evidence without hunting through a shared drive: checklist, cash, receivables, payables, accruals, prepayments, fixed assets, intercompany, and final review, or whatever order your close process uses.

Add page numbers to the combined PDF so review notes can cite stable references: "see page 42" is much clearer than "see the third tab in the accruals file". If a reviewer asks for a correction, rebuild the pack from the corrected source, renumber it, and update the version. Do not slip a replacement page into the middle without changing the retained copy's version record.

The read-only principle matters here. The close pack is evidence, so it is assembled and frozen, not edited. If an invoice is wrong, fix the accounting or obtain the correct document; do not mark up the retained evidence in a way that confuses source and review commentary.

Record a fingerprint and retain the signed-off pack

After sign-off, create a fingerprint with the PDF fingerprint tool and record it in the close checklist or sign-off log. A hash does not tell you whether the accounting is right. It proves that a later file is byte-for-byte the same PDF that produced the recorded fingerprint. If someone asks which version was reviewed, the hash gives you a practical integrity check.

Retention depends on local law, tax rules, audit requirements, and company policy, so confirm the period that applies to your organisation. Whatever the period, retain the signed-off PDF, the checklist or sign-off record, and any source files your policy requires. Store them in a folder path that includes the entity and period, not only the preparer's name.

A tidy close pack saves time because it removes archaeology. A reviewer can open one file, follow the checklist order, cite pages in review notes, and prove later that the retained pack is the one that was signed off.

Close pack checklist

• Every checklist item has an owner, reviewer, due day, status, and evidence reference.
• Reconciliations include the source documents needed to review the balance.
• Spreadsheet and CSV schedules are exported to PDF before sign-off.
• The pack is merged in checklist order and page numbered for review comments.
• A fingerprint of the signed-off PDF is recorded with the close record.
• The retained folder identifies the entity, period, version, and retention category.