> ## Documentation Index > Fetch the complete documentation index at: https://manual.risegroup.eu/llms.txt > Use this file to discover all available pages before exploring further. # Dimensions > Dimensions tell you what the money was for. Tag invoice lines with a project or cost centre and Rise splits the whole profit and loss along that axis. The chart of accounts tells you **where** the money went: software, rent, subcontracting. Dimensions tell you **what it was for**. Add a dimension — a project, say, or a cost centre — tag the invoice lines with a value, and Rise splits your whole profit and loss along that axis. Dimensions are yours to define. Rise ships none of its own, so you build exactly the axes your business reports on. ## What you can track Split costs and income across sites, teams or business units — Helsinki and Jyväskylä, or sales and delivery. See what a client project or an internal development effort actually cost. The figures accumulate from purchase invoices, expense claims and journal entries. Follow each property, vehicle or machine separately where the chart of accounts doesn't separate them. Gather the costs behind a grant application under one value, so the cost breakdown is ready when the application is. ## Creating dimensions Dimensions live in the company settings in the Rise web app. A dimension is an axis; a value is a choice on that axis. Go to **Company settings** and open **Dimensions**. Name the axis: **Project**, **Cost centre**, **Property**. Names are unique within a company. Add the options that belong on the axis: **Ratamo renovation**, **Building 1**, **Jyväskylä**. Values exist only if you create them here — nobody can invent a new one while tagging an invoice. Every value has a default share, 100 % unless you change it. When someone tags a line with that value, the share is pre-filled. Useful when a cost centre always takes, say, 60 % of a recurring invoice. Describe when the value should be chosen: "all invoices from Kone Oy", "anything related to the Ratamo site". This is the guidance Rise uses to tag lines automatically — the more precisely you describe it, the better the automation does. Dimensions belong to one company. If your Rise account has several companies, each has its own dimensions and values. ## Tagging invoice lines Once dimensions are in use, **tagging happens automatically**: Rise allocates lines according to the guidance you wrote with each value. Tagging by hand is the correction path — for when the automation got it wrong, or a line needs splitting differently. ### What the AI allocates on The guidance can rest on anything you can describe in words. The usual ones: | Basis | Example | | - | - | | **Subject** | Marketing costs; rent, water and electricity | | **Site or region** | Jyväskylä, Tampere, Central Finland | | **Person** | A particular employee — the allocation can follow from their site or their role | | **A reference on the invoice** | The buyer reference or project reference the supplier puts on the invoice | You can combine them, and a value can carry a fixed split — phone bills 40/60 across two sites, for instance. The more precisely you describe the basis, the less often an invoice lands on a person's desk. When the information isn't on the invoice at all, the invoice is raised for review — or it can be steered by writing a reference into the invoice's internal comments. Tagging is done **per line**, not per document — a single invoice can split across several projects. Open the document, expand the line and use its **Dimensions** block. You can tag lines on: * **Purchase invoices** — during approval or afterwards as a correction * **Sales invoices** — on saved drafts and on sent invoices * **Expense claims** — done by an accountant or a manager * **Journal entries** — done by the accountant team One line can carry values from several dimensions at once: the same subcontracting line can be both **Project · Ratamo** and **Cost centre · Jyväskylä**. Tagging only works once the document is saved, because tags attach to saved lines. On an unsaved invoice the block asks you to save the draft first. If you replace the lines of a tagged draft, the tags are lost — Rise warns you before saving. ### Splitting a line across values When one line serves two projects, split it. Give either a **percentage** of the line or an **amount** up to the line's net value, then add a second value for the remainder. Rise does not force the shares to add up to 100 %. Tag half the cost and the other half stays unallocated. Tag more than the line is worth and Rise flags the over-allocation. The flexibility is deliberate: partial tagging is a normal way to work. Use percentages on expense claim lines. Those lines have no net amount of their own, so splitting by amount isn't possible. ## Who can do what | Task | Admin | Manager | Accountant | Auditor | Employee | | - | :-: | :-: | :-: | :-: | :-: | | Create, rename and archive dimensions and values | ✅ | ✅ | ✅ | — | — | | Tag purchase and sales invoice lines | ✅ | ✅ | ✅ | — | — | | Tag expense claim lines | ✅ | ✅ | ✅ | — | — | | Tag journal entry lines | — | — | ✅ | — | — | Employees don't tag dimensions, not even on their own expense claims. They submit the claim and an accountant or manager tags it. An auditor sees everything and changes nothing. ## Renaming and archiving Dimensions and values are never permanently deleted, so the history survives. * **Rename** a dimension or value at any time. Every past entry follows the new name. * **Archive** a value you no longer use. It disappears from the pickers, but entries tagged with it still appear in reports, marked as archived. * **Restore** it by creating a value with the same name again. Rise brings the archived one back with its history. Every change to dimensions is written to the change log, with the value before and after. Start with one dimension and a handful of values. One well-tagged cost centre axis is worth more than four half-tagged ones, and you can add axes later. ## Related pages How receipts and expense claims reach the books. Where in invoice processing the dimension tagging lands. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.