Vendor invoices into CargoWise, without the keying.

Carrier and landside vendor invoices as PDF or XML, booking confirmations, recipient-created tax invoices, and forwarded eDocs. Each vendor has its own parser, written against that vendor’s real documents rather than a generic template.

Documents arrive by email to a dedicated address, by API, or through a batch inbox where a whole morning’s invoices can be dropped in at once. Inbound email is checked against sender authentication before it is accepted.

Every document passes three gates. The first confirms the document is structurally sound. The second checks the fields that matter: reference formats, required values, GST and totals that reconcile, and charge codes that are known.

The third compares each charge against that vendor’s rate history and flags the variance as minor, moderate, or major. The history builds itself from invoices already posted, so the check gets sharper the longer the system runs.

FlowDocs connects through eAdaptor, CargoWise’s own integration interface. It looks shipments up by bill of lading, container number, or reference, and posts the matched charges onto the right job.

The connection runs both ways: it also attaches the source document as an eDoc, creates jobs from booking confirmations, and publishes rate cards into CargoWise’s native rating.

A document that scores below the confidence threshold does not post. It goes to a review queue with the reason attached, and an operator resolves it, including entering the shipment by hand when matching fails.

It refuses to post an invoice with an unmapped charge code or a missing creditor code, and parks it instead. Every lookup, post, and approval is written to an audit log.

Each customer runs in their own environment, in their own AWS account, in the Sydney region. Your documents and credentials are not pooled with anyone else’s.

We are working with a small number of design partners as FlowDocs grows toward a broader platform.