Step 2.6 — Carrier Entry in HaulPay
Previous step: Step 2.5 — Carrier Profile Review and Activation Next step: Step 2.7 — EZ Loader → QBO Sync (Carrier)
⚠️ Sequence Critical
HaulPay entry must be complete before a carrier’s first load is dispatched — not after. Retroactive setup after dispatch creates payment delays that are difficult to resolve.
🎯 Ideal State
Trigger: Carrier activated in EZ-Loader (Step 2.5).
When Forza pays a carrier (or their factoring company) for a delivered load, the payment routes through HaulPay. HaulPay needs the carrier record in their system before the first load — not after.
Data entered into HaulPay:
Data Field Source Carrier company name EZ-Loader carrier profile MC# / DOT# EZ-Loader carrier profile Payee information Carrier directly (if self-invoicing) or their factoring company Factoring company name EZ-Loader payee link Factoring company contact info EZ-Loader payee link NOA from the carrier’s factoring company Uploaded to EZ-Loader carrier documents Owner: Concetta (Accounting).
🤖 SYSTEM AUTOMATION:
🛑 HARD GATE:
📍 Current State
🚧 Gap
🛠️ Gap Closure Actions
- Document the HaulPay carrier entry SOP Owner: Casey + Concetta | Effort: Low
- Establish a policy that HaulPay entry must be complete before first-load dispatch Owner: Casey + Concetta + James | Effort: Policy
- Evaluate whether HaulPay offers any API or bulk-load option for carrier records Owner: Casey + HaulPay account team | Effort: Low
- Track time-from-activation-to-HaulPay-entry metric Owner: Concetta | Effort: Low