Extract data from rate confirmations
Unstract reads broker-carrier rate confirmations in every broker's layout, along with load tenders and transportation requests, whether they come back signed by fax or arrive as PDFs, and sends the agreed rate and load details to your TMS or ERP.
lumper receipt in the packet? — Tessa
NFP RATE CON 11/26 · SUBJECT TO BROKER-CARRIER AGREEMENT
{ "load_number": "NFP-260418", "broker": "Northgate Freight Partners", "carrier": "Red Cedar Transport", "carrier_mc": "MC 1180452", "equipment": "53' Dry Van", "pickup_date": "11/04/2026", "linehaul_usd": 2450, "fuel_surcharge_usd": 318.5, "lumper_usd": 175, "total_carrier_pay_usd": 2943.5}
Trusted by logistics and supply chain teams around the globe
Each broker sends the load on its own paper
The rate con for one load can look nothing like the next. A week of them in a carrier's inbox or a broker's back office looks like this.
Printed, signed by dispatch and faxed back to the broker
Three brokers, three layouts, the same fields
Truck, trailer and a revised rate written in at dispatch
A factoring packet scanned as one PDF
Load tenders and transportation requests with several stops
Billing staff retype the rate, the accessorials and the load number from each confirmation, and a missed lumper or a wrong fuel surcharge gets the invoice short-paid or rejected by the factor.
Unstract reads every rate confirmation, pulls the load and rate fields you name, checks the carrier invoice against them, and sends the record to your TMS or ERP.
Read, extract and audit every load's agreed rate
Parsing, extraction and automation are three products that each work on their own. Pick the one your billing desk needs first and add the others as load counts grow.
Parse any rate confirmation into text with its layout intact
Brokers put the linehaul, the fuel surcharge and the accessorial terms in different boxes, and the signed copy often comes back as a fax or a phone photo. LLMWhisperer keeps every box where it was printed, so the detention terms stay apart from the lumper charge and the pickup window stays with its shipper.
Use it as a rate con parser that feeds your own LLM, or as the first step in a longer billing or audit process.
Learn more about LLMWhispererRate confirmation data extraction into one load record
Write a prompt naming the fields you need, and every rate confirmation, load tender or transportation request returns the same JSON, whichever broker issued it. Nobody builds a template for a new broker. When the carrier invoice bills more than the rate con allows, the charge comes back flagged with the agreed figure beside it.
Deploy it as an API, as an ETL pipeline, or as one step inside a freight audit run.
Learn more about Document StudioRun the freight audit from invoice to approved payment
Describe how your team audits carrier bills against the rate confirmation, in plain English, and Flow's agents build the workflow: invoices and PODs collected from email and carrier portals, each one matched to its rate con, charges compared, delivery confirmed. Clean bills post to your TMS or ERP, such as Oracle Transportation Management or NetSuite. You approve the workflow once, and every load runs through it the same way.
You choose where it stops: an overcharge above your tolerance, a duplicate PRO number, a missing POD, an exception written on the POD. Those loads go to a freight auditor or AP with the rate con open next to the invoice.
Learn more about FlowPull the agreed rates off your rate cons today
Start for free to parse and extract your rate confirmations now. A consultation sets up the full freight audit around your loads.
Rate cons, tenders and the paperwork billed against them
Documents
- Broker-carrier rate confirmations
- Revised rate confirmations
- Motor carrier load tenders
- Transportation requests
- Dispatch sheets
- Carrier freight invoices
- Bills of lading
- Proof of delivery receipts
- Lumper and scale receipts
- Accessorial approvals
- Factoring schedules of accounts
- Any other broker's rate con layout
Fields captured
Built for everyone who books, hauls and funds the load
Carrier invoices checked against the rate con you issued, so a padded fuel surcharge or an unapproved accessorial never reaches carrier pay.
Every broker's rate con read the moment it is signed, so billing starts from the agreed rate instead of whatever the driver remembers.
Rate cons from dozens of brokers filed in one format for each truck you dispatch, with pickup windows and appointments ready for the driver.
Rate con, BOL, POD and invoice in each packet checked against each other before you advance funds on the load.
Fewer short pays, faster carrier billing
Rates, margins and payout details kept private
A rate confirmation shows what a broker pays the carrier for a lane, and set beside the shipper's rate it gives away the broker's margin. Factoring packets add the carrier's bank and remit-to details, and the rate con names the driver and the truck. Fraudsters who get these papers redirect carrier payments or pose as the carrier to pick up the load.
- Encrypted in transit and at rest.
- Rate confirmations are never used to train models.
- Access by role, customer and carrier, with every corrected charge and released exception logged against the load number.
- Retention you set: rate cons and factoring packets are deleted on the schedule your broker-carrier agreements call for.
- Brokers and factors that keep carrier banking data on their own servers can run Unstract self-hosted.
What brokers, carriers and factors ask first
Start by extracting the load and rate fields, then automate around them. Document Studio returns the load number, parties, stops, linehaul, fuel surcharge and accessorials as JSON from each rate con. Flow then collects the rate cons from the inbox, matches them to the carrier invoice and POD, and posts the result to your TMS or ERP.
A rate confirmation parser turns the broker's PDF or fax into text a system can use. LLMWhisperer reads the page with its boxes kept in place, and Document Studio maps that text to your fields, so a detention term lands in its own field and never merges into the linehaul.
Yes. Fields are found by what they mean, not where they sit on the page, so a broker you have never hauled for needs no set-up. Every rate con comes back in the same schema.
Yes. Motor carrier load tenders and transportation requests return in the same schema as rate cons, including multi-stop tenders with an appointment for each stop.
Yes. Linehaul and fuel surcharge on the invoice are compared with the rate con, and each accessorial is checked against the agreed terms. Detention billed inside the free hours, or a lumper with no receipt, comes back flagged with the agreed figure beside it.
Yes. The invoice, rate con, BOL and POD in one PDF are split apart and read, then checked against each other: the same load number, the invoice total within the agreed rate, and a signed POD. A packet that fails any check waits for a person.
Yes. LLMWhisperer reads fax noise, skewed scans and phone photos, and picks up handwritten truck numbers and revised rates next to the printed fields. A value it cannot read with confidence goes to a person with the page.
The load waits in a review queue. The auditor sees the invoiced charge, the agreed figure and the box on the rate con it came from, then approves it, corrects it or sends a dispute to the carrier. The other loads keep moving.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Rate cons are encrypted, never used for training and kept only as long as you choose, and teams can self-host. The Trust Center lists every control.
Not for Flow. In a consultation we build the audit around your brokers' rate cons, your tolerance rules and your TMS or ERP, and most teams run live loads within days. To try extraction now, start for free with a single rate confirmation.
Bring a week of rate cons to the consultation
Signed rate cons from your busiest brokers, load tenders and a few factoring packets. You watch each load read live, with the rate, the accessorials and the invoice compared on screen.