.left-arrow.case-study { left: calc(50vw + 683px - 54px - 70px); } .right-arrow.case-study { left: calc(50vw + 683px - 54px - 20px); }
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.

Related articles

DevelopersAPI guides

How to import and review transactions

Transactions (commonly known as claims) can be uploaded into Enable. The following sections will walk you through how and where to complete uploads and how and where to review previous uploads. This is broken down into the following sections:

How to find transactions import

Transactions in deals can be accessed by navigating to config in the green banner and selecting import transactions.

If you do not have access to the config or the transaction upload, please reach out to our support team here.

Uploading transactions

Transactions can be uploaded in deals via the wizard; these must be done for each partner individually. To upload transactions:

  1. Navigate to config > import transactions.
  2. Select which distributor (or manufacturer) you are uploading transactions for and click next.
  3. Download the template.
  4. Populate the template. For guidance on each of the columns, see how to populate the transaction template here.
  5. Upload the template and wait for validation to load.
  6. Validate your import. This stage will flag if there are any errors within the upload or will give a short summary of your transactions if there are no errors. If there are issues to resolve, you will need to click back and repeat steps 4 and 5.
  7. Review your import and complete.

If you encounter any issues during the upload process, please reach out to our support team here.

How to populate the transaction template

Unless otherwise stated, each of the fields within the CSV template will need to be populated. For each role, you will need to specify the following:

  • Date: the date of a transaction.
  • Distributor Branch (Distributor Branch): the branch reference number for the relevant distributor. Note the text in the brackets may vary depending on settings during your implementation process.
  • Delivery Type (Delivery Type): will either be Distributor delivery or Direct. Note the text in the brackets may vary depending on settings during your implementation process.
  • Product (Product): The product reference number. Note the text in the brackets may vary depending on settings during your implementation process.
  • End-customer: the end customer trading partner reference.
  • Currency: the currency configured on your agreement. Options are CAD, EUR, GBP, and USD
  • (Optional) External reference: a text field you can use to add additional information, often used for audit purposes to align with external systems. This field is only available if configured, please reach out to our support team here if you encounter issues.
  • Units: the total number of units for the transaction line.
  • Value: the total transacted value of the transaction line.
  • (Optional) Partner reference: this is the distributor (or manufacturer) reference; this is optional because the wizard used here provides this information when the file is imported.
  • (Optional) Agreement ID: this can be the system-generated ID of the SPA (you can find this on the SPA details page) or an external reference for the relevant SPA. If this column is filled out, the system will attempt to reconcile against the inputted reference. If this column is not filled in or the inputted reference does not match an eligible SPA, the system will calculate the SPA offering the highest support.
  • (Optional) Advised earnings: allows an expected claim amount to be uploaded, which will appear in the special pricing support report under distributor estimate. Please note that this is not used for calculating support but is a validation step to ensure alignment. If populated agreement ID will be mandatory.
  • (Optional) Order reference: a text field you can use to add additional information, often used for audit purposes to align with external systems.
  • (Optional) Delivery reference: a text field you can use to add additional information, often used for audit purposes to align with external systems.
  • (Optional) Invoice reference: a text field you can use to add additional information, often used for audit purposes to align with external systems.

How to review previous transaction uploads

Once you have successfully uploaded transactions, you can review the uploads via config > transaction logs. The logs will allow you to download the file that was uploaded and review the following information:

  • Partner: only shown to manufacturer users; this displays the partner the transactions belong to.
  • Import date: the day the upload occurred.
  • Imported by: the name of the person who performed the upload.
  • New or replacement: specifies whether the transactions were new or if they replaced existing transactions.
  • Value: the total value of the transactions uploaded and the currency of them.
  • Transactions: the count of transaction rows within the file.
  • Date range: the period the transactions covered; this will start with the oldest transaction in the file and end with the newest.
  • File: an icon to allow you to download the file which was uploaded and review the exact transactions uploaded.

Not useful
1
2
3
4
5
Very useful
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Still have questions?
Raise a ticket or contact our support team.