Skip to content

Frequently Asked Questions

71 questions, grouped by topic. Every one of them was asked by a customer — we took them from the support desk’s own registry of diagnosed patterns rather than imagining what a reader might want to know, and the order within each topic is how often the desk had to answer it.

The answers here are deliberately short. Two or three sentences and a link: enough to tell you whether you are in the right place, and then the page that actually owns the explanation. If you want the long version, follow the link — it is maintained; this page is an index.

Start here: the five we are asked most

  1. Where did this figure come from? Nothing on the screen says.
  2. I saved it and nothing happened.
  3. Why can’t I edit this? The field is greyed out.
  4. LHDN rejected it. Where do I find out why?
  5. Stock Availability shows 50 physical but 0 available. Where did it go?

Notice what they have in common. Four of these five are not how do I do this — they are why is this what it is, or why did nothing happen. That is the shape of the questions we get, and it is why this site spends more effort explaining than instructing.

By topic

Numbers that do not agree

Two figures that should be the same, and are not. This is the commonest family of question we get by a wide margin, and the answer is nearly always the same shape: one of the two numbers was worked out once and written down, and the other is being worked out now.

Stock figures and costing

Stock questions are rarely about stock. They are about a number — an available quantity, a unit cost, a margin — and about which document moved it.

Documents, drafts and posting

Almost every nothing happened report turns out to be one of three things: it is still a draft, it is a document type that was never meant to post, or it finalised and the posting failed somewhere you cannot see.

Selling, pricing and the till

Selling questions cluster around two things: which of several prices the system chose, and which document actually did something.

Money in and money out

Receipts and payments are the part of the ledger customers touch most often, and the part where a small mis-step takes the longest to find.

E-Invoice and MyInvois

E-invoice is the second largest family of question we get, and most of it is one sentence: there is no error message, so something must be broken. Usually nothing is broken — the document is queued.

Buying and receiving

There is more than one way to buy something in BigLedger, and the flexibility is deliberate — each path exists because a real business needed it.

Access, branches and companies

Most access questions are one mechanism seen from different screens: a permission set is scoped to a company, a branch or a location, and a set with no target confers everything.

The platform, the API and other systems

What the platform is made of, and how other systems reach it.

Not here?

An entry only appears on this page when a page on this site answers it. Where a real, repeatedly-asked question has no page behind it yet, we record it as a documentation gap rather than write an answer we cannot stand behind — so the absence of a question here is information too.

For a problem with a message on the screen, start at Troubleshooting. For a figure that does not agree with another figure, start at When two numbers don’t tally. For a specific screen, the applet reference documents every one.

Related documentation