Tax
These data substitution records control how invoice tax is mapped to the Match Interface Input.
The 810 invoice may have multiple TXI (tax) segments at the invoice level and/or the detail line level. The EDI Invoice Match Interface process does not support multiple taxes or tax codes. Tax is only at the Invoice Header. The default behavior is to total the line tax and total the invoice tax. If the total invoice tax is not empty that is mapped to the Header Tax Amount field. If total invoice tax is empty, the total line tax is mapped to the Invoice Header Tax Amount field.
Disable mapping AOC tax
- Configuration
- Optional
- Default Behavior: All taxes are totaled at the line level and invoice/summary
- Related: MAP_AOC_LEVEL
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | MAP_AOC_TAX | ||
| Your Value | N | ||
| Partner Value | <tpid> |
Use to disable mapping TAX amount from a TXI segment that is associated with an Add On Cost. Some vendors may itemize the tax related to an Add on cost if it is taxable and then include the amount in the total tax. The default 810 mapping totals all line level TXI tax amounts and invoice level TXI tax amounts. This can effectively double the total tax amount when vendor sends both. Use the MAP_AOC_TAX with a Your Value of N to disable mapping the SAC level TXI segments.
Map tax as add on cost for all partners
Enables mapping a specific x12 tax code to an Add On Cost record for all trading partners.
- Cross-reference
- Optional
- Default Behavior: Add tax amount to total line tax or total invoice tax if no matching L1_TAX_TO_AOC record found.
- Related: <tpid>_TAX_TO_AOC, MAP_AOC_LEVEL
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_TAX_TO_AOC | ||
| Your Value | <your AOC code> | ||
| Partner Value | <TXI01> |
Use when you do not have tax on the purchase order and want to map the tax from a TXI segment to an Add On Cost. If a record matching the TXI01 is found an Add on Cost record will be created with the AOC code and the tax amount. Line Tax will create a Line Level AOC record. Invoice total tax will create a Miscellaneous Add On Cost record. The MAP_AOC_LEVEL level determines if the AOC record is created.
Map tax as add on cost for specific partner
Enables mapping a specific x12 tax code to an Add On Cost record for a specific trading partner ID.
- Cross-reference
- Optional
- Default Behavior: Use L1_TAX_TO_AOC lookup if a matching record is not found.
- Related: L1_TAX_TO_AOC, MAP_AOC_LEVEL
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_TAX_TO_AOC | ||
| Your Value | <your AOC code> | ||
| Partner Value | <TXI01> |
Use when using an L1_TAX_TO_AOC record is not desired or cannot be used because the partner uses a code to represent a different tax then the default or tax scenarios require different AOC codes.
Total tax as AOC
GHX specific mapping convert the total tax amount to a Miscellaneous Add On Cost.
- Configuration
- Optional
- Default Behavior:
- Related:
- Requires: L1_I_ADDON record to specify the AOC code to use for tax.
- GHX Only
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_I_810_TAX_IS_AOC | ||
| Your Value | Y | ||
| Partner Value | ENABLED |
Use this record to convert the total tax as miscellaneous AOC cost if you are using the GHX map. If this process is enabled, and there is total tax, then the tax amount is 0 and a miscellaneous AOC record is added with the amount.
This process is like the TAX_AS_AOC record, but it applies to summary tax total amount and not to individual TXI tax segments.
Tax AOC code
- Cross-reference
- Optional
- Default Behavior:
- Related: L1_I_810_TAX_IS_AOC
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_I_ADDON | ||
| Your Value | <addon code for tax > | ||
| Partner Value | TAX |
Use an L1_I_ADDON record to set the AOC code to use for tax with L1_I_810_TAX_IS_AOC