About Accruna
The books should be current. Almost nothing about accounting practice is.
Accruna is an accounting firm built on a simple observation: financial activity arrives continuously, but the profession still processes it in monthly batches. That gap is where late closes, stale numbers and unexplained balances come from. We built the firm to close it.
Accounting is the only function in a modern business that still ships on a monthly release cycle.
Everything else in the business moved to continuous. The ledger did not, because the work was too manual to run any other way. That constraint is gone.
Why Accruna exists
Accruna
The problem
Three things are true about accounting work at once.
None of them are anyone's fault. Together they explain why month-end is still painful in 2026 despite forty years of accounting software.
01
It is continuous, but done in batches
Transactions arrive every day. Processing happens monthly. That mismatch is what makes a close a project rather than a formality — a month of work arrives all at once, and it has to be understood before it can be booked.
02
It is rule-driven, but treated as judgment
Most of the volume involves no judgement at all: the same vendors, the same categories, the same treatment every month. It consumes senior time anyway, because there has been no reliable way to separate the routine from the ambiguous.
03
It is a service priced by time
Hourly billing means the firm is paid for inefficiency and the client is disincentivised from asking questions. Nobody designed it that way; it is simply what happens when the unit of delivery is a person's hour.
Our mission
Keep every client's books continuously closed, and make the reasoning behind every figure available.
That is deliberately narrow. We are not trying to build a general-purpose finance platform or an accounting AI for other firms to use. We are running an accounting practice, and the technology is how we run it.
Two commitments follow from the mission, and they shape most of our product decisions:
What we are
- An accounting firm, accountable for the work it produces
- A service engagement, not a self-serve software product
- Agent-operated in the transactional layer
- Human-owned in judgement, policy and sign-off
- Built to work with the systems clients already run
What we are not
- Not a licensed audit firm, and we do not issue audit opinions
- Not a tax filing service, though we maintain what filing depends on
- Not a replacement for a CFO's judgement or a controller's controls
- Not a tool we expect clients to operate themselves
- Not trying to serve every business — see our fit criteria
Product principles
Six principles we design against.
These are the tests we apply when deciding what to build, and the standards we expect to be judged by.
Principle 01
Automate the work, never the accountability
An agent may propose anything and approve nothing. If a human accepts a proposal, that human's name is on the entry. "The system decided" is not a position we will take with a client or an auditor.
Principle 02
Show the reasoning, not just the answer
A coding suggestion without its basis is not auditable, and it is not teachable. Every proposal shows the rule, the precedent or the pattern behind it — so a reviewer can disagree with the reasoning rather than just the outcome.
Principle 03
Never smooth a difference
Plugging, averaging or absorbing an unexplained balance is a decision to hide something. Differences are classified, assigned and stay visible until someone resolves them. This is slower on day one and considerably faster by quarter three.
Principle 04
Make everything reversible
Automation without reversibility is a liability. Entries are reversed rather than deleted, history is preserved, and the effect of any automated action can be identified and undone by batch.
Principle 05
Fit the client's stack, not ours
We adapt to the ledger, chart of accounts and tools a client already uses. Asking a business to re-platform its accounting to suit its accountant is a cost we are not willing to pass on.
Principle 06
Say what we do not do
Audit opinions, tax filing and certifications we do not hold. Stating limits plainly costs us some deals and saves both sides a great deal of time. A firm that overstates its scope will eventually underdeliver on it.
Who we build for
Companies whose finance work outgrew their finance capacity.
We are not sized for every business. These are the characteristics that make an engagement work well — and the ones that do not.
Characteristics of a good fit
- Meaningful transaction volume — enough that manual processing is a real cost
- Multiple systems — financial activity spread across tools that do not reconcile themselves
- External reporting needs — investors, a board, lenders or an audit
- A decision-maker available — someone who can approve mapping, policy and thresholds
- Willingness to document policy — or at least to let us help formalise it
- Comfort with automation — including the audit trail that comes with it
Characteristics that tend not to work
- Volume so low that a spreadsheet is genuinely cheaper
- A ledger locked inside a system with no API or export path
- Wanting a software licence with no service relationship attached
- Needing statutory audit sign-off rather than audit preparation
- Decision-making by committee on every mapping question
- Expecting the close to be fast while dependencies stay unresolved
How we approach the market
Four positions we have taken deliberately.
Each of these closes off options. They are choices rather than accidents, and they are worth knowing before you evaluate us.
We charge for the work, not the hours
Hourly billing pays a firm more when the work is inefficient, and it penalises a client for asking questions. We scope an engagement, quote it monthly, and absorb the efficiency gains rather than billing them back.
The trade-off: the scope has to be defined honestly at the start, which requires a real conversation about volume and complexity.
We do not sell software on its own
There is no self-serve plan and there will not be one. The value comes from the combination of agents and accountants; handing over the tooling alone would leave clients with the same problem and a new interface.
The trade-off: we cannot serve companies that want to run the process themselves, however capable they are.
We work with incumbents rather than against them
QuickBooks, Xero and the surrounding stack are where our clients' data lives. We connect rather than compete, because asking a business to migrate ledgers to suit its accountant is a cost with no return.
The trade-off: our capability is partly bounded by what those systems expose, and we are honest when a connection cannot be built.
We would rather lose a deal than overstate
No invented logos, no certification claims we cannot substantiate, no accuracy percentages we have not measured. Where a requirement is outside our scope, we say so during evaluation.
The trade-off: we lose deals to firms willing to be less precise, and we gain clients who read the details.
Where this goes
A close that stops being an event at all.
The end state is not a faster month-end. It is a ledger that is simply always correct — where "the close" is a reporting convention rather than a period of work, and where an accountant's time goes entirely to judgement, structure and advice.
Getting there requires three things to keep improving at once, and we are honest that the second two are harder than the first:
What success looks like for a client
- The ledger answers questions the day they are asked
- Month-end takes a review, not a week
- Every figure is traceable to a document and a decision
- Finance time goes to analysis and planning
- An audit is a review rather than a reconstruction
- Nobody is working the weekend to produce a board pack
Talk to us
The fastest way to judge this is to see it applied to your ledger.
We would rather you evaluated the output than the pitch. Bring real data and ask hard questions.
Book a demo
Thirty to forty-five minutes, working through your own ledger and a real month of transactions. The most direct route to a decision.
Email us
Security questionnaires, integration questions, partnership or press enquiries, or anything that does not need a meeting.
Read the detail first
Pricing drivers, the workflow end to end, and the security model — all documented before you speak to anyone.
Bring us your messiest month.
A recent trial balance, a bank statement and the transactions you are least sure about. That is a better demo than any walkthrough we could script.