Skip to content

Basic Operations

Almost everything in this section is about items, because items are what every other part of BigLedger reads. A sales order, a purchase invoice, a stock count, a price rule and an e-Invoice line all point at an item record. Get those right and the rest behaves.

Read these in this order

The two things that explain the whole section

1. Every item has two records. The document item is the commercial definition — price, tax, e-Invoice classification, what a document line can pick. The inventory item is the stock-keeping record that ledgers, balances, serial numbers and costing layers hang off.

They are linked, and creating a Basic Item in Doc Item Maintenance creates and links both. An item created on the inventory side alone cannot go on any document.

2. Three fields on an item are permanent. The item code, the item type and — for a Basic Item — the sub item type that decides how quantity is tracked. There is no repair; there is only obsolete-and-replace. Which is why the first page in the list above is about deciding, not doing.

Where the rest of your master data lives

This section covers items. The other master data you will need is documented alongside the applet that owns it:

What success looks like

You are through this section when you can answer:

  1. Which applet do you create a new product in, and why that one? (Doc Item Maintenance — it creates and links both records.)
  2. Which three fields on an item are permanent? (Item code, item type, sub item type.)
  3. What does it mean when an item’s FI Item Code is blank? (It has no document-item twin and cannot go on any document.)

Common mistakes

What goes wrongThe fix
Creating items in the Inventory appletCreate them in Doc Item Maintenance
Choosing an item type in a hurryIt is permanent — decide first
Serialising everything “to be safe”Every movement then needs serial entry
Leaving the e-Invoice classification on the tenant defaultSet it at creation; the failure surfaces much later
Leaving items uncategorisedCategory-based price rules match nothing, silently
Deleting an item with historySet it Inactive or Obsolete

Related documentation