972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Acknowledgments

EDI 151 Electronic Filing of Tax Return Data Acknowledgment

The X12 document used to acknowledge receipt of each tax return filed with the 813, and to report any errors.

Sent by
Taxing authority
Received by
Taxpayer or tax preparer
Standard
ANSI ASC X12

What is an EDI 151?

The EDI 151 Electronic Filing of Tax Return Data Acknowledgment is the ANSI X12 transaction set used to electronically acknowledge receipt of each tax return filed using the Electronic Filing of Tax Return Data transaction set (813). It may indicate any errors found.

For tax filers, the acknowledgment is proof that a return was received and accepted, which matters for meeting deadlines. Errors reported in it must be corrected and the return refiled, so filers monitor acknowledgments closely around due dates.

How the EDI 151 worksDiagram of the EDI 151 Electronic Filing of Tax Return Data Acknowledgment. Taxing authority sends it to taxpayer or tax preparer. It usually follows 813. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTA (Beginning Tax Acknowledgment) and BTI (Beginning Tax Information). 2 optional loops are listed by their first segment.How the EDI 151 worksElectronic Filing of Tax Return Data Acknowledgment: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS813Electronic Filing of TaxReturn DataEDI 151SENDERTaxing authorityRECEIVERTaxpayer or taxpreparer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TAGS … GETransaction set 151ST … SEHEADINGBTABeginning Tax AcknowledgmentBTIBeginning Tax Information+ 1 optional loop, starting with:PBIDETAIL+ 1 optional loop, starting with:TFSBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 151. Your trading partner's implementation guide adds its own requirements.
How the EDI 151 worksDiagram of the EDI 151 Electronic Filing of Tax Return Data Acknowledgment. Taxing authority sends it to taxpayer or tax preparer. It usually follows 813. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTA (Beginning Tax Acknowledgment) and BTI (Beginning Tax Information). 2 optional loops are listed by their first segment.How the EDI 151 worksElectronic Filing of Tax Return DataAcknowledgment: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS813Electronic Filing of Tax Return DataEDI 151SENDERTaxing authorityRECEIVERTaxpayer or taxpreparer997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TA (GS … GE)Transaction set 151 (ST … SE)HEADINGBTABeginning TaxAcknowledgmentBTIBeginning Tax Information+ 1 optional loop, starting with:PBIDETAIL+ 1 optional loop, starting with:TFSBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 151. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 151, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 151 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Acknowledging accepted tax returns
  • Reporting errors in filed returns
  • Providing proof of timely filing

Where it fits in the document flow

Usually follows 813 Electronic Filing of Tax Return Data
This document 151 Electronic Filing of Tax Return Data Acknowledgment
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 151 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BTA
  • BTI
  • PBI
  • TFS
  • FGS
  • SE

Practical example

The 151 in practice

A fuel distributor files tax returns in six states. Five states return 151 acknowledgments accepting the returns; one reports an error in a jurisdiction code. The distributor corrects the return and refiles it before the deadline.

Implementation

Implementation considerations for the 151

  • Monitor acknowledgments for every return filed.
  • Correct and refile rejected returns before deadlines.
  • Keep acknowledgments as proof of filing.
  • Map each error code to a corrective action.

How ECOM helps

Automate the 151 with ECOM

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related acknowledgments documents

All 9 acknowledgments documents

Need help with the EDI 151?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us