Glossary
The words this platform uses, and what it means by them.
| Term | What it means here |
|---|---|
| Module | A body of work with its own records — one tab across the top. |
| Group | A handful of related sections, on the modules large enough to need the level. |
| Section | A shelf of screens that belong together. |
| Screen | One list, report or workspace, with an address of its own. |
| Resource | What a screen is a view of — the kind of record it holds. |
| Company | A legal entity. Data is fully segregated between companies. |
| Unit | A node in the tree inside a company: business unit, division, department, cost centre, site. |
| Cube | An analytical model over records a module writes: the dimensions you may cut by and the figures you may cut. |
| Dimension | Something to cut a figure by — a date, a customer, a cost centre. |
| Key figure | Something measured — a sum, a count, an average, a ratio. Defined once and shared by every report that uses it. |
| Commitment | Money promised but not yet invoiced. Deducted from the budget at the moment of the promise. |
| Effective dating | A record that carries a window, so asking as at a date returns what was in force then. |
| Saved view | A list or report kept exactly as arranged, including the words typed into search. |
| Posting | Writing a financial event to the ledger. Balanced, dated into an open period, and not deleted afterwards. |
| Reversal | The way a posting is undone: an opposite posting, leaving both on the record. |
| Immutable | A record that does not change because not changing is the point of keeping it. |
| Classification list | A configurable list of values behind a dropdown, maintained per company. |
| Number range | The rule that decides how a document gets its number. |
| Drive | A connected place your files already are. |
| Agent | A standing instruction: watch for a condition and act when it holds. |