Tutorials
“Do I have to raise a sales order before I can invoice?” is the question the old Creating Your First Invoice page was reaching for, and the one to start from if you came here looking for it. The short answer is no, and the page that answers it in full is Standard Sales Workflow. This folder itself holds no tutorials any more; it stays so that old links still land somewhere useful.
Where the walkthroughs actually are
Four pages on this site are written as start-to-finish tutorials. None of them is in this folder.
| You want to… | Read |
|---|---|
| Take a customer from quote to money in the bank, including your first invoice | Standard Sales Workflow |
| Take a supplier from purchase order to payment | Standard Procurement Workflow |
| Read and write BigLedger data from your own code | Developer getting started |
| Build an applet | Applet development: getting started |
Everything else that walks you through a job is in the Guides, and if you would rather listen than read, the narrated presentations are in Learn.
Why your first invoice is two pages, not one
Pressing Finalise is the start of the job, not the end: it records the invoice as final and queues the rest. A background job posts the journal and moves the stock, and a separate one routes the invoice to LHDN — individually, inside the month’s consolidated e-invoice, or into a pool when something LHDN needs is missing. So the walkthrough is two pages:
- Standard Sales Workflow — the invoice, what it posts and how you see it posted (field by field: the Sales Invoice applet reference).
- E-Invoice Pools & Submission Routing — what happens on the way to LHDN; a document parked in a pool is moved or resubmitted in the My E-Invoice Admin applet.
A walk-in sale at the counter needs neither: Cash Sales does it with one document, the cash bill. The mechanism itself is narrated in Finalise: what the button starts, and what it writes.
Before your first invoice will post
Two things must exist first, and missing either shows up only after you finalise:
- Default GL codes on the company — without them the invoice still finalises, but its journal fails (no customer-account default) or posts short (no sales or tax default): Chart of Accounts Setup.
- MyInvois set up for the company, if you e-invoice — and its LHDN environment set first, because a blank one means the sandbox: MyInvois setup.
For a brand-new company, Getting Started and the series Set up a new company end to end put these in order.
When something looks wrong
| What you see | Where it is answered |
|---|---|
| “I finalised the invoice and nothing was submitted to LHDN.” | Understanding E-Invoice Statuses — almost always queued, not stuck |
| You raised a sales order and your stock did not move. | Standard Sales Workflow — an order never moves stock |
| “Every sales invoice finalises, but none of them post, and the trace names a missing default GL code.” | Chart of Accounts Setup |
An old bookmark to /tutorials/first-invoice/ or /tutorials/month-end-closing/ | They now open the sales workflow and the Month-End Closing Process |
How you know your first invoice worked
On the invoice’s Posting tab, Journal and Inventory both read posted; Inventory posted with Journal empty means the posting failed (Standard Sales Workflow, What success looks like). The e-invoice is a separate, later check: Understanding E-Invoice Statuses.
What this folder will not give you
No tutorials of its own (new walkthroughs go into the Guides or Learn), no video walkthroughs — the nearest thing is the narrated presentations in Learn — and no single walkthrough from keyboard to LHDN, because the posting and the e-invoice finish at different times.
Next
Start with Standard Sales Workflow.