Designed scope
- bank statement import
- matching rules
- an exception queue
In development · request access
R&D COPILOT Banking
Matches get proposed automatically, but nothing disappears from view — exceptions stay in plain sight.
01 / Workflow
From intent to a verifiable trail
The statement gets imported, rules propose matches, and the operator confirms or explains every difference before reconciliation closes.
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
- Confirming the actual banks involved, and their export formats, is the next step.
- An agreement with a bank-connectivity provider is still to be secured.
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.
- Bank feeds
- Accounting API
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.