The group whose consolidated treasury we described earlier moved on to payment approval once its banks and accounts had been brought together on a single platform. Its structure is the one described then: a holding company, a sub-holding that runs finance centrally and between ten and twenty operating companies, which change with each acquisition. Before the project, payments spread across some sixty bank accounts were created in the ERP and ended up being keyed into online banking by hand. The payment batch file was downloaded and uploaded again bank by bank, and each portal needed its own authorisation flow. When management wanted to extend payment powers to new people, every name required a separate procedure at each bank. As a result, approval rules depended on different portals, and nobody had a single view of who could authorise what.
The same need arises in much smaller companies. In a distributor with seven employees, segregation of duties was already in place: one person entered the batch into the main bank’s portal, and the owner gave the final click from his phone. The status of each transfer, however, was tracked on a spreadsheet shared by four people, which changed colour once a payment was approved. Foreign currency payments, on another bank, were handled separately.
Who should approve a payment before it goes out?
One person proposes, a second approves and whoever holds the powers signs; above an amount threshold, approval goes through two successive levels.
In a treasury platform the path always follows the same order. Invoices come from the ERP, the accounts team chooses the account and builds the batch, approvers authorise it, signatories sign it and the batch goes to the bank. Each step is logged with the user and the time, and the payment status can be read in the same place where it started.
For the distributor, Aesir’s proposal was to move the batch and its approval onto the platform, with two approvers and a direct connection to the main bank. The shared spreadsheet becomes unnecessary, because the status of every transfer is visible to anyone with permission to see it.
Thresholds and levels in payment approval
Payment approval is set by the amount of the batch. Below a threshold one approver is enough; above it, the batch goes first to the finance manager and then to the managing director, and further levels can be added. For a supplier with particular rules, a dedicated batch is prepared with its own path.
Powers are defined by the platform administrator, and they do not coincide with those lodged with the bank. This helps when the circle of approvers has to grow: the rule is written once, for all connected banks. Payment limits are set per user, and visibility is granted company by company.
Approvers need two-factor authentication. In the configurations Aesir follows, the authenticator app is mandatory for all users, and approval requires a one-time code generated on the phone. Signatories alone also need a signing certificate, stored on their workstation and loaded at each signature.
Sixty accounts, four signatories and an indemnity with the main banks
In the group described above, signing was organised in groups: four authorised people, two of whom always sign. The analysis separated two decisions that until then had coincided, namely who approves an expense and who sends it to the bank using their own powers.
The configuration provides for amount thresholds, a one-time code for approvers and a signing certificate for signatories only. With the two main banks an indemnity letter was signed: batches authorised on the platform arrive already approved, with no second step in online banking. Before real payments are moved, a test transfer for a token amount is made to check that the flow reaches the bank signed.
On the first test, the batch arrived unsigned. The defect surfaced on a token amount, before any payment to a supplier, and real payments stay in online banking until the test reaches the bank signed.
Insight. Separating approval from signature made it possible to extend authorisation powers without touching the signatures lodged with the bank. With the indemnity, however, responsibility for deciding who approves passes to the company: the authority matrix has to be written and approved by management before it is configured on the platform.
What remains with the bank when payment approval moves to the platform?
The bank receives the batch: either the final signature stays in online banking under the powers lodged with the bank, or the bank accepts flows authorised on the platform under an indemnity.
For payment approval on the platform, the read-only connection provided by payment services legislation is not enough: it brings balances and transactions, but cannot initiate transfers. Making payments requires a direct channel with each bank, activated institution by institution. After sending, an “unconfirmed” status is normal, because the bank does not return a specific outcome. If the debit does not appear among the transactions within the transfer’s execution time, the check is made with the bank. Confirmation arrives with the transactions, which the platform matches against due items as described in the article on automated bank reconciliation.
Supplier bank details are the most exposed point
Changing a supplier’s IBAN is the operation most sought by anyone attempting payment fraud. On the platform, users without access to the payee master data cannot change their bank details. Every change triggers an alert to the administrator and flags the payee as to be verified, with the name of the person who made the change and the time. The safest rule remains to manage master data only in the ERP.
Since 9 October 2025 the European regulation on instant payments has required banks to check that the payee’s name matches the IBAN before authorisation. The outcome of that check, however, stays within the banking circuit and does not come back to the platform, so the internal control on master data keeps all its weight.
A bridge solution while the ERP is not yet connected
Integration between ERP and platform takes time, and payment approval can change earlier. The batch file produced by the ERP, in the standard banking format, is uploaded to the platform instead of online banking. Levels, thresholds and signatures apply from day one, and powers are extended without repeating the procedures at each bank.
Without the return flow, due items remain open in the ERP, and someone has to close them: the connection has to be planned together with the bridge, with a date. The group described at the start uses this bridge until the exchange with its own ERP becomes two-way. When the ERP is Business Experience the integration is native, thanks to Aesir’s Gold Partner status with NTS Informatica. With other ERPs the starting point is the existing connectors, and a dedicated one is developed where none exists. For that group, the same project also covered dedicated accounts and balance consolidation, discussed in the article on group treasury.
In treasury projects Aesir Srl handles bank connections and the configuration of authorisation powers within a single relationship. It works throughout Italy and, when clients request it, also in Switzerland, the United Kingdom and the United States. The platforms adopted process data in European Union data centres, with ISO/IEC 27001 family certifications and requirements consistent with NIS2. Aesir applies these criteria to its own infrastructure as well, which is certified ISO 9001, 27001, 27017 and 27018.
Card payments: limit, receipt and approval in the same flow
Card spending follows the same logic as transfers, with one extra step: the limit is set before the expense, and approval comes on the receipt. In a company working on construction sites, which requested around thirty physical cards for its staff, the configuration provides for three administrators, three managers and budgets per cost centre. Every expense is linked to the site. The employee photographs the receipt in the app and the manager approves; a new card or a higher limit goes through the administrator.
Above the set limit the transaction is declined, and employees cannot make transfers from the app. At activation, two practical details slowed down card delivery: some invitations blocked by email filters and a name on an identity document that differed from the one in the invitation.
In the group with sixty accounts, expense refunds still go through payroll, and the platform’s cards are being evaluated to replace them.
Payment approval, step by step
| Step | Who does it | Control | Where the trail stays |
|---|---|---|---|
| Batch proposal | Accounts team | Invoices from the ERP, account chosen | Treasury platform |
| Approval | Finance manager, then management above threshold | Amount threshold, one-time code | Platform, with user and time |
| Signature | Signatories with powers | Certificate, or signature in online banking | Platform or bank portal |
| Sending and confirmation | Bank | Payee verification and execution | Bank transactions and reconciliation |
| IBAN change | Whoever can access master data | Alert to administrator, payee to be verified | Payee history |
Before moving payment approval onto a platform, it is worth defining:
- who proposes, who approves and who signs, company by company;
- amount thresholds and the number of levels;
- which banks accept an indemnity and which keep the signature in online banking;
- who can change suppliers’ bank details;
- a procedure for a lost or expiring signing certificate;
- a test transfer, bank by bank, before real payments;
- the return flow of outcomes to the ERP, or the planned date for activating it.
Questions from finance managers
Can payment approval be given from a phone?
Yes, with the one-time code generated by the authenticator app. In the configurations activated so far, the certificate signature, where required, is completed from the workstation on which the certificate is installed.
What happens if the signing certificate is lost?
The certificate is generated again, and the signatory installs it on the workstation before the next batch. The renewal procedure is best written before go-live, together with the list of signatories.
Does the bank check the powers of those who approve on the platform?
With the indemnity, the bank accepts flows authorised on the platform, and the company defines the powers. Without an indemnity, the final signature stays in online banking, under the powers lodged with the bank.
Do the company cards already in use have to be replaced?
There is no need to replace them. How they enter the treasury view depends on the platform and on the issuing bank: in some configurations they connect as an extra account, in others their transactions are imported from the card statement. Cards issued by the platform add per-person limits, receipts in the app and budgets per cost centre.
Let’s talk
Payment approval becomes manageable when the company writes its own rules once and the bank receives batches that are already authorised. If you would like to explore the subject or assess the situation in your own company, you can fill in the form at the bottom of this page or write to support@aesir-tech.it: we will arrange a free consultation and start from your numbers.