Skip to content

Getting Started

Three short pages, in this order, and you will be able to work. About forty minutes in total.

1. Introduction
What BigLedger is, what you will be doing, and the two facts behind most surprises
2. Finding your way around
The launchpad, launchpad views, and the layout every applet shares
3. Platform overview
Applets, modules, companies and branches — how the product is put together

If you are setting the system up rather than using it

The order is different. Configuration decisions cascade, and some of them are painful to reverse:

  1. Platform overview — companies, branches and locations. Everything else hangs off this structure, so get it right before any data is loaded.
  2. Chart of accounts setup — the account structure and, critically, the company default GL codes. Without those, documents either fail to post or — worse — post with lines missing and nobody told.
  3. Choosing an item type — the one field on an item you cannot change afterwards.
  4. Maintaining the item master — tax codes and e-Invoice classification, before anything is sold.
  5. Setting up pricing schemes — your standard price lists.
  6. Best practices — the five habits that prevent the expensive mistakes.

What success looks like

You are through this section when you can answer:

  1. What is the difference between an applet and a module? (An applet is a functional component; a module is a business grouping. Many-to-many.)
  2. What does a draft document do? (Nothing — it is invisible to everybody else until it is finalised.)
  3. Which sales document moves stock and posts to the ledger? (The sales invoice and the POS cash bill — and a Sales GIN Stock Out, if an integration raises one through the API.)

Where to go next

Basic operations
Items, customers, the fundamentals
Daily tasks
Orders, deliveries, payments
Administration
Users, teams and access
Best practices
What experienced users do differently
Workflow guides
End-to-end business processes
Troubleshooting
When something will not save or post

Where to ask

If the documentation does not answer your question, open an issue at BigLedger-Support/public — say which applet you were in, what you expected to happen and what happened instead. Anyone can read the tracker, so keep your tenant code and your own records out of the post; a question about your own tenant goes to your BigLedger contact (see Support).