Automated Cass Freight GL Coding Review
Every morning, WebRun opens CassPort, reviews the GL allocation data on processed freight invoices, flags any invoice with a missing GL code, an unrecognized cost center, or a code that falls outside your chart of accounts, and adds those exceptions to a Google Sheet queue for your accounting team to resolve.
How do I automatically catch freight invoice GL coding errors before month-end close?
WebRun reviews GL allocation data on every processed freight invoice in Cass each morning, checks each code against your chart of accounts, and adds any missing, unrecognized, or mismatched codes to a Google Sheet exception queue. Your accounting team clears the list before close, keeping freight costs correctly allocated in your ERP every month.
- GL coding errors caught daily rather than discovered at month-end
- Accounting team works a focused exception list, not the full invoice file
- ERP receives a clean, fully coded freight cost file every close cycle
Built for transportation accountants · freight audit teams · logistics controllers · AP and GL teams
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 - review GL allocation data on processed invoices
cassinfo.com
WebRun opens Cass to review GL allocation data on processed invoices. - Open CassPort and pull the latest batch of processed freight invoices with their GL allocation records
- Validate each GL code against your approved chart of accounts and cost center list
- Flag invoices with a blank GL field, an unrecognized code, a mismatched cost center, or an allocation that does not sum to 100 percent
- Capture invoice number, carrier, amount, current GL code, and the reason for the flag on each exception
Done when Every invoice with a GL coding issue is captured with its specific exception type.
-
2
Google Sheets - build and update the GL exception review queue
google.com
WebRun opens Google Sheets to build and update the GL exception review queue. - Append each GL exception as a new row in the GL Coding Review sheet
- Include invoice number, carrier, amount, current GL code, exception reason, and a blank Corrected GL column for your team to fill in
- Update the summary row showing total exceptions, total dollar value, and days until month-end close
Done when All GL exceptions are in the sheet with the summary totals updated.
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 recode invoices in Cass?
No. WebRun surfaces the exceptions in a Google Sheet for your accounting team to review and correct. Corrections are made by a human before the coding file is submitted to your ERP.
Where does it get the list of valid GL codes and cost centers?
You provide your approved chart of accounts and cost center list during setup. WebRun validates every incoming GL allocation against that reference list on each run.
How do we clear exceptions once they are fixed?
Your team updates the Corrected GL column in the sheet and marks the row as resolved. The daily run skips already-resolved rows so the queue only shows open items.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.