October 6, 2026

What an approval is bound to
When you approve something in Bertha, you approve exactly what you saw. Change a comma and the approval is gone.
"A person approves" is easy to say. It only means something if the approval is tied to the thing that was approved.
Think of a signature on a page. If someone can swap the page after you sign, the signature proves nothing. Bertha is built so the page cannot be swapped.
The approval covers what you saw
When Bertha prepares a reminder to a client or a set of write-offs, it shows you the whole thing: the recipient, the subject, the text, the amounts, the accounts. Behind the screen, that content is reduced to a fingerprint, called a hash. When you press approve, your approval carries that fingerprint.
At the moment of running, Bertha checks that what it is about to do has the same fingerprint. If it does, it runs. If it does not, it refuses and you review again.
So the approval covers the exact content shown, and nothing else.
Any change voids it
These all make an earlier approval void:
- you edit the subject or the text of a reminder,
- a document arrives that the reminder was asking for,
- an amount, a date or a description in the books changes after you looked,
- the approval was given more than 24 hours earlier.
The last one matters too. An approval is a decision about today's facts, not a standing permission. Reminders and write-off lists both expire after 24 hours and must be approved again.
The facts Bertha read are part of the approval. A write-off list records the version of every item it read, and a reminder records the version of the client's delivery. If any of them moved, the approval no longer matches.
Each action runs once and leaves a receipt
An approved action is written to a journal before it runs. When it has run, the receipt records what was done, who approved it, and when. Receipts are kept in the firm's own storage.
That order is what makes a crash harmless. If the device stops halfway, Bertha reads the journal on the next start and knows what already went out. A reminder is not sent twice, and a client's reminder count rises only from receipts, never from a guess.
Nothing is sent while unsure
Sometimes the outcome of an attempt is unknown: a mail server timed out, say, and Bertha cannot tell whether the message left. In that case it does not try again by itself. It hands the question to a person, because a second mail to a client is worse than a late one.
What is built and what is next
The approval, the journal and the receipts are built and tested in Bertha, and the reminders and write-offs both run through them, on demo data. Two things come before any real mail or booking: signing in as a named person, and a confirmation from the operating system itself for every approval, so the window alone cannot approve for anyone.
This is the rule behind everything Bertha does for you. If something goes to a client, changes the books or leaves the building, it is a proposal first, and a person decides. Read how a single reminder travels through it.
Sources. Bertha core, the actions, reminders, chase, books and desk modules.