A supplier invoice that arrives after month-end can still relate to goods or services received before the reporting date. If the obligation is omitted, expenses and liabilities may be understated, margins overstated and working-capital reporting distorted. The reverse is also true: a payment made after month-end does not automatically belong in the prior period.
The controller’s task is to establish what the business had received or consumed by the cutoff date, identify obligations that belong in the period, estimate amounts where invoices are missing, and preserve evidence showing why each item was accrued—or excluded.
What an unrecorded-liabilities search should accomplish
An unrecorded-liabilities search is a controlled process for finding obligations that existed at the reporting date but may not yet appear in accounts payable or the general ledger. It should combine transaction data with operational evidence: purchase orders, receiving records, service-entry approvals, contracts, vendor statements, expense reports and subsequent invoices or payments.
It is not simply a review of every payment after period-end. Each candidate must be assessed against the underlying facts, the applicable accounting framework and the company’s materiality and estimation policies.
10 controls to strengthen AP cutoff and liability completeness
1. Set a documented cutoff timetable
Publish a close calendar that states the last date for receiving invoices, approving service entries, submitting employee expenses and recording goods receipts. Define the accounting cutoff separately from the administrative invoice deadline. A late invoice should enter the review queue, not automatically be pushed into the next period.
Assign clear owners across procurement, receiving, operations, project managers and accounts payable. Require each location or business unit to certify that material goods and services received before period-end have been reported to Finance.
2. Build a complete population from multiple systems
Do not rely on the AP invoice register alone: it cannot identify an invoice that has not arrived or has not been entered. Build a population from relevant sources, including:
- Open purchase orders and goods receipts not yet matched to invoices.
- Service-entry sheets, work-completion approvals and project milestones.
- Invoices received but blocked, parked or awaiting workflow approval.
- Corporate-card transactions, employee expense claims and procurement-card feeds.
- Recurring contracts for utilities, rent, logistics, maintenance, software and professional services.
- Vendor statements and subsequent disbursement records.
Document report parameters, extraction dates, entities, ledgers and excluded transaction types. Reconcile key reports to their source subledgers or control totals so the review population is demonstrably complete.
3. Review subsequent disbursements systematically
Extract payments made after period-end for a risk-based window. The appropriate window depends on invoice cycles, payment terms, business seasonality and the time needed to receive invoices; it should not be an arbitrary fixed number of days.
For each material payment, inspect the invoice, purchase order or contract, evidence of receipt or service, invoice date, service period, payment date and general-ledger posting. Ask one central question: did the company receive the goods or services, or otherwise incur the obligation, by the reporting date?
Include all relevant payment channels—not only the main AP payment run. Consider wires, ACH, cheque payments, purchasing cards, employee reimbursements and payments initiated by local entities.
4. Match unbilled receipts and completed services
Review goods receipts and approved service entries that have no corresponding supplier invoice. Investigate aged or unusual balances, receipts posted near the cutoff, and purchase orders with substantial completion but no invoice. For services, obtain evidence such as approved timesheets, milestone acceptance, usage reports or project-manager confirmation.
A purchase order by itself does not prove that a liability has been incurred. Conversely, a missing purchase order does not eliminate an obligation when the company has received and accepted the goods or services. Escalate exceptions to the business owner and apply the relevant accounting policy.
5. Capture non-PO and decentralized spending
Some liabilities bypass the standard procurement workflow: legal services, consulting, freight, recruiting, marketing, repairs, customs brokerage and local facility costs are common examples. Send a short, structured certification to budget owners asking them to identify material work completed, goods received or contractual charges incurred but not yet invoiced.
Require support for significant responses and follow up on non-responses from high-spend departments. A blanket “no unrecorded liabilities” confirmation is weak if the signer has not reviewed relevant contracts, receiving data or open commitments.
6. Calculate recurring accruals using current evidence
For recurring services, use the contract rate, service period, usage data or a reasonable operational driver. For example, if a monthly maintenance service was delivered through the final day of the month but the invoice arrives two weeks later, accrue the portion attributable to the completed service period using the best available support.
Compare estimates with the eventual invoice and explain significant differences. Update assumptions when rates, volumes, contract terms or service dates change. Avoid carrying forward last month’s estimate without checking whether the underlying activity actually occurred.
7. Use vendor statements as a completeness check
Obtain statements for material or higher-risk suppliers and reconcile them to the AP subledger. Investigate invoices shown by the vendor but absent from the ledger, unapplied credits, disputed balances and payments not reflected by the supplier. Prioritize vendors with high transaction volumes, complex service arrangements, frequent disputes or a history of late billing.
Vendor statements are useful corroborating evidence, not a substitute for examining the underlying transaction. Resolve differences and retain the reconciliation and follow-up trail.
8. Separate estimation, approval and posting
Use a standardized accrual template that captures the supplier, legal entity, cost centre, account, service period, calculation basis, source evidence, preparer and reviewer. Require independent review for material or judgmental accruals. The reviewer should challenge the period attribution, estimate, duplicate risk and general-ledger coding—not merely approve the total.
Maintain a central accrual register and match new invoices against prior accruals before posting. This prevents the same cost from being recorded once as an accrual and again as an invoice expense.
9. Test both sides of the cutoff date
Test a sample of receipts and service completions immediately before and after period-end. Trace pre-close activity into the ledger and inspect post-close activity to confirm it has not been pulled into the wrong period. Pay particular attention to manual journals, backdated documents, unusual posting dates and transactions entered after the close was locked.
For significant exceptions, assess whether the issue is isolated or indicates a wider control failure—for example, delayed receiving confirmations, weak invoice workflow monitoring or unauthorized period reopening.
10. Control ERP data, posting periods and journal reversals
In SAP S/4HANA or another ERP, use purchase-order history, goods-receipt dates, service-entry approvals, invoice workflow status, posting dates and open-receipt reports as separate evidence points. Reconcile extracts to the AP subledger and general ledger. Preserve the report variant, filters and extraction timestamp.
Restrict period reopening and backdated postings to authorized users. Review manual accrual journals, changes to posting dates and late entries. Configure reversals consistently, but do not assume an automatic reversal proves that the original accrual was correct or that the subsequent invoice was matched properly.
How the accounting frameworks affect the review
The operational search is similar across jurisdictions, but the recognition, measurement, presentation and subsequent-event requirements must follow the entity’s reporting framework.
- US GAAP: Apply the relevant FASB Accounting Standards Codification requirements to the underlying liability and expense. Evaluate later information under the applicable subsequent-events guidance, including ASC 855 where relevant. The FASB identifies its Codification as the authoritative source of nongovernmental US GAAP; an Accounting Standards Update communicates amendments but is not itself the authoritative standard.
- IFRS: IAS 1 sets out the accrual-basis presentation framework (except for cash-flow information). Under IAS 10, later events that provide evidence of conditions existing at the reporting date are adjusting events; events indicative of conditions arising afterward are generally non-adjusting, with disclosure required when material.
- Canadian ASPE: Private enterprises should apply the relevant Part II requirements of the CPA Canada Handbook, including its subsequent-events guidance. Do not copy IFRS or US GAAP conclusions or disclosure wording without checking the applicable ASPE requirements and the entity’s accounting policies.
For audit readiness, PCAOB AS 1105 explains that company-produced information used as audit evidence should be evaluated for accuracy, completeness and sufficient detail, including consideration of relevant IT and application controls. AS 2301 describes how auditors design responses to assessed risks. These are auditor standards, not a substitute for management’s own control design, but they illustrate why a reproducible population and well-supported review matter.
A practical example
Assume a Canadian subsidiary receives maintenance services throughout December. The supplier’s invoice for $48,000 arrives on January 14. The operations manager confirms that the work was completed by December 31, and the contract supports the amount. Finance should evaluate and record the December liability under the subsidiary’s applicable framework, even though the invoice and payment occur in January.
Now assume a separate $12,000 invoice relates to work scheduled and performed on January 5. A December purchase order alone does not make that January service a December expense. The controller should document the period attribution and retain the evidence supporting the decision.
Month-end unrecorded-liabilities checklist
- Confirm close deadlines and obtain business-unit certifications.
- Extract subsequent payments across all material payment channels.
- Review unbilled receipts, service entries, blocked invoices and open purchase orders.
- Obtain targeted confirmations from high-spend budget owners.
- Reconcile selected vendor statements and investigate missing invoices or credits.
- Support estimates with contracts, usage, milestones or other reliable evidence.
- Check for duplicate accruals and match subsequent invoices to prior-period estimates.
- Test cutoff on both sides of the reporting date.
- Reconcile reports to the subledger and general ledger; retain parameters and evidence.
- Obtain independent review and track unresolved exceptions to closure.
Conclusion
A strong unrecorded-liabilities process is more than a post-close payment scan. It connects AP data with purchasing, receiving, operations and contract evidence; tests the period in which obligations arose; and produces a review trail that can be repeated every month. Controllers who make the process risk-based, data-driven and clearly owned can improve expense completeness, working-capital accuracy and audit readiness without turning every close into a manual invoice hunt.
Informational only: This article provides general controllership guidance, not accounting, legal or audit advice. Apply the current authoritative requirements for the entity’s reporting framework and consult qualified advisers for material or unusual arrangements.
