A reliable accounting close makes it possible to follow a material balance from the reported number back through the ledger, journal entries, reconciliations and source evidence—and to see who prepared and reviewed each step. Build the close as a controlled period-end workflow, not just a checklist: define the period boundary, owners, required evidence, exception handling and approval trail before work begins.
What makes an accounting close source-linked?
A source-linked close connects the work and its evidence across the reporting chain. For a material account or posting, a reviewer should be able to identify the relevant source records, understand how they support the balance or calculation, find any related journal entry, inspect reconciliation differences and see the preparation and review history.
As an Amazon Associate I earn from qualifying purchases.
This is broader than attaching files to journal entries. SAP Help defines month-end closing as “all activities involved in closing a posting period” and includes reporting, documenting posting data, internal evaluations and archiving among those activities. The close therefore needs a defined period boundary and a retained reporting trail, as well as supporting documents. SAP Help: Month-End Closing
Recommended Free Tools
No software feature alone makes a close complete or correct. The organization still needs appropriate accounting judgments, evidence, access controls, review and exception resolution.
Design the close in six steps
1. Set the period boundary and assign responsibility
Document the fiscal period, close calendar and posting cutoff. For every task, name the preparer, reviewer, prerequisites and escalation path. Identify upstream systems or teams whose activity must be finalized before the ledger is closed, and define how late, corrected or disputed activity will be handled.
Microsoft’s Dynamics GP guidance advises posting period- and year-end transactions before closing fiscal periods; later postings may require reopening a period. That is product guidance, not a universal accounting rule. Adapt the sequence and any reopening process to your system configuration and accounting policy. Microsoft Learn: General Ledger – Dynamics GP
2. Build an evidence map for each recurring task
Before a task goes live, specify what it is intended to establish and what a reviewer must be able to inspect. The map should connect the account or assertion to its source records, identifiers, reconciliation or calculation, related journal entry if there is one, preparer, reviewer, approval evidence and storage location.
- Source records: Name the expected documents or system records and retain stable identifiers, such as document numbers or references.
- Accounting link: Record the account and period, the calculation or reconciliation, and the journal-entry reference where applicable.
- Control evidence: Retain evidence of preparation, review, approval and the handling of exceptions.
- Retrieval: Specify where the evidence and its related reports will be stored so a later reviewer can find them.
An internal-audit manual from the Ghana Microfinance Institutions Network illustrates an audit trail linking a receipt and collection sheet to a general-ledger posting, with date and number references. It is a useful example of traceability, not a universal template. Ghana Microfinance Institutions Network Knowledge Hub: Risk Management I: Internal Controls and Fraud Prevention for Microfinance Institutions
3. Reconcile and document before sign-off
Define what counts as a completed reconciliation rather than relying on a checked box. At minimum, record the account and period in scope, the source and ledger balances, reconciling items, supporting evidence, preparer and reviewer, and the disposition of unresolved differences. If an item remains open, document its owner and next action under your organization’s procedure.
Sage Intacct’s guidance describes using a sequenced month-end checklist and retaining evidence that supporting controls operated. It also discusses recording who made a master-data change and when. These are examples of system-supported control evidence; the organization must determine which records and approvals its own process requires. Sage Intacct Help: Record to Report workflow controls
4. Post adjustments with traceable references
Keep the journal entry connected to the supporting records and, when relevant, to the original transaction. Microsoft documents source-document IDs and references, audit trail codes that can trace posting sequence to origin, and transaction matching that can link distributions in separate journal entries—including a period-end adjustment and its original transaction. Such links can help an auditor follow related activity, but matching features and terminology differ by ledger system. Microsoft Learn: General Ledger – Dynamics GP
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
5. Review the close package and control period status
Specify who approves the close, which reports and exceptions they review, how approval is recorded and what establishes the final period state. Also define how post-close corrections are requested, authorized, posted and documented. A system’s ability to lock a folder or period is not a substitute for the organization’s approval policy or evidence that the underlying accounting is sound.
SAP identifies reporting and documentation of posting data as period-close activities. Close-management providers describe features such as recorded sign-offs and locking; treat those descriptions as vendor claims, not independent evidence that a control is effective.
6. Archive records and improve the next close
Retain close reports, reconciliations, source records, journal references, approvals and exception dispositions under organizational policy and applicable requirements. Make sure staff can retrieve the package by period and account or task. SAP lists outputs such as Balance Audit Trail, accounting reconciliation, balance lists and open-item lists among close documentation, and describes archiving documents. Its documentation notes that archiving frequency depends on system data volume; it does not establish a universal legal retention period. Determine retention obligations for the relevant records and jurisdiction separately. SAP Help: Month-End Closing
After sign-off, review recurring exceptions, late inputs and task bottlenecks. Use the findings to adjust dependencies, evidence requirements or ownership for the next period, while preserving the approved close record.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat to include in a source-linked close checklist
A useful checklist combines task status with enough context to show what the task proves and how it was controlled. For each close task, include:
- Period, account or process scope, and task objective.
- Preparer, reviewer, due date and prerequisite tasks.
- Expected source records and their identifiers.
- Reconciliation or calculation method and related journal-entry reference, if applicable.
- Required review or approval evidence and where it is retained.
- Exception status, disposition, owner and follow-up where needed.
- Completion date and any required period-close or post-close action.
The checklist should reflect the entity’s accounting policy, materiality, systems and control design. A task marked complete without the required support or review evidence is not equivalent to a documented, reviewed close activity.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to evaluate accounting and close-management systems
Compare systems against the workflow your organization actually needs, rather than assuming that a checklist, audit trail or document attachment feature is sufficient by itself. Microsoft, SAP and Sage document accounting-system capabilities; close-management providers describe their own products. Vendor feature descriptions are not independent evaluations of control effectiveness, so verify current availability, integration scope, access controls and record retrieval in the configuration you intend to use.
| Evaluation area | What to verify |
|---|---|
| Source evidence | Can users retain source-document identifiers and navigate from ledger activity to the originating record? |
| Journal linkage | Can tasks and documents be connected to journal entries, and can related transactions be matched or grouped? |
| Control history | Does the system retain who prepared, reviewed, changed or approved relevant records, and when? |
| Reconciliation review | Can reviewers inspect balances, supporting records, reconciling items and unresolved differences before sign-off? |
| Period control | Can the organization govern posting periods, close status, corrections and reopening in line with its process? |
| Retention and retrieval | Can reports and supporting documents be retained and retrieved under organizational policy? |
| Permissions and scale | Can permissions and workflow roles reflect the organization’s structure and accounting team? |
CloseCore describes reconciliation checks, task and document links to journals, sign-off history, folder locking and user activity history. Loopfour describes task dependencies, owners, reconciliations, journal entries, approvals and activity records. These are each provider’s descriptions of its own product; confirm whether the capabilities are currently available and fit your systems and controls. CloseCore: Month-End Close Management Software · Loopfour: Month-End Close Automation
Quick Recap
Common design failures to prevent
- Closing without a clear cutoff: Transactions can be assigned to the wrong period if posting expectations and late-activity procedures are unclear.
- Using attachments without traceable references: A file is less useful if the reviewer cannot tell which transaction, account or calculation it supports.
- Recording completion without review evidence: Task status alone does not establish who reviewed the work or what they considered.
- Leaving exceptions ownerless: Unresolved differences need a documented disposition and accountable follow-up.
- Treating a software feature as a control: Matching, audit trails, locking and sign-off functions support a process; their presence does not establish that the process is appropriately designed or operated.
- Assuming one retention rule fits every record: Retention depends on the record and applicable requirements; set it through the organization’s policy and jurisdiction-specific advice.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
