Applets and Workflows

“I saved it and nothing happened.” It turns up in more support conversations than any other question we have counted, and the answer explains how this section is organised. In most document applets, saving keeps a draft, and a draft — open to any colleague whose permission covers it — posts nothing, moves no stock and reaches no report or later document. Finalise is what sets things off, and what it sets off happens somewhere you are not looking: the stock moves in one folder, the journal lands in another, the e-invoice queue in a third.

This section has one reference page per applet, grouped into folders by the part of the business they serve. Each folder opens with a page that says whose screen each applet is, what it writes when it goes FINAL, where its figures come from and what it will not do. If you want to learn a workflow step by step, start in the guides instead; if you want one applet by name, use the Complete Applet Catalog.

What happens behind the scene when you press Finalise

Finalise is a separate call, not a save: it locks the document and queues one primary job, which fans out to follow-on jobs for the stock lines, the journal, the cashbook lines and the e-invoice queue, with the item’s cost written back onto the line afterwards (What actually happens when I press Finalise?). So a document can read FINAL and have done only part of its job: a missing default GL code never stops FINAL, and a missing receivable or payable code leaves every document that needs it FINAL with no journal, nobody told. What a document moves is fixed by its type on the server — read the name in the folder page’s table, not the one on the button — and many applets (Bank Reconciliation, MY-SST, RMA, claims, CRM) write nothing to your books at all.

Which folder answers your question

You are asking	Open	Start at
“Which document actually takes stock out?”	Sales Workflow	What each document writes when it goes FINAL
“What is the difference between a goods received note and a purchase invoice?”	Purchase Workflow	Which one to pick
Which stock document moves stock, and what Balance and Available mean	Inventory Workflow	Where the three stock figures come from
“The document is Final but it is not in the general ledger.”	Finance	What happens when you press Finalise
A customer, supplier or item is wrong on a document	Master Data	Copied when the document is raised, or read when it posts
Where the e-invoice switches are	E-Invoice	The switches are not in these applets
A member’s bill earned no points	Membership	The setting that decides whether a bill earns points
A faulty item came back for repair or a swap	RMA	Which document settles the return
A member of staff paid for something and wants it back	Claims	Meet the claim this subsystem exists for
Who may open your tenant’s administration console	External Tenant Admin	Access
A marketplace, gateway, webhook or API connection	Integrations	Whose screen it is, what moves, and what presses the button
A job that should run by itself	Platform	What runs when nobody presses a button

Where a figure on an applet screen comes from — stored when something last ran, or worked out when you look — is on each folder page (finance, purchasing, stock, e-invoice), and Stored figures and live figures has the rebuild order.

When an applet did not do what you expected

What you see	Where it is answered
“I saved it and nothing happened.”	Nothing happened
“The document is Final but it is not in the general ledger.”	Finance: when something looks wrong
The GRN is FINAL and the stock has not moved	Purchase Workflow: when a purchase looks wrong
A return finalised, the books are right and the shelf count is one out	Sales Workflow: when a sales number is wrong
“Where did this figure come from? Nothing on the screen says.”	Stored figures and live figures
“I logged in and there are no applets at all.”	When this list and your screen disagree
“An applet I read about is not on my launchpad. Why?”	Complete Applet Catalog

To prove a document did its job whatever its status says, trace it in Financial Report › Error Checking › Trace Document and, for stock, the Stock Movement Report (how you know a document moved stock); Nothing happened covers the quieter case Trace Document does not catch. What must exist before any of it posts is on Finance.

What this section will not tell you

How to learn a workflow from nothing (the guides walk it with an example), which applets your login has (the My Applets tab of the Applet Store), price or plan, or every applet: some live applets have no page yet, and the catalogue marks them not yet documented. Applets built for a single customer are left out on purpose.

Browse by area

Master Data section

Which master-data applet owns the record a document is about to read: what each one feeds into posting, pricing, tax and e-invoice, which values are copied onto a document and which are read live when it posts, which of two look-alike records to create, and where a mistake made here is reported — somewhere else, later.

Purchase Workflow section

Which purchase document or applet to use for the job — requisition to invoice, the two receiving pairs, the debit and credit notes, returns, consignment and the supplier's own windows — what each one's FINAL writes into stock, the ledger and the next document, where the purchase figures come from, and what none of them will do.

Inventory Workflow section

Which inventory applet to open for the job in front of you: what each one writes into stock, the ledger and other modules, which ones move nothing whatever their name says, and where the balance, available and report figures come from.

Sales Workflow section

Which sales document to raise, whose screen it is, and what each one writes into stock, the ledger, the cashbook and the e-invoice queue when it goes FINAL — quotation, order, delivery order, invoice, cash bill, returns, credit and refund notes — with the checks that catch a sale posted to the wrong place.

Finance section

The finance applets — which ones write to your books and which only read them, what a finalised document sets off, where each finance figure comes from, and where to look when the document is Final but not in the general ledger.

E-Invoice section

The four e-invoice applets — whose screen each one is, what each writes, which one to open for which job, and where the switches they depend on actually live.

CRM section

Which CRM applet to put a team on — contact centre, chatbot, sales leads and deals, audit engagements, events — whose screen each is, what each writes into the customer record and into sales documents (a contact, a link, a shopping cart, and nothing else), when to pick which, and what none of them will do.

E-Commerce section

The e-commerce applets — which one answers which question, why none of them posts, the three paths from an online purchase to a sales order, where each online figure comes from, what must exist first, and a check that an online order reached your books.

Membership section

The membership applets — whose screen each one is, what each writes into points, vouchers and commission, which one to open for which job, and the company setting outside them that decides whether a bill earns anything.

Claims section

Paying staff back for what they spent on the company's behalf: whose screen each claims applet is, what a claim writes when it is approved and when the cycle closes (no journal, no cashbook line, no payable), which voucher records the payment, and what will not happen on its own.

Manufacturing section

Which manufacturing applet does what — the recipe, the job order, the shop floor and the packing desk — what each one writes behind the screen, the one step that moves stock and why it carries no cost, where the production figures come from, and what to check after a job.

Human Resources section

The people applets — what this folder holds and why neither can be installed, what you run instead (the employee master, expense claims, payroll elsewhere and a monthly journal), where the wages and claim figures come from, and the checks that tell you a payroll month is in the books.

RMA section

A faulty item comes back: which RMA screen tracks it while it is repaired, swapped or sent to the supplier, why none of them moves stock or money, and which sales or purchase document has to follow so the shelf, the customer and the supplier come out right.

Delivery Installation section

Which delivery screen is whose — dispatcher, driver, office, warehouse, supplier — and what each one writes into stock, the sales document and the delivery job; when to pick which; what Fully Delivered on an invoice really measures; and what none of these screens will do.

External Tenant Admin section

The one folder for your own tenant's administration console: who may open Tenant Admin and on what authority, what an installation, a rank or a permission set changes behind the screen, how an outside accountant or auditor gets in and out, and where the console stops.

Integrations section

Whose screen each connection out of BigLedger is: marketplaces, payment gateways, LHDN and Peppol, webhooks and the REST API, another BigLedger tenant, and the clocks that drive them; what moves, on what trigger, what breaks without a message, and where each one stops.

Platform section

Whose screen is whose among the platform applets: the BigLedger-staff consoles in this folder, the user, scheduler and approval screens your own administrator uses instead, what each changes behind the screen, and which jobs run without anyone pressing a button.

Complete Applet Catalog

Every applet that exists in BigLedger, generated from the product's own applet registry — grouped by area, with a link to each one's page, how an applet reaches a login, and why one you see here may be missing from your screen.

Applet Store

Reference for the Applet Store: the platform screen where a signed-in user browses the catalogues their login has been granted and installs applets onto their own account.

2 pages and 17 sub-sections — this list is read from the folder when the site is built, so it cannot fall behind what is in it.

Complete Applet Catalog

Every applet in the product, generated from the applet registry — including the ones nobody has written up yet

Applet Store

How a login finds, installs and uninstalls an applet

Modules

The business groupings these applets are documented in