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

Manually importing sales transactions for SPAs

Transactions for sales can be uploaded into the Enable platform to calculate special pricing agreement (SPA) support.

This article will guide you through:

  1. How to manually import sales transactions
  2. How to use the import transactions wizard for sales
  3. How to populate the transaction template for sales

Looking for something else?

How to manually import sales transactions

Channel admin users have access to the Config area and transaction uploads within Enable. If you require additional help, please reach out to our support team here.

To access the import transactions wizard in the Special pricing agreements app:

Step 1: Click on Config in the green banner at the top of the page

Step 2: Click on Import transactions in the drop-down menu.

Manufacturer view of Import transactions

Distributor view of import transactions

How to use the import transactions wizard for sales

Sales transaction imports via the wizard are done for each trading partner individually. To upload sales transactions:

Step 1: If your organization is a manufacturer, search by distributor name or reference, select the trading partner you are uploading sales transactions for and click Next. If your organization is a distributor, this step won’t apply in the import wizard.

Step 2: Click to download the sales transactions template. Upon downloading, you will be automatically taken to the Upload stage of the wizard.

Step 3: Populate the transactions template with your sales. For guidance on each of the columns, see how to populate the transaction template for sales below.

Step 4: Drag and drop the completed sales transactions file into the box in the Upload stage, or click to browse file selection to upload the completed sales transactions file. Wait for validation to load.

Step 5: Validate your import. This stage will display a summary of issues if any exist for the upload, or display give a short summary of your sales transactions if there are no errors. If there are issues to resolve, you will need to click Back and repeat steps 4 and 5.

Import transactions: Validation issues

Step 6: Review details of your import and click Submit for the sales transactions file to import.

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

How to populate the transaction template for sales

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

  • Date: The date of the sale, in the format YYYY-MM-DD, e.g. 2024-01-31 for 31st January 2024.
  • Distributor Branch (Distributor Branch): The branch reference number for the relevant distributor. Note the text in the brackets may vary depending on settings determined during your implementation process.
  • Delivery Type (Delivery Type): Enter either Distributor delivery or Direct. Note the text in the brackets may vary depending on settings determined during your implementation process.
  • Product (Product): The product reference number. Note the text in the brackets may vary depending on settings determined during your implementation process.
  • End-customer: The end customer trading partner reference.
  • Currency: The currency of the sale, e.g. USD, GBP, CAD or EUR. Each transaction file can only support one currency; if sales need to be imported for different currencies, one transaction file should be used per currency.
  • (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.
  • Units: The total number of units for the sale. Units can have no more than 4 decimal places.
  • Value: The total monetary transacted value of the sale. A value can have no more than 2 decimal places.
  • (Optional) Interface Date: If enabled in your channel, populate the interface date with the date of the import, in the format YYYY-MM-DD, e.g. 2024-01-31 for 31st January 2024.
  • (Optional) Order Line Item: A text field you can use to add additional information, often used for audit purposes to align with external systems.
  • (Optional) Partner Reference: The distributor/manufacturer reference. This field is optional since the import transactions wizard (see above) provides this information when the sales transactions file is imported.
  • (Optional) Agreement ID: If required, populate with the SPA reference (displayed on the SPA details page) to which this sales transaction line will earn support against. If this column is populated, the Enable platform will attempt to reconcile against the inputted SPA reference. If this column is not populated, the Enable platform will attempt to match the transaction to a SPA; if a transaction matches to two or more SPAs, the transaction will be matched to the SPA with the earliest end date.
  • (Optional) Advised Earnings: Allows an expected monetary claim amount to be specified, which will appear in the special pricing support report under distributor estimate; this is typically the earnings a distributor thinks they should be receiving, and therefore rarely generated by a manufacturer. Please note that this is not used for calculating support but is a validation step to ensure alignment. If Advised earnings is populated, then Agreement ID will be mandatory. Advised earnings can have no more than 2 decimal places.
  • (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.

What’s next?

Ready to view the status of your transaction import? Learn how to review transaction logs for SPAs here.

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.