Skip to content
Gallery
Custom Integrations
Share
Explore

icon picker
CSV Export Integration

This manual will guide you through Complyt's integration using CSV export method.
Complyt offers our clients a convenient method to utilize our engine without the need for a direct integration. With this partial integration approach, clients create scheduled reports in CSV format and send them to Complyt using a variety of methods such as SFTP, Email, SharePoint, and more.
Here's how it works:
(Client) Generate Scheduled Reports: Clients have the flexibility to generate scheduled reports according to their preferred frequency. These reports contain relevant data in a CSV format. * each line in the file represents a line item in the CSV.
(Client) Choose a Delivery Method: Clients can choose from multiple delivery options including SFTP, Email, SharePoint, and other convenient channels. This ensures that the reports are securely transmitted to Complyt's for further processing.
(Complyt) Data Parsing: Upon receiving the CSV report, we will automatically parse the information and extract the necessary data required for our calculations.
(Complyt) Complyt's Engine: Once the data is successfully parsed, Complyt's engine will execute the necessary calculations and analysis based on the provided data. This process is entirely handled by Complyt.
Done! All the information and results are reflected in Complyt's dashboard. Clients can access the dashboard and use the data to update the results in their ERP.

Important to Know

Each row in the file represents line item - Taxability can vary depending on the items sold. Thus, an invoice with multiple line items may have different tax rates applicable to each. To accurately process and calculate the tax for each item, it's necessary for each to be in a separate row.
Exempt Customers & Customer Type Update - Both exempt customers and customer types can affect tax calculation. For example - Some states include the taxable amount in the nexus threshold, and some states exclude the marketplace. It’s important to update regularly the customer types and update exemptions certificates.

CSV Template to Download

CSV Import Template.csv
461 B
Fields List
Field Name
Importance
Description
Format / Allowed values
Example
1
Customer ID
Mandatory
Unique identifier for each customer involved in a transaction.
String
15714
2
Customer Name
Mandatory
Full name of the customer
String
Complyt’s Home Made Cookies
3
Customer Country
Recommended
Country of the customer.
String
United States / USA
4
Customer State
Recommended
State of residence of the customer.
String
TX / Texas
5
Customer City
Recommended
City of residence of the customer.
String
Austin
6
Customer Street
Recommended
Street address of the customer.
String
501 S Congress Ave
7
Customer ZIP
Recommended
Customer’s Postal or ZIP code of the customer's address.
String
112224
8
Customer Created Date
Highly Recommended
Date when the customer's account was first created.
String (ISO8601)
yyyy-MM-dd
9
Customer Updated Date
Highly Recommended
Most recent date when the customer's information was updated.
String (ISO8601)
yyyy-MM-dd
10
Customer Type
Category of the customer.
This can influence nexus threshold calculations. If not applicable, the default value of 'RETAIL' will be assigned.
String (Options: RETAIL / MARKETPLACE / RESELLER)
RETAIL
11
Transaction ID
Mandatory
Unique identifier for each transaction.
String
455111
12
Transaction Name
Highly Recommended
Descriptive or reference name of the transaction.
String
INVUS44551 / SO55441
13
Transaction Type
Mandatory
The type of the transaction.
SALES ORDER / INVOICE / REFUND
INVOICE
14
Transaction Country
Mandatory
Country to which the transaction's items are shipped.
String
United States / USA
15
Transaction State
Mandatory
State to which the transaction's items are shipped.
String
TX / Texas
16
Transaction City
Mandatory
City to which the transaction's items are shipped.
String
Austin
17
Transaction Address
Mandatory
Street address to which the transaction's items are shipped.
String
501 S Congress Ave
18
Transaction ZIP
Mandatory
The shipping zip of the transactionZIP code of the shipping address for the transaction.
String
112224
19
Transaction Created Date
Mandatory
Date when the transaction was initiated.
String (ISO8601)
yyyy-MM-dd
20
Transaction Updated Date
Highly Recommended
Most recent date when the transaction details were updated.
String (ISO8601)
yyyy-MM-dd
21
Transaction Created From
Highly Recommended
Origin ID of the transaction, applicable if derived from another document like a sales order.
String
INVUS44551
22
Item ID
Mandatory
Unique identifier for each item in a transaction.
String
FC-2221
23
Item Name
Recommended
Official name of the item.
String
Fresh cookies
24
Item Description
Recommended
Detailed description of the item.
String
Complyt’s home made cookies
25
Item Unit Price
Mandatory
Price per unit of the item.
Float
50
26
Item Quantity
Mandatory
Number of units of the item included in the transaction.
Integer
4
27
Item Amount
Mandatory
Total price for the item, calculated as Item Unit Price multiplied by Item Quantity.
Float
200
28
Subsidiary
Highly Recommended
The ID or the name of the Subsidiary that is associated with the transactions
There are no rows in this table



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.