Skip to content
Learn
Presentations P-00000 to P-00999
What a supplier login shows, and what must be true first

What a supplier login shows, and what must be true first

Give your suppliers a login to your matching results · presentation 1 of 3 · 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.

Give your suppliers a login to your matching results · presentation 1 of 3

What a supplier login shows, and what must be true first

You can say what a supplier sees and can change through the AP Automation Supplier Access applet…

What the login is

Step 1 — Know what your supplier will see

You will know what a login gives a supplier, and what it does not.

Where this step sits
    flowchart TD
  s1["1. Know what your supplier will see"]
  s2["2. Get the matching running before anyone…"]
  s3["3. Make your receipts matchable first"]
  s4["4. Give every field on the row…"]
  s5["5. Keep the jobs the login does…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s1 here;

Step 2 — Get the matching running before anyone signs in

You will know why a new login can open onto an empty screen.

What you do
  1. Look at your own E-invoice Summary in the AP Automation applet

Step 3 — Make your receipts matchable first

The rows your supplier sees will say matched where the goods really were received.

What this step names
  1. The matcher compares the delivery-order number on their e-invoice with the number…
  2. Not the External Delivery Order box
  3. It compares amounts with no tolerance

Who does what

Step 4 — Give every field on the row an owner

Each field on a row will have one owner.

Where this step sits
    flowchart TD
  s1["1. Know what your supplier will see"]
  s2["2. Get the matching running before anyone…"]
  s3["3. Make your receipts matchable first"]
  s4["4. Give every field on the row…"]
  s5["5. Keep the jobs the login does…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Keep the jobs the login does not do

You will know which work stays with people.

Where this step sits
    flowchart TD
  s1["1. Know what your supplier will see"]
  s2["2. Get the matching running before anyone…"]
  s3["3. Make your receipts matchable first"]
  s4["4. Give every field on the row…"]
  s5["5. Keep the jobs the login does…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

NarrationSlide 1 of 8

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
Pair it by hand, and prove nothing received was left unbooked — transcriptWhat a supplier login shows, and what must be true first — transcript