Skip to content

Troubleshooting

This page sends you to the real message and the real fix: documents that will not finalise or post, serial, batch or bin quantities that do not match the line, records you cannot find, numbers that look wrong, and reports that disagree. If you are stuck on a posting problem, start with the two diagnostic screens.

Start here: which kind of problem is it?

Documents that will not finalise

A customer blocked for credit, and a date in a closed period, are on Stuck documents and missing records; the commonest line-level refusal is here.

Serial, batch or bin quantities do not match the line

What you see: the finalise is refused and the offending line is marked, naming the item.

Fix: complete that line’s Serial Number, Batches or Bin sub-tab so the allocation equals the line quantity. If a delivery arrived short, change the line quantity — do not pad the allocation.

Nothing happened

A document that is FINAL with no journal behind it has its own page: The invoice is FINAL but it is not in the ledger. Finalised, and nothing happened takes the rest: a document type that does not post, MISSING_CASHBOOK on a receipt, payment or transfer, a draft that reaches no other screen, and a price rule that does nothing.

Numbers that look wrong

When two figures that should agree don’t, each page below opens with a check:

Two reports disagree

They usually read different document sets. The purchase report, for instance, reads only finalised purchase invoices and returns — no orders, no GRNs, no drafts. Check what each reads on its applet page before assuming one is wrong.

A Trial Balance that comes back empty, and an available quantity lower than the balance, are on Stock and report figures.

Stock, finalised documents, printed paper and loyalty points

Three module pages answer these too: the same serial sold twice, or a serial showing quantity 2 — Serial numbers; cannot final — not enough stock for bundle item, or a bundle count that makes no sense — Bundles and grouped items; a document discount that has its own GL account, two header totals that do not add up, or a percentage that vanished — Group discount.

Where to ask

If none of this fixes it, open an issue at BigLedger-Support/public. Anyone can read the tracker, so keep your tenant code and your own records out of the post. Include:

  • the applet you were in;
  • the document type and its posting status — not its number;
  • the exact message, copied rather than paraphrased;
  • what you expected to happen.

A question that needs your tenant or a document number goes to your BigLedger contact (see Support).

Related documentation