Parcel invoice audit software checks what a carrier billed you against what you actually shipped, so overcharges and billing errors get caught instead of quietly paid. The real distinction between audit products is timing. Most parcel audit tools, including Reveel, reconstruct what a shipment should have cost after the carrier invoice arrives. Shipium's Always-On Audit validates the shipment before that invoice is ever generated, starting at the moment a carrier and rate are selected.
This article compares how each product works, what data each one checks against, and which approach fits which kind of shipping operation.
Quick comparison:
- Reveel audits invoices after carriers issue them, reconstructing expected cost from your contract and shipment records. It runs as a standalone platform alongside whatever system generates your labels.
- Always-On Audit validates a shipment at every stage of its lifecycle, rating, labeling, shipping, invoicing, and billing, starting before the label prints. It runs inside Shipium's execution platform, so the audit reference point is the exact rate Shipium quoted at carrier selection.
- The right fit depends on whether your execution platform already validates shipments upstream, whether you need peer benchmarking against other shippers, and whether billing has to flow through to your own customers, which matters most for 3PLs.
What Is Parcel Invoice Audit Software?
Parcel invoice audit software is a system that reviews carrier invoices and flags charges that don't match the contracted rate, the service actually used, or the shipment that was actually sent. It catches issues like misapplied surcharges, incorrect dimensional weight charges, duplicate billing, and charges for voided or undelivered shipments.
Carrier invoices are complicated by design. A single line item can combine a base rate, a fuel surcharge, a delivery area surcharge, and a residential or address-correction fee, each pulled from a separate rate table that carriers update on their own schedule. That complexity is why invoice audit tends to run as a standing operational function rather than a one-time cleanup project for shippers with meaningful volume, and manual review doesn't scale against that volume, which is why audit almost always means software rather than a person working through a spreadsheet.
Audit products differ mainly in what they check the invoice against. A post-shipment audit reconstructs an expected cost from your carrier contract and tracking data after the invoice arrives, then disputes whatever doesn't match. A pre-shipment audit compares the invoice against a rate the platform itself already quoted and recorded at the moment it selected the carrier, before the label ever printed. Reveel is built on the first model. Always-On Audit is built on the second.
How Reveel's Audit Product Works
Reveel's audit product Parcel Audit & Recovery ingests carrier invoices for UPS, FedEx, DHL, and other US carriers. It then checks them against your carrier agreement, and automates the process of filing claims for guaranteed service refunds and billing credits the carrier owes you.
Reveel's audit sits inside a broader analytics layer. The platform also includes Peer Index, a benchmarking score that compares your shipping profile against other shippers, and Reveel IQ, an AI analyst for querying shipment and invoice data in plain English. Reveel doesn't generate labels or select carriers itself, so its reference point for an audit is a contract and shipment records it has after the shipment already happened.
That architecture makes Reveel a fit for shippers whose execution platform, whether that's a carrier's own system has no invoice-checking capability of its own. It adds a dedicated audit and benchmarking layer without requiring a change to how labels actually get generated. It also means Reveel is reconstructing, after the fact, a rate that a different system already decided.
How Shipium's Always-On Audit Works
Always-On Audit is Shipium's continuous validation system across the full shipment lifecycle: rate, label, ship, invoice, and bill. Instead of waiting for an invoice to reconstruct what should have happened, Shipium validates the shipment at each point where a financial fact gets created, starting with the rate quote itself.
The model works in five stages, and each one writes to the same record.
Rate: a quote gets checked against your contract and discount terms before anything ships, catching a missed discount or a mispriced zone early. Label: once a carrier generates a label, Shipium compares it against that original quote and can pull the shipment aside or switch it to a different service if the price or eligibility no longer holds up. Ship: as the package moves, the system checks the scan record, weight, and dimensions against what was declared, and can start a service-failure claim the moment a delivery commitment slips. Invoice: when the carrier's bill lands, Shipium matches it line by line against everything already on record, clearing charges that check out and opening a dispute, with the cause attached, for the ones that don't. Bill: for operators who charge their own customers for shipping, that same expected-rate data becomes the basis for the customer invoice, checked against the same standard as the carrier charge.
The reason Shipium can validate upstream rather than reconstructing after the fact is that the platform is the system of record for the shipping decision itself. Rating, label, scan, and invoice data are joined by a single shipment ID in one financial ledger, so there's no separate reconciliation dataset to build or maintain. Every dispute and discrepancy feeds back into the rating engine and contract model, so the same error gets corrected at its source instead of resurfacing on the next invoice.
This model has produced three measurable outcomes for early customers: more than 99% of invoice lines get auto-approved without human review, the typical dispute cycle runs in days instead of the weeks or months a batch invoice audit takes, and finance gets real-time visibility into shipped-but-not-yet-billed accruals rather than working from month-old numbers.
The underlying record is built to be specific enough to act on. Every expected cost traces back to the rating call that created it: the contract version, a snapshot ID, and a timestamp to the second. Against that record, Shipium runs twelve deterministic audits plus nine detection models, configured per customer and per carrier. That combination catches a category of error a contract-based audit tends to miss: a shipment billed at the correct price for the wrong service, where the charge itself looks fine but the service level doesn't match what was actually used.
Shipium's CEO, Jason Murray, and SVP of AI Product and Engineering, Penny Allen, described the underlying mechanism to FreightWaves as a "digital twin," an internal model of what a shipment's cost and physical specifications should be, built the moment Shipium rates and routes the package. Because that record starts at rating rather than at invoicing, Allen said the team can trace a discrepancy back to its exact origin, down to the lane, the dimensioner, and the data stream it came from, rather than only knowing that a charge looked wrong. In one early example she described, the system flagged a carrier billing base rates instead of contracted rates within moments of Shipium building that customer's digital twin, and in another, caught a surcharge that a carrier had started applying two days before its stated effective date. Shipium's broader shipping platform has typically delivered a 12% cost reduction for parcel customers, Murray told FreightWaves, while Always-On Audit itself is still early in its rollout.
Within Always-On Audit, Billing Management is where invoice ingestion, reconciliation, and customer billing actually happen. Carrier invoices arrive by API, EDI, SFTP, or file transfer depending on what each carrier supports, and Shipium standardizes them into a single feed validated against pre-shipment data at the line-item level. For 3PLs, the same system applies customer-specific sell rates and attributes every invoice to the right account, so discrepancy detection and customer billing draw from one dataset instead of two.
Prevention vs. Recovery: The Core Difference
The difference between the two products is the reference point each audit checks against, and what happens once a problem turns up. Both check invoices against contract terms, audit weight and dimensional weight charges, model the impact of general rate increases, draft disputes with supporting evidence, and offer a natural-language AI layer for querying shipping data, at a similar level of depth.
Reveel's reference point is a contract and shipment record after the invoice arrives, so it's checking a bill against a reconstruction of what should have happened. That reconstruction is backward-looking, because the platform generating the shipment isn't the platform running the audit.
Always-On Audit's reference point is the rate, label, and shipment data Shipium's own platform already recorded when it made the carrier decision in the first place. Because Shipium is the system that made that original decision, it can correct a discrepancy at its source rather than just dispute it. When modeling shows a different carrier should have been used, Shipium can deploy that change directly in the rules engine, so the next package ships on the corrected decision instead of waiting on a separate project. Carrier modeling also draws on Shipium's pre-integrated carrier network, so adding a new carrier gets priced with real, held rates rather than rates inferred from scanned documents.
Capability Comparison
What This Means for Different Teams
Finance gets one dated, attributable expected cost per shipment, written before the carrier ever bills, so audit findings and month-end accruals reference the same record instead of two separately reconciled numbers.
Transportation gets a recommended carrier shift that becomes a rule in the execution path the next time a similar shipment ships, without needing a separate vendor or project to put it into effect.
3PL operators get customer pricing set at the moment a label is generated, rather than mapped back from invoices afterward, which is the difference between billing customers accurately in real time and reconciling margin loss after the fact.
Which Approach Fits Your Operation?
For most shippers, auditing at the source is the stronger long-term position. A post-shipment audit like Reveel's works from a rate it reconstructs after the fact, and that reconstruction carries two weaknesses: the contract it relies on can drift out of sync with what the agreement actually says, and by the time an error is caught, the shipment that triggered it has already gone out. Recovering the credit still takes a person negotiating with the carrier, and the same error tends to recur until something changes it upstream. Despite this, standalone product like Reveel still makes sense on top of an execution platform with no invoice-checking of its own, especially if peer benchmarking matters to your team.
For a shipper already running or evaluating Shipium for carrier selection and execution, Always-On Audit is the stronger choice. Because Shipium is both the platform that selects the carrier and the platform that audits the invoice, a discrepancy traces back to the exact rating call that created it and gets corrected directly in the rules engine, so the next shipment ships priced correctly instead of just getting refunded after the fact. A separate audit tool would only reconstruct data the platform already generates and validates directly, adding cost without adding accuracy.
