Connect your accounting system

Connecting signs you in to that system and asks it for permission to read your invoices and customers. You can revoke it from your own system at any time, and doing so stops the flow — invoices already filed stay filed.

Connecting an accounting system, and disconnecting one, is an Admin or Editor job. An Approver or a Viewer can see that a system is connected and which organisation it points at, but the Connect and Disconnect controls are switched off for them, with a note saying who to ask.

It is checked when you start, not at the end: if your role does not allow it, you are told before you are sent to sign in to the accounting system, rather than after you have already granted it access. The full table of what each role can do is on Users and roles.

The platform reads your buyers out of the connected system, so a customer with no tax number or no address there produces an invoice that cannot be filed. Each system keeps those in a different field, and QuickBooks has no such field at all until you create one.

The full per-system list is on ERP prerequisites. It is a one-time job per customer, and doing it before the first sync is far less work than chasing rejections afterwards.

Connecting is not the last step. With the ERP attached, the platform still has to be told which field in your data fills each field on a filed invoice, and that is PINT Mapping. Open it, click Pre-fill defaults at the top to populate the standard mapping for your system, then review every field before you rely on it.

A field your system does not hold at all can be marked Will be provided at invoice level, which means you type it per invoice instead — those invoices wait on Staged Invoices until you do.

The other configuration screen is Tax Codes, which maps your own tax rates to the UAE categories. It also starts from defaults for your system.

Most companies invoice from one accounting system, and the single connection above is all they need — skip this section. It is for a company that invoices from more than one system, or from more than one organisation in the same system, under a single TRN.

Connect each of them to the same entity: once the first system is connected, the entity page shows a small Connect more ERPs under the same TRN button below it (for Admins and Editors). Choose the system, sign in, and pick the organisation, as for the first connection.

Every invoice is filed with the entity's own details as the seller — its name, TRN and address — whichever system it came from. Nothing about the entity changes when you add a system.

Each connection has its own PINT Mapping, so you can map each one separately. A connection to another system starts from that system's defaults. A second organisation in the same system as the main connection uses the main mapping until you save one for it.

Make main on a connection makes it the one received invoices go into. The previous main connection stays connected and keeps sending, and every connection keeps its own mapping. Disconnect on a connection removes only that one, and its mapping is kept in case you connect it again. Disconnecting the main connection leaves the others connected and sending. Until a main connection is set again, invoices you receive are kept in TaxStar but not added to any accounting system, and the entity page says so.

An organisation can be connected to an entity only once. Two systems need one more step on each connection you add: an Odoo company is given its own webhook address to enter in Odoo, and a Zoho Books organisation needs its own webhook secret. Both are shown on that connection on the entity page.

Connections belong to an entity, not to you. If you invoice from two companies — two TRNs — each has its own entity, its own connection, its own tax codes and its own mapping, including two separate authorisations to the same accounting system when both companies live in it. One company with one TRN and several systems is the case above.