System

The module where you configure not one area of work but the whole database at once. The other modules answer questions like "how do we run the warehouse" or "how do we calculate payroll"; this one answers the questions above them: how many companies live in this database, from which number documents are counted, up to which date the past may be edited, and who has to approve an invoice before it can be posted.

Hence its character: the module's objects are rarely used directly. They are set up once when the database is started, and remembered on two occasions — when something has to be forbidden (close a period, require approval) or when the business grows (a new company, a new bot, a new letter template).

The route: from starting the database to the daily rules

Companies — how many legal entities keep books in this database
        ↓
Main Company — the details printed on every document
        ↓
Register sharing — what is taken from the main company and what is our own
        ↓
Rules of work: number series · reporting periods · approval rules
        ↓
Protecting the past: closing changes + transaction correction history
        ↓
Links to the outside world: mail · SMS · Telegram bots · synchronisation API

1. Companies — the list of legal entities, each with its own documents, balances and reporting.
2. Main Company — one card per company: name, address, bank, director. This is what the customer sees on an invoice.
3. Register sharing — so that items, contacts and units are not duplicated but taken from the main company.
4. Number series set the numbering ranges, reporting periods spare you typing dates every day, approval rules require a document of the chosen register to be approved before it posts (there is no amount threshold).
5. Closing changes cuts off backdated edits, while the Transaction correction history and the Transaction correction history report show what was edited before the lock.
6. Outward channels: Mail Text and Mail Sender, SMS Notification, Connected Telegram Bots, Registers sync API.

What is worth understanding

Sharing is a reference, not a copy. A company uses the main company's reference rather than receiving a copy of it: correct an item's name in one place and it changes everywhere. So decide what to share at the start — unpicking it later is harder than keeping things separate from the beginning.

A closed period beats an agreement. The setting names the date up to which documents cannot be posted, unposted or changed so that their posting is rewritten — the only way to avoid "the return is filed and the figures have moved". An in-place edit of a posted entry is seen by the Transaction correction history, a register that can be neither edited nor deleted by hand; but an unposted document deletes its entry together with that entry's history.

Approval rules stop the document, not the person. Until the rule is satisfied, the document will not post: the system clears "OK" and saves it as a draft; it is a technical stop, not a reminder somebody can ignore.

Number series are about ranges, not collisions. Without a series the system gives a document the number one above the largest in the register, and each company of the database counts on its own — numbers do not collide. A series is needed when numbers must run in ranges by period (for example, a range of its own for each year). One series, one register.

User settings are not access rights. They are the working attributes documents pick up by login: the sales department and the account for that person's advances. Rights live on the user card.

Attachments can be encrypted. A maintenance routine walks the server's whole file store — attachments and print-form templates — and puts an encrypted (or decrypted) copy next to each file; the original stays on disk. The direction is set by a server setting, not in the window — a decision made at database level, not per document.

Where to start in a new database

1. Companies and Main Company — who you are and what goes onto printed forms.
2. Register sharing — with more than one company, settle this before the first document.
3. Units (units of measure) — the base reference no item can be saved without; Countries — if needed, documents and cards do not read them yet.
4. Number series — before the first documents are entered.
5. Reporting Period, Approval Rules, Closing changes — rules that are easier to introduce now than to negotiate later.

Common tasks

You need	Where to go
add another legal entity	Companies
change the details on printed forms	Main Company
stop duplicating references between companies	Register sharing
set document numbering	Number series
close a period against edits	Closing changes
find out who edited the postings	Transaction correction history · Transaction correction history report
require a document to be approved before it posts	Approval Rules
e-mail an invoice to a customer	Mail Text + Mail Sender
connect a Telegram bot	Telegram Bots for Connection → Connected Telegram Bots
pull items, contacts and stock from a partner company's database (the sync service itself is not in the menu)	Registers sync API
reclaim the space taken by attachments	Cleanup attachments

Everything in the module

References: Companies · Countries · Units · Number series · Approval Rules · User Setting · Mail Text · Standard Text · Connected Telegram Bots

Logs: Transaction correction history

Settings: Main Company · Register sharing · Reporting Period · Closing changes · Time Sheet Settings · SMS Notification · Telegram Bots for Connection · Registers sync API

Reports: Transaction correction history report · Contact Change History

Maintenance: Mail Sender · Encrypt / Decrypt Files · Cleanup attachments · Clear telegram · Xlsx Import · Xlsx Export · Encrypt integration secrets (once after an update) · Rebuild search text without hidden fields (once after an update) · Migrate order print templates to new tags (once after an update)

Where to look next

• Database maintenance — service registers and heavy operations.
• Nominal ledger — reporting periods and closing the books from the other side.
• CRM — the contacts whose change history this module's report shows.