Who it's for · Desks whose invoices already live in email
Email-forward freight invoice intake
FTL bills do not start in a portal. They start as a carrier email with PDFs attached. Jorora intake lets you forward that thread to your organization address and run the same Freight Audit rules you would get from a drag-and-drop upload.
Why
Why intake has to be email-native
The inbox is the system of record
Asking the desk to download, rename, and re-upload every packet is how tools get abandoned by week two.
Same rules as upload
Forwarding is not a lesser path. Extraction, pay rules, duplicates, and credits match the in-app packet.
AP automation still expects a PO
Email PDFs with rate cons are exactly where generic AP intake fails. This job is that gap.
No TMS required to start
If the bill can be forwarded, the control can run. Integrations can come later.
How to
How to forward an FTL packet
Stay in the inbox where the PDFs already land.
Step 1
Set up the organization intake address
Each org gets a forward target. Keep invoice + rate confirmation on the same thread when you can.
Step 2
Forward the carrier email
Do not strip the PDFs. Detention and lumper evidence can ride along when those lines are in play.
Step 3
Let Freight Audit run
Same extraction and versioned rules as upload. You still review Approve / Needs Review / Reject.
Step 4
Act without leaving the pay stack
Dispute draft on reject. Copy fields or CSV on approve. The inbox started the job; AP still finishes remittance.
Workflow
Intake is not a TMS replacement
Email-forward is how the packet enters Jorora. Dispatch, tracking, and payment stay where they are. The job is: do not make a human become the integration layer between Gmail and a pay decision.
Pains
What email desks do today
- Downloading PDFs just to upload them again
- Losing the rate con that was three messages up the thread
- Generic AP capture that cannot read a rate confirmation
- Two tools for “email” and “audit” that never share rules
Jobs
What forward intake does
- Accept the packet from the inbox
- Apply the same pay rules as upload
- Keep credits consistent across paths
- Return a decision without a TMS project
Evidence
Why this URL deserves a rank
- Broker FTL reality is email + PDF, not EDI-first
- Same credits on both intake paths — no surprise metering
- Pairs with every other Freight use case on this hub
FAQ
Frequently asked questions
No. Same extraction, same rules, same credits. Attachments still need to be readable.
Forward both, or upload the missing file in the app and attach it to the same decision.
No. Humans authorize remittance after the decision.
Yes. Many desks mix both: forward the noisy inbox, upload the clean packet from a shared drive.
Related
Use cases, guides, and landings
Guides
Forward one real carrier email.
Two free credits. Upload or forward a real FTL packet.
