ARDEM FreightSure™ takes the repetitive work off your team so loads get created fast and invoices go out clean.

• Load tender intake — From email, shipper portals, or EDI 204, with customer rules and lane metadata applied automatically. 
• BOL / eBOL capture — Ingest paper BOLs, PDFs, images, and eBOL 2.1 payloads; extract shipper/consignee, commodities (NMFC/class), pieces, weight/dims, and references (PRO/PO/SCAC/ZIP+4). 
• POD & W&I documents — Pull proof-of-delivery and reweigh/inspection artifacts from drivers, terminals, or shipper feeds so billing has evidence up front. 
• Data validation — Check PRO, NMFC/class, and accessorials (liftgate, inside, limited access); flag reweigh/reclass variances for analyst review only when thresholds are exceeded. 
• Normalization & enrichment — Standardize formats, fix common defects, and reconcile interline partner data so downstream rating and billing stay accurate. 
• Native TMS posting — Create/ update loads and post clean EDI 210 invoices and 214 status updates inside your TMS queues (no new portal). 
• Exception handling — Risk-score each bill, route only high-risk items to a human queue, and attach supporting images/notes for fast resolution. 
• Reporting & governance — Track cycle time (POD→210), exception %, 997 acceptances %, 210 rejects %, and short-pay rate; retain full audit trails for finance and compliance. 

How It Works: POD → 210 Fast Lane

ARDEM FreightSure™ turns documents into clean invoices in three tight steps, without adding a new portal.

1. Capture once 
   • Intake from email/portals, eBOL 2.1 feeds, driver/terminal apps, scanners. 
   • Collect BOL, POD, and W&I/OS&D images; auto-read barcodes/PRO and timestamps. 
   • Normalize formats and attach artifacts to the load record at the start.
2. Validate & enrich 
   • Check PRO, shipper/consignee, NMFC/class, pieces/weight/dims, and accessorials (liftgate, inside, limited access). 
   • Flags reweigh/reclass variances only when thresholds are exceeded (human-in-the-loop). 
   • Catch duplicates, reconcile interline partner data, and ensure required docs are present. 
   • Pre-invoice (210) pre-flight: validate 210 structure/content; attach POD/W&I; hold failures in an exceptions queue.
3. Post natively 
   • Create/update loads and post clean EDI 210 invoices and 214 status updates inside your TMS queues. 
   • Track 997 acknowledgments and 210 rejects; route issues with images/notes to analysts. 
   • Maintain full audit logs and SLA timers for finance and compliance.

What you see:
Ops sees fewer touches and a shrinking exceptions queue. Finance sees faster POD invoice and fewer short pays. IT sees standards-based flows (eBOL + EDI) mapped cleanly to your TMS, no swivel-chair.

Typical targets (tune during onboarding): 

• POD→210: minutes/hours, not days 
• Exceptions to QA: <10% 
• Short-pay reduction: 30–60% via defect prevention 
• 997 acceptances: >99% on clean 210s 

Systems We Work With

We operate inside your environment using a “works-with” model, no certification or endorsement implied.

Carrier TMS (works-with, unaffiliated) 

• McLeod LoadMaster — native billing queues, imaging, EDI/API connectivity 
• Trimble TMW.Suite — enterprise ops/billing integration points 
• Carrier Logistics FACTS — LTL-specific workflows and billing

P&D / Document Capture 

• Common driver, dock, and terminal capture tools (POD, W&I, OS&D) 
• Imaging systems and inbox/portal intake for BOLs and supporting docs

Rating, Visibility & Shipper Connectivity 

• Rating: SMC³ (RateWare, LTL APIs) 
• Visibility: project44, FourKites (shipper/3PL ecosystems) 
• EDI: direct or via VAN/AS2 to shippers and brokers

Data Exchange Options 

• eBOL 2.1 REST payloads (create/update/cancel) 
• EDI: 204 (tender), 210 (freight invoice), 214 (status), 990, 997 
• APIs / SFTP / secure file drops based on your policy

What this means for your team
No new portal, no swivel-chair. We post to your native TMS queues and keep artifacts attached to each record for clean, auditable billing.

We Support Full Truckload (FTL)

FreightSure™ is FTL-ready. The same intake-to-invoice spine works for truckload carriers, no new portal. We ingest rate confirmations, capture BOL/POD and stop-level details, track detention/layover/TONU, attach lumper receipts, and post clean EDI 210 invoices with 214 updates inside your TMS.

What we automate for FTL 

• Rate confirmation intake (email/portal/API) → auto-create load with lanes, stops, and schedule.
• Stop-level capture: arrival/departure times, signatures/POD, lumper receipts, photos.
• Accessorials specific to TL: detention, layover, TONU, stop-offs, driver assist, tarp (flatbed), redelivery.
• Data checks: pieces/weight/dims consistency, reference IDs (PRO/PO/BOL), fuel surcharge tables.
• Native posting: create/update loads; transmit 210/214; monitor 997; hold exceptions for QA.
• Evidence: link receipts/images/notes to the invoice record for fast dispute resolution.

Typical outcomes 

• Delivered→210 in hours, not days.
• Accessorial capture rate ↑ (detention/lumper reimbursed on first pass).
• 210 reject rate ↓ with pre-flight checks; fewer back-and-forths with brokers/shippers.

Standards We Support

We align to industry standards so your data flows cleanly through shipper, carrier, and 3PL systems.

Digital LTL Council / NMFTA — eBOL 2.1 

• Support for create / update / cancel (REST) 
• Key identifiers & fields: SCAC, ZIP+4, PRO, shipper/consignee, commodities (NMFC/class), pieces/weight/dims, accessorials, hazmat/special handling 
• Structured error handling and idempotent processing 
• Upstream accuracy that drives downstream billing quality

EDI Spine (interoperability with shippers & 3PLs) 

• 204 — Load Tender 
• 210 — Freight Invoice (pre-flighted before release) 
• 214 — Shipment Status 
• 990 — Response to Load Tender 
• 997 — Functional Acknowledgment (acceptance monitoring)

Bridging & Validation 

• Map eBOL 2.1 payloads into TMS load creation and billing 
• Pre-invoice 210 checks with required documents attached (POD / W&I) 
• Exception routing with artifacts for fast dispute resolution

Why Choose ARDEM FreightSure™?

FreightSure™ lives inside your TMS, no new portal. We standardize intake (email, portals, eBOL 2.1), validate the data that drives margin, and post clean EDI 210 invoices with human-in-the-loop QA for edge cases. The result: faster POD invoice, fewer short-pays, and elastic back-office capacity.

• Works-with your stack: McLeod, TMW.Suite, Carrier Logistics FACTS (unaffiliated “works-with” model). 
• Standards-first: eBOL 2.1 + EDI 204/210/214/990/997 for clean interoperability. 
• Less swivel-chair: we post to your native billing queues; teams stay in familiar screens. 
• Defect prevention: accessorial/NMFC/weight checks and 210 pre-flight before release. 
• Right-touch QA: risk scoring routes <10% of bills to analysts; everything else flows straight through. 
• Proven governance: ISO 27001 • SOC 2 Type 2 • SOX-aligned processes with full audit trails. 
• Transparent SLAs: weekly metrics + heatmaps; monthly service reviews; continuous tuning. 

Finance 

• DSO impact: faster POD→210 (minutes/hours, not days).
• Disputes down: 30–60% fewer short-pays via defect prevention and pre-invoice checks.
• Write-offs reduced: complete evidence packets (POD/W&I) attached to each invoice.

Operations 

• Throughput up: automated intake and validation; analysts focus on true exceptions.
• SLA confidence: exception MTTR falls; aged exceptions shrink with clear queues and timers. 
• First-pass quality: >99.5% field validation on load creation; fewer rework loops.

IT/TMS 

• Low lift: “works-with” inside McLeod/TMW/FACTS—no parallel portal to maintain.
• Standards-based: eBOL 2.1 and EDI 204/210/214/990/997; clean mappings and auditability.
• Security assured: ISO 27001 • SOC 2 Type 2; role-based access and full audit logs.

Outcomes & SLAs

Set targets during onboarding; we baseline your current metrics and track improvements weekly. 

• POD → EDI 210 cycle time: minutes/hours, not days 
• Short-pay reduction: 30–60% via defect prevention and pre-invoice checks 
• Exceptions routed to QA: <10% of bills (risk-based) 
• 210 reject rates: trend toward <1% on clean, pre-flighted invoices 
• 997 acceptances: >99% on transmitted 210s 
• Load creation accuracy: >99.5% fields validated before release 
• Evidence completeness: 100% required artifacts (POD/W&I) attached on invoiced loads 
• Response SLAs (example; finalized at kick-off): critical exceptions ≤4 hours; standard exceptions ≤1 business day. 

Exception Handling & QA

Focus analyst time where it matters. Automation clears the routine; humans handle the edge cases. 

• Risk scoring on every bill — Rules- and ML-driven checks for PRO mismatches, NMFC/weight variances, accessorial conflicts, missing docs, duplicates, and EDI pre-flight failures. 
• Native exceptions queue (in your TMS) — We work inside your queues with clear statuses (New → Waiting Info → Ready to Post → Closed), SLA timers, and escalation paths. 
• Evidence attached to each item — BOL, POD, W&I images, partner/interline docs, and analyst notes travel with the record for faster approvals and fewer back-and-forths. 
• Pre-invoice (210) pre-flight — Validate structure/content, required segments, reference fields, and attachments before release; failed checks are held for review. 
• Dispute-ready packets — Auto-compile supporting artifacts for Finance/AR to resolve short-pays quickly. 
• Feedback loop & SOP refresh — Weekly defect heatmaps (top causes, lanes, shippers) with before/after impact tracking on fixes. 
• Sampling & quality control — Statistical sampling on auto-cleared bills; QA scorecards with thresholds; continuous tuning of capture/validation rules. 
• Compliance & audit logging — End-to-end timestamps, user actions, reason codes, and retention policies for audits. 
• KPI visibility — Exception rate, aged exceptions, MTTR, reopen rate, touches per dispute—reported by customer, lane, and terminal. 
• Access control — Role-based, least-privilege access with separation of duties.

Outcome: a shrinking exception queue, faster dispute resolution, and cleaner 210s with fewer short pays.

ISO 27001

(PCI DSS 3.2.1)

ISO 27001 (formally known as ISO/IEC 27001:2005) is a specification for an information security management system (ISMS). An ISMS is a framework of policies and procedures that includes all legal, physical, and technical controls involved in an organization’s information risk management processes.

SOC 2 Type 2

AWS Secure Cloud Utilization

A SOC 2 Type 2 report is an internal control report capturing how a company safeguards customer data and how well those controls are operating. These reports are issued by independent third-party auditors covering the principles of Security, Availability, Confidentiality, and Privacy.

SOX Compliance

Sarbanes–Oxley Financial Compliance

SOX Compliance mandates strict reforms to improve financial disclosures from corporations and prevent accounting fraud. We support issues such as auditor independence, corporate governance, internal control assessment, and enhanced financial disclosure based on your SOX Compliance Protocols.