Automated Estate Transaction Anomaly Detection
Every morning, WebRun opens EstateExec and scans transactions posted in the past 24 hours for anomalies such as duplicate amounts, transactions in unexpected categories, or amounts above your configured threshold, logs each flag to a Google Sheet, and posts the executor an immediate Slack alert for any issue found.
How do I automatically detect unusual transactions in an estate administration account?
Every morning, WebRun scans EstateExec for transactions from the past 24 hours that match anomaly patterns such as duplicates, amounts above your threshold, or unexpected payees, logs each flag to a Google Sheet, and posts the executor a Slack alert immediately. Nothing is blocked or reversed. All action stays with the executor.
- Unusual transactions are surfaced within hours rather than caught at month-end
- A running exception log builds an audit trail of every flag and its resolution
- Clean-scan days are confirmed automatically so the executor knows the check ran
Built for estate executors · probate attorneys · estate accountants · trust officers
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
www.estateexec.comin a real browser with your saved login - no setup, no API keys. -
1
EstateExec - scan recent transactions for anomalies
estateexec.com
WebRun opens EstateExec to scan recent transactions for anomalies. - Open EstateExec and navigate to the recent transaction list
- Review all transactions posted in the past 24 hours
- Flag any transaction that matches an anomaly pattern: duplicate amount and date, amount above the configured threshold, transaction in an unexpected category, or a distribution to an unrecognized payee
Done when All anomalous transactions from the past 24 hours are identified with the reason for the flag.
-
2
Google Sheets - log each flagged transaction with the anomaly reason
google.com
WebRun opens Google Sheets to log each flagged transaction with the anomaly reason. - Open the exception log spreadsheet
- Append a row for each flagged transaction with the date, amount, category, payee, estate name, and the anomaly reason
- Mark each as unreviewed until the executor confirms it is legitimate or flags it for correction
Done when Every flagged transaction has a row in the exception log with its anomaly reason.
-
3
Slack - alert the executor to any flags found
slack.com
WebRun opens Slack to alert the executor to any flags found. - Post a Slack alert to the executor's channel with a count of flags found
- List each flagged transaction with the amount, payee, estate name, and the anomaly reason
- If there are no flags, send a brief daily confirmation that the scan ran clean
Done when Executor has a Slack alert listing all exception flags found in the past 24 hours.
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 block or reverse any suspicious transaction automatically?
No. WebRun only flags and reports anomalies. It cannot block, reverse, or modify any transaction in EstateExec. All corrective action is taken by the executor or their attorney.
How does it define a large or unusual transaction?
You configure the thresholds when you set up the workflow, such as any single distribution above a set dollar amount or any transaction to a payee not on the approved list in EstateExec.
What if the same transaction is flagged multiple days in a row?
WebRun checks the exception log each morning and skips any transaction already flagged and awaiting executor review, so each item appears only once until it is resolved.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.