# Incomplete ERP Spend Data? Read the Invoices

> Most spend data problems are not missing data. The detail is sitting in invoice PDFs your ERP never kept. Here is where it goes, and how to get it back.

Source: https://www.spendcraft.com/blog/erp-drops-line-items-invoices-dont/

Aditya Chavali, 2026-11-04

"Our ERP data is not good enough for this."

I hear this in almost every first call. Sometimes it comes from procurement. More often it comes from finance or IT, right before they suggest waiting until after the next data cleanup project.

They are usually right about the ERP. They are usually wrong about the conclusion.

## Where the detail goes

A supplier sends an invoice. It has twelve lines. Each line has a description, a unit of measure, a quantity, a unit price. Sometimes a contract reference. Sometimes a freight charge broken out on its own.

Then AP posts it.

The ERP keeps a vendor, a total, a GL code, maybe a PO number. Line descriptions get truncated to fit a field. Units of measure disappear. Twelve lines become one. The freight charge gets folded into the total.

Nobody did anything wrong. AP is paid to post invoices accurately and on time, not to preserve detail for a category manager two years later. The ERP did its job. It recorded the payment.

But the detail you need for spend analysis is exactly the detail that got dropped.

## The data is not missing. It is in a different place.

Every one of those invoices still exists. A PDF attached to the AP record. A scan in a shared folder. An email attachment from the supplier.

The line descriptions are there. The quantities are there. The contract reference is there.

So the real question is not whether your data is good enough. It is whether your spend tool reads the invoice or only the ERP.

## What changes when you read the invoice

SpendCraft does this with Invoice Augmentation. It reads invoice PDFs, scans and supplier attachments, and recovers the details your ERP dropped or truncated: line descriptions, units of measure, quantities, contract references.

That detail matters most in three places.

**Classification.** A truncated description like "SVC CHG MAINT" is a guess. The full invoice line tells you what was serviced, how often, and under which agreement. Better input, better classification, fewer items in "Other".

**Price analysis.** You cannot compare unit prices when the ERP only kept totals. With quantities and units back, you can see what you actually paid per unit, and whether it moved.

**Recovery.** This is where finance pays attention.

## The money sitting in the detail

Some of the clearest savings in spend data are not negotiations. They are corrections. Money already paid that should not have been.

They only show up at line level.

- **Duplicate invoices.** The same invoice, posted twice, under a slightly different number or date.
- **Billed above PO price.** The PO said one price. The invoice charged more. AP matched the total and paid it.
- **Unapplied credits.** The supplier issued a credit. Nobody applied it.
- **Freight.** Charges that do not match the terms you agreed.

SpendCraft has a Caddie for each of these. Each one surfaces what may warrant review, you confirm what is real, and the result goes into a Recoveries Space.

One thing I insist on. The totals in those findings are sums of actual invoice amounts. Not estimates. Not "up to". When finance asks where a number came from, you can show them the invoices.

## You do not need a cleanup project first

The instinct is to fix the data, then analyze it. That project takes months and rarely finishes.

Start with what you have. Connect the ERP or upload a file. Bring the invoice documents along. Let the system recover the detail, and judge the result on your own spend.

That is what a Proof of Value is for. One category or one moment, worked end to end on your data. If the detail is not there, you will know quickly. Usually it was there all along. It was just never in the ERP.