Connect a signing device in three steps, and hear before it lapses
Each subsidiary signs its invoices with a device registered with the tax authority. Your team onboards it from a wizard, runs the compliance check, activates it, and is warned before its certificate expires.
- Status
- Active
- Primary
- Yes
- Compliance documents
- 6 of 6 passed
- Certificate expires
- In 6 days
Held · Final-week warning sent: renew before it lapses
From new device to signing
Onboard
Enter the one-time code from the tax authority. Axon Suite creates the device’s key and requests its compliance certificate.
Compliance check
Six test documents are signed and checked: an invoice, a credit note and a debit note, each standard and simplified.
Activate
Only a device that passed all six can be activated for real invoices.
Make it primary
One device per subsidiary signs. Choosing a new primary stands the old one down in the same step.
Details that matter
Warned before expiry
A daily check notifies your users 30 days before a primary device’s certificate expires, again in its final week, and once it has lapsed.
Revoke when needed
A revoked device never signs again, whatever state it was in.
Keys kept encrypted
Each device’s private key and access tokens are stored encrypted under the subsidiary’s own key.
Questions buyers ask
Who can activate or revoke a device?
Running the check, activating and choosing the primary need approval rights on e-invoicing. Revoking needs full rights.
What happens if a certificate lapses?
The device stops signing, and that subsidiary’s invoices are refused until a device is active again.
Can a subsidiary have more than one device?
Yes, several, but only the primary one signs.