Welcome to instaClaim
instaClaim helps accounting and claims teams turn source evidence into organized claim outputs. The product centers on Xero-first expense categorization, project periods, report configuration, invoice evidence packs, expense summary spreadsheets, and bank-statement redaction workflows.
What instaClaim Helps You Do
With instaClaim, you can:
- Set up organizations, users, roles, and integrations
- Map accounting records into claim-ready expense categories
- Configure report periods, filters, and output options
- Queue and review generated claim reports
- Track bank statement evidence and redaction status
- Keep claim evidence grouped by project and period
The documentation follows the product workflow: configure the workspace, connect accounting evidence, prepare claim settings, then generate and review outputs.
How to Use This Documentation
Start with the setup and claim workflow pages:
- Creating your organization covers the first workspace setup steps.
- Expense categories explains category mapping for claim reports.
- Report configurations explains report periods, filters, and output settings.
- Reports explains generated report runs and evidence outputs.
- Bank statements explains statement metadata, upload limits, and redaction status.
- Settings and integrations covers connected services and integration setup.
Best Way to Get Started
If you are new to instaClaim, follow this order:
- Set up your organization.
- Invite team members and confirm the access levels they need for claim preparation and review.
- Configure integrations for accounting and evidence workflows.
- Create expense categories and report configurations.
- Upload or register bank statements where redaction is required.
- Generate and review claim reports.
For Developers
Building integrations? Use the Developer Platform for API authentication, OpenAPI reference, SDK setup, MCP tools, signed webhooks, errors, pagination, rate limits, idempotency, and versioning policy. The developer surface is being rebuilt around claim workflows and must not depend on legacy product-specific endpoints after cutover.