Last updated
Stop Refreshing Drake and Lacerte: Alerts When E-File Comes Back Accepted or Rejected
You transmitted a batch. Now the office is waiting on the IRS or the state. The acknowledgement will not arrive as a Slack message. It will flip a cell in Drake, Lacerte, UltraTax, or ProSeries from pending to Accepted—or Rejected. Missing that for an hour in March is a real operational problem.
The problem: acknowledgements live in the desktop grid
CPAs, enrolled agents, and seasonal tax offices do not “check a website” for each client’s e-file ack. They work inside professional packages. After transmit, status sits in an EF / e-file / transmission window until MeF or the state transmitter writes back. Rejected needs a same-day fix. Accepted lets you stop hovering and move to the next return.
Visualping and Distill watch public URLs. They cannot see your licensed tax software. If the firm’s transmitter email is slow, noisy, or missing, the grid on the workstation is still the contract.
Use native signals first
If your vendor or transmitter already sends a reliable email or in-product alert for every ack, use that. Some Drake and Intuit workflows can email; coverage varies by product, bank products, and how the office is set up. This article is for the common case: you find out by looking at the screen.
Do not scrape IRS.gov for client data. Do not share a full return on a display in a public area. The job is “tell me the grid changed to a terminal status,” then you handle the reject codes in the software you already pay for.
Watch the transmission window
MonitorSensei runs in the browser. You describe what the finished status looks like, share that window (or the display that shows it), and get a browser or push notification when the description matches. Two trackers are usually better than one:
- “The EF transmission status shows Accepted.”
- “The acknowledgement column shows Rejected.”
Copy the labels from your build. Drake Tax, Lacerte, UltraTax CS, and ProSeries do not share one caption. Describe the end state, not “when it changes from Pending.” If you only care about rejects during crunch week, run the Rejected tracker alone.
Keep the status column visible. A covered window cannot be read. After the ping, open the return and work the reject—the alert is not the fix.
How to set it up during a filing day
- Transmit the batch as you always do.
- Leave the EF / e-file status grid in view.
- Create the tracker(s) in MonitorSensei with Accepted and/or Rejected wording from that grid.
- Share that window only, if the browser lets you pick it.
- Start tracking and go back to the next organizer. Handle acks when you are pinged.
Click-by-click account setup is in the tracker setup guide. The description is the only part that is tax-specific.
Privacy, compliance, and what this is not
Tax returns are sensitive. Share the smallest surface that shows status. MonitorSensei does not install on the PC, does not read your tax database, and does not replace IRS e-Services, your vendor’s ack reports, or written information-security procedures. It is not for watching staff screens. It is for your workstation while you wait on a batch you transmitted.
If firm policy forbids any screen capture of tax software, do not use this pattern. Follow the policy.
Same idea outside tax season
Long jobs that finish as a window you already have open:
Do not wait until the next time you glance at EF
Transmit. Describe Accepted or Rejected. Get pinged. Fix rejects while they are still cheap. Use vendor email when it is trustworthy; watch the grid when that is how your office actually finds out.