Larger organisations
Controls you can show an auditor, across every entity you run
For finance teams
- Several organisations, each with its own books and team
- Roles, with multi-factor authentication required by policy
- Approval trail on every posting and an audit history
- Organisation API keys and signed outbound webhooks
- Signed migration certificates when you move
What the work involves
What a finance team needs from its ledger
Run more than one entity
Each entity is its own organisation with its own books, team and settings, and people who work across them switch between organisations under one sign-in.In Kumry: Organisation switcher
Enforce access policy
Owners, admins, editors and viewers see and do different things. An organisation can require multi-factor authentication of everyone, and sensitive actions ask for it again at the moment they happen.In Kumry: Settings · Security
Evidence who did what
Each posting records who approved it and when, and the audit history shows who did what in the organisation. Each posted entry is linked to the one before it, so a change to an earlier entry would show up.In Kumry: Approval trail · Audit history
Connect your own systems
Organisation API keys act on behalf of the person who issued them, are stored only as hashes and are shown once. Some actions always stay with a signed-in person. Access is available on request.In Kumry: Settings · Integrations
Keep other systems in step
Signed outbound webhooks deliver events to an HTTPS endpoint you choose, so your endpoint can check each delivery came from Kumry.In Kumry: Webhooks
Move without losing the trail
Import each entity from Xero, reconciled to the cent against the source trial balance, with a signed migration certificate per migration. From QuickBooks Online, bring each entity’s chart of accounts, contacts and transaction history.In Kumry: Data migration
How it works
A walkthrough
How it works · an illustrative walkthrough, not a customer story
A group with three operating companies
A head office finance team, an accounts payable officer in each company, and a group reporting system that needs ledger events.
- 1
One organisation per company
Each company is set up as its own organisation; the finance team belongs to all three and switches between them.
- 2
Policy
Each organisation requires multi-factor authentication; AP officers are editors and the finance manager approves.
- 3
Migrate
Each company’s books are imported and reconciled to its source trial balance, and its certificate filed.
- 4
Integrate
An API key and a webhook endpoint connect the group reporting system to each organisation.
- 5
Audit
At year end the auditors are given the approval trail, audit history and migration certificates for each company.
Every entity has its own trail, and the evidence for a posting is in the ledger rather than in an email.
GST and BAS
GST and BAS for each entity
Traceable figures
GST groups
Lodging
Kumry prepares GST and BAS figures from your transactions. You, or your registered tax or BAS agent, review and lodge them with the ATO. This is general information, not tax advice.
Previews, stated plainly
Questions people ask
Can we see consolidated statements across entities?
Do you hold security certifications?
Is there an API?
Where is our data held?
Does Kumry run payroll or lodge with the ATO?
See how Kumry fits your group
Kumry accounts are set up on request: Get started takes you to a short request form.

