The Solution Bridge Blog
Drake Tax B Ack 7102: review the update and recalculation sequence
Record the affected return and update sequence so a B Ack 7102 is resolved with review, rather than repeated blind transmission attempts.
Applies to: U.S. Drake Tax desktop on Windows, using a tax-year 2025 office workflow. Vendor B Ack guidance is not year-specific. Not Drake Tax Online or a hosted-platform administration guide.
A return can encounter a software-update issue even when someone believes the office installed updates earlier. The useful starting point is the exact acknowledgment and the sequence of work: when the return was calculated, when updates completed and what happened during transmission. Keep those facts together before another person takes over.
This guide covers the U.S. Drake Tax desktop product on Windows, with a hypothetical 2025-return workflow. Confirm the installed year and environment before applying product instructions.
What Drake says about 7102
Drake associates B Ack 7102 with a return transmitted without all available updates. Its documented sequence is to have an authorized user install updates, recalculate the affected return, review accuracy, retransmit and retrieve acknowledgments through EF > Transmit/Receive > Acks Only. If updates are already installed, recalculation and the remaining review steps still matter. Follow Drake’s B Ack 7102 guidance for the exact product process.
Make the handoff specific
Use a compact issue record that a colleague can follow without opening unrelated client files:
- Identify the case: internal client reference, tax year, return type and the complete acknowledgment text.
- Separate observations from assumptions: “Updater completed at 8:40” is more useful than “everything should be current.”
- Assign responsibility: name the person handling the software step and the person approving the reviewed return.
- Record the outcome: document what was checked after each action, including any new message that replaced the original one.
- Keep transmission evidence separate: a technical task marked complete should not be mistaken for a final agency acknowledgment.
Check why the update was missed
For a network installation, Drake says the program must be closed on the workstations and server during scheduled updates. The computer must be on with a Windows user logged in; the user need not be signed in to Drake itself. Sleep or an overnight restart can interrupt the plan. Its detailed power-setting steps are explicitly for Windows 10, so do not assume identical menus elsewhere. See Drake’s scheduled-update notes.
An office can turn those conditions into a closing checklist owned by one person. Record the planned maintenance window and the morning check. If the same interruption repeats, give the administrator the observed pattern instead of changing several settings at once.
A hypothetical office example
A preparer leaves a 2025 return ready for review before the update window. The next morning, a colleague sees 7102. The issue note identifies the client reference and prior work time. The administrator confirms the update outcome; the reviewer then compares the refreshed working return with the retained review copy and documents any differences. Only the approved version moves onward.
The closing note records the later acknowledgment exactly as observed. If anything remains unclear, ownership and the next action remain open. This is a workflow example, not a claim that a particular client’s return was accepted.
Our cloud accounting and bookkeeping services can help organize the source-record handover that supports a clearer review.
Questions about this workflow
Should I repeatedly transmit the same unchanged return?
First complete the documented update and review sequence. Repeated attempts without a recorded change make the issue history harder to follow.
Does installing updates prove the return was accepted?
No. Record the subsequent acknowledgment as a separate outcome.
What belongs in a support handoff?
Include the product year, environment, exact message and a short action timeline. Use the approved secure channel for any client-specific records.
Prepared by The Solution Bridge. Sources checked October 5, 2026. Educational guidance; verify current product instructions and applicable requirements.
Useful answers
Drake FAQs
Does e-file eligibility confirm acceptance?
No. Read the actual acknowledgment for the relevant return and jurisdiction. Eligibility and acceptance are different stages.
Should I retransmit a pending return immediately?
First check its acknowledgments and exact message using Drake's current guidance. A pending transmission needs status review before another attempt.
Does every Drake product use the same instructions?
No. Check whether the article covers Drake Tax, Drake Tax Online or another Drake product, and verify the applicable tax year.
Talk to The Solution Bridge
Let’s make your next step clearer
Tell us what you need help with. For software enquiries, include the product, version and exact message. Please leave out passwords, tax identifiers and financial documents.