Accounting, unified at last.
Bookkeeping, VAT and MTD, payroll, practice management, e-commerce and client communication in one system — instead of five that almost agree with each other.
14-day free trial · no card required
The Frankenstein stack is expensive in a way nobody bills for.
Every tool in the list below is fine on its own. The cost is in the gaps between them — the exports, the re-keying, the quarterly reconciliation that exists purely because two systems hold the same number.
All eight are modules inside Qwikr. Not partners, not integrations — the same database, the same client record, the same audit trail.
The obvious transactions settle themselves
Reconciliation is mostly repetition with a few genuinely hard cases buried in it. Qwikr does the repetition with arithmetic — exact and tolerance matching, date windows, references and your own bank rules — before any model is involved.
What is left is the ambiguous pile, and that is where the AI is pointed. Its suggestions arrive with reasoning and evidence, and they wait in a queue for approval rather than posting quietly behind you.
- Deterministic matching runs first — rules always beat the model
- Receipt and bill OCR, matched to the bank line it belongs to
- Suggestions queued for approval with reasoning attached
- Every automated action written to the same audit log as a human one
Orders, fees and settlements — natively
Most accounting software has no concept of an order, a platform fee or a stock layer, so selling online means paying a third tool to flatten everything into journals before it arrives.
Qwikr connects to Shopify, WooCommerce, Amazon, eBay and Etsy directly. Payouts are decomposed back to the orders inside them, fee types are posted separately, and stock moves in real FIFO or LIFO layers.
- Five native marketplace and storefront connectors
- Settlements matched to underlying orders across period ends
- Commission, payment fees and refunds posted separately from revenue
- FIFO/LIFO stock layers with landed cost
Tax decided when the transaction is recorded
VAT goes wrong when the scheme is applied at the end of the quarter instead of at the point of entry. Qwikr decides the treatment as the transaction lands — domestic, cross-border, exempt or out of scope — and builds the return from that.
Selling into the EU, the customer's member state is determined from the evidence on the transaction and the destination rate applied, so the One Stop Shop return accumulates as you trade rather than being reconstructed each quarter.
- Standard, cash accounting and flat rate schemes applied at the point of entry
- EU One Stop Shop and EC Sales Lists built continuously
- Partial exemption and capital goods worked from the ledger
- Pre-filing diagnostics that catch the wrong return before HMRC does
Everything else, in the same system
Not a marketplace of partners. Modules, sharing one client record and one audit trail.
Built like financial software should be.
We are a new company, so we will not pretend to certifications we do not hold. What we can show you is how the thing is actually built.
A database per tenant
Not a shared table with a filter. Cross-tenant exposure is not one missing WHERE clause away.
Everything audited
Human, rule and AI actions all land in the same trail, with reasoning attached.
Encrypted credentials
HMRC, bank and accounting tokens encrypted at rest. TLS everywhere in transit.
API-first
The interface and the API sit on the same service layer, so anything you can click, you can call.
Moving across is the part everyone dreads
So it is built as a proper module rather than a support ticket. Import contacts, transactions, opening balances and history — then move the rest of your clients when you are satisfied.
Bring the history
Xero, QuickBooks, Sage and CSV — including opening balances, so nothing starts from a plug.
Start mid-year
No need to wait for April or a year end. Migrate when it suits the client.
A few clients first
Move a handful, satisfy yourself, then batch the rest. We will do the first ones with you.
Priced by what you use
Four plans, no per-client licences, no setup fee.
Questions, answered
The MTD functionality is built and works against HMRC’s API for VAT, Income Tax and RTI. Our production filing credentials are being finalised with HMRC, and until that is switched on the platform deliberately refuses to file rather than reporting a submission that never happened. We will tell you exactly where that stands before you rely on it for a deadline.
The migration centre imports contacts, transactions, opening balances and history from Xero, QuickBooks, Sage and CSV. Most practices move a few clients first, satisfy themselves, then move the rest in batches. We will do the first few with you.
No. Plans are bundles of modules, so you pay for what you switch on. A sole trader on Solo never sees practice management; a firm on Practice gets payroll and workflow included.
Payroll, practice management, AML, e-signatures, receipt capture, e-commerce sync and client messaging are modules inside Qwikr, not partners we integrate with. Whether that replaces your particular five depends on what you run — the honest way to find out is to tell us your stack and let us say which parts we do not cover.
Four plans, from £19/month for a sole trader to £149/month for a firm using every module, with a 14-day free trial and no per-client licences. Our first 500 customers pay half of that for 3 years.
That is the right question to ask, and we would rather answer it than dodge it. We are early, we hold no certifications yet, and we are onboarding practices deliberately slowly. What we can offer is a platform where every action is audited, your data lives in its own database, and you can export all of it whenever you like. Start with a few clients, not your whole book.
Start with one client
Not your whole book. Move a single client across, see whether it holds up, and go from there.