Track the states that need a nil escheat report
Every month, WebRun opens Simple Escheat, works out which states require a negative or nil report when you have no property to escheat, checks whether each has been filed for the cycle, books calendar events for the ones due, and posts the team a Slack list of the nil reports still owed.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track negative or nil escheat reports across states automatically?
Every month, WebRun opens Simple Escheat, works out which registered states require a negative report when you have nothing to escheat, and checks whether each is filed for the cycle. It books calendar events for the ones due and posts the team a Slack list of the nil reports still owed, so a required nil filing is never overlooked.
- Required nil reports are tracked even when there is no property to file
- Every outstanding negative report sits on the calendar with a reminder
- The team sees exactly which states still owe a nil filing each cycle
Built for compliance teams · unclaimed property analysts · controllers · multi-state filers
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
simpleescheat.comin a real browser with your saved login - no setup, no API keys. -
1
Simple Escheat - find states needing a nil report
WebRun opens Simple Escheat to find the states that require a nil report. - Open Simple Escheat and list the states you are registered in that require a negative report when there is no property to escheat
- For each, check whether you have property to file this cycle or whether a nil report is the requirement
- Note which nil reports are already filed and which are still outstanding for the cycle
Done when Every state requiring a nil report is identified and marked filed or outstanding for the cycle.
-
2
Google Calendar - book the nil-report deadlines
WebRun books each outstanding nil-report deadline on the shared calendar. - Open the shared compliance calendar in Google Calendar
- Create or update an event for each state whose nil report is still due, titled with the jurisdiction and cycle
- Add reminders ahead of the deadline so the team has time to file the negative report
Done when Every outstanding nil report has a calendar event with a reminder ahead of its deadline.
-
3
Slack - list the nil reports still owed
WebRun posts a Slack list of the nil reports still owed this cycle. - Post the team a short list of the states whose nil report is still owed this cycle
- Sort by deadline so the nearest jurisdiction stands out first
- Note how many nil reports are already filed so the remaining count is clear
Done when The team has this month's list of nil reports still owed in Slack.
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
Does it file the negative reports itself?
No. WebRun only tracks which nil reports are owed, books the deadlines, and posts a Slack list. Filing each negative report stays with your team, so nothing is submitted to a state on its own.
Why bother tracking nil reports at all?
Because several states require a negative report even when you have nothing to escheat, and missing one can trigger penalties. Tracking them means a required nil filing is never overlooked just because there was no property that cycle.
How does it know which states need a nil report?
It reads your registered states in Simple Escheat and applies each jurisdiction's negative-report rule, so only the states that actually require a nil filing appear on the owed list.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.