Integrations built in your pilot.
FinanceAI reads from the core banking, ERP, and file feeds you already use. Connectors are designed with your security team — read-only first, documented sync, write-back only on approval.
Read from core banking and ERP
Scheduled BAI2, MT940, CAMT.053, and GL extracts land with checksum validation. APIs are added when security review allows least-privilege scopes.
Agents decide with evidence
Reconciliation, KYC, and Close agents run rules first and cite real IDs — WIRE-88213, account 1010, UBO percentages — in every trace step.
Write back on approval
Journal proposals and disposition updates post to your systems only after a human approves. Each write is logged next to the agent trace.
Systems we commonly connect
Listed for planning conversations — your pilot scope may differ.
Core banking
- Temenos Transact
GL extracts, customer master, payment references
- FIS (Horizon / IBS)
DDA balances, transaction history, wire refs
- Fiserv (DNA / Premier)
Account and transaction feeds for recon
- Finastra (Fusion)
Cash management and GL bridge files
- Jack Henry (Symitar / SilverLake)
Share draft and loan payment detail
ERP / GL
- SAP S/4HANA
Cash subledger, AP/AR clearing, intercompany
- Oracle Fusion Financials
Bank statement reconciliation interfaces
- NetSuite
Multi-entity cash and close checklists
- Workday Financials
Bank reconciliation and journal proposals
- Microsoft Dynamics 365
Bank account and payment journal detail
Bank files & SFTP
- BAI2
Previous-day and intraday operating account files
- MT940 / MT942
SWIFT statement and intraday advice
- ISO 20022 CAMT.053
Structured end-to-end payment references
- CSV / vendor-specific exports
Mapped during pilot to your field dictionary
- SFTP drop zones
Scheduled ingest with checksum and replay
KYC data
- KYC / screening providers
Screening APIs and adverse media on request — built per pilot
Security defaults
- Read-only scopes by default; write paths enabled only for approved actions.
- Credentials live in your secret manager — not in application source.
- Workers can run in your cloud or VPC; residency follows your banking and ERP regions.
- Connectors are built during your pilot — not implied certified partnerships.
Questions
Which systems do you connect to?
Commonly Temenos, FIS, Fiserv, Finastra, Jack Henry, SAP, Oracle, NetSuite, Workday, Dynamics, plus BAI2/MT940/CAMT.053 and SFTP. KYC data providers are scoped per pilot. The exact list is documented in your pilot plan.
How long does a connector take?
A read-only bank file and GL export feed often takes two to four weeks once sandbox access and security review are in place. Write-back and multiple entities add time we estimate up front.
What is read vs write?
Read covers bank files, GL detail, and onboarding documents agents need to decide. Write is limited to approved journals or status updates — never bulk posting without a human gate.
Can we stay file-based?
Yes. Many banks and credit unions run pilots on SFTP drops only before APIs are approved.
Do you certify integrations?
No. We build and test connectors with your team during the pilot; we do not claim vendor-certified partnerships on this page.