Skip to content
Read a rejection and fix it · lesson 4 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 — Find out which record was actually read

You will stop correcting records that were never consulted.

What this step names
  1. First
  2. An e-invoice buyer block typed directly onto the sales document — if…
  3. Those details are used exactly as typed
  4. The customer record is never read at all

Step 2 — Understand the half-filled block

You can explain the most baffling rejection in e-invoicing.

  • Fill in one and the other seven are sent blank…
Screen capture pending the demo tenant

The sales document's e-invoice buyer block with a single field filled in and the rest empty, beside the customer record showing those same fields correctly populated

Step 3 — Know which address goes

An address rejection will not send you through six records looking for the offending one.

Where this step sits
    flowchart TD
  s1["1. Find out which record was actually…"]
  s2["2. Understand the half-filled block"]
  s3["3. Know which address goes"]
  s4["4. Correct the customer properly"]
  s5["5. Let BigLedger fetch what it can"]
  s6["6. Correct many customers in one pass"]
  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 — Correct the customer properly

The customer record is right, not merely different.

  • Open the customer in the Customer applet and go to its E-Invoice tab
  • Look the tax number up on the MyInvois portal rather than accepting whatever was…
Screen capture pending the demo tenant

The Customer applet's E-Invoice tab with the buyer's name, tax number, identity type and number, and the e-invoice address filled in

Step 5 — Let BigLedger fetch what it can

You will stop typing numbers the system can find for itself.

Where this step sits
    flowchart TD
  s1["1. Find out which record was actually…"]
  s2["2. Understand the half-filled block"]
  s3["3. Know which address goes"]
  s4["4. Correct the customer properly"]
  s5["5. Let BigLedger fetch what it can"]
  s6["6. Correct many customers in one pass"]
  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 — Correct many customers in one pass

A hundred bad tax numbers is one upload rather than a hundred records.

What you do
  1. Go to Tools, then Bulk Tin Validation
  2. Download the template from the screen, fill it in, choose the matching delimiter…

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.