Search EDIBlogs
50 results for “X12”
GlossaryX12ANSI ASC X12 is the American standards body and the EDI standard it maintains, widely used in North America for retail, logistics, finance, and healthcare transactions.ArticleX12 850 Purchase Order: Complete EDI GuideA complete, segment-by-segment walkthrough of the X12 850 Purchase Order — what it is, how it's structured, how to map it, and how to troubleshoot the errors that show up most often in production.ArticleX12 856 Advance Ship Notice: The Complete EDI GuideEverything you need to build, validate, and troubleshoot an X12 856 ASN — including the HL hierarchy that trips up almost every new implementation.ArticleX12 270/271 Eligibility Inquiry and Response: A Practical GuideHow the HIPAA X12 270/271 pair works together to verify patient insurance eligibility in real time, with the segment structure and benefit codes that matter most.ArticleEDI Mapping Explained: From ERP Fields to X12 and EDIFACT SegmentsA practical guide to how EDI mapping actually works — the concepts, common source formats, and a worked example translating SAP IDoc fields into an X12 850.ArticleThe X12 997 Functional Acknowledgment: What It Confirms (and What It Doesn't)A clear breakdown of what a 997 actually validates, how to read its AK segments, and why it's not the same thing as business-level order confirmation.QuestionHow do I map X12 856 HL loops correctly for a multi-pallet shipment?I'm building an 856 ASN map for a new retail trading partner. My shipment has 3 pallets, each with 2 cartons, each carton containing multiplQuestionShould I learn X12 or EDIFACT first as a new EDI analyst in the US?I just got hired as a junior EDI analyst at a manufacturing company that sells both domestically and to European customers. Most of our traiTransaction850 — Purchase OrderThe X12 850 is the electronic purchase order a buyer sends to a supplier to request goods or services, replacing paper or PDF POs with a structured, machine-readable document.Transaction855 — Purchase Order AcknowledgmentThe X12 855 is the supplier's formal response to an 850 Purchase Order, confirming, changing, backordering, or rejecting each line item.Transaction856 — Advance Ship NoticeThe X12 856 (ASN) tells the buyer exactly what was shipped, how it was packed (pallet/case/item hierarchy), and when it will arrive — before the truck reaches the dock.Transaction810 — InvoiceThe X12 810 is the electronic invoice a supplier sends after (or with) a shipment, billing the buyer for goods or services delivered.Transaction820 — Payment Order/Remittance AdviceThe X12 820 instructs a financial institution to make a payment and/or advises the payee which invoices a payment covers.Transaction940 — Warehouse Shipping OrderThe X12 940 instructs a third-party warehouse to pick, pack, and ship a specific order on behalf of the merchandise owner.Transaction945 — Warehouse Shipping AdviceThe X12 945 is the warehouse's confirmation back to the merchandise owner that a 940 shipping order was picked, packed, and shipped.Transaction997 — Functional AcknowledgmentThe X12 997 confirms that an interchange was received and whether it passed structural (syntax) validation — it does not confirm business acceptance of the content.Transaction214 — Transportation Carrier Shipment Status MessageThe X12 214 provides in-transit status updates (pickup, in-transit, delivered, exception) for a freight shipment.Transaction204 — Motor Carrier Load TenderThe X12 204 is a shipper's offer (tender) of a freight load to a carrier, specifying origin, destination, equipment, and commodity details.Transaction270 — Eligibility, Coverage or Benefit InquiryThe HIPAA X12 270 is a request from a healthcare provider to a payer asking whether a patient has active insurance coverage and what benefits apply.Transaction271 — Eligibility, Coverage or Benefit InformationThe HIPAA X12 271 is the payer's response to a 270 inquiry, detailing whether the patient is covered and describing plan benefits, copays, and limitations.Transaction276 — Health Care Claim Status RequestThe HIPAA X12 276 asks a payer for the current processing status of a previously submitted health care claim.Transaction277 — Health Care Claim Status ResponseThe HIPAA X12 277 is the payer's answer to a 276, reporting where a claim stands in adjudication.Transaction278 — Health Care Services Review – Request/ResponseThe HIPAA X12 278 requests prior authorization or a referral for a health care service, and carries the payer's determination.Transaction834 — Benefit Enrollment and MaintenanceThe HIPAA X12 834 communicates enrollment, changes, and terminations of health plan coverage from an employer or sponsor to a payer.Transaction835 — Health Care Claim Payment/AdviceThe HIPAA X12 835 explains how a payer adjudicated a claim — what was paid, denied, or adjusted, and why — while optionally carrying the actual payment.Transaction837 — Health Care ClaimThe HIPAA X12 837 is the electronic claim a provider submits to a payer to request payment for services rendered (professional, institutional, or dental).TransactionORDERS — Purchase Order MessageUN/EDIFACT ORDERS is the international equivalent of the X12 850 — a structured purchase order used widely across Europe and global trade lanes.TransactionORDRSP — Purchase Order Response MessageUN/EDIFACT ORDRSP is the supplier's response to an ORDERS message, confirming, amending, or rejecting the purchase order — the EDIFACT counterpart to the X12 855.TransactionDESADV — Despatch Advice MessageUN/EDIFACT DESADV is the international equivalent of the X12 856 Advance Ship Notice, describing what was shipped and how it is packed.TransactionINVOIC — Invoice MessageUN/EDIFACT INVOIC is the electronic invoice message, the EDIFACT counterpart to the X12 810, used to bill for goods or services delivered.TransactionIFTSTA — International Multimodal Status Report MessageUN/EDIFACT IFTSTA reports shipment status and milestones across a transport chain, the EDIFACT counterpart to the X12 214.ArticleEDIFACT ORDERS: A Complete Guide to the International Purchase Order MessageHow UN/EDIFACT ORDERS compares to the X12 850, its segment structure, and what to watch for when trading with European and global manufacturing partners.JobEDI Analyst — Confidential Retail DistributorSupport daily EDI operations, monitor transaction failures, and onboard new retail trading partners onto existing X12 maps.JobEDI Developer — Leading 3PL ProviderBuild and maintain EDI maps across X12 and EDIFACT for a growing logistics network, working closely with WMS and TMS integration teams.GlossaryISA (Interchange Control Header)The first segment of an X12 interchange, identifying the sender, receiver, and control number for the entire envelope of transactions.GlossaryIEA (Interchange Control Trailer)The closing segment of an X12 interchange, containing a count of functional groups and the matching interchange control number from the ISA.GlossaryGS (Functional Group Header)Marks the start of a functional group — a batch of one or more transaction sets of the same type (e.g., all 850s) — within an X12 interchange.GlossaryST (Transaction Set Header)Marks the beginning of a single X12 transaction set (e.g., one purchase order) and specifies its type code and control number.GlossaryHL (Hierarchical Level)An X12 segment used to build parent-child relationships between loops, such as shipment, order, pack, and item levels in an 856 ASN.GlossaryN1 (Party Identification)An X12 segment identifying a party involved in the transaction, such as a buyer, seller, ship-to, or bill-to location.GlossaryPO1 (Baseline Item Data)The X12 850 segment representing a single line item on a purchase order, including quantity, unit price, and product identifiers.GlossaryBEG (Beginning Segment for Purchase Order)The X12 850 segment that carries the purchase order number, type, and date, marking the start of the transaction's business content.GlossaryTranslationThe runtime process of converting data from one format to another according to a mapping specification — for example, converting an internal order record into an X12 850 file.GlossaryFunctional AcknowledgmentThe X12 997 (or 999) transaction confirming an interchange was received and whether it passed structural validation, without judging business content.GlossaryASN (Advance Ship Notice)A shipment notification sent before or at the time of shipping, detailing what was shipped, how it was packed, and expected arrival — the business term for the X12 856 / EDIFACT DESADV.GlossaryCARC (Claim Adjustment Reason Code)A standardized code used in the X12 835 to explain why a claim payment differs from the amount billed.GlossaryRARC (Remittance Advice Remark Code)A standardized code providing additional explanatory detail alongside a CARC in an X12 835 remittance advice.GlossaryNPI (National Provider Identifier)A unique 10-digit identification number for covered healthcare providers in the United States, used throughout HIPAA X12 transactions.GlossaryEnvelopeThe set of control segments (ISA/GS/ST...SE/GE/IEA in X12, or UNB/UNH...UNT/UNZ in EDIFACT) that wrap one or more business documents for transmission.GlossaryUNB (Interchange Header)The EDIFACT segment that opens an interchange, identifying sender, recipient, and interchange control reference — the EDIFACT counterpart to X12's ISA.