Department structure
Reporting follows the real organisation chart.
- Departments defined by the company
- An owner per department
- Used on expenses
- Used on purchase orders as well
Budgets are set by department and period, and the expenses recorded in the application are compared with them at any moment. Every outgoing payment has a department, a category, a supplier and an attached document, so budget execution is available during the current month, not after the accounting is processed.
From $2,900 excl. VATone-time payment, no monthly subscription
Budgets and expenses in a CRM, with variances visible in time. Budgets are set by department and period, and the expenses recorded in the application are compared with them at any moment. A separately licensed module, from the Procurement menu. Lifetime licence, installation on the company’s server and unlimited users.
Works together with: Zarina SMART, Procurement and suppliers, Payments and receipts.
The problem is not the lack of a budget, but how late you find out how much of it has been used.
The module adds the department structure, budgets by period and the comparison with recorded expenses.
Reporting follows the real organisation chart.
The plan becomes a record, not a file.
Execution is available at all times.
Every amount has its justification.
Commitments do not stay outside the records.
The information reaches the decision-makers.
Direct effects of having the budget and the expenses in the same system.
The correction can be made during the current month.
Every budget has an owner.
The overall picture is available immediately.
Audits no longer block the team.
Next year’s budget is built on history.
The first source of savings you can actually identify.
The mechanism is simple, and that is exactly why it works without extra administrative effort.

The structure follows the company’s real organisation chart, not one invented for reporting. Each department has an owner.
Each department receives a value for the chosen period. Later revisions stay in the record’s history.
Each expense gets a department, a category, a supplier and an attached document. The coding is what makes the report usable.
Committed amounts can then be tracked alongside expenses already recorded, before the invoice arrives.
The comparison between budget and expenses is available permanently, without waiting for a monthly process.
The position can be sent automatically, at set intervals, to the people who make cost decisions.
A budgets module does not produce useful information if expense coding is not disciplined. We say this before implementation.
An exhaustive list never gets used.
Without it, the report stays incomplete.
The justification goes with the amount.
Discipline is established, not assumed.
Useful information is what is available at the moment of the decision, not what is correct at month end.
Budget, recorded expenses and available amount, for each department, over the chosen period.
Differences appear explicitly, so the discussion starts from figures, not impressions.
The comparison with previous periods shows whether a variance is an incident or a trend.
Grouping by category shows where consumption is concentrated and where an intervention makes sense.
Where the spend is concentrated, a renegotiation has an immediate effect.
The position arrives by email at set intervals, without anyone compiling it by hand.
Mechanisms that remove re-entering data and compiling reports by hand.
There is no second register to keep.
Information flows without being asked for.
Taking over existing records is quick.
Every change stays recorded.
The data reaches the accountant without manual work.
Revenue and costs are compared in the same system.
Cost information is sensitive internally. Visibility is configured explicitly.
We do the configuration at implementation, on the company’s real structure.
Reporting follows the organisation chart.
Fewer and clearer, not exhaustive.
The starting point of the comparison.
Expenses come from it.
You decide who sees what.
Discipline decides the quality of the report.
The module gives management control over costs. It does not replace accounting and does not block operations.
We prefer to say from the start in which situations the module is not worth its cost, so the sales conversation does not begin with the wrong expectations.
The situations in which the module pays for itself quickly.
The situations in which we recommend not buying it now.
The module has its own manifest and is activated by licence, in the procurement menu.
It contains the departments, the budgets by period and the comparison with expenses.
The mandatory core brings users and roles, clients and contacts, a lead and sales pipeline, custom fields and 15 interface languages.
Expenses and orders come from the procurement and suppliers module, so activating them together is recommended.
Package composition and prices by edition are on the pricing page.





















You pay once. Everything that follows is written here, not in hidden conditions.
It is part of the Procurement, costs and budgets package: $450 excl. VAT, on top of the core ($2,320). Bought separately, together with the core: $2,770.
Cheaper in a bundle. The tiers group several packages at a price lower than their sum:
List prices, excl. VAT, one-time payment, unlimited users. The struck-through price is the sum of the packages bought individually. Current offers apply on the pricing page.
Over 3 years, the subscription costs $10,480; the Zarina Enterprise licence costs $6,970, once.
An indicative comparison: enter the subscription price you pay now. The licence does not grow with the number of users.
A six-page document with everything you need to know before a sales conversation. No obligation and no sales call.
We install Zarina CRM on your hosting, configure it around your own workflow and train your team. From that moment on, the application is an asset of your company, not a recurring expense.