LankaQR, JustPay, and ERP: How Sri Lankan Retailers Should Connect Payments to Accounting

Digital payments are accelerating across Sri Lanka, but many retailers still reconcile LankaQR and JustPay manually. Here is how to connect payments to POS, invoicing, and ERP—with official limits and sources.

Sri Lankan retailers are adopting LankaQR and JustPay faster than they are fixing the back office. Customers pay in seconds; finance teams still spend hours matching bank notifications, POS totals, and accounting entries. That gap becomes expensive when VAT e-invoicing, branch reporting, and audit requests require proof—not guesses.

The Central Bank of Sri Lanka (CBSL) has been actively promoting digital payments nationwide, including the Digital Payments Promotion Campaign 2025 under the theme “Shaping the Future through Digital Transactions,” launched in January 2025 with island-wide awareness events for merchants and MSMEs. At the same time, CBSL’s Payments Bulletin for the fourth quarter of 2025 shows LankaQR and JustPay growing as core retail rails on the Common Electronic Fund Transfer Switch (CEFTS). Retailers should treat payment adoption and ERP reconciliation as one project.

LankaQR and JustPay in plain language

LANKAQR is Sri Lanka’s national interoperable QR standard for local-currency payments and peer-to-peer transfers. CBSL first established the standard through Payment and Settlement Systems Circular No. 06 of 2018 and continues to update the specification—the January 2026 LANKAQR Specification V1.3 is issued under Circular No. 2 of 2026. LankaPay, the national payment network operator, enables banks and finance companies to onboard merchants and issue QR codes.

JustPay is a separate CEFTS-based mechanism that lets customers link bank accounts to participating mobile apps and pay or top up wallets in real time. It is not the same product as LankaQR, though both often appear together in a retailer’s digital payment mix. According to CBSL’s Q4 2025 Payments Bulletin, JustPay was launched by LankaPay in 2017 and remains one of the key retail payment channels alongside LankaQR, LPOPP, and GovPay.

LANKAQR: QR scan payments to merchants; static or dynamic codes; domestic apps and selected international wallets (including UPI, UnionPay International, and Alipay+ per CBSL).
JustPay: account-linked payments through approved mobile apps on CEFTS.
GovPay: government digital collections platform that evolved from the Government Digital Payment Platform (GDPP) pilot and was officially launched in February 2025.

Official limits and economics retailers should know

Before connecting payments to ERP, finance teams need the operational rules—not only the marketing brochure. CBSL’s Q4 2025 Payments Bulletin publishes the following reference limits and charges:

JustPay maximum per transaction: Rs. 50,000.
JustPay transactions above Rs. 10,000 require an OTP from the issuer bank (effective 1 April 2024, per Payment and Settlement Systems Circular No. 01 of 2024).
LANKAQR maximum per transaction: Rs. 500,000.
LANKAQR maximum merchant discount rate (MDR): 1% for domestically operated mobile payment apps; 1.8% for apps linked to international payment service providers.
LANKAQR merchants registered: about 460,990 by end of Q4 2025 (up 9.6% from the prior quarter, per CBSL/LankaPay data cited in the bulletin).

These limits affect checkout design, refund policy, and how supervisors approve high-value sales. They also affect ERP configuration: payment methods, fee accounts, and exception workflows should reflect real rails—not a generic “digital payment” bucket.

ERP dashboard for retail finance and payment reconciliation — Payment rails only create value in the business when sales, settlement, fees, and ledger entries stay aligned.

Why UPI and tourist payments matter for retailers

International QR acceptance is no longer a niche airport-shop feature. CBSL reports that LankaQR supports seamless tourist payments from apps connected to UnionPay International, India’s Unified Payments Interface (UPI), and Alipay+. NPCI International and LankaPay have expanded UPI merchant acceptance for Indian tourists scanning LankaQR at hotels, supermarkets, and retail chains—with participation from major hospitality and retail brands.

For Sri Lankan retailers in tourism corridors, that is revenue opportunity and reconciliation risk. The customer pays in INR through a familiar app; your books still need correct LKR settlement, MDR treatment, branch attribution, and tax documentation. Without ERP discipline, “more digital sales” can mean more unexplained settlement differences at month-end.

The reconciliation problem most retailers still have

POS shows total digital sales; bank statement shows net settlements after MDR and timing delays.
Branch staff record payments under vague labels like “QR” without method, reference, or terminal ID.
Finance exports spreadsheets and manually posts journals.
Returns and partial refunds do not link cleanly to the original payment rail.
VAT invoices and daily Z-reports cannot be traced to the settlement that actually arrived.

This is the exact opposite of what CBSL’s digital payment push is trying to achieve. The public campaign emphasizes safer, faster, more convenient payments—but business value only appears when those payments flow into controlled accounting.

How to connect LankaQR and JustPay to ERP properly

1. Standardize payment methods in POS and ERP

Create separate tender types for LankaQR (domestic), LankaQR (international/UPI), JustPay, card, cash, and bank transfer. Each tender should carry fields for reference number, acquiring bank or wallet, branch, and cashier. Generic “digital” tenders make audits painful.

2. Map settlement files to sales, not only to bank cash

Most retailers reconcile too late—when money hits the bank. Better practice is to match in two steps: (a) POS transaction to authorization/reference, (b) acquirer settlement batch to net bank deposit including MDR. ERP should store both the gross sale and the fee where required for management reporting.

3. Tie payments to invoices and VAT lines

With VAT e-invoicing and RAMIS integration on the horizon for many businesses, payment data must connect to invoice numbers, tax lines, returns, and credit notes—not only to a daily total. If your POS can issue tax invoices but ERP learns about sales only through a manual summary, compliance risk sits in that gap.

4. Automate exceptions, not the whole ledger

Start with exception detection: missing references, duplicate settlements, amount mismatches above a tolerance, refunds without original tender, and branch totals that disagree with acquirer reports. Human approvers should clear exceptions before month-end close.

5. Close the day at branch level

Each outlet should produce a daily close pack: POS tender summary, unsettled transactions, cash drawer count, digital settlement references, and variances. Area managers review before headquarters consolidates. This pattern scales better than central finance chasing forty branches over email.

What to implement first: a 30-day retailer plan

Week 1: Document current payment methods, acquirers, MDR rates, and settlement timing by branch.
Week 2: Fix POS tender setup and train cashiers to capture references consistently.
Week 3: Build ERP mapping for gross sales, MDR/fees, and net bank deposits.
Week 4: Run daily reconciliation for one pilot branch; measure unmatched transactions and time saved.

Questions to ask your bank, POS vendor, and ERP partner

Can we receive settlement reports with transaction-level references exportable to CSV or API?
Does the POS support dynamic LankaQR amounts tied to invoice totals?
Can ERP import acquirer files and match to POS receipts automatically?
How are international QR/UPI settlements identified separately from domestic QR?
What happens to refunds, voids, and partial returns on each payment rail?
Can branch managers see unsettled digital payments before close of day?

Where Capricon fits

Capricon Core connects billing, inventory, finance, branch operations, and reporting so digital payments are not trapped at the counter. Capricon Pay adds centralized payment workflow thinking for businesses that need stronger collections and transaction visibility. The goal is not “accept QR.” The goal is one operational truth from sale to settlement to VAT-ready reporting.

If you are enabling LankaQR because of CBSL’s nationwide promotion—or because Indian tourist traffic is rising—schedule a readiness review on one branch first. Test a normal sale, a QR sale, a refund, and an end-of-day close before rolling out nationally.