Keep the employer filing map with the packet
Identify the legal employer, reporting year, all planned batches and the designated authoritative transmittal. The 2025 instructions allow multiple transmittals for an ALE member while requiring one authoritative employer summary.
Keep the employer-wide population separate from each accompanying batch. If different providers prepare portions of the same employer's records, reconcile their allocation before electronic packaging. An aggregated group does not have one combined authoritative transmittal across all its members.
Check scope, format and production readiness
The actual export must follow the applicable IRS AIR tax-year requirements. Record the environment, technical version and exact output that passed validation. A test response is not evidence for the production packet.
Fictional employer LG-25 allocates 150 complete annual records to batch A and 50 to batch B. Its release inventory contains 200 records across the two batches. A later provider split of A into 100 and 50 should preserve the same 200-record employer population and its authoritative map. Reconcile the resulting submissions before accepting a new provider total.
Track receipts and submission outcomes together
Store the receipt reference, submission references, sent-file version and original inventory together. Retrieve the acknowledgment in the correct environment. The IRS instructs transmitters to wait at least 10 minutes after the Receipt ID before the first acknowledgment request.
Record the agency's exact status and the affected scope. A top-level mixed outcome requires review of the submissions beneath it. An internal status such as awaiting payroll is a work assignment, not an AIR processing result.
Route the next action from actual filing history
Give the transmitter the original outcome, rejected scope or accepted record reference, and approved revised data. Publication 5165 and Publication 5258 distinguish replacement handling from accepted-record correction and specify electronic association requirements.
Employer-summary and employee-form errors can require different actions. The form instructions specify a standalone complete corrected authoritative 1094-C and prohibit correcting a nonauthoritative transmittal. Preserve that distinction when preparing the technical handoff.
After another action, link its new outcome to the original history. Reconcile unique intended records separately from the number of records appearing across attempts.
Choose a practical guide
Use the practical guide library below for the next step. Each guide includes a worked example, a diagram and a downloadable worksheet.
Questions from reporting teams
Can a group dashboard substitute for the employer batch map?
Only if it preserves each legal employer's actual scope and authoritative designation. A group-wide total cannot populate one ALE member's summary.
What if a provider splits our approved export?
Request the resulting submission inventory and mapping back to the approved source keys. Reconcile all resulting counts and preserve the authoritative structure.
Is a replacement the same as a correction?
No. The prior outcome and affected level govern the process. Preserve the actual history and have the transmitter apply the current AIR rules.
Does an accepted employer packet prove employee furnishing?
No. Track the relevant employee statement obligations and delivery evidence separately from the IRS submission result.
Prepare your employer's electronic filing project
Create a BoomTax account to begin your organization's filing setup. Keep the reporting year, expected return volume and reviewed source records available as you prepare the project.
