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 · Government and regulatory

EDI 153 Unemployment Insurance Tax Claim or Charge Information

The bi-directional X12 document employment security agencies use to notify employers or other agencies of possible unemployment insurance charges.

Sent by
Employment security agency or employer
Received by
Employer or agency
Standard
ANSI ASC X12

What is an EDI 153?

The EDI 153 Unemployment Insurance Tax Claim or Charge Information is the bi-directional ANSI X12 transaction set employment security agencies can use to notify employers, or other agencies, of a possible charge to the employer's unemployment insurance tax account, and employers can use to respond.

When a former employee claims unemployment benefits, the employer's account may be charged, which affects its tax rate. Employers review the notices and contest claims where the separation reasons do not qualify, so timely electronic notices and responses matter.

How the EDI 153 worksDiagram of the EDI 153 Unemployment Insurance Tax Claim or Charge Information. Employment security agency or employer sends it to employer or agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTI (Beginning Tax Information) and the required N1 loop with N1 (Party Identification) and detail: the required NM1 loop with NM1 (Individual or Organizational Name). 1 optional loops are listed by their first segment.How the EDI 153 worksUnemployment Insurance Tax Claim or Charge Information: who sends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 153SENDEREmployment securityagency or employerRECEIVEREmployer or agency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CBGS … GETransaction set 153ST … SEHEADINGBTIBeginning Tax InformationRequired loop N1 · repeats many timesN1Party IdentificationDETAILRequired loop NM1 · repeats many timesNM1Individual or Organizational Name+ 1 optional loop, starting with:PAMBlue 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 153. Your trading partner's implementation guide adds its own requirements.
How the EDI 153 worksDiagram of the EDI 153 Unemployment Insurance Tax Claim or Charge Information. Employment security agency or employer sends it to employer or agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTI (Beginning Tax Information) and the required N1 loop with N1 (Party Identification) and detail: the required NM1 loop with NM1 (Individual or Organizational Name). 1 optional loops are listed by their first segment.How the EDI 153 worksUnemployment Insurance Tax Claim or ChargeInformation: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 153SENDEREmploymentsecurity agencyor employerRECEIVEREmployer oragency997 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 CB (GS … GE)Transaction set 153 (ST … SE)HEADINGBTIBeginning Tax InformationRequired loop N1 · repeats manytimesN1Party IdentificationDETAILRequired loop NM1 · repeatsmany timesNM1Individual orOrganizational Name+ 1 optional loop, starting with:PAMBlue 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 153. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 153, 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 153 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

  • Notifying employers of new unemployment claims
  • Reporting charges to employer accounts
  • Responding to claim notices

Where it fits in the document flow

This document 153 Unemployment Insurance Tax Claim or Charge Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 153 (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
  • BTI
  • N1
  • NM1
  • PAM
  • SE

Practical example

The 153 in practice

A former employee files an unemployment claim. The state agency sends the employer's unemployment cost management provider a 153 with the claimant, the separation reported and the potential charge. The provider reviews the employer's records and responds that the employee resigned voluntarily.

Implementation

Implementation considerations for the 153

  • Respond within the deadlines the agency sets.
  • Provide accurate separation information.
  • Protect claimants' personal data under applicable law.
  • Track charges against the employer's account.

How ECOM helps

Automate the 153 with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

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 government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 153?

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

Request a Demo Contact us