Three registrations, one schedule: what setting e-invoice up three times actually means — 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 is about to bring the second and third company of a group onto e-invoice and wants to know what genuinely repeats. In about eleven minutes you will know which work is done three times because it must be, which per-company choices quietly reach the other companies, and which things belong to the tenant however many companies sit in it.

Step 1 — Treat each company as its own taxpayer with its own destination

After this step you will not assume the second company inherits anything from the first. Each company has its own tax identification number, its own registration and service tax numbers, its own address — and its own LHDN environment. That last one is the trap for a group. The retail company was set up carefully and points at production. The online company is enabled a month later, its environment left blank, and a blank is read as the sandbox: its documents come back Valid, with an identifier and a QR code, having been filed with nobody. Nothing on either company’s screen says the two are pointed at different systems. A small minority of tenants are in exactly that state today, nine of the ninety.

Reference: Organization — Company E-Invoice tab

Step 2 — Count the intermediary rows in pairs

After this step you will know how many of something you have never seen. Behind each company sit the intermediary rows that hold its token: one for the sandbox, one for production, configured by your BigLedger contact once you have appointed BigLedger on the MyInvois portal for that company’s tax number. Three companies means six rows, and the token in each is minted on behalf of that one company. The failure message is precise about it: no intermediary config found for this company in that environment. When the third company stops submitting, do not look at the first one’s working configuration for comfort; it says nothing about the third. Appointment on the portal, and the rows behind it, are per company and per environment.

Reference: My E-Invoice Admin Applet — Configuration

Step 3 — Watch one company’s e-mail switch reach the others

After this step you will read a per-company switch as a tenant decision. Send Email To Buyer is set per company, but the queue that sends the validated PDF is one queue for the tenant, worked oldest-ten-first. On a tenant with the schedule row, every validated individual e-invoice is queued before the switch is read; a company with the switch off leaves its rows untouched, at retry zero, and they are selected again on every tick. Once ten of those are the oldest rows in the queue, nothing behind them is ever reached — including the retail company’s rows, whose switch is on. So the online company deciding it does not want the e-mail can stop the retail company’s customers receiving theirs.

Reference: My E-Invoice Admin Applet — How the queue moves, and how it stops

Step 4 — Accept what is the tenant’s

After this step you will stop asking for per-company versions of three things. The schedule is the tenant’s: a new tenant is given one set of timed jobs, which of them exist is decided per tenant, and no company owns a job or a run day of its own. The admin applet’s settings are the tenant’s: hide the single-general pool from the menu and it is hidden for every company’s staff, because the keys are saved once for everyone who can open Settings. And the pools are the tenant’s: there is one Batch Pool holding every company’s receipts, which you filter by company rather than open per company — and a user’s company-scoped permission does not narrow it, the filter does.

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

Step 5 — Use the Disable switches per company, knowing both halves

After this step you can switch consolidation off for one company without misunderstanding what you did. The distribution company sells only to businesses and wants every sale reported individually; its Disable Consolidated Submission switch takes Consolidated out of the Submission Type list on every one of its documents, while the retail company keeps the option. That is real and it is per company. Its limit is equally real, and it was ruled rather than guessed: the switch governs what a person may choose, a default set anywhere else still applies, and the consolidation run writes Consolidated onto documents itself without consulting it. Set the switch, and still read the consolidation report for that company at month end.

Reference: Organization — Company E-Invoice tab

Step 6 — Run three reports, not one

After this step your month-end check will match the shape of the group. The Discrepancies Report is created for one company and one month; it refuses to run without a company. So the group’s month is three reports, each comparing that company’s finalised sales against the e-invoice records held for them, and the ghost-document check inside it is per company too. Hand each company’s clerk their own, and read the environment field on each company before you read any of the three, because a report of Valid e-invoices filed in the sandbox is a clean report of nothing. Three companies, three environments, three reports: the shape of the work is the shape of the group.

Reference: My E-Invoice Admin Applet — 8. Monthly Report → Discrepancies Report

How the steps fit together

    flowchart TD
  s1["Step 1 — Treat each company as its own taxpayer with its own destination"]
  s2["Step 2 — Count the intermediary rows in pairs"]
  s3["Step 3 — Watch one company's e-mail switch reach the others"]
  s4["Step 4 — Accept what is the tenant's"]
  s5["Step 5 — Use the Disable switches per company, knowing both halves"]
  s6["Step 6 — Run three reports, not one"]
  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: The customer the whole group shares, and whose e-invoice it is · Back to the series · Play this as a presentation