Auto-profile any file
CSV, pipe, tab or Excel — the profiler finds the delimiter, the header row, and infers a type for every column from the data itself.
DIVINE Recon reads the switch and your core, matches what agrees, and turns everything that doesn't into a tracked, provable case — with the commission you were owed quantified along the way.
From the moment a file lands to the certificate an examiner signs, every step is configurable, provable, and yours to host.
Compose your own rule waterfall — reference, amount, account, date window, fuzzy narration — per product, direction and counterparty. No vendor-fixed logic.
Upload any file, have its columns auto-profiled, tag what matters, and wire up who matches whom. A new reconciliation is an afternoon, not a project.
Every unmatched item becomes a case: categorised, routed to a team, aged against an SLA, and resolved under maker–checker with full provenance.
Recompute the commission, tax and levy you were owed on payments that failed to settle — revenue at risk, quantified to the pesewa.
Institution-branded certificates, an append-only hash-chained journal, and one-click examiner packs. Provable, not just printed.
A plain PHP/LAMP stack your own IT team can deploy, read and patch. Payment data never leaves your building.
Each pass runs on what the last one left behind — strictest criteria first, so a confident reference-and-amount match happens before anything fuzzy is ever suggested.
The residue is where the money hides. Each exception opens a case with a category that tells you exactly what broke — and the one that matters most is caught first.
| Case | Reference | Amount | State |
|---|---|---|---|
| EXC-000212 | 821563258 | ₵ 90.00 | their-side |
| EXC-000213 | 821490021 | ₵ 4,000.00 | debited |
| EXC-000214 | 821490088 | ₵ 512.50 | pending |
| EXC-000210 | 821489744 | ₵ 75.00 | resolved |
GhIPSS settles principal, never commission. So leakage from mischarged or uncollected fees is invisible — unless something recomputes it independently against your own tariff.
| Reference | Comm. | Levy | Total |
|---|---|---|---|
| 1486170514 | ₵10.00 | ₵12.50 | ₵22.50 |
| 1486170512 | ₵10.00 | ₵8.50 | ₵18.50 |
| 1486170513 | ₵8.00 | ₵4.00 | ₵12.00 |
What used to be professional-services work is now client configuration. Define products, upload sources, confirm the columns, wire the matching, ship the export template.
CSV, pipe, tab or Excel — the profiler finds the delimiter, the header row, and infers a type for every column from the data itself.
Confirm which column is the reference, the amount, the account, the status. Saved as a versioned schema that guards against layout drift.
Draw which document matches which — switch vs ledger, or switch vs middleware vs core to isolate exactly which hop broke.
Choose the debit and credit columns your core expects, drag them into order, and add custom narrations like Outwards RVSL {amount} {txn_date}.
Security is the first objection in every procurement — so it's built in, not bolted on. The audit trail isn't merely stored; it's cryptographically provable.
Account numbers encrypted with AES-256-GCM; matched via keyed HMAC hashes, so routine runs never touch plaintext.
Four-eyes on every sensitive action. Self-approval blocked in code, not by convention.
Every view of a real account number is written to the journal — who saw what, and when.
Analyst, supervisor, auditor, admin — granular permissions, least-privilege by default.
Alter any record and the chain breaks from that point on. A daily job re-verifies the whole chain and raises a critical alert if it ever fails.
A plain, framework-free PHP application on a standard LAMP stack — the easiest possible artefact for a bank's own team to review, deploy and patch.
The most convincing pilot is your own data, run in parallel with your manual process for a month. Let's set one up.
Prefer email? info@avalongh.com