Configuration and Administration
gtm.dutyTax Properties
To control the behavior of Global Trade Management, you can change settings in the glog.properties file or the appropriate property set.
The following properties are used in the Classification > Duty and Tax Analysis window. The product classification selected on this screen will be sent to the external content provider to obtain the duties and taxes which may be applied to a specific product on a trade transaction.
Property |
New in Version |
Description |
---|---|---|
6.3 |
This property identifies the external system to which the duty and tax request will be sent. |
gtm.dutyTax.dsg
This group of properties is mainly used in the Estimate Duty and Taxes window. These properties are required to configure the system to send trade transaction information to a third party data provider and obtain duty and tax values for a trade transaction or a line for calculating the landed cost.
Note: Do not modify these properties unless directed by OTM/GTM Support.
Static Properties
Following are the static properties shipped with GTM:
Property |
New in Version |
Description |
---|---|---|
6.4 |
This property is used to send the export date against this date qualifier to the tax engine. Default: EXPORT DATE Note: The value of this property should be same as that of the property gtm.lcs.dateOfExport.dateQualifier. |
|
6.4 |
This property identifies the external system to be used for tax callout. Default: EXTERNAL_SYSTEM_TAX |
|
6.4 |
This property allows you to block tax callout to the external system. Default: True |
|
6.4 |
This property allows you to block the processing of the duty retrieved from the tax engine. Default: True |
|
6.4 |
This property allows you to block the processing of the tax retrieved from tax engine. Default: True |
|
6.4 |
This property is used to send the duty tax quantities against this quantity qualifier to the tax engine. Default: ORDERED |
|
6.4 |
This property is used to send the location details as source location against this location qualifier to the tax engine. Default: SHIP_FROM Note: The value of this property should be same as that of the property gtm.lcs.shipFromLocation.locationQualifier. |
|
6.4 |
This property is used to send the location details as destination country against this location qualifier to the tax engine. Default: SHIP_TO Note: The value of this property should be same as that of the property gtm.lcs.shipToLocation.locationQualifier. Note: It is mandatory to configure this property to perform the Look Up Trade Program action on a transaction/transaction line/declaration/declaration line. Else, an error will be displayed. |
In addition to the above properties, GTM also supports some dynamic properties to handle the duty and tax request and response.
Duty and Tax Request Properties
The third party data provider accepts values classified under five categories as part of the request XML. The categories are:
- COST_OF_GOODS
- FREIGHT_AMOUNT
- DUTIABLE_FREIGHT_AMOUNT
- INSURANCE
- OTHERS
You can map a value with one of these five categories by adding a property in the following format:
- gtm.dutyTax.dsg.requestMapping.valueQualifier.<gtm value qualifier>=<Third Party Data Provide Value Category>
For example, you can map the DOMESTIC FREIGHT of GTM with FREIGHT_AMOUNT category of the data provider by adding a property gtm.dutyTax.dsg.requestMapping.valueQualifier.DOMESTIC FREIGHT=FREIGHT_AMOUNT
Following are the properties shipped with GTM to cover value mappings:
Duty and Tax Response Properties
There might be different kinds of custom charges applicable for the imported goods. The third party data provider replies to GTM request with all those duty and taxes by classifying them under four different categories. These custom charges categories are:
- DUTY
- VAT
- EXCISE TAX
- OTHER TAX
You can use the following property format to map all taxes under a data provider category to a single GTM value qualifier:
- gtm.dutyTax.dsg.responseMapping.valueQualifier.<custom category>=<GTM value qualifier>
Alternatively, you can use the following property format to treat a custom charge as special and save it against a single value qualifier:
- gtm.dutyTax.dsg.responseMapping.valueQualifier.<custom category>.<tax group short name>=<GTM value qualifier>
Following are the default properties shipped with GTM to handle the response mappings:
Property |
New in Version |
Description |
---|---|---|
6.4 |
This property is used to save the DUTY returned by the data provider against DUTY qualifier in GTM. Default: DUTY |
|
6.4 |
This property is used to sum up and save all the taxes returned by the data provider with EXCISE as tax category against EXCISE TAX qualifier in GTM. Default: EXCISE TAX |
|
6.4 |
This property is used to sum up and save all the taxes returned by the data provider with OTHER as tax category against OTHER TAX qualifier in GTM. Default: OTHER TAX |
|
6.4 |
This property is used to save the harbor maintenance fees of OTHER TAX category against HMF qualifier in GTM. Default: HMF |
|
6.4 |
This property is used to save the merchandise processing fees of OTHER TAX category against MPF qualifier in GTM. Default: MPF |
|
6.4 |
This property is used to sum up and save all the taxes returned by the data provider with VAT as tax category against VAT qualifier in GTM. Default: VAT |
Related Topics
Properties Setup for Landed Cost
Response Structure Information