Bulk Transaction Uploads
Read about how to add transactions using a CSV file.
You can upload a group of transactions in bulk using the file upload feature. The file must use the CSV format and UTF-8 encoding.
Preparing the CSV File
The file must include the following columns:
- Transaction ID
- Order Date
- Transaction Value
- Currency Code
- Transaction Type
Evidence is prioritized as follows:
- Billing country
- IP address
- Credit Card BIN
- Payment method country
- Other commercially relevant information
The following table list all the possible columns or fields. Mandatory fields are denoted by an asterisk:
| Field | Type | Comments |
|---|---|---|
| Transaction ID | Alphanumeric | This ID must be unique except when a transaction is refunded. In this case, you must list the sale before the refund. |
| Order Date | Date DD/MM/YYYY | This is the transaction date. The quarter that the transaction is settled in is based on this date. Ensure that the date and time are specified in the merchant's time zone. For refunds , this date is used as the refund timestamp. |
| Transaction Value* | Numeric MMM.nn | The total transaction value. To create a placeholder transaction for a subscription, enter 0.00. |
| Currency Code* | ISO 4217 | The three letter code that represents the transaction currency. |
| Credit Card Bank Identification Number (BIN) | 6-9 Numeric | The first 6 digits of the credit card number that identifies the issuer of the card. Evidence priority: 3. |
| Payment Method Country | ISO 3166 - 2 Alpha | If this is provided, it is used instead of the BIN. For example, you can derive this value from the PayPal sender country. Evidence priority: 3. |
| IP Address | IPv4 dotted or IPv6 colon | The consumer's IP address when they made the purchase. Evidence priority: 2. |
| Billing Country | ISO 3166 - 2 Alpha | The customer's billing country. Evidence priority: 1. |
| Other Commercially Relevant Information | ISO 3166 - 2 Alpha | Any other information about customer's country that was provided. Evidence priority: 4. |
| Product Type | default or e-book or /e-newspaper | The product type as defined by Taxamo. This is set to default if not provided. |
| Transaction Type* | Sale or Refund | Indicates whether the transaction was a sale or refund. For refunds, the Transaction ID field must use an ID for a transaction that is already confirmed within Taxamo, or reference a Transaction ID used for a sale from earlier in the same file. |
| Buyer's Name | Alphanumeric | The name of the buyer. This value can be wrapped in double quotation marks. For example "John R. Smith". |
| Street Name | Alphanumeric | The name of the street where the buyer lives. This value can be wrapped in double quotes. For example "17th Avenue". |
| Building Number | Alphanumeric | The number of the building where the buyer lives. This value can be wrapped in double quotes. For example "1 / 3". |
| Address Detail | Alphanumeric | Further details for the buyer's address. This value can be wrapped in double quotes. For example "Apartment no. 90". |
| City | Alphanumeric | The buyer's city. This value can be wrapped in double quotes. For example "Colorado Springs". |
| Postal Code | Alphanumeric | The buyer's postal code. This value can be wrapped in double quotes. For example "V3M 3B5". |
| Region Code | Alphanumeric | Two-letter code representing the region, where applicable. For example, the code for Quebec in Canada is QC. This information is required for tax calculation in Canada, if the region is enabled |
| Description | Alphanumeric | The description of the product. |
| Buyer's Tax Number | Alphanumeric | This is the buyer's tax number and is used for Business-to-Business validation. The service only checks the syntax of this number. Transactions that fail this check, are treated as Business-to-Consumer (B2C) and taxed accordingly. |
| Buyer's Email | Alphanumeric | The buyer's email address. Automatic email delivery is disabled for bulk uploads by default. If you want to enable automatic mail delivery, contact customer support. |
Tip
To download an example file, open the dashboard and go to Transactions > Upload. Click Download example file.
Uploading the File
To upload the file, complete the following steps:
- Log on to the dashboard and go to Transactions > Upload.
- The Block file processing if transactions with non-matching evidence are found. checkbox is selected by default. We recommend that you do not change this.
If you want to accept all transactions even where conflicting evidence exists, choose the Accept all transactions, even those with non-matching evidence. Evidence with the highest priority will be used. checkbox.
If you want to flag transactions with conflicting evidence without accepting them, choose the Flag transactions with non-matching evidence, but create transactions where the collected evidence matches. checkbox. - Click Choose File and select your CSV file.
- Click Submit for processing.
The report is available under the Recent uploads section.
Updated 2 months ago