Your AI assistant, connected to the Banking Orchestrator
Ask about payments, balances and approvals in plain language. Your rights and signatory rules still apply.
Same platform, same controls
Direct
A request reads from or acts on the platform directly, without opening the portal. The assistant calls the Orchestrator's tools and gets structured results back.
Under your rights
The MCP endpoint does not introduce a separate permission model. Every tool call runs under the rights of the connected user, so the assistant can only do what that user is allowed to do.
Under your approvals
Signatory rules and four-eyes approvals still apply to everything the assistant initiates.
What the assistant can do
Read
Balances and bank statements. Payments with their status: who has signed, who still needs to, and by when. Counterparties with their approval status and risk level.
Act
Prepare payments and direct debits, one by one or in bulk. Add or update counterparties. Your signatory rules and four-eyes approvals still apply.
See it at work
Start with the overview, then pick one of three short examples.
Results may vary by assistant. Not affiliated with Anthropic, OpenAI or Mistral AI.
Access, signatures and audit trail
“Nothing runs anonymously and nothing sits outside the platform's controls.”
- Sign-inEvery connection starts with a real user signing in to FinologeeBKO.
- RightsThe assistant can only do what that user is allowed to do. If that user can only read, so can the assistant.
- SignaturesThe assistant has no signing function. Payments it prepares follow your signatory rules.
- Audit trailEvery change is recorded in the audit trail, under the user's name.
Before a colleague connects an assistant, check their rights in FinologeeBKO: the assistant gets exactly those.
Where your data goes
FinologeeBKO runs in Luxembourg
FinologeeBKO is hosted in Luxembourg by EBRC, part of the POST Luxembourg group, in Tier IV-certified data centres. What your assistant reads also goes to your AI provider.
Your provider agreement applies
Your AI provider processes what the assistant reads, under your agreement with it. If professional secrecy or outsourcing rules apply to you, check the agreement against them.
Bring your own assistant
Use the AI assistant and plan you already have. Finologee provides the connection between it and FinologeeBKO.
Connect your AI assistant
FinologeeBKO connects through MCP, an open standard that links AI assistants to business software.
- Ask Finologee support to switch on the connection and send you the details.
- Add FinologeeBKO as a custom connector in your assistant.
- Sign in with your usual FinologeeBKO login.
Step-by-step guides for each assistant are in the documentation.
Common questions
Does the assistant have its own permissions?
No. Everything it does runs under the rights of the user who connected it, so it can only do what that user is allowed to do.
Can it release a payment on its own?
No. It cannot sign, so a payment it prepares follows your signatory rules.
Can the assistant read our emails and files?
Only what you give it: files you attach, or apps you connect it to yourself. FinologeeBKO does not see your emails or files.
Is our data used to train AI models?
Finologee does not. For your AI provider, it depends on your plan and your agreement with it.
What is covered today?
About 40 actions across payments, direct debits, accounts and counterparties.
Which assistants can we use?
Claude, ChatGPT, Mistral Vibe and agents built in Microsoft Copilot Studio. With ChatGPT and Mistral Vibe, your plan must allow custom connectors. Others on request.
How do we get started?
If you already use FinologeeBKO, ask Finologee support to switch on the connection. If not, book a demo.
Claude is a trademark of Anthropic, ChatGPT of OpenAI, Mistral Vibe of Mistral AI and Copilot Studio of Microsoft.
Do you want to know what we could build together?
Or get a product demo? Get in touch and we will evaluate how we may help you.