Choose an SME and corporate banking platform by testing one thing before anything else: whether it can model your most complex client as an organisation, with its legal entities, users, limits and approval rules, without custom code. Then check that payments, files, trade finance, lending and ERP connectivity all obey that same model, and that your own teams can change it. Feature lists come last, because most shortlisted vendors will tick the same boxes.
This guide is for banks selecting a business banking channel: a corporate internet banking solution, an SME app, a cash management portal, or one platform for all three. It sets out how business banking differs from retail, the capability checklist, the evidence to request, a scoring grid, the demo scenarios to script and the red flags that should end a conversation.
How is business banking different from retail banking?
In retail banking the customer is a person: one identity, one login, one set of accounts. In business banking the client is an organisation. The people who log in are employees or owners acting on its behalf, each allowed to see and do different things, and the organisation keeps changing: staff join and leave, entities are added, signing authority moves.
That one difference drives everything else. A payment is not simply sent: it is initiated by one person, approved by others and released under limits. Onboarding is not the verification of one individual: it is the verification of a company, its signatories and its owners. Servicing involves a relationship manager and an operations team as well as the client. A platform designed around a single login can imitate all of this on the surface, and the gaps appear with the first complex client you migrate.
SME, mid-market or large corporate: one platform or two?
The three segments want different things from the same bank. The table below is a simplification, but it shows why a single fixed design rarely fits all of them.
There are two defensible answers. One platform with a shared organisation and entitlement engine, presented simply to an SME and in full to a group treasury, gives you one integration layer, one security model and a path for clients to grow without migrating. Two platforms can be justified when the SME proposition is a distinct mobile product with its own brand and pace. What is hard to defend is two platforms by accident: a retail app stretched upwards and a corporate portal stretched downwards, with mid-market clients badly served by both. Decide deliberately, and write the decision into the RFP.
| Segment | Typical structure | Main channel | What matters most |
|---|---|---|---|
| SME | One entity, a few users | Mobile first | Fast onboarding, simple approvals, invoicing, payroll |
| Mid-market | Several entities, a finance team | Web and mobile | Approval matrices, bulk files, accounting integration |
| Large corporate | Group with subsidiaries | Web, host-to-host, APIs | Liquidity views, trade finance, ERP connectivity |
What should an SME and corporate banking platform include?
Use this checklist to define scope, and mark each line as needed at launch, needed later or not needed. Then ask every vendor which lines are live in production today, which are configuration and which are roadmap.
- Business onboarding and KYB: company registry data, documents, signatories and ultimate beneficial owners captured as structured data. The FATF guidance on beneficial ownership of legal persons (Recommendation 24) is the international reference your compliance team will work from.
- Organisation modelling: groups, legal entities, subsidiaries, departments and users, with each user scoped to the parts of the organisation they work in.
- Entitlements and approvals: roles, limits per user and per account, maker-checker, and approval matrices by product, amount and entity.
- Payments: single and bulk payments, payroll and salary files, local instant rails, cross-border transfers and ISO 20022 messaging.
- Cash and liquidity: balances and positions across accounts, currencies and entities, with statements and reports the client can export.
- Trade finance: letters of credit and guarantees, with applications, amendments and document presentation online. ICC rules such as UCP 600 for documentary credits and URDG 758 for demand guarantees shape these journeys.
- Lending and credit facilities: applications, limits, drawdowns and repayment schedules.
- Cards and expense: corporate and virtual cards with limits and controls per cardholder.
- Connectivity: host-to-host file exchange and APIs into the client’s ERP and accounting systems.
- Invoicing and receivables for SMEs: invoices, payment requests, collection and reconciliation.
- Service requests: letters, statements, cheque books and payment recalls, tracked to completion.
- Audit trail: every view, initiation, approval, rejection and release, timestamped and attributed, for the client and for the bank.
How do you test the entitlement and approval model?
This is the criterion that separates business banking platforms, and it cannot be judged from a slide. Take your most complex real client structure, anonymise it and give it to each vendor as a test case: a holding company, several subsidiaries in different countries, shared service staff who act for more than one entity, and a board resolution that says who may sign what.
Then ask to see it configured, not described. Can a rule require any two of five signatories below a threshold and a named director above it? Can limits apply per user, per account, per day and per transaction at the same time? Can an approver delegate during leave, with an expiry date? Who can change the rules: the client’s administrator, the bank, or only the vendor? What happens to payments already in the queue when a rule changes or a signatory leaves? Each answer should be demonstrated on screen and be visible afterwards in the audit trail.
What evidence should you request on payments, integration and security?
On payments, ask for the file formats and message standards supported in production, and test with your clients’ real files. ISO 20022 is the ISO standard for financial messaging, and the CPMI at the Bank for International Settlements has published harmonised ISO 20022 data requirements for cross-border payments that it encourages the market to align with by end-2027 at the latest, so a platform limited to legacy formats will age quickly. Payroll deserves its own test, because it is tied to national systems. In the UAE, the government portal states that establishments registered with the Ministry of Human Resources and Emiratisation must pay wages through the Wage Protection System, via banks, exchange houses or financial institutions authorised by the central bank. In Saudi Arabia, the Ministry of Human Resources and Social Development directs establishments to submit their wage files through the Mudad platform. Ask to see a salary file validated, approved and reconciled for your market.
On integration, request the API documentation and a sandbox before the contract, not after. Ask how a client’s ERP sends a payment file and receives statements and status reports without anyone logging in, and how that channel is authenticated. Where open banking applies, ask how business accounts are handled: SAMA’s Open Banking Framework, for example, was issued first for account information services, with payment initiation named as the focus of the second release, and a business client’s consent may need more than one signatory.
On security, look for strong authentication at login, transaction signing bound to the payment details, and controls built for bulk payments: beneficiary whitelists, file integrity checks, duplicate detection, a second approval when a beneficiary’s account details change, and alerts on unusual files. Ask for the latest independent penetration test summary, and for the procedure when a client administrator’s credentials are compromised.
How should you score the vendors?
Agree the weights before the first demo, so the scoring cannot bend towards the most polished presenter. The weights below are a starting rule of thumb, not data: a bank focused on SMEs would move weight from trade finance and host-to-host connectivity to onboarding and mobile.
Score evidence, not promises. A capability shown working on your scenario earns full marks, a capability shown on the vendor’s own data earns part, and a roadmap item earns none.
| Criterion | Suggested weight | Evidence to request |
|---|---|---|
| Organisation and entitlement model | 25% | Your most complex client, configured live |
| Payments, files and messaging | 20% | Your real files processed in a sandbox |
| Integration with the core and client ERPs | 15% | API documentation, sandbox, reference architecture |
| Security and fraud controls | 15% | Signing flow, bulk payment controls, test reports |
| Configurability by bank teams | 10% | A rule and a journey changed during the demo |
| Relationship manager and operations tooling | 10% | Bank-side console and work queues |
| Segment fit and roadmap | 5% | SME and corporate views, a dated roadmap |
Which demo scenarios should you script?
Send every vendor the same script two weeks ahead and hold them to it. Six scenarios cover most of the risk.
- Onboard a company with two layers of ownership, capture its beneficial owners and signatories, and show the case as the bank’s compliance officer sees it.
- Build the group: three entities, ten users, a shared finance team and an approval matrix with two thresholds. Change one rule and show the audit record.
- Upload a payroll file containing two deliberate errors and a duplicate. Show validation, correction, approval by two people on mobile and the final status report.
- Send a cross-border payment from a subsidiary, approved at group level, and show the message that reaches your payment system.
- Apply for an import letter of credit, amend it, and show the bank-side queue and the client’s view of deadlines.
- Remove a signatory who has payments awaiting approval, then show what happens to those payments.
What are the red flags?
Some findings should lower a score. These should make you stop and ask whether the vendor belongs on the shortlist at all.
- A retail platform with a business skin: the client is still a single login, and extra users are bolted on as sub-users without their own identity, limits or audit trail.
- Approval flows that are hard-coded, capped at a fixed number of levels, or changeable only by the vendor through a change request.
- Entities modelled as separate clients, so a group cannot see or move cash across them.
- Bulk payments approved as a total, with no way for the approver to inspect the individual lines.
- No bank-side console: relationship managers and operations cannot see what the client sees or act for the client under control.
- Reference clients that all sit in one segment when you intend to serve another.
How Eurisko fits
Eurisko’s corporate and SME banking platform is built on Eurisko DXP and runs in front of any core. It models groups, legal entities, subsidiaries, departments and cost centres, scopes each user to the parts of the organisation they work in, and routes transactions through approval policies by product, type and amount, with steps that need any one approver, all of them or a quorum. Payments and payroll, trade finance, lending, treasury, cards, receivables and service requests follow the same model, and bank teams configure journeys, products and rules without code and publish them without an app release. Eurisko has delivered banking software since 2009 with a team of more than 200 engineers, and our ISO 27001 certification is in progress.
We are not the right choice if what you need is a core banking ledger, a payments hub or a trade finance back-office system: our platform is the channel and orchestration layer in front of those systems, not a replacement for them. If the criteria above match your shortlist, we are glad to run your scripted scenarios with your own client structure.