Record to report process flowchart (cut-off to sign-off)
Record to report process flowchart for the period-end close: sub-ledger cut-off, accruals, intercompany matching, balance-sheet reconciliations, journal approval, consolidation, flux review, disclosure and sign-off.
What the record to report process flowchart (cut-off to sign-off) process is
Almost every close runs late for the same reason, and it is not transaction volume. The first days go on finding out whether the sub-ledgers are actually shut. Payables is still keying invoices, payroll posted a correction after the cut-off, and the inventory count has not been valued, so the general ledger team accrues against a moving number and then accrues again when it stops moving. The rest of the delay is review that happens too late to change anything: reconciliations prepared on day five and reviewed on day nine, a flux commentary written from figures nobody has questioned yet, and a stack of top-side journals posted at group level because there was no time to push the fix back into the entity ledger. A close that takes twelve days rarely contains twelve days of work. It contains three days of work, a queue, and a review cycle that starts after the numbers have already reached the board.
This chart starts where the sub-ledgers stop. Accounts payable (intake, matching, the exception queue, the payment run) is its own function and its own map at /templates/accounts-payable-process, and invoicing, credit control, dunning and cash application sit at /templates/accounts-receivable-process. Both feed record to report; neither is part of it. The line is the cut-off: once payables has closed its ledger for the period, what this process owns is the general ledger accrual for the backlog payables still holds at cut-off, not the invoices in it. The buying cycle upstream of that, from requisition through purchase order and goods receipt, is covered at /templates/erp-p2p-process-flow. The chart also stops short of assurance. Checking whether the close was performed as documented is an audit, and that lifecycle (programme, independence, fieldwork, findings, corrective action, verification) lives at /templates/internal-audit-process and /templates/audit-process. This page is the doing, not the checking: the auditor appears here only as the reason the close binder has to be retrievable.
Three decisions that most written close procedures leave implicit are drawn explicitly. "All sub-ledgers closed on time?" is a gate before any accrual is posted, with a loop back to the owners, because accruing over ledgers that are still open is what makes the first pass of the numbers disposable. "Reconciling items cleared?" separates a reconciliation that balances from one that is finished: the open-items branch sends the difference to be investigated and the reconciliation to be prepared again, rather than letting an explanation roll forward untouched for six months. And "Post-close adjustment required?" carries a real consequence: a material entry means "Reopen the period and post the entry", which loops all the way back to "Lock the trial balance" and re-runs the consolidation and the flux review, while an immaterial one goes on the summary of unadjusted differences. Sign-off is a decision too: "Results approved for release?" can be withheld, which is why the chart ends in a delayed filing as well as a closed period. Everything after the lock also sits in different lanes on purpose: consolidation, the flux review, the management pack and the statements are prepared by people who did not post the entries.
What this flowchart covers
In this template
- Five swimlanes (Sub-ledger owners, General ledger accountant, Financial controller, Group reporting and CFO) across six phases: Cut-off, Adjustments, Reconciliation and review, Consolidation and analysis, Reporting, and Sign-off and archive.
- Cut-off as a controlled boundary: "Cut off and close the sub-ledgers" performed by the owners of payables, receivables, payroll, expenses, fixed assets and inventory, then an "All sub-ledgers closed on time?" gate that loops back to them instead of letting the close proceed over an open ledger.
- Adjustments and intercompany: "Post accruals, prepayments and provisions" in the general ledger lane, followed by "Match intercompany balances" and the "Intercompany balances agree?" decision, whose out-of-balance branch runs through "Resolve the difference with the counterparty" and back round to matching.
- The reconciliation-exception loop: "Prepare balance-sheet reconciliations" feeding "Reconciling items cleared?", where open items go to "Investigate the reconciling item" in the sub-ledger lane and the reconciliation is prepared again before it can be reviewed.
- One approval gate for the ledger ("Reconciliations and journals approved?" with a "Correct and resubmit the journal" return path) then "Lock the trial balance", "Consolidate, eliminate and translate", and a flux review whose "Variances explained?" decision sends anything it cannot account for to "Investigate the unexplained movement" before the review runs again.
- Reporting and sign-off with two endings rather than one: the management pack and statutory statements behind a "Disclosures complete and accurate?" loop, a "Post-close adjustment required?" branch that can reopen the period, and the CFO's "Results approved for release?", which either runs through "Archive the close binder and evidence" to "Period closed and results reported" or stops at "Sign-off withheld and filing delayed".
When to use this template
- You are documenting the period-end close for the first time and the current version is a task spreadsheet with no owners, dependencies or review points on it.
- Your close is drifting later each quarter and you need to see whether the days go on waiting for sub-ledgers, on clearing reconciliations, or on reviewing figures that have already been circulated.
- You are moving to a new ERP or consolidation tool, and cut-off times, journal approval thresholds and elimination rules have to be agreed before anything is configured.
- An auditor has asked how journals are reviewed and where the close evidence is kept, and the honest answer at the moment is that it depends who prepared it.
- You are bringing a new financial controller or a shared service team into the close and need one page showing who does what, in what order, and what blocks what.
How it works
Rename the lanes to your finance function
Replace Sub-ledger owners, General ledger accountant, Financial controller, Group reporting and CFO with the roles you actually have. In a single-entity business the Group reporting lane collapses into the controller and consolidation becomes the translation of one foreign subsidiary, or disappears. In a shared service centre, split Sub-ledger owners into the teams that genuinely own each cut-off, because "finance" confirming a ledger is closed is nobody confirming it. Whatever else you merge, keep preparer and approver in different lanes.
Publish the close calendar with owners and times
Attach your calendar to the opening step and give every task an owner, a deadline with a time on it, and its dependencies. Publish it before the period ends rather than on day one, and show what is blocked by what: accruals wait on sub-ledger closure, consolidation waits on locked entity trial balances, the management pack waits on the flux review. A calendar that lists tasks without dependencies makes lateness look like one person's problem when it is the whole downstream queue's.
Write the cut-off rule for every sub-ledger
Put the specifics onto the closing step: the date and time postings stop for each ledger, who confirms it, and what happens to a transaction that arrives late — accrued now, or posted to the next period. Be explicit about the two that are usually vague, goods received but not invoiced and expenses claimed after the cut-off. Then decide who may reopen a sub-ledger once it has been confirmed closed, because in most systems that is a permission several people quietly hold.
Put your own thresholds on the two review gates
"Reconciling items cleared?" and "Reconciliations and journals approved?" are inert until you attach numbers. Set ageing limits by item type, a value above which a difference must be written off or escalated rather than carried forward, the journal value that requires a second approver, and the accounts that are reviewed every period regardless of movement. State what evidence must be attached, because a reconciliation supported only by another spreadsheet is not supported at all.
Define what triggers a reopen, and what does not
Agree in advance what makes a post-close adjustment material enough to justify "Reopen the period and post the entry", who authorises it, and what has to be rerun afterwards — here, the trial balance lock, the consolidation and the flux review. State the alternative just as clearly: immaterial items go on a summary of unadjusted differences and are judged in aggregate. Note where the line moves once accounts have been issued, since a correction after that is a restatement with its own disclosure path.
Walk it through with the close team, then publish a version
Take the last period as a test case and walk the chart through with a sub-ledger owner, the general ledger accountant, the controller and whoever runs consolidation, marking every point where the real sequence differed from the drawn one. Correct the map to what happens rather than to what the procedure claims. Then publish that revision and keep the earlier ones, and link it from the close calendar, so the team and the auditor asking which procedure was in force are reading the same version.
Frequently asked questions
What are the steps in the record to report process?
Close the sub-ledgers — payables, receivables, payroll, expenses, fixed assets and inventory — and confirm each one is shut rather than assuming it. Post accruals, prepayments and provisions for what those ledgers have not captured. Match intercompany balances and resolve differences with the counterparty entity. Prepare balance-sheet reconciliations and clear or explain every reconciling item. Have someone independent of the preparer approve the reconciliations and the journals. Lock the trial balance. Consolidate the group, eliminate intercompany and translate foreign currency. Run a flux or variance review against budget and prior period and explain the movements. Prepare the management reporting pack, draft the statutory statements and review the disclosures. Decide whether any post-close adjustment is material enough to reopen the period. Obtain sign-off, then archive the close binder. Different frameworks group these differently — record, reconcile, report and analyse is a common four-way split — but the spine is the same, and the two steps most often skipped are the independent review of journals and the archive.
How is record to report different from accounts payable and accounts receivable?
They meet at the sub-ledger boundary. Accounts payable owns supplier invoices from intake through matching, approval, the exception queue and the payment run. Accounts receivable owns invoicing, credit control, dunning, disputes and cash application. Both are continuous, transaction-level processes with their own controls and their own maps, at /templates/accounts-payable-process and /templates/accounts-receivable-process. Record to report is periodic and starts where those ledgers stop: it takes the closed sub-ledgers as given, accrues for what they have not processed, reconciles the balances they produce, and turns the result into reported figures. The practical test is what you are holding. If you are chasing an invoice, resolving a dispute or releasing a payment run, you are in a sub-ledger process. If you are asking whether the payables balance in the general ledger is complete, supported and correctly cut off, you are in record to report — and the answer depends on how well the sub-ledger process ran.
How long should a period-end close take?
There is no standard, and the number matters less than what sits behind it. A monthly close of four to six working days is generally treated as strong and one running into double figures as slow, but a five-day close achieved by reviewing nothing is worse than an eight-day close with signed reconciliations behind it. Look at where the days go rather than at the total. Days lost waiting for sub-ledgers to shut are a cut-off discipline problem. Days lost in reconciliation usually mean an exception backlog carried in from earlier periods. Days lost after the numbers exist mean review is scheduled too late to change anything. Shortening a close is mostly a matter of moving work out of it — reconciling balances weekly, matching intercompany continuously, agreeing recurring accruals in advance — rather than compressing the same work into fewer late evenings.
Who should approve journal entries at period end?
Someone other than the person who prepared them, with the supporting schedule in front of them. The usual arrangement is that the general ledger accountant prepares and posts, a financial controller reviews and approves, a second approver is required above an agreed value, and anything unusual — manual entries to cash, revenue, provisions or reserves — takes a separate route. Two populations deserve review of their own: journals posted after the sub-ledgers closed, and top-side entries booked at group level after entity ledgers are locked, because that is where management override would appear if it were happening. Approval has to be recorded somewhere it can be retrieved alongside the journal a year later, not in an email thread. The question at audit is rarely whether an entry was approved; it is who approved it, when, and against what evidence.
How is this different from an internal audit process flowchart?
One performs the close, the other checks it. This chart is the finance team's own operating cycle, running every period: cut-off, adjustments, reconciliations, journal approval, consolidation, reporting and sign-off. An audit is an independent examination of whether that happened as documented, and it has a different shape — an audit programme, an independence check, planning, fieldwork and sampling, findings classified and reported, corrective action, and verification that the action worked. That lifecycle is mapped separately at /templates/internal-audit-process, with a broader version covering internal, supplier and certification audits at /templates/audit-process. The two connect at one step in this chart, "Archive the close binder and evidence": the reconciliations, journal support, consolidation workings and disclosure checklist retained there are exactly what an internal or external auditor samples, which is why archiving is a step in the process rather than an afterthought.
Where this process fits
In most operations this process follows Payroll process flowchart (cut-off to payment and filing).
Comes before
- Payroll process flowchart (cut-off to payment and filing) — Payroll process flowchart from cut-off to payment: starters and leavers, approved hours, variance checks, gross-to-net, an independent pre-payment review, funding, the bank file, statutory filing, payslips and the journal.