Guide

This is the task layer: how to raise an order, receive a delivery, take a payment, price a product, close a month of e-invoices, find a report. It is written for the person doing the job, not for the person who built the system.

Some pages here walk one screen. Others walk a whole job — taking an order through to the money arriving, getting stock to agree with the shelf — across several screens, telling you which step is the one that matters. Both live here now.

Where to start

New to BigLedger? Getting started — about forty minutes, three pages, and you will be able to work.

Setting the system up? Five steps, in this order, take a new company from first login to a transaction that posts correctly. Step 3 is the one people skip and regret.

Already working and stuck on one thing? Go straight to the area below, to troubleshooting, or to the FAQ — questions customers actually asked, each answered in two or three sentences and a link to the page that carries the rest.

Browse them by who you are, or by what you are facing

The areas below are the shelf, in reading order. The same walkthroughs are also grouped three other ways — generated from each guide’s own front matter, so a guide is written once and appears wherever it belongs.

The areas

Doing the day’s work

Running a whole process end to end

Why it works the way it does

The one thing worth knowing before anything else

Nothing before the sale posts to your ledger, and the only stock that moves before it is stock sent to a customer on consignment — from your store to their location, still yours. Quotations, sales orders, delivery notes and delivery orders record intent and drive the process. Stock leaves, and the sale posts, when a sales invoice, a POS cash bill or a Sales GIN Stock Out is finalised; the last is a goods issue created only through the API. (An open order does reduce the available quantity, so the same unit is not promised twice.)

On the purchasing side it is the mirror image: a standard goods received note records the count, and the purchase invoice books the stock and the liability.

More of this in best practices, and the reason behind it in the generic document.

Two other layers, and which one you want

Modules link to applet pages rather than repeating them, so there is one page per applet and it is the current one.

By the work you do

Sales and customer service — sales overview · creating a sales order · processing a delivery order · recording a customer payment · sales workflow guides

Purchasing and receiving — purchasing overview · creating a purchase order · goods received note · purchase invoice processing · purchasing workflow guides

Product and pricing — choosing an item type · maintaining the item master · maintaining items · pricing schemes · price books · designing pricing rules

Logistics — planning delivery trips · processing a delivery order

Finance and accounting — accounting guides · reports and analytics · financial accounting module

Malaysian e-Invoice — e-invoice guides · e-Invoice and PEPPOL

Administration — administration · document approvals

Building on BigLedger — developer documentation · API reference · applet development

Reading orders

Each row links a guide that exists. Follow a column top to bottom.

Money

1. Chart of Accounts Setup — design the account structure before anything posts
2. Credit Limits and Payment Terms — the terms and ceilings you trade on, and what BigLedger actually does with them
3. Journal Entries — post, clone and void a manual journal
4. Bank Reconciliation — match the statement, find the variance, keep the audit pack
5. Financial Reporting — trial balance, P&L, balance sheet, export

Selling

1. Standard Sales Workflow — quote, order, pick, invoice, collect
2. Cash Sales — the walk-in counter sale and closing the till
3. Credit Sales — payment terms, chasing what is owed, what credit limits really stop
4. Partial Delivery — one order, several shipments
5. Instalment Sales — paying over time, and the financing workflow the product does not have
6. Installation Scheduling — delivery jobs, trips, drivers, stops
7. Returns & Exchanges — the three return documents and when each applies
8. Balancing the Drawer — counting the till, working out what you expected, and naming which of four things a difference is
9. Banking the Day’s Takings — the cash out of the drawer, into the bank, and onto the statement
10. Deciding on Credit — what a customer owes the whole group, and whether they get more goods
11. Stopping Supply to a Customer — the stop, what it refuses, and what can quietly remove it
12. Chasing Overdue Accounts — the weekly collections routine when nothing reminds anyone
13. Sales That Arrive From Another System — where a synced sale came from, what it posts, and the morning check that notices a feed has stopped

Buying

1. Standard Procurement — order to payment, and when stock actually moves
2. Direct GRN — goods that arrived without an order
3. Direct Invoice — rent, utilities, subscriptions and other non-stock spend
4. Invoice-First — deposits and bills that arrive before the goods
5. Consignment Purchasing — stock the supplier still owns

Malaysian e-invoicing

1. What Malaysia Requires — the rollout, the 72-hour window, where BigLedger sits
2. MyInvois Setup — authorise BigLedger as your intermediary and turn it on in the right order
3. Pools & Routing — individual, consolidated, or parked, and why
4. Validation Rules — why LHDN rejects a document and how to fix it
5. The Month-End Cycle — the 1st to the 7th, in order
6. Cancel and Correct — when a validated e-invoice turns out to be wrong
7. Incoming Supplier E-Invoices — what arrives from your suppliers, and what BigLedger does not see
8. Peppol Configuration — delivering straight into a trading partner’s system

What success looks like

You are using this section well if, faced with a new task, you can say within thirty seconds which layer has your answer:

1. “How do I take a deposit on an order?” → here.
2. “What does the whole credit-sale cycle look like?” → here, in the process areas above.
3. “What exactly does the Allow Exceed Contra setting do?” → applet reference.

Can’t find it here?

• Applets — one reference page per applet: every screen, field and setting
• Learn — the same material as short narrated presentations you can also read
• API Reference — the REST surface, generated from the backend’s routes
• Demos & Resources — recorded demos and presentation material
• Ask a question — open an issue in BigLedger’s public support tracker. 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).