PRODUCTS · FINANCE · GENERAL LEDGER
LEYSCO100 · GENERAL LEDGER & DOUBLE-ENTRY — LIVE

Every transaction, balanced.

A double-entry general ledger where every operational document posts a balanced journal — debits equal credits, to the shilling. Sub-ledgers roll up to one GL, the trial balance ties, and the period closes — posted to the SAP Business One general ledger through a production bridge. Live.

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
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
40+document types
integration-register
RECEIPT · 40+ DOCUMENT TYPESA production, bidirectional bridge moving 40+ SAP Business One document and master-data types — pull-based, idempotent, process-isolated per company database — writing every external reference straight back onto the SAP document. — delivered-integration register; the Leysco SAP Bridge (production .NET connector), verified 2026-07 · integration-register
one production ledger
ON LEYSCO100LiveDouble-entry general ledger in production — every operational document posts a balanced journal that bridges to the SAP Business One GL (OJDT/JDT1/OACT).
ON LEYSCO AKILIDesignedLeysco Akili has a native immutable multi-book general ledger designed — not yet built; the live GL is the Leysco100 strength today.
The category

General ledger / double-entry accounting core

The names you'll be comparing

SAP Business One GL · Oracle NetSuite GL · Microsoft Dynamics GL · Sage GL

The difference

A double-entry ledger where every operational document posts a balanced journal straight to the SAP Business One general ledger through a production bridge — one ledger of record the whole house posts on, not an export reconciled by hand each month.

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

JOURNAL · JE-2026-04417SYNTHETIC
ACCOUNTDEBITCREDIT
1200 Accounts Receivable232,000
4000 Sales Revenue200,000
2200 VAT Output (16%)32,000
Dr 232,000Cr 232,000BALANCED
DEBITS = CREDITS TO THE SHILLING · 200,000 + 16% VAT 32,000 = 232,000 · POSTED LIVE

Two sides, always equal.

Live · the entry

Every transaction posts a balanced journal — total debits equal total credits, to the shilling. A customer invoice of 200,000 plus 16% VAT posts as a 232,000 debit to Accounts Receivable against a 200,000 credit to Sales and a 32,000 credit to VAT. If the two sides do not agree, it does not post.

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

Live
SUB-LEDGERS → CONTROLSYNTHETIC
SUB-LEDGERCONTROL ACCOUNTTIES TO
Accounts Receivable1200 A/R controlthe customer detail
Accounts Payable2100 A/P controlthe vendor detail
Bank1010 Bankthe statement
Inventory1300 Stockthe stock ledger
4 sub-ledgersone GLRECONCILED
SUB-LEDGER DETAIL = GL CONTROL ACCOUNT · A/R · A/P · BANK · INVENTORY · IN PRODUCTION

Sub-ledgers roll to one GL.

Live · the roll-up

Accounts Receivable, Accounts Payable, bank and inventory each keep their detail, and each posts to a control account in the one general ledger — so the control balance always equals the sub-ledger it summarises. One ledger, reconciled, in production.

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

Live
TRIAL BALANCE · PERIOD JUNSYNTHETIC
ACCOUNTDEBITCREDIT
1010 Bank180,000
1200 Accounts Receivable52,000
5000 Cost of Goods Sold120,000
1300 Inventory120,000
4000 Sales Revenue200,000
2200 VAT Output32,000
Dr 352,000Cr 352,000TIES
Σ DEBITS = Σ CREDITS = 352,000 · PERIOD LOCKS · POSTS TO SAP B1 GL (OJDT/JDT1/OACT) · LIVE

The trial balance ties.

Live · the close

At period end the trial balance ties — total debits equal total credits across every account — the period locks, and the financials come straight off the one ledger. The balanced journals post to the SAP Business One general ledger (OJDT/JDT1/OACT) through the production bridge.

integration-register
RECEIPT · 40+ DOCUMENT TYPESA production, bidirectional bridge moving 40+ SAP Business One document and master-data types — pull-based, idempotent, process-isolated per company database — writing every external reference straight back onto the SAP document. — delivered-integration register; the Leysco SAP Bridge (production .NET connector), verified 2026-07 · integration-register

Live

Everything in the finance line.

In this line
General Ledger & Double-EntryLiveThis page — balanced journals, one GL.
Multi-rail Payments & BankingLiveM-Pesa / DTB / Co-op / NCBA rails, auto-matched.
Accounts ReceivableLiveCustomer invoices, ageing, collection.
Accounts PayableLiveVendor bills, the A/P the AI drafts into.
Bank ReconciliationLiveStatement match, open-payment recon.
Payment Terms & Credit ControlLiveDue-date, ageing, credit limits.
Expense & Petty CashDesignedClaims, floats, GL posting adapter.

The two books balance.

Signature · Balanced to the shilling

A double-entry ledger is structurally level: every transaction is one amount written twice — once into the debit book, once into the credit book — and if the two sides do not agree to the shilling, it does not post. A customer invoice of 200,000 plus 16% VAT enters as Dr Accounts Receivable 232,000 against Cr Sales 200,000 and Cr VAT Output 32,000; at period end the trial balance ties across every account — posted to the one SAP Business One general ledger. Live.

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

Double-entry general ledger LIVESynthetic · illustrative
Customer invoice→ JE-2026-04417
Goods — trade supply200,000
VAT 16%32,000
TotalKES 232,000
The debit bookDr
1200Accounts Receivable232,000
Σ Dr232,000
The credit bookCr
4000Sales Revenue200,000
2200VAT Output (16%)32,000
Σ Cr232,000
Trial balance · period JunSynthetic
AccountDebitCredit
1010Bank180,000
1200Accounts Receivable52,000
5000Cost of Goods Sold120,000
1300Inventory120,000
4000Sales Revenue200,000
2200VAT Output32,000
TiesΣ Dr = Σ Cr352,000352,000
A/R 52,000 = 232,000 invoiced − 180,000 collected · COGS 120,000 = inventory relieved 120,000
Two entries that must agree, or nothing posts: Dr 232,000 = Cr 232,000 on the journal, Σ Dr = Σ Cr = 352,000 on the trial balance — balanced to the shilling, posted to the one SAP Business One general ledger (OJDT/JDT1/OACT) through the production bridge. The ledger is live; these specific figures are synthetic, illustrative.
1.66M+one ledger of record
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

This is the same ledger that carries 1.66M+ invoices posted live in a single production system, countable in the SAP ledger — every one a balanced journal. One ledger the house posts on, not a copy reconciled by hand.

The double-entry GL, sub-ledger roll-up and SAP Business One posting are the Leysco100 strength today, in production. A native immutable multi-book general ledger on Leysco Akili is designed, not yet built. We chip each as it is.

Built for operations that…
  • post every transaction as a balanced journal, debits equal credits
  • roll A/R, A/P, bank and inventory sub-ledgers into one general ledger
  • close a period on a trial balance that ties to the shilling
  • post straight to the SAP Business One GL, not an export reconciled by hand
The old way → this way

Operational totals re-keyed into the accounts, and a trial balance that never quite tied one balanced ledger, sub-ledgers reconciled, posted to SAP B1

Part of the house.

Related

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

One ledger. Balanced, closed, posted.

Implemented by the team that runs the region's ledgers. Nairobi · EAT.
See the ledger
Talk to us · WhatsApp +254 780 457 591