Which Format Do You Support When Importing Transactions?

Which Format Do You Support When Importing Transactions?


We do not have a pre-defined, preferred format.

We provide different ways to ingest sales transactions - from CSV files, from CRM and accounting systems (ex: QuickBooks, HubSpot, SalesForce, Stripe, Chargebee, Xero, Dynamics, etc.), from FTP, from databases (ex: PostgreSQL, Snowflake, etc.), from APIs (ex: upload API, Zapier), from Web Endpoints. 

You can import multiple batches of transactions using different formats. So, for example, you could import transactions from both "import1.csv" and "import2.csv", each having totally different columns. All transactions will be available from the same view.

As you import transactions, we will ask you to map fields to different categories. As you map fields, we will tell you what type of sales incentive plan you can design. In the great majority of cases, you will be able to build a large variety sales incentive plans from any format.

If there are some limitations, we will tell you. For example, if you import transactions with only a [transaction date], a [transaction revenue], and a [sold by] field, you will not be able to design plans based on profit. Including a product name would allow this - although you would need to provide margin % entries in the product catalog (one for each product name).

Also note that we've paid great care to providing maximum flexibility. For example, whether you have currencies specified as separate columns / fields, or specified within data fields (ex: "USD 1.23"), we will handle both. Similarly, whether your taxes are specified as percentages or amounts, we will handle both.