Confirm that your software is enrolled as an Authorized IRS e-file Provider for employment taxes and that you have active credentials for the MeF system (EFIN and ETIN); 94x series returns (941, 940, etc.) are transmitted via the MeF A2A channel
Submit the 94x return XML via the MeF SendSubmissions SOAP operation, following the 94x-specific XML schema and the MeF Submission Composition Guide sections applicable to employment tax returns
After submission, use GetSubmissionStatus with the SubmissionId to monitor whether the return has moved to Accepted or Rejected; for employment tax returns the processing timeline may differ from individual or business income tax returns
Upon acceptance, retrieve the acknowledgement from the MeF system using GetAcknowledgements; the acknowledgement for a 94x return confirms the SubmissionId, AcceptanceDateTime, and includes a confirmation that the return was accepted into IRS processing
For rejected returns, parse the AcknowledgementDetail for the specific rule violation codes and consult the MeF Error Dictionary for 94x-specific error codes to correct and resubmit; resubmission of a rejected employment tax return requires a new SubmissionId
Retain the accepted acknowledgement XML alongside the submitted return XML; IRS e-file guidelines specify retention requirements for acknowledgement records that enrolled EROs must follow
Known gotchas
The 94x XML schemas are separate from the income tax return schemas in the MeF library; using the wrong schema family causes immediate schema-validation rejection at the MeF gateway before business-rule processing
Employment tax deposits (EFTPS payments) are separate from return filing; submitting an accepted 94x return does not initiate tax payment — the filer must separately ensure EFTPS deposits are made by the applicable deposit schedule deadlines
Some 94x forms have associated schedules (e.g., Schedule B for Form 941) that must be included in the submission XML when applicable; omitting a required schedule that is triggered by the return data causes a business-rule rejection rather than a schema error
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp