View solution: Business management
Skirmbooks is the accounting and tax platform we built for Skirmshop Spain, the founder’s online store. It came from a simple question: if the store already produces every invoice and every sale in our own systems, why did the books have to be rebuilt by hand every quarter?
The challenge
Running the admin of a store that sells to several countries is a constant drip. The bank piles up movements that have to be matched with invoices; suppliers email their invoices, when they remember to, and sales have to end up as ledger entries and in the quarter’s VAT. When all of that is gathered at the end of the period, whatever is missing turns up late and in a hurry.
We did not want to replace the accounting firm. We wanted the work to reach them done and checked.
The solution
Skirmbooks is split into eleven modules, each with one job, which talk to each other through events on a message queue. By design, none of them writes into another’s area, and every periodic task is an independent trigger that can run again without duplicating anything.
Every morning the bank movements are imported over PSD2, along with the payment gateway’s. Every quarter of an hour one sweep proposes matches for anything new and another generates the ledger entries for received invoices and store sales; the database rejects any entry whose debits and credits do not balance. When a charge shows up without an invoice, the system looks for it in the mailbox and flags it if it cannot find it. Once a week it also analyses thirteen months of invoices to spot the recurring ones and anticipate when the next should arrive.
On the tax side, drafts of the Tax Agency returns are recalculated daily while their filing window is open. Each month the books the accounting firm has already filed are downloaded from the SII and compared with the ledger and the bank.
AI steps in where it helps: it reads and classifies invoices, and the codebase also includes a validator that checks tax decisions against a corpus of regulations. It files nothing on its own. The accounting firm still reviews and files; Skirmbooks prepares, cross-checks and alerts.
The result
The platform is designed to have the store’s books up to date every morning, and it flags mismatches as soon as they appear, without waiting for quarter close. Each module runs on its own and every periodic task is a separate trigger: the modules that process queues scale with KEDA according to the load on their queue, and the periodic batch jobs scale up from zero when it is time for them to work. It is multi-company and already sends our own company its daily summary of invoices still to be matched.