SearchStart a task
Guides›developers
developers

Testing versus production e-invoicing environments

Separate sandbox credentials, test taxpayers, schema versions and non-production identifiers from legally valid issuance.

e invoice sandboxtest invoice XMLproduction electronic invoice

What it means

Sandbox environments help test payload shape, authentication and workflow, but often use synthetic identities, relaxed checks or different certificates.

A sandbox success is not proof that production master data, routing and authority rules will pass.

Implementation method

  1. 1
    Maintain separate endpoints, credentials, certificates and data.
  2. 2
    Version test fixtures by country/profile release.
  3. 3
    Run negative tests, retries and status transitions, not only a happy path.
  4. 4
    Perform controlled production verification with approved entities and rollback procedures.

Common mistakes

!
Using production tax IDs in public test files

Build an explicit control or test case for this condition.

!
Sharing secrets between environments

Build an explicit control or test case for this condition.

!
Assuming sandbox code lists update on the same date as production

Build an explicit control or test case for this condition.

!
Skipping certificate rotation and clock-skew tests

Build an explicit control or test case for this condition.

Questions and answers

Can production responses be replayed in sandbox?

Usually not safely. Redact and transform test fixtures while preserving the structural condition being tested.

What should a go-live checklist include?

Credentials, endpoints, profiles, identities, routing, certificate trust, monitoring, support ownership and rollback.

Can EInvoiceLab officially certify test and production environments?

No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.

Should I keep the original structured file?

Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.