The engine, without
our interface on top.
For groups running multiple entities, platforms embedding accounting into their own product, and firms whose requirements need a contract rather than a checkout page.
Built to be built on
The API came first rather than last, which is why it covers the whole product instead of the parts someone got round to exposing.
Documented REST API
Every object the interface touches is reachable over the API — contacts, invoices, bills, journals, payroll, clients and returns — with generated reference docs kept in step with the code.
Signed webhooks
Subscribe to events, verify the signature, and get delivery attempts logged with retries rather than a single fire-and-hope POST.
Scoped API tokens
Tokens issued per integration with their own permissions, revocable independently, and every call attributable in the audit log.
Per-tenant isolation
Each tenant gets its own database rather than a shared table with a filter on it. One customer’s query cannot reach another customer’s rows.
Multi-entity consolidation
Group structures with intercompany eliminations and consolidated reporting, rather than a spreadsheet that merges four exports.
Reporting packs
Templated board and management packs generated on a schedule and delivered automatically to the people who need them.
Marketplace and Zapier
Connect the long tail of tools through Zapier and the app marketplace where a bespoke integration is not worth building.
Headless deployment
Run Qwikr as the financial engine behind your own product, with your interface in front of it and none of ours in the way.
Bespoke terms
Data processing agreements, security review, support terms and service levels negotiated rather than clicked through.
Events you can actually rely on
Most webhook implementations send a POST and consider the job done. When your endpoint is briefly down, the event is gone, your system is silently out of step with the ledger, and nobody finds out until a figure disagrees.
Qwikr signs every delivery, records each attempt with its response, and retries on a backoff. When something fails you can see exactly what was sent and replay it.
- HMAC-signed payloads you can verify before trusting
- Delivery attempts and responses logged and inspectable
- Automatic retries with backoff, and manual replay
- Per-endpoint subscriptions so consumers get only their events
{
"contact_id": "ct_8f21",
"reference": "INV-2291",
"currency": "GBP",
"lines": [
{
"description": "Advisory — September",
"quantity": 1,
"unit_amount": 1450.00,
"tax_rate": "STANDARD_20"
}
]
}Consolidation without the spreadsheet
Groups usually consolidate by exporting each entity, pasting into a workbook, and adjusting for intercompany by hand. The workbook then becomes the actual source of truth, and it lives on somebody's laptop.
Qwikr holds the entities in one structure, eliminates intercompany balances and transactions as part of the consolidation, and produces the group position as a report rather than as a file.
- Multiple legal entities under one group structure
- Intercompany balances and transactions eliminated automatically
- Currency translation for overseas subsidiaries
- Group and entity reporting from the same underlying ledger
Questions, answered
The API is not a reporting afterthought bolted onto a web app — the application and the API sit on the same service layer, so anything the interface can do is available programmatically. That makes it viable to put your own product in front of Qwikr and use it purely as the ledger and compliance engine underneath.
Each tenant has its own database. That is a stronger boundary than row-level filtering, where a single missing WHERE clause exposes other customers, and it makes per-tenant export, backup and deletion straightforward rather than a migration.
Standard plans run on shared limits appropriate to interactive use. Enterprise agreements set throughput against what you actually need — tell us the shape of your load and we will write it into the agreement rather than guessing at a number now.
Yes, as part of an enterprise agreement, with the specifics agreed in writing. We would rather commit to something we have negotiated with you than publish a number on a marketing page.
Single-tenant deployment is available under an enterprise agreement where there is a regulatory or contractual reason for it. It is a conversation rather than a checkbox — talk to us about the requirement.
Not yet. Staff sign in with email, password and two-factor authentication. Single sign-on through Google or Microsoft identity is on the roadmap — tell us which identity provider you use and we will tell you where it stands.
Qwikr is a young company. We would rather tell you that plainly and then answer whatever your procurement process needs to ask, than publish a wall of badges. Bring us your security questionnaire.
Tell us what you need it to do
Send over the requirement, the integration shape or the security questionnaire. We will tell you honestly whether we are the right fit.