Our accountant doesn't see our invoices. And that's OK

Krystyna has been our accountant since July 2026. And she doesn't see our invoices.

Wait — let me explain, because it sounds worse than it is. Krystyna sees the result: ordered sets of documents that land in her inbox. What she doesn't see is what we see — the raw stream of invoices, confirmations, reminders, and the whole circus that normally ends up in an accounting firm's mailbox.

And that's OK. Actually — that was the point.

The classic flow goes like this: an invoice lands in the company inbox. Someone opens it, saves it, forwards it to the accounting office. Then: "did it arrive?", "send it again", "what about the one from the 12th?". Someone builds a spreadsheet to track what's been sent and what hasn't. The accountant gets PDFs in random order and sorts them herself. Everyone wastes time, nobody is sure of anything.

We were about to do exactly that. Seriously. In July 2026, right after the KRS entry (0001255421), we started with the perfectly classic question: "how are we going to hand documents over to the office?". And I think only because we happened to be building our own mail infrastructure at the time, one of us said: "why hand anything over at all?". [to be confirmed by Kamil: who said it and when — I want a concrete detail here]

Exactly.

Instead of a manual flow, we did one thing: all accounting correspondence goes to a single alias, [email protected]. That's it. No copy-pasting, no "send me the scan again". On the way sits the same worker we use for all our mail — it filters, sorts, and makes sure Krystyna gets what she's supposed to get. We keep contacts in a whitelist in a plain Google Sheet as CSV: new counterparty = new row, no redeploys.

And here's the core of the shift I want to write about:

We assumed control equals visibility. That if the accountant doesn't see every invoice with her own eyes, the flow is broken. That something will get lost, that someone will miss something, that "that's not how you do it".

It works the other way around. When an automation does the sorting, the accountant gets less noise and more of what matters. In her first week, Krystyna caught a NIP-8 correction for us and handled the VAT-R — not because she dug through our mess, but because she got a clean, complete package. Her work starts where our pipeline ends.

What were we afraid of? That something would disappear. And that was the only legitimate fear — which is why the gateway is fail-open: even if the worker dies, the mail still reaches the inbox. Sorting can be redone. Losing something can't. That was our hard design rule and probably the only one we never negotiated.

I'm not sure this works for everyone. It worked for us because we're small: one alias, a handful of counterparties, one accountant. With thousands of documents, we'd probably need more than a CSV in a spreadsheet. But I think the principle holds: the accountant doesn't need to see raw invoices. She needs to see an ordered result. Visibility is not control. Control is a pipeline that sorts for the human.

Looking back, we'd do the same thing — just faster. We spent the first days on a "who sends what to whom" spreadsheet that died after two days, because it turned out nobody sends anything to anyone. [to be confirmed by Kamil: did that spreadsheet actually happen, or is that my over-interpretation — if not, I'll cut it]

Next week: the mail gateway that never blocks. This story has a second layer — and that's where I'll show how we built it.