Share
Explore

icon picker
Assessment Requirements Manual

Thank you for choosing us as your partner in sales tax compliance. This guide is designed to streamline your participation in our Auto Assessment process, ensuring you provide the necessary data accurately and efficiently for optimal tax evaluation.
By following the instructions outlined here, you will help us generate a comprehensive tax profile that covers nexus obligations and historical tax exposures—laying the foundation for accurate compliance and strategic decision-making.

Assessment Deliverables

Upon successful data submission and processing, you will receive:
Economic Nexus Mapping Identification of states where your business has tax obligations based on transaction volume, revenue thresholds, and product types.
Exposure Calculation Retrospective estimation of sales tax obligations per transaction, as if Complyt had been calculating the tax from the outset—factoring in product type, location, and customer exemptions.

Data Preparation: Key Requirements

To enable precise tax analysis, we need the following inputs before beginning the automated assessment:

1. Product Classification

Different products can have significantly different tax treatments. Our compliance team will collaborate with you to categorize each item and assign the correct tax code based on its taxability per jurisdiction.
📌 Why It Matters: SaaS, tangible goods, and digital products often have different rules.
✅ We will guide you through this classification process.

2. Physical Nexus Details

Please provide information about any physical presence your business has across U.S. states—including offices, warehouses, employees, or inventory. Required details: Start date of the physical Nexus and relevant state.
📌 This presence may establish an obligation to collect and remit sales tax.

3. Exempt Customers List

Share a list of tax-exempt customers, such as non-profits, government agencies, or resellers.
✅ Include exemption certificates or status indicators if available.
📌 Exempt status will override standard tax calculations where applicable.

Data Format Guidelines

Each row in the dataset must represent a single line item from a transaction (invoice, sales order, etc.).
This structure is essential because:
Different line items may have different tax rates based on product type and jurisdiction.
Line-level detail allows our engine to compute itemized tax exposure with high fidelity.
Example: An invoice with three items must be represented in three separate rows, each containing all relevant fields (e.g., product name, transaction date, customer, state, amount, etc.).

Important Reminders

The quality of the results depends on completeness and accuracy of your data.
This is a one-time data pull for assessment purposes only—no financial liability is created during this process.
The assessment is retrospective—calculating what your tax obligations would have been using our engine.
If you have questions or require assistance while collecting the data, please don’t hesitate to reach out to your dedicated onboarding or compliance contact at Complyt.

Template File

Automated Assessment Template.csv
287 B
Fields
Field Name
Importance
Description
Examples 2
Customer Name
Customer's name. If not applicable, the ID can be used as the name as well.
Complyt’s Home Made Cookies 15714 CS323241
Item Amount
Total price for the item, calculated as Item Unit Price multiplied by Item Quantity.
20
Subsidiary
The ID or the name of the Subsidiary that is associated with the transactions
Complyt INC
Customer Exempt
Yes
Currency
USD AUD
Customer ID
The customer ID in the accounting system. If there isn’t an ID (because the customers are not managed in a system), a unique value such as an email address is also applicable.
15714 CS323241 Complyt@Complyt.io
Transaction ID
Unique identifier for each transaction.
388828
Transaction Type
The type of the transaction.
INVOICE
REFUND
Transaction Country
The shipping country of the transaction. The system will ignore non-USA countries, including blank values.
USA United States
Transaction State
The shipping State of the transaction
NY New York
Transaction Created Date
The date of which the transactions was issued
Allowed format - yyyy-MM-dd
2023-05-17
Item Name
Item’s unique name or ID
Subscription module per year
Item Unit Price
Price per unit of the item.
5
Item Quantity
Number of units of the item included in the transaction.
4
Customer Type
Category of the customer.
This can influence nexus threshold calculations. If not applicable, the default value of 'RETAIL' will be assigned.
RETAIL
MARKETPLACE
RESELLER
Transaction City
City to which the transaction's items are shipped.
Orlando Baltimore
Transaction Address
Street address to which the transaction's items are shipped.
20 E Market St 101 S West St
Transaction ZIP
The shipping zip of the transaction. If missing, a default ZIP will be used
19801 89169
Tax Code
The tax identifier for the line item in Complyt's system. If this field exists, a product classification file is not required.
C3S1 - SaaS PC20 - Professional Services
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.