Getting Started
“I logged in and there are no applets at all.” If that is where you are, the cause is almost always your login, not the product, and the table under When the first week goes wrong says who fixes it. This section is for anyone starting work in a BigLedger tenant: a new accounts clerk at GadgetSphere Sdn Bhd (GS), or the person setting up its three companies and 22 branches.
Read the three pages below in order; they take about thirty-five minutes in total.
What a new tenant already holds, and who put it there
| What | Put there by | Where you see it |
|---|---|---|
| The tenant and its first owner | BigLedger, at tenant creation | Tenant Admin › Tenant Admins |
| Your login on the tenant | An Owner or Admin, who adds your e-mail or mobile number | Tenant Admin › Tenant Users |
| The applets on your launchpad | An install for your login only, from the Applet Store | Your launchpad — a colleague’s tiles say nothing about yours |
| Background schedules | Written once, all switched on, at tenant creation; a later default arrives only if BigLedger installs the defaults again | Scheduler |
| Companies, branches and the chart | Nobody until you create them; a new company has no default GL codes, branch or cashbook | Organisation, then Chart of Account › Default GL Codes |
| E-invoicing | Switched off for each new company; a blank LHDN Environment means the sandbox | Organisation › your company › E-Invoice tab |
If you are setting the system up rather than using it
The order is different, because configuration decisions cascade: the Core module’s setup order gives the sequence, and Setting up a group which way to set each choice.
- Platform overview — companies, branches and locations, before any data is loaded.
- Chart of accounts setup — and the company default GL codes, without which a FINAL document gets no journal, or a journal with a line left out.
- Choosing an item type — the one item field you cannot change afterwards.
- Maintaining the item master — tax codes and e-Invoice classification, before anything is sold.
- Setting up pricing schemes — your standard price lists.
- Best practices — the five habits that prevent the expensive mistakes.
One missing company default, or an incomplete company e-invoice identity, affects every branch of that company at once; Applet Settings are shared across the whole tenant (Finding your way around).
When the first week goes wrong
Most of these show no error: Finalise hands the journal, stock and e-invoice work to background jobs, so the screen reports success first.
| Symptom | Read |
|---|---|
| “I logged in and there are no applets at all.” | Ask the Owner or Admin to add you and give you a catalogue, then install from the Applet Store |
| “My colleague can see it and I cannot.” | Finding your way around (listings are filtered by default) and Teams and permissions |
“Every sales invoice finalises, but none of them post, and the trace names a missing default GL code.” (MISSING_DEFAULT_GL_CODE: DEBTOR) | Chart of accounts setup — map it, then Resolve in Trace Document |
| Trade debtors is debited less than the invoice total, and a sales or tax line is missing | The same guide — map the default, then Repost each affected invoice |
| Sales finalised in your first week never appear in e-invoicing | MyInvois setup, Step 4 — the company was not enabled at FINAL, and the check is not repeated |
E-invoices come back Valid, LHDN has no record, and the Validation URL starts with preprod. | MyInvois setup — the LHDN Environment was blank (sandbox) |
| Every e-invoice fails at once, from every branch | MyInvois setup — the company’s own e-invoice identity is incomplete |
| A job BigLedger told you about does nothing | Scheduler — your tenant has no schedule for it |
| A US-dollar purchase invoice is FINAL with empty TraceDocument grids | Press BASE and read the ringgit copy (Purchase Invoice) |
The parts of the job that stay with a person
- Who holds Owner and Admin rank — decide on day one; Tenant Admin opens only for these ranks. Check Tenant Admins lists exactly those people.
- Who decides the chart and the default GL codes — your accountant, per company, before anybody finalises. Check one test invoice per company posts three journal lines: trade debtors, sales and output tax.
- When to switch e-invoicing on — whoever owns tax compliance, after the LHDN environment and company identity are complete and before the first finalise. Check one document comes back Valid with a Validation URL not starting
preprod. - Which background jobs run — your finance lead with BigLedger, job by job, at go-live. Check each job’s effect appears where it should.
What success looks like
You can say how an applet differs from a module (a component against a business grouping, many-to-many), what a draft does (nothing until finalised), and which sales documents move stock (the sales invoice and the POS cash bill).
Where to go next
Questions the documentation does not answer go to Support.