---
title: "Invoice audit and spend analysis: every invoice read and checked"
description: "The module takes invoices as PDFs, e-invoices or CSV, checks each line against its arithmetic, earlier invoices and agreed prices, and adds up the spend."
url: https://www.cureman.de/en/modules/invoice-audit-and-spend-analysis
language: en
updated: 2026-11-16
alternate_de: https://www.cureman.de/de/module/rechnungspruefung-und-ausgabenanalyse.md
---

# Invoice audit and spend analysis: every invoice read and checked

> The invoice audit and spend analysis module of Cureman reads every invoice into line items, checks it and adds it up. Structured e-invoices such as XRechnung, Peppol, ZUGFeRD and Factur-X are parsed without a model. PDFs and images are read by a model and stay labelled that way until a person has reviewed them. Each invoice is checked against its own arithmetic, earlier invoices and agreed prices, and all lines are added up by category, supplier, item, month and delivery site. It works for software, services and physical goods alike.

An invoice is the one document that says what was actually bought, in what quantity, at what price and from whom. This module reads every invoice into line items, checks each of them and adds the lines up into a picture of spend. It works the same for software, services and physical goods, because a line is a description, a quantity, a unit and a price.

## What it takes in

| Way in | How it is read | Model involved |
| --- | --- | --- |
| E-invoice XML: XRechnung, Peppol BIS, ZUGFeRD, Factur-X | Parsed as structured data | No |
| ZUGFeRD PDF | The XML attached inside the PDF is found and parsed | No |
| Other PDFs, scans and photos | A model transcribes the document into a fixed shape | Yes |
| CSV export with one row per line item | Parsed, with English or German headers and number formats | No |
| Typed in or corrected on the invoice page | By a person | No |

Documents arrive by upload or through an ingest endpoint that scripts and mail-to-webhook services can post to. What a document is, is decided from its first bytes and not from its name, and the same file sent twice gives one invoice.

## Read, then checked

Whoever read the invoice, its own figures are checked by arithmetic: the required details are present, the lines add up to the net total, quantity times unit price gives each line amount, net plus tax gives gross, the tax matches the rates of the lines, and the due date is not before the invoice date.

- A parsed, imported or typed invoice whose checks pass is accepted.
- An invoice read by a model whose checks pass is accepted where the organisation allows that, and otherwise waits for review. Either way it stays labelled as read by a model until a person has reviewed it.
- An invoice with a failing check waits for review with the check named. The reviewer corrects what was misread or accepts the document as it is, and then the audit raises the difference.
- A document that is not an invoice, such as a reminder or a delivery note, is rejected.

Each line is then matched to a supplier, an item, a unit, a category and the delivery site the invoice prints.

## What the audit finds

| Finding | Amount |
| --- | --- |
| Duplicate invoice: same supplier, number and gross amount, or same supplier, amount and date under another number | Gross of every copy after the first |
| Arithmetic in the supplier's favour | The differences |
| Price above an agreement with that supplier for that item | (Billed minus agreed) times quantity |
| A period billed twice | The later line times the overlapping share of its period |
| Bank details changed from what earlier invoices used | None: an action item |
| Early payment discounts on offer | Gross times the discount rate, at low confidence, because payments are not known |

Amounts found once are shown as "to recover, once". They are never added to yearly savings.

## Spend analysis

Twelve months of lines, with credit notes counted negative, are added up by month, category, supplier, cost centre and delivery site. The analysis shows which suppliers carry most of the spend, the tail of small suppliers, the suppliers that bill regularly and the price history of each item across suppliers. From this it raises findings on where to tender, consolidate or renegotiate:

- an item bought from several suppliers at different average prices;
- one supplier billing the same item at different prices depending on the delivery site;
- an item under an agreement bought elsewhere at a higher price;
- a supplier's unit price that rose in recent months, valued at what the increase costs on last year's quantity;
- large suppliers without agreed prices, and a long tail of small ones, both without an amount.

A saving nobody has quoted or billed is not counted.

## From a finding to money back

Every finding has an action plan. For a duplicate, an arithmetic error, a price above the agreement or a period billed twice, a message asking the supplier for a cancellation, a corrected invoice or a credit note is drafted from the computed facts. A person approves it before it is sent, and the reply is filed with the conversation. For changed bank details the plan sends nothing: it tells a person to confirm the account by phone with a contact they already know. Price findings lead to a draft sourcing event where [sourcing and negotiation](https://www.cureman.de/en/modules/sourcing-and-negotiation) is booked. Invoices to review and steps to approve wait in the list of decisions.

## What it needs and what it measures

The module requires no other module. It meters the amounts recovered through invoice findings that were marked done in the month.

## Related reading

- [Invoice audit checklist](https://www.cureman.de/en/articles/invoice-audit-checklist)
- [Detecting duplicate invoices](https://www.cureman.de/en/articles/detect-duplicate-invoices)
- [Finding price increases on invoices](https://www.cureman.de/en/articles/price-increases-on-invoices)
- [Spend analysis basics](https://www.cureman.de/en/articles/spend-analysis-basics)
- [E-invoices: XRechnung and ZUGFeRD](https://www.cureman.de/en/articles/e-invoices-xrechnung-zugferd)
- [Changed bank details on invoices](https://www.cureman.de/en/articles/changed-bank-details-on-invoices)

## Questions and answers

### Is what a model reads from an invoice trusted?

No. A PDF or a picture is transcribed by a model into a fixed shape, and from there it is treated as data. The amounts are checked against each other by arithmetic, the invoice is labelled as read by a model until a person has reviewed it, and a finding that rests on it is never given high confidence. An organisation can require a review of every model-read invoice.

### Which e-invoice formats are read without a model?

XRechnung and Peppol BIS in the UBL syntax, and ZUGFeRD and Factur-X in the CII syntax. They are parsed as structured data. A ZUGFeRD PDF is read from the XML attached inside it. CSV exports with one row per line item are also parsed without a model.

### Does the module work for physical goods and services, or only for software?

For all three. An invoice line is a description, a quantity, a unit and a price, whatever was bought. Categories, items, suppliers and delivery sites are matched in the same way for office supplies, maintenance contracts or software subscriptions.

### Can invoices be collected from our mailbox?

Not directly. The mailboxes an organisation connects are for conversations, and the product does not collect invoices from them. For an automatic flow there is an ingest endpoint with a key of the organisation's own, which a mail-to-webhook service or a script can post documents to.

### What does the module count as a saving?

The amounts recorded as recovered on invoice findings that were marked done, for example a credit note for a duplicate. Amounts found once are shown as to recover once and are never added to yearly savings. There are no benchmark figures, and a saving nobody has quoted or billed is not counted.

## Read next

- [Invoice audit checklist: what to check on every invoice](https://www.cureman.de/en/articles/invoice-audit-checklist): Six checks for every supplier invoice before it is paid: formal details, arithmetic, price, duplicate, billing period and bank details, each with its rule.
- [How to detect duplicate invoices before and after payment](https://www.cureman.de/en/articles/detect-duplicate-invoices): Matching rules for exact and near duplicate invoices: normalised invoice numbers, amount and date, credit notes, and what to do once a duplicate is found.
- [How to find price increases on supplier invoices](https://www.cureman.de/en/articles/price-increases-on-invoices): Build a unit price history per item and supplier from invoice lines, spot the increase, compute what it costs per year and check it against the agreement.
