Carrier Rate Confirmation Parsing & Extraction
For Carrier billing and dispatch coordinators
Prepare load reference, lane, agreed rate and accessorial terms from a rate confirmation with fields you can edit. Billing logic external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- load reference
- DEMO-LOAD-0042
- broker name
- Example Broker - synthetic
- carrier name
- Example Carrier - synthetic
- pickup date
- 2026-09-30
- origin address
- 100 Example Way, Sample City, CA 00000
- destination address
- 200 Example Avenue, Sample City, NV 00000
- linehaul rate
- 1250
- accessorial terms text
- Accessorial terms text explicitly printed in the original synthetic source for reviewer context.
{
"load_reference": "DEMO-LOAD-0042",
"broker_name": "Example Broker - synthetic",
"carrier_name": "Example Carrier - synthetic",
"pickup_date": "2026-09-30",
"origin_address": "100 Example Way, Sample City, CA 00000",
"destination_address": "200 Example Avenue, Sample City, NV 00000",
"linehaul_rate": 1250,
"accessorial_terms_text": "Accessorial terms text explicitly printed in the original synthetic source for reviewer context."
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
A rate confirmation arrives for carrier billing and dispatch coordinators. The next step needs load reference, lane, agreed rate and accessorial terms, recorded under the correct document reference before the information enters your shipment or billing review system.
A rate confirmation includes detention terms but no approved detention amount. Capture the terms as text and leave later billing calculations external. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Rate confirmation PDFs
- Scanned or photographed rate confirmation pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking load reference, broker name, carrier name, your application maps the reviewed record into your shipment or billing review system. Keep the original document reference with the result. Billing logic external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
load_reference | string | Load reference exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
broker_name | string | Broker name exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
carrier_name | string | Carrier name exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
pickup_date | date | Pickup date explicitly printed in this rate confirmation. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
origin_address | string | Origin address exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
destination_address | string | Destination address exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
linehaul_rate | currency | Linehaul rate explicitly labeled in this rate confirmation. Preserve its sign and stated currency; do not calculate a missing amount. |
accessorial_terms_text | string | Accessorial terms text exactly as printed in this rate confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- A rate confirmation includes detention terms but no approved detention amount. Capture the terms as text and leave later billing calculations external.
- Check pickup date against their own printed labels; leave an unstated date empty instead of deriving it.
- Check linehaul rate for signs, decimal placement and stated currency before any downstream calculation or posting.
Prove the fit on a representative batch.
Test rate confirmation examples from the layouts your team actually receives. Include the exception described here: A rate confirmation includes detention terms but no approved detention amount. Capture the terms as text and leave later billing calculations external. Compare the extracted load reference, broker name, carrier name and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when rate confirmation intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for carrier billing and dispatch coordinators. Bring difficult rate confirmation samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about carrier rate confirmation intake
Which fields can I capture from a rate confirmation?
The starter schema contains load reference, broker name, carrier name, pickup date, origin address, destination address, linehaul rate, accessorial terms text. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in carrier rate confirmation intake?
A rate confirmation includes detention terms but no approved detention amount. Capture the terms as text and leave later billing calculations external. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your shipment or billing review system?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Billing logic external.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.