Purchase Order to Bill: Closing the Loop Between Your Field Software and Your Books

A purchase order has 4 states and most systems only track the first. Created, received, invoiced by the supplier, paid. The leak sits between state 2 and state 3, where the part is on the job and the supplier bill has not arrived, and nobody owns that gap.

The short version

The customer was invoiced last week. The supplier bills you this week. Somebody has to decide whether that bill is right, which job it belongs to, and whether it matches what was ordered.

In most service companies that person does it by memory and email search, once a month, under time pressure. It is one of the least visible jobs in a service business and one of the most expensive when it goes wrong:

• Bills paid that do not match what was ordered
• Bills paid twice, usually when a supplier resends
• Job costs that are complete only after month end, if ever
• Credits for returned parts that never arrive and nobody chases

None of that is an accounting failure. It is a handoff with no record on either side of it.

4 states, and the gap where the money sits

The purchase order is the only object that spans both systems, which is why it has to carry the state.

State	What is true	Where it usually lives
1. Raised	Ordered from a supplier for a job, not yet arrived	Field software, or an email
2. Received	The part is here, the cost belongs on the job	Field software, if receiving exists
3. Billed	The supplier has invoiced you for it	Accounting, arriving separately
4. Paid	Money has left	Accounting

Two things go wrong at the boundary. A purchase order stuck at state 2 forever is a part received with no bill, which is either a supplier who has not invoiced or a bill that arrived and was matched to nothing. Both are money and neither shows up on any report most service companies run.

A purchase order that jumps from 1 to 4 is worse. The bill was paid without anyone confirming the part arrived or that the price matched the order, which is where duplicate payments and quiet price increases live.

The accrual nobody makes

Between received and billed you owe money you have not been asked for, and your books do not know.

For a service company with a handful of open orders that is a rounding error. For a service company with three or four technicians ordering parts across a month, the total sitting in that gap at any moment is real, and it makes the month look better than it is.

The consequence is a familiar pattern. A good month, then a poor one, and the difference is largely when supplier bills happened to land rather than how the work went. Anyone trying to read job margin or monthly profit from that is reading noise.

Closing it does not require accrual accounting or a bookkeeper. It requires the received state to exist and to be visible, so the value of parts received and not yet billed can be seen as a number rather than inferred.

What "syncs with QuickBooks" has to mean here

Every product in this category says it integrates with accounting, and the range behind that phrase is wide.

For the purchase order loop specifically, three questions decide whether the handoff is closed:

1. Does a vendor bill exist as a record? Not just an invoice to your customer, but a bill from your supplier, with the vendor on it.
2. Can it be matched to the purchase order that caused it? Automatically or with one click, rather than from somebody having kept track.
3. Do credits and corrections cross? Returns, restocking fees and price adjustments are ordinary here, and plenty of integrations move invoices in one direction only.

Roopairs describes its QuickBooks connection as an integration sync rather than an export, working with Online or Desktop, and what moves includes vendors, bills, credit notes and the journal entries behind them along with the deletes, voids and updates that follow. The second half of that list is the part that decides how much of month end is done by hand, and it is the part most integrations stop short of.

Three-way matching, without the enterprise version

The principle is that three documents have to agree before money leaves: what you ordered, what arrived, and what you were billed.

In a large business that is a formal control with segregation of duties. In a six-van service company it is a two minute check, and it catches the three things that actually happen:

• Price drift. The order said one price and the bill says another. Usually legitimate and worth knowing.
• Quantity mismatch. Three ordered, two delivered, three billed.
• The duplicate. A supplier resends a bill and it gets paid twice because nobody recognized it.

The reason to do it at the purchase order rather than at the bill is that the purchase order knows the job. Catching a price difference is useful. Catching it and having the job it affects is what lets you decide whether to re-invoice the customer.

The mechanics of matching deserve their own treatment, and this page is about the handoff rather than the check.

Who owns the gap

The most common root cause is that nobody does. The technician fitted the part, the office invoiced the customer, and the bookkeeper pays what arrives.

Naming an owner is a five minute decision and it changes the outcome more than any tool:

• Somebody receives. Parts arriving get marked received, same day, by whoever unpacks them. This is the step that most often does not exist.
• Somebody reviews open orders weekly. Ten minutes on anything received and not billed, or raised and not received after a two weeks.
• Somebody matches before payment. Not a formal control, just the two minute check above.

The weekly review is the one that pays. It surfaces the supplier who never invoiced, the credit that never arrived, and the order that was placed twice, all while the people involved can still recall the job.

Closing the loop this quarter

Start by counting the gap rather than fixing it. Pull every purchase order created in the last three months and mark which ones you can trace to a supplier bill. The proportion you cannot is the size of the problem, and it is usually larger than expected.

Then add the received step if it does not exist, because everything downstream depends on it. Then put the weekly ten minutes in somebody's calendar.

Software matters at the point where the purchase order, the job and the bill have to be one chain rather than three records that a person connects. Until then the discipline does most of the work.

Roopairs runs a product tour where you can follow one job from the purchase order through to the supplier bill reaching the books.

What service companies in the trade say

“It tracks technicians in the field, cust information, job locations, parts & pricing, vendor information and job scheduling.” — D. Williams

Also worth reading

• Purchase Orders in Field Service Software
• Three-Way Matching for Service Companies
• Service software built to manage purchase orders and inventory

Frequently asked questions

What does purchase order to bill mean?

The full path a parts purchase takes: created with a supplier for a job, received when the part arrives, billed when the supplier invoices you, and paid. Closing the loop means each step is recorded and connected to the one before, so the cost reaches the job and the bill can be checked against what was ordered.

Why do supplier bills get paid without checking?

Because the check requires two records that usually live in different places. The order is in field software or an email and the bill is in accounting, and matching them by hand takes longer than paying. That is the specific manual step this loop exists to remove.

What is the received state and why does it matter?

Marking that a part physically arrived, separately from ordering it and from being billed for it. It matters because it is when the cost belongs on the job, and because the difference between received and billed is money you owe that your books do not yet know about.

How do I stop paying a supplier bill twice?

Match every bill to a purchase order before payment, and treat a bill with no matching order as a question rather than an invoice. Duplicates almost always arrive as a resend of something already paid, and they are obvious the moment the purchase order is the thing being paid against.

Does this need accrual accounting?

No. It needs the received state to exist so you can see the value of parts received and not yet billed. Whether you formally accrue that is a conversation with your accountant. Seeing the number is useful regardless of how the books are kept.

What if our supplier bills monthly in one statement?

Then matching is at the line level rather than the document level, and it is more work rather than less. Ask the supplier for line references to your purchase order numbers on the statement. Most will do it, and it turns a monthly reconciliation into a comparison.