Guides
and documentation

ClaimKit helps Australian technology companies prepare R&D Tax Incentive claims using the technical and financial records they already keep. Instead of running interviews and writing a claim narrative from scratch each year, ClaimKit reads your engineering and accounting tools, drafts the answers required by the AusIndustry application form, and lets you review and refine them before you submit.

A claim in ClaimKit moves through five phases — Discovery, Sources, Tracking, Generation, and Review — that mirror the stages of a manually-prepared R&D claim.

If you have not yet been invited to a workspace, ask your finance lead or your ClaimKit account contact to invite you. Workspace owners can add new members from Settings > Workspace.

ClaimKit reads from the tools your team already uses so it can identify R&D activities and costs without you re-entering them. Connections live under your claim's Sources page and are authorised through each provider's standard OAuth flow — ClaimKit never asks for raw passwords.

Engineering tools we read from include GitHub, GitLab, Linear, Jira, and Notion. We use these to find the projects, issues, and pull requests that describe what your team built during the financial year. For evidence-gathering we also support Google Drive — useful for pulling in design docs, RFCs, and meeting notes that justify the technical uncertainty in your claim.

Financial tools we read from include Xero and QuickBooks Online. These provide the salary, contractor, and expense data that drives the apportionment and final R&D expenditure figures.

ClaimKit stores the minimum necessary information from connected tools to support your claim — titles, summaries, references back to the source record, and any extracted content needed to draft answers. We do not maintain a wholesale copy of your tools' data.

You can connect or disconnect any source at any time from the Sources page. Disconnecting revokes ClaimKit's access immediately at the provider; we keep the data we previously ingested for the current claim, but stop pulling new updates.

A workspace represents a single company preparing one or more R&D claims. Workspace owners control billing, integrations, and member access from Settings > Workspace. Collaborators can be invited by email; they receive a sign-up link and pick their own password.

Roles are simple by design: workspace owners can do everything, collaborators can read and edit claim content but cannot change billing or remove members.

If a team member leaves your company, remove them from Settings > Workspace > Members. Their authored content stays in the workspace; only their access is revoked.

Customer data is encrypted at rest and in transit, with access scoped to the workspace it belongs to. All customer-facing traffic is served over HTTPS.

ClaimKit does not use your data to train AI models. The large language models we rely on to generate answers are accessed through commercial APIs whose terms exclude customer inputs and outputs from training data.

We retain claim data for as long as your workspace is active so you can refer back to prior years. On account closure or written request, we delete your data in line with our data retention policy. You can request an export of your data at any time by getting in touch.

Security questions, vulnerability reports, and data-processing agreement requests can be sent to the address below. ClaimKit is currently in the middle of a SOC 2 audit and will publish the resulting report once available.

Our full set of security policies, certifications, and audit reports lives in the ClaimKit Trust Center.