Product
Six agents. One ledger. Someone accountable for every line.
Accruna is not a dashboard that sits on top of your books. It is the team that keeps them — a set of specialised agents, each responsible for one part of the accounting cycle, with experienced accountants owning the decisions agents are not allowed to make.
Agent roster
- Ledger agentCoding & classification
- Reconciliation agentBalance matching
- Expense agentPolicy & receipts
- Revenue agentInvoicing & AR
- Close agentChecklist orchestration
- Reporting agentStatements & variance
Overview
What the platform covers.
The full accounting cycle, end to end — so nothing falls between a tool that codes transactions and a person who reviews a report.
Core capabilities
Continuous bookkeeping
Transactions coded to your chart of accounts as they arrive, with source documents attached.
Bank & card reconciliation
Statement-to-ledger matching across every account, with differences classified rather than absorbed.
Expense management
Receipt capture, policy evaluation and an approval path for anything outside the rules.
Invoicing & receivables
Invoice creation, delivery, ageing and approved reminder sequences that stop when paid.
Month-end close
A fixed, ordered checklist with named owners and blocking review steps.
Reporting & analysis
P&L, balance sheet, cash view and variance narratives generated from the live ledger.
Agents
The repeatable work
Coding, matching, capturing, chasing, drafting, checklist execution.
Accountants
The judgment work
Policy calls, unusual items, variances, revenue recognition, sign-off.
You
The decisions
Approvals above your thresholds, budget context and final acceptance.
01 · Transaction ledger
Bookkeeping that explains itself.
The ledger agent reads every incoming transaction, identifies the counterparty, and proposes the account, class and tax treatment. It shows its reasoning — and it shows what it is unsure about.
Supplier intelligence
Vendor names are normalised so "AMZN MKTP US*2K4L" and "Amazon Web Services" resolve to the same counterparty with a consistent treatment.
Precedent matching
Each suggestion shows the similar historical transactions it was based on, so you can see the pattern, not just the answer.
Rules you control
Set deterministic rules for known cases. Rules always win over model suggestions, and the rule that fired is recorded on the line.
Confidence thresholds
You decide what auto-posts and what queues for review. Anything below the threshold is never posted on a guess.
AMZN MKTP US*2K4L
Sep 27, 2025 · −$320.18 · Mercury · Card ••4471
- Proposed account6100 · Software & subscriptions
- ClassEngineering
- Tax treatmentDeductible · SaaS
- ConfidenceHigh (96%)
- Precedents matched14 prior transactions
- Rule appliedR-0142 · AWS/Amazon → 6100
| Account | Statement | Ledger | Difference | Classification |
|---|---|---|---|---|
| Chase · Operating | $842,109.44 | $842,109.44 | $0.00 | Matched |
| Chase · Payroll | $96,204.10 | $96,204.10 | $0.00 | Matched |
| Amex · Corporate | $41,882.60 | $41,882.60 | $0.00 | Matched |
| Stripe clearing | $128,660.00 | $128,660.00 | $0.00 | Matched |
| Undeposited funds | $4,120.00 | $3,980.00 | $140.00 | Timing — resolves Oct 2 |
Timing differences are logged against the period they resolve in and clear automatically. Nothing is left as a permanent reconciling item.
02 · Reconciliation
Balances matched, differences named.
The reconciliation agent works the statement against the ledger line by line. What it cannot match it does not hide — it classifies the difference and routes it to the right owner.
- Line-level matching rather than lump-sum balancing, so a $140 difference is a specific item, not a rounding entry.
- Timing differences tracked across period boundaries with an expected resolution date.
- Suggested correcting journals for genuine mismatches — prepared, never posted without approval.
- Sub-ledger tie-outs for AR, AP, payroll, fixed assets and deferred revenue.
- Retained history for every account and every closed period, exportable for audit.
03 · Expenses & payables
Policy enforced before the money moves.
The expense agent reads receipts, matches them to card transactions, and evaluates each item against the spend policy you wrote. Anything ambiguous becomes an approval request with the policy rule quoted back.
| Merchant | Amount | Policy result | State |
|---|---|---|---|
| ABAirbnb | −$982.10 | Within lodging cap | Approved |
| UBUber | −$42.30 | Meals & transport | Approved |
| DLDelta | −$512.20 | Receipt missing | Flagged |
| NSNova Strategic | −$12,500.00 | Above approval threshold | Awaiting approver |
| FGFigma | −$144.00 | Software subscription | Approved |
Flagged items block only themselves. The rest of the ledger continues to code and reconcile while an approver responds.
What agents never do with your money
- Release a payment without an approved bill
- Change a supplier's bank details
- Override a policy rule it was not authorised to override
- 1 Invoice #2041 · Halden Retail $8,400.00 · 14 days overdue · reminder 2 of 3 queued Queued
- 2 Invoice #2044 · Presto Labs $4,200.00 · disputed on scope · excluded from sequence On hold
04 · Invoicing & receivables
Cash in, without the awkward chasing.
The revenue agent raises invoices, tracks them against terms, and drafts the follow-ups. You approve the cadence once — the agent keeps it running and stops the moment money lands.
- Invoice generation from retainers, milestones, usage or time, posted to the correct revenue account.
- Approved dunning sequences — you control the tone, the intervals and who gets copied.
- Dispute handling that pulls an invoice out of the chase sequence automatically.
- Deferred revenue schedules maintained against the same ledger the statements come from.
- AR ageing kept current as payments land, not rebuilt at month-end.
05 · Month-end close
A close that runs in the same order, every period.
The close agent orchestrates the checklist; humans own the sign-offs. Dependencies are enforced, so a task cannot be marked complete while its input is open.
| Close task | Owner | Evidence produced | Blocks close? |
|---|---|---|---|
| Bank and card reconciliation | Reconciliation agent | Signed reconciliation per account | Yes |
| Payroll tie-out to ledger | Payroll agent | Gross-to-net to GL bridge | Yes |
| Revenue recognition review | Revenue agent + accountant | Deferred revenue schedule and adjustments | Yes |
| Accruals and prepayments | Ledger agent | Basis for each accrual, with supporting calc | Yes |
| Inventory or WIP roll-forward | Ledger agent | Opening-to-closing movement, with variances | Yes |
| Intercompany elimination | Close agent | Elimination entries and residual check | Yes |
| Variance analysis | Reporting agent, reviewed by accountant | Narrative on material movements | Yes |
| Exception queue cleared | Assigned accountant | Decision and rationale per item | Yes |
| Statement pack issued | Accounting manager | P&L, balance sheet, cash view, close report | Yes |
Working days 1–2
Bank, card and sub-ledger reconciliations complete. Payroll and revenue tie-outs finish.
Working days 3–4
Accruals, prepayments and eliminations posted. Exception queue worked and cleared.
Working day 5
Variance narrative written, statements reviewed, pack issued with sign-off on record.
06 · Exception handling
The queue that keeps accountants in the loop.
An exception is anything an agent is not authorised to decide alone. It arrives with the context needed to make the call quickly.
What triggers an exception
- Vendor not seen before, or flagged as high risk
- Amount above your approval threshold
- Transaction conflicts with the expense policy
- Variance against budget or prior period beyond tolerance
- Missing documentation or an unmatched receipt
- Low confidence on coding with material value
What arrives with each item
- The source document and the bank or card line
- The agent's proposed treatment, in plain language
- Comparable historical items and how they were handled
- The rule or policy clause that was touched
- The accounting impact if the proposal is accepted
- Who else has seen it, and what they decided
What happens after the decision
- The entry posts with the accountant's name attached
- The decision feeds the precedent set for future coding
- If it reveals a policy gap, you can amend the rule
- The full before-and-after is written to the audit log
- The close checklist unblocks and continues in order
07 · Reporting & analysis
Reports that arrive before you ask.
The reporting agent builds statements from the live ledger and drafts the variance narrative alongside them. An accountant reviews the commentary before it reaches you, so you read analysis rather than a data dump.
Financial statements
P&L, balance sheet and cash flow, in your reporting currency and, where relevant, on a consolidated basis.
Budget vs. actual
Variance against the budget you load, with movements beyond tolerance explained rather than listed.
Cash position
Cash by account and currency, with a short-horizon view built from open receivables and scheduled payables.
Unit economics inputs
Revenue and cost by class, project or customer, so margin analysis is possible without a separate workbook.
Close report
A period summary: what closed, what was adjusted, what was flagged, and who signed off on each part.
Audit pack
Reconciliations, workpapers, journal support and approval history bundled for external review.
| Line | Actual | Budget | Variance |
|---|---|---|---|
| Revenue | $125,430 | $118,000 | +6.3% |
| Cost of revenue | ($31,120) | ($30,500) | +2.0% |
| Gross profit | $94,310 | $87,500 | +7.8% |
| Payroll | ($48,920) | ($49,600) | −1.4% |
| Marketing | ($21,540) | ($14,000) | +53.9% |
| Software | ($6,842) | ($7,200) | −5.0% |
| Net income | $43,185 | $36,700 | +17.7% |
Variance narrative — marketing
Spend of $21,540 is $7,540 above budget, driven by the September product launch campaign ($6,900) plus a reclassification of $640 of agency work previously coded to professional fees. Approved by M. Okonjo on Sep 28.
Comparison
How this differs from a monthly bookkeeping service.
Both produce a set of books. The difference is when the work happens, and what happens when something does not fit.
| Dimension | Typical monthly bookkeeping | Accruna |
|---|---|---|
| When work happens | In a batch, after month-end | Continuously, as transactions arrive |
| Coding rationale | Held in the preparer's head | Recorded on the line, with precedents |
| Reconciliation | Monthly sweep, differences carried | Daily, at line level, differences classified |
| Receipt collection | Chased by email at month-end | Captured as spend occurs, duplicates blocked |
| Question turnaround | Depends on the preparer's queue | Live ledger, answerable same day |
| Close duration | Two to four weeks after period end | Designed for the first week |
| Audit preparation | Reconstructed from scratch | Workpapers retained as they are produced |
| Scaling with volume | Requires more people | Volume absorbed by agents; people review |
| Accountability | Depends on who was assigned | Named owner on every task and sign-off |
When to look elsewhere
- You need statutory audit sign-off as a licensed audit firm
- Your ledger is a bespoke ERP with no export or API path
- You want to file your own tax returns and only need a coding tool
- You have fewer than roughly 50 transactions a month and a spreadsheet works fine
Where the fit is strongest
- Transaction volume has outgrown manual processing
- Investors, lenders or a board need numbers on a schedule
- You are preparing for a raise, an audit or a diligence process
- Finance capacity is the constraint, not finance expertise
- Work happens across several tools that do not reconcile themselves
Technical capabilities
Built for the way finance data actually moves.
Detail for the finance engineer or controller who has to make this work with the rest of the stack.
Data ingestion
Bank feeds through aggregators, direct ledger APIs, card and payroll connectors, plus scheduled CSV and SFTP imports for anything without an API.
- Idempotent imports — reloading a file will not double-post
- Field-level mapping you can review and version
- Rejected rows surfaced with the reason, never silently dropped
Data model
Double-entry throughout, with multi-entity, multi-currency and dimensional reporting (class, location, project) available from the first period.
- Immutable journal history with reversal, never deletion
- Attachments stored against the entry, not the batch
- Period locking with a documented reopen process
Rules engine
Deterministic rules for known patterns, evaluated before any model suggestion. Rules are versioned so you can see which version was in force at any time.
- Conditions on vendor, amount, descriptor, account and day of week
- Simulation mode to test a rule against history before enabling it
- Rule hit counts, so unused rules can be retired
Controls
Separation of duties between preparing, approving and posting, with approval thresholds set per entity and per amount band.
- Delegation with an expiry date, not an indefinite handover
- Dual authorisation on supplier bank detail changes
- Access reviews with an exportable permission matrix
Security
Least-privilege access for people and agents alike, with encryption at rest and in transit and an audit log covering every action.
- Agent credentials scoped to a single task, rotated automatically
- Full audit trail with actor, timestamp and before/after values
- Data residency options discussed during scoping
Reporting and export
Statements, schedules and workpapers available as PDF, spreadsheet or structured data, produced from the same source as the ledger itself.
- Scheduled delivery to a list you control
- Comparative periods with a stable report layout
- Historical export of every period you have been with us
In practice
Which capabilities matter most, by situation.
Rarely does a company need every feature on day one. These are the usual starting points.
| Situation | First capability to switch on | Why it helps first |
|---|---|---|
| Preparing for a raise | Reporting & audit pack | Statements and workpapers that survive diligence review |
| High card spend | Expense policy engine | Stops out-of-policy spend before it reaches the ledger |
| Ecommerce volume | Reconciliation at line level | Processor payouts matched at scale without manual pairing |
| Slow collections | Invoicing & dunning | Consistent follow-up without anyone drafting emails |
| Multi-entity growth | Consolidation | One close calendar across every entity and currency |
| First audit | Traceability & audit trail | Every figure traceable to a document and an approval |
Product questions
Questions about the product.
The ones finance teams ask us most often, answered without hedging.
Yes, within limits you set. Coding and classification can post automatically above a confidence threshold, for values below your approval band, where a rule or precedent applies. Journal entries, accruals, corrections and anything touching cash require a human approval before they post.
You choose the thresholds, and you can change them at any time. If you would rather review everything for the first quarter, that is a supported configuration — many engagements start that way and loosen up once the precedent set is established.
Your chart of accounts stays yours. During onboarding we map it in full — including classes, locations and project dimensions — and agree how each account is used. We will flag accounts that are ambiguous or duplicated, but we will not restructure your ledger unilaterally.
Where a restructure would genuinely help, we will propose it with the migration cost and the effect on comparatives, so it is your decision.
Subscription, retainer and milestone revenue are supported with schedules maintained by the revenue agent. Deferred and unbilled balances roll forward automatically and reconcile to the ledger each period.
The accounting policy is agreed with you at onboarding and reviewed when your contracts change. The agent applies the policy; an accountant owns any judgement call about whether a contract has changed it.
Yes, and it often works well. Accruna can operate purely as the accounting engine while your existing advisor keeps the strategic relationship. Access can be scoped read-only for them, or with review rights if they want to approve work.
The one thing we will not do is produce work that a second firm then re-does in parallel. If your accountant wants to keep preparing the books, that is fine — but the value of Accruna is that the ledger is already maintained, so duplicating it defeats the purpose.
Each entity keeps its own books in its own functional currency. Consolidation runs with the exchange rates you approve, and intercompany balances are eliminated with any residual difference flagged rather than absorbed.
Translation differences are tracked separately from trading results, so the consolidated P&L reflects performance and the reserve reflects currency movement — the way it should be.
Every automated action is reversible and recorded. A miscoded line is reclassified with the original entry preserved; an incorrect accrual is reversed with an explanation attached. Nothing is deleted.
We also monitor agent accuracy by category and will tell you where performance is weaker — for example, a new vendor type with few precedents — rather than letting you assume uniform confidence across the ledger.
Accruna keeps the books that tax filings depend on, including sales tax categorisation and the schedules your preparer will ask for. The filing itself depends on your jurisdiction and structure, and is scoped as a separate engagement with the right licensed preparer.
What you get either way is a ledger that reconciles, which is the part that usually makes filing painful.
See your own ledger, handled.
We will take a recent month of your transactions and walk through how each capability would apply — including where a human would have to step in.