How it runs

First feed to first
recovered dollar —
seven steps.

No rip-and-replace. Volta Orange sits alongside your TMS and AP stack, feeds off the data you already have, and runs a rhythm you can staff to.

Step by step

Each step has an input, an owner, and an output.

Nothing here is a workshop or a strategy deck. Every step produces an artifact the next step consumes.

  1. 01

    Week 1

    Connect carriers, contracts, and sources

    Carrier EDI, invoice inboxes, TMS, and container event providers are plugged in. Rate agreements and accessorial schedules load as the source of truth.

    Input
    Carrier credentials, rate PDFs, TMS access
    Output
    Live feeds, contracts on file
    Owner
    Volta Orange + your ops lead
  2. 02

    Week 2

    Backfill 30–90 days of history

    Historical invoices are re-run against contracts and container events. First overcharge report and D&D exposure map lands, with what's still disputable clearly marked.

    Input
    Recent invoices and event history
    Output
    Backfill audit, disputable window
    Owner
    Volta Orange
  3. 03

    Week 2–3

    Reconcile every line to a contract and a container

    Charges are normalized, tied to a shipment and equipment, and compared to the rate on file. Fuel, FX, and accessorials are checked against the schedule that applies.

    Input
    Normalized charge lines + contracts
    Output
    Line-level match with variance flags
    Owner
    System
  4. 04

    Week 3

    Flag overcharges and D&D exposure

    Continuous checks surface rate variances, duplicate accessorials, missing credits, and containers past 50% of free time — before AP clears the invoice.

    Input
    Live invoices + container events
    Output
    Exception queue with dollar amounts
    Owner
    System
  5. 05

    Week 3–4

    Route exceptions to owners

    Ops picks up detention risk. Finance picks up billing variances. Every flag has an assignee, an SLA, and the evidence pack the carrier can't hand-wave.

    Input
    Exception queue
    Output
    Assigned claims with SLAs
    Owner
    Ops + finance leads
  6. 06

    Week 4+

    Work claims to close

    Disputes are filed with the BOL, rate sheet, and event trail attached. Carrier replies, credit memos, and status changes stay on the original claim — not in inboxes.

    Input
    Assigned claims
    Output
    Filed disputes, carrier responses, credit memos
    Owner
    Ops or finance owner
  7. 07

    Monthly

    Report recoveries and exposure

    Recovery, open exposure, and dispute aging land in one view finance and ops both trust — and export cleanly to the report your auditor will ask for.

    Input
    Closed claims + open queue
    Output
    Recovery ledger, exposure report, auditor export
    Owner
    Finance

Book a walkthrough

Walk the seven steps against your carrier mix.

A 45-minute session with your ops and finance leads. We map your carriers, rate agreements, and current dispute flow — and show exactly where each step plugs in.