Operations
Purchase order matching when you are the supplier
Your invoice usually sits unpaid over paperwork, not price: a retyped PO number, a packing slip missing it, a cert never attached. Here is the fix.
When you are the supplier, purchase order matching is not your customer's AP process. It is the reason your invoice sits unpaid. The invoice usually fails on paperwork rather than price: a PO line-item number that was retyped wrong, a packing slip missing the PO number, or a cert that was never attached to the billing packet. BrixIQ reads the incoming customer PO, groups its revisions and duplicates, picks the governing version, and matches it line by line against the order, then flags invoices whose required documents are missing before they go out. Mismatches are queued for a person to clear, not resolved automatically.
Nearly everything written about PO matching is written for the other side of the table. This is the version for the shop that is owed the money.
What is purchase order matching, and why does it look different from the shop side?
From the buyer's side it is a control. Two-way matching compares the invoice against the purchase order. Three-way adds the receiving record. Four-way adds inspection. The buyer's AP team runs the match to prevent paying for things that were not ordered or did not arrive, which is entirely reasonable.
From your side it is a test your cash flow depends on passing, that you did not design, and that you cannot see. When your invoice fails the match, nothing tells you. You find out 30 or 45 days later when the money does not arrive, and by then the person who typed the PO number has typed 200 more.
What does a customer actually require before it will pay an invoice?
The requirements are not secret. Most primes publish them, and almost nobody in the shop has read them. Northrop Grumman's Supplier Invoice Instructions (revised October 2025) open with the whole story in one sentence: "If the supplier invoice does not meet the criteria below, payment will be delayed until Corrected."
The list runs to ten required elements. The three that fail most often in practice:
- a complete and valid PO number,
- the PO line-item number for each invoice line, not just the header,
- the PO number carried onto third party shipping documents and packing slips.
Missing any of these may result in rejection. Then come the mechanical rules people forget exist: PDF only, one invoice per PDF attachment, the invoice must be the first page, letter or legal size, 300 dpi minimum, black and white with no greyscale or color. A packing slip submitted on its own appears on the documents-not-accepted list.
These are one prime's rules, and every customer's differ. That is precisely the point. The list exists, it is published, it is reasonable, and it is different for each customer you ship to. The shop that treats invoice requirements as tribal knowledge is retaking a slightly different test every week, blind.
Why do these invoices fail more when the shop is busy?
Because every requirement above is transcription, not judgment, and transcription error rates scale with volume and interruption rather than with anyone's competence.
Volume is exactly what changed this year. The July 2026 ISM report (released August 3) put Production at 58.5 percent, its highest reading since November 2021, up 6.3 points in a month. Backlog of Orders jumped to 55.0 from 50.5. Fabricated Metal Products and Primary Metals were both among the 15 industries reporting growth. More production means more shipments, more shipments mean more invoices, and the office producing those invoices is still the same two people.
So a busy quarter produces a rejection spike that looks like a staffing problem and is not. It is the same arithmetic that made quote turnaround the bottleneck of this upturn: the transcription desks do not scale with the floor. And the second-order effect is the cruel one: the shop that is busiest is least able to spare someone to work the exception queue, so rejected invoices age fastest exactly when cash matters most.
Is your customer's AP getting stricter, or does it just feel that way?
Stricter, measurably, because it is getting more automated. Microsoft's Business Central 2026 release wave 1 (generally available April 2026) rebuilt purchase invoice matching so an invoice line can be matched against multiple order lines and posted receipt lines, including partial receipts and item tracking.
What buyer-side automation means for you as the supplier: fewer humans reading past a typo. A person in AP could see that PO 44821 "line 3" obviously meant line 2 and pay it anyway. A matching engine posts an exception. Supplier-side reporting confirms where this lands: missing or incorrect PO numbers top the list of invoice rejection reasons (May 2026).
The tolerance for sloppy paperwork that existed ten years ago is being engineered out of your customers' AP departments, and it is not coming back.
What about the cert? The finishing-specific version of this problem
There is a failure mode none of the AP literature covers, and finishing shops live in it. The price was never disputed. The invoice itself is complete. The customer will not pay because the required document package (the CoC, the cert, the inspection record) was not attached, and the invoice is not rejected, it is parked, in a queue you cannot see.
Finishing shops get this worse than machine shops for structural reasons: more shipments, smaller dollar value per shipment, and a cert obligation on nearly every one. The cost of scattered quality records shows up here as aged receivables, not just as audit pain.
One fix needs no software at all: write down, per customer, exactly what must travel with the invoice, and make that list a checklist owned by one named person instead of tribal knowledge. That single page pays for the hour it takes.
How does BrixIQ change the shape of this?
The defect in this whole chain is created upstream, at the moment someone retypes a PO number. Chasing harder downstream does not fix it; reading the document does.
BrixIQ reads the incoming customer PO, groups its revisions and duplicates, picks the governing version, and matches it line by line against the order. On the way out, invoicing carries a required-document packet: a missing cert or CoC raises an exception before the invoice leaves, not 45 days after. Certs are generated from job data and findable by search.
| What happens to a mismatched PO line | By hand in the office | Typical ERP AP screen | With the document read |
|---|---|---|---|
| Who notices | Whoever retypes it, if they do | The customer's matching engine | The match, before invoicing |
| When | Sometimes never | 30 to 45 days later | Same day |
| What follows | The invoice goes out wrong | An exception on the buyer's side you cannot see | A queued mismatch for your person to clear |
The approval line stays where it belongs: PO mismatches are queued for a person to clear, not auto-resolved, and invoices are not released without a person releasing them. BrixIQ drafts and flags; your office decides.
One shop's own measurements, from Anodizers Inc, with the framing they deserve (one shop's numbers, not a benchmark or an average): PO tracking and validation went from three people spending an hour or more each to automatic, with only mismatches queued. Finding a cert went from 40 minutes to under a minute.
On cost, stated plainly: BrixIQ is $995 per facility per month with unlimited users, no setup fee, and metered usage with a cap you set. The base tier is print reading and estimating; finance, which covers the invoicing and collections described here, is an add-on module. For accounting, BrixIQ connects to QuickBooks Online, and it connects to the system you already have, or serves as the system of record for a shop with none.
Common questions
What is the most common reason a manufacturing invoice gets rejected?
A missing or incorrect PO number or PO line-item number. It tops the rejection-reason list in supplier-side reporting, and it is the first item on Northrop Grumman's published requirements.
Do I need to put the PO number on the packing slip too?
For some customers, yes, and Northrop Grumman requires it on third party shipping documents and packing slips explicitly. Check each customer's published supplier instructions; most primes have them.
Why does my invoice sit when nobody disputed the price?
Usually a required document was not attached. The invoice is not rejected, it is parked, and nothing notifies you. Cert packages are the classic case in finishing work.
Can I fix this without replacing my ERP?
Yes. The matching and the document packet come from reading the documents themselves, not from your ERP, so nothing gets replaced or migrated. For a shop with no ERP at all, BrixIQ can be the system of record, at the same product and price.
Does BrixIQ pay or approve anything on its own?
No. It drafts and it flags. Mismatches queue for a person, and a person releases every invoice.