Step 2.7 — MVMNT → QBO Sync (Carrier Record) with Option B Payee Configuration

File name note

Previously named Step-2.7-EZ-Loader-QBO-Sync-Carrier. Renamed to Step-2.7-MVMNT-QBO-Sync-Carrier on 2026-04-29. Content reflects the actual MVMNT-based process. EZ-Loader migration was cancelled 2026-04-28.

Previous step: Step 2.6 — Carrier Entry in HaulPay Next phase: Phase 3 — Load Lifecycle


🎯 Ideal State

Trigger: Carrier activated in MVMNT (Step 2.5) and entered in HaulPay (Step 2.6).

MVMNT creates the carrier as a vendor in QuickBooks-Online via the real-time two-way sync.

Option B Payee Configuration — Forza’s Global Standard

When a carrier uses a factoring company, the QuickBooks-Online vendor record can be configured two ways. Forza uses Option B globally.

OptionConfigurationForza Uses?
Option B (Forza standard)Carrier is the vendor name. Factoring company’s address is set as payee address. Each carrier has their own vendor record.✅ Yes
Option A (rejected)Factoring company as vendor name. Carriers roll up under one vendor. Bulk payments easier but destroys carrier-level visibility.❌ No

Why Option B:

  • Preserves carrier-level payment visibility in QuickBooks-Online
  • AP aging reports show per-carrier balances clearly
  • Reconciliation with HaulPay’s remittance (sent at carrier level) is straightforward
  • 1099 reporting at year-end works correctly — each carrier receives their own 1099

What to Verify After Sync

CheckExpected
Carrier name synced correctlyMatches MVMNT carrier profile
Payee addressFactoring company address (if factoring) or carrier address (if self-invoicing)
QB Sync ID present in MVMNT carrier profileConfirms link is active

Owner: Concetta (Accounting — spot-check verification).

🤖 SYSTEM AUTOMATION

Sync is fully automated. The Option B configuration is set once globally — Concetta does not revisit this per-carrier.


📍 Current State

  • The MVMNTQuickBooks-Online real-time sync is active (team to confirm exact depth and any manual double-checks happening alongside it).
  • Option B is confirmed as Forza’s convention — carriers are set up as vendor names with factoring company addresses as payee addresses.
  • Option B convention is followed in practice but not formally documented as written policy.

🚧 Gap

  1. Option B convention is confirmed but not documented as formal policy.
  2. No verification routine formally documented for the per-carrier sync spot-check.
  3. No alerting on sync failures — currently caught only when Concetta notices a missing vendor record.

🛠️ Gap Closure Actions

  • Document Option B payee configuration as formal Forza policy Owner: Casey + Concetta | Effort: Low
  • Run a controlled test — activate a test carrier in MVMNT, verify QuickBooks-Online vendor record appears correctly with Option B payee configuration Owner: Casey + Concetta + James | Effort: Low
  • Document the carrier sync verification SOP Owner: Casey + Concetta | Effort: Low
  • Build an n8n watcher to alert on missing carrier QB Sync IDs and route to Teams (per the automation architecture) Owner: Casey | Effort: Medium