Embat Unifies Treasury Operations with New Global Banking Infrastructure

The Spanish fintech's "Global Banking" offering lets mid-market companies open local IBANs in 22 jurisdictions through a fully digital KYC process, with transactions written back to enterprise resource planning systems automatically.

What the product actually does

The architecture consolidates four functions that have historically required separate vendors: cash management, international payments and collections, FX hedging across more than 60 currencies, and ledger reconciliation. Account opening is positioned as a days-long process rather than the weeks typical of correspondent banking relationships. ERP integration is handled at the transaction layer, eliminating the manual posting cycle that finance teams currently rely on for multi-currency operations.

The product runs on Embat's existing AI infrastructure, including its agentic assistant TellMe. The stated purpose is operational acceleration, though the underlying capability is structurally closer to embedded banking infrastructure than to software tooling.

Structural positioning

Embat's move follows a pattern already visible across treasury and finance automation providers: a shift from selling software that sits on top of banking rails to operating rails directly. By combining account opening, payments, FX, and reconciliation inside one stack, the company positions itself closer to the movement of funds rather than to the management of financial data around those funds.

Álvaro Dexeus, Director of Global Banking, framed the launch around persistent friction in European treasury operations, noting that structural problems persist even for large multinationals. The product targets mid-market companies with cross-border operations — a segment underserved by traditional correspondent networks and underserved by consumer-grade neobanks.

What to watch

The architecture assumes that a single regulated entity can hold IBANs across 22 jurisdictions. The banking licenses, partner banks, or passported arrangements underpinning that footprint are not disclosed in the announcement. For finance teams evaluating the product, the practical questions are standard but unresolved: where accounts are actually held, how client funds are safeguarded under each local regime, and what happens to reconciliation when a partner bank changes its API contract. Treasury automation built on someone else's license inherits that license's risk profile.