How accounts payable is usually set up in finance and ERP systems

Accounts payable usually runs as a subledger inside the ERP. Supplier invoices are captured, matched to purchase orders and receipts, approved, and paid in scheduled runs. Each step posts to the general ledger automatically, so the AP balance and the ledger control account should always agree.

Where the subledger sits

The AP module holds open items by supplier. It does not keep its own chart of accounts. Every invoice, credit note and payment carries a posting rule that sends a summarised or detailed entry to a liability control account in the general ledger. Direct manual journals to that control account are normally blocked. When they are allowed, reconciliation becomes painful at month-end.

Posting rules are configured once and rarely revisited. Many surprises come from here: a tax code mapped to the wrong account, or a supplier group defaulting to an expense line nobody remembers choosing.

Vendor master data

The supplier record is the anchor. It stores bank details, payment terms, tax identifiers, the default currency and whether the supplier is subject to year-end tax reporting. Purchase orders, invoices and payments all read from it.

Most organisations separate who can create or edit a supplier from who can enter invoices or release payments. Bank detail changes typically trigger a second approval and a call-back to a known contact. Before a payment file is released, it is checked against this master file so that money goes to the account on record and nowhere else.

Getting invoices in

Invoices arrive by email, supplier portal, electronic exchange or paper. Larger setups run a capture tool that reads the document and creates a draft entry. Electronic invoicing networks feed structured data straight in, which cuts keying errors but needs ongoing maintenance of supplier connections and message formats.

Whichever route is used, someone audits the key fields: supplier, invoice number, date, tax and total. Duplicate checks run on supplier and invoice number, and often on amount and date as well.

Matching and exceptions

PO-backed invoices are matched to the order and usually to the goods or service receipt. Tolerances decide how far price or quantity may differ before the invoice is blocked. Invoices without a purchase order follow a separate path, routed to a budget holder for coding and sign-off.

Blocked items land in an exception queue. Clearing it means chasing a missing receipt, querying a price with the buyer, or asking the supplier for a credit note. This queue is where most AP effort actually goes, and it is worth looking at closely before changing anything else.

Approval and the payment run

Approval workflows route by amount, cost centre or legal entity. Once an invoice is approved and due, it becomes eligible for the payment proposal. The system builds a list based on due dates and terms. A clerk reviews it and removes anything on hold. A separate person then authorises the release.

The ERP produces a bank file in the bank's required format. After the bank confirms, the payment clears the open items and posts cash. Returned or rejected payments come back as exceptions and reopen the invoice.

Public sector bodies often have an extra flow for payments between government entities, where settlement data is pulled from a central treasury system, recorded against the payable and confirmed as properly settled.

Accruals, taxes and the month-end

Goods received but not yet invoiced are accrued, usually from the receipt-not-invoiced report. These entries reverse automatically at the start of the next period. Manual accruals for services without a receipt are a common weak spot.

Sales tax or VAT is calculated on the invoice line from tax codes. Withholding tax, where it applies, is deducted at payment. Suppliers flagged for year-end reporting accumulate totals that feed information returns to the tax authority and to the payee.

At period close, AP is locked, the subledger is reconciled to the control account, and the period is opened for the next cycle.

Records, reporting and inquiries

Scanned images and approval history attach to the transaction and are kept under the retention policy. Standard reports cover aged payables, invoice status, payment detail and disbursement summaries for cash reconciliation. Supplier inquiries are handled through a shared mailbox, a ticketing tool or a self-service portal showing invoice and payment status.

Questions to ask the people who run it

What is documented and what happens on a busy Tuesday are often different. Useful things to ask:

• Which invoices do you key by hand even though a capture tool exists, and why?
• When an invoice blocks on price, who do you actually contact, and how long does it sit before anyone chases?
• Are there suppliers paid outside the normal run? Who decides that?
• How do bank detail changes really reach you, and has anyone ever skipped the call-back?
• What do you remove from the payment proposal before release, and is that rule written anywhere?
• Which accruals are estimates you work out in a spreadsheet?
• Do you ever post to the AP control account directly? Under what circumstances?
• What do suppliers ask about most often, and could they find the answer themselves?
• Where do you keep notes about awkward suppliers or recurring problems?

The answers usually reveal workarounds that grew up around a tolerance set too tight, a missing approval route or a report nobody trusts. Those are the places a redesign either succeeds or quietly fails.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.