Floemdata
BI & Reporting

Net Sales: Returns and Cancellations Counted Once

From gross to net sales: how returns and cancelled documents distort the number, checks that prevent double counting, and Floemdata's real status.

Floemdata · · 4 min read
A solid square missing two corner pieces, with the removed pieces drawn as dashed outlines beside it

At month end the sales report shows 1,000,000 and accounting says 940,000. The gap often comes from returns and cancellations either not being deducted at all or being deducted twice. The figures in this post are for illustration only; the example is fictional and belongs to no real company.

Gross, net and the items between

  • Gross sales: the total of the sales invoices issued.
  • Returns: the credit note or return invoice issued for goods the customer sent back. It reduces sales.
  • Cancellations: a document treated as void because it was issued in error. It should behave as if it never sold anything.
  • Discounts: discounts given on the line or at the end of the document; it should also be clear whether the report includes them in the net figure.

How double counting happens

  • A cancelled invoice stays in the report and the document that reverses it is deducted like a return: the cancellation reduces twice, or not at all.
  • A return exists as a negative row in the sales table and is also subtracted from a separate returns report: the same return is deducted twice.
  • A return is deducted in the month of the original invoice rather than the month it arrived: the net figure of two months keeps shifting. Which one is chosen should be written down.

Four checks

  • Find out how cancelled documents are flagged in the source system and write the report filter accordingly.
  • Decide whether returns are stored as negative rows or in a separate column; do not do both.
  • Rebuild gross - returns - cancellations = net by hand for one month.
  • Compare the report's net sales with the net movement of the sales account in accounting.

Where Floemdata stands

Floemdata's Silver layer does not take sales documents whose cancellation flag in SAP Business One is CANCELED = 'Y'. The Gold sales movement table is kept at line level and return invoices appear as negative rows. For each month Gold also compares its own net sales with the net credit of the sales accounts in the journal entries, and marks the month as matching when the difference is below one percent of the sales amount.

Not verified: we did not check, against an independent SAP source, what flag the counter-document has that SAP B1 creates when it cancels an invoice, nor whether that document passes the filter above; the code filters only the value 'Y'. Whether these counter-documents cause double counting should be tested in a real SAP environment.

To start, write last closed month's gross, returns, cancellations and net into a table and compare with accounting. Questions are welcome at info@floemdata.com or via Floemdata.

← All guides