Your bookkeeping, your accounting and your ERP are connected once in the gateway. After that finance asks in its own words, and no agent can approve anything on its own.
One account is fine for one person. The difference shows up when a whole team uses AI, and when somebody asks what it cost or where the data went.
Everyone signs up separately. Nobody knows what it costs, who has access, or what has been shared.
One way in to every model. One login, one invoice, and you can see what is actually happening.
Claude today, something else next year. With Walma you use all of them and switch when it suits you, without redoing the work.
We have done the groundwork: ready-made connections to the tools you already use, with proven skills and instructions, so the team actually gets going instead of just trying it out.
If you want visibility, you get it: everything the agent does is visible, you get feedback on how the work could be better, and you can put a stop to things it should not do.
Walma AI Hub is a layer between your tools and the models. Here is what that means in practice.
IT approves an MCP server once. After that the tool appears for the people who should have it, with the right permissions. Nobody on the team touches an API key.
NetSuiteofficial
SpirisbetaClaude, GPT, Gemini and the open models all reach the same connections. You pick the model per task instead of locking yourself in, and if you switch next year the tools come along.
When the off-the-shelf tools run out, we build. RAG over your own material, bespoke agent flows, and narrow MCP servers for systems the vendor has not covered, all running inside the same gateway and the same log.
Finance systems are where the Nordic vendors lag behind. For Fortnox and Visma we build the connection ourselves, and we say so plainly rather than letting it look finished.
The vendor's own server. Switched on and running the same day.
NetSuiteofficialSpirisbetaCommunity-built. We review the tool descriptions and pin the version before approving.
Fortnoxcommunity
Visma eEkonomicommunityVisma e-conomiccommunity
Business CentralcommunityThese we build ourselves, as narrow read-only servers in your tenant. Tell us which you need first.
Pleoin progress
Rampin progress
Brexin progressIncluded in every rollout.
Questions finance already asks, minus building a pivot table first.
The gateway runs in your own Azure tenant in an EU region. Every call is logged with user, tool and arguments. That is the answer when your data protection officer asks where the data goes.
Built for European requirements from day one. Details, subprocessors and policies live in our Trust Center.
Open the Trust CenterNot on its own, and not with us by default. Connections are set read-only, so the agent analyses, reconciles and prepares the basis but posts nothing. If something is to be written back we require human approval per action, and the approval lands in the log. A mistake in the finance system costs real money, so that is the right order.
The wrong question to lock yourself into, in our view. The models trade places a couple of times a year, and the one best at reading an invoice is not necessarily best at summarising a year-end close. With Walma you connect the systems once and then run Claude, GPT or Gemini against the same data, so you can switch when something better arrives without redoing the integration work.
Stripe, Xero and NetSuite have official servers. Spiris has one in beta, one company at a time. SAP and Business Central go through third parties and need review. For QuickBooks, Pleo, Ramp and Brex we build the connection ourselves.
The agent pulls from the source instead of guessing. You ask about overdue invoices, variances against budget or the basis for accruals, and it runs the query against the system and answers with rows it has actually read. Every call is logged with the question asked and what came back, so the answer is traceable the way an audit trail is. That is the difference from pasting an export into a chat.
The gateway runs in your own Azure tenant in an EU region, so prompts, arguments and logs are processed there. If a vendor's server sits outside the EU we tell you before you approve the connection.
Twenty minutes with an engineer. We connect one of your real systems, read-only, and show what finance can ask the next day.