TRACIUM — Logistics Audit & Dispute Intelligence Platform

The Problem

Carrier billing errors are not exceptions.
They are the default.

Carriers operate complex billing systems across service lines, surcharge categories, and weight methods. Your ERP records expected costs at shipment time. These two systems rarely agree — and the difference is almost always absorbed by the shipper.

Across an enterprise processing hundreds of invoices per month, even a 1–3% billing error rate represents material, recurring financial leakage. The problem compounds because most teams have never measured it against a structured audit baseline.

Most tools tell you what you spent.
TRACIUM tells you what was wrong, provable, and recoverable.

No Systematic Invoice Validation

Root Cause

Most teams lack a deterministic comparison between what the ERP expected and what the carrier invoiced. Errors stay invisible because no one has built the infrastructure to find them 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 tools and spend analytics platforms tell you what was paid. They cannot tell you what should have been paid, or identify the specific invoice row that contains a provable billing error.

Leakage That Compounds Silently

Financial Exposure

Manual review is too time-consuming to run on every invoice. Teams catch the obvious outliers. Duplicates, weight discrepancies, and rate mismatches accumulate — undetected and unrecovered.

How It Works

Ingest. Audit. Dispute. Recover.

TRACIUM is a pipeline, not a tool. Each step produces a structured output that feeds the next — no manual handoff, no spreadsheet intermediary, no interpretation layer between the data and the dispute.

Load two independent data feeds

INGESTION requires two independent data feeds loaded separately. Feed one: shipment and delivery records exported from SAP, ERP, or TMS — this is the SAP 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.

INGESTION — Dual-Feed Ingestion + Deterministic Linkage

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 financial value and lifecycle state.

BLACKLIGHT — Audit Engine

Investigate findings and surface exposure

Each finding shows the rule that fired, the severity, the full evidence chain, and the discrepancy amount. FINANCIALS surfaces invoice-level financial truth — every row, every variance. SIGNALFORGE provides statistical anomaly context and investigation guidance. It is an explanation layer, not an audit authority.

BLACKLIGHT + FINANCIALS + SIGNALFORGE

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. Teams review before sending. Nothing is transmitted without explicit approval. Manual, batch, and automated dispatch modes are all supported.

CLAIMFORGE — Recovery Pipeline

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

Six systems. One audit pipeline.

BLACKLIGHT

Canonical Audit Engine & Investigation Surface

BLACKLIGHT is the system spine. It executes deterministic rules against linked shipment-invoice pairs, produces canonical findings with financial values and lifecycle states, and provides a full investigation interface. Every finding shows the rule, the evidence, the discrepancy amount, and the operational context. 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. Payloads are pre-populated and reviewed before sending. Manual, batch, and automated dispatch are all supported. 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.

SIGNALFORGE

Statistical Anomaly Layer & Investigation Support

SIGNALFORGE runs statistical anomaly detection independently of the rule engine, surfacing patterns that deterministic rules cannot catch — near-duplicate billing, cost-per-kg spikes, carrier behavior shifts. It is strictly an explanation and investigation guidance layer. It never creates findings, never modifies audit results, and never determines financial truth. This boundary is enforced architecturally.

SIGNALFORGE assists investigation. BLACKLIGHT determines audit truth. These are different systems.

FINANCIALS

Invoice-Level Exposure & Financial Truth Surface

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 Execution Context & Audit Baseline

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 SAP INTENT side of every finding — the ground truth that makes audit possible.

Logistics teams review OPERATIONS to validate that findings reflect real shipment-side discrepancies before authorizing disputes.

INGESTION

Dual-Feed Data Ingestion & Linkage Foundation

INGESTION 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 SAP INTENT against CARRIER CLAIM. Both feeds must be present. Audit does not run on a single data source. Unlinked rows are reported honestly and produce no findings.

Why TRACIUM Is Different

Audit infrastructure.
Not a reporting tool.

TRACIUM is not a BI platform. It does not aggregate spend, model projections, or surface configurable KPIs. It is built at the architectural level to produce evidence-backed findings, enforce audit truth, and execute financial recovery. These are not feature distinctions — they reflect a different design philosophy entirely.

Generic Logistics Analytics & BI Tools

✕Show carrier spend — cannot identify which specific invoice rows are wrong

✕Generate flags and alerts with no lifecycle state, no evidence chain, no dispute path

✕Configurable KPI dashboards — metrics with no underlying audit evidence

✕No deterministic linkage between invoice rows and shipment records

✕No dispute generation — every recovery action requires manual human effort

✕AI-derived conclusions without auditable evidence chains

✕Recovery measured as projected or modelled savings — not confirmed outcomes

TRACIUM

✓Deterministic findings — specific invoice rows, specific discrepancies, specific evidence

✓Canonical findings with lifecycle state: OPEN → DISPUTED → DISMISSED → RESOLVED

✓All metrics are direct outputs of audit findings — no configured KPIs, no synthetic surfaces

✓Typed, deterministic identifier linkage between every invoice row and its shipment record

✓CLAIMFORGE: dispute generation, review, transmission, and tracking — built into the platform

✓Zero fabrication: if evidence is insufficient, the system states it rather than producing an unsupported finding

✓Recovery measured from confirmed dispute outcomes only — never modelled or projected forward

Recoverable Conditions

What the audit engine detects.

TRACIUM identifies billing discrepancies where deterministic rules fire against linked evidence. The following are the core recoverable finding categories the audit engine is built to detect and quantify.

OVERCHARGE

Rate & Amount Overcharge

Invoiced amount exceeds the expected cost recorded in the shipper's ERP beyond the defined threshold. Quantified as both a percentage variance and an absolute dollar discrepancy per invoice row. Fires when billed amount exceeds SAP intent by more than 5%.

DUPLICATE_INVOICE

Duplicate Invoice Detection

The same shipment billed twice under different invoice numbers. Detected through deterministic cross-referencing of shipment identifiers across invoice records. Both charges are confirmed against the same shipment-side evidence and grouped as one canonical finding.

WEIGHT_MISMATCH

Weight Discrepancy

Carrier-billed weight differs from the gross weight recorded in the shipper's system by more than the defined threshold. May originate from carrier re-weigh, dimensional weight calculation differences, or data entry errors. Detected deterministically at the invoice row level against SAP weight fields.

SERVICE_LEVEL_MISMATCH

Service Level Mismatch

A shipment booked at one service level is invoiced at a different rate class. The invoice references the correct shipment — the discrepancy is in the service code applied. Detected through deterministic comparison of the expected service level against the billed service code.

THIRD_PARTY_BILLING_ERROR

Third-Party Billing Error

Carrier invoice is billed to a third-party account that does not match the billing responsibility recorded in the shipment data. Detected through deterministic comparison of the billed payer type and account against the expected payer configuration in the ERP.

ACCOUNT_NUMBER_MISMATCH

Account Number Mismatch

The carrier account number on the invoice does not match the account number recorded in the shipment's billing configuration. Detected through normalized exact-match comparison of the billed account reference against the expected account number from the shipment record.

Platform Tour

The platform in operation.

Every screen reflects backend state only. What you see is canonical audit, dispute, ingestion, and investigation state — no fabricated findings, no synthetic financial truth.

Dual-feed ingestion

Deterministic linkage

Canonical audit findings

Reviewed dispute workflow

Client-scale navigation

Configuration governance

Backend-owned totals

Performance-optimized upload and operations paths

BLACKLIGHT

Canonical Audit Engine & Investigation View

BLACKLIGHT is the evidence-first investigation surface for canonical audit findings. The screen combines the finding feed, backend-owned financial context, Context Intelligence, SAP root cause detail, and lifecycle actions without creating a second source of truth.

Canonical finding list with severity, rule, shipment, invoice, and exposure value

Backend summary totals drive command bar, footer, badges, and finding counts

Context Intelligence surfaces evidence snapshot, root cause, suggested fix, summary, and recommendation

Investigation View shows raw shipment, invoice, delivery, carrier, service, tracking, and lifecycle evidence

CLAIMFORGE

Recovery Pipeline

Recovery Velocity tracks dispute value across DRAFT, SENT, and RESOLVED over time. The dispute board shows every active dispute with carrier, invoice, service level, and canonical finding link — all at a glance.

Recovery Velocity: live dispute book by created timestamp and lifecycle state

DRAFT / SENT / RESOLVED columns with real-time totals and amounts

Every dispute is pre-populated from finding evidence and reviewed before sending

Canonical link on every dispute traces back to the originating BLACKLIGHT finding

SIGNALFORGE

Statistical Anomaly Support

SIGNALFORGE surfaces statistical anomalies for investigation support only. It highlights cost-per-kg spikes, baseline variance, carrier behavior shifts, and anomaly confidence without generating findings, modifying audit results, or determining financial truth.

Priority anomaly cards show carrier, shipment, invoice, billed amount, score, cost/kg, and baseline

Anomaly confidence badges are separate from BLACKLIGHT Evidence Confidence

Supports patterns deterministic rules may not catch while preserving BLACKLIGHT as audit authority

Runs as an explanation and triage layer — never as a findings engine

FINANCIALS

Invoice Intelligence

Raw invoice-level financial truth — every row, every variance, every OVERCHARGED tag. The Exposure Heatmap shows audit yield sized by carrier and rule type. Top discrepancies surface the highest-priority individual recovery targets.

Exposure Heatmap: carrier-rule exposure from canonical open audit findings

Invoice table with expected vs billed, variance %, and OVERCHARGED tags

Top discrepancies panel identifies highest-priority individual recovery rows

Total overcharged, count, and match/under always visible in sidebar

OPERATIONS

Shipment Execution Baseline

OPERATIONS is the shipment-side baseline for audit investigation. It exposes shipment, delivery, carrier, route, tracking, billed-versus-expected context, weight, invoice count, notes, and risk state so logistics teams can validate operational truth before dispute action.

Shipment records show carrier, route, tracking number, delivery number, invoice count, weight, and audit status

Search, status filtering, and pagination keep client-scale shipment data reachable

Shipment notes preserve operational review context beside the audit baseline

High-risk scoring helps teams prioritize shipment-side validation before authorizing disputes

UPLOAD

Dual-Feed Data Ingestion

UPLOAD is the controlled ingestion workflow for SAP/ERP/TMS intent and carrier claim data. Operations files and Financial files are loaded separately, templates are client-ready downloadable assets, Data Quality Check runs before audit, and upload actions do not trigger BLACKLIGHT automatically.

Step 1 loads the Operations shipment feed: SAP/ERP/TMS intent baseline

Step 2 loads the Financial invoice feed: carrier claim reality

Data Quality Check inspects linkage, weight drift, rule collisions, and duplicate chains before audit

Audit runs only when explicitly executed; unlinked rows are reported honestly and produce no findings

Analytics Philosophy

Every number is
a finding consequence.

TRACIUM does not produce configurable KPIs, modeled projections, or abstract metrics. Every number, chart, and visual on the platform represents something provable, recoverable, and operationally real.

All analytics surfaces are direct visualizations of canonical audit findings, dispute lifecycle state, and recoverable financial exposure. If no findings exist, there is nothing to report. This is not a quality standard — it is a system constraint.

Most tools answer: "What did we spend?" TRACIUM answers: "What is wrong, what is in dispute, and what has been confirmed recovered." The distinction is not cosmetic. One produces reports. The other produces recovery.

METRIC	WHAT IT ACTUALLY REPRESENTS
Audit Yield	Sum of discrepancy amounts across OPEN findings. A direct output of the audit engine — not a configured KPI.
Recovery Rate	Confirmed carrier credits from resolved disputes only. Not projected. Not modelled. Not estimated.
Carrier Leakage	Distribution of actual detected errors by carrier and rule type — what the deterministic engine found, not modelled behavior.
Linkage Coverage	Percentage of invoice rows linked to shipment records. Low coverage means audit yield is not meaningful yet — fix data first.
Finding Lifecycle	Operational pipeline state across OPEN, DISPUTED, DISMISSED, RESOLVED. A direct reflection of the audit and recovery pipeline.

Who It's For

Built for teams with financial accountability for carrier costs.

◈

Logistics & Transportation Teams

Responsible for freight cost control across multiple carriers and service types. TRACIUM replaces ad-hoc manual review with a systematic audit engine that surfaces findings your team can investigate, validate, and escalate with full operational context.

◉

Finance & Accounts Payable

Accountable for invoice accuracy and period-close reporting. Finance teams use FINANCIALS to validate that billed amounts match expected costs at the row level — and to confirm disputed amounts align with canonical finding evidence before authorizing recovery actions.

⬡

Carrier Billing & Freight Audit Teams

Dedicated teams responsible for identifying and recovering discrepancies. TRACIUM replaces manual audit with a systematic engine — producing evidence-backed findings on every invoice, generating dispute communications automatically, and tracking recovery through to resolution.

◇

Supply Chain Operations Leadership

Executives accountable for logistics performance and cost control. TRACIUM's audit yield and recovery pipeline data provides the baseline measurement of carrier billing accuracy — and the infrastructure to improve it systematically rather than through periodic manual reviews.

◌

Audit & Compliance Teams

Teams requiring traceable evidence and maintained audit trails. TRACIUM preserves full finding lifecycle history — findings are never deleted, every status transition is tracked, and dispute evidence is exportable for regulatory, contractual, or internal audit purposes.

◆

Enterprise SAP Environments

Organizations running SAP ERP as their shipment system of record. TRACIUM is purpose-built for SAP INTENT vs CARRIER CLAIM comparison. Shipment data loads from SAP exports — no live API integration required to begin generating findings. Future phases include controlled SAP writeback for approved corrections.

Platform Integrity

Evidence first.
No fabrication.
Full traceability.

TRACIUM's credibility depends on one principle: never stating more than the evidence supports. Every finding is backed by evidence. Every financial figure is derived from canonical backend state. If evidence is incomplete, the platform says so explicitly — it does not produce a finding it cannot defend.

These are not aspirations. They are architectural constraints enforced at the system level.

①

Deterministic Audit Logic

All findings produced by rule-based logic against linked evidence. No probabilistic inference. No AI-determined financial conclusions. Rules fire or they don't.

②

Full Evidence Traceability

Every finding links to the specific invoice row, shipment record, rule, expected value, and actual value. The evidence chain is always visible — nothing inferred without backing data.

③

Dispute Review Before Transmission

Disputes are generated as drafts for team review. Nothing is transmitted to carriers without explicit approval. Automated sending is a deliberate configuration choice, not a default.

④

Raw Identifier Integrity

Shipment, delivery, and invoice identifiers are preserved exactly as loaded. No reformatting, no synthesis. Carrier-facing disputes always use the original identifier values.

⑤

Complete Lifecycle History

Findings are never deleted. Every lifecycle transition — OPEN, DISPUTED, DISMISSED, RESOLVED — is preserved for compliance, retrospective review, and audit trail purposes.

Frequently Asked

Common questions, answered directly.

Is TRACIUM a dashboard or BI tool?+

No. TRACIUM is a logistics audit and dispute platform. It does not produce configurable dashboards, abstract KPIs, or modeled analytics. Every data surface is a direct reflection of canonical audit findings, dispute lifecycle state, and recoverable financial exposure. If no findings exist, there is nothing to display. This is a system constraint, not a feature setting.

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. Manual, batch, and automated dispatch are all supported. Automated sending is a deliberate configuration choice, not a default. Nothing is transmitted to a carrier without explicit user action.

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 includes SIGNALFORGE — a conservative intelligence layer used for explanation, statistical anomaly detection, and investigation guidance. SIGNALFORGE is not the audit engine and is not a source of findings. Audit findings are generated by BLACKLIGHT using deterministic rules, not AI inference. SIGNALFORGE interprets what the deterministic engine found. It cannot create, modify, or override findings. This boundary is enforced architecturally.

How does this compare to using a third-party audit firm?+

Third-party audit firms review invoices in arrears, charge 25–50% of recovered amounts, and deliver findings as reports. TRACIUM audits continuously, produces findings as structured data with lifecycle state, generates dispute communications within the platform, and costs a fraction of contingency fees at scale. Your team controls the findings and acts on them directly.

What does implementation look like?+

Implementation begins with a client mapping layer that maps your field names to TRACIUM's canonical model — typically completed in 2–4 weeks using representative invoice and shipment samples. No live ERP integration is required to begin. Initial operation is CSV-based. First audit findings are typically available within 3–4 weeks of onboarding start, depending on data quality and identifier consistency.

Carrier billing
errors are systemic.
Prove them.

Carrier billing errors are not exceptions.
They are the default.

Ingest. Audit. Dispute. Recover.

Six systems. One audit pipeline.

Audit infrastructure.
Not a reporting tool.

What the audit engine detects.

The platform in operation.

Every number is
a finding consequence.

Built for teams with financial accountability for carrier costs.

Evidence first.
No fabrication.
Full traceability.

Common questions, answered directly.

Audit your carrier billing.
Recover what is owed.

Carrier billingerrors are systemic. Prove them.

Carrier billing errors are not exceptions.They are the default.

Ingest. Audit. Dispute. Recover.

Six systems. One audit pipeline.

Audit infrastructure.Not a reporting tool.

What the audit engine detects.

The platform in operation.

Every number isa finding consequence.

Built for teams with financial accountability for carrier costs.

Evidence first.No fabrication.Full traceability.

Common questions, answered directly.

Audit your carrier billing.Recover what is owed.

Carrier billing
errors are systemic.
Prove them.

Carrier billing errors are not exceptions.
They are the default.

Audit infrastructure.
Not a reporting tool.

Every number is
a finding consequence.

Evidence first.
No fabrication.
Full traceability.

Audit your carrier billing.
Recover what is owed.