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.
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.
What data is required to get started?+
Two data sources are required: carrier invoice files in CSV format (invoice number, shipment reference identifiers, billed amounts, service level fields), and shipment-side records from SAP or equivalent ERP (shipment number, delivery number, expected cost, carrier, service level, weight). A client mapping layer is configured during onboarding to align your field names with TRACIUM's canonical model.
Does TRACIUM use AI?+
TRACIUM includes SIGNALFORGE — an AI 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.
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.
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 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.
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.
