The Carriers list — what each carrier row tells you

Find a carrier with search

Type in Search by carrier name to narrow the list. In the walkthrough, typing "Frozen" leaves Frozen and Frozen Food Express. Clear the box to see everything again.

Sender Email — how mail is matched

This column shows which sender addresses belong to the carrier. A pattern like %@ffex.net is a wildcard: it matches any address at that domain, so billing@, ar@ and invoices@ all land on the right carrier. "not set" means KnowDoc can't tell when an email comes from this carrier.

Load # Field — where the load number lives

Each carrier puts the load number in a different place on its invoice, and this column says where KnowDoc looks for it. On the first page alone there are four: invoice_details.load_number, customer_reference_number, bol_number and booking_number. That's why every carrier needs its own profile.

Schema — how the invoice is read

A named schema (Badger Freight Bill, DTS Freight Bill, FFE Freight Bill) tells KnowDoc how to read that carrier's invoices. "No schema" means there's nothing set up to read them yet.

Samples — has it been tested?

Samples shows whether the profile has been tried on a real invoice. In the walkthrough only Badger has one ("1 sample"); every other row says none.

Spot the carriers that need work

Read across each row for gaps. A carrier with no sender email and no schema can't be matched or read, so its invoices end up in Flagged. Start with those, then add samples to the rest.

• Neither (fix first) — Alliance Shippers, Aloha and GIX: no sender email and no schema.
• No sender email — Frozen has a schema, but mail can't be matched to it.
• No schema — BlueGrace is matched by email, but there's nothing to read its invoices with.
• No sample — Every carrier except Badger. Add one so the profile gets tested.

Add a carrier

New Carrier (top right) starts the setup for a carrier that isn't on the list yet. Use the ⋯ menu on a row to work on an existing carrier's profile.