Automated Cass Duplicate Freight Invoice Detection
Every morning, WebRun opens CassPort and scans incoming invoices for duplicates based on carrier, invoice number, shipment reference, amount, and date. Any matched pair is flagged and logged to a Google Sheet so your AP team can review before payment is released.
How do I automatically detect duplicate freight invoices before payment?
WebRun scans your Cass invoice queue every morning, matching incoming invoices against recent history by carrier, invoice number, shipment reference, and amount. Suspected duplicates are logged to a Google Sheet with the match reason and dollar exposure, giving your AP team a clear review list before any payment is released.
- Duplicate invoices caught before payment rather than recovered after
- AP team reviews a targeted list instead of scanning every invoice
- Running dollar-exposure tally shows audit value at a glance
Built for AP teams · freight audit managers · transportation controllers · logistics finance
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
my.cassport.comin a real browser with your saved login - no setup, no API keys. -
1
Cass - scan invoice queue for duplicate submissions
WebRun opens Cass to scan invoice queue for duplicate submissions. - Open CassPort and navigate to the current invoice processing queue
- Compare each new invoice against recent history using carrier ID, invoice number, PRO number, shipment date, and billed amount
- Flag any pair where two or more invoices share the same carrier and invoice number, or where amount and shipment reference match within a rolling lookback window
- Capture both invoice records and the matching fields for each suspected duplicate
Done when Every suspected duplicate in the current batch is identified with its matching counterpart.
-
2
Google Sheets - log flagged duplicates for AP review
WebRun opens Google Sheets to log flagged duplicates for AP review. - Append each flagged duplicate pair as a new row in the Duplicate Flags sheet, with carrier, invoice numbers, amounts, and match reason
- Mark the newer or lower-confidence invoice as the suspected duplicate
- Update the running total of flagged invoices and estimated dollar exposure at the top of the sheet
Done when All suspected duplicates are logged and the sheet totals are current.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it automatically reject or void duplicate invoices?
No. WebRun flags and logs suspected duplicates in Google Sheets for your AP team to review. No invoice is rejected or returned to a carrier without human approval.
What fields does it use to detect a duplicate?
It matches on carrier ID, invoice number, PRO or shipment reference, amount, and billing date within a configurable lookback window. You can tighten or relax the matching rules during setup.
What happens if a flagged pair turns out to be a legitimate re-bill?
Your AP team reviews each flag in the sheet and clears it. The cleared pair is noted so the same match does not re-trigger on the next run.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.