Automated Drake E-File Rejection Worklist
Every morning, WebRun opens Drake, processes new e-file acknowledgements, finds the returns that came back rejected with their reject codes, logs each one to a Google Sheet worklist with the preparer, and posts the team a Slack list of returns to fix and resend.
How do I turn e-file rejections into a worklist automatically?
Every morning, WebRun opens Drake, processes the latest e-file acknowledgements, and pulls out the returns that came back rejected along with their reject codes. It logs each one to a Google Sheet worklist with the preparer and posts the team a Slack list of what to fix and resend, so rejections never sit unnoticed.
- Rejected returns surface the morning after transmission, not days later
- Each rejection lands on a worklist with its code and a plain-language note
- No accepted return clutters the list, so preparers act only on what failed
Built for tax practices · accounting firms · CPA firms · tax preparers
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.drakesoftware.comin a real browser with your saved login - no setup, no API keys. -
1
Drake - process acks and find rejections
drakesoftware.com
WebRun opens Drake to process acknowledgements and find rejected returns. - Open Drake and run EF then Process Acks to load the latest acknowledgements
- Search the EF Database and capture every return with an R rejected status and its reject code
- Note the client, return type, preparer, and the reject code explanation for each
Done when Every newly rejected return has been listed with its reject code and preparer.
-
2
Google Sheets - log the rejection worklist
google.com
WebRun logs each rejected return with its reject code and preparer. - Log each rejected return with its client, type, preparer, reject code, and explanation
- Mark accepted and pending acknowledgements separately so the worklist stays focused on rejections
- Keep a running record so repeat reject codes become easy to spot
Done when The rejection worklist sheet reflects today's acknowledgements.
-
3
Slack - report what needs fixing
slack.com
WebRun posts the day's e-file rejection worklist to Slack. - Post the team a short list of returns that came back rejected today, grouped by preparer
- Include the reject code and a plain-language note on what it means
- Leave it for each preparer to fix, recalculate, and resend the return in Drake
Done when The team has today's rejection worklist 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
Will it refile or resend returns on its own?
No. WebRun reads the acknowledgements and builds the worklist only. Every rejected return is left for a preparer to fix, recalculate, and resend in Drake, so nothing is retransmitted to the IRS without a person doing it.
How does it tell rejections from acceptances?
It reads the acknowledgement status in the Drake EF Database, where A means accepted, P means processing, and R means rejected. WebRun pulls the R returns onto the worklist and notes the reject code for each.
Does it explain what each reject code means?
Yes. WebRun pairs each reject code with the explanation from Drake and adds a plain-language note, so a preparer can see at a glance what failed and what to correct before resending.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.