Search for Unrecorded Liabilities: A Practical Year-End Payables Completeness Audit Guide

A search for unrecorded liabilities is one of the most important year-end procedures for trade payables and accrued expenses because the principal risk is often completeness: an obligation may belong to the reporting period even though it never reached the closing payable ledger. Vouching only items already recorded in the ledger can therefore miss the very misstatement the procedure is designed to find.

ICAI's Guidance Note on Audit of Liabilities specifically identifies cut-off procedures, documentary evidence, year-end transactions and subsequent events as relevant areas when examining trade creditors and other current liabilities. ICAI's current standards repository also lists SA 500, Audit Evidence, which requires audit procedures designed to obtain sufficient appropriate audit evidence and requires the auditor to consider the relevance and reliability of information used as evidence. The ICAI Engagement and Quality Control Standards repository is the current index for the applicable Standards on Auditing.

What the search is trying to detect

The procedure is not simply a check for unpaid supplier invoices. It is designed to identify obligations that should have been recognised at year-end but were omitted, recorded in the wrong period or recorded for the wrong amount. Depending on the entity, the risk may arise from goods received before year-end with invoices posted later, services completed but not accrued, supplier balances omitted from the payable listing, purchase cut-off errors, or liabilities deliberately deferred to improve reported profit or working capital.

The direction of testing matters. For an existence test, the auditor may start with a recorded balance and inspect supporting evidence. For a completeness test, the more useful starting population is often outside the closing ledger: post-year-end payments, supplier statements, invoices received after year-end, unmatched goods-received records, open purchase commitments, recurring expense contracts or other evidence that could reveal a missing obligation.

A practical six-step audit approach

1. Understand how liabilities enter the books. Map the purchase-to-pay process: purchase order, receipt of goods or services, invoice capture, approval, three-way matching where applicable, posting and payment. Identify where a valid obligation can exist before an invoice is recorded.
2. Identify the relevant source populations. Obtain post-year-end bank or payment listings, invoices received after the reporting date, supplier statements, unmatched receipt records, open purchase orders and schedules of accrued expenses where relevant to the entity.
3. Assess the reliability of those reports. SA 500 requires the auditor to consider relevance and reliability. If an internally generated report is being used, consider whether its accuracy and completeness need to be tested and whether it is sufficiently precise and detailed for the audit purpose.
4. Select items based on the risk. Do not automatically choose an arbitrary number of days or only the largest ledger balances. Consider materiality, assessed risk, payment patterns, late invoice processing, unusual vendors, manual journals and the period in which year-end obligations are most likely to surface.
5. Trace each selected item back to when the obligation arose. Inspect invoices, contracts, purchase orders, goods-received notes, service completion evidence, correspondence and other relevant records. The question is whether the underlying goods or services and the related obligation belong to the reporting period under the applicable financial reporting framework.
6. Resolve exceptions and conclude on the population. For items that should have been accrued or recorded, quantify the misstatement, understand why it arose, consider whether the exception indicates a broader process weakness or possible bias, and determine whether additional procedures are needed.

Procedure 1: test subsequent payments

Start with cash or bank disbursements made after year-end and work backwards to the supporting obligation. A payment in April does not automatically prove that a liability existed on 31 March. The auditor should establish what was purchased, when goods were received or services were performed, the contractual terms, and when the entity became obligated.

This is a powerful completeness procedure because the source population is not limited to liabilities already recorded at year-end. It can reveal an invoice posted and paid after close even though the underlying transaction belonged to the previous period.

Procedure 2: reconcile supplier statements

Supplier statements can identify invoices, credit notes or balances that do not appear in the client's ledger. Where statements are available, reconcile material or risk-selected suppliers to the accounts payable records and investigate differences. SA 500 notes that consistent evidence from different sources can provide more assurance than evidence considered individually, and information from sources independent of the entity can strengthen internally generated evidence.

A difference is not automatically an unrecorded liability. It may reflect timing, disputed items, payments in transit, supplier errors or credit notes. The audit conclusion comes from resolving the reconciling item, not simply recording that a difference exists.

Procedure 3: inspect invoices received after year-end

Review invoices entered or received after the reporting date and inspect the underlying receipt or service evidence. Invoice date alone is often not enough. Goods may have been received before year-end with the invoice issued later, or an invoice may be dated before year-end for services that were not yet performed. Focus on the economic event and the applicable recognition criteria.

Procedure 4: examine unmatched receipts and accrued expenses

For businesses with inventory or formal procurement systems, unmatched goods-received records can highlight goods received before year-end for which the invoice has not yet been posted. For service-heavy businesses, the equivalent risk may sit in accrued expenses: legal fees, audit fees, professional services, utilities, freight, incentives, rent or other recurring costs for which the invoice cycle does not align neatly with the reporting date.

The audit programme should match the business model. A manufacturing entity may need strong goods-receipt cut-off work; a consulting or technology entity may need more emphasis on service completion evidence and recurring accruals.

Worked example: invoice posted in April

Assume a company pays ₹9 lakh on 12 April against an invoice entered on 5 April. The search for unrecorded liabilities should not stop at the posting date. The auditor inspects the engagement letter and completion evidence and finds that the professional service was completed on 28 March. The next question is whether, under the applicable accounting framework and the facts of the arrangement, an obligation existed at 31 March and should have been accrued. If the same evidence instead shows that the service was performed only on 2 April, the April payment by itself would not establish a 31 March liability.

The example shows why the procedure is evidence-driven: payment date is a lead, not the accounting conclusion.

How to choose the look-forward period

There is no universal number of post-year-end days that makes the procedure sufficient in every audit. The period should be designed around the entity's payment cycle, invoice-processing lag, nature of liabilities, assessed risk and materiality. If suppliers are normally paid 60 days after receipt, a very short look-forward window may miss relevant obligations. If the entity pays most vendors within a week, the same window may produce much stronger coverage.

Working-paper checklist

• State the completeness risk and the financial statement areas covered.
• Document each source population used and how its completeness and accuracy were considered.
• Record the selection method, materiality or risk rationale and the look-forward period.
• For each item, retain the evidence establishing when goods or services were received and when the obligation arose.
• Reconcile supplier-statement differences and document their resolution.
• Quantify identified unrecorded or late-recorded liabilities and cross-reference proposed adjustments.
• Consider whether exceptions indicate a broader cut-off problem, control deficiency or need to extend testing.
• Conclude explicitly on whether sufficient appropriate evidence was obtained for the relevant completeness assertion.

Common mistakes

• Sampling only from the closing trade-payables ledger when the objective is to find items missing from that ledger.
• Treating every post-year-end payment as a prior-period liability without establishing when the underlying obligation arose.
• Using an internally generated post-year-end invoice or payment report without considering whether the report itself is complete and accurate.
• Choosing a fixed look-forward period without relating it to the entity's payment cycle and risk profile.
• Ignoring services and accruals because there is no goods-received note.
• Accepting management's explanation for supplier-statement differences without corroborating evidence.

Practical takeaway

A good search for unrecorded liabilities begins outside the year-end payable ledger. Use subsequent payments, supplier statements, post-close invoices, receipt records and accrual evidence to identify possible obligations, then trace each item to the underlying goods or services and determine when the liability arose. The strongest working paper makes the completeness objective, source populations, report reliability, selection logic, exceptions and final conclusion visible rather than treating the exercise as a mechanical after-date payment check.