Accounts Payable Ledger Template

In plain language: Records the legal name, address, contact details, and unique vendor ID for every creditor in the ledger.

Common mistake: Using a trade name instead of the vendor's registered legal entity name — this creates mismatches during tax reporting (1099 / T4A) and can delay vendor verification during audits.

In plain language: Captures each invoice number, invoice date, and a brief description of the goods or services billed.

Common mistake: Omitting the corresponding purchase order number. Without a PO reference, three-way matching is impossible and duplicate payment risk increases significantly.

In plain language: States the agreed payment terms for each invoice and the resulting due date by which payment must be remitted.

Common mistake: Recording the due date from the receipt date rather than the invoice date. Vendor contracts almost always calculate terms from the invoice date — using the wrong start date creates phantom extra days and late payment penalties.

In plain language: Records the gross invoice amount, any applicable taxes, and the currency in which payment is owed.

Common mistake: Not stating the currency for international vendors. USD and CAD amounts look identical in a ledger without a currency code, leading to foreign exchange errors and overpayments.

In plain language: Sorts each outstanding invoice into an aging bucket — current, 1–30, 31–60, 61–90, or 90+ days past due — to prioritize collections and flag overdue obligations.

Common mistake: Classifying invoices as current when they are within the payment window but likely to miss the due date given cash constraints. Aging should reflect actual payment risk, not just calendar math.

In plain language: Records whether each invoice is unpaid, partially paid, paid in full, disputed, or on hold — and logs the date and method of each payment made.

Common mistake: Marking an invoice 'paid' upon initiating a wire transfer rather than upon confirmed receipt by the vendor. Reversals and failed transfers leave phantom 'paid' entries that distort the running balance.

In plain language: Maintains a cumulative total of all unpaid amounts in the ledger, updated after each entry, with period subtotals for reconciliation against the general ledger.

Common mistake: Reconciling the AP ledger against the general ledger only at year-end. Monthly reconciliation catches posting errors and prevents a compounding discrepancy that is far harder to unwind after 12 months.

In plain language: Documents any invoice placed on hold pending resolution of a billing discrepancy, short-shipment, or quality dispute — including the reason and expected resolution date.

Common mistake: Leaving disputed invoices in the standard aging column without a hold notation. Disputed amounts inflate the 61–90 or 90+ aging buckets and trigger unnecessary escalation to vendors or auditors.

In plain language: Requires sign-off from an authorized officer confirming that all entries have been reviewed, payment approvals are documented, and the ledger is accurate as of the stated date.

Common mistake: Having the same person who enters invoices also approve payments. This single-person control violates segregation of duties and is a primary fraud risk vector identified in financial audits.

In plain language: Captures goods or services received but not yet invoiced, ensuring these obligations appear on the balance sheet even before a formal invoice arrives.

Common mistake: Omitting accruals from the AP ledger entirely and recording them only as a journal entry adjustment at period-end. This creates a gap between the operational ledger and the financial statements that confuses auditors and overstates available cash.

An accounts payable ledger is a formal financial record that lists every outstanding obligation a business owes to its vendors, suppliers, and creditors. It captures invoice numbers, amounts, due dates, payment terms, aging classifications, and payment status for each open liability. The ledger serves as the operational detail behind the accounts payable balance on the balance sheet and is the primary document reviewed during financial audits and lender due diligence.

An accounts payable ledger records money your business owes to others — vendor invoices, supplier bills, and trade credit. An accounts receivable ledger records money others owe to your business — customer invoices and outstanding billings. Both are subsidiary ledgers that reconcile to control accounts in the general ledger, but they sit on opposite sides of the balance sheet: AP is a liability, AR is an asset.

In small businesses, the bookkeeper or owner typically maintains the AP ledger. In mid-sized companies, an AP clerk handles data entry while a controller or CFO reviews and approves it. Regardless of company size, internal controls require that the person entering invoices is different from the person authorizing payments — combining both roles in one person is a primary fraud risk and a common audit finding.

Monthly reconciliation against the accounts payable control account in the general ledger is the standard for most businesses. High-volume AP departments reconcile weekly. Waiting until year-end is a common but costly mistake — undetected discrepancies compound over 12 months and can take days to untangle during audit fieldwork. A monthly close process catches errors when they are still easy to trace.

No statute explicitly mandates a document called an 'accounts payable ledger,' but tax authorities in the US (IRS), Canada (CRA), the UK (HMRC), and the EU (member-state revenue authorities) all require businesses to maintain accurate records of all liabilities and expenditures. An AP ledger is the standard mechanism for satisfying those record-keeping obligations. Inadequate AP records are one of the most common triggers for tax audit adjustments and financial restatements.

An AP aging schedule classifies outstanding invoices into time buckets — typically current, 1–30, 31–60, 61–90, and 90+ days past due — based on how long they have been unpaid. It matters for two reasons: operationally, it prioritizes which invoices to pay first to avoid late fees and protect vendor relationships; financially, a heavy 90+ bucket signals a cash flow problem that will appear on the balance sheet and raise red flags with lenders and auditors.

The AP ledger is a subsidiary ledger — a detailed breakdown of every individual transaction that rolls up into a single control account (Accounts Payable) in the general ledger. The closing balance in the AP ledger must match the AP control account balance exactly. When they don't match, the difference indicates a posting error, a missing entry, or a payment recorded in one place but not the other.

Three-way matching is an internal control process that verifies a vendor invoice against the original purchase order and the goods receipt record before authorizing payment. The AP ledger is the central document where the results of this matching are recorded — the PO number and receipt reference are captured alongside the invoice, confirming that all three documents align before the invoice moves to the payment queue.

Yes, a Word or spreadsheet-based AP ledger is entirely appropriate for small businesses processing fewer than 50–100 vendor invoices per month. It provides an audit trail, enforces consistent data capture, and satisfies tax authority record-keeping requirements without the cost of accounting software. As transaction volume grows beyond 100 invoices per month, migrating to dedicated accounting software (QuickBooks, Xero, or an ERP) becomes more efficient.