Shipment Intent Validation | Carrier Billing Intelligence | Recovery Workflow

Carrier billing
errors are systemic.
Prove them.

TRACIUM compares shipment records against carrier invoices to identify billing discrepancies, preserve supporting evidence, explain why they matter, and support controlled dispute and recovery workflows.

41
Active Audit Rules
2
Independent Data Feeds
0
AI-Generated Findings
TRACIUM ATLAS
GOVERNED AI INTELLIGENCE
SHIPMENT INTENT DETERMINISTIC TRUTH
ATLAS
EXPLAIN INVESTIGATE ROOT CAUSE RECOMMEND
TRACIUM establishes truth. ATLAS interprets governed truth.
Deterministic Audit Findings
Every finding is a provable, evidence-backed condition between shipment intent and carrier claim — not a flag, not a model output.
Backend-First Financial Truth
All financial surfaces derive from canonical backend state. No UI-side inference. No parallel computation.
Recoverable Exposure Control
Disputes are generated from canonical findings and tracked through full lifecycle to confirmed resolution.
Zero Fabrication Architecture
No invented linkages. No synthetic conclusions. If evidence is incomplete, the system reports it — not a finding.
Enterprise Workflow Discipline
Full audit trails. Review before sending. Lifecycle state from OPEN through RESOLVED — nothing deleted, everything traceable.
The Problem

Carrier billing discrepancies are difficult to prove without shipment evidence.

Carrier invoices and operational shipment records are created by separate systems for different purposes. When their service, weight, payer, accessorial, account, or value data does not align, the discrepancy can be difficult to detect, explain, and dispute without a structured evidence layer.

Across high-volume transportation operations, individually small discrepancies can accumulate across carriers, services, invoices, and billing periods. The challenge is not merely detecting an unusual charge — it is proving the discrepancy using the original shipment and carrier records.

Spend reporting shows what was billed.
TRACIUM investigates whether the carrier claim aligns with shipment evidence.
No Systematic Invoice Validation
Root Cause

Operational shipment records and carrier invoice data are often reviewed in separate systems. Without a governed comparison layer, discrepancies can remain difficult to identify and explain at scale.

Dispute Processes That Don't Scale
Operational Gap

When errors are found, disputes live in email threads, spreadsheets, and manual follow-up. No audit trail. No status visibility. No structured measurement of what was recovered.

Dashboards Show Spend — Not Errors
Tool Gap

BI and spend analytics platforms are primarily designed for reporting and visibility. TRACIUM adds a governed validation layer linking shipment evidence, carrier charges, configured rules, and resulting findings.

Leakage That Compounds Silently
Financial Exposure

Manual review becomes difficult to apply consistently across high-volume invoice populations. Duplicate billing, weight differences, service mismatches, and unsupported charges may require systematic comparison and investigation.

How It Works

Ingest. Audit. Dispute. Recover.

TRACIUM is a structured investigation and recovery platform. Each stage produces a governed output for the next: source data becomes linked evidence, linked evidence becomes findings, and approved findings can become reviewed dispute drafts and recovery records.

01
Load two independent data feeds
UPLOAD requires two independent data feeds loaded separately. Feed one: shipment and delivery records exported from SAP, ERP, or TMS — this is the SHIPMENT INTENT baseline. Feed two: invoice and charge data from carrier billing sources — this is the CARRIER CLAIM. TRACIUM links these two feeds deterministically using shipment number, delivery number, tracking number, PRO number, or carrier reference. Every row is reported — including what linked, what did not, and why. Unlinked rows produce no findings and generate no disputes.
UPLOAD — Dual-Feed Ingestion + Deterministic Linkage
02
Execute deterministic audit
BLACKLIGHT runs the audit engine against linked shipment-invoice pairs. Overcharge thresholds, duplicate detection, weight comparison, service level validation — each rule fires against evidence. No estimates. No model predictions. Canonical findings only, each with grounded evidence, lifecycle state, and financial impact where deterministically supported.
BLACKLIGHT — Audit Engine
03
Investigate findings and surface exposure
Each finding shows the rule that fired, the severity, the full evidence chain, and any grounded financial impact or review requirement. FINANCIALS surfaces invoice-level financial truth — every row, every variance. TRACIUM ATLAS provides investigation assistance, pattern discovery, and root-cause guidance grounded in deterministic truth. It is a governed intelligence layer, not an audit authority.
BLACKLIGHT + FINANCIALS + TRACIUM ATLAS
04
Generate and review disputes
CLAIMFORGE converts OPEN findings into structured, carrier-facing dispute drafts — pre-populated with finding evidence, raw shipment identifiers, and discrepancy details. Individual and batch dispute workflows are supported, with carrier-configured recipients, CC/BCC routing, evidence packages, and reviewed email handoff. No carrier communication is treated as sent without explicit user action or confirmed provider success.
CLAIMFORGE — Recovery Pipeline
05
Track recovery through to resolution
Disputes move through DRAFT → SENT → RESOLVED. Status is tracked continuously and reflects backend truth. Recovery amounts are confirmed outcomes only — never projected. Full finding and dispute lifecycle history is always visible and never deleted.
CLAIMFORGE — Lifecycle Tracking
Platform Modules

One platform. From shipment evidence to recovery intelligence.

INSIGHTS
Transportation Intelligence Center
INSIGHTS is TRACIUM's transportation intelligence homepage — a read-only portfolio surface across the governed Platform Scope. It surfaces total shipments, total billed transportation spend, canonical finding volume, disputed and resolved activity, finding distribution, carrier exposure, financial exposure, and trend and driver analysis.
INSIGHTS consumes backend-owned canonical analytics. It does not create findings or replace operational workflows.
BLACKLIGHT
Canonical Audit Engine & Investigation Surface
BLACKLIGHT is the system spine. It executes deterministic rules against linked shipment-invoice pairs, produces canonical findings with lifecycle states and financial impact where deterministically supported, and provides a full investigation interface. Every finding shows the rule, evidence, operational context, Source Traceability, and any grounded financial impact or review requirement. Findings include backend-owned Rule Explainability, deterministic Finding Confidence, recoverability classification, Source Traceability, and exportable evidence. It is the sole source of audit truth in TRACIUM — everything else derives from it.
Findings lifecycle: OPEN → DISPUTED → DISMISSED → RESOLVED. Nothing deleted. Every transition tracked.
CLAIMFORGE
Recovery Pipeline & Carrier-Facing Dispute Workflow
CLAIMFORGE converts OPEN audit findings into structured, evidence-grounded carrier disputes. Every dispute derives from a canonical BLACKLIGHT finding and consumes Rule Explainability, Finding Confidence, and configured recipient routing. Payloads are pre-populated and reviewed before sending. Individual and batch dispute workflows are supported, with carrier-configured recipients, CC/BCC routing, evidence packages, and reviewed email handoff. No carrier communication is treated as sent without explicit user action or confirmed provider success. Lifecycle state — DRAFT, SENT, RESOLVED — is tracked continuously and drives all financial recovery reporting.
CLAIMFORGE is not a reporting layer. It is a recovery execution system with direct carrier-facing output.
FINANCIALS
Invoice & Financial Intelligence
FINANCIALS displays raw invoice-level data exactly as ingested — every row, every variance, every tag. The Exposure Heatmap visualizes audit yield by carrier and rule type. Top discrepancies surface the highest-value individual recovery targets. No aggregation conceals the truth. All figures are backend-driven consequences of canonical audit findings, not computed by the UI.
Finance teams use FINANCIALS to validate disputed amounts against finding evidence and track recovery for period close.
OPERATIONS
Shipment Operational Intelligence
OPERATIONS provides the shipment-side baseline that the audit engine compares against carrier invoices. Shipment records carry carrier assignments, service levels, expected costs, route data, package weights, and risk scores. High-risk shipments are flagged based on billed-to-expected divergence. This is the SHIPMENT INTENT side of every finding — the shipment-intent baseline that makes audit possible.
Logistics teams review OPERATIONS to validate that findings reflect real shipment-side discrepancies before authorizing disputes.
UPLOAD
Governed Dual-Feed Ingestion
UPLOAD is the required data foundation for every audit TRACIUM runs. It accepts two independent feeds: shipment and delivery records from ERP, SAP, or TMS systems, and invoice and charge data from carrier billing sources. The feeds are loaded separately, linked deterministically by shipment number, delivery number, tracking number, PRO number, or carrier reference, and validated before audit execution.
TRACIUM compares SHIPMENT INTENT against CARRIER CLAIM. Both feeds must be present before audit execution. Audit does not run on a single data source. Unlinked rows are reported honestly and produce no findings.
TRACIUM ATLAS
Governed AI Intelligence Across TRACIUM
TRACIUM proves what happened. ATLAS helps you understand why — and what to do next. ATLAS works across governed TRACIUM contexts to help investigate findings, understand evidence, identify recurring patterns, explore likely root causes, evaluate portfolio drivers, and determine informed next steps.
ATLAS does not generate audit findings, override BLACKLIGHT, rewrite canonical financial truth, autonomously mutate lifecycle, or autonomously send disputes. Human review remains explicit where required.
Why TRACIUM Is Different

Shipment intent validation.
A governed evidence layer for carrier billing investigation.

Many freight-audit platforms validate invoices using contracts, rates, shipment records, and business rules. TRACIUM is specifically designed around a governed comparison between shipment-side operational evidence and carrier billing claims, with explainable findings, source traceability, and controlled dispute workflows.

Common Invoice-Centred Audit Workflow
Often centres investigation on the invoice, rate, contract, or payment record
Shipment context may be available without being presented as a governed intent baseline
Analysts may need to reconstruct supporting evidence across multiple systems
The relationship between source fields, rule logic, findings, and disputes may not be visible in one workflow
Customer-specific configuration may depend on vendor implementation or managed services
Dispute and recovery activity may remain distributed across software, service teams, email, and external workflows
Public product materials provide limited detail about field-level evidence lineage and rule governance
TRACIUM
Uses shipment-side operational evidence as the governed intent baseline for comparison with carrier billing claims
Produces explainable, evidence-backed findings with visible rule logic, linkage, and supporting fields
Connects discrepancy, root cause, dispute workflow, and recovery operations inside one platform
Validates service, payer, accessorial, HazMat, declared value, insurance, and billing consistency claims
CLAIMFORGE supports human review, dispute drafting, controlled transmission, response tracking, and recovery lifecycle evidence
If evidence is insufficient, the platform preserves the gap instead of generating a finding
Confirmed recovery and earned fee visibility remain separated from open exposure and workflow value
Activated Audit Rules

What the audit engine detects.

TRACIUM validates carrier billing claims against shipment intent, execution evidence, and deterministic audit rules. These are the currently activated rule families used to identify evidence-based recovery and review conditions.

ACCESSORIAL_FEE_INVALID
Accessorial Fee Invalid
Detects accessorial charges that appear on the carrier invoice but are not supported by shipment characteristics, configured business rules, or expected service conditions.
ACCOUNT_NUMBER_MISMATCH
Account Number Mismatch
Identifies invoices billed to a carrier account that does not match the expected account, payer setup, or shipment billing responsibility.
ADDRESS_CORRECTION_INVALID
Address Correction Invalid
Flags address correction fees where shipment data does not support a carrier-applied correction charge or where the correction appears inconsistent with the submitted address.
COMMODITY_CODE_INVALID
Commodity Code Invalid
Validates explicit commodity codes against the active governed structural and vocabulary configuration and identifies values that do not satisfy the configured deterministic requirements.
COMMODITY_CODE_MISSING
Commodity Code Missing
Identifies international shipment commodity lines where required commodity-code evidence is absent.
COUNTRY_OF_ORIGIN_INVALID
Country of Origin Invalid
Validates explicit country-of-origin values against the active governed country vocabulary and identifies structurally unsupported values.
COUNTRY_OF_ORIGIN_MISSING
Country of Origin Missing
Identifies international shipment commodity lines where required country-of-origin evidence is absent.
CUSTOMS_DOCUMENTATION_MISSING
Customs Documentation Missing
Identifies international shipments where required customs-documentation evidence is not present in the mapped operational data.
CUSTOMS_LINE_VALUE_MISSING
Customs Line Value Missing
Identifies persisted shipment commodity lines where required customs line-value evidence is absent.
DECLARED_VALUE_MISMATCH
Declared Value Mismatch
Compares declared value submitted at shipment time against the declared value billed or used by the carrier to identify mismatched insurance or value-based charges.
DECLARED_VALUE_MISSING
Declared Value Missing
Detects shipments where declared value should be present based on shipment data or business rules but is missing from the billing or shipment evidence.
DELIVERY_AREA_SURCHARGE_INVALID
Delivery Area Surcharge Invalid
Validates delivery area surcharge charges against shipment destination data and expected surcharge applicability.
DRY_ICE_FEE_INVALID
Dry Ice Fee Invalid
Identifies dry ice fees that are billed without supporting shipment-side dry ice indicators, shipment attributes, or configured rule evidence.
DUPLICATE_FUEL_CHARGE
Duplicate Fuel Charge
Detects multiple explicit fuel charge lines on the same carrier invoice using persisted invoice charge-line evidence while avoiding duplicate-invoice double counting.
DUPLICATE_INVOICE
Duplicate Invoice
Detects duplicate carrier invoices or duplicate invoice-line billing patterns using deterministic invoice identifiers, shipment references, and charge evidence.
EXPORTER_OF_RECORD_MISSING
Exporter of Record Missing
Identifies international shipments where required exporter-of-record evidence is absent from the mapped shipment data.
EXTENDED_DELIVERY_AREA_INVALID
Extended Delivery Area Invalid
Validates extended delivery area surcharge charges against destination data and expected extended-area applicability.
FUEL_ACCESSORIAL_MISMATCH
Fuel Accessorial Mismatch
Validates explicit fuel-to-accessorial charge relationships against governed accessorial eligibility configuration and flags unsupported fuel application to ineligible charge lines.
FUEL_INDEX_DATE_MISMATCH
Fuel Index Date Mismatch
Compares the explicit billed fuel index date against the deterministically applicable configured fuel period and identifies unsupported period mismatches.
FUEL_INELIGIBLE_SERVICE
Fuel Ineligible Service
Identifies fuel charges billed against a carrier and service combination that is not eligible under the active governed service configuration for the shipment date.
FUEL_PERCENTAGE_MISMATCH
Fuel Percentage Mismatch
Compares deterministic billed fuel percentage evidence against the applicable governed fuel schedule and identifies differences outside the configured tolerance.
FUEL_SURCHARGE_MISSING
Fuel Surcharge Missing
Identifies shipments where exact carrier-and-service configuration establishes that fuel is expected but deterministic invoice fuel evidence is absent.
FUEL_SURCHARGE_UNEXPECTED
Fuel Surcharge Unexpected
Identifies explicit carrier fuel charges where shipment-side authorization or eligibility evidence does not support the billed fuel surcharge.
HAZMAT_CLASS_MISMATCH
Hazmat Class Mismatch
Compares explicit shipment-side hazardous material class against explicit invoice-side hazardous material class and flags mismatches only when both sides are present and conflict.
HAZMAT_DOCUMENTATION_FEE_INVALID
Hazmat Documentation Fee Invalid
Identifies hazardous material documentation fees that are billed without supporting shipment-side hazardous material documentation requirements or configured evidence.
HAZMAT_FEE_MISSING
Hazmat Fee Missing
Detects shipments marked as hazardous material where an expected carrier hazardous material fee is missing from the billing record.
HAZMAT_FEE_UNEXPECTED
Hazmat Fee Unexpected
Flags hazardous material fees billed on invoices where shipment data does not indicate hazardous material handling or authorization.
IMPORTER_OF_RECORD_MISSING
Importer of Record Missing
Identifies international shipments where required importer-of-record evidence is absent from the mapped shipment data.
INCOTERMS_INVALID
Incoterms Invalid
Validates explicit Incoterms values structurally against the active governed vocabulary without inferring legal responsibility, liability, or contractual interpretation.
INCOTERMS_MISSING
Incoterms Missing
Identifies international shipments where required Incoterms evidence is absent from the mapped shipment data.
INSURANCE_VARIANCE
Insurance Variance
Compares shipment value, declared value, and carrier insurance-related billing to detect unsupported or mismatched insurance charges.
LIFTGATE_INVALID
Liftgate Invalid
Identifies liftgate charges that are billed without supporting shipment delivery requirements, location indicators, or service evidence.
LIMITED_QUANTITY_MISBILLING
Limited Quantity Misbilling
Detects billing inconsistencies involving limited quantity shipments where the invoice charge treatment does not align with shipment-side limited quantity indicators.
LITHIUM_BATTERY_FEE_INVALID
Lithium Battery Fee Invalid
Flags lithium battery fees that are billed without supporting shipment-side lithium battery indicators or configured rule evidence.
OVERCHARGE
Overcharge
Detects invoice charges that exceed expected charge logic based on available shipment, service, payer, and billing evidence.
RESIDENTIAL_SURCHARGE_INVALID
Residential Surcharge Invalid
Validates residential surcharge charges against destination classification, shipment data, and expected residential applicability.
SERVICE_LEVEL_MISMATCH
Service Level Mismatch
Compares the service level shipped or requested against the service level billed by the carrier to detect mismatched service claims.
THIRD_PARTY_BILLING_ERROR
Third Party Billing
Identifies third-party billing charges or payer logic that does not align with shipment billing responsibility, account configuration, or expected payer evidence.
WEEKEND_DELIVERY_MISMATCH
Weekend Delivery Mismatch
Flags weekend delivery charges or service claims that are inconsistent with shipment dates, delivery expectations, or billed service details.
WEIGHT_MISMATCH
Weight Mismatch
Compares shipment-side weight evidence against carrier invoice weight claims to detect weight-based billing discrepancies.
WRONG_PAYER
Wrong Payer
Detects invoices or charges assigned to the wrong billing party based on shipment responsibility, account mapping, and payer configuration.
Analytics

Transportation intelligence built from canonical truth.

TRACIUM analytics are never invented in the reporting layer. Every number shown is downstream of ingested source data, deterministic linkage, deterministic findings, dispute lifecycle, and confirmed recovery — never a UI-side estimate.

INSIGHTS aggregates this governed portfolio intelligence into a single transportation intelligence surface. FINANCIALS preserves invoice-level truth beneath it. BLACKLIGHT owns the findings themselves, and CLAIMFORGE owns the dispute and recovery workflow that follows. TRACIUM ATLAS may interpret this governed context to help explain patterns and drivers — it does not invent metrics or recompute financial truth independently.

MetricOwner & Purpose
SHIPMENT VOLUMETotal shipments in the governed Platform Scope, sourced from OPERATIONS.
CARRIER SPENDTotal billed transportation spend, sourced from invoice-level FINANCIALS data.
FINDING EXPOSUREFinancial impact of canonical findings, owned by BLACKLIGHT.
DISPUTED EXPOSUREValue currently in active dispute, tracked through CLAIMFORGE lifecycle state.
RESOLVED / CONFIRMED RECOVERYConfirmed recovery outcomes only — never projected or estimated.
CARRIER / RULE CONCENTRATIONDistribution of findings and exposure by carrier and rule, surfaced in INSIGHTS.
Who It's For

Built for the teams closest to the evidence.

🚚
Transportation / Logistics
Investigate carrier billing against actual shipment execution and intent, using OPERATIONS as the audit baseline.
💰
Finance / Accounts Payable
Validate invoice discrepancies, financial exposure, disputes, and confirmed recovery against invoice-level FINANCIALS truth.
🔍
Internal Audit / Controls
Trace findings from source evidence through deterministic rule logic and full lifecycle history.
📊
Supply Chain Leadership
Use INSIGHTS for portfolio-level transportation intelligence — carrier concentration, exposure, and recovery visibility.
🔗
ERP / TMS / SAP Teams
Identify operational and data patterns that may be driving recurring transportation discrepancies.
🤝
Freight Audit / Consulting Partners
Use TRACIUM as a governed evidence and recovery platform within customer engagements.
Governance

AI can interpret the evidence. It cannot rewrite it.

TRACIUM's architecture keeps deterministic truth and AI-assisted interpretation strictly separate. Deterministic rules own findings. Canonical backend state owns financial truth. Source identifiers remain traceable end to end, and insufficient evidence is reported as insufficient evidence — never inferred.

TRACIUM ATLAS consumes this governed context to help investigate and explain, but its interpretation is always distinct from deterministic truth. Human review governs any carrier-facing action, and every transition in the finding and dispute lifecycle remains auditable.

01
Deterministic Audit Authority
BLACKLIGHT is the sole source of audit truth. Findings are rule-based, not model-generated.
02
Evidence & Source Traceability
Every finding traces back to raw shipment and invoice identifiers, preserved exactly as ingested.
03
Governed ATLAS Context
ATLAS interprets deterministic truth to explain and investigate — it does not generate or override findings.
04
Human-Reviewed Action
Carrier-facing communication requires explicit human review before it is treated as sent.
05
No Fabricated Recovery
Recovery figures reflect confirmed outcomes only — never projected or estimated values.
06
Auditable Lifecycle
Findings and disputes move through tracked lifecycle states. Nothing is silently deleted.
Frequently Asked

Common questions, answered directly.

Is TRACIUM a dashboard or BI tool?+
No. TRACIUM is a shipment-intent validation, carrier billing investigation, dispute, and recovery platform. Its reporting surfaces are derived from identifiable operational records, carrier invoice data, linkage results, canonical findings, dispute lifecycle state, and confirmed recovery outcomes. Operational and data-quality information remains visible even when no audit findings are produced.
What data is required to get started?+
Two independent data feeds are required. Feed one — Shipment/Delivery: records from SAP, ERP, or TMS in CSV format, including shipment number, delivery number, carrier, service level, expected cost, and weight. Feed two — Invoice/Carrier: carrier billing data in CSV format, including invoice number, billed amounts, billed weight, service level, and at least one deterministic reference field (shipment number, delivery number, tracking number, PRO number, or carrier reference). A client field mapping layer is configured during onboarding to align your specific field names to TRACIUM's canonical model. Both feeds must be present before audit can execute.
Are disputes reviewed before going to carriers?+
Yes. CLAIMFORGE generates dispute drafts pre-populated with finding evidence — reviewed by your team before any transmission. Individual and batch dispute workflows are supported, with carrier-configured recipients, CC/BCC routing, evidence packages, and reviewed email handoff. No carrier communication is treated as sent without explicit user action or confirmed provider success.
What happens to invoices that don't link to shipments?+
Unlinked invoice rows are displayed in FINANCIALS with their linkage status and the reason the link failed. They produce no audit findings and generate no disputes. TRACIUM does not fabricate findings from unlinked data. Unlinked rows may indicate data quality issues, format mismatches, or genuinely unrecognized references requiring investigation before audit can proceed.
How are audit findings generated?+
Findings are produced by BLACKLIGHT, TRACIUM's deterministic audit engine. The engine applies defined rules — overcharge thresholds, duplicate detection, weight comparison, service level validation — against linked shipment-invoice pairs. A finding exists because specific field values from two sources differ in a way that satisfies a defined rule. There is no probabilistic inference and no AI-determined conclusion.
Does TRACIUM use AI?+
TRACIUM uses TRACIUM ATLAS — a governed intelligence layer that helps users investigate findings, understand patterns, and explore root causes. ATLAS consumes deterministic TRACIUM truth and provides AI-assisted investigation and recommendation. ATLAS does not generate audit findings; audit findings are generated by BLACKLIGHT using deterministic rules. ATLAS interprets what the deterministic engine found and helps users understand why. It cannot create, modify, or override findings. This boundary is enforced architecturally.
How does this compare to using a third-party audit firm?+
TRACIUM provides a governed shipment-intent, evidence, and investigation layer that connects operational records, carrier billing claims, rule logic, findings, human review, and controlled recovery workflows. It can be used directly by enterprise transportation, finance, AP, and internal audit teams, or incorporated into the workflow of freight-audit service providers and implementation or consulting partners. TRACIUM is not currently positioned as a freight-payment processor or as a replacement for every managed freight-audit service. The operating team retains visibility into and control over every finding and dispute action.
What does implementation look like?+
Implementation begins with a client mapping layer that maps your field names to TRACIUM's canonical model, using representative invoice and shipment samples. No live ERP integration is required to begin. Initial operation is CSV-based. Timing to first audit findings depends on data availability, linkage quality, carrier coverage, configuration requirements, and pilot scope, and is scoped individually for each engagement.
Get Started

Audit your carrier billing.
Recover what is owed.

Discuss a scoped recovery engagement or enterprise pilot. TRACIUM will assess shipment and invoice data structure, deterministic linkage feasibility, validation scope, and the evidence, security, and onboarding requirements needed for execution.

Direct contact: thomas.rvachew@tracium.tech