Close every reconciliation the same day, with a clean audit trail.
ATM, 1LINK, RAAST, card and nostro files are still matched by hand in many banks, with no control over who changed what. KodevRecon replaces those spreadsheets with one controlled platform for operations and finance, from file intake to a certified balance.
- Built for 1LINK, RAAST and SBP needs
- Maker-checker on every posting
- On-premises by default
Today’s reconciliations
Ranked by risk
| Break | Recon | Cause | Age | Amount (PKR) |
|---|---|---|---|---|
| BRK-ATM-20714 | ATM 3-way | EJ vs switch | 1 d | 25,000 |
| BRK-IBF-08833 | 1LINK IBFT | Missing credit | 2 d | 140,500 |
Screen shown with sample data.
Reconciliation is still the bank’s riskiest spreadsheet.
Manual matching
Statements and settlement files ticked by hand every morning, by people who should be investigating.
Customer refunds missed
Failed ATM and IBFT debits found late, so refunds miss scheme and SBP timelines.
Suspense that ages
Unexplained differences sit for months, then surface at month end or in audit.
Weak segregation
The same person matches, adjusts and approves, with no tamper-evident trail.
Transaction matching and balance-sheet attestation, on one platform.
New sources are set up as file formats and matching rules, not custom code.
ATM and CIT cash
Three-way match of core banking, switch and EJ, with cash-in-transit counts.
1LINK IBFT and RAAST
Interbank transfers, settlement files, fees and charges.
Nostro and SWIFT
MT940, MT950 and camt.053 against the mirror ledger, with positions and forecast.
Treasury deals
FX and money-market deals against MT300 and MT320 confirmations.
Cards and disputes
Visa and Mastercard clearing, chargebacks and linked customer refunds.
GL and suspense
Balance proof, GL attestation and the month-end close.
From file to certified balance.
Nothing posts, no rule changes and no user gets access without a second person approving it.
Files checked first
SFTP, API and database pulls; layout, counts, control totals and SHA-256 fingerprints.
Versioned rules
Exact, tolerance, reversal pairs, carry-forward and learned suggestions.
Breaks ranked by risk
Routed to teams and investigated with SWIFT and email chasers.
Maker-checker posting
Approval by amount band; balanced journals posted to core banking.
Prove and lock
Balance proof, GL attestation, sign-off and period lock.
Every difference explained before anyone signs.
- The maker can never approve their own item, enforced in code
- Second checker and Head of Reconciliation above the bank’s limits
- Hash-chained audit trail, verified daily; every search and export logged
- Matching rules written in plain words and simulated on past data before go-live
- Month-end close checklist, then the period locks
- Auditors build their own audit binder, read only
Each user starts with their own work.
- Queues by role: items to approve, refunds due today, breaks past SLA
- Each break shows all sides, the differing fields and a suggested fix
- Learned suggestions pair items the rules missed, such as a mistyped STAN
- Card and 1LINK disputes tracked to closure with stage deadlines
- Live management dashboard: auto-match rate, open breaks, unreconciled value
- Ask questions of the data without SQL, with card numbers masked
Connects to core banking, payments and SWIFT.
KodevRecon installs in the bank’s own data centre and talks to the systems already there, by file or API.
| Core banking | Temenos T24, Finacle, Symbols, UBANK PLUS; others by file or API |
| Payments and cards | 1LINK IBFT, RAAST (pacs.008), Visa Base II, Mastercard IPM, ATM switch (ISO 8583) |
| SWIFT and treasury | MT940/MT950, camt.052/053/054, MT300/MT320, MT103/MT202, MT199/MT399 chasers |
| Branch and cash | ATM electronic journals, CIT replenishment files, email and PDF statements |
| Hosting | On-premises on VMware or OpenShift by default; in-Pakistan private cloud where SBP rules allow |
| Interfaces | REST APIs, SFTP, database links, ITSM and email |
Security and resilience a bank can sign off.
Performance and resilience figures are design targets, agreed with each bank. Designed to the SBP technology risk and outsourcing frameworks.
A focused pilot proves value in about one quarter.
Two or three reconciliations first. We measure auto-match rate, manual hours saved, breaks past SLA, refunds on time and audit findings closed.
Discover
Workshop with operations, finance, IT and audit; files, rules and limits mapped.
Install and configure
On the bank’s infrastructure, with live feeds for 2–3 reconciliations.
Parallel run
Beside the current process, compared daily; users trained and VAPT done.
Go live and extend
Sign-off by business, IT risk and audit; spreadsheets switched off.
See KodevRecon on your own files.
Use the working demo with each role, or send masked sample files for a fit review. No cost, no commitment.