Automate freight paperwork without automating bad data.
Bills of lading, proofs of delivery, rate confirmations and carrier invoices arrive in different layouts and different quality. Pycas reads the fields, applies rules you define, and holds missing, conflicting or questionable data for a person before approved results move on.
- Start with one document type
- Your validation rules, in writing
- Human review for exceptions
- CSV, QuickBooks bill file or REST API today
AI reads. Rules check. People decide the exceptions.
The document is already digital. The handoff usually is not.
The expensive part is rarely opening the PDF. It is identifying the shipment, re-keying the fields, comparing them with another record, finding what is missing and then entering the approved result somewhere else.
Re-keying
Reference numbers, carrier details, dates, weights, charges and other fields are typed again even though they already exist on the document.
Cross-checking
Someone compares totals, required references, vendors or rate data by eye before a shipment, billing or payment record can move forward.
Exceptions
Faint scans, missing values, duplicate invoices and unusual layouts consume the attention that routine documents should not.
System handoff
Even after a document is reviewed, approved data often has to be copied into accounting, a TMS, an ERP, a spreadsheet or another workflow.
Choose one freight document type first.
A useful pilot does not promise to automate the entire operation at once. Pick the document that creates the most repetitive handling, define the fields and rules that matter, and measure that workflow against the way your team handles it today.
Bill of lading
Target the shipment or reference number, dates, shipper/consignee details, quantities, weights or other fields your operation actually needs.
Proof of delivery
Capture the identifiers and delivery fields you use today, including the imperfect scans and driver photos that create manual work.
Rate confirmation
Extract the rate and reference data your team relies on so it can be validated or used as reference data in a configured workflow.
Carrier invoice
Read header fields and line items, check arithmetic and duplicates, and configure comparisons against the reference data that determines whether the invoice should pass.
Extract first. Validate second. Review only what failed.
Those stages stay separate on purpose. A field that looks plausible to a reader is not automatically an approved business record.
Receive
Upload a PDF, scan or photo, or send a document through the API. Files can be up to 15 pages.
Extract
Pycas readers capture the configured fields, tables and line items from the document.
Validate
Deterministic rules check required fields, arithmetic, dates, duplicates and configured reference data.
Review
Anything that fails a rule is held with the reason shown. A person approves or corrects it.
Deliver
Approved data leaves as CSV/Excel, a QuickBooks bill-import file or REST API output; other integrations are scoped separately.
The platform is already running.
Pycas Document Processing is the production system behind this offer. Freight-specific fields and business rules are configured on top of capabilities that are already live.
- ✓PDF, scan and photo intake, up to 15 pages per file
- ✓Field, table and line-item extraction
- ✓Required-field, arithmetic, date and duplicate checks
- ✓Reference lookups and deterministic rule results
- ✓Human exception-review screen with audit history
- ✓CSV/Excel, QuickBooks bill-import file and REST API output
Your fields, your rules, your destination.
The pilot is where generic document processing becomes your freight workflow. We do not advertise a plug-and-play connector to a TMS we have not built.
- ✓The exact freight fields you need from one document type
- ✓Required references and acceptance rules
- ✓Carrier, vendor, PO or rate-reference matching where the source data is available
- ✓The conditions that should stop a document for human review
- ✓The export or API payload your downstream process needs
- ✓Named TMS, ERP or accounting integration quoted separately when required
Test the workflow on 25 of your own freight documents.
Pick one document type and use representative files, including the awkward scans or layouts that actually take staff time. We will look at what the platform extracts today and identify which fields, validation rules and handoffs belong in a pilot.
Assessment documents follow the free-plan retention policy and are deleted automatically after 30 days; you can delete them yourself at any time from inside the app.
freight documents, free
Start Free — 25 Freight DocumentsRather have us run them with you? Request an assessment and we will set it up on a call.
One freight document type. Three weeks. $2,900.
You send 50–100 representative examples and define what “correct” means. We configure the fields and rules, run the workflow, and hand you results you can check line by line.
- ✓One document type, up to 20 fields plus line items
- ✓Your deterministic validation rules configured and documented
- ✓Up to 500 documents processed during the pilot
- ✓Exception-review screen for your team
- ✓Written results by field and exception type
- ✓Production scope and quote if the workflow earns the next step
50% on signing · 50% on delivery
The pilot fee is credited toward a production build when you proceed within 60 days. Named TMS/ERP integration, multiple document types or broader workflow changes are quoted separately.
Request a Freight Pilot ScopeAlready have a workflow mapped? Include the document type, approximate monthly volume, current destination system and the checks a person performs today.
Prove the document workflow first.
A named integration is useful only after you know what data is trustworthy enough to send into it. The first question is not whether an API exists. It is whether the field extraction, deterministic checks and exception path work on the documents your team really receives.
That is why we start with representative documents and a measurable workflow rather than a long integration project.
Read the freight automation guideA good first measurement: take the same sample documents your team processes manually today. Record which fields are keyed, which checks are performed, which exceptions require judgment and where approved data goes. Use the pilot to compare against that actual process.
Straight answers for freight teams
Do you already connect to my TMS?
Pycas provides CSV/Excel and REST API output today. A named TMS or ERP connector is scoped as an integration engagement rather than advertised as a connector that may not fit your implementation.
Can you compare a carrier invoice with rate data?
Yes when the reference data is available in a form the workflow can query or load. The pilot defines the matching rule, the source of the rate data and what should happen when the values do not agree.
Do you need a template for every carrier or customer?
No fixed visual template is required for each layout. The readers extract configured fields from variable documents, while the validation layer remains deterministic. Representative examples still matter because the pilot should include the layouts and scan quality your operation actually sees.
What happens when the document is unclear?
The workflow is designed to stop questionable data rather than force an answer. Missing values, failed rules and other exceptions can be routed to the review screen with the reason shown for a person to approve or correct.
Should we start with BOLs, PODs, rate confirmations or invoices?
Start with the document type that creates the most repetitive handling and has a clear downstream destination. One document type makes it easier to define success, measure the current process and decide whether the next automation step is worth building.
Bring one freight document workflow.
We will start with the files your team already handles, identify the fields and rules that matter, and tell you whether the free assessment or the fixed-price pilot is the right next step.