Skip to content
Set up a new company end to end · presentation 6 of 8 · 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.

Set up a new company end to end · presentation 6 of 8

The mapping that decides whether a document posts

You can map GadgetSphere's default GL codes, name the two different failures a gap produces and why only one of them names the missing…

Step 1 — Find the tab, which is not where you would look

You will stop searching the Organisation applet.

Screen capture pending the demo tenant

Chart of Account applet, Companies, the Default GL Codes tab with its seven sub-tabs

Step 2 — Understand what you are actually mapping

The tab will make sense rather than looking like a wall of drop-downs.

Where this step sits
    flowchart TD
  s1["1. Find the tab, which is not…"]
  s2["2. Understand what you are actually mapping"]
  s3["3. Map the roles a retailer actually…"]
  s4["4. Know when the failure appears…"]
  s5["5. Learn the two different failures…"]
  s6["6. Know that a half-mapped link is…"]
  s7["7. Map the month-end pairs before your…"]
  s8["8. Check the side each account sits…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  s7 --> s8
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — Map the roles a retailer actually uses

GadgetSphere can post.

What you do
  1. Work the sub-tabs in order and map what a retailer needs, leaving the rest
  2. Press Save once on the company header, which writes every changed key together

Step 4 — Know when the failure appears, which is not when you make it

You will understand why this mistake survives testing.

Where this step sits
    flowchart TD
  s1["1. Find the tab, which is not…"]
  s2["2. Understand what you are actually mapping"]
  s3["3. Map the roles a retailer actually…"]
  s4["4. Know when the failure appears…"]
  s5["5. Learn the two different failures…"]
  s6["6. Know that a half-mapped link is…"]
  s7["7. Map the month-end pairs before your…"]
  s8["8. Check the side each account sits…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  s7 --> s8
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Learn the two different failures, because only one names the gap

You will read a posting error correctly the first time.

What this step names
  1. Purchase
  2. Tax
  3. Rounding
  4. Charges or stock-balance line
  5. BigLedger looks for a GL code on the line
  6. Then on the document header

Step 6 — Know that a half-mapped link is worse than no link

You will check one thing that almost nobody checks.

Where this step sits
    flowchart TD
  s1["1. Find the tab, which is not…"]
  s2["2. Understand what you are actually mapping"]
  s3["3. Map the roles a retailer actually…"]
  s4["4. Know when the failure appears…"]
  s5["5. Learn the two different failures…"]
  s6["6. Know that a half-mapped link is…"]
  s7["7. Map the month-end pairs before your…"]
  s8["8. Check the side each account sits…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  s7 --> s8
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;

Step 7 — Map the month-end pairs before your first month-end

Your first close will produce the journals you expect.

Where this step sits
    flowchart TD
  s1["1. Find the tab, which is not…"]
  s2["2. Understand what you are actually mapping"]
  s3["3. Map the roles a retailer actually…"]
  s4["4. Know when the failure appears…"]
  s5["5. Learn the two different failures…"]
  s6["6. Know that a half-mapped link is…"]
  s7["7. Map the month-end pairs before your…"]
  s8["8. Check the side each account sits…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  s7 --> s8
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s7 here;

Step 8 — Check the side each account sits on before you save

You will have caught the error that never raises one.

What this step names
  1. Read the mapping back once and check the obvious pairs — output…
  2. Input tax at an asset
  3. The debtor account at an asset
  4. The creditor account at a liability
  5. Stock control at an asset

NarrationSlide 1 of 9

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.