FAQ
Common questions
How is data isolated between our entities?
Each entity's chart of accounts and ledger are logically separated within the same installation. Multi-entity support is a first-line design property, not a bolt-on — one deployment can serve entities in different jurisdictions without forking the code or the chart of accounts.
What does implementation look like?
Implementation timelines and the integration specification are shared once you request documentation. It depends on how many entities, currencies, and reporting frameworks are in scope for your first installation.
Which reporting frameworks are supported?
The reporting framework is set per entity — IFRS, US GAAP, or a local framework — so one installation can serve institutions in different countries without a fork. Statements export as ISO 20022, the format banks, auditors, and treasury systems already read.
How is pricing structured?
Licensing is structured around the number of legal entities on one installation, active currencies, reporting frameworks required, and integration support level — not per-seat. See how pricing works; commercial terms are confirmed during technical evaluation.
Do you replace our existing accounting system, or sit alongside it?
Reserve Fintech is the ledger and accounting layer itself, not a reporting add-on. Whether it replaces or sits alongside an existing system depends on your architecture — this is one of the first things covered in technical evaluation.
What happens if we need to leave?
Every balance is derived from the entries, and every entry is exportable. Because balances are never stored independently of the entries that produce them, there is no proprietary snapshot format standing between your data and your next system.
Have a question that isn't answered here?
Request Documentation →