One tenant, three companies, twenty-two branches: where each e-invoice fact lives — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for whoever runs the books for a group — GadgetSphere’s three companies and twenty-two branches in one tenant — and has been asked whether e-invoice is set up once or three times. In about ten minutes you will have a three-row map that any setting the platform shows you fits into.

Step 1 — Start from what LHDN can see

After this step you will know why the company is the level that matters most. The tax authority does not know what a tenant is and does not know what a branch is. It knows taxpayers, and in BigLedger a taxpayer is a company record: its tax identification number, its registration and service tax numbers, its industry code and its address. Every e-invoice the group sends carries one company’s identity as the supplier, copied from that record — an individual e-invoice from the company on the document, a consolidated one from the company whose receipts it rolls up. So whatever the group shares between its companies, the thing LHDN receives is always one company’s document, and the identity on it belongs to that company alone.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

Step 2 — Then what the tenant holds exactly once

After this step you will stop looking for per-company copies of things that have none. The customer list, the supplier list and the item list are one list for the whole tenant, by design — a shopper who buys in one branch and returns the item in another has to be one record, found by both counters. With that list travel every customer’s tax number, identity, e-invoice address and skip flag. The item classification list, the e-invoice unit list and the tax-code list are one list each. The schedule is the tenant’s: one set of timed jobs, including both consolidation runs. And the e-invoice admin applet’s settings, pools and listings are one screen over everything, filterable by company but never divided by it.

Reference: Organization — What the organisation tree does not divide

Step 3 — Then what a branch is to an e-invoice

After this step you will be able to say in one sentence what a branch does here. A branch is a place written on the document — a column on the header and on every line, beside the company and the profit centre. The e-invoice pipeline reads exactly one branch setting, Skip E-Invoice, which silences every document raised there. Beyond that it copies the branch code and identifier onto each individual e-invoice, so the branch is there to filter on, and it leaves them off a consolidated e-invoice built by the common run, so under that run a branch cannot be found on the finished document at all. Nothing else on the branch record — its timezone, its tax registration number, its default printable — is consulted.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

Step 4 — Answer “do we set it up three times?”

After this step you can give the answer with its shape. Yes for the company tab: the identity, the LHDN environment, the intermediary rows, the status switch, the printable formats and the e-mail switch are done once per company, so GadgetSphere does that work three times and runs the thirty-second success check three times. No for the lists: a customer entered for the retail company is already the online company’s customer, and an item classified once is classified for all three. No for the schedule: there is one, and it serves every enabled company. And nothing at all for the branches: twenty-two branches need twenty-two records for stock and cash, and not one e-invoice setting among them.

Reference: MyInvois Setup Guide — What success looks like

Step 5 — See that one schedule serves three companies, and the gate is still per company

After this step a common misunderstanding will not cost you a month. The consolidation run is a tenant job, and it groups whatever is waiting by company first and document type second, producing one consolidated e-invoice per company per document type each time it fires. You cannot give the online company a different run day from the retail company; they share the timetable. What is per company is the gate in front of the run: a company whose e-invoice status is disabled contributes nothing to any pool, so switching one company off does not slow the others, and switching one on needs no new schedule. Roughly a quarter of the customer base runs two or more enabled companies under a single timetable in exactly this way.

Reference: My E-Invoice Admin Applet — 3. Pools — what the buttons do

Step 6 — Prove the map in thirty seconds

After this step you will have seen all three levels on one screen. Open the To IRB E-Invoice listing in the admin applet. Every company’s e-invoices are in the one list — that is the tenant level. Filter by company code and open one individual e-invoice from each company: the supplier block changes, and it is that company’s own record — the company level. Now read the branch column: it is filled on the individual e-invoices and blank on a consolidated one built by the common run — the branch level, present by copy and absent by design. If those three observations hold, the map holds for your tenant, and every setting you meet from now on goes into one of the three rows.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

How the steps fit together

    flowchart TD
  s1["Step 1 — Start from what LHDN can see"]
  s2["Step 2 — Then what the tenant holds exactly once"]
  s3["Step 3 — Then what a branch is to an e-invoice"]
  s4["Step 4 — Answer 'do we set it up three times?'"]
  s5["Step 5 — See that one schedule serves three companies, and the gate is still per company"]
  s6["Step 6 — Prove the map in thirty seconds"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Next: Three registrations, one schedule: what setting e-invoice up three times actually means · Back to the series · Play this as a presentation