You Pay Supplier Invoices on Trust. That's Where the Money Goes.

Field Forge now checks every supplier invoice against what you ordered and what turned up on site, and flags the price creep, the double charges, the wrong-supplier bills and the over-charges before you pay them. Three-way matching, built into the way you already raise POs.

You pay supplier invoices on trust

Be honest about how a supplier invoice actually gets paid. It lands. Someone opens it, glances at the total, and pays it. Nobody pulls the original purchase order. Nobody checks it against what was delivered. There is no time, and most of the time it is roughly right, so it gets paid.

"Roughly right" is the problem. A unit price that crept up £20. A line billed for twelve when ten turned up. An invoice from a supplier that is not even on the order. The same invoice number, paid twice, three weeks apart. None of these announce themselves. They just quietly come out of the margin on a job you thought you had won.

Across a year and a few hundred POs, "roughly right" is a number you would not like to see written down.

What three-way matching actually means

Three-way matching is the discipline that proper finance teams have used for decades, and it is exactly three questions, asked together, before a penny goes out:

1. What did we order? (the purchase order)
2. What did we receive? (the delivery)
3. What are we being billed? (the supplier invoice)

If those three do not agree, you do not pay until they do. Simple in principle. The reason most trades never do it is that doing it by hand, per line, per invoice, is a job nobody has time for.

So we made the system do it.

What Field Forge catches, automatically

When you record a supplier invoice against a PO, Field Forge compares it line by line and raises anything that does not line up:

• Price creep. The PO says £260 for the skip. The invoice says £280. You see "£260 to £280, +7.7%" against the line, and anything past your tolerance is flagged for a look rather than paid on the nod.
• Over-billing. Invoiced for more than you ordered? Twelve charged against ten ordered gets flagged, not buried in a subtotal.
• The wrong supplier. An invoice whose company does not match the supplier on the PO is flagged on sight. Mis-directed and duplicate-vendor invoices are one of the most common ways money walks out of a business, and it is exactly the kind of thing a tired Friday afternoon misses.
• Duplicate invoices. The same invoice number cannot be slipped through and paid a second time.
• Currency and totals. A bill in the wrong currency, or one whose figures do not add up, is caught before it reaches your accounts.

These checks are not a nicety in the screen you happen to be looking at. They run on the server, so the control holds however the invoice gets entered, and a flagged invoice cannot be quietly signed off. Anything outside tolerance lands in front of your accounts person with the reason attached.

The catalogue keeps you honest

Matching does more than protect the bill in front of you. When you keep a line, Field Forge can add it to your parts catalogue at the price you actually paid. Your catalogue stops drifting away from reality while your suppliers reprice, so the next quote you write is costed on real numbers, not last year's.

Better matching feeds better quoting. That is the bit that compounds.

Labour and subbies, not just materials

Most matching tools assume everything is a box you can receive into a warehouse. The trades do not work like that. You cannot "goods receipt" a day of labour or a subcontractor's work.

Field Forge handles labour, subcontractor and plant lines with a streamlined two-way match: the invoice is the gate, no pretend delivery note required, while materials still need a delivery confirmed before they match. CIS sits in the right place throughout, because you are raising POs to subbies as a matter of course.

The AI suggests, the system signs nothing off on trust

We will keep saying this because it matters. The AI reads the invoice and proposes the match. It does not invent your totals, and it does not approve anything. Every line total, variance and VAT figure is computed by a deterministic engine, and a query has to be resolved, or consciously approved with a recorded reason, before the PO closes. No number lands on your books because a model felt confident.

Every step, the upload, the extraction, the variance flag, the sign-off, sits on an audit trail. When your accountant or HMRC asks where a figure came from, the answer is one click.

See it on your own invoices

Field Forge is the AI-native operating system for UK trade contractors. Start a free 30-day trial at fieldforge.io, raise a PO, record an invoice against it, and watch the match do the checking you never had time for.