Accounts payable: what each role knows and where the gaps cause trouble

Each role in accounts payable sees one slice. Buyers know what was agreed. Receivers know what arrived. Approvers know whether the spend was wanted. AP clerks know what the invoice says. Treasury knows the cash. Trouble starts where one slice is treated as the whole picture.

Buyers and the vendor master

The buyer negotiated the deal. They know about the side agreement on freight, the price that was supposed to drop after the first delivery, and the supplier contact who actually answers email. Very little of that reaches the purchase order. Even less reaches the vendor master file.

The person who maintains vendor records knows something the buyer usually does not. They know which bank details changed recently, which supplier exists under two names, and which records were set up in a hurry. When an invoice fails to match, the clerk sees a price difference. The buyer would see a deal that was never written down. Neither sees the other's view without a phone call.

Receiving

The warehouse or the requester confirms that goods or services arrived. They know about partial deliveries, substitutions and damaged items sent back. They often record receipt late, or in bulk, or not at all for services.

AP cannot tell the difference between "not yet received" and "received but never logged." Both look identical in the system. Many exceptions that land on the AP desk are really receiving problems in disguise.

The clerk keying and auditing invoices

The AP clerk knows the invoice better than anyone. They spot the duplicate with a slightly altered number. They notice when a supplier's letterhead changes. They know which vendors always bill before shipping.

What the clerk lacks is context on intent. A clerk can see that an invoice exceeds the order. Whether the excess was authorised over the phone is invisible to them. So they park it as an exception, and it sits until someone with that knowledge responds.

Approvers

Budget holders know whether the spend was wanted and whether the work was done well. They rarely know the payment terms, the early payment discount, or that the supplier is already chasing. An approval request that arrives without that information gets treated as low priority.

The opposite gap matters too. Approvers sometimes sign anything that looks familiar. AP assumes approval means scrutiny. Often it means the approver recognised the vendor name.

Treasury and the payment run

Treasury knows the cash position and which payments can wait. It does not know which supplier has threatened to stop deliveries, or which invoice the clerk released only after a long dispute. Holding a payment run for liquidity reasons can undo weeks of relationship repair that nobody in treasury knew about.

After payments go out, someone must confirm they settled. Returned payments and rejected bank details come back to treasury first. Whether that news reaches the vendor master team quickly decides whether the next run fails in the same way.

The close team

The accountant running period end needs accruals for goods received but not yet invoiced. They depend on receiving data and on AP's view of what is still in the queue. They also post the reversals next period. If AP clears a backlog just after close, the accrual and the actual invoice can both hit the ledger. The close accountant sees a variance. AP sees a normal week. Manual journal adjustments then paper over a timing problem that a short conversation would have explained.

Tax and reporting

Whoever handles payables tax knows which vendors need year-end information returns, which purchases carry use tax, and where withholding applies. That knowledge depends on tax classifications captured when the vendor was set up. If the vendor master team did not know a field mattered, it is blank, and the gap surfaces only when reports are due.

Inquiries

Suppliers know things AP does not: that a payment arrived without a remittance advice, that a credit note was issued but never applied, that a contact left. The person answering supplier calls often holds the best early warning in the whole process. That information is rarely logged anywhere others can see it.

Questions to ask the people who run the process

What is written down and what happens usually differ. These questions tend to expose the difference.

• When an invoice does not match the order, who do you actually contact, and how do you know it is them?
• Which suppliers do you handle differently from the documented steps, and why?
• How do service receipts get recorded, if at all?
• What do approvers see when they open a request, and what do they ask you for afterwards?
• When a payment bounces, who finds out first, and how long until the vendor record is fixed?
• Which spreadsheets or inboxes hold information the system does not?
• At month end, which invoices do you hold back or rush through, and does the close team know?
• Which vendor fields get left blank because nobody explained their purpose?
• What do suppliers complain about most when they call?
• If you were away for a fortnight, what would break first?

The answers point to where knowledge lives in one head and nowhere else. Those places are where 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.