A bank connection that reads balances does not necessarily let you send payments. And a payment instruction that has been approved internally is not necessarily accepted by the bank. Design the treasury stack around those boundaries before selecting a provider.
Three capabilities, four distinct records
| Capability | Record to retain | Critical boundary |
|---|---|---|
| Bank reporting | Account, balance type, currency and observation time | Read access must not grant payment authority |
| Payment preparation | Batch and instruction IDs, source obligation and approved version | Preparing a batch must not release it |
| Authorised release | Who approved or released the exact version, when and under which entitlement | A changed instruction needs the required fresh review |
| Reconciliation | Bank response and eventual settlement or rejection | Submitted is not settled; retries must not duplicate payment |
The accounting or AP system can originate the obligation while the treasury system coordinates approval and dispatch. The bank remains the authority for what it accepted or settled. Keep a link between the original obligation, prepared instruction and bank reference so a reviewer can reconcile a partial rejection without looking at a screen recording.
Compare the shape of the stack
Trovata: API-linked payment workflows where the connection supports them. Its Payments Guide lists supported connections and payment types and distinguishes initiator, reviewer, approver and releaser permissions. Use it to evaluate an API-based path. Require confirmation for each bank, account and rail, not just a claim that a bank is connected. Demonstrate the difference between approval, submission and the response from the bank.
Kyriba: evaluate a central payment hub for multiple routes. Kyriba’s payments materials describe centralised ERP-to-bank connectivity and approval workflows. Consider this architecture if separate entity and bank paths are difficult to govern consistently. Ask to see one direct bank connection and one materially different route. Confirm what evidence survives any file conversion and who manages rejected items.
J.P. Morgan Access: consider keeping release in the bank channel. Access product material describes payment controls and user entitlements. A bank-native release path can be the smaller stack when most payments already go through that channel. Validate which preparation steps stay upstream and which controls the bank actually enforces for your account and permissions. Do not infer that an internal approval automatically meets a bank release requirement.
Run a non-production reconciliation drill
Create a batch containing three synthetic instructions. Change one after review, have the test bank or simulator reject another, and replay the transmission response. Show which record invalidates the earlier approval, which instructions may be retried, and how duplicate transmission is prevented. Simulate an unavailable bank connection and identify the authorised fallback and the records it must produce.
Compare quotes using the same scope: entities, account connections, payment rails, expected volume, bank fees, entitlement administration and fallback support. Choose bank-native release when it is sufficient. Add a hub when consolidating preparation and policy materially reduces operational exceptions without hiding the bank’s response.
Related: systems of record and integration reconciliation ownership.