Accounts payable process for enterprise finance controllers

What the enterprise AP process covers from bill to payment

An enterprise accounts payable process takes a supplier bill from receipt to payment through defined steps: registering the bill, matching it to an approved purchase and proof of delivery, approving it under delegated authority, scheduling payment, and recording the payment against the bill. The finance controller's job is to make sure each step has an owner and leaves evidence.

Controllers inherit AP problems from every department that buys things. Procurement raises purchase orders, operations receives goods, project managers accept services, and finance pays. AP is where those separate actions have to agree, so most of the design work is getting each department to record its part.

Duplicate bills, unverified receipts and other AP leaks

Money leaves an enterprise through AP in a handful of predictable ways. A supplier emails a bill and also posts a paper copy, and both get keyed. A bill is paid before anyone confirms the goods arrived. A supplier's bank details are changed on the strength of a single email. Supplier credit notes are filed and never applied.

None of these need fraud. They need only a busy team and a process that relies on memory. The controls in the next three sections target each one.

One cheap detective control is worth adding straight away. Ask your larger suppliers for a monthly statement and reconcile it to your payables listing for that supplier. Bills on their statement that are missing from your books reveal invoices stuck in inboxes; payments on your side that the supplier has not applied reveal misallocated or duplicated amounts. Unapplied supplier credit notes also tend to surface here.

Matching bills to purchase orders and goods received

For purchased goods, the standard check is a three-way match: the bill agrees to the purchase order on price and item, and to the goods received note on quantity. For services, the equivalent is a match to the purchase order plus a sign-off from the person who accepted the work.

Agree tolerances with procurement so small rounding differences do not stall payment, and send anything outside tolerance back to the buyer rather than leaving the AP clerk to resolve it. Bills without a purchase order should be exceptions limited to categories such as utilities or statutory payments, each with a named approver.

Register every bill on arrival, even if it cannot be approved yet. A bill sitting unregistered in someone's inbox is a liability the company cannot see, which distorts both cash planning and period-end accounts.

Controls for the supplier master file

The supplier master holds the bank account every payment goes to, so changes to it need tighter control than almost any other record.

• New suppliers are created only by a named finance role, with registration documents on file
• Bank detail changes require a written request on supplier letterhead and a call-back to a contact already on record
• A second person approves every bank detail change before it takes effect
• Duplicate checks run on company registration number and bank account, not only on supplier name
• Suppliers with no recent transactions are blocked until reactivated through the same approval
• The controller reviews a report of all master file changes every month

Accruals and cutoff when supplier bills arrive late

Suppliers do not invoice on your timetable. At period end there will be goods received and services delivered with no bill yet. Leave those costs out and the P&L understates expenses while the balance sheet understates liabilities.

Use received-not-billed reports from procurement and confirmations from department heads to build an accrual list, then reverse the accruals in the following period when the real bills arrive. The controller should review large accruals individually and ask budget owners to confirm anything that looks estimated rather than evidenced.

Payment runs need the same discipline. Fix a regular run date, pay approved bills by due date rather than by whoever shouts loudest, and have the payment file released by bank signatories who did not prepare it. A forecast of upcoming payables, built from approved bills and expected accruals, lets the controller warn treasury about large outflows before the run.

Keeping the AP trail in one system

An AP process with this many checks is hard to evidence when bills live in email and payments are tracked on a spreadsheet. For any payment, the controller should be able to pull the bill, its approval and the bank record without asking three people.

BukuCloud records bills and supplier payments against each other and produces the P&L and balance sheet from the same entries, so payables on the balance sheet tie back to individual bills. Your external accountant can review those records directly. More at bukucloud.com.

Frequently asked questions