Platform Overview
If you are about to start using BigLedger — or you are evaluating it — this page is the shape of the thing in about ten minutes. No procedure to follow; just the structure, so the rest of the documentation makes sense.
What BigLedger is, in one paragraph
BigLedger (akaun.com) is a web-based, cloud-native business operating system. It covers accounting, inventory, sales, purchasing, point of sale, e-commerce, HR and Malaysian LHDN e-Invoice. You reach it in a browser; there is nothing to install on a server. And because every screen in it is built on the same documented HTTP API, it is designed to be operated by software — including AI agents — as readily as by people.
Applets, modules, and why both words exist
Two words get used constantly in this documentation, and they are not the same thing.
An applet is a functional component — one screen or set of screens that does one job. Cashbook. Chart of Account. Internal Sales Invoice. Stock Take. Bank Reconciliation. The applet registry currently holds 210 active applets, of which 149 are the ones a customer would ever be given.
A module is a business grouping — Financial Accounting, Inventory, Purchasing, POS, E-Commerce, CRM, HR & Payroll, Manufacturing, Membership, Claims, E-Invoice.
The two are many-to-many. The Tax Configuration applet, for example, belongs to Financial Accounting and Sales and Purchasing and E-Commerce and POS — it is one thing, used by five groupings. This is why applet documentation lives in one place (the applet reference) and modules link to it rather than repeating it.
The practical consequence for you: your tenant has a specific set of applets turned on, and that set is what you can do. If a screen this documentation describes is not in your menu, the applet is not enabled for your company — that is a licensing and configuration question for your BigLedger contact, not a fault.
What sits underneath all of them
One shared data core
Every applet reads and writes the same records. Your customer list is one customer list; the Sales Invoice applet, the Statement of Account applet and the POS all see the same entity. There is no synchronisation step between applets and no separate “integration” to configure between them, because there is nothing to integrate — they are views onto one database per tenant.
This is the single biggest practical difference from running separate accounting, inventory and POS packages.
Companies, branches and locations
BigLedger is multi-company from the ground up. GadgetSphere Sdn Bhd — the example business used throughout these guides — runs three legal entities (GS retail, GSO online, GSD distribution) in one tenant, with 22 branches under them and stock locations under those.
Almost every configuration decision in BigLedger hangs off this structure: default GL codes are per company, cashbooks are granted per branch, stock balances are per location. Getting the organisation structure right before you load data is the highest-leverage hour of any implementation.
Identity and access
- One login across every applet. You sign in to the tenant, not to an application.
- Multi-factor login is supported on the platform’s login service.
- Permissions are per applet and per document type, with separate create, read, update and delete rights — which is how a branch cashier can raise a cash bill but not a journal.
The API, and agents
Everything above is reachable over one REST API. The platform’s own screens are clients of it, which is what makes it complete rather than an export layer: at the commit recorded in AI and Automation, the backend serves 18,630 routes across 2,216 controllers, of which 1,116 carry the server-to-server access endpoint a program uses with an access key instead of a human session. A single generic-document endpoint within that covers 97 document types — sales orders, purchase invoices, stock transfers, payment vouchers and the rest.
If your interest in BigLedger is “can an agent run this”, that page is the honest answer, including what the AI features do not do.
What is Malaysian about it
- LHDN MyInvois e-Invoice — submission, validation, the holding pools, cancellation and correction, and incoming supplier documents. See the e-invoice guides.
- PEPPOL — an access point and the routing configuration behind it.
- SST — the sales and service tax configuration and reporting.
- Malaysian payroll statutory deductions in the HR & Payroll module.
The applet categories you will meet first
| Grouping | What it does for you | Where to read |
|---|---|---|
| Financial Accounting | Chart of accounts, journals, cashbooks, AR and AP, bank reconciliation, financial statements | Module · Accounting guides |
| Sales | Quotation, order, delivery, invoice, returns, credit and debit notes | Sales guides |
| Purchasing | Requisition, purchase order, goods received note, purchase invoice | Purchasing guides |
| Inventory | Item maintenance, stock balance, transfers, stock take, adjustments | Module · Inventory guides |
| Sales | Quotations, orders, invoices, returns, credit and debit notes | Module |
| Point of Sale | Cash bills at the counter, cashier reporting, customer display | Module |
| E-Invoice | MyInvois and PEPPOL submission and receipt | E-invoice guides |
What success looks like
You have got what you need from this page if you can answer these three, in under thirty seconds:
- Is “Cashbook” an applet or a module? (An applet. Modules are the business groupings that contain them.)
- Where does the documentation for a screen live? (Under
/applets/— modules and guides link to it.) - If a menu item you read about is missing from your tenant, what is the likely reason? (That applet is not enabled for your company.)
Common mistakes
| Assumption | What is actually true |
|---|---|
| “I need to integrate the accounting applet with the inventory applet” | There is nothing to integrate — they read the same records |
| “Every BigLedger customer has the same menu” | Your menu is the set of applets enabled for your tenant |
| “Set up the companies later, get transacting first” | Default GL codes, cashbook access and stock balances all hang off the organisation structure; changing it after data is loaded is painful |
| “The documentation for this screen will be under my module” | Applet reference pages live in one place and are linked from every module that uses them |
Where to go next
Questions people ask
How is this different from a traditional ERP? Structurally: you are given the applets your business needs rather than a single monolithic installation, and everything runs in a browser against a cloud backend. Commercially, ask your BigLedger contact — this wiki does not publish pricing.
Can it handle more than one company? Yes. Multiple companies, branches and locations in one tenant, with multi-currency documents. GadgetSphere’s three companies in the examples throughout these guides are the normal shape, not an edge case.
Is my data secure? Traffic between your browser and the platform is encrypted with TLS, and access is controlled by role-based permissions down to applet and document level. We do not publish a security certification on this wiki. If you need a formal statement — an ISO 27001 or SOC 2 attestation, a completed vendor security questionnaire, or a data-processing agreement under Malaysia’s Personal Data Protection Act 2010 (PDPA) — ask your BigLedger contact, who can tell you what exists today.
Can I integrate with my existing systems? Yes — over the REST API described above, and through the integration applets for e-commerce marketplaces and Peppol. See Developers.
What if I need something that does not exist? Raise it at BigLedger-Support/public and someone will pick it up.