Skip to content
Reconcile supplier e-invoices against your purchase documents · lesson 7 of 7 · for the whole-system operator — you run the books Read the full lesson · Back to the course

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another — or read the full lesson, which carries the same steps, the same audio and the whole transcript.

Step 1 — Name what builds your side without you

You know the worklist maintains itself.

What this step names
  1. How you know it ran is direct and immediate…
  2. Open PD Matching Q.
  3. The row is there with its document number
  4. Supplier
  5. Date
  6. Amount

Step 2 — Name what runs in the other console

You can describe AP Automation's automation without naming a screen.

Where this step sits
    flowchart TD
  s1["1. Name what builds your side without…"]
  s2["2. Name what runs in the other…"]
  s3["3. Let the result go out to…"]
  s4["4. Name the places where nothing tells…"]
  s5["5. Know the one action that does…"]
  s6["6. Have last month's proof generated…"]
  s7["7. Run the thirty-second check that covers…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — Let the result go out to your suppliers by itself

You have the one thing in this area that tells somebody something without anyone opening a screen.

Where this step sits
    flowchart TD
  s1["1. Name what builds your side without…"]
  s2["2. Name what runs in the other…"]
  s3["3. Let the result go out to…"]
  s4["4. Name the places where nothing tells…"]
  s5["5. Know the one action that does…"]
  s6["6. Have last month's proof generated…"]
  s7["7. Run the thirty-second check that covers…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — Name the places where nothing tells you anything

You know what your own habits must cover.

Where this step sits
    flowchart TD
  s1["1. Name what builds your side without…"]
  s2["2. Name what runs in the other…"]
  s3["3. Let the result go out to…"]
  s4["4. Name the places where nothing tells…"]
  s5["5. Know the one action that does…"]
  s6["6. Have last month's proof generated…"]
  s7["7. Run the thirty-second check that covers…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Know the one action that does not exist here

You will not look for a button that was never built.

What this step names
  1. If you need to reject one
  2. It happens on the MyInvois portal or on that supplier's own buyer…
  3. BigLedger will never learn that you did it

Step 6 — Have last month's proof generated, and read it correctly

Your month-end starts with a report you did not build.

Screen capture pending the demo tenant

Monthly Report, Discrepancies Report, the IRB Audit Summary tab with the From Supplier (Matched) column reading zero against every document type

Step 7 — Run the thirty-second check that covers the gap

You have the routine that sits exactly where the automation stops.

Where this step sits
    flowchart TD
  s1["1. Name what builds your side without…"]
  s2["2. Name what runs in the other…"]
  s3["3. Let the result go out to…"]
  s4["4. Name the places where nothing tells…"]
  s5["5. Know the one action that does…"]
  s6["6. Have last month's proof generated…"]
  s7["7. Run the thirty-second check that covers…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s7 here;

Left and right arrows, or the space bar, move between slides. Play and pause belong to you — nothing moves on by itself unless you tick the box above.