A new set of books,productive from day one.

Chart of accounts, master data, accounting history, firm rules and data and documents available for the new company. The actual sources depend on the accounting software and the flow of the firm.

No. The accounting software remains the firm's accounting system. Clerk uses it operationally: navigates the screens, carries out authorized work and updates the work in the same environment already used by the team.

Through a browser extension, working in the session the firm has already opened: the credentials stay yours and you never hand them over. Clerk opens the screens of the accounting software and writes into them the way a colleague sitting at that desk would, and after each entry it reads back to check it went through. It is not a link between systems: it is an operator. The flip side is that when the software vendor changes the screens the extension has to be updated, which is why we keep watch on the vendor’s roadmap.

We will tell you straight away, so you do not have to fill in a form to find out: today Clerk works inside Genya, and that is the only accounting software it writes into. Getting inside a piece of accounting software means writing an operator for it, screen by screen, and there is no switch that turns them all on. If you use TeamSystem, Zucchetti, Profis or anything else, automatic posting is not there today and you would have to wait for your own software; the review — the part that rereads what has already been posted — we can run on an export of yours, without touching the software, and tell you what it finds. We would rather say so now than after three meetings.

The accountant, as with a colleague’s work: responsibility for the accounts and the tax returns cannot be transferred to a piece of software, and we are not selling you that. This is why Clerk posts on its own only where the firm has already confirmed that treatment, stops where it is unsure instead of guessing, and leaves a record of what it did and when, line by line: you can always tell what it wrote and what you wrote.

They are two separate layers, and the whole thing rests on that distinction. To propose an entry Clerk looks at how previous ones went: that is a clue, and as such it can also inherit the bad habits of whoever came before. To review, on the other hand, it uses neither the history nor AI: it applies fixed rules that give a true or false answer. A payment to a supplier that is matched to no invoice is an error, not an opinion. Where the rule is only a suspicion it says so as a warning, and where it lacks the data to rule at all it stays silent and tells you, rather than passing the gap off as a check that was cleared. A reviewer who gets one finding wrong out of twenty is ignored on all twenty.

We are not giving you a percentage, because it depends on how regular your companies are and we would not know beforehand. What we will tell you is how it grows: at the start Clerk posts and brings everything to review, and it takes on a type of operation by itself only after the firm has confirmed that treatment several times. The scope starts narrow — the most repetitive and regular cases — and widens from there. «Authorised» means this, in practice: not a single switch that turns everything on, but one type of operation at a time, switched on by you and switchable off by you. Outside that scope it does not try: it stops and hands it to you. Credit notes, transfers between accounts, accruals and prepayments, withholding tax and the less straightforward VAT cases are work for a professional, and until they enter the confirmed scope they stay yours.

the accountant. Clerk isolates decisions it can't yet automate, shows available context, and learns from the confirmed choice.

Let's start with a new real set of books, from the accounting software you use and from the data available. This way we can see how much onboarding, how much operation and which audit controls Clerk can take over.