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 · Finance

EDI 818 Commission Sales Report

The X12 document a retailer uses to advise a trading partner of commission sales and salary information.

Sent by
Retailer
Received by
Vendor or manufacturer
Standard
ANSI ASC X12

What is an EDI 818?

The EDI 818 Commission Sales Report is the ANSI X12 transaction set a retailer uses to advise a trading partner of commission sales and salary information. The commission data lets the trading partner reconcile commission payments and salary support.

In some retail arrangements, a vendor funds sales staff in the retailer's stores, or pays commission on the sales they make, for example in cosmetics or fragrance counters. The 818 reports the sales and staff costs per store and period, so the vendor can verify what it owes or what the retailer claims.

How the EDI 818 worksDiagram of the EDI 818 Commission Sales Report. Retailer sends it to vendor or manufacturer. 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: BSC (Beginning Segment for Commission Sales Report and Periodic Compensation) and the required N11 loop with N11 (Store Location). 2 optional loops are listed by their first segment.How the EDI 818 worksCommission Sales Report: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 818SENDERRetailerRECEIVERVendor ormanufacturer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RPGS … GETransaction set 818ST … SEHEADINGBSCBeginning Segment for Commission Sales Report and Periodic CompensationRequired loop N11 · repeats up to 999N11Store Location+ 2 optional loops, starting with:LINNM1Blue 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 818. Your trading partner's implementation guide adds its own requirements.
How the EDI 818 worksDiagram of the EDI 818 Commission Sales Report. Retailer sends it to vendor or manufacturer. 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: BSC (Beginning Segment for Commission Sales Report and Periodic Compensation) and the required N11 loop with N11 (Store Location). 2 optional loops are listed by their first segment.How the EDI 818 worksCommission Sales Report: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 818SENDERRetailerRECEIVERVendor ormanufacturer997 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 RP (GS … GE)Transaction set 818 (ST … SE)HEADINGBSCBeginning Segment forCommission Sales Report andPeriodic CompensationRequired loop N11 · repeats up to999N11Store Location+ 2 optional loops, starting with:LINNM1Blue 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 818. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 818, 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 818 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 sales made by vendor-funded staff
  • Reporting salary support claimed from vendors
  • Supporting reconciliation of commission payments

Where it fits in the document flow

This document 818 Commission Sales Report
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 818 (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
  • BSC
  • N11
  • LIN
  • NM1
  • SAL
  • AMT
  • SE

Practical example

The 818 in practice

A department store employs beauty advisors whose pay is partly funded by a cosmetics brand. Each month it sends the brand an 818 with sales by store and advisor and the salary support claimed. The brand checks the figures against its agreement and its own sales data and settles the amount.

Implementation

Implementation considerations for the 818

  • Agree the reporting period and level of detail with each vendor.
  • Protect employee personal data included in salary reporting.
  • Reconcile reported sales with the vendor's own sell-through data.
  • Link reports to the commission or support agreement.

How ECOM helps

Automate the 818 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Solution

Financial Document Automation

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

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

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 818?

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

Request a Demo Contact us