Loads today47
On-time94%
Exceptions6
#88421 Savannah→CHI 214 X6
#88419 Memphis LTL At dock
#88414 Dray ATL HOS risk
TMS · CMS · Role dashboards
Run loads, money, and drivers in one intelligent flow.
DICAFLOW is a TMS for carriers and 3PLs running real lanes: tender loads, dispatch assets, capture PODs at the door, and push 214-style status timelines to customers who still live in EDI—without your billing team retyping weights from a camera roll.
Smart Invoice reads your contract tables (base rate, FSC, detention, lumper, stop-offs). Billing & Accounting Management maps charges to the GL you already use. GPS shows where drivers are—not just for dots on a map, but for detention clocks and service windows. AI scanning turns BOL and rate-con photos into structured fields tied to the load ID. A built-in TMS CMS powers shipper portals, driver briefings, and email/SMS templates—while saved dashboard views give dispatch, billing, and the C-suite their own default workspace.
Illustrative workflows—wire your real EDI guides (210/214/990), motor carrier SCACs, fuel tax (IFTA) exports, and AI model accuracy to your legal and IT policies before go-live.
Active loads
#88421 · Savannah → Chicago
Reefer · 38,400 lb · 3 stops
214: In transit
#88407 · I-85 dray
Driver: R. Santos · Unit 412
AI: POD scan queue
Drivers / GPS
ELD + app · 27 online
Geofence: 6 arrivals / 2 detention risk
Next service window
CVSA blitz week · doc pack ready
Billing
Smart Invoice batch
14 ready · 6 matched to 210
AR / AP snapshot
DSO 34d · carrier pay Tue
// ai.scan · bol_sav_88421_p1.jpg
pro_number: "SVH-441092" · seal: "882144" · confidence: 0.96
gl: 4000-FTL · tax jurisdiction matched
gps: ping 45s · corridor I-95N
pro_number: "SVH-441092" · seal: "882144" · confidence: 0.96
gl: 4000-FTL · tax jurisdiction matched
gps: ping 45s · corridor I-95N
Built for carriers, brokers, and fleets that live on the road
KETTLEMAN LINEHAUL
Bridgeport Logistics LLC
Great Lakes Refrigerated
Redhook Intermodal
Atlas Final Mile
From dock check-in to paid invoice
DICAFLOW treats each shipment as a single thread: appointment times, seal numbers, lumper tickets, and OS&D notes stay on the load. When the trailer bumps the dock, geofence + timestamp feed detention logic; when the BOL is photographed, AI fills pro numbers and piece counts for billing—no second spreadsheet labeled “FINAL v3.”
- Multi-stop and pool distribution with per-leg costs
- Carrier packets: COI, W-9, factor notice on file
- IFTA mileage buckets when you enable fuel & toll imports
Dashboard views for every seat
DICAFLOW ships opinionated defaults—then lets each role pin widgets, filters, and KPIs. Operations live on the live board; finance lives on cash and margin; executives get a rolling week without drill-down noise. Views are permission-scoped and can be duplicated per terminal or customer team.
Ready to bill14
DSO34d
Disputes2
Batch B-908 Smart Invoice $428k
Factor file OTTP · Tue OK
GL sync QBO · 11:04 Synced
Detention Pending proof 3
Online27
Geofence8
Idle >15m3
Unit 412 I-95N On route
Unit 405 Geofence in 12:08
Unit 398 App only Low batt
Rev / mile$2.84
Deadhead6.2%
Claims0.11%
Top lane CHI-DFW +margin
Customer Retail A OTIF 97
Read-only milestones, doc downloads, and branded copy—served from the same CMS that powers your public status pages.
PO 77821 In transit ETA Fri
POD pack Available PDF
EDI 214 Mirrored ✓
Open tenders9
Accepted4
Docs due1
COI Exp 45d Valid
Rate con #RC-4410 Signed
Payment Quick pay On
TMS CMS: content that ships with the freight
Manage shipper-facing portals, driver quick-help articles, check-in instructions per consignee, and transactional templates (email, SMS, in-app) in one CMS layer. Content is versioned, scoped by customer or terminal, and referenced from loads so updates propagate without redeploying code.
Winter receiver hours · Chicago consolidation
Check in at Door 14. After 18:00 CT, appointments move to the night gate—drivers must upload scaled weight before leaving the lot. Questions: dispatch@kettlemanlinehaul.com · reference the PRO on the BOL.
CMS entries can drive dashboard callouts too—e.g. embed safety bulletins on the dispatch home view or show finance a rolling “rate change log” pulled from published notices.
Where DICAFLOW earns its keep
Four operating modes we see every week in freight—asset fleets, brokered coverage, finance close, and audit defense.
Asset carriers
Fleet-first dispatch
Assign drivers to tractors and trailers with HOS-aware boards. Push preplans to the cab, auto-start GPS when the driver begins the trip, and close the loop when the signed POD lands—same night accrual for revenue teams.
Brokers & 3PL
Cover loads with confidence
Track carrier SCAC, MC/DOT, and insurance expirations beside the load. Customer-facing milestones mirror what you send on 214; carrier pay mirrors rate con and accessorial approvals—fewer “we never agreed to that” calls.
Finance & back office
From trip to trial balance
Smart Invoice batches roll up fuel surcharges, stop charges, and detention that already met your clock rules. Push journal entries to QuickBooks Online, Xero, or NetSuite with dimensions for customer, lane, and equipment class.
Compliance & audit
Evidence on demand
Every AI extraction stores the original image/PDF, model version, and reviewer sign-off. When a shipper disputes accessorials or DOT asks for maintenance ties to a trip, you open one load—not three systems.
The miles your software has to survive
TMS, finance, field, and AI—together
One load ID from tender to payment: operations see execution, finance sees margin, safety sees documents, and customers see milestones—without exporting CSVs named “do_not_use.”
Transportation Management System core
Order intake (EDI 204, API, or CSV), tendering, dispatch boards, multi-stop trips, trailer pools, and OS&D—structured so Smart Invoice, GPS, and AI scans inherit the same reference numbers shippers already use.
GPS
Live driver locations, geofences, and status—so dispatch sees delays before the customer calls.
Smart Invoice
Pull delivered miles, stops, detention minutes, and fuel index tables into a customer-ready 210 packet (PDF/EDI). Flag when billed weight ≠ scaled weight or when a rate con shows a different FSC floor.
Billing & Accounting Management
Carrier settlements, factoring file exports, cash application, and GL mappings (revenue, pass-through, accruals). Allocate linehaul vs. fuel vs. accessorials to the accounts your controller already defined.
Driver tracking & location intelligence
Blend mobile app pings with partner ELD positions. Share read-only links to shippers, start detention clocks on geofence entry, and retain breadcrumb history for claims—subject to your driver privacy policy.
AI document scanner
Drivers snap BOLs at the guard shack; back office drops rate cons and lumper receipts as PDFs. Models extract SCAC, PRO, seal, piece count, and signatures—low-confidence cells go to a review queue with side-by-side originals.
Exceptions & approvals
Detention, layover, and reweigh requests route to the right approver with document evidence attached—no lost email threads.
Role dashboards & TMS CMS together
Saved views stack widgets (KPIs, maps, queues, AI review) per persona—dispatch, billing, safety, executive. The same CMS that edits shipper portals can inject snippets into those dashboards: safety blitz notices, customer bulletins, or temporary receiver hours, scoped by terminal and effective dates.
Connects to the logistics ecosystem
Bridge telematics, maps, accounting, and shipper systems so status, documents, and dollars stay synchronized—whether your customer still wants X12 or a modern REST webhook.
ELD / telematics
Maps & routing
Accounting / ERP
Fuel & cards
EDI / APIs
Customer portals
Use webhooks and APIs to push status, documents, and journal entries. List your certified integrations here as you onboard partners.
Trust for freight, finance, and location data
Shippers and regulators expect proof. Drivers expect privacy. Finance expects controls. Describe your real posture where noted.
Encryption in transit and at rest
TLS for browsers and mobile; encrypted storage for documents, extracted AI fields, and financial records.
Role-based access control
Separate dispatch, billing, drivers, and partners. Mask sensitive customer rates where needed; audit views for administrators.
Location data governance
Configurable retention for GPS traces, consent flows for driver apps, and geodata handling aligned with regional privacy rules.
Document & AI provenance
Store originals alongside machine extractions; human overrides are logged for disputes and carrier settlements.
Availability & backups
Operations run around the clock—document your SLA, RPO/RTO, and disaster recovery tests for enterprise RFPs.
Scoped integrations
API keys per environment, IP allow lists optional, and no silent broadening of accounting sync scope.
Rollout that respects the dock
Go live without freezing the yard: pilot one customer lane or one terminal, match invoices to the penny, then expand.
Model your network
Import customers, consignees, SCAC list, tractors/trailers, drivers, tax nexus, and chart of accounts. Map charge codes (linehaul, FSC, detention, lumper) to GL and dimensions finance already audits.
Wire tracking & documents
Connect Samsara, Geotab, or platform ELD feeds; publish mobile capture to drivers. Turn on AI models per doc type (BOL vs. rate con) and staff a 15-minute daily exception huddle until accuracy holds.
Run revenue in parallel
Bill 50 loads in DICAFLOW while legacy TMS still runs the rest; reconcile AR and carrier pay weekly. When variances stay inside your threshold, cut over Smart Invoice and accounting exports fully.
Typical first-month wins: same-night POD indexing, detention billed with geofence proof, and dispatchers who stop asking “which spreadsheet is live?”
One platform, roles that match the terminal
Dispatch sees movement. Finance sees margin. Drivers see only what they need.
Dispatch & planners
- Live board with ETAs and exception flags
- Drag-and-drop assignments tied to HOS snapshots
- Document inbox fed by AI scanner queues
Drivers & owner-operators
- Simple app: next stop, capture POD, scan docs
- Location sharing with clear start/stop boundaries
- Settlement previews when you enable pay rules
Billing & leadership
- Smart Invoice batches with approval gates
- Margin by customer, lane, and equipment class
- Exports to your accounting system of record
Why fleets outgrow patchwork tools
TMS, billing, GPS, and documents each work better when they share one load ID.
| Need | Spreadsheets + inbox | Single-point tools | DICAFLOW |
|---|---|---|---|
| Invoice from real execution | Copy/paste, error prone | Manual bridge between TMS & accounting | Smart Invoice tied to loads & PODs |
| Driver location you can defend | Phone tags & screenshots | Map app outside billing context | GPS + history on the same load |
| Document data entry | Clerical backlog | OCR with no TMS link | AI scanner → structured load fields |
| Accounting truth | Delayed close, weak audit trail | Duplicate masters | Billing & accounting module + exports |
Marketing comparison—validate claims against your product roadmap and legal review.
POD to invoice used to be our black hole. Now scans hit load 88421 the same night—billing stopped Slack-bombing drivers for retakes.
We bill detention with geofence timestamps and the signed lumper receipt in one PDF. Retail customers stopped short-paying lines that “didn’t have backup.”
Questions, answered
TMS, billing, GPS, and AI scanning—practical questions carriers ask before they switch.
What is included in the TMS?
Load lifecycle management—order intake, tendering, dispatch, execution tracking, and exceptions—designed to feed Smart Invoice and accounting without retyping.
Which dashboard views ship out of the box?
Typical defaults include Dispatch Command (live board + exceptions), Billing & AR (batches, DSO, disputes), Fleet & GPS (map-backed positions and geofences), Executive KPI (margin, deadhead, OTIF), plus permission-scoped Shipper Portal and Carrier Workspace summaries. Each supports saved personal and shared team layouts.
What does the TMS CMS control?
Customer- and terminal-scoped content: portal pages, driver briefing articles, check-in copy tied to consignees, email/SMS/in-app templates with merge tags, and optional public status messaging. Publishing workflows and version history keep marketing and ops from overwriting each other.
How does Smart Invoice differ from a PDF template?
It applies your contract rules, accessorial logic, and tax configuration to each delivered load, flags anomalies, and prepares batches for customer submission or EDI.
Does Billing & Accounting replace my ERP?
It can run as your operational billing hub with GL exports, or sync to QuickBooks, Xero, NetSuite, or your ERP—define your supported connectors on a integrations page.
How does driver location tracking work?
Typically via mobile app or ELD partner feeds, with configurable ping rates, geofences, and retention. Always align collection and disclosure with employment law and local privacy rules.
What does the AI document scanner extract?
Common freight documents: BOL numbers, stops, quantities, signatures, dates, and reference IDs—tuned per doc type. Low-confidence fields route to human review; keep humans in the loop for regulated freight.
Where is data hosted?
Document regions, subprocessors, encryption standards, and certifications (e.g., SOC 2) on your trust page when available.
Can we migrate from another TMS?
Most teams import open loads, master data, and historical documents in phases. Parallel-run billing until variances fall inside your tolerance.
Mobile for drivers—online only?
Roadmap-dependent: many fleets start with online capture and queue uploads at better signal; document your offline behavior when you ship it.
Freight moves fast. Your back office should keep up.
DICAFLOW unifies Transportation Management with Smart Invoice, Billing & Accounting Management, live driver location, and an AI document scanner—so every mile, document, and dollar traces to the same pro number.
Swap in your live KPIs (POD-to-bill hours, DSO, detention capture rate), motor carrier IDs, and SOC 2 / CSA program details as you harden the product for production.