Finance Index
What is the search for unrecorded liabilities, and how does AP prepare for it?
Reference guide to unrecorded liabilities, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
An unrecorded liability is an obligation that existed at period-end but wasn't in the books - typically an invoice received late, lost in someone's inbox, or never accrued. The "search for unrecorded liabilities" is the auditor's completeness test: they examine payments and invoices processed after year-end and check whether each belonged in the audited period. AP's preparation is making sure the answer is consistently "it was recorded or accrued."
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| The search for unrecorded liabilities | An unrecorded liability is an obligation that existed at period-end but wasn't in the books - typically an invoice received late, lost in someone's inbox, or never accrued. | Keeps close, reporting, and system records aligned. |
| Audit evidence | The subsequent disbursements listing (payments made after period-end, usually through fieldwork), the post-close invoice register with service/receipt dates, the year-end accrual schedule, the open PO and received-not-invoiced reports, and the AP aging. | Keeps evidence clear and reduces control risk. |
| Run a self-test | Replicate their procedure in the first weeks of the new year: pull invoices and payments processed after close, flag anything with a prior-period service or receipt date, and check each against the accrual. | Keeps evidence clear and reduces control risk. |
| How bad is an unrecorded | Severity scales with size: immaterial items are passed adjustments; material ones become booked adjustments and a likely control deficiency comment; pervasive ones can escalate to significant deficiency or worse. | Keeps evidence clear and reduces control risk. |
| Approval path | Centralize intake: one published submission channel per entity, automated email capture that records arrival instantly, a forward-don't-process rule for employees, and vendor onboarding that locks in the right address. | Reduces payment errors, timing issues, and reconciliation cleanup. |
What will auditors ask AP to provide for the search?
The subsequent disbursements listing (payments made after period-end, usually through fieldwork), the post-close invoice register with service/receipt dates, the year-end accrual schedule, the open PO and received-not-invoiced reports, and the AP aging. They'll sample payments and trace each back: if the goods or services predate year-end, they expect to find it in AP or the accrual.
How do I run a self-test for unrecorded payables before the auditors do?
Replicate their procedure in the first weeks of the new year: pull invoices and payments processed after close, flag anything with a prior-period service or receipt date, and check each against the accrual. Add vendor statement reconciliations for your top 20 vendors and a received-not-invoiced review. Anything you find, you fix with a late accrual - found by you it's housekeeping, found by them it's a finding.
How bad is an unrecorded liability finding, and how do we respond?
Severity scales with size: immaterial items are passed adjustments; material ones become booked adjustments and a likely control deficiency comment; pervasive ones can escalate to significant deficiency or worse. Respond by booking the correction, doing a root-cause review (where did the invoices hide?), and showing process changes - auditors judge the response as much as the miss.
Invoices hiding in approver inboxes and department drawers never reach AP until past due - how do companies achieve invoice completeness?
Centralize intake: one published submission channel per entity, automated email capture that records arrival instantly, a forward-don't-process rule for employees, and vendor onboarding that locks in the right address. Completeness is an intake architecture outcome, not an audit-season effort.
What evidence supports the completeness assertion for accounts payable?
A controlled intake process (every invoice recorded on arrival), the accrual methodology and schedule, vendor statement reconciliations, the received-not-invoiced review, and a clean history on the auditor's subsequent disbursements test. Completeness is proven by process plus testing - there's no single report that demonstrates a negative.
How should we use vendor statements to find unrecorded liabilities?
Reconcile statements from your largest and most active vendors at period-end: any invoice on their statement missing from your ledger is a candidate unrecorded liability. Statements are the only completeness source that comes from outside your own systems - that independence is why auditors like them.
How do we use open PO and receiving reports to detect liabilities with no invoice recorded?
The received-not-invoiced report is a liability detector by construction: goods arrived, no invoice - accrue it. Review open POs past their expected delivery date too; some represent received goods where receiving entry was skipped, which is a liability hiding one layer deeper.
We restated because of material unrecorded liabilities - what process changes do boards and auditors expect?
Structural fixes, not vigilance pledges: centralized automated intake, a documented accrual methodology with system-backed inputs, vendor statement reconciliation as a standing control, sub-certification from budget owners on known unbilled obligations, and quarterly self-testing. Expect a remediation timeline with named owners and evidence of operation.
Cutoff testing vs search for unrecorded liabilities - how do the two procedures differ?
Cutoff testing samples transactions recorded near period-end and verifies they're in the right period (both directions). The unrecorded liabilities search works from post-period payments and invoices backward, hunting specifically for liabilities that should have been recorded. AP provides period-end registers for the first and subsequent activity listings for the second.
What intake controls guarantee every invoice enters the system the day it arrives?
A dedicated system-owned intake address (not a person's inbox), automatic record creation with timestamp on arrival, no-paper-processing policy with scanning routed to the same queue, vendor onboarding that sets the channel, and a monthly report of invoices arriving via side doors so you can shut them. "Guarantee" is strong - but recorded-on-arrival architecture gets you close enough that the residual risk is auditable.
Stampli perspective
Completeness starts at intake: Stampli's centralized capture means invoices create a recorded, timestamped entry the day they arrive - through any channel - instead of accumulating in inboxes and drawers. Real-time visibility into everything captured but not yet posted gives the accrual its in-flight population, and the immutable audit trail documents receipt dates when auditors trace subsequent payments back to the period they belong to.