Metering & data
Tracing an Invoice Line Back to the Work Behind It
By the Orvlin team · · 2 min read
Invoice usage audit trail: what to decide
Support receives a simple question: why is this line $417? If answering requires asking three engineers for screenshots, the billing system is missing a practical control. The calculation should be reproducible from saved records.
Keep the raw quantity, normalized unit, included allowance, applicable rate and rounding decision. For tiered prices, preserve the allocation across bands. Contract overrides and corrections should be identifiable without searching email threads.
Follow one account through the calculation
A $40 line could mean 4,000 requests at one cent, or 5,000 requests less a 1,000-request allowance. Both produce the same amount but imply different customer expectations. Showing the allowance separately makes the second calculation understandable.
Check this before launch
An audit trail should not expose sensitive request contents. Event IDs, timestamps and quantities usually explain a charge without publishing customer payloads. Provide deeper access only through a controlled investigation.
Steps to take next
- Save the price version used for each charge.
- Retain references to contributing usage records.
- Make allowances and credits visible in the calculation.
- Practice answering a dispute from the saved records alone.
Frequently asked questions
- Do customers need every raw event on an invoice?
- Usually not. Keep the invoice concise, and provide a drill-down or export with the supporting quantities and references when needed.