Ask a health system CFO where their supply chain spend data lives, and you'll get three different answers depending on who's in the room. The AP team points to invoices. The finance team points to the General Ledger. Supply chain points to the ERP's PO and receiving records. All three are supposedly describing the same transaction. In practice, they rarely agree, and almost nobody has the time or tooling to figure out why.

That gap is where health systems quietly bleed margin.

What invoice data should be

In a clean world, an invoice is a structured, machine-readable record: vendor, item, quantity, unit price, contract reference, PO number, GL code, and delivery confirmation, all tied together and postable in near real time. It should match the purchase order it came from and the receipt that confirmed the goods arrived, at the line-item level, not just the total dollar amount.

What invoice data actually is

Most health systems are still working with PDFs, scanned images, and EDI feeds of wildly varying quality. Vendor names show up five different ways across five invoices from the same company. Units of measure don't match between the invoice and the PO (a case here, a box there). Contract pricing gets negotiated centrally but enforced inconsistently at the invoice level, so the system pays list price on a meaningful share of transactions without anyone noticing. Coding to a GL category often happens manually, by someone doing their best guess under time pressure, not by someone who understands the clinical or supply chain context.

None of this is anyone's fault exactly. It's the natural output of high transaction volume, fragmented vendor relationships, and systems that were never designed to talk to each other cleanly.

What actually lands in the General Ledger

By the time spend hits the GL, most of the texture is gone. You get a category rollup and a dollar figure. You don't get the line-item detail, the vendor-specific pricing variance, or the exception history that would tell you why a number moved. A CFO looking at the GL can see that supply expense in a category went up. They can't see, without a lot of manual digging, whether that's volume, price creep, a contract lapse, or a coding error.

That disconnect between the transactional detail and the financial rollup is exactly why so much supply chain leakage never gets caught. The evidence exists somewhere in the system. It's just not connected to anything that would flag it.

The 3-way match that never actually matches

The 3-way match—tying the PO, the receipt, and the invoice together before payment—is supposed to be the control that catches all of this. In theory, if the three documents agree, the payment is legitimate. In practice, exact matches are the exception, not the rule.

Partial shipments break it. Blanket POs against which dozens of invoices get billed over months break it. Price variances that fall under approval thresholds get waved through without real scrutiny. Unit-of-measure mismatches create phantom discrepancies that look like errors but aren't, and real discrepancies that look fine but aren't. AP teams, faced with volume and no time, end up approving on exception thresholds that are wide enough to let real problems through, or narrow enough to bury the team in false positives.

The result is a control that exists on paper but doesn't actually do the job it was designed to do at the level of rigor a CFO would assume it does.

Why this is the use case AI was built for

This is not a problem that needs more headcount doing the same manual reconciliation faster. It's a problem of pattern recognition across messy, unstructured, high-volume data, exactly the kind of task where AI has a real, unglamorous, high-ROI role to play.

An AI system can normalize vendor names across formats, reconcile units of measure automatically, learn what a genuine contract price variance looks like versus a legitimate exception, and connect invoice-level detail all the way through to GL impact. It can surface the handful of discrepancies that actually matter out of thousands that don't, and it can do it continuously instead of in a quarterly audit that finds problems six months too late.

This is the core of what Translucent does. We don't treat supply chain spend and the GL as two separate systems that occasionally get reconciled by hand. We connect the invoice, the PO, the receipt, and the ledger into one connected layer, so a CFO can see not just that a number moved, but why, and what it's doing to margin.

The 3-way match was never the problem. The fact that nobody had the tooling to actually run it at the line-item level, at scale, in real time, was the problem. That's solvable now.

‍