The fields on a new company's E-Invoice tab that switch something on, and the four that do not — transcript

Presentation 2 of 4 in Set up MyInvois and Peppol for a new company · about 10 minutes · for the whole-system operator — you run the books.

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 filling in the E-Invoice tab of a company that was created this morning, and would like to spend their afternoon on the fields that matter. In about ten minutes you will be able to sort that tab into three piles.

Step 1 — Start with the one field that is a gate

After this step you will know which field is different in kind from all the others. E-invoice status is not a preference, it is a gate. When a document is finalised, BigLedger asks whether this company is enabled; if the answer is no, the document is dropped there and then, with no queue row, no pool row and no error. Nothing sweeps it up later when you do enable the company. Every other field on this tab changes what an e-invoice says. This one changes whether there is an e-invoice at all, which is why it belongs last in your filling-in order and first in your understanding.

Reference: Organization — Company E-Invoice tab

Step 2 — Recognise the block that is printed on every document

After this step you will know why one company record can break a whole group. The tax number, identity type and value, registration number, service tax number, industry code, business activity description, address and contact number are not stored for reference. They are copied onto the supplier side of every sales e-invoice this company issues, and they are all on the mandatory list. Get one of them wrong and nothing fails selectively — every document from every branch to every customer fails in the same way at the same moment. The contact number has the trap in it: it is checked for length, between eight and twenty characters, so a short number or the word not applicable fails the whole document.

Reference: My E-Invoice Admin Applet — Configuration

Step 3 — Meet the fields that only record an intention

After this step you will stop expecting two of these drop-downs to do anything. E-Invoice Mechanism offers Peppol or direct LHDN, and nothing in the platform reads it except a search filter — it does not switch the Peppol pipeline on, which is a separate status on the next tab. Batch Line Logic offers by branch, by document or by line, and no consolidation run consults it; which run your tenant gets is decided by which one has a scheduled job. Both are worth setting correctly, because they are the record of what the company was promised and what your BigLedger contact configures from. Neither is a control.

Reference: Organization — Company E-Invoice tab

Step 4 — Leave the credentials block empty on purpose

After this step you will not spend a morning on the MyInvois portal for nothing. Near the bottom of the tab there is a block labelled taxpayer ERP API credentials — a client ID, two secrets and an expiry date — and its own help text offers it as a way to pull your suppliers’ e-invoices with your own credentials. Leave it blank. Nothing in BigLedger reads any of those four fields today, on any path we can find, and not one company in the whole customer base has filled it in. Filling it in achieves nothing except putting a copy of your client secret somewhere new.

Reference: Organization — Company E-Invoice tab

Step 5 — Learn the test that sorts the tab for you

After this step you will be able to do this on any screen, not just this one. Ask of each field: if I change this and change nothing else, what appears differently, and where? A tax number changes the supplier block on tomorrow’s e-invoice. A status changes whether tomorrow’s document exists. A mechanism changes a value in a database column and a row in a search result. When the honest answer to the question is nothing, the field is a note to yourself and to your support contact — still worth being accurate, never worth an afternoon. The same question is what separates a setting from a label everywhere in the platform.

Reference: Organization — Company E-Invoice tab

Step 6 — Fill the tab in the order that fails safely

After this step you have a sequence you can hand to somebody else. Identity first — tax number, identity type and value, registration and service tax numbers, industry code, address, a contact number of the right length, e-mail. Then the LHDN environment, set to production. Then the intentions, mechanism and batch line logic, set to whatever your group agreed. Then, last, the e-invoice status. Every step before the last is reversible and invisible; the last one starts the clock. Save, then finalise one small sale and watch it reach Valid before anybody else in the company starts issuing invoices.

Reference: MyInvois Setup Guide — Common mistakes

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.

1. A company was enabled for e-invoicing on the tenth, and three invoices were finalised on the ninth. What happens to those three? They are picked up on the next sweep once the company is enabled
Nothing — they were dropped at finalisation, with no queue row and no error, and have to be found and pushed through by hand
They appear in the Batch Pool for the month

2. What does setting E-Invoice Mechanism to *Peppol* do? Switches the Peppol pipeline on for the company
Routes e-invoices through Peppol instead of MyInvois
Nothing but record the value — the only thing that reads it is a search filter

3. Your supplier contact number is stored as *N/A* on the company record. What is the effect? Every e-invoice from that company fails, because the contact number is checked for a length of eight to twenty characters
The field is left blank on the e-invoice and the document is accepted
Only documents to customers without a phone number fail

4. Should you obtain a client ID and secret from the MyInvois portal and enter them in the Taxpayer ERP API Credentials block? Yes — without them inbound supplier e-invoices cannot be retrieved
No — nothing reads those fields today, and no company in the customer base has filled them in
Only if the company is in the production environment

5. Which field on the tab should be set last? E-invoice status, because enabling it is what starts documents flowing
The supplier tax number, so it can be verified against LHDN first
Batch Line Logic, because consolidation depends on it

Answer key

Nothing — they were dropped at finalisation, with no queue row and no error, and have to be found and pushed through by hand — Organization — Company E-Invoice tab
Nothing but record the value — the only thing that reads it is a search filter — Organization — Company E-Invoice tab
Every e-invoice from that company fails, because the contact number is checked for a length of eight to twenty characters — My E-Invoice Admin Applet — Configuration
No — nothing reads those fields today, and no company in the customer base has filled them in — Organization — Company E-Invoice tab
E-invoice status, because enabling it is what starts documents flowing — MyInvois Setup Guide — Common mistakes

This is a self-check. Your answers are marked in your browser and stay there — nothing is sent anywhere, nothing is recorded, and the marking is readable in the page source, so it is not a credential. Open the answer key at any time.

Next: Turning Peppol on for a new company, and the queue your document actually lands in · Back to the series · Play this as a presentation

Last updated on September 19, 2026

The fields on a new company's E-Invoice tab that switch something on, and the four that do not Turning Peppol on for a new company, and the queue your document actually lands in