Data substitution mapping and configuration - 810 match invoice
This section describes EDI Data Substitution records that are related to processing X12 810 Invoice transactions to EDI Invoice Match Interface Input records.
Disable mapping payment terms
Disable mapping of payment terms from an ITD segment.
- Configuration
- Optional
- Default Behavior: Map Discount, Discount Days and Net Due Days from ITD segment.
Vendors can include an ITD segment to communicate payment terms. If the discount days, discount date, and net due data fields are specified, they are mapped to the EDI Match Interface Input. The settings on your Terms Code are overridden, which may cause problems if the vendor's payment terms are different then the payment terms in your setup.
Use L1_MAP_INV_TERMS record with a Your Value of N to disable mapping payment terms from an ITD segment. Your Terms Code is used on the match invoice from the defaulting rules.
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_MAP_INV_TERMS | ||
| Your Value | N | ||
| Partner Value | <tpid> or * | Use * to disable for all 810 |
Setting the invoice posting date
- Configuration
- Optional
- Default Behavior: Invoice Posting date value is not set.
- Related:
| Field | Value | Example | Comment |
|---|---|---|---|
| List name | SET_INV_POST_DATE | ||
| Your value | N | N disable mapping | |
| Partner value | <tpid> -or- * | Trading partner id or * for all trading partners | Use * to disable for all partner 810s |
Use to address the issue with 810 Invoices that are received but not processed before month end is closed. Electronic invoices or X12 810 invoices contain an invoice date. If no posting date is specified when processing invoices, then the invoice date is used. If an electronic invoice is processed after month end closing and the invoice date is in the closed period, the invoices cannot be loaded.
Enabling SET_INV_POST_DATE with a Your Value of Y sets the invoice posting date to when the 810 was translated.
Disable mapping ship to GLN
- Configuration
- Optional
- Default Behavior: All GLNs are mapped to interface input records.
- Related: L1_I_USE_GLN
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | MAP_SHIPTO_GLN | ||
| Your Value | N | N disable mapping | |
| Partner Value | <tpid> or * | Use * to disable for all partner 810s |
If you are using GLNs, the default behavior is to map all GLNs from the 810 to the EDI Match Interface Input. Except for specific cases where a ship to location is used in match rules, a ship to is unnecessary and may cause problems in the match process. Use the MAP_SHIPTO_GLN record with a Your Value of N to disable mapping a ship to GLN.
Set the invoice type
- Cross-reference
- Optional
- Default Behavior: The invoice type is not set. If invoice type is blank, then the invoice is processed as a normal match invoice.
- Related:
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_INVOICE_TYPE | Applies to all trading partner IDs | |
| Your Value | C | C for credit | |
| Partner Value | <BIG07> | CR, CI |
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_INVOICE_TYPE | Use for a specific trading partner | |
| Your Value | C | C for credit | |
| Partner Value | <BIG07> | CR, CI |
The primary usage is to enable processing of credit invoices. This data substitution record is used to cross-references the value in BIG07 with the invoice type code C for Credit Memo.
Set the process type
- Cross-reference
- Optional
- Default Behavior: Process Type is not mapped.
- Related: ALL_INVOICES
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_PROCESS_TYPE | Use this to set for a specific trading partner ID | |
| Your Value | B | Use B to set to Basic/Expense. Use V to set the type to Service Contract. |
|
| Partner Value | <BIG07> or * |
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_PROCESS_TYPE | Using this will set for all trading partner ID values. | |
| Your Value | V | Use B to set to Basic/Expense. Use V to set the type to Service Contract. |
|
| Partner Value | <BIG07> |
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_INVOICE_HC | Use this to set for a specific trading partner id | |
| Your Value | B | Use B to set to Basic/Expense. Use V to set the type to Service Contract. |
|
| Partner Value | <BIG07> or * |
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_INVOICE_HC | Use this to set for all trading partner id values. | |
| Your Value | V | Use B to set to Basic/Expense. Use V to set the type to Service Contract. |
|
| Partner Value | <BIG07> |
Use to set the Process Type based on the value that is sent in BIG07. Process Type is also known as Invoice Entry Template.
Process Type can be set for a specific trading partner ID <tpid> or for all trading partners using the reserved L1 trading partner ID.
There are two variations: _PROCESS_TYPE and _INVOICE_HC. _INVOICE_HC is available for backward compatibility.
Use Account Number in N1BT
- Configuration
- Optional
- Default Behavior: Use account number in N1ST04
- Related:
- GHX ONLY
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_I_810_USE_N1BT | ||
| Your Value | Y | ||
| Partner Value | ENABLED |
GHX specific mapping to use the N1BT04 element to lookup company, vendor and other values for cross-reference instead of the N1ST04 element value.
Disable mapping invoice line numbers
- Configuration
- Optional
- Default Behavior: Map line numbers from 810 if record does not exist with value N
- Related: L1_I_USE_810_ITEMNUMBERS
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_I_810_LINENUMBERS | ||
| Your Value | N | ||
| Partner Value | <tpid> OR * |
Use the L1_I_810_LINENUMBERS substitution to disable mapping invoice line numbers if the invoice lines do not reliably match the PO line numbers.
The default behavior is to map invoice line numbers from the 810. This helps matching if the line numbers match the PO Line numbers. If a number is not included in the IT101 element the line sequence number is used. If it is a partial invoice, the line numbers may not match. The vendor 810 may also use a different numbering format. If a vendor substitutes an item, they may cancel the original line and add a new line.
Disable mapping item numbers
- Configuration
- Optional
- Default Behavior: item numbers qualified with IN are mapped.
- Related: L1_I_810_LINENUMBERS
- GHX Only
| Field | Value | Examples | Comments |
|---|---|---|---|
| List name | L1_I_USE_810_ITEMNUMBERS | ||
| Your value | N | ||
| Partner value | ENABLED |
This is a legacy GHX specific data substitution to disable mapping buyer item numbers from invoice lines. It is included for backwards compatibility. As implemented by GHX, Partner Value is ENABLED and Your value is N to disable mapping your item numbers from the invoice lines.
Trading Partner Item specific UOM lookup depends on the item being mapped.
Disable mapping zero cost invoice lines
- Configuration
- Optional
- Default Behavior: All invoice lines are mapped.
- Related: None
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | MAP_ZERO_COST | ||
| Your Value | N | ||
| Partner Value | <tpid> or * |
Invoice matching problems can occur if a vendor includes zero-cost items on their invoice that are not on the original PO. This mapping configuration provides a way to disable mapping invoice lines for zero-cost or no-charge items.
Disable mapping GTINs - MAP_GTIN
- Configuration
- Optional
- Default Behavior: GTINs are mapped by default.
- Related:
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | MAP_GTIN | ||
| Your Value | N | ||
| Partner Value | <tpid> or * |
Invoice line matching problems can occur if the vendor includes GTIN for an item and it does not match or you do not use GTINs. This mapping configuration provides a way for you to disable mapping the GTIN for invoice lines for a trading partner.
Map PO number to external PO
- Configuration
- Optional
- Default Behavior: PO Number is mapped to PO Number field if CREATE_EXPENSE_INVOICES is not enabled.
- Related: ALL_INVOICES_ARE_EXPENSE, CREATE_EXPENSE_INVOICES
| Field | View | Example | Comment |
|---|---|---|---|
| List Name | MAP_TO_EXTERNAL_PO | ||
| Your Value | Y | ||
| Partner Value | <tpid> or * |
Use to move PO Number to External Purchase Order. If the PO Number is invalid because it is too large or has non-numeric characters, the import will fail and records are written to EDI Work. Use this data substitution to enable interfacing the invoice by mapping the PO Number to External Purchase Order field.