Supplier payment tracking finance and operations can both trust

Why operations and finance disagree about supplier payments

Supplier payment tracking that both finance and operations trust comes from one shared record per bill, showing whether it is approved, scheduled, paid or on hold, with the payment date and reference visible to anyone who needs it. When operations can check status themselves, they stop relying on finance's memory or their own side spreadsheet.

The disagreement usually starts with a supplier phone call. A site manager is told deliveries will stop until an overdue bill is settled. The manager asks finance, finance says the bill was never approved, and the manager insists it was signed weeks ago. Each is describing a different document, and neither can see the other's view.

Fields every supplier payment record should carry

If any of these is missing, someone will keep it in a separate file, and that file becomes the version operations believes.

• Supplier name and code from the supplier master
• The supplier's own bill number and bill date, exactly as printed
• Purchase order or contract reference
• Department and cost owner who requested the purchase
• Due date under the agreed credit terms
• Current status and the date it last changed
• Scheduled payment run
• Bank payment reference once paid, or the hold reason if held

Status definitions both teams sign up to

Agree the meanings in writing. Approved should mean approved for payment, not merely that a manager has seen the bill. Paid should mean money has left the bank, not that a payment file was prepared. When finance says paid and the supplier says nothing arrived, the gap is often a batch prepared but not yet released by the bank signatories.

Add a held status with a compulsory reason, such as disputed quantity, missing delivery note, or awaiting a supplier credit note. Held bills are the ones operations most needs to know about, because they usually need action from the department that made the purchase.

Partial payments and set-offs need their own handling. If finance pays part of a bill pending a credit note, or offsets an amount the supplier owes back, the record should show the balance remaining and why. Otherwise operations sees a bill marked paid, tells the supplier the matter is closed, and the supplier rings back about the shortfall a fortnight later.

Retentions on construction or project contracts are a common example. The supplier sees a retention as money owed; finance sees it as not yet due. Record retained amounts separately, with the release condition and the person who confirms it has been met.

Answering supplier queries from the record, not from memory

Give operations read-only visibility of bill and payment status for their own suppliers or cost centres, through system access or a regular report. A site manager who can see that a bill is held for a missing delivery note can fix the problem directly. Without that visibility, the same manager phones finance, waits, and passes vague news back to the supplier.

For finance, the rule is that supplier queries are answered from the record. If the record cannot answer the question, it is incomplete, and the fix goes into the record. Over time this ends the habit of individual AP staff keeping private notes on which suppliers are sensitive.

Send remittance advice with each payment, quoting the supplier's own bill numbers. Suppliers allocate receipts against their invoices, and a lump sum with no breakdown generates more calls.

A weekly payment review between finance and operations

A short standing review catches problems before suppliers escalate. The agenda can stay the same each week: held bills and who owns each one, bills due in the next payment run that still lack approval, suppliers who have contacted operations about money, and any supplier operations wants prioritised because of a critical delivery.

Finance brings the status report and operations brings the supplier conversations. Priority payment decisions are made in the meeting and recorded, which heads off side requests later in the week.

Keep the meeting tied to the record. If a status is wrong in the system, correct it during the review rather than noting it for later. If a supplier keeps appearing on the agenda, look at the cause: unclear delivery documentation, terms that do not match the purchase order, or a buyer who places orders outside procurement.

Recording bills and payments in the same place

The surest way to keep one version of payment status is to record bills and supplier payments in the system that produces the accounts. BukuCloud handles bills and supplier payments together, so a bill shows as paid because a payment was entered against it, not because someone updated a tracker. See bukucloud.com.

Frequently asked questions