Skip to main content

Transaction Data: CSV Uploads & How to Export Orders

When to use CSV uploads, the required column format, how to export from common systems, and marketplace-specific guidance.

If you're not using a direct integration with Zamp, you can provide transaction data via CSV. This article covers when to use CSV uploads, the required format, how to export from common systems, and answers to common questions.

When to use CSV uploads

Use CSV uploads when:

  • Your e-commerce platform doesn't have a direct Zamp integration

  • You have transactions from marketplaces (Amazon, Target, Walmart, etc.)

  • You need to provide historical data

  • You have offline or manual sales

Zamp simplified CSV template (column reference)

Use the table below as a reference when formatting your CSV. We can also provide an example file on request.

  • This CSV template can be used for single line item exports or multi-line item exports consolidated into a single row.

Refunds: For refund transactions, the following fields should have negative amounts: transactionShippingHandling, transactionSubtotal, transactionDiscount, transactionTax, and transactionTotal.

Column Name

Required?

Used for

Notes

transactionId

Yes

The ID for the transaction.

May also be referred to as an invoice ID, order ID, or similar.

transactionParentId

No

For refund transactions only. The ID for the original order transaction.

Helpful when available.

marketplace

No

The marketplace where the sale took place.

Supported values: AMAZON, META, TIKTOK, WALMART, TARGET_PLUS, ETSY, EBAY, MIRAKL, MACYS, ALIBABA and other supported values listed here.

If not a marketplace sale, use FALSE.

See why this field matters in this explainer on marketplace facilitator laws.

wholesale

No

true, false, or blank to note if the order was sold to a wholesaler/reseller.

Defaults to false if blank.

transactionDiscount

No

The total discount for the order or refund.

Defaults to 0. Must be positive; cannot be a percentage.

transactionSubtotal

Yes

The combined total of the order or refund after the discount.

Should not include shipping, handling, or tax.

transactionShippingHandling

No

The combined shipping and handling cost.

Defaults to 0.

transactionTax

Yes

The total tax collected on an order, or refunded for a refund.

Defaults to 0.

transactionTotal

Yes

The total amount charged or refunded.

Should equal subtotal + shipping/handling + tax.

transactionDate

Yes

The date the order or refund occurred.

Example: 10/21/2024.

shipToAddress1

No

First line of the shipping address.

Recommended for accuracy. See how ship-to address affects determining your sales tax jurisdiction.

shipToAddress2

No

Second line of the shipping address.

Examples: Suite 23, Apt 16, Building 5.

shipToCity

No

The shipping city.

Required if shipToZip is not provided. Example: Cincinnati.

shipToState

Yes

The shipping state.

Required if shipToZip is not provided. Supports US states, PR, and Canadian provinces.

shipToZip

Yes

The shipping zip / postal code.

US: 12345 or 12345-6789. Canada: e.g., H1A 0A0.

shipToCountry

Yes

The shipping country.

Supports US and CA.

currency

Yes

The transaction's currency.

Defaults to USD if blank.

productTaxCode

Maybe (see Notes)

A specific Zamp Tax Code for the transaction.

If blank, the product is assumed fully taxable. If zero, a product tax code or reason is required.

Ship-to address requirements

For US transactions, the minimum required is the zip code, OR the city and state. For non-US transactions, the minimum required is the city and country (use a 2 or 3-character ISO country code — look codes up at iso.org if needed).

For physical products, use the shipping address. For digital, service, or non-physical products, use the billing address.

How to submit CSV files

  1. Email to support. Attach your CSV file to a message to [email protected].

  2. Include the period. Specify which month/period the data covers.

  3. Note the source. Tell us where the data came from (e.g., "Target January 2026").

Automated data checks in Zamp

When you upload your CSV in Zamp, Zamp runs automatic checks to make sure the data will result in accurate tax calculations for your filings.

Once a CSV is uploaded, click Analyze CSV to start the check. Zamp runs through four validation categories:

  1. Shipping AddressWhy: To account for state-by-state differences and bucket your transactions into the correct state. A minimum of a city or state is required.

    1. What the error means and how to fix it: A row has no usable ship-to address, or one we can't resolve to a state. Fix: fill in the destination address — state plus postal code is enough.

  2. Transaction AmountsWhy: To ensure all amounts reconcile properly when completing returns.

    1. What the error means and how to fix it: The row's total doesn't equal its line items plus shipping plus tax. Zamp shows the number it expected — for example, "Subtotal + shipping + tax = $412.50 (not $407.00)". Fix: correct the total, or the line item that's off.

  3. Exemption ReasonsWhy: Exemptions should be tagged appropriately to avoid unexplained zero-tax transactions.

    1. What the error means and how to fix it: Tax is zero on a sale into a state where you're registered, and nothing in the row explains why. Fix: give the row a product tax category, mark it resale or exempt, or mark it as a marketplace sale. Any one of these clears it.

  4. Date FormatsWhy: Confirms all transactions are flowing into the correct filing periods.

    1. What the error means and how to fix it: The transaction date is absent or falls outside the period being filed. Fix: add the order date, or confirm the period.

Other errors you may hit

Some uploads currently fail with a generic error rather than a named category. Here's what those actually mean and how to resolve them:

  • Non-USD currency on a US sale. The row ships to a US address but carries a non-USD currency. Fix: convert the amounts to USD, or split the file by currency.

  • Tax rate looks too high. The effective rate on the row is over 50%, which is usually a decimal or column problem rather than a real rate. Fix: check that row's tax and total.

  • Tax sign doesn't match the transaction. Tax is positive on a credit, or negative on a sale — almost always from a refunds or credits export. Fix: make the tax sign match the transaction.

  • Too many line items on one order. A single transaction has over 100 line items. You don't need to fix this one — contact us and we'll handle it.

  • Something else in the row didn't validate. This is a catch-all. If you hit it, click Get help from our team and send us the file rather than guessing, and we'll identify the specific cause.

If the check returns transactions with errors, click into each category to review them. Once the issues are resolved, you can re-attempt the upload.

If you're unsure how to resolve an error, click Get help from our team and provide as much detail as you can — our team will assist.

Common CSV upload questions

"My CSV has different column names"

That's okay. Just let us know what each column represents and we'll map it correctly.

"I have multiple files"

You can send multiple files. Label each clearly with the source and period.

"Some transactions are missing tax"

If tax wasn't collected on certain transactions, include them anyway. We need the full picture to file accurate returns.

How to export orders from your system(s)

Zamp doesn't integrate with every e-commerce, invoicing, or bookkeeping platform, but we can process transactions from any system when they're imported via CSV.

Transactions versus line items

Most systems distinguish between transactions and line items. The relationship is one-to-many: a single transaction may have one or many line items. If your transactions can include multiple line items, you must list them individually (each on its own row). Otherwise we can't process the import.

Required columns for multi-line item exports

  • Transaction date. The date of sale.

  • Transaction/Order/Invoice ID. Needed to connect line items to the same order.

  • Ship-to state and Ship-to zip code.

  • Line item quantity and price. Quantity is the number of units; price is the unit price.

  • Line item and/or transaction discounts. Separate columns for transaction vs. line item.

  • Line item and/or transaction shipping & handling fees.

  • Line item ID

  • Transaction OR line item taxes.

  • Transaction total. Including price, discounts, shipping, and tax.

  • Marketplace. For marketplace-facilitated transactions, one of the supported marketplaces listed here (e.g., AMAZON, ETSY, WALMART, etc).

  • Purpose. For wholesale or resale transactions, value of RESALE.

  • Entity. For supported entity exemptions such as NON_PROFIT and others listed here.

  • Product Tax Code. If your product is tax-exempt or taxed at a lower rate, one of the supported tax codes listed here. Let us know if we can help at [email protected].

Our line item template can be found here.

Marketplace-specific guidance

Amazon

  • Amazon remits tax directly in most states.

  • We still need transaction data for nexus tracking.

  • Download reports from Seller Central.

Target

  • Provide the Sales Tax by State report.

  • Include all transaction files for the period.

Walmart

  • Download the Tax Remittance Report.

  • Include transaction details.

Related resources

Need help?

Questions about data uploads or exports? Reach out to your onboarding specialist or [email protected].

Did this answer your question?