Audit carrier surcharges without a black box

An invoice often shows only a short label and amount. Reconstruction needs more: type, trigger, calculation basis, rate or fixed amount, effective period, affected services and contract exceptions.

This structure prevents the audit from reacting to labels alone. Two carriers can name the same economic event differently, while one label may calculate differently by service. The internal rule object translates carrier language into explicit versioned logic.

UPS describes index-based fuel surcharges with defined adjustment cycles, and DPD also publishes variable energy and fuel components. The audit needs the published percentage, index lag and effective date.

Next comes the basis: transport charge only, selected accessorials or a wider sum? Public carrier material and the negotiated agreement may complement each other. Contract-specific rules take precedence over a generic assumption.

Additional handling, address correction, oversize and non-conveyable charges need a triggering event. The audit searches for a measurement, scan, timestamp or status code. If it is absent, the line remains open. If it exists, threshold and amount are reconstructed.

Keep human-readable explanations separate from machine-readable events. Free text can support review but should not replace a deterministic trigger. Evidence must show which structured value activated the fee.

Peak, demand and emergency fees may apply only in specific windows or lanes. Remote-area and island fees rely on published area tables. A dated version is essential; later updates must not be projected backwards.

International shipments add currency conversion. Store original currency, exchange rate, source and applied date separately so currency movement is not mislabeled as a rate variance.

Small differences often come from rounding per line, per fee, per invoice or after tax. An audit that rounds only at the end can manufacture thousands of cent-level variances. Version the rounding rule just like the percentage.

Use tolerance for technical residues, not as a blanket filter for small amounts. Many small true variances can become material at volume. Technical tolerance and economic threshold are different decisions.

A good sequence reduces false findings: service and effective date first, then area or weight, trigger and calculation basis, followed by rate, rounding and tax. Only after every layer is reproduced should expected and billed amounts be compared.

The result should not merely say wrong. It should expose rule version, inputs, calculation, original line and linked source so a third party can inspect the difference. That turns rate logic into an auditable system rather than another black box.