Skip to content
Learn
Presentations P-00000 to P-00999
Where every number on the report comes from, and when it was read

Where every number on the report comes from, and when it was read

Prove the month: the Discrepancies Report · presentation 2 of 4 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Prove the month: the Discrepancies Report · presentation 2 of 4

Where every number on the report comes from, and when it was read

You can say, for any figure on the four tabs, which table it was read from, which date and status rules selected it…

The two sides

Step 1 — Read your own side: five filters on the document table

You will know exactly which of your documents the ERP Transaction Summary counted.

What this step names
  1. It reads your document table and keeps a document when five things…
  2. It is not deleted
  3. Its document date falls inside your two chosen days
  4. It is not marked Skip E-Invoice
  5. Its currency is the company's own currency

Step 2 — Read the e-invoice side: a date, then a sort by status

The IRB Audit Summary will mean something precise.

Cancelled

A cancelled header goes to the Cancelled figure

Step 3 — Know which month a header belongs to

A whole class of "the sides don't match" will resolve itself.

Where this step sits
    flowchart TD
  s1["1. Read your own side…"]
  s2["2. Read the e-invoice side: a date…"]
  s3["3. Know which month a header belongs…"]
  s4["4. See how a consolidated e-invoice is…"]
  s5["5. Read the gap tab as two…"]
  s6["6. Make the two sides meet…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — See how a consolidated e-invoice is counted

The document counts on the two summaries will be comparable.

Where this step sits
    flowchart TD
  s1["1. Read your own side…"]
  s2["2. Read the e-invoice side: a date…"]
  s3["3. Know which month a header belongs…"]
  s4["4. See how a consolidated e-invoice is…"]
  s5["5. Read the gap tab as two…"]
  s6["6. Make the two sides meet…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Read the gap tab as two exact tests

"missing" will have a definition.

What this step names
  1. The first direction
  2. Exists in ERP and missing in e-invoice
  3. Takes your side's documents — with the skip filter deliberately left off…
  4. Keeps those that have neither an e-invoice header pointing at them nor…

Making the sides meet

Step 6 — Make the two sides meet, one line per document type

You can explain 37,912 against 38,000 in a sentence.

  • Take one document type — cash bills for the retail company
  • Start with the ERP count, 38,000

37,912

After this step you can explain 37,912 against 38,000 in a sentence

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on
The question the Discrepancies Report can answer, and the one it cannot — transcriptWhere every number on the report comes from, and when it was read — transcript