Fixing Historical Usage Without Erasing the Evidence

Correcting historical usage: what to decide

Someone discovers a quantity was multiplied by 1,000 twice. Editing a database row seems quick, until support asks why yesterday’s export no longer matches today’s invoice. A correction needs to explain the journey, not just the final total.

Distinguish raw measurements, rated quantities and finalized charges. Each layer needs its own correction procedure. Recomputing a draft may be straightforward; correcting an issued invoice generally requires a separate financial document or adjustment.

An illustrative case

A job was recorded as 8,000 units instead of eight. A correction references the original job and removes 7,992 units from the applicable aggregate. If the invoice is already issued, finance reviews the corresponding credit rather than treating the repaired aggregate as proof that the original invoice never existed.

The important caveat

Avoid unbounded replay. A backfill that mixes corrected records with already-accepted originals can introduce new duplicates. State whether the operation replaces a dataset or appends adjustments before running it.

Review these decisions

• Record a correction reason and approving person.
• Preview affected accounts and invoice periods.
• Reconcile old totals, adjustments and new totals.
• Keep a customer-readable explanation for material changes.