Optional
XLSXFileOptional
active?: booleanOptional
remarks?: stringOptional
sheetOptional
strategy?: "asLineItemList" | "asPDF"Optional
aliasOptional
automatedOptional
customerOptional
customsOptional
GRN?: stringOptional
GRNAccessOptional
LRN?: stringOptional
declarantOptional
dakosyOptional
active?: booleanOptional
dataOptional
active?: booleanOptional
annotationOptional
classification?: { Optional
automateValue between 1 (very confident) to 0 (no confidence)
Optional
automateDefines whether a classification shall be assumed correct if a specific confidence level is reached
Optional
classifyWhether to classify using dexter classification or let user manually classify
Optional
engine?: "default" | "dexter_experimental" | "llm"Optional
engineOptional
exportOptional
llmOptional
classificationOptional
extractionOptional
onlyOptional
overridefor rossum
Optional
promptOptional
queueOptional
requireOptional
requireOptional
dataOptional
active?: booleanOptional
createOptional
active?: booleanOptional
createOptional
active?: booleanOptional
aggregated?: booleanOptional
threshold?: numberOptional
createOptional
active?: booleanOptional
createOptional
active?: booleanOptional
createOptional
active?: booleanOptional
createOptional
active?: booleanOptional
createOptional
active?: booleanOptional
masterControls master data integration automation settings
Optional
autoImmediately confirm master data entries that were created automatically (in technical terms: mark them as user-edited)
Optional
createEnable creation of material master data that does not exist yet
Optional
createEnable creation of stakeholder master data that does not exist yet
Optional
createEnable creation of tariff number master data that does not exist yet
Optional
materialGeneral integration options for both material and tariffNumber based master data
Optional
additionalControls how additional material properties are handled
Optional
propagateIf true, material tags from items will be added to existing tags If false, tags will not be propagated Default: false
Optional
updateCASNumbers?: booleanIf true, CAS numbers from items will update material CAS numbers Default: true
Optional
updateIf true, gross weights from items will update material gross weight Default: true
Optional
updateIf true, net weights from items will update material net weight Default: true
Optional
updateIf true, units of measurement from items will update material UoM Default: true
Optional
documentControls document code integration from different sources.
Optional
persistOptional
historyControls how history data is configured and managed
Optional
enabledControls which historical data should be tracked
Optional
countryTrack country of origin changes over time
Optional
prices?: booleanTrack price changes over time with associated quantity info
Optional
maxMaximum number of entries to keep in each history. Default: 10
Optional
trackIf true, recipients will be tracked in the history with NO limit(!). Needs to be true for useRecipientOrImporter to work for matching
Optional
persistThis is always persisted for tariff number based master data, but needs to be explicitly enabled for material based master data
Optional
persistIf any descriptions were found in the shipment item, they will be persisted in the master data If update mode is active, the descriptions will be replaced on each update (except if the new description is empty)
Optional
tariffMatching options for tariff number master data, effectively which properties from the shipment will be used to match the tariff number These properties from the shipment (and item) will also be automatically persisted in the master data, each combination of these properties will be a separate master data entry
Optional
useOptional
useOptional
useOptional
useOptional
useOptional
updateEnable updates of fields in automatically created materials
Optional
updateEnable updates of fields in automatically created stakeholders
Optional
updateEnable updates of fields in automatically created tariff numbers
Optional
updateEnable updates of fields in manually created materials
Optional
updateEnable updates of fields in manually created stakeholders
Optional
updateEnable updates of fields in manually created tariff numbers
Optional
requireOptional
dataOptional
active?: booleanOptional
addOptional
additionalDetermines how to deal with additional costs like shipping costs, packing, ...
Optional
aggregateOptional
aggregateDetermines whether or not to aggregate (sum up) pallets together with other package types
Optional
allowOptional
alwaysOptional
alwaysOptional
alwaysOptional
assumeOptional
assumeOptional
calculateOptional
calculateOptional
calculateOptional
grossOptional
netOptional
checkDetermines whether trade preference shall be invalidated if wording or spelling is wrong
Optional
customsCustom formatting for transforming the (autofixed) customs tariff number into a new tariff number. Default to empty (no mapping used).
The input JSON object has the same structure as the descriptionFormatStringJsonAta:
{ "tariffNumber": "1234567890", "quantity": 1234, "tariffNumberDescription": "Einrichtungen, Maschinen, Apparate und Geräte zur Kälteerzeugung", "lineItemDescription": "Orsiro Mission 2.5/9 PTCA-Stents ", "lineItemDescriptionShort": "Orsiro Mission PTCA-Stents ", "materialDescription": "PCTA-Stents", "enrichedDescription": "PCTA-Stents", "enrichedDescriptionShort": "Stents", "preferMaterialMasterData": false, "materialMatched": true, "useCustomsTariffNumberDescription": true, "useLineItemDescriptionShortening": true, "materialMatchedByTariffNumber": true, "materialMatchedByMaterialNr": false }
Optional
customsOptional
defaultOptional
defaultOptional
descriptionCustom formattings for the resulting description of line items. For more complex conditional formattings, use the JSONAta property instead.
Possible variables are:
All these variables can be combined with an optional separator to include after the variable. This separator will only be printed if the variable is not empty. Format: {variable}[separator]
Examples: {tariff-number-description}[ - ]{enriched-description} {tariff-number-description}[ - ]{enriched-description-short} {tariff-number-description}[ - ]{line-item-description} {material-description}[ - ]{line-item-description} {enriched-description-short}
Optional
descriptionCustom formattings for the resulting description of line items as a GPT prompt.
{ "tariffNumber": "1234567890", "quantity": 1234, "tariffNumberDescription": "Einrichtungen, Maschinen, Apparate und Geräte zur Kälteerzeugung", "lineItemDescription": "Orsiro Mission 2.5/9 PTCA-Stents ", "lineItemDescriptionShort": "Orsiro Mission PTCA-Stents ", "materialDescription": "PCTA-Stents", "enrichedDescription": "PCTA-Stents", "enrichedDescriptionShort": "Stents", "preferMaterialMasterData": false, "materialMatched": true, "useCustomsTariffNumberDescription": true, "useLineItemDescriptionShortening": true, "materialMatchedByTariffNumber": true, "materialMatchedByMaterialNr": false }
Optional
descriptionCustom formattings for the resulting description of line items as a JSONAta query. The result must be a string, not an object. The "simpler" descriptionFormatString will be ignored if this is set.
The input JSON object looks like this:
{ "tariffNumber": "1234567890", "quantity": 1234, "tariffNumberDescription": "Einrichtungen, Maschinen, Apparate und Geräte zur Kälteerzeugung", "lineItemDescription": "Orsiro Mission 2.5/9 PTCA-Stents ", "lineItemDescriptionShort": "Orsiro Mission PTCA-Stents ", "materialDescription": "PCTA-Stents", "enrichedDescription": "PCTA-Stents", "enrichedDescriptionShort": "Stents", "preferMaterialMasterData": false, "materialMatched": true, "useCustomsTariffNumberDescription": true, "useLineItemDescriptionShortening": true, "materialMatchedByTariffNumber": true, "materialMatchedByMaterialNr": false }
Examples:
Built-In Standard formatting depending on various state variables: useCustomsTariffNumberDescription and ( preferMaterialMasterData = false or materialMatched = false ) and $exists(tariffNumberDescription) and $string(tariffNumberDescription) != "" ? tariffNumberDescription & " - " & ( useLineItemDescriptionShortening = true and materialMatched = false ? (($exists(lineItemDescriptionShort) and $string(lineItemDescriptionShort) != "") ? lineItemDescriptionShort: lineItemDescription) : ( materialMatched = true ? materialDescription : ( useLineItemDescriptionShortening = true ? lineItemDescriptionShort : lineItemDescription ) ) ) : enrichedDescription
Example Result with JSON input from above: "Einrichtungen, Maschinen, Apparate und Geräte zur Kälteerzeugung - PCTA-Stents"
Static formatting for customer preferring combined material and line-item descriptions: $exists(materialDescription) and $string(materialDescription) != "" ? materialDescription & ' - ' & lineItemDescription : lineItemDescription
Example Result with JSON input from above: "PCTA-Stents - Orsiro Mission 2.5/9 PTCA-Stents"
Optional
disableOptional
disableOptional
doDefault: Assume origin from preference. Set to true to mitigate this behavior
Optional
documentOptional
add3LNAQualifiers?: booleanOptional
addOptional
blacklistOptional
noOptional
eliminateOptional
emailOptional
enforceOptional
forceOptional
forceOptional
forceOptional
forceOptional
forceOptional
forceOptional
foreignBetween 0 and 1
Optional
freightOptional
active?: booleanOptional
maximumOptional
minimumOptional
packageif strategy = packageDependent
Optional
priority?: "fallback" | "override"Optional
relativeIf strategy === relative then goods value is multiplied by this multiplier to receive freight costs
Optional
strategy?: "default" | "austriaWeightDependent" | "packageDependent" | "distanceDependent" | "relative" | "containerSizeDependent"Optional
guaranteeOptional
guaranteeOptional
guaranteeOptional
ignoreOptional
ignoreOptional
ignoreOptional
ignoreOptional
keepOptional
lineOptional
maxOptional
normalizeDetermines whether or not data from incoming emails are extracted and normalized.
false
Optional
normalizeOptional
prioritizeOptional
prioritizeOptional
remarks?: stringOptional
omitWhen set to true, line item descriptions will be omitted from the final goods description (if possible, if no other description is available it will be used).
Optional
preferOptional
preferOptional
preferOptional
removeOptional
active?: booleanOptional
searchOptional
active?: booleanOptional
specializedExperimental: Use specialized formatting for aggregated descriptions. This will be used if useSpecializedDescriptionAggregation is set to true. If not set, uses the default descriptionFormatStringJsonAta and aggregation algorithm. The input for this JSONAta query is an array of lineItemContexts.
Optional
statisticalOptional
statisticalOptional
translateOptional
active?: booleanOptional
destinationOptional
useOptional
useEnables experimental feature to use specialized description aggregation for line items, summing up quantities and concatenating lineItemDescriptions with "-" in the special "aggregated.aggregatedDescriptions" map (otherwise this property will remain empty or undefined).
Optional
waybillOptional
dataOptional
active?: booleanOptional
fraudOptional
defaultOptional
defaultOptional
doOptional
doOptional
eventsOptional
flagsOptional
forceOptional
forceOptional
handleXLSXFileOptional
hsOptional
active?: booleanOptional
research?: booleanOptional
idOptional
importOptional
active?: booleanOptional
sftp-Optional
sftp-Optional
sftp-Optional
sftp-Optional
sftp-Optional
sftp-Optional
isOptional
isOptional
masterOptional
useOptional
matchingOptional
materialOptional
disableOptional
disableOptional
disabled?: booleanOptional
sendOptional
sendOptional
tariffOptional
matchOptional
stakeholderOptional
mergeOptional
moduleOptional
procedureOptional
projectOptional
pseudonymizationOptional
active?: booleanOptional
interval?: numberOptional
time?: numberOptional
referenceOptional
ruleOptional
sortSort line items before applying line item rules with annotateOnlyFirstLineItem. This influences which ones of these line items will be annotated. Default value: position
Optional
ruleOptional
rulesOptional
submissionOptional
subscriptionOptional
uploadOptional
userOptional
whitelisted
Execution strategies are customer-configurable plans on how to process a specific case.