Skip to content
  • There are no suggestions because the search field is empty.

Curing Tax Documentation Issues

Resolve specific issues on a previously submitted W-8 form without re-collecting the entire form.

 

Curing Tax Documentation

After a W-8 form is submitted, Taxbit runs validation checks to confirm the form meets IRS requirements. When a submission does not pass validation, the form remains valid in your records but is flagged with an issue. Curing is the focused remediation flow that lets an end user resolve specific issues in the SDK instead of starting the W-8 over from scratch.

As part of the curing flow, the end user uploads supporting evidence and, for some issue types, provides a short explanation. The reviewers then approve or reject the cure in the Taxbit Dashboard.


Why it Matters

  • This ensures that end users do not need to redo their W-8. They only fix the part of the submission that is incorrect, within the SDK.
  • Reviewers can manage issues in the SDK instead of over email. The Dashboard surfaces curable issues, the supporting documents the end user uploaded, and the available reviewer actions.
  • Targeted remediation can reduce abandonment. Asking an end user to upload one document for one issue typically creates less drop-off than asking them to redo an entire W-8.
  • Cures create a closer audit trail because they are tied to the specific issue they resolve, with a visible status and timestamp for your team and compliance reviewers.

 

Who Should Use this Feature?

This feature is designed for customers who collect W-8BEN, W-8BEN-E, or W-8IMY forms from non-US payees through Taxbit’s React SDK or hosted collection. It is especially useful for teams with tax operations or finance reviewers who currently manage W-8 issues over email and want payees to resolve issues without leaving the SDK.

Please note: If you only collect W-9 forms, this feature does not apply. W-9 submissions do not surface curable issues and are instead handled through B-notice flows or full resubmission.

 

Before You Begin

Dashboard updates for curing are not currently enabled by default. The SDK experience is generally available to customers using React SDK v4.1.0 or later, but the Dashboard reviewer tools must be enabled separately for your tenant.

If you want access to Dashboard reviewer tools such as filtering, bulk resolve, document upload, or requesting additional documentation, contact your Customer Success Manager or open a ticket with our CX Team by submitting your request here: Online Submission Form

Please note: If your team can see the curing flow in the supplier-facing UI but not in the Dashboard, it is because the SDK and Dashboard releases are enabled independently.

 

Issues that Can be Cured

Only specific W-8 issues are eligible for curing, and eligibility depends on the form type.

  • US Indicia
    • Supported for W-8BEN, W-8BEN-E, and W-8IMY.
  • Treaty Country Mismatch
    • Supported for W-8BEN and W-8BEN-E, but not W-8IMY.
  • Care-of Address
    • Supported for W-8BEN-E and W-8IMY, but not W-8BEN.
  • PO Box Address
    • Supported for W-8BEN-E and W-8IMY, but not W-8BEN.

Other issue types, such as incomplete data, inconsistent data, or change in circumstances, are not curable and require the end user to redo the relevant W-8 sections through the questionnaire.

 

How End Users Experience Curing

End users see curing when your SDK includes the <TaxbitCuringDocumentation /> component and the end user has at least one open curable issue on a previously submitted W-8.

The end-user flow is a single page with these sections:

  1. Issue summary, including a short explanation and a bulleted list of open issues.
  2. Upload documentary evidence using a PDF, JPEG, or PNG file up to 10 MB.
  3. Reasonable explanation, shown only for US Indicia issues. End users choose from six categories: Student, Teacher or Trainee, Diplomat, Spouse or Child, Does Not Meet Substantial Presence Test, or Closer Connection Exception.
  4. Additional fields for the last two explanation categories, such as day counts or country and reason.
  5. Review and submit.

After submission, the issue moves from Open to In Review and reviewers can take action in the Dashboard.

 

How Reviewers Experience Curing

Tax Documentation Table

On the Tax Documentation table, reviewers see a new Curing Doc Status column. Available values are Submitted, Additional Documentation Needed, and None. Reviewers can also filter by Curing Doc Status through Advanced Filters, and exports include the new column when access is enabled.

Issue Details Modal

Reviewers can use a bulk Resolve issues action from the issue table to resolve grouped curable issues in a single modal. They can also request additional documentation. When an issue is In Review and the end user has at least one document on file, the reviewer can move the issue back to Open so the end user can submit again through the SDK.

Submitted Documents Card

On Account Details > Submitted Documents, reviewers can view curing documents uploaded through the SDK. Tax managers can also manually attach a curing document on behalf of an end user using the Upload Documents button. Supported file types are PDF, JPEG, and PNG up to 10 MB.

 

How the End User Can Resolve an Issue

Step 1: The end user signs in to your product.

Step 2: Your product displays a notice that their tax documentation needs attention. Taxbit recommends gating this link on useTaxbit().needsCuringDocumentation.

Step 3: The end user opens your curing page, which renders <TaxbitCuringDocumentation />.

Step 4: The end user reviews the issue summary, uploads a supporting document, and, when applicable, selects a reasonable explanation category.

Step 5: The end user submits the cure.

Step 6: The issue moves to In Review. The end user sees a confirmation and cannot submit again for the same issue until a reviewer takes action.


How the Reviewer Can Approve

Step 1: From the Dashboard, the reviewer navigates to the Tax Documentation page.

Step 2: The reviewer filters the table by Curing Doc Status > Submitted, or by a specific issue type using existing issue filters.



Step 3: The reviewer opens the row to view the Issue Details modal to review the submitted documentation and either resolves the issue, which moves it from In Review to Resolved, or requests additional documentation, which moves it from In Review back to Open.



Step 4: After a reviewer resolves the issue, the end user is notified that their documentation is now valid. If additional documentation is requested, the end user can submit again through the SDK.

Step 5: After resolution, the Dashboard refreshes to reflect the updated status.

For more information on the Tax Documentation page, please refer to the following guide: Tax Documentation Page

 

Edge Cases and Known Limitations

  • The Dashboard side of curing is gated. Without Dashboard access enabled for your tenant, reviewers will not see the Curing Doc Status column on the Tax Documentation page, the bulk resolve action, the request-additional-documentation flow, or the upload modal, even if end users are successfully submitting cures through the SDK.
  • Cures submitted through the SDK are still captured even when dashboard tooling is not yet enabled for your tenant.
  • Address-shape issues on individual W-8BEN forms are not curable. CARE_OF_PERMANENT_ADDRESS and PO_BOX_PERMANENT_ADDRESS only resolve through curing for W-8BEN-E and W-8IMY. Individual W-8BEN end users must redo that section through the questionnaire.
  • “In Review” is a one-way gate for the end user. Once they submit, they cannot submit again on the same issue until the reviewer resolves the issue or requests additional documentation. While the issue is “In Review”, the SDK widget renders nothing for the end user.
  • The SDK onSuccess callback confirms upload, not approval. When it fires, Taxbit has received the document successfully, but the issue is still In Review. End-user messaging should reflect that the document was received and will be reviewed, rather than approved.
  • Curing documents do not have a downloadable PDF for the end user. useTaxbit().documentUrl still points to the underlying W-8 PDF, not the curing submission. The curing document is visible to reviewers in the dashboard but is not surfaced for end-user download.