A search for unrecorded liabilities tests whether the client left year-end obligations off its books. You read payments that left the bank in the weeks after year end, pull the invoice behind each one above a chosen threshold, and ask whether the goods or services arrived before year end. If they did, a liability belonged on the books.
What does a search for unrecorded liabilities test?
A search for unrecorded liabilities tests the completeness of accounts payable and accrued expenses. Completeness asks whether every obligation that existed at year end is in the accounts. The payables listing cannot answer that, because a bill the client forgot to record is not on the listing at all.
That is why the search starts outside the payables ledger. Testing items on the listing, such as confirming vendor balances or vouching invoices, is good evidence that recorded payables exist and are stated at the right amount. It says nothing about the invoice sitting in a manager's inbox on December 31, or the contractor who has not billed yet.
Understated liabilities are the direction of misstatement that management has a motive to create. Leaving costs out raises profit and improves the current ratio. A client close to a loan covenant, a bonus target or a sale has a reason to let some invoices slip into next year. The search is the auditor's main tool against that, and it deserves real effort even when payables look small.
The search also catches honest errors. Year-end closes are rushed, and an invoice received on January 4 for December work is easy to post to January. Either way, the evidence is the same: something was paid later for something received earlier.
Subsequent disbursements in the bank records as the search population
Subsequent disbursements are the payments that leave the client's bank accounts after year end, and they are the best population for the search because almost every real liability is paid eventually. The bank statement is also produced by a third party, so a payment cannot be hidden from it the way an invoice can be hidden from the ledger.
Build the population from the bank, not from the check register. The register is the client's record and may omit items, such as wire payments or debits a vendor pulled by ACH. The statements for every operating account, read line by line, give the full list of money that left. Include payments from credit cards, payroll accounts and any account that pays vendors.
For each outgoing line you need the date, the amount, the payee and a reference. Electronic payments often carry only a short description, so plan to match them to the payment batch or remittance advice the client used. Checks carry a number, which lets you pull the check image and the invoice it paid.
Receipts in the same period are a different test. Cash collected after year end supports the existence of receivables, not the completeness of payables, and is covered in subsequent receipts testing for receivables. Keep the two populations apart in the file, since they prove different things.
Setting the threshold and the window for an unrecorded liabilities search
The threshold is the payment size above which you examine every disbursement, and the window is how many weeks after year end you read. A common approach sets the threshold as a fraction of performance materiality and reads until the end of fieldwork or the report date. Both choices are judgment calls you must write down.
Choosing the dollar threshold
Start from the amount that would matter. If an individual payment below the threshold could not, alone or with others like it, change a reader's view of the payables, you can leave it out of the detail test. A threshold that is too high leaves a dozen mid-sized invoices untested, and together they can add up to more than anyone intended.
Look at the shape of the client's payments before you fix the number. A business that pays a few large suppliers can use a higher threshold, since most of the money passes through a handful of lines. A business that pays hundreds of small vendors needs a lower one, or a sample from below the threshold as well. The number in the example below is invented and is not a rule.
Choosing the window
The window should run long enough for year-end invoices to be paid. Most vendors bill within a month and are paid within one or two more, so a window of eight to ten weeks is often used. Read the client's payment terms: a company that pays on 60-day terms needs a longer window than one that pays on receipt.
If the report date arrives before the window closes, extend the work with other evidence, such as unpaid invoices on file and the open purchase orders, and say so in the workpaper.
Testing each subsequent disbursement against year-end payables
Testing a subsequent disbursement means finding the invoice or document behind the payment, reading the date the goods or services were received, and comparing that date to year end. If the service date is before year end, the amount belongs in the old year's liabilities. Then check whether it was recorded there.
The table below is a worked example for a client with a December 31 year end and a $5,000 threshold. Every vendor, date and amount is invented for illustration.
| Paid | Payee | Amount | Service or delivery date | In year-end AP or accruals? | Conclusion |
|---|---|---|---|---|---|
| Jan 6 | Freight carrier | 7,480.00 | Dec 18 to Dec 29 | Yes, AP listing | Recorded correctly |
| Jan 12 | Legal firm | 12,900.00 | November and December fees | No | Unrecorded liability, propose entry |
| Jan 15 | Software vendor | 24,000.00 | Annual licence from Jan 1 | No | New-year cost, no entry |
| Jan 22 | Equipment supplier | 31,250.00 | Delivered Dec 30 | No | Unrecorded liability; also check fixed assets |
| Feb 3 | Property owner | 9,600.00 | February rent | No | New-year cost, no entry |
| Feb 9 | Consultant | 5,450.00 | Split: half December, half January | Partly | Accrual short by 2,725.00 |
Read the invoice, not just the invoice date. An invoice dated January 10 can bill December work, and an invoice dated December 28 can bill a service that starts in March. The legal fees row is a typical find: professional firms often bill a month or more in arrears.
Some payments need more than an invoice. A payment to an owner, a family member or a company the owner controls should be read for what it really settles. Those flows have their own risks, described in related party transactions in bank statements.
Which unrecorded liabilities never show up as a payment?
Some unrecorded liabilities never show up as a subsequent payment because they are still unpaid when the window closes, are settled without cash, or were paid before year end and later reversed. Bank records miss them. You find them by reading other sources: unpaid invoices, vendor statements, contracts, minutes and the legal letter.
Sources to read beyond the bank
Unpaid invoices on file at the end of fieldwork are the first source. Ask for the stack that has not yet been entered, and read the service dates. Vendor statements from the largest suppliers show what the vendor thinks it is owed, which may include invoices the client never received.
Contracts and board minutes reveal obligations such as commitments, guarantees and settlements. Payroll records show wages earned in December but paid in January, along with the related taxes and benefits. Credit card statements show charges made in late December that post in January.
Liabilities that net against receipts
A refund owed to a customer, a rebate due to a distributor, or a deposit held for a customer may be settled by netting against a later receipt. No disbursement line appears. Read credit memos issued after year end for the same reason you read disbursements.
Mistake: ending the unrecorded liabilities search when fieldwork ends
A common mistake in the search for unrecorded liabilities is letting the window end whenever the field team leaves, rather than on a date set in advance. The search then covers three weeks for one client and ten for another, and nobody can say whether the population was complete. Fix the window in the plan and record any change.
The same mistake shows up in the population. A team that reads only the main operating account, or only checks, will miss the wire to a supplier from a second account and the ACH debit a vendor pulled directly. List every account the client pays from, and tie the list to the cash lead schedule before you start.
Watch for filtering by payee. Leaving out payroll processors, tax authorities and card issuers because "they are not vendors" removes some of the largest year-end obligations: payroll taxes, sales taxes and card balances. Include them in the population and decide on each one.
The window also has a back end. A large payment made in the last week of December, reversed or refunded in January, can mean a liability was settled on paper but not in fact. If you see one, extend the review to those reversals.
Documenting unrecorded liabilities findings for the reviewer
The workpaper for a search for unrecorded liabilities should state the population, the window, the threshold and the reason for each, then list every disbursement tested with its support and conclusion. Unrecorded items found go to the summary of adjustments, with the total compared to performance materiality and a note on whether the pattern suggests more.
A reviewer wants to see four things. First, that the population is complete: a tie of the disbursements read to the bank statements for the window. Second, that each item above the threshold was tested, with a reference to the invoice. Third, that the conclusions follow from the dates. Fourth, what was done about what was found.
When a search turns up several unrecorded items, treat that as information about the client's close process, not just as entries to book. It may mean a control over invoice receipt is not working. The same exception layout used in a reconciliation report sample for workpapers works here: each item, its evidence and its status, in one list.
If a finding looks deliberate, such as invoices held back in a pattern or a vendor paid from an account nobody mentioned, the work changes from an audit test to an inquiry. A forensic audit checklist for bank records sets out what to secure and review next.
Reading eight weeks of statements line by line is slow. PreciseBankFlow extracts each statement line, confirms the statement foots and lists every disbursement, so the population you test is complete before you start pulling invoices.