Logistics Transaction Verification

Logistics invoices are complex. Your operations shouldn't be.

Freight and warehouse billing often leave contract, physical activity, invoice, and payment evidence in separate systems. We link available source records into transaction context for downstream review.

⚠

The Problem

Your carrier invoices can arrive before their supporting evidence is connected.

Card transactions arrive from your bank or card program — merchant, amount, date — with no line items, no commodity codes, no PO reference. ACH and wire payments carry even less: a routing number, an amount, and a memo field that someone typed. Carrier invoices arrive as EDI 210 transactions, carrier-portal PDFs, and TMS exports with no common schema.

The result is that your finance team closes month-end by matching payments to purchases by hand. AP automation helps with invoice routing. Rate comparison against contracted terms is still done in Excel, when it's done at all. Duplicate invoices slip through because the dedup key is a PRO number in an email, not an indexed record.

Weight discrepancies require comparing the billed weight on the carrier invoice to the actual weight at origin. Without a link between WMS and AP records, that comparison can be manual and intermittent.

The Viacle Solution

Source-aware transaction context for freight events.

Configured connectors can ingest available EDI X12 210/214 invoices, carrier events, TMS exports, and document records, then link them in a structured Purchase Object. Fields and comparisons depend on the connected sources and configured rules.

EDI X12 210 ingest — standard freight invoice evidence can be mapped for a configured connection
Contracted rate comparison — configured CWT, zone-matrix, lane-mileage, and flat-rate terms can be compared with linked invoices
Weight discrepancy review — linked BOL and billed-weight evidence can support configured variance checks
Duplicate PRO review — available invoice history and PRO references can support duplicate checks
Accessorial review — available detention, liftgate, residential, and fuel-surcharge terms can be compared under configured rules
Carrier context — source records, comparisons, statuses, and follow-up references remain linked for downstream systems
Review-package export — configured downstream workflows can receive linked source references and calculated comparisons

For 3PL warehouses & fulfillment providers

Link available billable activity and contract evidence.

Multi-client 3PL warehouses may hold receiving, storage, pick, pack, and accessorial activity in different systems. We can link available WMS activity, contract terms, and invoice evidence into source-aware context for downstream review.

Available WMS events, contract terms, and accessorial activity linked to invoice evidence in one record
Available receiving, storage, pick, pack, and special-handling activity available for configured review
Configured rate-card terms — per case, pallet, pick, square foot, and storage threshold — compared with linked billed lines
Linked WMS activity, applicable contract terms, charge comparisons, and variance references for downstream workflows

Example API Response

Freight purchase object — EDI 210 invoice with audit result

JSON Response — freight invoice with accessorial dispute flag

{
  "object": "purchase",
  "id": "pur_vc_4fa82e91",
  "status": "completed",
  "merchant": {
    "id": "mer_apex_freight_007",
    "name": "Apex Freight Services",
    "tin": "47-2938410",
    "tin_verified": true
  },
  "items": [
    {
      "name": "LTL Base Rate — Chicago to Dallas, 480 lbs",
      "commodity_code": "78101700",
      "price": 412.00,
      "contracted_rate": 412.00,
      "variance": 0
    },
    {
      "name": "Residential Delivery Accessorial",
      "commodity_code": "78101700",
      "price": 155.48,
      "contracted_rate": 0,
      "variance": 155.48,
      "dispute_flag": "accessorial_not_in_contract"
    }
  ],
  "amounts": { "subtotal": 567.48, "disputed_amount": 155.48, "currency": "USD" },
  "freight_metadata": {
    "pro_number": "PRO-4829301",
    "bol_number": "BOL-2026-0812",
    "carrier_scac": "APEX",
    "audit_result": "disputed"
  },
  "dispute": {
    "id": "dsp_7c2f1a",
    "status": "open",
    "reason": "Freight invoice includes accessorial charges not in contracted rate"
  }
}

What you can build

Capabilities unlocked by freight purchase objects

Configured carrier-invoice comparisons using available source evidence

Rate-vs-billed comparison for CWT, zone-matrix, lane-mileage, and flat-rate carrier contracts

Duplicate PRO review using available invoice history and references

Weight comparison using linked BOL and carrier-billed evidence

Accessorial review using available carrier-contract terms

Carrier context with source references, comparisons, and statuses

Configured GL fields returned to downstream accounting workflows

Linked source references and variance comparisons for dispute workflows

Connected carriers and platforms

Freight connectors included

Connector availability, source coverage, and partner requirements vary. Review the current integrations catalog for supported freight sources.

See what's hiding in your logistics invoices.

Connect your carriers or warehouse activity and upload the applicable rate contracts. We'll show you where billed and expected charges diverge before you commit to anything.

Book a logistics demo Read the API docs →