Company Management

1Step by step, setting up a company #

1. Create the company if it does not exist. It gets its own database, copied from the model, and is allocated to you.
2. Check its details — name, address and registrations. The GST number is validated as you type.
3. Add its branches. One already exists (the default branch) and cannot be deleted; rename it to your main office rather than adding a duplicate. Adding more branches is ERP edition only; Professional works with that one branch.
4. Add divisions if you report on a second axis, and say which branches each applies to. Leave the branch list empty to mean every branch.
5. Add group companies if branches invoice under more than one legal entity, and list the branches under each (ERP edition only).
6. Switch on Track Division and Allow Group Company in General Settings once the structure is in place.

2What the subscription limits #

• Companies are sold by count. When the figure above reads its limit, Create is refused until more are allotted against the serial.
• Users and devices are sold by count too, and are shown here for reference; they are enforced at sign-in and activation, not on this screen.
• Branches, divisions and group companies are NOT sold by count. Nothing limits how many you create.
• Modules decide which parts of the product appear. The ERP edition gates every branch option on other screens, group companies, and adding branches. Professional always works in branch 1, which it can still edit on the branch master.

3Why a card can be switched off #

• Track Division off — divisions still save here, but no entry screen or report offers them. Turn it on in General Settings when the divisions are ready.
• Allow Group Company off — groups still save here, but documents do not print under them.
• Both are deliberate: the master stays open so the structure can be built BEFORE the feature is switched on.
• Not an Administrator — every card is readable, none of them saves. The API checks the role again, so the buttons are a courtesy rather than the rule.
• Signed in as support — a Global Administrator has no licence of its own, so every figure here is read against the licence of the COMPANY it signed into, and every limit is that licence's. It sees exactly what that company's own administrator sees, and is refused a further company in the same words.
• A Developer may edit the companies allocated to them and may never create one. Create is refused with that reason rather than the licence's.

4Rules and integrity #

• A company's code, database name and financial year cannot be changed — the database is named after all three.
• The default branch (BrID 1) cannot be deleted . Unallocated vouchers, ledgers and employees fall back to it.
• A branch or division that anything has been posted against cannot be deleted — around sixty tables refer to a branch. Disable the branch, or mark the division inactive, instead.
• Deleting a group company takes its branch list with it (the database cascades that one).
• Every one of these tables carries permission triggers : a save or delete can be refused by the database itself, and the message says which permission was missing.

5If something does not work #