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.
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:
See the Standard returns guide for implementation details.
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:
orderID at the time of the credit.See the Standalone credits guide for implementation details.
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.
Regardless of which path you use, returns and credits affect your tax calculations based on when they occur relative to your filing periods.
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.
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.
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.
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.
Start with the guide that matches your integration scenario: