Delivered to paid in minutes.
TIR in, driver back: billing fires. Every accessorial captured from the move, not reconstructed from memory. Every line matched against the customer PO before the invoice goes out. Discrepancy flagged before submission. Same-day close.
How it works
Driver returns with TIR and delivery confirmation: billing fires
TIR closes the chassis. Signed delivery confirmation closes the move. Both land: billing triggers. Paperwork in this region can be inconsistent (wrong codes, missing fields, damage notes scrawled on the corner of a page). We surface the grey areas before they become disputes.
Every line item calculated: chassis days, per diem, accessorials
Chassis days counted from pickup to return exactly. Per diem and fuel surcharge applied at the correct rate for that customer and lane. Every line backed by data already in the system.
Invoice pushed to your billing stack: zero re-keying
Synced to QuickBooks, your TMS, and the customer portal simultaneously. Same-day invoicing. Human-in-the-loop by default; invoices queue for one-click approval before going out. Nothing leaves without sign-off.
Mismatches flagged before the customer disputes them
Accessorial the customer's PO doesn't cover. Per diem they'll push back on. We catch the discrepancy before the invoice goes out.
Before Doublefast: invoices hand-keyed days after delivery
Coordinator re-keys delivery data from a PDF. Invoice goes out 3–5 days later. Disputes pile up. Cash cycle stretches to weeks.
After Doublefast: invoice sent the moment the driver taps delivered
Driver taps delivered: invoice generates. Base rate, accessorials, chassis days. Pushed to billing stack in seconds. Zero re-keying. Grey areas (wrong codes, damage notes, missing fields) caught before they leave the system, not disputed two weeks later.
Built for the real world.
Driver picks up at 6am, returns empty at 5pm: chassis hours captured exactly. Per diem starts the day after free time expires; customers dispute a single day. Redelivery noted on paper, never logged in the app. Fuel surcharge at 15% for one customer, 12% for another on the same lane. Invoice rejected because the line item didn't match the customer's PO word for word. We reconcile all of it before it goes out.
* Estimates based on live deployment data. Read the case study →
CBP customs hold
CBP places a hold at discharge; terminal blocks pickup, LFD clock keeps running. We detect it immediately, draft a notification to the customs broker, and queue the appointment to fire the moment it clears.
Container still on vessel
DO arrives before discharge. LFD won't post until after the vessel berths. We monitor discharge status and capture the LFD the moment the terminal sets it.
Chassis split
Container available at PNCT, chassis pool tapped out, so the driver deadheads to Port Newark. We detect the split, adjust the move sequence, and bill the extra chassis time exactly.
Appointment cancelled day-of
Terminal cancels a confirmed slot with no notice, common at APM Newark and eModal. We detect it within seconds and re-snipe immediately.
LFD change after vessel berths
Steamship line adjusts free time; terminal portal and steamship line website show different dates. We pull both, take the tighter date, and re-sort the dispatch queue.
Accessorial mismatch
Redelivery logged on paper, not in the app. Fuel surcharge at 15% when the contract says 12%. We reconcile every accessorial against the delivery confirmation before the invoice goes out.