Keptable
Detect revenue leakage. Recover missed income. Reconcile money flows across till, payments, settlements and bank.
The leak is real. The cause is fixable.
Most SMEs run revenue across at least four systems: a till, a payment processor, a bank, and an accounting tool. None of them agree at the row level. The 1–3% that goes missing every month looks like noise until you measure it. Keptable is the layer that does the measuring, names the cause, and gives staff a workbench to fix it.
How it works
Keptable ingests transactions, payments, settlements, adjustments, invoices and subscriptions from every system you run, and writes them to a single append-only ledger with currency normalisation, tenant isolation and a full audit trail. The financial truth of your business, in one queryable place.
A rules engine watches the ledger for the patterns that quietly cost you money: orders fulfilled but not paid, payments with no matching transaction, oversized discounts, voids without a reason, refund anomalies, settlement variance, duplicate payments, failed subscription renewals, overdue invoices and cash that never closed. Each detection opens a case for staff to act on.
Match transactions to payments to settlements to bank deposits, with amount tolerance and time-window logic. Surface mismatches, overpaid, underpaid, duplicate and unmatched as states a finance lead can act on. Stop the end-of-month spreadsheet exercise that nobody enjoys and nobody trusts.
When a detection fires, Keptable opens a case in the operational workbench. Notes, attachments, assignment, resolution reasons, escalation timers. Every action is logged. When a customer disputes a charge, an inspector asks a question or your accountant queries a discrepancy, the answer is one click away.
v1 detection set
Every detection runs as a typed, parameterised rule template. No free-text DSL, no surprises, no AI labelling that can't explain itself. Each one opens a case with the evidence the staff member needs to resolve it.
Who it's for
Hospitality is our v1 ICP. The architecture is connector-first and sector-agnostic; the buyer language and rule templates adapt.
Multi-site groups and growing independents. Till variance, settlement gaps, refunds without reason. Primary v1 ICP.
Trades, callouts, fleet operators. Jobs completed and billed but not paid. Settlements that don't match invoiced totals.
Appointment-driven businesses with deposits, products and services on the same till. Discount and void monitoring.
Subscription renewal failures, invoices overdue past tolerance, retainers that drift past their billing cycle.
Event-day variance: deposits, balances, cancellations, refunds and the mismatch between expected and recorded revenue.
Private practices and clinics with mixed payer models, insurance settlements and patient-side invoicing.
Refund-rate outliers, duplicate charges, payment-processor settlement variance, subscription churn signals.
Why we built this
GOOOD Mansfield runs ten kinds of revenue across a till, a payment processor, a Stripe account, a delivery partner and a bank. By month four, we knew the systems didn't agree, but couldn't say where. By month six, we had a £3,000 hole we couldn't attribute. Keptable started as the internal tool that gave us the answer; the platform exists because that hole exists in every multi-system operator we've since spoken to.
Frequently asked
We're piloting with multi-site hospitality operators ahead of public launch. Other sectors welcome to join the waitlist.