Kora, the assistant in every plan
Meet Kora.
She reads everything. She undoes anything she does alone.
Kora comes with every Stone Ledger plan and with the trial. She reads your ledger, your stock, your pipeline and your payroll, answers questions across all of them, and prepares documents for you to approve. Work she runs unattended happens only inside a standing approval you gave, and only where the effect can be put right; money and anything irreversible always wait for a person. This page says exactly what she does on her own, what waits for you, what the Advanced seat adds, and the things she is never allowed to do.
On this pageWhat Kora doesWhat waits for youHow a change is put rightAdvanced KoraAutomationsMeasured
In every plan
One question across the whole business, answered from your own rows.
The included Kora is not a teaser for a paid one. She reads the actual rows of your books, your stock, your pipeline and your people, not a summary somebody exported last night, and answers in plain English, citing what she read.
Across everything
One question, not two systems
"Which customers are late paying and also have an order waiting to ship?" is a single question here. Anywhere else it is a CRM, a ledger, an export and an afternoon.
Shows her working
Every answer points at its rows
Open them. An answer that cannot show where a number came from is a rumour, and you do not file a return on a rumour.
Drafts
Invoices, journals, quotes, orders
Filled in and unposted, waiting for you. You approve a document, not a suggestion in a chat window.
Your permissions
She sees only what you can see
Ask about a payroll you are not allowed to open and she will not answer, because she cannot read it either.
Your data stays
No third-party model vendor
Kora runs on Stone Ledger's own servers against Stone Ledger's own knowledge store. Your books are not sent to another company's model.
What waits for you
Kora reads anything you can read. What she may write is bounded.
Everything she can do is one of four kinds. The first happens on its own; the second and third wait for you unless YOU have given a standing approval that names the operation, and even then money and anything that cannot be undone still wait. The fourth never happens at all. This is the same on both tiers — the Advanced seat buys depth, not permission.
- 01
Looking something up. Happens straight away
Balances, ageing, a customer's history, a variance, what changed last week, where a number came from.
- 02
Preparing a document. Waits for you
An invoice, a journal, a quote, a purchase order, filled in and unposted. You approve the document.
- 03
Changing the books. Waits, unless you said otherwise in advance
Posting, closing a period, changing what somebody may do, deleting anything. It waits for you — unless a standing approval you gave names that operation and its scope AND the effect can be put right, in which case it may run unattended and you read it in the day's report. What was approved, by whom, with what figures and when are kept together afterwards either way.
- 04
Moving money, or anything that cannot be undone. Always waits
Paying, transmitting a filing, sending. No standing approval reaches these: every operation that moves money needs a fresh one-time passcode typed by a person immediately before it happens, and an automation cannot satisfy that.
- 05
Saying something happened in the world. Never
She cannot sign a compliance record. She did not see the laptop handed back or the training finished, so she may not say she did. 18 of 59 controls are marked not-evidenceable for the same reason.
Kora reads everything you can read. Nothing she does alone is anything you cannot undo.
How a change is put right
Nothing she does on her own is something that cannot be undone.
"Everything is reversible" is a claim no accounting system can honestly make. You cannot unsend an e-mail, untransmit a filing or unpay a supplier. What is true here, and what you can check, is that every one of the 292 operations that change the books declares which of these three it is. An operation that declares none fails our own build.
| How it is put right | Operations | What it means |
|---|---|---|
| A rewind | 137 | The platform undoes it: a reversing entry, a compensating action, with preconditions. |
| A forward correction | 27 | Superseded, amended, adjusted, reprinted. You do not erase a posting; you post the correcting one. |
| Neither, and it says so | 128 | A filing an authority accepted. A payment that left the bank. Each carries a written reason, and Kora may never do one of these on her own. |
| Every operation that changes the books | 292 | of 883 registered operations. |
On her own
Three conditions. All three, every time.
Kora runs a job unattended only when all three hold. They are read from the operation itself at the moment it runs, never from a list somebody keeps by hand.
- 01
A person gave a standing approval
Naming the operation and its scope, unexpired and not revoked. A standing approval authorises the work, never the rules around the work. She cannot widen her own limits.
- 02
The effect can be put right
A rewind or a named forward correction. If it is one of the 128 that cannot be put right, it waits for you, however routine it looks. Being sure is not the same as being allowed.
- 03
No money moves without a person at the keyboard
Paying a bill reverses in the ledger, but the money still left. So every operation that moves money requires a fresh one-time passcode typed by a person, immediately before it happens. An automation cannot satisfy that, by construction.
| Outcome | When | What you do |
|---|---|---|
| Done | All three conditions hold | Nothing. You read it in the day's report. |
| Staged | The work can be prepared but not committed: money, a filing, anything that leaves the building | Inspect a finished batch and approve it in one action. Every item shows the instruction that created it. |
| Refused | Outside the standing approval, its scope, or your plan | You are told why, by name. Nothing half-happens. |
Advanced Kora
The included assistant answers a question. The Advanced seat takes a job.
Advanced Kora reads, decides, acts, checks her own result and keeps going until the job is done or she needs you. She can be spoken to, she runs your automations while nobody is watching, and she brings Advanced Analytics with her. The difference is depth, never permission: the rules above are identical on both. Sold per assigned person on every paid plan, so you give her to the three people who need her. The price is on Pricing.
| Capability | Included Kora | Advanced Kora |
|---|---|---|
| Answers a question from your records | Yes | Yes |
| Works a whole job through, checking her own result | — | Yes |
| Steps she will take on one question | Standard | Twice as many |
| Voice: speak to her, she speaks back | — | Yes |
| Runs automations unattended | — | Yes |
| Advanced Analytics | — | Included |
| Daily allowance | Standard | Twice the standard |
| Moves money, or does anything that cannot be undone, on its own | Never | Never |
| Changes the books on its own | Only under a standing approval you gave | Only under a standing approval you gave |
| Signs a compliance record | Never | Never |
| Price | In every plan | Per assigned person, on any paid plan |
Advanced Analytics
Your own data beside the ledger. One question across both.
Every plan reads the figures the product computes: statements, ageing, dashboards. Advanced Analytics is the other half, packaged with Advanced Kora because the two answer the same request: work this out for me.
- 01
Load a file, query it with the ledger
A bank export, a supplier's price list, last year's spreadsheet. Query it and your books in one question, without it ever becoming a posting.
- 02
One definition of every figure
"Gross margin" is defined once, and every report, dashboard and Kora answer uses that definition. Two reports disagreeing about one word is a definition problem, and it is removed here.
- 03
Budgets against what actually posted
Variance is computed off the ledger, not off a spreadsheet kept beside it.
Automations
Standing rules that run without anyone opening the screen.
An automation is a rule you write once: when this happens, do that. Kora runs it at the hour you chose, under the name of the person who owns it, and can do exactly what that person could do and no more.
- 01
Good for the work that is certain and dull
Chase the ageing at nine on a Monday. Flag every bill that arrives without a purchase order. Reconcile the settlement file the morning after it lands. Prepare everything, post nothing, put the exceptions in front of a person.
- 02
Comes with the Advanced seat, on any paid plan
You do not need a bigger plan to automate something. The adapter builder, which lets Kora work a system we ship no connector for, is company plumbing and stays with Corporate and Suite.
- 03
Three things take a job off the unattended list
It would change who may do what. It would claim something about the outside world. It would set the standard it is judged by. No matter how routine it looks.
Measured
Numbers with a published floor, not a demo.
Answerability is the share of questions a person judged answerable that Kora answers from the organisation's own records. The correct-refusal rate is the share of out-of-scope questions she declines instead of inventing an answer. Both are measured on question sets written before the work they test, and each figure is a floor the product's build enforces: a release that falls below it does not ship.
Everywhere you work
The same Kora, wherever the work is.
She is not a separate product with its own login. She is inside the accounting screens, the warehouse, the payroll run, the CRM and the portals, whichever of them you have enabled, and she is in the API so your own tools can ask her too. Voice, on the Advanced seat, works on the desktop and in the phone app.
The Foundation
What every plan includes, from the smallest up: the whole ledger, the close, the audit trail, the portals and Kora.