For finance and billing teams

Answering an invoice trace request

A customer has asked for the calculation behind a usage invoice, line by line, before they approve it. Here's what they're asking for, why it's a fair request, and how to answer it on one page.

TrueUpp · 19 October 2026 · 6 min read

What the request asks for, and why it's reasonable

A trace request usually comes from the customer's finance, procurement or FinOps team. They've taken the terms in their order form, recomputed the invoice, and arrived at a different number, or at a range of numbers because the order form doesn't settle every rule. They're asking for two things: the calculation behind your figure, line by line, and a plain answer on each rule they list.

It's a request for information, and a fair one. Their accounts payable team can't approve an amount it can't trace to a contract, and the rules that decide a usage invoice are often not in the order form at all. In our review of 64 usage-based pricing pages, 92% didn't say what happens to credits on a mid-cycle plan change and 72% didn't say what happens to unused included usage at period end. If your contract doesn't say, your billing system, or whoever ran the calculation, decided. The customer is asking what was decided.

A clear answer tends to settle it. A slow or partial one tends to delay payment on the whole invoice, not just the part in question.

The five lines a reply should contain

Then answer each rule they asked about in one sentence: the clause that sets it, or, if the contract is silent, the treatment you applied. If a plan changed during the period, say how the balance was carried across it and from what date.

A template reply

Replace everything in square brackets. Delete any line that doesn't apply.

Subject: Re: Invoice [number] for [period]: usage trace

Hello [name],

Thanks for checking invoice [number] against your order form. Here is the calculation behind [amount], by line.

1. Opening balance: [units] credits. This is [units] unused at the end of [previous period], capped at [cap]% of [the commit / the remaining balance], under [clause].
2. Usage counted: [units] units from [start] to [end], cut off at [time and time zone]. [Failed requests / retries / late events] are [counted / excluded] under [clause / our standard practice]: [units] were excluded.
3. Drawn: [units] from rolled-over credits, then [units] from this period's [units] included credits.
4. Rolled over: [units] carry into [next period], capped at [cap]% of [basis]. They expire on [date].
5. Overage: [units] units. Tier 1, [units] × [rate] = [amount]. Tier 2, [units] × [rate] = [amount]. Tiers [count across the period / reset each month]. Total [amount].

On the points you raised:
- [Rule]: [the clause, or the treatment we applied where the order form doesn't say].
- [Plan change]: the unused balance of [units] was [carried into / reset at] the new plan on [date].

[If the numbers above differ from the invoice: We've found a difference of [amount] and will issue a [credit note / corrected invoice] by [date].]

We're happy to put these rules into your order form at renewal so future invoices can be checked the same way.

[Name]
[Title], [Company]

What producing it takes

From a spreadsheet

Someone rebuilds the period by hand. They find the order form and every amendment, pull usage with the right cutoff, and replay the balance through earlier periods, because this period's opening balance depends on all of them. Then they have to work out which rule the spreadsheet applied where the contract is silent, which may not be written down anywhere. How long that takes depends on how many periods and amendments the balance runs through. It also has to be done again for the next customer who asks.

From a per-line ledger

If each invoice line is stored with its inputs (the usage counted, the credits it drew, the rollover lot and its expiry, the tier and rate) and the clause that set each one, the reply is an export, not an investigation. The rules the contract doesn't state are recorded once, as decisions, so every customer gets the same answer.