Setting up BSuit for a new organisation
What an administrator configures, in the order it has to exist, before people can record transactions.
On this page
Process at a glance
- Company, currency and countryAdministratorThe legal entity exists with its base currency.
- Install modulesAdministratorOnly the modules you licensed appear in the menu.
- Taxes and exchange ratesFinance administratorTax codes and rates are available on documents.
- Fiscal year and periodsFinance administratorPostings have an open period to land in.
- Chart of accountsFinance administratorLedger groups and ledgers, including bank, retained earnings and FX gain/loss.
- Record types and numberingAdministratorEvery voucher type is numbered and knows whether it needs approval.
- Approval workflowsAdministratorDocuments that need approval are routed to approvers.
- Users, roles and securityAdministratorPeople can sign in and see only what their role allows.
- Email and print templatesAdministratorNotifications are delivered and documents print in your format.
#Purpose
Use this chapter when a new organisation (tenant) or a new company is being prepared for use. It lists the configuration in dependency order: each step relies on the ones before it. Skipping ahead is the most common reason a first transaction cannot be saved or posted.
#What BSuit creates for you
When a tenant is provisioned, several masters are seeded automatically so you do not start from empty screens.
| Master | Created by | Where to maintain it |
|---|---|---|
| Currencies (ISO 4217) | Seeded | Currencies |
| Countries (about 80) | Seeded | Countries |
| Exchange-rate provider (Frankfurter, on by default) | Seeded | Exchange rates |
| 67 record types with numbering series, 43 print templates, 4 email templates | Seeded | Record types |
| Chart of accounts and the first fiscal year with 12 monthly periods | Seeded when Finance is installed | Ledgers |
| Default company "MAIN" (only when no company exists) | Seeded | Companies |
| Taxes | You | Taxes |
| Email server settings | You | Email configurations |
| Company details, logo and addresses | You | Companies |
#Step 1 — Company, base currency and country
- Open Administration › Companies and edit the company created for you (or create one).
- Set the legal name, country, address and logo.
- Set the company currency. This is the base currency used by foreign-exchange revaluation and consolidation.
#Step 2 — Install modules
Administration › Modules lists the modules available to your plan. Installing a module that depends on another is refused until the dependency is installed ("Module … depends on modules that aren't installed"). Only administrators can install modules.
#Step 3 — Taxes and exchange rates
- Create each tax and its rate in Administration › Taxes; link product-specific taxes in Product taxes.
- Check Administration › Exchange rates. The seeded provider fetches daily rates; add manual rates for currencies it does not cover.
#Step 4 — Fiscal year and periods
- Open Finance › Fiscal years. The first year and its 12 monthly periods were created at install.
- For later years, create the year, then open Finance › Fiscal periods and make sure its periods exist.
- Postings are refused in closed periods, so check the current period is open before go-live.
#Step 5 — Chart of accounts
- Review the seeded ledger groups (Asset, Liability, Income, Expense, Equity) and ledgers.
- Create a ledger for each bank account and link it to the bank.
- Make sure an Equity group exists: year-end close moves profit into Retained Earnings under Equity.
- Choose the FX gain and loss ledgers if you use foreign currencies (needed for automatic revaluation).
- Create the control and posting ledgers other modules need: inventory (stock, goods-received control, COGS, variance), purchase-invoice posting (AP control, default expense), payroll posting and travel-expense posting.
#Step 6 — Record types and numbering
Each voucher type (cash receipt, journal, sales invoice…) is a record type. Its prefix, next number, padding and reset rule decide the document number; its flags decide whether it needs approval, a party account, a project, and whether it moves stock.
| Setting | Effect |
|---|---|
| Prefix, next number, padding, separator, suffix | The automatic document number (for example CR-0001). |
| Reset (none / yearly / monthly) | Numbering restarts on the calendar year or month — not the fiscal year. |
| Requires workflow approval | The document cannot be posted until it is approved. |
| Party account required / shown | A customer or supplier must be chosen. |
| Update stock | Posting the document moves inventory. |
#Step 7 — Approval workflows
- Open Workflow automation › Templates to review the seeded approval templates.
- Link each template to the record type it approves (only super administrators can change templates and links).
- Set up delegations for approvers who will be away (Workflow automation › Delegations); a delegate can act only on steps that allow delegation.
#Step 8 — Users, roles and security
Create users in Identity › Users and give them roles. See the chapter “Roles and access” for how permissions work.
#Step 9 — Email and print templates
- Add your mail server in Administration › Email configurations and use its Test action.
- Review the seeded print templates and email templates and apply your branding.
#Before the first transaction: checklist
| Needed | To save | To post |
|---|---|---|
| Active record type and permission record_type.<code>.create | Yes | Yes |
| Party, trade account or fund, when the record type requires them | Yes | Yes |
| A project — whenever the Projects module is installed | Yes | Yes |
| Ledgers for each line | Yes | Yes |
| Approval, when the record type requires it | No | Yes |
| An open fiscal period for the date | No | Yes |
| Passing the budget check, balanced debits and credits | No | Yes |
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- System administrators and implementation consultants
- Owner
- BSuit documentation team
- Reviewer
- Editorial review pending
- Last verified
- 2026-09-25
- Checked against
- cb3691bbf
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:article/guide/implementation-setup
Known limits: Written from a line-by-line read of the implementation (every statement traced to source). Not yet walked through end to end by a trainer on a running system.