All templates

Automated Freight Factoring Exception and Anomaly Flags

Every morning, WebRun opens OTR Solutions and scans recent transactions for exceptions: duplicate invoice numbers, fuel advances above your threshold, invoices lacking a matched rate confirmation, and carriers submitting an unusually high volume of loads. It logs every flag to a Google Sheet and posts an anomaly digest to Slack for your team to review.

Runs on WebRun · Strict Lockdown policy
Every day at 6:00 AM WebRunorchestrates each step
1 OTR Solutions scan transactions for exception patterns
2 Google Sheets log flagged anomalies with details
3 Slack post anomaly digest for team review
In short

How do I automatically detect unusual or suspicious activity in my freight factoring account?

WebRun scans OTR Solutions every morning for exception patterns: duplicate invoice numbers, fuel advances above threshold, invoices missing rate confirmations, and unusual carrier submission spikes. Every flag is logged to a Google Sheet and posted as a Slack digest so your operations team can investigate before any irregular transaction is funded.

  • Duplicate invoices and oversized fuel advances caught within hours of submission
  • Full anomaly log in Google Sheets for audit and pattern analysis
  • Operations team notified every morning before the business day starts

Built for freight factoring operations managers · carrier account teams · trucking finance directors · fleet compliance officers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens client.otrsolutions.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    OTR Solutions - scan transactions for exception patterns
    otrsolutions.com
    WebRun in OTR Solutions: scan transactions for exception patterns
    WebRun opens OTR Solutions to scan transactions for exception patterns.
    • Open OTR Solutions client portal and review transactions submitted in the last 24 hours
    • Check for duplicate invoice numbers submitted more than once
    • Identify fuel advance requests above the configured threshold (default 50 percent of linehaul)
    • Flag invoices without a matching rate confirmation on file
    • Note any carrier whose submission volume is more than double their 7-day average

    Done when All exception patterns in the last 24 hours are identified and documented with amounts and carrier names.

  3. 2
    Google Sheets - log flagged anomalies with details
    google.com
    WebRun in Google Sheets: log flagged anomalies with details
    WebRun opens Google Sheets to log flagged anomalies with details.
    • Append each flagged anomaly to the exception tracking Google Sheet
    • Record the date, carrier name, exception type, invoice or transaction reference, and amount
    • Mark high-priority flags where a fuel advance exceeds the threshold or a duplicate was already funded

    Done when All anomalies are logged in the tracking sheet with type, amount, and priority level.

  4. 3
    Slack - post anomaly digest for team review
    slack.com
    WebRun in Slack: post anomaly digest for team review
    WebRun opens Slack to post anomaly digest for team review.
    • Post a daily anomaly digest to the operations Slack channel
    • Group flags by exception type: duplicates, oversized advances, missing rate confirmations, and volume spikes
    • Tag the accounts team for high-priority flags that may require a hold or reversal decision

    Done when The operations team has this morning's anomaly digest in Slack with high-priority flags tagged.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
client.otrsolutions.com
ScheduleRuns automatically on this cadence
Every day at 6:00 AM
DeliveryHow each run's result reaches you
Anomaly digest · Slack
OutputWhat each run produces - A daily anomaly digest in Slack listing exception types, amounts, and carriers, plus an exception tracking Google Sheet for audit and trend review.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it block or reverse a transaction automatically when an anomaly is detected?

No. WebRun flags anomalies and notifies your team in Slack but takes no financial action on its own. Any hold, reversal, or escalation is a human decision made after reviewing the flag.

What counts as an oversized fuel advance?

OTR Solutions allows fuel advances up to 50 percent of the linehaul. WebRun flags any advance request that exceeds the threshold you configure during setup, defaulting to the OTR Solutions maximum.

How does it detect duplicate invoices?

It compares each invoice number submitted in the last 24 hours against the prior 30-day history in OTR Solutions. Any invoice number that appears more than once is flagged as a potential duplicate for your team to verify.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.