Getting Started
Three short pages, in this order, and you will be able to work. About forty minutes in total.
What BigLedger is, what you will be doing, and the two facts behind most surprises
The launchpad, launchpad views, and the layout every applet shares
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:
- Platform overview — companies, branches and locations. Everything else hangs off this structure, so get it right before any data is loaded.
- Chart of accounts setup — the account structure and, critically, the company default GL codes. Without those, documents will not post.
- Choosing an item type — the one field on an item 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.
What success looks like
You are through this section when you can answer:
- 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.)
- What does a draft document do? (Nothing — it is invisible to everybody else until it is finalised.)
- Which sales document moves stock and posts to the ledger? (The sales invoice, and the POS cash bill.)
Where to go next
Items, customers, the fundamentals
Orders, deliveries, payments
Users, teams and access
What experienced users do differently
End-to-end business processes
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 tenant you are on, which applet you were in, and what you expected to happen.