Returns and Credit Overview

When a customer returns items or receives a credit adjustment, TaxCloud needs to know so that your tax liability is accurately reduced and your filings reflect the change. TaxCloud supports two mechanisms for this, each designed for different scenarios.

Two paths for adjusting tax liability

Standard returns

Use the Refund API when you need to reverse part or all of an existing order. This is the most common approach and the recommended default for most integrations.

With standard returns, you reference the original order by its orderID and specify which items are being returned. TaxCloud automatically looks up the original tax calculation including rates, TICs, and exemption status and reverses the appropriate amounts. You can issue multiple returns against the same order until the cumulative total equals the original order amount.

Use this when:

A customer returns one or more items from a previous order.
You need to issue a partial return (e.g., one item out of five).
You need to issue returns in multiple batches over time against the same order.
You want full audit traceability between the return and the original transaction.

See the Standard returns guide for implementation details.

Standalone credits

Use the Create Order endpoint with kind set to "credit" when you need to issue a tax credit that is not tied to a specific existing order. Rather than returning against an order, you create a new order that applies a negative tax liability.

This approach is designed for scenarios common in accounting platforms and ERP systems where credit memos or adjustments exist independently of specific invoices.

Use this when:

Your system issues standalone credit memos (e.g., QuickBooks Online credit memos).
The original transaction was not processed through TaxCloud and the tax has not been processed.
Your integration workflow doesn’t have access to the original orderID at the time of the credit.
You’re migrating from another tax provider and need to record credits for transactions that originated elsewhere.

See the Standalone credits guide for implementation details.

Choosing the right approach

Scenario	Recommended Path	Why
Customer returns items from an order	Standard Return	Maintains direct link to original transaction; simplifies audits
Partial return, with more returns expected later	Standard Return	Supports multiple returns per order with cumulative tracking
Credit memo from accounting platform (no original order)	Standalone Credit	No order to return against; credit exists independently
Migrating historical credits from another tax provider	Standalone Credit	Original transactions aren’t in TaxCloud
General adjustment where original order ID is available	Standard Return	Always prefer the standard path when you have the order reference

When in doubt, use standard returns. They provide the strongest audit trail and are the approach preferred by tax authorities during compliance reviews. Reserve standalone credits for cases where a standard return genuinely isn’t possible.

Tax implications

Regardless of which path you use, returns and credits affect your tax calculations based on when they occur relative to your filing periods.

Returns before filing

If the return or credit is processed within the same filing period as the original transaction, TaxCloud treats it as though the original sale amount was lower. The tax adjustment is reflected automatically in your next filing, no additional action is required on your part.

Returns after filing

When a return or credit falls into a different filing period than the original transaction, TaxCloud applies a credit to offset the previously remitted tax. This credit reduces your tax obligation in the current filing period.

Backdated returns

Returns should always reflect the actual date the return or credit occurred. If a return is backdated to a previously filed period, it may require an amended tax return. TaxCloud does not currently generate automatic alerts for these adjustments, you are responsible for tracking them and contacting TaxCloud support if an amendment is needed.

Important: Creating a new order to replace a returned one may affect tax nexus calculations in some states, as certain jurisdictions determine nexus based on transaction count.

Compliance considerations

Tax authorities, particularly those participating in the Streamlined Sales Tax (SST) program, generally prefer that credits be traceable to the original transaction. This is one of the key reasons standard returns are the recommended default.
For standalone credits, consider maintaining your own mapping between credit orders and the original invoices they relate to, even if TaxCloud doesn’t enforce this linkage.
In rare cases, a filing period may go negative (more credits than debits). When this happens, some states may request documentation about what the credits apply to. Having clear internal records, whether through standard returns or your own credit-to-invoice mapping, helps resolve these inquiries quickly.

Core endpoints

Functionality	Description
Refund Order	Issue a full or partial return against an existing order. Supports multiple returns per order.
Create Order	Create a standalone credit by setting `kind` to `"credit"`.
Get Order	Retrieve order details, including any returns issued against it.

What to do next

Start with the guide that matches your integration scenario:

Standard returns — Step-by-step guide to issuing returns against existing orders, including multiple returns per order.
Standalone credits — Guide to creating credit adjustments not tied to a specific order.