Bank Reconciliation - MoMo - GIP-GhanaPay

Everything in the box

• 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.
• Any combination of keys — GhIPSS reference, amount with tolerance, recipient account, date ± N days, fuzzy narration, institution codes.
• One-to-many settlement matching with sum tolerance for bulk switch legs.
• Every match is explainable — stamped with the rule version and pass that produced it, for audit.
• Versioned under maker–checker — rule changes take effect only after a second officer approves them.
• Failed but customer debited — the classic loss position — is flagged the moment a failed transfer still moved money.
• Routed to teams by category, aged against configurable SLAs, escalated on breach.
• Maker–checker resolution — one officer proposes with justification, another approves. Self-approval is blocked.
• Export to your core — bulk-select cases and generate a debit/credit upload file in your CBS's own format.
• Your tariff, versioned — percentage, flat, caps, tiers, channel and segment rules, E-Levy as its own line, effective-dated.
• Commission at risk is quantified for every payment that failed to reconcile, split into commission, tax and levy.
• The figure falls as cases resolve — the headline counts only money still genuinely at risk, never stale exposure.
• 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}.
• 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.
• Runs on Windows/WAMP or Linux — the same code, no OS lock-in
• Your database, your encryption keys, your backups
• Background workers scheduled through your own OS
• Reviewable source; no framework upgrade treadmill
• Daily auto-matching and missing-file alerts
• Scheduled backups with retention
• SLA sweeps and escalations
• Health page: database, workers, disk, audit chain