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 · Healthcare and insurance

EDI 268 Annuity Activity

The X12 document annuity providers use to send account activity to distributors such as broker-dealers, planners and banks.

Sent by
Annuity provider
Received by
Distributor, such as a broker-dealer, planner or bank
Standard
ANSI ASC X12

What is an EDI 268?

The EDI 268 Annuity Activity is the ANSI X12 transaction set used to convey annuity account activity from annuity providers to distributors, such as broker-dealers, financial planners, banks and savings institutions, to communicate account activity and values.

Advisors need to see their clients' annuity values and transactions alongside other holdings. Activity data, such as premiums, withdrawals, transfers between investment options and fees, lets distributors' systems show complete client portfolios and supports supervision of transactions. Activity is often reported daily, so that distributors' systems show values and transactions that match the provider's records.

How the EDI 268 worksDiagram of the EDI 268 Annuity Activity. Annuity provider sends it to distributor, such as a broker-dealer, planner or bank. 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: BGN (Beginning Segment) and detail: the required N1 loop with N1 (Party Identification). 5 optional loops are listed by their first segment.How the EDI 268 worksAnnuity Activity: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 268SENDERAnnuity providerRECEIVERDistributor, such as abroker-dealer, planneror bank997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code PFGS … GETransaction set 268ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop N1 · repeats many timesN1Party Identification+ 4 optional loops, starting with:PIDPO1ACTCONBlue 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 268. Your trading partner's implementation guide adds its own requirements.
How the EDI 268 worksDiagram of the EDI 268 Annuity Activity. Annuity provider sends it to distributor, such as a broker-dealer, planner or bank. 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: BGN (Beginning Segment) and detail: the required N1 loop with N1 (Party Identification). 5 optional loops are listed by their first segment.How the EDI 268 worksAnnuity Activity: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 268SENDERAnnuity providerRECEIVERDistributor, suchas abroker-dealer,planner or bank997 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 PF (GS … GE)Transaction set 268 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop N1 · repeats manytimesN1Party Identification+ 4 optional loops, starting with:PIDPO1ACTCONBlue 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 268. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting annuity contributions and withdrawals
  • Reporting transfers between investment options
  • Reporting account values to distributors

Where it fits in the document flow

This document 268 Annuity Activity
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 268 (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
  • BGN
  • NM1
  • N1
  • PID
  • PO1
  • ACT
  • CON
  • BLI
  • IT1
  • EFI
  • LX
  • AM1
  • RPA
  • AMT
  • SE

Practical example

The 268 in practice

A broker-dealer's advisors service thousands of annuity contracts from several insurers. Each night the insurers send 268 activity files with the day's transactions and current values. The broker-dealer's portfolio system updates client accounts, and supervisors review large withdrawals.

Implementation

Implementation considerations for the 268

  • Reconcile values with transactions reported.
  • Identify contracts and investment options consistently.
  • Protect clients' personal and financial data.
  • Agree the frequency and cut-off of activity reporting.

How ECOM helps

Automate the 268 with ECOM

Industry

Financial Services

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

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

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

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

Related transactions

Related healthcare and insurance documents

All 31 healthcare and insurance documents

Need help with the EDI 268?

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

Request a Demo Contact us