Test vs live mode

A sandbox lets you create bookings, issue invoices, and save calculations without ever touching your real fiscal data — then wipe it all clean when you're done.

The Test / Live switch

At the top of the dashboard is a Test / Live toggle. It controls which set of data you're working with right now:

  • Live — your real bookings, invoices, and saved calculations. A green "Live data" indicator shows in the header.
  • Test — an isolated sandbox. A "Sandbox data" indicator and a banner remind you that test mode uses isolated sandbox bookings, invoices, and saved calculations.
The header toggle switches between live data and an isolated sandbox.

What test mode isolates

Test mode is a true isolation, not a visual filter. Records created while you're in test mode are flagged is_test and are kept separate from your live records at every layer:

  • Bookings, invoices, and saved calculations created in test mode are marked as test data and only appear while the toggle is on Test.
  • Fiscal numbering is separated. Test invoices burn their fiscal numbers from a dedicated TEST fiscal series, so practising issuance never consumes a number from your real, gapless live sequence. That separation is exactly what makes the whole test set safe to delete later.
Detail
Tax calculations themselves are identical in both modes — the same engine, the same jurisdictions and rates. Test mode changes where your saved records live and which fiscal series an invoice draws from, not the math.

Wiping test data

Because the sandbox is fully separated, an organization admin can erase it in one action without endangering live records.

  1. 1
    Open organization settings as an admin

    The wipe test data action is organization-admin gated. Regular members don't see it.

  2. 2
    Run the wipe

    TaxLens deletes the org's sandbox bookings, invoices, and saved calculations and returns a count of what was removed. Your live data — and your live fiscal sequence — are untouched.

Heads up
The wipe is destructive within the sandbox: it cannot be undone. It only ever affects is_test records for the active organization, never live data.