It is the second week of the month and the office manager at a sixty-person machine shop has the card statement open beside a spreadsheet. Forty-one charges. Eleven have no receipt. She emails the maintenance lead, the two buyers and the owner, again: please send receipts. The maintenance lead replies with one photo of a crumpled slip from the bearing supplier. She codes it to repairs and maintenance, because it usually is, and moves on.
Clearing the card statement is three jobs, not one
Every card charge has to answer three questions before the month closes, and they are different kinds of question.
The first is clerical: is there a receipt, and does it match the charge? No judgment is involved, only patience.
The second is a pattern: which account does this hit? Bearings from the same supplier go to the same place nearly every month. Most of the time the right answer is whatever the answer was last time.
The third is judgment: what was this for? Was the bearing for the spindle on machine 4, which is overhead, or for the customer's fixture on work order 2231, which is a cost on a job you will be quoting again? Only the person who bought it knows, and they knew it best on the day they bought it. It matters most for job costing and gets the least attention, because it comes last.
What PEX says it shipped, and where it stops
CPA Practice Advisor reported on October 13, 2026, in a piece that restates the company's announcement, that PEX, a company card and spend management platform, has launched a set of AI features. No independent testing was found, so everything here is PEX's own account. As of October 2026, PEX says it reads each receipt and matches it to the card transaction, suggests a GL code based on the team's history, and reads details off bills.
None of this is new for this job. PEX described AI receipt matching in a 2024 product update and says it introduced AI GL coding in 2025; the October launch gathers both under the PEX AI name. Together they aim at the first question and offer a guess at the second. PEX's help pages add a catch: without a receipt, the AI will not suggest a code. In the scene above, eleven of the forty-one charges would get nothing.
It does not touch the third. A GL code from history is an account, not a work order, and nothing in the announcement mentions coding a charge to a job, a work order or a customer. PEX's QuickBooks Online connector already syncs transactions and receipt images nightly and maps QuickBooks Category, Class and Customer fields to PEX tags, so a shop that tracks jobs as QuickBooks customers, on a PEX plan that includes tags, can already tag a charge to a job, by hand. It all works only on PEX cards, and someone on the floor still has to send in the receipt. PEX describes anomaly detection as "coming soon," so do not plan around it.
The hard part is the history it learns from
A suggestion drawn from past coding is only as good as past coding. In our experience, the account a small shop uses for "parts" has years of guesses in it, made by whoever was clearing the statement that month. Software that learns from that history will repeat the guesses, faster. The first month on any tool like this is an audit of your own chart of accounts, whether you planned one or not.
Who will resist, and why they are right
The office manager will resist, and she has a point. She will know which suggestions are wrong, because she made half of the original mistakes and corrected the other half by hand. If the tool proposes a code and her job becomes clicking approve, the easiest path is to approve everything, and the errors that used to get caught will flow straight into job costs. Expect her to keep her own spreadsheet beside the new screen for a few months. Let her. That spreadsheet is your test of whether the suggestions are any good.
The honest no: if your people cannot tell you what a purchase was for at the moment they make it, no matching layer will tell you later. Fix that first: a work order number in the text that carries the receipt photo costs nothing and answers the question software cannot. And if you run fewer than about thirty card charges a month, an hour of someone's time is cheaper than changing card programs for this feature.
If this is your Thursday afternoon, the ten agent roles are in the Library.