Organisation, Main HQ and branches

Everything JomeInvoice knows about your own company lives in Settings → Workspace Settings → Organisation. It holds two things: your Main HQ, which was created with your workspace, and any Branches you add.

Most businesses only ever need the Main HQ. If you trade from one place under one name, there is nothing to add here - your only job is to make sure the details on your HQ are complete and correct.

You need branches when one company issues invoices from more than one place. A branch is a separate outlet, shop, or channel that issues invoices under your workspace. Every invoice you create carries an Issuing branch, and it defaults to HQ.

How HQ and branches fit together

One idea makes the rest of this page easy. Your Main HQ is your workspace's own branch, and it is the default for everything. A branch you add only has to hold what makes it different.

That splits into two kinds of setting:

• Workspace-wide, held once on your HQ. Your company identity and tax details, TIN verification, your shared request link, and your API credentials. Branches do not have their own and never need one.
• Defaulted from HQ, overridable per branch. The address, invoice logo, footer, and invoice notification recipients. Give a branch its own and that branch uses it; leave it and the branch follows HQ.

So when an invoice is issued by a branch, it uses that branch's details where the branch has them, and falls back to HQ where it does not.

What the Organisation tab holds

Go to Settings, find Workspace Settings, click View, then open the Organisation tab. You will see:

• Main HQ - a single entry for your company itself.
• Branches - the branches you have added, with an Add Branch button.

Each entry shows the name, whether it is your HQ or a Branch, and its country - your HQ also shows its registration number, and a branch shows its address. View opens it so you can read or change what it holds, and each branch has a delete control beside it.

Your Main HQ also carries a Verified or Not Verified badge, which tells you whether your tax details have been checked. Verified and Not Verified below explains what to do about it.

Which setup is yours

Once you have branches, they show up beyond this tab. Each invoice carries an Issuing branch that defaults to HQ, see Create an invoice. A monthly B2C consolidation produces one consolidated draft per branch, so five outlets give you five consolidations, see Run your monthly B2C consolidation. Invoice exports can be filtered by issuer/branch, see Export invoices. And on the Team tab you control which branches each of your people can see, and route each outlet's notifications to them - see Teams: branch access, sources, and notifications.

Inside your Main HQ: the Details tab

Click View on the Main HQ. The Details tab shows its Business Information, and Edit lets you change it.

This is your company's own record - the details LHDN receives on every submission. A branch holds a much smaller set, covered further down.

Below Business Information are:

• Registered Address and Business Address, both required. The next section explains why there are two.
• SST No. and Tourism Tax No., your tax registration numbers where you have them. Both are optional.

Everything else in the table above is required, apart from Old BRN/SSM.

Who gets notified: the Contact tab

Your Main HQ's Contact tab holds the people who receive email notifications for validated invoices, as a Primary contact and an optional Secondary. Select Existing Member lets you pick someone already in your workspace rather than typing their details again.

This is a different thing from the Email on the Details tab. That one is your company's email address as submitted to LHDN; these are the people JomeInvoice notifies. Changing one does not change the other, and they do not have to be the same address.

This is your workspace default. A branch can override it with its own contacts, so each outlet's invoice notifications reach whoever runs it - see Inside a branch further down.

Verified and Not Verified

At the top of your Main HQ, next to its name, is a badge reading either Verified or Not Verified. It means one thing: whether your TIN has been checked against your business registration details.

Verification happens once, for the workspace. Branches do not verify separately, so you only ever have to get this right in one place.

Verified is what you want. It confirms your tax details hold together.

Not Verified appears alongside a Verify TIN No button. Click it to run the check.

If the check does not pass, you will see:

TIN Verification Error
TIN validation failed. Please check your TIN number and registration details.

The message is telling you the two things that have to agree. Work through them in this order:

1. Check the TIN itself. It has to include the entity prefix, and the prefix has to match your Entity Type - a company TIN looks like C12345678901. A TIN typed without its prefix, or an Entity Type that does not match the prefix, is the most common cause. See TIN verification: company vs individual.
2. Check the registration details. Your Business Name must match your SSM registration, and New BRN/SSM must be in the new 12-digit format. See Why your invoice was rejected for the registration number formats.
3. Correct whichever is wrong on the Details tab using Edit, save, then click Verify TIN No again.

If you have checked your registration details and the check still fails, contact JomeInvoice rather than editing repeatedly.

Share your request page

The Share button next to your Main HQ opens Share Workspace, holding the link and QR code that let your customers request an e-invoice from you. There is one of these for your workspace - branches do not get their own.

This is mainly for B2C selling. A walk-in customer scans the QR code or follows the link, fills in their own details, and the request reaches you for approval - which also keeps that sale out of your monthly consolidation.

From the panel you can Preview the page as a customer sees it, Copy Profile Link to paste into your website or an email, or Generate QR PDF for a print-ready code to put on a counter or a receipt.

The full workflow, including what your customer fills in and how you approve it, is in Share your e-invoice request link and QR code.

API credentials: the Client Secret tab

If you submit invoices through the JomeInvoice API, this is where your credentials live. Open your Main HQ and go to the Client Secret tab. Like verification and sharing, these are workspace-level - branches do not have their own.

Client Secret holds the Client ID and Client Secret your integration authenticates with. Both are hidden by default; use the eye icon to reveal one, or Copy to take it without displaying it.

Both values stay retrievable, so if someone has simply mislaid the secret, reveal it or Copy it again. You do not need to regenerate.

Regenerate issues a new pair, and you should use it when a credential has been exposed - shared with someone who should not have it, sent over email or chat, or committed to code. Treat it as a planned change: the old pair stops working, so your integration will fail to submit until the new values are in it. If submissions start failing on authentication, API submission errors covers what to check.

Who can see or regenerate these is controlled by the Settings → API Credentials permission on a user role, which offers None, View, and Regenerate separately. See User roles and permissions.

The tab also holds a Purchase Module ERP Secret, with its own Client ID, Client Secret, and Expiry Date. These are not JomeInvoice credentials: they are your own ERP system credentials as registered on the MyInvois portal, which let JomeInvoice fetch the e-invoices your suppliers have submitted against you. Leave it empty unless you use the Purchase module.

Registered Address and Business Address

Both addresses are stored on the entity, and both have to be filled in. Only one of them is sent to LHDN.

Each is entered as an address line, an optional second and third line, a postcode, a city, a state, and a country. If you trade from your registered address, tick Same as Registered Address on the Business Address block rather than typing it twice.

Which one is decided by a separate setting: Settings → Workspace Settings → General, under e-Invoice Submission, called Invoice Submission Address. It takes either Registered Address or Business Address, and new workspaces start on Registered Address.

So when would you change it? Registered and trading addresses often differ - a company may be registered at its company secretary's or accountant's office while its actual premises are somewhere else. If that is you, put the registered address in Registered Address, put the address you trade from in Business Address, then set Invoice Submission Address to the one that should reach LHDN.

Two things to keep in mind:

• If both addresses are the same, the setting makes no practical difference. Leave it alone.
• The setting chooses which kind of address, once, for the whole workspace. You cannot pick Registered for one branch and Business for another. But whose address is submitted follows the branch that issued the invoice - a branch's own address overrides your HQ's.

How your supplier name appears on submissions

If you run branches, you also get to choose which name is submitted as the Supplier Name. That choice is MyInvois Supplier Name Source, on the General tab under Other Settings. It covers Sales and Self-Billed invoices.

This is one choice for the whole workspace rather than a setting on each branch. Pick the form that names you the way you want to appear on the submission, and keep it consistent across your branches.

The choice that matters is whether your buyers should see which outlet issued the invoice. Entity + Branch Name is the safest default: your company is always identifiable, and the outlet is visible where there is one.

Inside a branch

A branch is deliberately much lighter than your Main HQ. It does not hold its own TIN, registration number, entity type, or MSIC code - those belong to the company and are verified once, on the HQ. Click View on a branch and you get three tabs.

Address

Registered Address and Business Address for that branch. These override your HQ's on invoices this branch issues, which is what lets an outlet show its own trading address rather than head office - including on the address submitted to LHDN.

Contact

The same Primary and Secondary contacts as your HQ's Contact tab, but for this branch, with Add Email Recipient to add more.

Use this to route each outlet's invoice notifications to whoever actually runs it, instead of everything landing in one head-office inbox. Leave it and the branch follows your HQ contacts.

Settings

Two branch-level overrides, each with its own switch:

• Branch Logo - use a branch-specific logo on invoices and PDFs generated for this branch. When it is off, or you have not uploaded one, the entity logo is used.
• Footer - use a branch-specific footer when invoices are generated for this branch. When it is off, the branch falls back to the workspace default set by Enable Invoice Default Footer on the General tab.

This is how a business with several outlets or brands issues invoices that look like they came from that brand - its own logo, its own remarks and payment instructions - while everything still submits under one company.

Add a branch

To add a branch and set it up:

Change a branch

To change an existing branch's address, footer, logo, or the people who receive its invoice emails:

Related articles

• Workspace Settings - every settings tab at a glance, and the General tab in detail
• Create your JomeInvoice account - creating and verifying a workspace, and what one workspace represents
• Why your invoice was rejected - the company profile and MSIC rejections, and how to fix them
• TIN verification: company vs individual - TIN formats and entity types
• Create an invoice - where the issuing branch is chosen
• Share your e-invoice request link and QR code - what the Share button gives you, and the full request workflow
• Run your monthly B2C consolidation - one consolidated draft per branch