Accounts Payable Completeness: Search for Unrecorded Liabilities

Answer B. These procedures are classic tests for identifying liabilities incurred before the balance‑sheet date that were not recorded, i.e., understatement of payables. Reconciling vendor statements, testing transactions just before and after year‑end, scanning subsequent disbursements, and confirming vendor balances are aimed at detecting unrecorded liabilities, so completeness is the primary assertion. They may provide secondary evidence about existence or cutoff, but the main objective is detecting omissions.

Why not A: This option tempts because confirmations and reconciliations can support that recorded payables actually exist. However, the described procedures emphasize finding liabilities that were omitted or recorded in the wrong period, so their primary focus is detecting understatement (completeness), not merely proving recorded balances exist.

Why not C: Reviewing invoices and purchase orders relates to amounts, so a candidate might think valuation is tested. In practice, valuation testing focuses on price accuracy, recalculation, and allocation; the listed procedures are directed at discovering missing liabilities rather than primarily verifying numeric accuracy or classification.

Why not D: Examining transactions around year‑end is a common cutoff test, which makes this answer attractive. But the overall set of procedures, vendor statement reconciliation, scanning subsequent disbursements, and confirmations, are intended to detect payables that should have been recorded at the balance‑sheet date but were omitted, so completeness (omission/understatement) is the primary assertion; cutoff is narrower (timing) and therefore secondary here.

Answer B. Examining subsequent cash disbursements and tracing them to year-end receiving reports and vendor invoices helps identify liabilities that existed at the balance-sheet date but were not recorded until after year-end. Subsequent payments provide documentary evidence that an obligation existed at year-end, so this procedure directly tests the completeness assertion. It is stronger than inquiry alone because it relies on third-party and source documents.

Why not A: Confirmations to large recorded vendors primarily test the existence and accuracy of recorded payables. Focusing only on large recorded balances is less effective for finding liabilities that were omitted entirely from the client's listing and therefore does not directly address completeness.

Why not C: Inspecting documents for recorded vouchers provides evidence about the existence and accuracy of items on the ledger, but it does not search for liabilities that were omitted from the subsidiary ledger. Thus it is not the best procedure when the primary concern is completeness.

Why not D: Recalculation verifies the arithmetic accuracy of the listing but says nothing about whether all liabilities were included. A correctly totaled listing can still omit payables, so this procedure does not address completeness.

Answer B. The primary assertion is completeness of liabilities at year-end where invoicing lags are common. Examining subsequent cash disbursements and tracing those payments, receiving reports, and late vendor invoices back to the year-end payable and accrual listings directly identifies obligations for goods received before 12/31/20X5 that were not recorded. This procedure most directly addresses the risk created by late invoices and weak manual accrual review.

Why not A: Confirmations are externally sourced and can detect undisclosed balances, but they are less direct here because many suppliers invoice late and statements are unavailable; searching subsequent disbursements tied to receiving evidence more reliably uncovers liabilities omitted at year-end.

Why not C: Vendor statements can help detect missing payables, but statements are unavailable for many key suppliers in this scenario and, even when available, may not reflect goods received before year-end if invoicing or statement preparation is delayed. Therefore this is less sufficient than tracing subsequent payments and receiving reports.

Why not D: Open purchase orders document authorization or commitments but do not prove receipt; goods may not have been received by year-end. For completeness of recorded liabilities, evidence of receipt and subsequent payment or invoicing is more relevant.

Answer B. When the auditor is concerned about understatement of accounts payable, procedures that look for unrecorded liabilities are required. Reviewing cash disbursements after year-end and tracing those payments to receiving reports and vendor invoices can reveal payments for goods or services received before year-end that were not recorded. This directly tests the completeness assertion for payables.

Why not A: Confirmations to customers address accounts receivable (amounts customers owe the client), not the client's obligations to vendors, so they do not provide direct evidence about unrecorded accounts payable.

Why not C: Observing inventory provides evidence about existence, condition, and count accuracy; although inventory and purchases relate to payables, observation does not directly identify vendor obligations omitted from the accounts payable records.

Why not D: Recalculating depreciation tests valuation and accuracy of asset-related expense, which is unrelated to the completeness of accounts payable and would not help uncover unrecorded vendor liabilities.

Answer A. The primary risk identified is completeness (understatement) of accounts payable because goods were received before year‑end but recorded only when invoices arrived later. A search for unrecorded liabilities using receiving reports, related vendor invoices, and subsequent cash disbursements directly targets that completeness risk and provides strong, corroborating evidence (especially subsequent payments that are external and traceable). This substantive procedure is more effective and timely than relying first on control testing or indirect analytics when specific unrecorded items are suspected.

Why not B: Confirmations can verify vendor balances but are less effective for detecting liabilities that were not recorded because no invoice was issued or because shipments near year‑end may not appear on a vendor's year‑end statement. Confirmations also may have low response rates and do not directly tie to receiving reports or subsequent payments the way a targeted search does.

Why not C: Testing controls may be useful if the auditor plans to rely on them, but control testing does not itself identify specific liabilities that were omitted from the year‑end accounts payable balance. Given the concrete receiving‑report/invoice timing issue, substantive procedures that search for unrecorded liabilities are required to detect omitted payables.

Why not D: Analytical procedures can indicate unusual trends but provide indirect evidence and cannot locate or quantify specific unrecorded liabilities. With receiving reports showing goods received before year‑end, direct substantive procedures (search and review of subsequent disbursements) are necessary to obtain sufficient appropriate evidence about completeness.