Balance Sheet Account Reconciliation Template
GL versus independent source, reconciling items with type, age and owner, unexplained difference threshold, roll-forward, evidence index, preparer and reviewer sign-off
使用方法: Use it each period for every balance sheet account, at the frequency its risk tier sets. Fill the account header and independent source first, then list reconciling items with type, age and owner and recompute the unexplained difference. The main pitfall is a supporting balance taken from the ledger itself, or a difference parked in suspense.
预览
Account Reconciliation: [Entity] [GL account] [Period end]
Balance sheet account reconciliation with preparer and reviewer evidence: account header and risk tier, balance per general ledger against an independent source, reconciling items with age and owner, unexplained difference against a threshold, roll-forward of activity, evidence index, ageing and write-off decisions, preparer certification, reviewer checklist and escalation. Control language follows the GAO Standards for Internal Control in the Federal Government (Green Book, GAO-25-107721, 2025 revision, US public domain). COSO, IFRS, ISA and PCAOB standards are cited by name only. Replace every
[bracketed]value and every row marked Example. This is a document format, not accounting, audit, tax, legal or financial advice. Obtain the standard or law for the normative text.
Document control
| Field | Value |
|---|---|
| Document ID | [REC-account-entity-YYYY-MM] Example: REC-1250-CC-DE-2027-03 |
| Version | [0.1] |
| Status | [In preparation / Prepared / Reviewed / Escalated] |
| Owner | [@account-owner] |
| Approvers/reviewers | [@reviewer] (not the preparer) |
| Last updated | YYYY-MM-DD |
| Classification | [Confidential] |
| Entity | [Entity code and name] Example: CC-DE, Corvid Commerce GmbH |
| GL account | [Number and name] Example: 1250 Receivable from PSP (clearing) |
| Period end | YYYY-MM-DD Example: 2027-03-31 |
| Account currency | [EUR] |
| Control ID | [CTL-ID from the risk and control matrix] Example: CTL-R2R-006 |
| Due date (prepare / review) | YYYY-MM-DD / YYYY-MM-DD Example: WD+3 2027-04-05 / WD+4 2027-04-06 |
Approvals
| Role | Name | Decision | Date |
|---|---|---|---|
| Preparer | [@name] | [Prepared, certification in section 8] | YYYY-MM-DD |
| Reviewer | [@name] | [Reviewed / Returned / Escalated] | YYYY-MM-DD |
| Escalation approver (if any) | [@name] | [Write-off or adjustment approved] | YYYY-MM-DD |
Revision history
| Version | Date | Author | Change summary |
|---|---|---|---|
| 0.1 | YYYY-MM-DD | [@name] | Balances loaded, reconciling items listed |
| 0.9 | YYYY-MM-DD | [@name] | Example: Preparer certification signed |
| 1.0 | YYYY-MM-DD | [@name] | Example: Reviewed, RI-02 correction posted as JE-2027-03-0418 |
Contents
- Account header and risk tier
- Balance per ledger and supporting source
- Reconciling items
- Unexplained difference and threshold
- Roll-forward of activity
- Supporting evidence index
- Ageing, clearance and write-off decisions
- Preparer certification
- Reviewer checklist and sign-off
- Exceptions escalated
- Reconciliation policy reference
- Glossary and references
1. Account header and risk tier
Describe the account in plain words: what transactions post to it, from which systems, and what the balance represents at period end. The risk tier sets the frequency, the reviewer level and the evidence standard. Assign the tier with the criteria in section 11 and review it at least once a year, or when the account's activity changes.
| Field | Value |
|---|---|
| Account purpose | [What the balance represents] Example: Card and wallet sales captured by the webshop but not yet paid out by the PSP to the CC-DE bank account |
| Posting sources | [Systems and entry types] Example: Order-to-cash interface (sales, refunds), bank statement import (payouts), manual entries (fees, chargebacks) |
| Normal balance | [Debit / Credit] Example: Debit |
| Risk tier | [High / Medium / Low] Example: High: high volume, cash-like, manual entries for fees and chargebacks, fraud exposure through refunds |
| Assertions at risk | [Existence, completeness, accuracy, cut-off, valuation] Example: Existence, completeness, cut-off |
| Frequency | [Monthly / Quarterly] Example: Monthly |
| Independent source | [Document not produced by the GL] Example: PSP merchant balance report downloaded from the PSP portal |
| Preparer / reviewer | [@names] Example: CC-DE accountant / CC-DE controller |
| Linked control | [Control ID and short description] Example: CTL-R2R-006, monthly PSP clearing reconciliation reviewed by entity controller |
The Green Book asks management to design control activities that achieve objectives and respond to risks (Principle 10) and to use quality information from reliable sources (Principle 13). For a reconciliation, that translates into two tests of the source: it must come from outside the ledger, and the preparer must be able to show how it was obtained (a download log, a confirmation, a system report with parameters). A spreadsheet that someone else typed is not an independent source until it is agreed to something that is.
2. Balance per ledger and supporting source
Take the GL balance from the trial balance after the entity GL lock, not from a working report. Take the supporting balance from the independent source dated at the same period end and the same time zone. If the source is in a different currency, translate at the closing rate and show both amounts.
| Line | Description | Amount (EUR) | Source reference |
|---|---|---|---|
| A (Example) | Balance per GL, account 1250, CC-DE, 2027-03-31 | 1,284,600.00 | [TB-CC-DE-2027-03, run 2027-04-06 09:10] |
| B (Example) | Balance per PSP merchant balance report, 2027-03-31 23:59 CEST | 1,236,900.00 | [EV-01] |
| C = A - B (Example) | Difference to explain | 47,700.00 | Computed |
The difference is explained in section 3. If the difference is zero, still list items that net to zero (for example a timing item offset by an error), because the reviewer needs to see them.
3. Reconciling items
Each reconciling item has an ID, a type, the date it arose, its age at period end, an owner and an expected clearance date. Use four types: timing (will clear by itself in the normal course, such as a sale captured on the last day and settled the next), GL error (the ledger is wrong and needs a journal entry), source error (the external source is wrong and the counterparty must correct it), and under investigation (cause not yet known). A GL error that is material for the account is corrected in the period, not carried as a reconciling item; a GL error below the correction threshold may be corrected in the next period if the reviewer agrees.
| Item ID | Description | Type | Date arose | Age (days) | Amount (EUR) | Action | Owner | Expected clearance |
|---|---|---|---|---|---|---|---|---|
| RI-01 (Example) | Card sales captured 2027-03-31 after the PSP batch cut-off, in the 2027-04-01 batch | Timing | 2027-03-31 | 0 | 38,450.00 | None; agree to 2027-04-01 PSP batch | [@accountant-de] | 2027-04-01 |
| RI-02 (Example) | PSP processing fees for March deducted by the PSP, not yet booked in GL | GL error | 2027-03-31 | 0 | 4,120.00 | JE-2027-03-0418: Dr 6810 Payment processing fees, Cr 1250 | [@accountant-de] | 2027-04-06 |
| RI-03 (Example) | Chargeback on order 88412 debited by PSP, disputed with evidence of delivery, not booked | GL error (below correction threshold) | 2027-02-14 | 45 | 2,380.00 | Reclassify on 2027-04-01: Dr 1255 Chargebacks in dispute, Cr 1250; dispute outcome then decides loss or recovery | [@ar-lead-de] | 2027-04-30 |
| RI-04 (Example) | Customer refund processed in PSP portal 2027-03-30, refund entry posted in GL on 2027-04-01 | GL error (below correction threshold) | 2027-03-30 | 1 | 1,950.00 | None; agree to April GL posting | [@accountant-de] | 2027-04-01 |
| Total (Example) | 46,900.00 |
The total of reconciling items is 38,450.00 + 4,120.00 + 2,380.00 + 1,950.00 = EUR 46,900.00. RI-02 is a GL error that is corrected in March because the fee belongs to March expense; after JE-2027-03-0418 the GL balance becomes EUR 1,280,480.00 and RI-02 drops out of the reconciliation. The reconciliation is presented here before the correction so that the reviewer sees the error and its fix; the final version shows the corrected balance with a reference to the entry. RI-03 and RI-04 are also GL errors, but each is below the EUR 2,500 correction threshold in section 11, so the reviewer agrees to correct them in April. RI-04 is a cut-off error (the refund belonged to March) that the April posting clears. RI-03 is not unexplained: the PSP has already taken the cash, so the balance is a claim on the cardholder's bank, not on the PSP. Moving it to a separate "chargebacks in dispute" account keeps the PSP clearing account clean and makes the dispute visible on its own ageing report; carrying a known item as "under investigation" would hide it.
4. Unexplained difference and threshold
The unexplained difference is the part of the difference that no reconciling item explains.
where is the GL balance, is the supporting balance and are the reconciling items with the sign convention in the guidance block.
| Line | Amount (EUR) |
|---|---|
| Difference A - B (Example) | 47,700.00 |
| Less total reconciling items (Example) | (46,900.00) |
| Unexplained difference U (Example) | 800.00 |
| Threshold: lower of EUR 1,000 and 0.1% of A (0.1% x 1,284,600.00 = 1,284.60) (Example) | 1,000.00 |
| Within threshold? (Example) | Yes |
An unexplained difference below the threshold does not need an entry this period, but it is not ignored. Record it as an item under investigation in the next period's reconciliation with an owner. If the same account shows an unexplained difference three periods in a row, escalate it in section 10 even if each one is small, because a repeating difference usually means a missing posting rule. An unexplained difference above the threshold blocks the reviewer's sign-off until it is explained or escalated.
In the example, the EUR 800.00 is traced in April to a currency rounding difference on GBP card sales processed by the PSP for the CC-DE webshop; the fix is a mapping change in the order-to-cash interface, logged as ISS-2027-04-02 in the April close.
5. Roll-forward of activity
A roll-forward is a second, independent check. It confirms that last period's reviewed balance is still the starting point and that each type of movement agrees to its source report. It is required for high-risk accounts and useful for any account with large gross flows and a small net balance, such as clearing accounts.
| Line | Description | Amount (EUR) | Agreed to |
|---|---|---|---|
| Opening balance 2027-02-28 (Example) | Reviewed closing balance of REC-1250-CC-DE-2027-02 | 1,190,300.00 | [Prior reconciliation] |
| Add: card and wallet sales captured (Example) | Order-to-cash interface postings | 9,842,750.00 | [Sales capture report] |
| Less: payouts received in bank (Example) | Bank statement import | (9,731,200.00) | [Bank reconciliation] |
| Less: refunds booked (Example) | Order-to-cash interface | (12,980.00) | [Refund report] |
| Less: February PSP fees booked in March (Example) | Manual JE-2027-03-0102 | (4,270.00) | [PSP February invoice] |
| Closing balance per GL 2027-03-31 (Example) | Before RI-02 correction | 1,284,600.00 | Line A |
Check: 1,190,300.00 + 9,842,750.00 - 9,731,200.00 - 12,980.00 - 4,270.00 = 1,284,600.00. The February fees booked in March show the same pattern as RI-02: fees have been booked one month late. The reviewer raises this as a process issue (section 10), because the March correction is only a fix for one period.
6. Supporting evidence index
List every document the reconciliation relies on. Store evidence in the controlled close folder with read-only access after review. A reviewer or auditor should be able to re-perform the reconciliation from the evidence index alone. Where evidence is a system report, record the report name, parameters and run time.
| Evidence ID | Description | Source | Obtained by / date | Location |
|---|---|---|---|---|
| EV-01 (Example) | PSP merchant balance report as at 2027-03-31 23:59 CEST | PSP portal download, report "merchant balance", account CC-DE | [@accountant-de] 2027-04-01 | [Close folder / 2027-03 / CC-DE / 1250] |
| EV-02 (Example) | PSP batch report 2027-04-01 showing RI-01 transactions | PSP portal | [@accountant-de] 2027-04-02 | [Same folder] |
| EV-03 (Example) | PSP March fee invoice | PSP portal, invoice [number] | [@accountant-de] 2027-04-02 | [Same folder] |
| EV-04 (Example) | Chargeback notice and dispute submission for order 88412 | PSP dispute module | [@ar-lead-de] 2027-02-20 | [Same folder] |
| EV-05 (Example) | GL trial balance extract, account 1250 | ERP, TB report, company 1100, period 2027-03 | [@accountant-de] 2027-04-06 | [Same folder] |
| EV-06 (Example) | Sales capture, refund and bank reports for the roll-forward | ERP and bank portal | [@accountant-de] 2027-04-05 | [Same folder] |
7. Ageing, clearance and write-off decisions
Age reconciling items from the date they arose, not from the date they were first listed. Items older than the policy limit need a decision: chase, correct or write off. Write-offs are journal entries and follow the normal approval limits; they are never posted by the preparer without approval. Track the ageing profile over time; a growing tail is a sign that the account's process is failing, even if every reconciliation is signed on time.
| Age bucket | Count | Amount (EUR) | Items | Decision required |
|---|---|---|---|---|
| 0 to 30 days (Example) | 3 | 44,520.00 | RI-01, RI-02, RI-04 | No |
| 31 to 60 days (Example) | 1 | 2,380.00 | RI-03 | Monitor; decide by day 60 |
| 61 to 90 days (Example) | 0 | 0.00 | Entity controller decision | |
| Over 90 days (Example) | 0 | 0.00 | Financial controller decision; write-off or provision | |
| Total (Example) | 4 | 46,900.00 |
Check: 38,450.00 + 4,120.00 + 1,950.00 = 44,520.00; 44,520.00 + 2,380.00 = 46,900.00.
| Decision ID | Item | Decision | Amount (EUR) | Entry | Approved by | Date |
|---|---|---|---|---|---|---|
| WO-2027-03-01 (Example) | RI-03 | If the dispute is lost by 2027-04-30, book the chargeback as a loss (Dr 6820 Chargeback losses, Cr 1255); if won, clear 1255 against the PSP re-credit | 2,380.00 | [Planned JE in April] | [@controller-de] | 2027-04-06 |
Provisioning for items that are likely to be lost follows the group's expected credit loss and provisions policies, documented in Accounting Policy Manual (finance/accounting-policy-manual); the reconciliation records the decision and links to the entry.
8. Preparer certification
The preparer signs the statements below. Each statement is about this reconciliation only. If a statement is not true, strike it, explain why in the comment, and tell the reviewer before they start.
| No. | Statement | Confirmed |
|---|---|---|
| P1 | The GL balance is taken from the locked trial balance for the period | [Yes / No] |
| P2 | The supporting balance comes from a source independent of the GL, at the same cut-off | [Yes / No] |
| P3 | Every reconciling item is listed with type, age, owner and clearance date | [Yes / No] |
| P4 | GL errors above the correction threshold have been corrected by approved journal entries | [Yes / No] |
| P5 | The unexplained difference is within the threshold or escalated in section 10 | [Yes / No] |
| P6 | The roll-forward agrees opening balance, activity and closing balance | [Yes / No] |
| P7 | All evidence is indexed in section 6 and stored in the controlled folder | [Yes / No] |
| P8 | I did not prepare or approve any entry that I am relying on as evidence without disclosing it here | [Yes / No] |
| Preparer | Signature or system approval | Date | Comment |
|---|---|---|---|
| [@name] | [Electronic sign-off reference] | YYYY-MM-DD | Example: RI-02 corrected by JE-2027-03-0418 prepared by me and approved by the entity controller |
9. Reviewer checklist and sign-off
The reviewer must not be the preparer and should not have posted entries to the account in the period. Record what was checked, not only that it was checked. Comments and questions raised during review stay in the file, with their answers, because they are the evidence that the review was precise enough to detect an error. Under the Green Book, monitoring and remediation (Principles 16 and 17) depend on deficiencies being found and acted on; a review that never finds anything should itself be questioned.
| No. | Review step | Result | Comment |
|---|---|---|---|
| R1 | Agree GL balance to locked trial balance | [Done / Exception] | |
| R2 | Agree supporting balance to source document; check source is independent and dated at period end | [Done / Exception] | Example: EV-01 opened in portal, matches |
| R3 | Vouch reconciling items above [EUR 10,000] and a sample of smaller items to evidence | [Done / Exception] | Example: RI-01 agreed to EV-02 batch totals |
| R4 | Confirm item types are correct (timing versus error) and that errors have entries | [Done / Exception] | Example: RI-03 and RI-04 retyped from timing and investigation to GL error; below threshold, April entries agreed |
| R5 | Check arithmetic of the reconciliation and roll-forward | [Done / Exception] | |
| R6 | Check ageing and that overdue items have decisions | [Done / Exception] | |
| R7 | Check unexplained difference against threshold and trend | [Done / Exception] | Example: EUR 800, first occurrence |
| R8 | Consider whether the balance looks reasonable against activity and prior periods | [Done / Exception] | Example: Up 7.9% before the RI-02 correction (7.6% after), consistent with late-March sales |
| R9 | Confirm the certification in section 8 is complete | [Done / Exception] |
| Reviewer | Decision | Signature or system approval | Date |
|---|---|---|---|
| [@name] | [Reviewed / Returned for correction / Escalated] | [Reference] | YYYY-MM-DD |
If the reviewer returns the reconciliation, the preparer updates it and the reviewer reviews again; both rounds are recorded in the revision history.
10. Exceptions escalated
Escalate when an unexplained difference exceeds the threshold, when an item passes the age limit without a decision, when the same issue recurs, or when the reconciliation was not prepared or reviewed on time. Escalated issues go to the close issues log in Month-End Close Checklist (finance/month-end-close-checklist). If the issue suggests that a key control did not operate or was not designed well enough, the internal control lead evaluates it in Control Deficiency Evaluation (compliance/control-deficiency-evaluation).
| Escalation ID | Issue | Escalated to | Date | Outcome |
|---|---|---|---|---|
| ESC-2027-03-01 (Example) | PSP fees booked one month late in February and March (RI-02 and roll-forward) | Financial controller | 2027-04-06 | Accrue PSP fees monthly from the PSP fee report on WD+1; added to GL-01 in the close checklist from April 2027 |
11. Reconciliation policy reference
The values below come from the group reconciliation policy. They are Example values for Corvid Commerce Group plc; set your own in your accounting manual, reflecting materiality for the financial statements and the risk of each account.
| Policy element | High risk | Medium risk | Low risk |
|---|---|---|---|
| Typical accounts (Example) | Cash, clearing, intercompany, revenue-related, judgemental provisions, suspense | Payables, accruals, prepayments, fixed assets | Share capital, long-term deposits, dormant accounts |
| Frequency (Example) | Monthly | Monthly | Quarterly |
| Due date (Example) | Prepare WD+3, review WD+4 | Prepare WD+4, review WD+5 | Prepare WD+5, review WD+7 |
| Reviewer level (Example) | Entity controller | Entity controller | Senior accountant |
| Roll-forward required (Example) | Yes | If gross activity above EUR 1 million | No |
| Unexplained difference threshold (Example) | Lower of EUR 1,000 and 0.1% of balance | Lower of EUR 5,000 and 0.5% of balance | EUR 10,000 |
| Correct GL errors in period (Example) | Above EUR 2,500 | Above EUR 10,000 | Above EUR 25,000 |
| Age limit for decision (Example) | 60 days | 90 days | 180 days |
Assign risk tiers using these criteria: transaction volume, use of manual entries, degree of judgement, exposure to fraud or misappropriation, history of errors, and whether the account is close to a material line in the financial statements. Review the tier for every account once a year and when a new system, process or entity is added. Accounts with zero balance and no activity still need a quarterly check that nothing posted to them, because an unexpected posting is itself a signal.
11.1 Common errors to look for
Reviewers and preparers find the same problems across many organisations. A supporting balance taken from a report that reads the GL (for example, an ERP "bank balance" screen rather than the bank statement) gives no independent evidence. Reconciling items described only as "timing" with no transaction reference cannot be vouched. Items that are positive one month and negative the next with similar amounts often mean a recurring entry is posted in the wrong period. Foreign-currency accounts reconciled in the functional currency only can hide differences in the transaction currency; reconcile in the transaction currency first, then check the revaluation. Finally, a reconciliation that is always completed on the due date by the same person, with no comments from the reviewer, deserves a second look by the financial controller from time to time.
11.2 Choosing the independent source by account type
The right source depends on what the balance represents. For bank and cash accounts, use the bank statement or a bank confirmation at the period-end cut-off. For clearing accounts with payment processors, use the processor's merchant balance or settlement report. For receivables and payables control accounts, agree the GL to the sub-ledger ageing, and then rely on the sub-ledger's own controls (customer statements, supplier statement reconciliations for the largest suppliers). For intercompany balances, use the counterparty's ledger balance as confirmed in the intercompany matching tool. For prepayments, accruals and deferred revenue, use a schedule built from contracts or invoices, and check a sample of schedule lines to the underlying documents each period. For fixed assets, agree to the fixed asset register roll-forward. For provisions and other judgemental balances, the source is the approved calculation or memo; the reconciliation confirms that the GL equals the approved amount and that the memo is current. For tax balances, use the tax computation and the latest returns or authority statements.
11.3 Automated matching
Many organisations use matching software for high-volume accounts. Automation changes the evidence, not the need for review. Keep the matching rules under change control, review the rule set at least yearly, and treat unmatched items exactly like manual reconciling items: typed, aged and owned. Auto-certification of low-risk accounts with zero balance and no activity is acceptable when the policy allows it and the rule itself is tested. The reviewer still signs the overall reconciliation status for the entity each period.
12. Glossary and references
12.1 Glossary
| Term | Meaning in this template |
|---|---|
| Reconciliation | Comparison of a GL balance with an independent source and explanation of the difference |
| Reconciling item | An identified, documented reason for part of the difference |
| Timing item | Reconciling item that clears in the normal course in a later period |
| Unexplained difference | Part of the difference not explained by reconciling items |
| Roll-forward | Opening balance plus period activity equals closing balance |
| Independent source | Evidence produced outside the GL being reconciled |
| Risk tier | Classification that sets reconciliation frequency, depth and review level |
| Clearing account | Account that temporarily holds amounts between two processes, expected to be near zero or to turn over quickly |
| Chargeback | Reversal of a card payment initiated by the cardholder's bank |
| Suspense account | Account used to hold unidentified items; should be empty at period end |
12.2 References
| Reference | Version or date | Use |
|---|---|---|
| GAO, Standards for Internal Control in the Federal Government (GAO-25-107721) | 2025 revision, issued 2025-05-15, effective from FY2026 | Control language: control activities (Principle 10), quality information (Principle 13), monitoring and remediation (Principles 16 and 17) |
| SEC Release 33-8810 / 34-55929 | Effective 2007-06-27 | Management's ICFR evaluation guidance for SEC registrants (applies to Corvid as a Form 20-F filer); reconciliations as period-end controls |
| COSO Internal Control, Integrated Framework (2013) | Name only | Framework widely used for ICFR; not reproduced |
| ISA 240 (Revised), PCAOB AS 2401 | Names only; ISA 240 (Revised) for periods beginning on or after 2026-12-15 | Auditor fraud procedures that look at manual adjustments, including reconciling entries |
| [Group reconciliation policy] | [Version] | Risk tiers, thresholds, due dates |
| [Group accounting manual] | [Version] | Correction and write-off approval limits |
Standard and licence note
Based on the GAO Standards for Internal Control in the Federal Government (Green Book, GAO-25-107721, 2025) and SEC Release 33-8810 (2007), both US government works in the public domain; they are cited and the text here is original. The reconciliation layout, risk tiers and thresholds are original practitioner writing; no standard prescribes them, and the threshold values are examples, not requirements. COSO, IAASB (ISA 240) and PCAOB (AS 2401) materials are cited by name and number only; no text from them is reproduced or paraphrased. Corvid Commerce GmbH and every figure are fictional. Check the current official versions of every cited source and your local law before use. Template licence: MIT.
相关模板
13-Week Cash Flow Forecast Template (Direct Method)
Direct-method weekly cash forecast: opening cash and facilities, receipts and disbursements by category, weekly roll, headroom vs minimum, variance and bridge, levers
财务、投资与会计Annual Budget Template (FP&A Operating Plan)
Annual budget pack: targets, calendar, assumptions, revenue drivers, headcount, opex, capex, three statements, sensitivities, phasing, sign-off
财务、投资与会计Annual Credit Review Template (Covenant Monitoring, Early Warning, Watch List)
Lender periodic review: utilisation, performance vs case, covenant recalculation, EWIs, watch list, rating, IFRS 9 stage, refinancing, actions