Multiple companies in one install

TSync can run several companies from a single installation. Each company keeps its own warehouses, stock, production orders, purchase orders and invoices — and its own document numbering — while you switch between them from the top bar. It is turned off by default, so nothing changes until you enable it.

Check you're ready first

Before you switch multi-company on, open Setup → Companies → Readiness (the Readiness button on the Companies page). It gives you a simple go/no-go answer:

  • Ready / Review needed — multi-company can be turned on. Review needed just lists a few surfaces (like the audit log or exports) worth double-checking for your setup; it does not block you.
  • Blocked — your installation is missing a piece of the per-company "wall" that keeps each company's data separate (usually because an upgrade didn't finish). The page names exactly what's missing. Re-run the upgrade, then check again.

The page shows two lists: the isolation anchors (the data that must be tagged with a company — warehouses, invoices, bank accounts, treasury, …) each marked Present, Missing or Not installed; and the leakage vectors (the places data could otherwise leak between companies) with how each is handled. If anything critical is missing, the system will refuse to enable multi-company and send you here — so you can never turn it on in a state where companies could see each other's data.

Turn it on

  1. Go to Setup → Companies (/admin/tsync_tenants).
  2. Click Enable multi-company.

While it is off, the system behaves exactly as before — a single company.

Add a company

On the same page, type a name and click Create. The first, built-in company is called Default and holds everything that already existed.

Rename a company

Made a typo in a company name? On Setup → Companies (/admin/tsync_tenants) each company row has an inline rename field — just edit the name and save. The built-in Default company name is fixed and cannot be renamed.

Switch company

Once enabled, a company picker appears in the top bar (the building icon). Click it and choose a company to switch. You stay on the page you were on, and the picker shows which company you are currently in.

Each company has its own document numbers

Give every company a short series code (Setup → Companies, the Series box next to each company). That code is added to the company's document numbers so each company counts independently:

  • Company A (series A): NIR-A-00001, NIR-A-00002, …
  • Company B (series B): NIR-B-00001, …

This applies to internal documents (goods receipts/NIR, delivery notes/AVIZ, returns, production orders, purchase orders) and to the sales documents that are numbered — invoices, estimates and credit notes — so each company runs its own independent sequence (e.g. company A's estimates are EST-A-1, EST-A-2, while company B's start again at EST-B-1). If you leave the series empty, the system uses an automatic code so two companies never share the same number. A draft invoice keeps its place until you finalise it, then takes the next number in that company's own sequence.

Decide who can see which company

Go to Setup → Companies → Access control. For each company, tick the staff who may use it:

  • A staff member with nothing ticked anywhere can access every company (this is the default).
  • As soon as you tick specific staff for a company, only those people can switch to it — everyone else no longer sees it in the picker.

What is kept separate between companies

When multi-company is on and you are working inside a company, you only see — and only act on — that company's data:

  • Warehouse — warehouses, stock, stock movements, lots, goods receipts (NIR), delivery notes (AVIZ) and returns;
  • Production & purchasing — production orders, purchase orders, supplier invoices (bills) and bill payments;
  • Sales — invoices (including their draft → final numbering), estimates, proposals and credit notes, customer payments and expenses. Estimates and credit notes also get their own per-company numbering;
  • Accounting — the general journal and every accounting report (trial balance, profit & loss, balance sheet, tax, aging, budgets, reconciliations), plus period close — you can only close your own company's books;
  • Reports — every commercial report in the reports console (invoices, estimates, proposals, credit notes, payments, customer balances, sales by item, bills, expenses);
  • Activity / Audit log — each change is recorded against the company that made it, so you see your own company's history (plus platform-wide system events);
  • Scheduler — the job runs you start are tagged to your company.

Your money data stays isolated, too

When multi-company is on, each company sees only its own financial data. Bank accounts, money-holding places (Treasury), treasury balances, transfers and bank statements are kept separate per company. When you switch the active company from the top-bar company picker, the data you see changes accordingly — company A's bank account does not appear under company B.

Shared, global items belong to the Default company and stay visible everywhere — for example a chart of accounts or a shared nomenclature.

This means you can safely run several companies in one TSync without their money data ever mixing.

Each company can also have its own brand colours: open the Visual Theme Manager while inside a company and the theme you save applies to that company only — the Default theme is the fallback.

Company-wide management views and overall analytics / business intelligence still show the whole picture for administrators — by design (those are organisation-level totals, not per-company operations).

Each company can work in its own currency

A company is not tied to the installation's currency. On Setup → Companies (/admin/tsync_tenants), switch into the company first, then give it its own value for:

  • Currency country — which central bank publishes the rates (BNR for Romania, BNM for Moldova, ECB for the euro area);
  • Base currency — the currency that company's own figures are kept in;
  • FX fetch mode — how the rates are brought in.

Leave a field empty and the company simply inherits the installation-wide setting; fill it and the company overrides it. The overrides are listed on the same page, so you can see at a glance which ones a company has.

These are used, not merely stored. The currency page shows what the engine actually uses for the company you are inside, a Fast Contract takes the company's base currency, the chart-of-accounts guard checks the company's country, and the daily rate job fetches every source that any company uses — so on one install a Romanian company gets BNR rates and a Moldovan one BNM rates, the same day.

A new company starts on the installation's defaults; nothing is guessed from its name or its numbering series, so set its currency yourself when you create it. With a single company, none of this changes anything.

Branches & operational units

A company often works from more than one place — a head office, a few shops or showrooms, a warehouse point, a service point. Branches give you one tidy list of those places instead of typing them into a free-text field that everyone spells differently.

Open Setup → Companies → Branches (the Branches button on the Companies page).

  • Add a branch — click New branch, pick the company it belongs to, give it a name and (optionally) a short code, type and manager. A branch always belongs to one company.
  • Default branch — the first branch you create for a company becomes its default; use the star button to move the default to another branch. A company always has exactly one default.
  • Deactivate / archive — a branch you no longer use can be deactivated (it stops appearing in lists) or archived (hidden away). You can re-activate it later.

Turn the layer on when you're ready

Branches start in Off mode, so adding them changes nothing elsewhere yet — you can build the list in peace. When you're ready to use branches across the app, change the Mode in the settings panel:

  • Off — registry only (the default).
  • Shadow — build the list and map old values, with no change to your day-to-day screens.
  • Hybrid — branch pickers, filters and badges start appearing in the modules you choose.
  • Canonical — a branch becomes required wherever you've configured it.

The same settings panel lets you choose where a branch should be required (leads, projects, financial or warehouse documents, HR), how strictly branch access is enforced, and what to suggest as the default branch. Branches work on a single-company install too — you don't need multi-company switched on to use them.

Who can use each branch

Open Branch access (the button on the Branches page) to decide which staff may work in which branch:

  • Pick a branch, then grant access to a staff member and choose their level (view, operate, manage, branch manager, branch admin). Remove a grant at any time.
  • A staff member with no grants anywhere can use every branch (the default). As soon as you grant them specific branches, they are limited to those — others stop seeing that branch (once enforcement is on in the settings panel).
  • Branch access sits under company access: a person needs access to the company before a branch in it makes sense.

Putting a lead in a branch

Once the branch layer is in Hybrid (or Canonical), each lead can be tied to a branch:

  • Open a lead — the Branch block on the lead shows its current branch (or a reminder if one is required) and a dropdown to Set branch. You only see branches of the active company that you're allowed to use.
  • New leads can get a branch automatically: if your default-branch behavior is use the company default branch, a new lead with no branch is filled in with the company's default branch.
  • On the leads list a Branch column and badge show each lead's branch, and you can filter the list by branch — handy for a branch manager who only wants their own leads.

Branches on projects, invoices, estimates & proposals

The branch also reaches your projects and commercial documents:

  • Open a project — a Branch bar at the top lets you set the project's branch (and a new project takes the company's default branch automatically).
  • Invoices, estimates and proposals inherit their branch from the project they belong to — so a document raised under a project is automatically tagged with that project's branch (or the company default if it isn't linked to a project).
  • The invoices, estimates, proposals and projects lists each gain a Branch filter, so you can narrow any of them to a single branch.

Moving off an old "branch" text field

If you used to keep the branch as a free-text custom field (e.g. Filiala), open Branches → Branch mapping:

  • It finds those branch-like custom fields and lists every distinct value with how many records use it.
  • For each value, map it to an existing branch or create a branch from it — the leads that used that text value are then filled in with the real branch automatically. Values you don't want can be ignored.

On multi-company installs: if the same text value is used by more than one company, TSync will not auto-fill it (to avoid putting one company's branch onto another company's leads) — the backfill count shows 0, and you map that value per company instead. The Health page flags any record whose branch ends up on the wrong company so you can correct it.

The BX lead view (the alternative lead screen) also gets the native Branch selector, so you set the branch from the registry no matter which lead screen you use.

Tip: turn multi-company on only when you really run more than one company. For a single business, leave it off.