810 Invoice

Implementation
Guidelines
810
Invoice
8/1/2016
Table of Contents
q Menard, Inc. Electronic Commerce Information

General contact and setup information you will need to properly set up Menards in your
systems.
q Business Rules 810 Invoice

This section outlines the general requirements and expectations of the program. It also
presents the document segments and details.
q EDI Mapping Specifications 810 - Invoice

These are the EDI mapping specifications for the 810 document. Any questions concerning
the definition and/or use of any of the segments should be communicated immediately to
avoid possible misunderstandings.
q 810 Business Examples

This is example data according to the 810 specifications provided. It contains several
shipping scenarios and displays expectations for various types of purchase orders.
q Electronic Invoicing Testing Guidelines

This outlines the flow of testing with regards to what we expect from our vendors and what
our vendors can expect from Menard, Inc.
q EDI Mapping Specifications 864 - Text Message

These are the EDI mapping specifications for the 864 document. Any questions concerning
the definition and/or use of any of the segments should be communicated immediately to
avoid possible misunderstandings.
q 864 Business Examples

This is example data according to the 864 specifications provided.
Menard, Inc. 4777 Menard Drive Eau Claire, WI 54703 Phone: (715) 876-5911 Fax: (715) 876-2562
Electronic Commerce Information
General Information:
Address: Menard Inc Partners Website: www.menard-inc.com
Attn: EDI Dept Supplier Portal: https://supplier.menard-inc.com/hsx/html/login.html
5101 Menard Drive
Eau Claire WI 54703
Contacts:
Brian Fechter Heidi Franko Tyler Moldenhauer Kirsten Sadler
EDI Coordinator EDI Analyst EDI Analyst EDI Analyst
715-876-2612 715-876-2273 715-876-4072 715-876-2410
bfechter@menard-inc.com hfranko@menard-inc.com tmoldenh@menard-inc.com ksadler@menard-inc.com
Shirley Mance
EDI Specialist
715-876-2575
smance@menard-inc.com
Document Information:
Standard: ASC X.12 Version / Release: 004010
Documents Presently Traded:

810 Invoice 856 Advance Ship Notice
850 Purchase Order 864 Text Message
852 Product Activity (VMI/SBT Programs Only) 870 Order Status Report
855 PO Acknowledgment (VMI Programs Only) 997 Functional Acknowledgment
Transmission Information:
Primary Value Added Network: If your company is unable to support direct AS2 connection please
contact us for list of existing VAN connections your company may utilize
to facilitate EDI communications with Menards.
EDI/INT Software: BizManager v3.3
AS2 URL: http://dmz-bizmgr.menard-inc.com:9080/msgsrv/as2

AS2 ID: 006203210PAS2
AS2 IP Address: 173.245.131.13
AS2 MDNs: Synchronous
Encryption Algorithm: DES3 168
Signature Algorithm: SHA1 160
Authorization Information Qualifier (ISA 01): 03

Authorization Information (ISA 02): Internal Menards Vendor #
Security Information Qualifier (ISA 03): 01
Security Information: (ISA 04): Internal Menards Vendor #
Interchange ID Qualifier (ISA 05): 01
Interchange Sender ID (ISA 06): 006203210P
Functional Group Sender ID (GS 02): 006203210
Segment Delimiter: ~ (7E)

Element Delimiter: * (2A)
Sub Element Delimiter: > (3E)
Business Rules 810 Invoice
Expectations
We expect our vendors to provide an 810 invoice on all orders transmitted via EDI.
The only exception being no charge orders 810 should not be sent for invoice totaling $0.
We expect that our vendors will not transmit an 810 invoice before the product has shipped.
We expect our vendors to provide a unique invoice # for each 810 invoice transmitted, unless an 810 invoice was
previously rejected/refused and a corrected 810 invoice is being submitted in its place.
We expect the invoice number format on the 810 invoice to follow the same format as what previously appeared on paper
invoices and in the same sequence.
Electronic invoice #s cannot exceed 11 characters. If paper invoices have leading 0s, s or spaces these should
be omitted from the electronic invoices.
We expect our vendors to monitor for 997 rejections in addition to 864 refusals for 810s.
We expect our vendors to stop mailing paper invoices (if not already doing WEB Invoicing) once EDI invoicing is
implemented.
Credit memos to remain in a paper format at this time.
Production Validation Process

Step 1 Map Validation
If the 810 invoice does not follow the defined format, a 997 will be immediately sent back indicating a rejected status. The
AK3 & AK4 segments of the 997 will detail the issue.
Note: Vendor is expected to correct the mapping issue and resend the 810 under new ISA/GS control #s.
864 messages will NOT be returned on 810s rejected during translation 997 rejection will be the only communication.
Step 2 Basic Validation
After successful translation, a check is done to verify if basic information such as PO#, store#, sku#, etc. are legitimate. If
a discrepancy is found, an 864 will be immediately sent back detailing the issue.
Note: Vendor is expected to correct the data and resend the 810 under new ISA/GS control #s.
Step 3 Matching Validation
After successful basic validation, the invoice is sent to a holding area to await the receipt of the shipment. Shortly after
receipt of the shipment, a match is done against the appropriate elements of the invoice, purchase order, and receiving
information.
Upon a successful match, the invoice will be scheduled for payment according to terms. If not, an 864 refusal will be sent
detailing the issue. Vendor is expected to review the 864 and either correct / resend the invoice under new ISA/GS control
#s if invoice was in error or contact our AP dept via the means listed in the 864 message to dispute / discuss the issue
should vendor believe Menard, Inc was in error.
Additional Notes
The EDI 864 document replaces the paper payment refusal form previously used.
If a total discrepancy of $2.00 is found during the matching process, the invoice will be paid and a deduction will be
taken for the difference. Vendors can authorize a higher threshold if desired.
Automated e-mails will be sent to the vendor confirming PO changes. This is not meant to initialize a change, but rather
to summarize a previously communicated/approved change to provide better records.
An EDI 864 will be provided to also indicate a successful match. This is an optional document and can be discontinued if
not desired by the vendors credit department.
Unless an existing written agreement allows for overages, a 25% deduction of the overage amount will be taken. Any
deductions taken for overages will be noted on the remittance advice with an invoice number starting with an ELVC
prefix.
The status of EDI invoices may be checked on our website www.menard-inc.com.
o There may be a day lag between the transmission/translation of the 810 and when status can be viewed online.
o In the case of certain payment refusals vendors may authorize deduction/short payment through the EDI Invoice
Lookup on the Partners website.
An acceptable 810 invoice document will contain valid data in all of the Mandatory segments/elements
below as well as the Conditional segments/elements when the condition is present.
Element Description Detail Usage

BIG01 Invoice Date Date of invoice creation Mandatory
BIG02 Invoice Number Unique invoice #, cannot exceed 11 characters Mandatory
BIG04 Purchase Order Number Original PO# from BEG03 of 850 PO Mandatory
BIG07 Transaction Type Code "DI = Debit Invoice Mandatory
CUR01 Entity Identifier Code "SE" = Selling Party Mandatory
CUR02 Currency Code USD Mandatory
REF01 Reference Identification Qualifier "VR" = Vendor ID Number Mandatory
REF02 Vendor # Menard Assigned Accounts Payable Number Mandatory
N101 Entity Identifier Code "ST" = Ship to, "BT" = Bill to, "BS" = Bill and Ship to,
Mandatory
"OB" = Ordered By Cannot send both BS and ST/BT.
N102 Ship To/Bill To Location Return value received in N102 of the 850 Mandatory
N102 Ordered By Location Return value received in N102 of the 850 Mandatory
ITD01 Payment terms code 01-Basic, 05-No Discount Applicable, 09-Proximo Mandatory
ITD02 Terms Basis Date Code Beginning of terms period code. Code 3 used. Mandatory
ITD03 Terms Discount Percent Discount percentage, when applicable Conditional
ITD04 Discount Payment Due Date Discount Due Date, when applicable Conditional
Number of days in discount terms period, when
ITD05 Terms Discount Days Due applicable Conditional
ITD06 Net Payment Due Date Net Due Date Mandatory
ITD07 Terms Net Days Number of days in net terms period Mandatory
ITD08 Terms Discount Amount Total amount of terms discount, when applicable Conditional
ITD12 Terms Description Text description of terms Net 30 Days Mandatory
ITD13 Day of Month Day of month due (Only for Prox terms) Conditional
DTM01 Date/Time Qualifier Use 011 Mandatory
DTM02 Ship Date Date shipped Mandatory
IT101 Sequence Number Line item (Sequence) # from PO101 of 850 PO Mandatory
IT102 Quantity Invoiced Quantity being invoiced for this shipment Mandatory
IT103 Sales Unit Unit of Measure from PO103 of the 850 PO Mandatory
IT104 Unit Price Menard Cost Mandatory
IT106 Product/Service ID Qualifier "SK" = SKU Mandatory
IT107 Sku Menard SKU # from PO107 of the 850. Mandatory
IT108 Product/Service ID Qualifier "VP" = Vendor Part Number Mandatory
IT109 Vendor Part Number Your Vendor Part #. Mandatory
PID01 Item Description Type "F" = Free Form Mandatory
PID05 Product Description Line Item Description. Mandatory
Element Description Detail Usage
TDS01 Gross Invoice Total Total invoice amount (including applicable charges) Mandatory
TDS02 Amount used for terms disc calculation Only provide if amount differs from value in TDS01 Conditional
TDS03 Net Invoice Total Total invoice amount less terms discount Mandatory
CAD01 Transportation Method / Type Code R Used for Rail shipments only
CAD02 Equipment Initial Railcar Abbr. Used for Rail shipments only Conditional
Based on
CAD03 Equipment Number Railcar Number Used for Rail shipments only Shipping
CAD04 Standard Carrier Alpha Code Carrier SCAC Used for Van/Flat shipments only Method
CAD05 Routing Carrier Name Used for Van/Flat shipments only
SAC01 Additional Allowance/Charge Indicator A= Allowance, C = Charge Conditional
F340 = Pickup Allowance D240 = Freight Charge
D270 = Fuel Surcharge
SAC02 Allowance D270 = Fuel Surcharge Conditional
H400 = Stop Charge
Additional Allowance/Charge Qualifier H605 = Tarp Charge
SAC05 Amount Dollar amount of allowance or charge when applicable Conditional
EDI Mapping Specifications
810 - Invoice (08/01/16)
ISA - Interchange Control Header Usage: Mandatory

ID Element Description Type Min/Max Notes
ISA01 I01 Authorization Information Qualifier ID 2/2 03 = Additional Data Information
ISA02 I02 Authorization Information AN 10/10 Authorization ID (Menard Assigned Vendor #)
ISA03 I03 Security Information Qualifier ID 2/2 01 = Password
ISA04 I04 Security Information AN 10/10 Security Password (Menard Assigned Vendor #)
ISA05 I05 Interchange ID Qualifier ID 2/2 Sender's ID Qualifier
ISA06 I06 Interchange Sender ID AN 15/15 Sender's ID
ISA07 I05 Interchange ID Qualifier ID 2/2 Receiver's ID Qualifier
ISA08 I07 Interchange Receiver ID AN 15/15 Receiver's ID
ISA09 I08 Interchange Date DT 6/6 YYMMDD
ISA10 I09 Interchange Time TM 4/4 HHMM
ISA11 I10 Interchange Control Standards Identifier ID 1/1 U = ASC X12
ISA12 I11 Interchange Control Version Number ID 5/5 00401
ISA13 I12 Interchange Control Number NO 9/9 Sender's Interchange Control Num
ISA14 I13 Acknowledgment Requested ID 1/1 0 = No Ack (TA1) Requested
ISA15 I14 Test Indicator ID 1/1 P = Production Data, T = Test Data
ISA16 I15 Component Element Separator AN 1/1 >
GS - Functional Group Header Usage: Mandatory

GS01 479 Functional Identifier Code ID 2/2 IN = Invoice Information
GS02 142 Application Sender's Code AN 2/15 Sender's Identifier
GS03 124 Application Receiver's Code AN 2/15 Receiver's Identifier
GS04 373 Date DT 8/8 Date (YYYYMMDD)
GS05 337 Time TM 4/4 Time (HHMM)
GS06 28 Group Control Number NO 1/9 Sender's Group Control Number
GS07 455 Responsible Agency Code ID 1/2 X = ASC X12
GS08 480 Version/ Release/Industry Identifier Code AN 1/12 004010
ST - Transaction Set Header Usage: Mandatory

ST01 143 Transaction Set Identifier Code ID 3/3 810 = Invoice
ST02 329 Transaction Set Control Number NO 4/9 Sender's Transaction Set Control Number
BIG - Beginning Segment For Invoice Usage: Mandatory

BIG01 373 Date DT 8/8 Invoice Issue Date (YYYYMMDD)
BIG02 76 Invoice Number AN 1/11 Invoice Number
BIG04 324 Purchase Order Number AN 12/12 PO# assigned by Menard, Inc
BIG07 640 Transaction Type Code ID 2/2 DI = Debit Invoice
810 - Invoice (08/01/16)
CUR - Currency Usage: Mandatory

CUR01 98 Entity Identifier Code ID 2/3 SE = Selling Party
CUR02 100 Currency Code ID 3/3 USD = U.S. Dollars
REF - Vendor Account Number Usage: Mandatory

REF01 128 Reference Identification Qualifier ID 2/2 VR = Vendor ID Number
REF02 127 Reference Identification AN 4/8 Menard Accounts Payable Number
N1 - Ship To Location Usage: Mandatory

N101 98 Entity Identifier Code ID 2/2 ST = Ship To
N102 93 Name NO 1/30 Return Ship to location received in N102 of the 850.
N1 - Bill To Location Usage: Mandatory

BT = Bill To
Note: It is acceptable to send a BS qualifier in lieu of
separate N1*ST and N1*BT segments only if the location #'s
are the same. If bill and ship to location differ then separate
N101 98 Entity Identifier Code ID 2/2 N1*ST and N1*BT loops must be sent.
N102 93 Name NO 1/30 Return Bill to location received in N102 of the 850.
N1 - Ordered By Location Usage: Mandatory

N101 98 Entity Identifier Code ID 2/2 OB = Ordered By
N102 93 Name NO 1/30 Return Ordered by location received in N102 of the 850.
810 - Invoice (08/01/16)
ITD - Terms of Sale/Deferred Terms of Sale Usage: Mandatory

Code identifying type of payment terms
01 = Basic (Ex: 2% 10, Net 30)
05 = Discount Not Applicable (Ex: Net 30)
ITD01 336 Terms Type Code ID 2/2 09 = Proximo (Ex: 2% 10th, Net 30th)
Code identifying the beginning of the terms period
ITD02 333 Terms Basis Date Code ID 1/2 Note: Typical code used is 3 for invoice date
Terms discount percentage
ITD03 338 Terms Discount Percent Description R 1/4 (Ex: 2% 10, Net 30 would be 2)
Terms discount due date
ITD04 370 Terms Discount Due Date DT 8/8 (Ex: 2% 10, Net 30 would be 10 days from invoice date)
Discount days due
ITD05 351 Terms Discount Days Due N0 1/3 (Ex: 2% 10, Net 30 would be 10)
Due Date
ITD06 446 Terms Net Due Date DT 8/8 (Ex: 2% 10, Net 30 would be 30 days from invoice date)
Due Days
ITD07 386 Terms Net Days N0 1/3 (Ex: 2% 10, Net 30 would be 30)
Total amount of terms discount
ITD08 362 Terms Discount Amount N2 1/10 Note: If no terms discount given, leave null
ITD12 352 Description ID 1/80 Freeform description of terms requested by Vendor
Used only with Prox termsday of month due
ITD13 765 Day of Month N0 1/2 (Ex: 2% 10th, Net 30th would be 10)
DTM - Date/Time Reference Usage: Mandatory

DTM01 374 Date/Time Qualifier ID 3/3 011
DTM02 373 Date DT 8/8 Shipped Date
Loop ID - IT1
IT1 - Baseline Item Data Usage: Mandatory
IT101 350 Assigned Identification AN 1/10 Menard, Inc Item Sequence Number from PO101 of 850.
IT102 358 Quantity Invoiced R 1/10 Quantity of Item Invoiced
IT103 355 Unit or Basis for Measurement Code ID 2/2 Menard, Inc Ordering Unit from PO103 of 850.
IT104 212 Unit Price (Include Decimal Points) R 1/8 Unit Price of the Item Purchased (includes decimal)
IT106 235 Product/Service ID Qualifier ID 2/2 SK = SKU
IT107 234 Product/Service ID AN 7/7 Menard, Inc SKU # from PO107 of 850.
IT108 235 Product/Service ID Qualifier ID 2/2 VP = Vendor Part Number
IT109 234 Product/Service ID AN 1/48 Vendor Part Number assigned by Vendor
PID - Product/Item Description Usage: Mandatory

PID01 349 Item Description Type ID 1/1 F = Free Form
PID05 352 Description AN 1/80 Line Item Description
End Loop ID - IT1
810 - Invoice (08/01/16)
TDS - Total Monetary Value Summary Usage: Mandatory

Gross Invoice Amount
The total (including all charges less any allowances) before
TDS01 610 Amount N2 1/8 the terms discount is applied.
Gross Invoice Amount Applicable to Discount
Should only be populated if amount upon which terms
discount is calculated differs from amount in TDS01 else,
TDS02 610 Amount N2 1/8 leave null.
Net Invoice Amount
Total amount due less terms discount
TDS03 610 Amount N2 1/8 Note: If no terms discount supply value noted in TDS01
CAD - Carrier Details Usage: Mandatory

R = Rail
CAD01 91 Transportation Method/Type Code ID 1/2 (Rail Shipments Only - Leave null if not by Rail)
Railcar Abbreviation
CAD02 206 Equipment Initial AN 1/4 (Rail Shipments Only - Leave null if not by Rail)
Railcar Number
CAD03 207 Equipment Number AN 1/10 (Rail Shipments Only - Leave null if not by Rail)
Standard Carrier Alpha Routing Code
Ex: UPSS for United Parcel Service
CAD04 140 Standard Carrier Alpha Code ID 2/4 (Do not include element if shipped by rail)
Free-form description of the carrier's identity
Ex: United Parcel Service
CAD05 387 Routing AN 1/35 (Do not include element if shipped by rail)
Loop ID - SAC
SAC - Service Promotion, Allowance, or Charge Usage: Conditional
SAC01 248 Allowance or Charge Indicator ID 1/1 A = Allowance, C = Charge
Code to indicate the type of Allowance or Charge
SAC02 1300 Service, Allowance or Charge Code ID 4/4 See table in packet for list of acceptable codes.
SAC05 610 Amount N2 1/10 Service, Allowance or Charge Dollar Amount
End Loop ID - SAC

810 - Invoice (08/01/16)
CTT - Transaction Totals Usage: Mandatory

CTT01 354 Number of Line Items NO 1/6 Total number of Line Items (IT1) in the transaction Set.
SE - Transaction Set Trailer Usage: Mandatory

SE01 96 Number of Included Segments NO 1/10 Total Number of Segments
SE02 329 Transaction Set Control Number NO 4/9 Transaction Set Control Number
GE - Functional Group Trailer Usage: Mandatory

GE01 97 Number of Transactions Sets Included NO 1/6 Total Number of Transaction Sets
GE02 28 Group Control Number NO 1/9 Group Control Number
IEA - Interchange Control Trailer Usage: Mandatory

IEA01 I16 Number of Included Functional Groups NO 1/5 Total Number of Functional Groups
IEA02 I12 Interchange Control Number NO 9/9 Interchange Control Number
810 Business Examples
Standard Invoice - Discounted Terms
This is an example of an invoice with discounted terms. The ship to and bill to location are the same so N1*BS
value from the N102 of the 850 can be returned instead of sending separate N1*ST and N1*BT segments on
the 810.
ST*810*0001~
BIG*20160801*12345678901**DIST29999999***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*BS*3039~
N1*OB*3039~
ITD*01*3*2*20160816*15*20160831*30*2237****2% 15 Net 30 Days~
DTM*011*20160801~
IT1*1*50*EA*9.95**SK*1234567*VP*ABCDEFG~
PID*F****HIGH QUALITY ABCDEFG~
IT1*2*30*EA*20.25**SK*1231234*VP*TUVWXYZ~
PID*F****HIGH QUALITY TUVWXYZ~
IT1*4*18*EA*.75**SK*1237890*VP*LMNOPQR~
PID*F****HIGH QUALITY LMNOPQR~
TDS*111850**109613~
CAD****FDCC*FED EX GROUND~
CTT*3~
SE*18*0001~
Standard Invoice - Net Terms

This is an example of an invoice where there is no terms discount. The PO has separate ship to and bill
locations. N1*ST, BT and OB values from the N102 elements of the 850 should be returned on the 810.
ST*810*0001~
BIG*20160801*12345678901**DCXD29999998***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*ST*3499~
N1*BT*3039~
N1*OB*3039~
ITD*05*3****20160831*30*****Net 30 Days~
DTM*011*20160801~
TDS*111850**111850~
CTT*3~
SE*19*0001~
Standard Invoice - Prox Discounted Terms
This is an example of an invoice where there are prox discounted terms. The ship to and bill to are the same
so N1*BS value from the N102 element of the 850 can be returned instead of separate N1*ST and N1*BT
segments on the 810.
ST*810*0001~
BIG*20160710*12345678901**DIST29999997***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*BS*3039~
N1*OB*3039~
ITD*09*3*2*20160810*31*20160830*51*2237****2% 10th Net 30th*10~
DTM*011*20160710~
TDS*111850**109613~
CTT*3~
SE*18*0001~
Standard Invoice - Prox Discounted Terms

This is an example of an invoice where there are prox discounted terms and the cutoff day has been
surpassed. The ship to and bill to are the same so N1*BS value from the N102 element of the 850 can be
returned instead of sending separate N1*ST and N1*BT segments.
ST*810*0001~
BIG*20160726*12345678901**DIST29999996***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*BS*3039~
N1*OB*3039~
ITD*09*3*2*20160910*46*20160930*66*2237****2% 10th Net 30th Prox 25th*10~
DTM*011*20160726~
TDS*111850**109613~
CTT*3~
SE*18*0001~
Rail Shipment
This is an example of an invoice for an order where the PO was shipped via rail car. The PO has separate
ship to and bill locations. N1*ST, BT and OB values from the N102 elements of the 850 should be returned on
the 810. Please note CAD segment CAD04 and 05 elements omitted for rail shipments.
ST*810*0001~
BIG*20160801*12345678901**DY 19999999***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*ST*3099~
N1*BT*3039~
N1*OB*3039~
ITD*01*3*2*20160816*15*20160831*30*2237****2% 15 Net 30 Days~
DTM*011*20160801~
TDS*111850**1109613~
CAD*R*ABCD*123456~
CTT*3~
SE*19*0001~
Freight Charge Example

This is an example of an invoice where there was a freight charge on the PO please note SAC segment. The
ship to and bill to are the same so N1*BS value from the N102 element of the 850 can be returned instead of
sending separate N1*ST and N1*BT segments.
Invoices submitted with freight charge where order in our system does not have corresponding freight charge
associated will be refused.
ST*810*0001~
BIG*20160801*12345678901**ECWE39999999***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*BS*3011~
N1*OB*3011~
ITD*01*3*2*20160816*15*20160831*30*2252****2% 15 Net 30 Days~
DTM*011*20160801~
TDS*112600**110348~
SAC*C*D240***750~
CTT*3~
SE*19*0001~
Special Order - Ship Direct to Guest
This is an example of an invoice for an order that was shipped direct to the guest. N1*ST, N1*BT and N1*OB
values from the N102 elements of the 850 will need to returned. N1*ST should be the guest name from the
N1*ST02 element of the 850.
ST*810*0001~
BIG*20160801*12345678901**ECWE39999998***DI~
CUR*SE*USD~
REF*VR*VENDR001~
N1*ST*BOB DOE~
N1*BT*3011
N1*OB*3011~
ITD*01*3*2*20160816*15*20160831*30*2252****2% 15 Net 30 Days~
DTM*011*20160801~
TDS*112600**110348~
SAC*C*D240***750~
CTT*3~
SE*20*0001~
Electronic Invoice Testing Guidelines
Vendor will notify us when ready to begin testing and time will be scheduled accordingly.
o Ready to test means 810 map has been built to spec and you are ready to receive test 850s and turn
around requested test 810s for review.
We will provide test 850 data for which 810 invoices should be created and returned. Tests will cover all
PO types/scenarios.
No test 810s should be transmitted to Menard Inc. unless advised to do so by your testing contact.
We will provide a standardized review of data and pass/fail the test data while noting specific problem areas
should they exist.
o In the event test data has issue it is expected that corrected 810 data will then be generated and
submitted for secondary review.
o Both format and content will be reviewed for accuracy.
Vendor will notify us when ready to receive test 864s, we will then transmit test 864s.
o We require 997s to be returned for each of the test 864s noting acceptance.
o The tests will reflect generic verbiage but will have the necessary elements present for you to test
your maps/processes for handling of the 864 messages.
In some specific cases upon completion of all required 810 and 864 testing, vendor may be asked to begin
providing 810s on all production EDI orders in a parallel test mode. Paper invoices will continue to be sent
for payment during this period, test 810s will not be processed for payment, simply transmitted for review.
o If vendor is currently submitting invoices electronically through our partners website this
parallel testing would not be performed.
After all required testing is completed we will coordinate/schedule a time to move the 810/864 to
production.
o We expect that extra care will be taken to make sure that we will not receive any duplicate invoices
no invoices submitted both via paper and/or the partners website and EDI.
o For those transitioning from paper invoices to EDI, no further paper invoices should be submitted for
payment after the defined last paper invoice.
o If invoices are currently being submitted through our partners website any remaining orders on the
website need to be invoiced through the website. EDI orders cannot be invoiced through the
website, WEB orders cannot be invoiced via EDI.
o When we move to production, we will need to know the last invoice number sent by paper and the
first invoice number sent via EDI.
Last paper invoice # would not be applicable for vendors currently invoicing through our
partners website.
Payments will continue to be made by paper check.
864 - Text Message (08/01/16)
ISA - Interchange Control Header Usage: Mandatory

ISA01 I01 Authorization Information Qualifier ID 2/2 03 = Additional Data Information
ISA02 I02 Authorization Information AN 10/10 Authorization ID (Menard Assigned Vendor #)
ISA03 I03 Security Information Qualifier ID 2/2 01 = Password
ISA04 I04 Security Information AN 10/10 Security Password (Menard Assigned Vendor #)
ISA05 I05 Interchange ID Qualifier ID 2/2 Sender's ID Qualifier
ISA06 I06 Interchange Sender ID AN 15/15 Sender's ID
ISA07 I05 Interchange ID Qualifier ID 2/2 Receiver's ID Qualifier
ISA08 I07 Interchange Receiver ID AN 15/15 Receiver's ID
ISA09 I08 Interchange Date DT 6/6 YYMMDD
ISA10 I09 Interchange Time TM 4/4 HHMM
ISA11 I10 Interchange Control Standards Identifier ID 1/1 U = ASC X12
ISA12 I11 Interchange Control Version Number ID 5/5 00401
ISA13 I12 Interchange Control Number NO 9/9 Sender's Interchange Control Num
ISA14 I13 Acknowledgment Requested ID 1/1 0 = No Ack (TA1) Requested
ISA15 I14 Test Indicator ID 1/1 P = Production Data, T = Test Data
ISA16 I15 Component Element Separator AN 1/1 >
GS - Functional Group Header Usage: Mandatory

GS01 479 Functional Identifier Code ID 2/2 TX = Text Message
GS02 142 Application Sender's Code AN 2/15 Sender's Identifier
GS03 124 Application Receiver's Code AN 2/15 Receiver's Identifier
GS04 373 Date DT 8/8 Date (YYYYMMDD)
GS05 337 Time TM 4/4 Time (HHMM)
GS06 28 Group Control Number NO 1/9 Sender's Group Control Number
GS07 455 Responsible Agency Code ID 1/2 X = ASC X12
GS08 480 Version/ Release/Industry Identifier Code AN 1/12 004010
ST - Transaction Set Header Usage: Mandatory

ST01 143 Transaction Set Identifier Code ID 3/3 864 = Text Message
ST02 329 Transaction Set Control Number NO 4/9 Sender's Transaction Set Control Number
BMG - Beginning Segment for Text Message Usage: Mandatory

Purpose
18 = Reissue required on 810 document
44 = Reissue required on 870 document
BMG01 353 Transaction Set Purpose ID 2/2 54 = Approval on 810 document
Invoice Number (BIG02 of the 810)
BMG02 352 Description AN 1/80 Report Number (BSR03 of the 870)
864 - Text Message (08/01/16)
MIT - Message Identification Usage: Mandatory

MIT01 127 Reference Identification AN 1/30 PO Number
MIT02 352 Description AN 1/80 High Level Summary
Loop ID - MSG
MSG - Message Text Usage: Mandatory
MSG01 933 Free Form Message AN 1/264 Free Form Message
End Loop ID - MSG
SE - Transaction Set Trailer Usage: Mandatory

SE01 96 Number of Included Segments NO 1/10 Total Number of Segments
SE02 329 Transaction Set Control Number NO 4/9 Transaction Set Control Number
GE - Functional Group Trailer Usage: Mandatory

GE01 97 Number of Transactions Sets Included NO 1/6 Total Number of Transaction Sets
GE02 28 Group Control Number NO 1/9 Group Control Number
IEA - Interchange Control Trailer Usage: Mandatory

IEA01 I16 Number of Included Functional Groups NO 1/5 Total Number of Functional Groups
IEA02 I12 Interchange Control Number NO 9/9 Interchange Control Number
Please note - 864 messages will not be returned for any 810 document that was rejected during translation.
997 rejection will be only notice returned to you advising document(s) have not been successfully translated
and need to be corrected/sent back through under new ISA/GS control #s.
Basic Validation Error

Upon receipt of an invoice, an initial check is performed to ensure general information such as PO#, Sku#, etc is valid
such that future processing will be able to perform a full match once the shipment arrives. If something is amiss, an 864
refusal is returned immediately.
ST*864*0001~
BMG*18*9876543210~
MIT*ECWE12345678*INVALID DATA ON INVOICE# 9876543210~
MSG*INVALID PO# FOR INVOICE 9876543210~
SE*5*0001~
Matching Validation Error

During the matching process, pricing and quantities from the invoice are checked against our system. If there is a
discrepancy that is equivalent to a dollar amount >$2 (or greater than the amount a vendor authorizes to deduct), an 864
refusal is returned to the vendor. This final matching process is not performed until initial receipt is performed against the
order.
ST*864*0001~
BMG*18*9876543210~
MIT*ECWE12345678*Invoice has been payment refused~
MSG*Item not received~
MSG*Sku: nnnnnnn Sequence: nnn~
MSG*Quantity invoiced (n) does not match quantity received (n)~
MSG*Sku: nnnnnnn Sequence: nnn~
MSG*Quantity invoiced (n) does not match quantity received (n)~
MSG* If you disagree, fax your concerns to the Store Operations Payment Refusal review team at 715-876-5964.~
MSG*Alternatively, an email can be sent to PRFresponse@menard-inc.com. All Authorizations to deduct are final.~
SE*11*0001~
Matching Success (Optional)

If everything is successful during the matching process, a message is sent back to the vendor noting that the invoice has
been matched and a code 54 is used in the BMG01 to denote an approval (versus code 18 used to denote a refusal).
This is an optional message and is sent by default. If the vendors credit dept does not wish to receive these messages,
they can confirm via e-mail that these are not required and we can forward request to ur AP department to have these
turned off.
ST*864*0001~
BMG*54*9876543210~
MIT*ECWE12345678*Matched~
MSG*Matched~
SE*5*0001~

810 Invoice

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

810 Invoice

Enviado por

Direitos autorais:

Formatos disponíveis

Implementation

q Menard, Inc. Electronic Commerce Information

q Business Rules 810 Invoice

q EDI Mapping Specifications 810 - Invoice

q 810 Business Examples

q Electronic Invoicing Testing Guidelines

q EDI Mapping Specifications 864 - Text Message

q 864 Business Examples

Documents Presently Traded:

EDI/INT Software: BizManager v3.3

AS2 URL: http://dmz-bizmgr.menard-inc.com:9080/msgsrv/as2

Authorization Information Qualifier (ISA 01): 03

Segment Delimiter: ~ (7E)

Production Validation Process

Element Description Detail Usage

ISA - Interchange Control Header Usage: Mandatory

GS - Functional Group Header Usage: Mandatory

ST - Transaction Set Header Usage: Mandatory

BIG - Beginning Segment For Invoice Usage: Mandatory

CUR - Currency Usage: Mandatory

REF - Vendor Account Number Usage: Mandatory

N1 - Ship To Location Usage: Mandatory

N1 - Bill To Location Usage: Mandatory

N1 - Ordered By Location Usage: Mandatory

ITD - Terms of Sale/Deferred Terms of Sale Usage: Mandatory

DTM - Date/Time Reference Usage: Mandatory

PID - Product/Item Description Usage: Mandatory

TDS - Total Monetary Value Summary Usage: Mandatory

CAD - Carrier Details Usage: Mandatory

End Loop ID - SAC

CTT - Transaction Totals Usage: Mandatory

SE - Transaction Set Trailer Usage: Mandatory

GE - Functional Group Trailer Usage: Mandatory

IEA - Interchange Control Trailer Usage: Mandatory

Standard Invoice - Net Terms

Standard Invoice - Prox Discounted Terms

Freight Charge Example

ISA - Interchange Control Header Usage: Mandatory

GS - Functional Group Header Usage: Mandatory

ST - Transaction Set Header Usage: Mandatory

BMG - Beginning Segment for Text Message Usage: Mandatory

MIT - Message Identification Usage: Mandatory

End Loop ID - MSG

SE - Transaction Set Trailer Usage: Mandatory

GE - Functional Group Trailer Usage: Mandatory

IEA - Interchange Control Trailer Usage: Mandatory

Basic Validation Error

Matching Validation Error

Matching Success (Optional)

Você também pode gostar