ERP Bank Integration Sri Lanka: H2H, Statements, and Cash You Can Trust

Many Sri Lankan businesses assume cash is under control because the internet banking balance looks healthy. That number is a snapshot of cleared funds—not of invoices paid, supplier runs committed, MDR still to deduct, or deposits that have not yet matched to customers. Finance still spends evenings in Excel because banking activity and ERP truth are two different movies.

ERP bank integration closes that gap. It is not a “nice IT project.” It is how you shorten cash blind spots, stop dual entry, and make month-end close something you manage—not something you survive.

What breaks in daily operations

• Customers pay without usable invoice references; cashiers and collectors guess.
• LankaQR / CEFTS / card settlements arrive as net batches while POS shows gross sales.
• Supplier and payroll runs are typed twice—once in ERP, again in the bank portal.
• Bank fees, partial payments, and multi-invoice receipts sit in an exception pile nobody owns.
• Treasury sees yesterday’s truth; decisions get made on stale cash.

Three integration levels (pick the one you can operate)

1. Statement-led reconciliation

Import MT940-style / CSV / PDF-derived statements into ERP and match by amount, date, and reference. Lowest technical bar. Works only if payment descriptions and invoice numbers are disciplined. Good starting point for single-entity SMEs.

2. Payment initiation + status feedback

Approved AP and payroll runs leave ERP as structured payment instructions; the bank returns status (accepted, rejected, settled). Removes the second typing pass. Requires clear maker-checker rules inside ERP so finance, not IT, owns the workflow.

3. Host-to-Host (H2H)

A dedicated secure channel between your ERP estate and the bank for high-volume bulk files, automated statement retrieval, account inquiry, and reconciliation loops—without staff jumping between banking apps. Sri Lankan banks have launched and partnered on H2H specifically to cut manual uploads and dual systems. Treat H2H as architecture plus process ownership, not only a file drop.

Design rules that prevent expensive rework

1. Keep a bank-agnostic payment object in ERP (intent → rail → status). Do not mirror one bank’s schema into your ledger.
2. Enforce invoice / customer references at the payment edge (QR, portal, remittance advice)—automation cannot invent missing discipline.
3. Use idempotent payment IDs so retries do not double-pay.
4. Prefer event-driven status (callbacks/files) over endless portal polling.
5. Separate exception queues by type: missing ref, amount variance, fee, FX, duplicate—so SLAs are meaningful.
6. Measure straight-through processing (STP) rate and time-to-match—not only “integration went live.”

Sri Lanka rails to plan for

Your integration map should name the real channels your customers and suppliers use—not a generic “digital” bucket. Typical mid-market mixes include CEFTS realtime transfers, SLIPS bulk credits, LankaQR and JustPay at retail edges, card acquiring, and classic cheque / PDC operating habits. See also LankaQR, JustPay, and ERP for retailers.

30-day readiness plan

1. Week 1: Inventory bank accounts, payment methods, volume, current portal steps, and who owns exceptions.
2. Week 2: Standardize references and tender/method codes in POS, invoicing, and ERP.
3. Week 3: Pilot statement matching for one entity or branch; log unmatched causes.
4. Week 4: Scope H2H or payment API with your bank + ERP partner; define maker-checker and rollback tests.

Where Capricon fits

Use Capricon Core ERP as the system of record for invoices, stock, and finance. Add Capricon Pay when collections and multi-channel settlement visibility matter. Need bank-specific adapters, multi-entity payment factories, or H2H glue that products do not ship? That is custom software development in Sri Lanka—with software AMC after go-live.

If the only dashboard your board trusts is the banking app, you do not yet have a cash position—you have a balance. Start with Capricon’s cash & VAT readiness audit, then see the retail ERP cash case study.