How does a new acquisition entity prepare for its own e-file authorization?

New-entity e-file readiness means that the entity intended to perform the relevant electronic filing activities has the applicable IRS authorization, identified responsible people, controlled access, and a tested operating workflow. It is distinct from buying client relationships, hiring preparers, obtaining an EIN, or licensing tax software.

What must a new acquisition entity establish?

Establish the actual provider arrangement for the transaction before promising that the buyer can electronically file acquired client work. The seller’s successful historical filing activity does not establish authorization for a different buyer entity.

The buyer hub places this question in closing readiness. The tax practice acquisition guide addresses the larger service and credential review; here the focus is the provider that will originate or otherwise perform the relevant e-file activities.

Map the legal entity, taxpayer identification information, location, intended provider roles, principals, responsible officials, and operating staff. Have the transaction advisers and responsible provider review the actual structure rather than assuming that a trade name determines the answer.

Keep unresolved authorization separate from technical configuration. A software environment can be accessible and apparently ready while the necessary provider approval remains incomplete.

Can the buyer use the seller’s EFIN?

A buyer should not treat the seller’s EFIN as a transferable acquisition asset. IRS EFIN questions and answers states that EFINs cannot be transferred to another entity or used by the purchaser of the business.

A seller’s continuing consultation does not by itself authorize the buyer entity to use that number. A purchase agreement, transition-services clause, or retained login cannot replace the IRS provider requirements.

Where parties propose a continuing authorized service arrangement, obtain specific guidance about its permissibility, provider responsibilities, and facts. Do not disguise unauthorized buyer activity as seller assistance or assume that a seller’s presence solves an entity mismatch.

Identify the precise proposed activity. Preparing a return, originating an electronic submission, transmitting data, reviewing work, and providing client support are different functions. Assigning each to an accountable authorized workflow makes gaps visible.

When should an acquisition application be prepared?

Prepare early enough to understand the applicable submission requirements, complete the information, and address questions before the intended production date. The correct timing depends on the actual acquisition and provider situation.

IRS Publication 3112 application and participation guidance states that providers acquiring an existing IRS e-file business must submit a new application and proof of acquisition within the period beginning forty-five days before and ending thirty days after the acquisition. It also directs providers to contact the IRS before filing-season transfers for transition assistance.

The publication advises allowing for application processing that may take up to forty-five days. Those instructions should not be interpreted as a guaranteed approval date or permission to use the prior provider’s number while waiting.

Determine what evidence can be prepared before the acquisition and what requires completed transaction documents. Maintain a submission record and tracking information rather than describing the application as complete because someone began entering data.

For other ownership or organizational changes, obtain guidance on the relevant application or update requirements. This guide addresses a new buyer entity and does not substitute a blanket rule for every possible restructuring.

How should individual preparer requirements be distinguished?

Distinguish the provider’s authorization from the requirements that apply to people preparing returns. A credentialed employee and an approved provider solve related but different readiness questions.

The IRS PTIN requirements for preparers explains that compensated individuals who prepare or substantially assist in preparing federal tax returns generally need a valid PTIN, with specified exceptions. A preparer identification number is not the acquisition entity’s EFIN.

Create separate evidence fields for the entity’s provider status, each person’s applicable preparer requirements, their permitted software access, and their assigned review or production role. Do not merge them into a single checkbox labeled licensed.

Confirm current information with the responsible people using a secure process. Acquisition diligence should not expose personal application information to staff or buyers who have no approved need for it.

Schedule qualified review and supervision independently of application processing. Receiving provider authorization does not establish that the practice has sufficient technical expertise, adequate capacity, or complete client records for every acquired engagement.

How can a buyer build a realistic readiness timetable?

Build a dependency schedule from the intended first production date backward, then test whether the required evidence can exist on time. Avoid planning every task around an assumed best-case approval.

The following figures are illustrative internal planning allowances. Only the separate IRS processing guidance above describes its published application expectation; these allowances are not an IRS service commitment or universal acquisition timetable.

If the buyer proposes a first production date thirty-five days away, a sixty-day sequential planning allowance exceeds that date by twenty-five days. This is a planning mismatch to resolve, not a prediction that approval will take exactly sixty days.

Some preparation can overlap if it does not depend on approval or require impermissible activity. Identify each permitted overlap and retain a hold point for authorization-dependent configuration or production. Simply compressing the bars on the schedule changes no requirement.

Integrate that timetable with the software cutover guide. The provider decision and the migration decision must both be ready; a realistic filing plan requires the slower unresolved dependency to be addressed.

What should happen when readiness is delayed?

Escalate the delay and determine a permitted operating arrangement before the affected work becomes urgent. Contact the appropriate IRS assistance channel and obtain transaction-specific advice rather than borrowing a number or sharing credentials.

Identify the current obligation owner, client status, actual due dates, and what work may lawfully proceed. Any alternative service or provider arrangement needs its own authorization, responsibility, information-access, and client documentation review.

A delayed application is different from a denied or suspended provider situation. Preserve the actual status and reason so advisers do not build a transition plan around an inaccurate description.

Do not promise clients automatic extensions, guaranteed filing, or an unrestricted paper alternative without reviewing the actual requirements and facts. A production limitation can require a specific client decision and appropriately qualified advice.

Add delay costs to the cash forecast if a supported temporary arrangement, additional staff, or overlapping software is necessary. Those costs should be separately funded and should not assume that delayed buyer collections arrive on the original date.

How should the buyer complete the authorization process?

Complete a documented sequence that assigns application responsibility and distinguishes submission, authorization, and operating readiness. Preserve evidence at each hold point.

1. Map the actual buyer entity, acquisition structure, locations, provider activities, and responsible people.
2. Review applicable IRS application, acquisition-proof, and timing requirements for the proposed arrangement.
3. Prepare and submit the required application information through authorized access, preserving tracking evidence.
4. Resolve requests or status questions and review the actual authorization outcome before dependent activity.
5. Configure the approved provider workflow, verify personnel requirements, and test permitted operational readiness.
6. Assign ongoing application maintenance, access control, filing-status monitoring, and escalation responsibilities.

A readiness memo should state what is approved, which records establish it, which production population is covered by the plan, and what remains unresolved. Keep that memo separate from general closing enthusiasm.

The technology and data migration guide can help identify interfaces and access owners. Use it to ensure that the authorized entity and responsible people match the production configuration after the acquisition.

What evidence should remain after closing?

Retain appropriate application, authorization, configuration, and responsibility records in a controlled location. The objective is to support maintenance and accountability without distributing sensitive personal information unnecessarily.

Reconcile staff changes, access changes, locations, and provider activities with the current arrangement. Assign a person to identify when a change requires further action rather than allowing application information to become stale after the transaction team leaves.

Track production exceptions through actual acknowledgments and resolution records. Provider authorization establishes a necessary readiness component, while successful operation still requires careful handling of each return, client instruction, and filing status.