ERP Has Its Finger on the Payment Trigger: After Odoo Moves "Initiate Payment" into the System, Who Will Be the One to Confirm?

Today is Saturday, November 21, 2026. This week, there was a piece of news in the enterprise software field that was not particularly loud but carried considerable weight: On November 17, Odoo's official blog announced that its partnership with the open banking platform Salt Edge has expanded from "reading bank data" to "directly initiating payments," making Odoo the first customer to go live with Salt Edge's Bulk Payments feature.

What matters here is not that the feature list has gained a line, but that the boundary between ERP and the bank has been shifted. In the past, ERP was a "system of record"—recording after the fact whom you paid and how much; now it is reaching out to become a "system of execution"—paying the money out directly. Once a line is crossed, the old ledger of permissions, approvals, and audits has to be recalculated.

2021 → 2026

It took Odoo and Salt Edge about 5 years to go from a bank data aggregation partnership to payment initiation

I. From 'Seeing' to 'Moving Money': The Line ERP Crossed

Let's first set the facts straight. According to an announcement on the official Odoo blog dated November 17, 2026, the cooperation between the two companies began in 2021, when Salt Edge's Data Aggregation service helped Odoo connect bank data into its accounting platform, and what users could do was 'view transactions and match invoices.' What is being added this time is two capabilities:

  • Pay by Bank (bank direct payment): Initiate and confirm payment for a single invoice in Odoo, completed through a direct bank connection, without needing to switch to the online banking interface.
  • Bulk Payments (Batch Payments): Initiate multiple transactions with a single authentication, allowing the finance team to approve a batch of supplier payments at once instead of clicking one by one.

The announcement particularly emphasized that neither feature requires exporting payment files from Odoo anymore, nor re-entering payment information in the bank interface. According to Olivier Maessen, Odoo Product Lead, this enables "a direct connection between the Odoo platform and banks, eliminating file uploads and manual entry." Vladimir Modirchi, Product Manager at Salt Edge, called it a signal of "embedded finance entering ERP and accounting platforms."

Coverage is another point worth noting: with this launch, Salt Edge expanded Bulk Payments from Italy to the broader EU and the UK. And Salt Edge's own foundation is — the PSD2 open banking platform, ISO 27001 certification, an AISP license under PSD2, and connections to more than 5,000 financial institutions in over 50 countries (all from the vendor introduction on Odoo's official blog).

The endpoint of embedded finance is to turn "payment" from a cross-system procedure back into an action within a business process. But fewer procedures do not mean less responsibility—it only shifts responsibility from the "operational stage" to the "authorization stage".

Pastnow
Reconcile in Odoo → Export payment file → Log in to online banking → Re-enter → Return to the platform for write-offSelect invoices in Odoo → authenticate once → initiate payments in batches → write status back to the platform

II. The efficiency is real, and the "authorization" that has been compressed away is also real

Authenticate once and approve a batch—for businesses with large numbers of suppliers, fixed monthly payments, or payroll runs, the efficiency gains are real. The problem lies precisely in the four words "authenticate once."

Paying one transaction at a time in the past was essentially setting a manual gate for each sum of money: each click on confirm was an authorization. Now this gate has been condensed into a single instant—a batch of payments is released simultaneously under one authentication. The arithmetic of efficiency improvement is simple, but risk exposure is not simply additive: if even one recipient account information entry in a batch is wrong, or one amount is entered incorrectly, the impact is no longer on one payment but on the entire batch.

The most concealed risk of batch authorization is not "paying the wrong party," but "paying a vendor who has changed their account." A change of receiving account should be the highest-level review item; once the batch process sends it into "one-time authentication" together with dozens of normal payments, this highest-risk action is drowned among a batch of ordinary actions.

It is worth noting that around the release of this announcement, the industry is forming a clearer consensus on “which actions should be decided by humans.” The November 2026 issue of ERP News (Issue 65, themed “When AI Acts”) put “who has the final say” on its cover: in the article, Vijay Vidiyala, head of product and technology at PairSoft, stated clearly that agents can use ERP records to investigate invoice anomalies and prepare payment batches, but actions such as payment release and changes to supplier bank accounts must be authorized by humans. In the same period, the French National Cybersecurity Agency (ANSSI) proposed seven principles for protecting AI agents, one of which is to clearly define: which actions agents can perform autonomously, which must be approved by humans, and which should be directly prohibited.

Putting these together, the direction is clear: whether this time Odoo initiates the payment itself, or in the future an agent initiates the payment within the ERP, "initiating" and "approving" must be two actions that can be audited separately, and must not be blurred together by a "single authentication."

Action TypeConsequence reversibilityRecommended authorization level
Initiate reconciliation and retrieve bank statementsRead-only, reversibleAutomatic by the system; just leave a record.
Prepare payment batches and generate draftsNot executed, reversibleAgent/System can autonomously
Allow small payments and payments to fixed payeesDifficult to reverse; payment recovery requiredAutomatic within batch and within threshold + post-event sampling inspection
Release entire batch payment / Change supplier bank accountHigh-risk, easily drowned out in bulkMust be manually reviewed transaction by transaction + dual sign-off

III. Once ERP Takes Hold of the Trigger, the Three Lines the CIO Must Redraw

For companies that have already enabled or plan to enable this type of direct-connect payment, the following three points are not bonus factors in vendor selection, but bottom lines that must be clearly drawn before go-live.

First, the permission boundary: treat "initiate payment" as an independent high-risk permission point. Do not simply continue using the original accountant role because it sits within the finance module. The three permissions of initiating, approving, and maintaining bank accounts must be held by different people; no single person should hold any two of them at the same time—this is the minimum requirement of segregation of duties, and batch payments only make the cost of violating it greater.

Second, the status line: model "submitted", "confirmed", "settled", and "returned" separately. Direct payment connections return a bunch of asynchronous statuses; within a single batch, some may succeed and some may fail. If ERP has only one "paid" checkbox, finance will mistakenly treat it as settled before the bank result comes back. This is the same type of problem as cross-border tax filing interfaces: deterministic failures can be retried, but unconfirmed statuses must be queried first and cannot be assumed to be success or failure.

The status trap of batch payments: "The bank has accepted it" ≠ "the money has arrived in the counterparty's account" ≠ "the counterparty has posted and cleared it." In a batch, as long as one payment remains in "unconfirmed," reconciliation of the entire batch cannot be considered complete. In the financial system, "unconfirmed" must be given a separate status, along with a fallback path for inquiry/reconciliation.

Article 3, the audit trail: enable call logs, business documents, and approval records to mutually identify one another. Once payments can be initiated directly from the ERP, the questions raised in an audit become: who initiated this batch, who approved it, at what time, based on which invoice, and through which bank account. The timestamps and operators in the three records must match, and the retention period must be consistent with that of accounting archives. Without this chain, “one certification approves a batch” is a muddled account in the face of an audit.


Final thoughts: Three practical recommendations for CIOs

1. Before going live, run a "batch failure" drill first. Simulate three scenarios in a batch of payments: a single payment fails, the receiving account changes, and the bank status is returned late, to see whether the system can correctly mark it as "unconfirmed" and prevent the entire batch from being mistakenly judged as completed.

2. Set up a two-tier gate for batch payments. One tier sets thresholds based on amount, number of transactions, and payee whitelist; batch processing is allowed within the thresholds. The other tier requires mandatory per-transaction dual signatures for account changes, new payees, and payments exceeding thresholds, and these must not be allowed to be swallowed by batch processing.

3. Build separation of duties into system permissions, not just into policy. Physically isolate the three permissions of initiation, approval, and account maintenance in the system, and regularly run an unauthorized-access test using real roles to confirm that the policy does not remain on paper.

ERP holding the payment trigger is a step forward in efficiency and also a stress test for governance. What truly sets organizations apart is not who connects to the bank first, but who, after connecting, can still clearly explain who released each payment, when, and on what basis. Only when this question can be answered can the payment trigger be handed over.

Data and citation sources for this article: Odoo's official blog "Odoo expands partnership with Salt Edge and is the first to go live with Bulk Payments" (2026-11-17); ERP News Magazine Issue 65 "When AI Acts" (November 2026 issue, including the Vijay Vidiyala interview and ANSSI's seven principles). The functional coverage, certifications, and number of institutions mentioned in this article all reflect the vendor's public statements; before implementation, please refer to local bank and compliance requirements.

Zhongdi Information · Enterprise Digitalization Observer | Focusing on open-source software, ERP, and intelligent management

关于我们

​我们致力于帮助中小企业实现数字化转型,我们的团队由一群充满激情和创新思维的专业人士组成,他们具备丰富的行业经验和技术专长。

扫一扫获取顾问以及手册

Sign in to leave a comment
After AI scrubbed away the provenance, an open-source project switched its license from MIT to GPL