Search for Unrecorded Liabilities: Procedures, Period and Documentation

Most audit procedures test that what is recorded is real. The search for unrecorded liabilities tests the opposite: that what should be recorded is there. The risk is understatement: invoices sit in a drawer, services received in December are billed in February, or accruals are left out to make results look better.

This guide covers how to plan and perform the search for unrecorded liabilities in a nonissuer audit under GAAS, including the search period, thresholds, sources and documentation.

What the search addresses

The primary assertion is completeness of accounts payable, accrued liabilities and the related expenses or assets. It also supports cutoff of purchases and expenses.

Testing the recorded accounts payable listing cannot prove completeness on its own, because an omitted invoice is not on the listing. The search therefore starts from sources outside the recorded balance: cash paid after year end, invoices received after year end and documents that show obligations existed at year end.

In risk assessment under AU-C 315, completeness of liabilities is often assessed as higher risk when the entity has incentives to report better results, such as debt covenants, bonuses based on income, or a pending sale.

The core procedure: subsequent disbursements

The most common procedure is to examine cash disbursements made after year end and determine whether each relates to a liability that existed at the balance sheet date.

Steps

1. Obtain the cash disbursements journal or check register from the day after year end to the end of the search period.
2. Tie the listing to bank statements to show it is complete. A disbursements report that omits wires or ACH payments would leave a gap.
3. Select disbursements above a threshold, plus any below it that look unusual.
4. For each selection, obtain the vendor invoice and supporting documents (receiving report, contract, statement of services).
5. Determine the date the goods or services were received.
6. If received on or before year end, confirm the amount was included in accounts payable or accrued liabilities.
7. If received after year end, confirm it was not recorded as a year-end liability.
8. Quantify any omission and carry it to the summary of misstatements.

The key date is when the obligation arose, not the invoice date or the payment date. An invoice dated January 10 for consulting performed in December is a December liability.

Choosing the threshold

The threshold should be low enough that the untested remainder could not plausibly add up to a material omission. A common approach is to tie it to performance materiality under AU-C 320, setting it at a fraction of performance materiality so that several untested items could not combine into a material error. Document the threshold and the reasoning. Lower it if prior years had unrecorded liabilities, controls over purchasing are weak, or the entity has an incentive to understate expenses.

Search period: how long after year end

The search should run as close as practical to the report date. Liabilities surface over time: the longer you look, the more invoices for pre-year-end activity have been received or paid.

Tie the search to subsequent events work under AU-C 560, which covers the period through the report date. Many firms extend the subsequent disbursement listing up to the end of fieldwork and then perform inquiry and a brief review for the remaining days before the report is dated.

Other sources of unrecorded liabilities

Subsequent disbursements will not find a liability that has not been paid yet. Use other sources as well:

• Unpaid invoices received after year end: review the open invoice file and the AP aging at the date of fieldwork for invoices dated or relating to the prior year.
• Receiving reports before year end without a matching invoice: goods received but not invoiced (often called "received not invoiced" or GRNI).
• Open purchase orders and contracts: commitments with performance before year end, such as construction or software implementation.
• Vendor statements: compare statements from major vendors with the AP subledger; a statement showing invoices the entity has not recorded is direct evidence.
• Board and committee minutes: approvals of settlements, bonuses or purchases.
• Legal letters and legal expense: unbilled legal fees and possible claims, which also feed the litigation and contingencies work.
• Payroll: accrued wages for the last pay period, bonuses, commissions, paid time off and payroll taxes.
• Taxes: sales and use tax, property tax and income tax payable.
• Recurring expenses: utilities, rent, insurance and professional fees where the December bill arrives in January.
• Debt: accrued interest, and any draws on a credit line after year end that relate to year-end obligations.

An analytical review of expense accounts helps too. If a monthly recurring expense shows eleven months of activity, the twelfth is probably unrecorded.

Worked example (illustrative figures)

Year end December 31. Performance materiality $120,000. Threshold for subsequent disbursements: $15,000. Search period January 1 to March 10 (end of fieldwork).

Unrecorded liabilities identified: $35,700. Both are factual misstatements to post under AU-C 450. The legal invoice should also be reviewed with the legal letter response, because unbilled legal work can point to a claim that needs evaluation for accrual or disclosure.

Projecting results and responding to exceptions

The search is usually a targeted test of items above a threshold, not a statistical sample, so known errors are not projected in the way a sample result would be. Still, exceptions say something about the untested remainder. If several unrecorded items are found:

• consider lowering the threshold and extending the search
• ask management to perform its own review of post-year-end invoices and record any further omissions, then test their work
• assess whether purchasing and accrual controls have a deficiency to communicate under AU-C 265

If you do use sampling for part of the population, design and evaluate it under AU-C 530, including projecting the misstatement to that population.

Documentation

AU-C 230 expects the workpaper to show:

• the objective and assertions addressed
• the search period and why it ends where it does
• the source listings and how their completeness was checked (tie to bank statements)
• the threshold and its rationale
• each item tested with check number, date, vendor, amount and the date the obligation arose
• the other sources reviewed (unpaid invoices, receiving, contracts, minutes, legal)
• results, quantified exceptions and whether management recorded them
• a conclusion on the completeness of liabilities

Common problems

• Search ends at an arbitrary date well before the report date, with no update.
• Listing not proven complete, often because wires and ACH payments sit in a separate report.
• Invoice date used instead of service date, so December services billed in January pass as correct.
• Threshold too high relative to performance materiality, leaving a large untested remainder.
• Only paid items examined, ignoring unpaid invoices and goods received not invoiced.
• Exceptions treated as isolated with no consideration of extending the search.

Frequently asked questions

What is the search for unrecorded liabilities?

It is a set of substantive procedures, mainly examining payments and invoices after year end, to identify obligations that existed at the balance sheet date but were not recorded. It addresses the completeness of liabilities and related expenses.

How far after year end should the search for unrecorded liabilities go?

As close to the report date as practical. Many firms test subsequent disbursements through the end of fieldwork and then update with inquiry and a brief review of later payments before the report is dated.

What threshold should I use for subsequent disbursements?

There is no required amount. Firms commonly set it as a fraction of performance materiality so that untested items could not combine into a material omission, and lower it where risk or prior errors justify.

Why isn't testing the accounts payable listing enough?

An omitted liability does not appear on the recorded listing, so testing it only addresses existence and accuracy. Completeness needs evidence from outside the listing, such as subsequent payments, unpaid invoices and receiving records.

Are accrued expenses part of the search for unrecorded liabilities?

Yes. Payroll, bonuses, interest, taxes, professional fees and recurring services are frequent sources of unrecorded liabilities and should be considered alongside trade payables.

Sources

• AICPA, AU-C Section 500, Audit Evidence; AU-C Section 330, Performing Audit Procedures in Response to Assessed Risks
• AICPA, AU-C Section 560, Subsequent Events and Subsequently Discovered Facts
• AICPA, AU-C Section 315 (as revised by SAS No. 145); AU-C Section 320; AU-C Section 450; AU-C Section 265; AU-C Section 530; AU-C Section 230
• AICPA, AU-C Section 501, Audit Evidence: Specific Considerations for Selected Items (litigation, claims and assessments)

CORAA prepares ready-to-review audit files for US CPA firms from QuickBooks books; you review and sign. See /us.

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error