Step 4.7a — Factoring Rejection Handling
Triggered from: Step 4.7 when HaulPay rejects a submitted invoice. Returns to: Step 4.6 after resolution and resubmission.
Note
Rejections are rare per tech stack meeting: “Doesn’t happen.” But when they do occur, unresolved rejections defer cash flow. Every missed week of resolution is a missed advance.
🎯 Ideal State
Rejection Reasons and Resolution Paths
Reason Resolution Path Missing document Complete document set (Step 4.1), resubmit Data error (amount, reference, Shipper name mismatch) Correct in EZ-Loader/QuickBooks-Online, regenerate invoice, resubmit NOA not on file with Shipper Resolve NOA (Step 1.8), resubmit when acceptance received Shipper credit exceeded Wait for Shipper payment to free credit, negotiate higher limit with HaulPay, or move load to self-finance Shipper account flagged / concerns Escalate to Nick (Founder/CEO) — may indicate credit deterioration Rejection Response SOP
- HaulPay delivers rejection notice (email or portal alert). Concetta logs the rejection in EZ-Loader load notes and a central tracking mechanism.
- Concetta diagnoses the rejection reason.
- Concetta executes the appropriate resolution path.
- Resubmit to HaulPay per Step 4.6 mechanics.
- If rejection relates to Shipper credit or account status, escalate to Nick (Founder/CEO) immediately — this is a signal of deteriorating Shipper risk, not just a document issue.
Rejection Metrics to Track
- Rejection rate (% of submitted invoices)
- Rejection reason distribution (which issues recur)
- Time from rejection to resubmission
- Resubmission success rate
Patterns in rejection reasons point to upstream process issues — missing documents repeatedly means Step 4.1 completeness gate needs tightening; reference number errors mean Step 3.1 enforcement needs Step 1.6 configuration.
Owner: Concetta (primary). James (if scope/load data is the issue). Nick (Founder/CEO) if Shipper credit or risk is the issue.
🛑 HARD GATE:
Rejected invoices do not generate advance funds or customer-facing invoices. Every unresolved rejection is a deferred collection. Resolution speed directly affects cash flow.
📍 Current State
- Rejections are rare per tech stack meeting.
- No documented rejection-response SOP.
- No tracking mechanism for rejection metrics.
- When rejections occur, Concetta handles case-by-case.
🚧 Gap
- No documented rejection-response SOP.
- No rejection tracking or metrics.
- No Nick (Founder/CEO) escalation path for credit-related rejections.
🛠️ Gap Closure Actions
- Document the rejection-response SOP with the 5-step resolution process and reason-based resolution paths Owner: Casey + Concetta | Effort: Low
- Establish rejection tracking (extends the submission tracking from Step 4.6 Gap Closure 3) Owner: Casey + Concetta | Effort: Low
- Establish Nick (Founder/CEO) escalation protocol for credit/risk-related rejections Owner: Casey + Nick + Concetta | Effort: Policy
- Add rejection metrics to Phase 7 monitoring cadence Owner: Casey + Concetta | Effort: Low