Skip to content
Companies, branches and dimensions, and what each one decides · presentation 1 of 5 · 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.

Companies, branches and dimensions, and what each one decides · presentation 1 of 5

One tenant, three companies, and the list they all share

You can decide whether a new operation is a company or a branch using the test that actually settles it…

Step 1 — Apply the test that actually settles company or branch

You can stop arguing about size.

What this step names
  1. A branch shares the company's chart of accounts
  2. Its default account mapping
  3. Its tax defaults
  4. Its e-Invoice registration with the revenue board

Step 2 — Know which mistake costs you more

You will lean the right way when the answer is genuinely unclear.

What this step names
  1. Making a company where you wanted a branch is annoying and visible…
  2. Two sets of default account mappings and two e-Invoice registrations for what…
  3. Every movement of stock or money between them has to be keyed…

Step 3 — Know where the boundary the server enforces actually runs

You know which promises about separation you can make.

What this step names
  1. When somebody's permission is targeted at one company or one branch
  2. The document listing query carries that target into its own conditions
  3. It checks the branch the document was raised at and the branch…

What the tree does not divide

Step 4 — Know the one list every company in your tenant shares

You will stop looking for a setting that is not there.

What this step names
  1. A shopper who buys at one branch and returns the item at…
  2. Found by both counters
  3. The return cannot be processed and their loyalty balance splits in two

Step 5 — Plan around it, and know the one control that does hold

You can answer the privacy question honestly.

Where this step sits
    flowchart TD
  s1["1. Apply the test that actually settles…"]
  s2["2. Know which mistake costs you more"]
  s3["3. Know where the boundary the server…"]
  s4["4. Know the one list every company…"]
  s5["5. Plan around it, and know the…"]
  s6["6. Settle the codes before you create…"]
  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 — Settle the codes before you create the first record

You have spent twenty minutes to avoid a migration.

What you do
  1. Create the first branch

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.