Go live

Going live means pointing the code you tested in your sandbox at your production organization, loading your production data, and getting your forms reviewed and approved for filing. This page covers the steps in order, what to watch once you're live, and what to do when data changes after a form is filed.

Before you begin

The test cycle has passed in your sandbox organization. See Test in your sandbox.
Your production credentials. Your production organization has its own client_id, client_secret, and Organization ID on its Developer Settings page, set up by Taxbit the same way as your sandbox. Request tokens with them as in Authenticate.

1. Match production to your sandbox

Set up the production organization the way your sandbox is set up, so the code you tested moves over unchanged.

The filer. Create your production filer, in the Dashboard (Settings > Filer Setup) or through the API, and mark it as the default; see Set up your filer. Its legal name, TIN or EIN, and address are what appear on your forms and filings, so confirm them before your first filing.
Assets. Configure the assets your platform supports with the Assets API. If CARF or DAC8 applies, tag stablecoins when you create them; see Self-certification and transaction reporting.
Cost-basis methods (disposition_method), if you use cost basis. See Choose a cost-basis method.
Your IDs. Use the same ID scheme for account owners, accounts, and transactions that your app used against the sandbox.

2. Load your production data

Account owners and accounts. See Create account owners and accounts.
Tax documentation, if you collect it. Collect it with the React SDK in production, using account owner tokens your backend requests, or send it through the API: Send recipient tax data, Collect seller data, or Self-certification and transaction reporting.
Transactions or form data, sent as form items, on the data path you chose; see Choose your data path, Send payment transactions, and Send transactions and read gains. For historical loads, the Ingest page in the Taxbit Dashboard takes CSV and JSONL files and offers each CSV template; Taxbit Support can walk you through it.

Taxbit gives you the timelines for getting each tax year's data in, so forms can be generated and approved in time.

3. Point your webhooks at production

If you use webhooks, give your implementation manager your production endpoint, as in the last step of Testing and going live on the Webhooks page.

4. Agree who delivers and who files

Delivering recipient copies is yours. Show each recipient's copy in your app through GET /v1/accounts/{id}/tax-documents, as in Retrieve US tax forms or, for DAC7 and MRDP, Retrieve DAC7 and MRDP recipient copies, or download copies from the Dashboard. If some recipients want paper copies, prefers_physical_mail marks their accounts; it doesn't send anything by itself. You request mailing from the Forms page, and Taxbit mails those forms through its print-and-mail provider. Taxbit doesn't email recipient copies; delivery in your app or by mail is yours to arrange. Which of these you use is agreed with your implementation manager.

Filing is Taxbit's. You review your generated forms on the Forms page and approve them for filing on the Filing page, by the approval deadline Taxbit gives you for each form type. Taxbit then files them with the tax authority. You don't file directly.

5. Reconcile and approve

Review draft forms. Generate a QA Package from your production organization's Eligibility page, and check the draft forms against your records.
Reconcile totals. Check counts and totals against your own books using the reports on the Reports page.
Approve filing on the Filing page.

What to monitor after you go live

In the Dashboard:

The Eligibility page: which accounts are eligible for each form, and which have changed since their forms were last generated.
The Forms page: your generated forms and their status.
The Tax Documentation page: every account with its tax documentation status, with filters to find the ones that need attention.
The Reports page: the reports you reconcile from.

In your systems:

Forms. The FORM_STATUS_UPDATE webhook tells you when a form is generated, filed, or deleted, and is_filed on the tax documents endpoint, GET /v1/accounts/{id}/tax-documents, says whether a form has been filed; see Webhooks and Retrieve US tax forms.
Tax documentation. ACCOUNT_OWNER_TAX_DOCUMENTATION_STATUS and the TIN matching events flag documentation that needs attention; see Webhooks and Send recipient tax data.
Cost basis. INVENTORY_UPDATE and calculation_status show when inventory and gains have caught up; see Know when inventory and gains are current.
Errors. Watch for 429s and 5xx responses, and log x-request-id with each failure; see Errors and rate limits.

If data changes after filing

Correct the data the same way you sent it: resend the transaction, form data, or account data. Resending doesn't file anything by itself. The change shows on the Eligibility page, where you generate the new form; you review it on the Forms page, approve it for filing on the Filing page, and Taxbit files the correction or void. It works the same way for every form type. The new form is a new revision; see Find corrections and earlier revisions.

For anything else, contact Taxbit Support.

Where to go next

Webhooks: the events behind the monitoring above.
Errors and rate limits: what to retry and what to log.
FAQ: the questions integrators ask most often.

Questions? Contact Taxbit Support or [email protected].