Designed scope
- journals and accounting periods
- financial reporting and reconciliation
- isolation by legal entity
In development · request access
R&D COPILOT Accounting
One statutory ledger — and every figure in it can be traced back to the document that produced it.
01 / Workflow
From intent to a verifiable trail
Operational facts arrive as immutable requests; accounting applies the relevant policy and posts or reverses them — it never rewrites them.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
Capabilities and boundaries
On the roadmap
- Validating the Odoo/OCA localization for Romania on one single major version is the next step.
- An accountant's sign-off on FIFO/CMP/LIFO and the ANAF/MF reports comes next.
03 / API
Controlled integrations
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
- ERP
- Inventory API
- Banking
04 / Docs
Public integration notes
Working contract
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
Access and availability
Validating the application entry point — origin, path, license, and release evidence — is the next milestone before the /app route goes live.
Price and inclusions
Pricing and commercial terms are being worked out; there is no published price or checkout yet. Reach out for where things currently stand.
05 / FAQ
Factual answers
Is the product available now?
Not yet — it's in development. Reach out and we'll tell you exactly where things stand and how to get early access.
Can I purchase online?
Not yet — there's no self-serve checkout while pricing and terms are being finalized.
What does this page prove?
It describes what's designed and what's still ahead — not a claim that this is production-ready or certified today.