Accounting you can sign off on.
What protects your books isn’t a promise: it’s system rules that can’t be bypassed.
Permissions · External accountantThe certificate key, kept out of the database
The private key of the digital seal certificate is handed to the authorized certification provider (PAC). If you decide to keep it so you can cancel invoices, it stays on the server, outside the database; you can uncheck that option.
We never ask for the e.firma
An advanced electronic signature shouldn’t live in a system the hotel doesn’t control. Your accountant signs the XML.
Permissions by action
Entering data, configuring, closing the month and reopening it are separate permissions. Reopening is a special permission that no one has until it’s granted.
The rules that can’t be bypassed
- The day’s report stays signed and immutable, with who signed it and when.
- Journal entries are never edited or deleted; they’re corrected with another journal entry.
- A closed month can only be reopened with permission, and the reopening is recorded with its reason.
- The transaction log shows who made each transaction, or which process made it.
- Each hotel sees only its own information.
What we don’t promise
We don’t claim certifications we don’t have. If your auditor needs specific security information, write to us.
Start with yesterday.
If your hotel already signs off on its night audit, Containn can post yesterday today. The chart of accounts is set up in one step, the transaction code mapping is done once, and from then on every signed-off day becomes a journal entry.