PRODUCTS · FINANCE · PAYMENTS
LEYSCO100 · PAYMENTS — LIVE IN PRODUCTION

Every rail, matched to the ledger.

M-Pesa and DTB land in real time and bank settlements arrive by file exchange — incoming payments auto-match to the invoice they settle and post to the same ledger discipline that carries 1.66M+ invoices. Outgoing vendor and B2C runs go the other way.

See the rails liveThe Finance line
6 railspayment rails
deployment-record
RECEIPT · PAYMENT RAILSDelivered payment rails: M-Pesa STK, DTB STK and Card EFTPOS multi-rail at the till; Co-operative Bank, NCBA and Stanbic bank-file exchange; SAP ByDesign ↔ M-Pesa B2C payroll disbursement (20–100 daily payments, scaling to 50,000/yr) at SHOFCO. — MASTER_GLOBAL_DOSSIER §7-8; NCBA/DTB runbooks (framework-main/docs), verified 2026-07 · deployment-record
1.66M+invoices
sql-count
RECEIPT · 1.66M+ INVOICES1,666,107 invoices posted in a single hosted customer system — SAMWEST hosted production DB (SWD_LIVE), countable live in the SAP ledger. — SAMWEST hosted production DB, verified 2026-07 · sql-count
one house, one ledger
reconciliation
RECEIPT · ONE HOUSE, ONE LEDGERThe same house that posts 1.66M+ distribution invoices in production runs these operations — one ledger discipline, one approval engine, one team across pay, people and distribution. — derived: c-004 (SAMWEST sql-count) + c-011 (REEDS billing ledger), verified 2026-07 · reconciliation
SAMWEST · Car & General · live rails
ON LEYSCO100LiveMulti-rail payments hub in production — M-Pesa/DTB/Co-op/NCBA rails, auto-match to A/R.
ON LEYSCO AKILIDesignedLeysco Akili .NET has a Payments module schema — designed, not built; rails remain the Leysco100 strength.
The category

East-Africa payment rails & cash application

The names you'll be comparing

Flutterwave · Cellulant · DPO Group

The difference

The gateways move money; this hub also posts it — every incoming payment auto-matched and reconciled under the same ledger discipline the house runs 1.66M+ invoices in.

sql-count
RECEIPT · 1.66M+ INVOICES1,666,107 invoices posted in a single hosted customer system — SAMWEST hosted production DB (SWD_LIVE), countable live in the SAP ledger. — SAMWEST hosted production DB, verified 2026-07 · sql-count

INCOMING · AUTO-MATCHSYNTHETIC · 11 JUL 2026
RAILREFAMOUNTMATCHED TO
M-Pesa STKQGR7X2M948,200INV-2026-0142
Co-op bankCB-8841125,000INV-2026-0138
DTB STKDT-552717,600INV-2026-0151
NCBANC-339092,450INV-2026-0129
M-Pesa STKQH2K7P16,900— unmatched
MATCHED283,2504 of 5 · 1 held
INGESTED · AUTO-MATCHED TO OPEN A/R · UNMATCHED HELD, NOT GUESSED

Payments that match themselves.

Incoming

M-Pesa STK and DTB STK land in real time; Co-operative Bank and NCBA arrive by bank-file exchange — all auto-match to the open invoice they settle, with an exception queue for the ones that don't.

deployment-record
RECEIPT · PAYMENT RAILSDelivered payment rails: M-Pesa STK, DTB STK and Card EFTPOS multi-rail at the till; Co-operative Bank, NCBA and Stanbic bank-file exchange; SAP ByDesign ↔ M-Pesa B2C payroll disbursement (20–100 daily payments, scaling to 50,000/yr) at SHOFCO. — MASTER_GLOBAL_DOSSIER §7-8; NCBA/DTB runbooks (framework-main/docs), verified 2026-07 · deployment-record

OUTGOING BATCH · VENDOR + B2CSYNTHETIC
PAYEERAILAMOUNTSTATE
Njoroge SuppliersCo-op EFT212,400APPROVED
Bidii LogisticsM-Pesa B2C38,900APPROVED
Kariuki HardwareCo-op EFT74,150PENDING
APPROVED → RELEASE251,300
WITHHOLDING-TAX COMPUTED · APPROVED BEFORE RELEASE — KARIUKI PENDING, HELD

Vendor and B2C runs, in one batch.

Outgoing

Outgoing payments go the same rails in reverse — single or batch runs to vendors and payees, with withholding tax computed and approval required before a shilling leaves.

DAY-END RECONCILIATIONSYNTHETIC
ACCOUNTSTATEMENTLEDGERΔ
Co-op · KES1,842,6001,842,6000
NCBA · KES617,300617,3000
M-Pesa float94,01094,0100
RECONCILED2,553,9102,553,9100
STATEMENT VS LEDGER · AUTO-MATCHED · ZERO VARIANCE NET OF OPEN ITEMS

Reconciled to the bank statement.

Reconciliation

Every rail's settlement reconciles to the bank statement and to open payments — the day's cash position is a report you read, not a hunt you run.

POSTING FLOWSYNTHETIC · PER RECEIPT
M-Pesa STK QGR7X2M9 48,200
→ match INV-2026-0142 (open A/R)
→ post ORCT receipt (incoming payment)
→ ledger DR bank CR A/R — one chart of accounts
ONE POSTING PATH FROM THE RAIL TO THE GENERAL LEDGER

Under the same ledger as everything else.

One ledger

Payments post to the same ledger discipline that carries 1.66M+ distribution invoices — one chart of accounts, one approval engine, one truth across sales, cash and pay.

sql-count
RECEIPT · 1.66M+ INVOICES1,666,107 invoices posted in a single hosted customer system — SAMWEST hosted production DB (SWD_LIVE), countable live in the SAP ledger. — SAMWEST hosted production DB, verified 2026-07 · sql-count

Everything in the Finance line.

In this line
Payments Integration HubLiveMulti-rail incoming + outgoing, auto-match.
A/R & Customer InvoicingLiveSub-ledger, credit memos, allocation.
A/P & Vendor PaymentsLiveSingle & batch runs, withholding tax.
Bank Reconciliation & CashLiveStatement match, open-payment recon.
Payment Terms & CreditLiveDue-date, ageing, credit control.
General LedgerLivePosts / bridges to SAP B1.
Expense & Petty CashDesignedClaims, floats, GL posting adapter.

Every payment threads to its receipt.

Signature · Synthetic refs, real pipeline

M-Pesa and bank payments land in one incoming feed. Each one threads through auto-match to its open invoice and posts to the ledger as a receipt — rail, reference and amount carried through, never re-keyed.

deployment-record
RECEIPT · PAYMENT RAILSDelivered payment rails: M-Pesa STK, DTB STK and Card EFTPOS multi-rail at the till; Co-operative Bank, NCBA and Stanbic bank-file exchange; SAP ByDesign ↔ M-Pesa B2C payroll disbursement (20–100 daily payments, scaling to 50,000/yr) at SHOFCO. — MASTER_GLOBAL_DOSSIER §7-8; NCBA/DTB runbooks (framework-main/docs), verified 2026-07 · deployment-record

RAILREFAUTO-MATCH · KESINVOICEPOSTED (ORCT)
M-PESA STKQGR7X2M9KES 48,200INV-2026-0142POSTED → ORCT
CO-OP BANKCB-8841KES 125,000INV-2026-0138POSTED → ORCT
DTB STKDT-5527KES 17,600INV-2026-0151POSTED → ORCT
NCBANC-3390KES 92,450INV-2026-0129MATCHED · awaiting post
M-PESA STKQH2K7P1KES 6,900HELD · unmatched— no open-invoice match
Incoming payments auto-match to open A/R and post to the ledger — the unmatched one is held, not guessed. Synthetic refs; real pipeline. Scope: Kenya.
1.66M+invoices posted
sql-count
RECEIPT · 1.66M+ INVOICES1,666,107 invoices posted in a single hosted customer system — SAMWEST hosted production DB (SWD_LIVE), countable live in the SAP ledger. — SAMWEST hosted production DB, verified 2026-07 · sql-count

Every open invoice in a ledger that carries 1,666,107 posted ones is a payment waiting to be matched — and the rails post their receipts back under the same ledger discipline.

On Leysco Akili, Payments is a designed .NET module schema — informed by these rails, not yet built. The multi-rail hub is the Leysco100 strength today.

Built for operations that…
  • collect across M-Pesa, bank and card on one hub
  • auto-match incoming payments to open invoices — not a month-end spreadsheet
  • run outgoing vendor and B2C batches with approval and withholding tax
  • reconcile every rail to the bank statement at day-end
The old way → this way

Rail-by-rail portals and manual receipt matching → one hub, auto-matched and posted

Part of the house.

Related

A/R & Invoicing

The open invoices the rails settle.

Live

Bank Reconciliation

Every rail reconciled to statement.

Live

Payroll

Salary disbursement on these rails.

Live

The house has worked SAP Business One since 2017.

company-books
RECEIPT · SINCE 2017Operating heritage from 2017 as Leysco Systems Consulting (company books from 2019 preserved); LEYSCO LTD incorporated 2020, reg. PVT-5JU8VBP, Nairobi. One continuous practice, one team. — company books; registration PVT-5JU8VBP, verified 2026-07 · company-books

Put every rail on one ledger.

Implemented by the team that built it. Nairobi · EAT.
See the rails live
Talk to us · WhatsApp +254 780 457 591