In Variable Overview, a user can create a variable that can be used for multiple calculations.

• This gives the user the freedom to dynamically set values for commissions or fees on Seller-level.
• Moreover, this way, VAT and WHT rates can be created individually for each Venture or country and can be applied on Seller-level.
• As a result, VAT and WHT rate calculations can be shown in the account statement and do not need any manual adjustment with an external tool (e.g., Excel files, etc.).

When adding a variable to the Transaction Rule Engine, the following information is required:

• “Variable Name”: Variable should have a unique name. Please make sure that this variable can be used by several transaction rules. Therefore, make sure that you are able to identify the variable easily.
• “Label”:  Generated automatically and used to fetch information with variable values.
• “Description”: A short explanation of the variable
• “Type”: Defines if a variable value should be generated as a number or as a percentage.
• “Inheritance Type”: You can define on which level you would like to manage values.
  • “Global”: One global value is applied.
  • “Global + Seller”: You can set a global value and a Seller-specific value.
  • “Category”: You can set global and Seller-specific values on category-level (same logic as the legacy way to set commissions on a category-level).

After defining all fields and clicking “Save Changes,” the variable will be saved and displayed in both Variable Overview and in variable values.

Variable Overview:

Create a variable:

In Transaction Rules Overview, you can create and search for transaction rules. By clicking on a rule name, you are able to see all of its details.

To enable or disable rules simultaneously, do the following:

1. Click the “Enable” or “Disable” button. Status will change to “Ready to be enabled” or “Ready to be disabled”
2. Click “Publish changes” button to save changes.

When adding a transaction rule, the following information is required:

• “Rule Name”: Rule should have a unique name and be as specific as possible in order to simplify the search.
  • Bad example: “Commissions” (too generic)
  • Good example: “Commission for local Sellers for drop shipping orders”
• “Account Statement Group”: Linked to transaction type and will be shown in account statements. You can find a list with predefined account statement groups. If you wish to create a custom account statement group, please refer to the Account Statement Groups Overview.
• “Description”: A short explanation of the transaction rule
• “Outcome”: Defines which type of transaction should be generated. Please make sure that the outcome name is included in your account statement group.
• “Enable pre-calculation”: Defines whether or not to specify events for transaction pre-calculation.
• “Pre-calculated on”: Specifies the events that will trigger the pre-calculation.
• “Events”: It is possible to choose one or multiple events that the transaction should be triggered by.
• “Condition”: Defines restrictions that have to be fulfilled for the rule to be applied (e.g., FirstDayofMonth && item.ShippingTypeIsDropshipping).
• “Net Amount Formula”: Defines the calculation that will be generated with the transaction rule before taxes.
• “VAT Formula”: Calculates a VAT rate using the outcome from net amount formula amount (will be displayed in account statement).
• “WHT Formula”: Calculates a WHT rate using the outcome from net amount formula amount (will be displayed in account statement).
• “Add to the latest closed account statement”: The created transaction will be associated with the previously closed account statement and correct the payout (click the link to read more about the feature).

After defining all fields and clicking “Save Changes,” the transaction rule will be saved and propagated in Transaction Rule Overview.

Transaction Rules Overview:

Enable/disable rules:

Create a transaction rule:

In the “Variable Value” tab, you can see a list with variables and edit values by clicking “Edit.” Depending on the inheritance type, you can set values on global or Seller-level, as well as on category-level.

Variable Values Overview:

Edit values:

The following tab is only visible to Seller Center’s maintenance team in order to simplify the context/attribute creation process.

When adding a context/attribute, the following information is needed:

• “Label”: Define a label that will be shown as an option during transaction rule creation.
• “Type”: Defines a value of the expression.
• “Description”: A short explanation of created context
• “Event”: Multiple events can be shown where macro can be used.
• “Expression”: Code of the macro

Macros Overview:

Create a macro:

In Account Statement Groups Overview, a user can create account statement groups that will be linked to one of the default transaction types.

• Account statement groups will allow Ventures to create transaction rules in combinations that were not possible before (e.g., two or more rules generating transactions with the same reference and transaction type).

The only constraint for duplication protection is set regarding the account statement group/reference combination: in no case will the rules generate two transactions for the same account statement group/reference pair.

When adding a new account statement group, the following information is needed:

• “Account Statement Group Name”: Define a custom account statement group name.
• “Transaction Type”: Choose the transaction type from the default list.
  • This will be displayed for the Seller in the overview and account statement.
• “Outcome”: Transaction outcome (Credit / Debit), which gets applied to the Account Statement
  • Will be applied for all rules, which use a certain account statement group

After defining all fields and clicking “Save Changes,” the account statement group will be saved and displayed in the list when creating a transaction rule.

Account Statement Groups Overview:

Create a new account statement group: