Skip to content

Modules Documentation

Work in Progress — This section is currently being updated to standardize module layouts, roles, and workflows. We will be updating this content from time to time.

BigLedger Module Documentation

BigLedger is organised into modules — business-focused groupings of the applets that work together to do a job. An applet can belong to more than one module: the Tax Configuration applet is needed by accounting, sales, purchasing, e-commerce and the till alike, and it is documented once, in /applets/, with every module linking to it.

Module membership is an editorial judgement, and it is written down. BigLedger’s own data holds no module↔applet relationship — the link table is empty — so which applets belong to which module is a decision the documentation makes rather than a fact it reads. The decision, its reasoning and the places where it is genuinely ambiguous are recorded in planning/specs/module-applet-membership.md, and each module page lists the applets it owns and the applets it depends on separately.

All Modules

Foundation

Core Module
Master data and tenant administration — the foundation every other module reads
Financial Accounting
Ledger, journals, vouchers, bank reconciliation, and budgetary controls

Revenue & Customer Operations

Sales
The B2B sales document chain — quotation to order to invoice to return, credit note and refund
Point of Sale
The retail till — the cash bill, its settlement methods and the reports that balance a shift
E-Commerce
Multi-channel online selling with marketplace integration
Membership & Loyalty
Customer loyalty programs, points currency, and voucher management

Supply Chain & Operations

Purchasing
Purchase-to-Pay, from quotation and requisition through receipt to supplier invoice
Inventory & Warehouse
Stock tracking, transfers, warehouse bin management, and replenishment
Manufacturing
Production planning, shop floor execution, and job order management

Compliance & Specialized

E-Invoice & PEPPOL
MyInvois and PEPPOL electronic invoicing compliance
Claims Management
Employee expense claims and reimbursement cycles
HR & Payroll
The employee master and the claims hand-off to payroll; attendance, leave and payroll applets exist in source but are not yet registered
Digital CRM
Contact centre, sales leads, engagement register and event calendars

Standard structure

Every module hub page carries the same four things:

  1. What the module is for, in terms traceable to the applets beneath it.
  2. Applets in this module — every one linked, with a sentence on what it is for, and any registry applet that has no page yet named as a gap rather than omitted.
  3. What actually happens — for a module whose documents reach the ledger, which ones post and which only record.
  4. What this module needs from others — the dependency view, linked across modules.

Beneath the hub sit Concepts, Configuration, Use cases, Reports, Best practices, Related applets and API reference. A page that carries a sources: map in its front matter has been grounded against the applet pages and the backend; one that does not has not yet been through that pass.