Skip to main content

Review COGS postings

Cost of goods sold records what the stock you sold cost you. Without it, revenue lands with no cost against it and your margin is meaningless.

Needs organisation-admin access.

What to look for​

Entries waiting on configuration. A COGS entry is recorded when stock moves, but its account is not always resolved at that moment. If the configuration is missing, the entry waits — it is not lost, but it is not posted either.

A steady number waiting almost always means one account is unmapped, not many separate problems. Map it and the group clears.

Steps​

  1. Review the COGS entries, including any waiting.
  2. If entries are waiting, check Issues for what configuration they need.
  3. Map the account.
  4. The waiting entries release themselves — nightly, or on the next live attempt.

Why entries wait rather than failing​

Stock has to move when the warehouse says it moved. Blocking a dispatch because an account is unmapped would be the wrong trade: the goods have physically gone, and refusing to record that does not un-send them.

So the movement is recorded truthfully and the accounting catches up. See how COGS works.

Checking the cost looks right​

The cost is the weighted average cost of the stock that moved, at the point it moved — what you actually paid across the receipts making up that stock, not the latest price.

A cost that looks wrong is usually a receiving problem rather than an accounting one: stock received at the wrong price, or received without a cost at all.

Timing matters​

Revenue and its cost belong in the same period. Entries sitting unposted across a period end are the case worth caring about, because that is when both periods end up wrong.

Worth checking before a period closes rather than after.

Count variances are handled the same way — recorded as subledger entries, resolved when configuration allows, surfaced in the same queue.