Your SAP stays the ledger.
Field orders, till sales, collections and fiscal receipts are captured at the edge and posted straight into your SAP Business One — pull-based, idempotent, one process per company database, every SAP reference written back onto the source. 1.66M+ invoices deep.
sql-count
integration-register
integration-register
Integration & connectors / iPaaS — the SAP Business One operations bridge
Boomi · MuleSoft · Celigo
A generic iPaaS moves records between systems. This is a purpose-built SAP Business One operations bridge — pull-based, idempotent, process-isolated per company database, writing every external reference back onto the SAP document. integration-register
| EDGE SOURCE | EDGE DOCUMENT | SAP OBJECT | POSTED |
|---|---|---|---|
| Leysco Field | Field invoice | A/R Invoice (oInvoices) | DocEntry 88421 |
| Leysco POS | POS sale | A/R Invoice (oInvoices) | DocEntry 88422 |
| Field collection | M-Pesa receipt | Incoming Payment (oRCT) | DocEntry 51203 |
| Van dispatch | Delivery note | Delivery (oDeliveryNotes) | DocEntry 33110 |
| TIMS | Fiscal receipt (CUIN) | written back onto invoice | INV 88421 |
| 5 edge documents | 3 SAP object types | refs written back |
The edge captures; SAP stays the ledger.
The edge posts inField orders, till sales, collections and fiscal receipts are captured where the business happens and posted straight into your SAP Business One — every one carrying the SAP reference back onto the source document. reconciliation
| SAP OBJECT | DIRECTION | WHAT IT CARRIES |
|---|---|---|
| Business Partners (oBusinessPartners) | IN | customer & vendor master |
| Items (oItems) | IN | product master |
| Price Lists (oPriceLists) | IN | pricing to the edge |
| Sales Orders (oOrders) | OUT | field & web orders |
| Deliveries (oDeliveryNotes) | OUT | van dispatch |
| A/R Invoices (oInvoices) | OUT | field & POS invoices |
| Incoming Payments (oIncomingPayments) | OUT | field & rail collections |
| Journal Entries (oJournalEntries) | OUT | GL & fiscal postings |
| 8 of 40+ shown | bidirectional | master data in · documents out |
40+ document and master-data types, both ways.
Both waysMaster data flows in — business partners, items, price lists — so the edge prices and identifies correctly; documents flow out — orders, deliveries, invoices, payments, journals — so the ledger stays whole. Forty-plus SAP object types, bidirectional. integration-register
guard idempotency-key INV-2026-8820 → not yet posted
post SAP oInvoices (DI-API) → DocEntry 88421
write back → source SAP ref 88421 stamped on the edge doc
isolate one process / company SWD_LIVE · no cross-database bleed
Idempotent, isolated, written back.
Safe by constructionThe bridge pulls from the edge, guards each document with an idempotency key so nothing double-posts, runs one process per company database so nothing bleeds across tenants, and stamps the SAP reference back onto the source the moment it lands. integration-register
| PLATFORM | VIA | STATUS |
|---|---|---|
| SAP Business One | DI-API bridge | Live |
| SAP S/4HANA | data + fiscal | Live |
| SAP Business ByDesign | OneConnect | Live |
| Sage / Sage X3 | data + TIMS | Live |
| Microsoft Business Central | adapter | Live |
| Skyplanner | adapter | Live |
| Microsoft Dynamics NAV | data | Live |
| Tally | data | Live |
| 8 of 14+ named | delivered |
14+ platforms, one integration house.
One patternThe same pull-based, write-back pattern reaches beyond SAP Business One — S/4HANA, Business ByDesign, Sage, Business Central and more — named, delivered integrations, not a slideware roadmap. integration-register
Everything in the integration line.
In this line| The Leysco SAP Bridge | Live | DI-API write-back, 40+ doc types, bidirectional. |
| Universal Adapter Catalog | Early access | 25 seeded adapters, configure-not-code. |
| External Data Gateway | Early access | Semantic virtual data layer; AI/MCP substrate. |
| Sync Orchestration | Early access | Watermark polling, incremental pull. |
| Pipeline / Saga Orchestration | Early access | Multi-step, compensating transactions. |
| Inbound Webhook / Event Gateway | Early access | Event ingestion into the platform. |
| Field Mapping Studio | Early access | Fuzzy to semantic field matcher. |
| Credential Vault | Early access | AES-256-GCM per-tenant secrets. |
| Integration Health & Observability | Early access | Sync status, retries, dead-letter queue. |
| Generic OData v4 + REST | Early access | Configure-not-code endpoints. |
Every edge document lands stamped with its SAP reference.
Signature · Synthetic data, real workflowA field invoice, a till sale, a mobile-money receipt and a van delivery each post through the bridge into SAP Business One — idempotent, one process per company database — and the SAP reference is written straight back onto the source. integration-register
sql-count
The SAP Business One company databases we host and operate hold 8.09M business documents and 35.1M posted lines — and the bridge is the seam that keeps every edge document and the ledger in agreement.
On Leysco Akili, integration is a native External Data Gateway and a 25-adapter catalog — early access, not a production bridge. The SAP B1 bridge behind SAMWEST's 1.66M+-invoice ledger is the Leysco100 strength today.
- run SAP Business One as your system of record and need the field, the till and the rails posting into it
- want every external document to write its SAP reference back onto the source — no orphaned records
- need idempotent, process-isolated posting per company database, not a fragile nightly export
- already run several ERP and accounting platforms and want one integration house
Nightly CSV exports and re-keyed invoices that never quite reconcile → edge documents posting into SAP, referenced both ways
Part of the house.
RelatedPayments Hub
The rails whose receipts post to SAP.
LiveKRA Fiscalisation
Fiscal receipts written back to the invoice.
LiveVan Sales
The field documents the bridge posts.
LiveThe house has worked SAP Business One since 2017. company-books