Skip to content
Sales you skip because a platform e-invoices them · presentation 5 of 5 · 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.

Sales you skip because a platform e-invoices them · presentation 5 of 5

How far the e-commerce reconciliation actually goes

You can say exactly what the Reconciliation (Sales) screens do and do not do for GadgetSphere Online…

Step 1 — Meet the two registers this screen pairs

You will know what the screen is trying to do.

Where this step sits
    flowchart TD
  s1["1. Meet the two registers this screen…"]
  s2["2. Know which of the two fills…"]
  s3["3. Know that nothing fetches the other…"]
  s4["4. Know the four keys…"]
  s5["5. Do not press Auto Match on…"]
  s6["6. Reconcile the way that actually works…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s1 here;

Step 2 — Know which of the two fills itself

You will know the half that works.

What this step names
  1. A processor watches every finalisation and writes a row into the sales…
  2. Belongs to a company enabled for e-invoicing
  3. Is a sales document type
  4. Carries the skip flag

Step 3 — Know that nothing fetches the other half

You will stop waiting.

Where this step sits
    flowchart TD
  s1["1. Meet the two registers this screen…"]
  s2["2. Know which of the two fills…"]
  s3["3. Know that nothing fetches the other…"]
  s4["4. Know the four keys…"]
  s5["5. Do not press Auto Match on…"]
  s6["6. Reconcile the way that actually works…"]
  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 — Know the four keys, and the one that can never agree

You will know what would happen even if the rows arrived.

What this step names
  1. The matcher pairs on four values: reference number
  2. Transaction date
  3. Amount and the buyer's identification number
  4. It applies each test only when the incoming row carries that value

Step 5 — Do not press Auto Match on the sales screen

You will avoid an expensive misunderstanding.

Where this step sits
    flowchart TD
  s1["1. Meet the two registers this screen…"]
  s2["2. Know which of the two fills…"]
  s3["3. Know that nothing fetches the other…"]
  s4["4. Know the four keys…"]
  s5["5. Do not press Auto Match on…"]
  s6["6. Reconcile the way that actually works…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Reconcile the way that actually works today

You will have a method that proves the same thing without the screen.

What you do
  1. Take the skipped documents total from your monthly report — the figure you read…
  2. Keep the comparison in your month-end file and do not expect these ten screens…

NarrationSlide 1 of 7

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.