Native collection overview
Taxbit's tax documentation collection, built for native iOS and Android apps.
In developmentNative Tax Documentation Collection is in development. If you're interested in using it, reach out to your Taxbit contact.
Native Tax Documentation Collection brings Taxbit's tax form collection into native mobile apps. You add Taxbit's questionnaire screen to your iOS or Android app, match it to your brand, and Taxbit handles everything about the tax form itself: which questions to ask, how they're worded, whether the answers are valid, and storing the finished form.
- Native. It's built with each platform's own UI tools, not a web view, so it looks and feels like the rest of your app.
- Always up to date. The tax rules run on Taxbit's servers. When rules, questions or wording change, your users get the update right away, with no app release on your side.
- Ready-made, and yours to style. It comes with complete screens out of the box. You set the colors, shapes and page layout, and you can add your own screens into the flow.
Working so far: the W-9 in the iOS prototype. Self-certification works in the web prototype. W-8 (BEN, BEN-E, IMY) and DPS are in development.
Who does what
| You | Taxbit |
|---|---|
| Add the questionnaire screen to your app | Decides which questions to ask, based on the answers so far |
| Match it to your brand | Writes every label and error message, translated into 40+ languages |
| Decide what happens when it's done | Checks TINs, addresses and the other answers |
| Confirms the form is complete, then stores it |
How it works
sequenceDiagram
participant App as Your app
participant Q as Taxbit questionnaire
participant T as Taxbit
App->>Q: Show the questionnaire
loop Whenever an answer changes the form
Q->>T: The answers so far
T-->>Q: The questions to show now, their labels, any problems
end
Q->>T: Submit, once the form is complete
T-->>App: Receipt (document_id)
- Your app shows the questionnaire screen, styled to match your app.
- When an answer changes the form, for example picking "LLC", the questionnaire sends the answers to Taxbit.
- Taxbit sends back the updated form: the questions to show now, their labels, and any problems.
- When Taxbit says the form is complete, the questionnaire submits it and your app gets a receipt.
Your team doesn't write any of this. The questionnaire handles it.
Native collection or the React SDK?
Both give your users the same guided experience, where each person only sees the questions that apply to them. The difference is where your users are and how rule updates reach them.
| Taxbit React SDK | Native collection | |
|---|---|---|
| Availability | Available now | In development |
| Built for | Web apps (React) | Native iOS and Android apps |
| What you get | A ready-made form you style with CSS | Ready-made native screens you style with a theme |
| How rule updates reach your users | You upgrade the SDK and release your app | Automatically, with no release on your side |
| Needs a connection | Only to submit | Whenever an answer changes the form |
| Platforms | React | iOS (prototype). Android is planned. |
If your users are on the web, use the Taxbit React SDK. Native collection is for teams whose users complete tax forms inside a native mobile app.
Already collecting tax information yourself?Both guide your users through the questions. If you gather the information in your own forms or systems and only need to check it, use the Validation API instead.
Next steps
- Walkthrough: what your app does, and what happens under the hood
- Developer guide: styling, layouts, pre-filling data and more
Updated about 1 hour ago

