Integrations
“How do I connect another system to BigLedger?” The answer depends on which way the data goes and on who presses the button, and most of the screens are not in this folder. Four pages live here: the marketplace synchronisation index, the Scheduler, tenant-to-tenant connectivity and the applet registry. Payment gateways, LHDN and Peppol, webhooks, the REST API and messaging channels have pages elsewhere; the table routes to each, and each page says what stops without telling anyone.
Whose screen it is, what moves, and what presses the button
| Connection | Whose screen | What moves, and on what trigger |
|---|---|---|
| Marketplace shops — Lazada, Shopee, TikTok Shop, Shopify (EcomSync Related Applets) | Your e-commerce or operations person, in Organisation (the marketplace branch), Doc Item Maintenance (listings) and Sales Order (Internal) (orders) | In: orders, as finalised sales orders on the marketplace branch. Out: items, prices, stock, fulfilment status; payouts as receipt vouchers. Every one is a clock you create; only the shop’s authorisation comes back by callback |
| Your own storefront and its payment gateway (CP Commerce Admin, Merchant Admin) | Whoever runs the website | In: the gateway’s callback turns the cart into a FINAL sales order with the payment as a settlement line — no receipt voucher (Core Concepts §4) |
| LHDN e-invoice and Peppol (E-Invoice hub) | Your accounts team | Out: finalised sales documents, on clocks a new tenant is created with. In: validation results, rejections, incoming Peppol documents |
| Webhooks (Webhooks) | A developer, through the API — not the Web Hook settings screen | Out: one POST per subscribed event, one attempt, no signature, no alert. A webhook says something changed; the API pull makes your copy right |
| The REST API (Integrate an External System) | A developer | Either way, on your trigger. A document your system creates is an ordinary document — same posting, same e-invoice queue — carrying your system’s own reference. Nothing tells anyone when your feed stops (the morning check) |
| Another BigLedger tenant (T2T Admin) | The administrator of each tenant | Neither way, by itself. It maps companies, branches and items; no document process consults a mapping |
| Messages (Unified Contact Center) | Contact-centre agents | In: each message becomes a routed task; replies go back on the same channel. Posts nothing |
| Bank statements (Bank Reconciliation) | Your accounts clerk | In, by hand: an uploaded statement file, matched against the cashbook |
| The clock behind all of it (Scheduler) | Your tenant administrator | Each due ACTIVE clock queues its job. Last Run Date means fired, not worked |
| The applet registry (Developer SysAdmin) | BigLedger’s platform developers; here for history | What the Applet Store shows and which catalogues carry an applet |
Payment Channel has no page yet. It is listed with the E-Commerce module.
Which one to pick
- You sell on Lazada or Shopee and want the orders in the books. A marketplace branch, linked listings, and clocks: start with the EcomSync setup order and create the clocks last. Your own CP Commerce storefront is one of the marketplace types.
- A second company in your group should see the first company’s documents. Not T2T. Within the same tenant, pair the branches in the intercompany setting, per branch and per document type (Setting up a group). T2T is for two organisations that each pay for their own tenant, and it maps records without moving documents.
- Another system of yours needs to know when something changes here. A webhook for the hint, the API for the truth; build as if the webhook may never arrive.
- Something should run every night. The Scheduler: create the clock INACTIVE, press Run Now, look for the job’s output, then set it ACTIVE.
- A customer wants their e-invoice, or LHDN rejected one. The E-Invoice hub.
What runs when nobody presses a button, and what does not
Every connection above except the gateway callback and the REST API is a clock. A new tenant is created with a set of them, almost entirely LHDN work, and no marketplace, webhook, gateway-sweep or GitHub clock is among the defaults — a re-install of the defaults never adds one either. So a marketplace branch with its shop authorised and no clock behind it looks complete and syncs nothing. A job that exists runs on your tenant only if the Scheduler listing shows an ACTIVE row with its code and a Last Run Date that moves; the Scheduler page lists the defaults and the four facts that decide whether a job works.
When something here goes wrong
Start on the page that owns the connection: EcomSync Troubleshooting (an order missing from BigLedger, an old price on the shop, a lapsed authorisation, the shop’s Balance and dashboard figures), Webhooks (a missed event, a missing authentication header, the delivery log), T2T Admin (a half-copied mapping), Core Concepts §4 (a gateway payment with no receipt voucher) and the E-Invoice hub.
The product tells nobody when a feed stops, so name one person per channel to check it every working morning: the Scheduler dates against their timetables, each shop’s orders against the seller centre (Running an Online Channel), yesterday’s storefront orders carrying a gateway settlement line against the gateway’s own report, and your own webhook delivery log.