Get your customers ready for e-invoice · presentation 4 of 6 · 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.

Get your customers ready for e-invoice · presentation 4 of 6

Make a broken record impossible to save

You can say what BigLedger already refuses to save on a customer and what it happily lets through…

Step 1 — Know what the save already refuses

You will know exactly how much protection you are starting with, which is less than you would hope.

Where this step sits

    flowchart TD
  s1["1. Know what the save already refuses"]
  s2["2. Make the identity number mandatory"]
  s3["3. Sort out the phone number…"]
  s4["4. Make sure the people filling this…"]
  s5["5. Accept that nothing checks the number…"]
  s6["6. Prove the guard rails are up"]
  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 — Make the identity number mandatory

A clerk cannot create a customer with no identity number at all.

Turn it on, and tell the branches first…

Screen capture pending the demo tenant

Application Settings with the Mandatory Fields panel open and the identity or registration number switch turned on

Step 3 — Sort out the phone number, and know it misbehaves

Your contact numbers will be present, and you will not be confused by a screen that disagrees with itself.

What you do

Set it to whichever value gives you the behaviour you need on the screen…

Step 4 — Make sure the people filling this in can see the tabs

Nobody will be unable to finish a record for reasons they cannot see.

What this step names

Every edit tab
The E-Invoice tab and the Address tab included
Has a hide switch that is off by default
A matching show permission

Step 5 — Accept that nothing checks the number itself

You will stop treating a saved record as evidence that it is correct.

Where this step sits

    flowchart TD
  s1["1. Know what the save already refuses"]
  s2["2. Make the identity number mandatory"]
  s3["3. Sort out the phone number…"]
  s4["4. Make sure the people filling this…"]
  s5["5. Accept that nothing checks the number…"]
  s6["6. Prove the guard rails are up"]
  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 — Prove the guard rails are up

You will know the settings took, rather than assuming it.