Vendor payment disputes: two records of the same work that never met

Two emails, one week apart

The first email came from the vendor: milestone two is done, please pay. The second came from finance a week later: the purchase order has no budget left. Between them, a relationship that had taken a year to build was close to breaking. The vendor felt cheated. Finance felt pressured. The project manager was in the middle, with a deadline that needed the vendor's next phase.

The person who saw it first

Layla, the project manager, did not take sides. She put both records on one screen. The purchase order had three milestones. The first had been paid. The second was complete on the plan, with the vendor's delivery attached and accepted by the client. The order's budget had not been spent on the vendor's work at all: a change request had been charged to the wrong line.

Ten minutes later the money was on the right line, the payment was approved, and it went out on Thursday. The vendor signed the next phase the following month, and the change request was billed where it belonged.

The textbook name: the vendor payment dispute

Vendor payment disputes rarely start with bad faith. They start with two records of the same work that never meet. The vendor tracks what was delivered. The project tracks the plan. Finance tracks the purchase order and its budget. When these three live in different systems, every milestone becomes a reconciliation, and every reconciliation is a chance for an argument.

The cost is high. Late payments damage the vendor's cash flow and the client's reputation. Disputes consume the time of senior people. And a vendor who feels unfairly treated prices that risk into the next contract.

Signs to watch for

Disputes are predictable. Watch for milestones described in the contract in words that nobody tied to a task in the plan. Purchase orders with a single line for very different kinds of work. Deliveries sent by email to one person and never recorded where finance can see them. Change requests approved without saying which order line will carry their cost.

Another sign is the tone of vendor emails. When a vendor starts sending reminders with dates and amounts in bold, the relationship is already costing you. Good vendors are in demand, and they remember which clients pay on time without an argument.

The cost is not only the dispute itself. Every hour a project manager spends reconciling three records is an hour not spent on the project. Every late payment weakens your position in the next negotiation. And when an auditor later asks why a payment was made, the answer should be one record, not a folder of emails.

How to prevent it

Tie the money to the work. Each milestone should sit on a line of the purchase order and on the project plan at the same time. Completion should be a recorded event with the delivery attached and an acceptance by a named person. Payment should follow from that acceptance, through an approval, without a separate negotiation. And everyone involved should read the same record.

How ApprovedFlow does it

In ApprovedFlow vendor milestones sit on the lines of the purchase order and on the project's plan. A milestone can be a fixed amount or a percentage of its contract line. When it is completed and accepted, its payment is released for approval, and the order shows what has been used and what is left. Finance, the project manager and the vendor read the same record, so a dispute becomes a ten-minute check.

A question for you

When a vendor says done, who on your side can prove it, and how long does it take?