Intake
Wherever the document arrives, whether by inbox, SFTP, portal, scan, or EDI, it lands in one queue with source, timestamp, and hash.
- Email & shared mailboxes
- SFTP & carrier portals
- EDI 850 / 856 / 810
- Scanned paper
Intake, classify, extract, validate, route. Every pipeline we build runs these five stages. What changes is the documents at intake, the rules at validate, and the system of record at route.
Wherever the document arrives, whether by inbox, SFTP, portal, scan, or EDI, it lands in one queue with source, timestamp, and hash.
We decide what the document actually is: BOL, invoice, COI, pay app, PO. All trained on your samples, not on a template catalogue.
Extraction tuned to the document in hand. Structured, semi-structured, or a scan someone signed with a marker.
The decision layer. Cross-document checks, tolerance rules, business logic. Exceptions route to the human your team has always used.
Clean data lands in the system of record. Your ERP, your TMS, your PM tool. With the audit artifact attached to the source document.
If yours is not listed, send it. We will tell you whether it belongs in the unstructured, structured, or cross-document track.
These are the documents people send each other. They arrive as PDF attachments, phone-scanned images, or faxed pages. Layouts differ by sender. This is where extraction and classification do the heavy lifting.
Carrier, consignee, weights, piece count, signatures. Carrier-specific layouts, often handwritten on the dock copy.
Line items, HS codes, incoterms, country of origin. Extracted to match against the BOL and customs declaration.
Coverage types, limits, additional insured, expiration. Parsed into your vendor or sub database for compliance tracking.
Schedule of values, work completed this period, retainage, stored materials. Reconciled line-by-line against the contract SoV.
Conditional, unconditional, partial, final. Cross-checked against the pay application and funding amount.
Email PDFs from vendors that have never sent EDI and never will. Matched to PO and receipt inside your ERP.
These documents have a schema on the sender side, but the schema differs per buyer. We normalise the incoming format into one representation your ERP can post against without a new integration per customer.
EDI 850, portal downloads, and email PDFs consolidated into one clean order record per customer and SKU.
Customer-formatted SOs validated against contract pricing, inventory, credit limits, and ship-to master data.
EDI 856 matched against the PO and the receiving scan. Exceptions route before the truck is unloaded, not after.
EDI 810 and portal-exported invoices normalised for three-way match and posting to a niche ERP.
Entry summaries, manifests, arrival notices. Cross-checked against the commercial invoice and country-of-origin rules.
Pulled from customer portals on schedule, parsed into your CRM with the ship date, volume, and spec requirements already extracted.
Single-document extraction is commoditised. The work is in the business logic that compares one document against another against a rulebook, and routes the exception to the right desk.
Tolerance rules set by your controller. Mismatches route to the named AP reviewer for the GL account.
HS code agreement, weight and piece reconciliation, country-of-origin consistency. Clears the shipment before dock release.
Retainage math, SoV reconciliation, lien waiver coverage. PM sees only the exceptions worth their time.
Assembled as one file for the underwriter, with missing documents flagged back to the broker before triage.
Product data sheets cross-referenced against project specifications. Flags for substitution requests and spec deviations.
Signed dock receipts, delivery confirmations. Reconciled with the shipment record and routed to billing.
Clause extraction cross-referenced with the signed order. Renewal dates, liability caps, and data terms land in the CLM with source citations.
Certificate of analysis reconciled with incoming inspection and supplier compliance docs. Trail ready for ISO audit without a scramble.