Bookkeeping is mostly re-typing things the business already knows

Sit with a bookkeeper for a morning and count how much of the work is discovery and how much is transcription. A sale happened at the till; someone types it into the accounts. Payroll ran; someone types the journal. Stock was revalued at the quarter; someone works out the entry and types that too.

None of that is bookkeeping. It is data entry against a business that already knows the answer, and it is where the errors come from — because a figure typed twice is a figure that can differ twice.

Books is the hub, not another app

Rutba Books sits at the point every other product posts into. A sale at the point of sale, a payroll run in Rutba People, a stock movement in Rutba Inventory — each writes its own journal entry as it happens, not in a nightly batch and not through an export somebody schedules.

That changes what month end is. It stops being a reconstruction of what happened and becomes a review of what is already recorded. The close is a reading exercise, not an archaeology one.

Two apps, one ledger, one licence

The purchase gets you two applications, and they are deliberately not a basic tier and a professional tier.

• Books — the daily surface: invoices, bills, receipts, supplier payments, credit notes, quotes, banking and reconciliation, expenses, collections, and the customer and supplier ledgers.
• Accounts — the accountant’s workbench: chart of accounts, journals, tax and periods, budgets, projects, currency, and the financial reports.

They are lit by the same pair of module keys because they are two views of one ledger — the operator working today’s invoices and the accountant working the period. Splitting the licence would mean charging you to see your own books twice, and neither view hides anything from the other.

The part where most accounting software is vague

Bank connections are where product pages get slippery, so here is ours in plain terms. Statement files work today, in whatever your bank actually emits — CAMT.053, MT940, OFX/QFX or CSV — and so does SFTP delivery. Reconciliation must reach zero; it does not let you close a match that does not balance.

Payment runs go out under a build, approve, export, settle discipline, exported as ISO 20022, ACH or CSV. The approval step is not decoration: a payment file is the one artefact in a finance system where an unreviewed mistake leaves the building.

The credit gate, as an example of the point

Here is the kind of thing that only exists when the books are not a separate system. A customer at the counter asks to pay later. The till checks the credit gate — their balance, their terms, their history — before completing the sale.

In a business running a separate accounting package, that check is a phone call to the office, or it does not happen. It is not a feature anybody puts on a feature list, and it is worth more than most of the things that are on one.