Notice This app is in Beta Testing We are still testing Taxesfiler, so features may change.

Developer platform

Tax compliance, as an API your product calls.

The same deterministic engine, the same versioned rules and the same audit trail that the application uses — reachable from your own software, under your own interface. Every response carries the rule version that produced it, so a figure you render to your users can be explained later.

Sandbox

Synthetic taxpayers, realistic enough to break on.

Prompt 3 is right that engineering teams must be able to test without touching a real taxpayer's file. The sandbox is a separate tenant with generated people, companies, documents and filing scenarios — including the awkward ones, which is the point.

What it contains

  • — An individual with employment, rental and investment income
  • — A sole trader with mixed personal and business spending
  • — A company with payroll, assets and a book-to-tax difference
  • — A cross-border group with intercompany charges
  • — Receipts that are duplicates, illegible, or altered
  • — An assessment that disagrees with what was filed

How it behaves

Filing in the sandbox reaches an authority's test environment where one exists, and a simulator where it does not — and the response says which. A sandbox that always succeeds teaches you nothing about the failure you will meet in production, so the simulator returns rejections, information requests and reassessments on demand.

Keys are prefixed, and the prefix is load-bearing.

A sandbox key begins tf_test_ and a live key tf_live_. The server refuses a test key against production data and a live key against the sandbox, rather than routing by an environment header that a misconfigured deploy can get wrong in the direction that files a real return from a test suite.