Divako Settlement · Allocation
Any rule your building actually uses.
Split by metered usage, by floor area, equally, or by ownership fraction – per cost category, per building. Compose the strange cases from parts instead of ordering custom code. Every result stays traceable back to the readings that produced it.
Common water · Building A
composed rule
Building main
Σ apartment meters
Common (virtual)then split
by floor area
residential units only
remainder → cooperative
Cost allocation · you control
Your building. Your rules. Our maths.
Every cost type splits differently. Define each one once – water by consumption, heating by area, a service fee equally – and the system runs it forever after. Save a setup as a template and reuse it across every project that works the same way.
no developer needed →
Formula builder
Compose the hard cases. No developer.
Most buildings need four standard rules. The fifth one is always strange – a kindergarten on the ground floor, a shared heating circuit, one supplier bill covering three zones. The formula builder covers those with parts you combine yourself.
- 01Sums and differences of meters
- 02Scalars and linear combinations
- 03Share of a total
- 04Fixed and variable parts in one rule
- 05Filters on unit attributes – residential, commercial, kindergarten
- 06Per-zone decomposition of a single supplier bill
Save a finished setup as a template and reuse it on every project that works the same way.
Virtual meters · fill the gaps
Found the leftover. Split it fairly.
Common-area water, corridor heat, shared lighting – calculated from the meters you already have. Every value traceable back to its source.
Building main
412.6 m³
−Apt 1A68.2 m³
Apt 1B42.8 m³
Apt 2A91.5 m³
Apt 2B55.1 m³
…+3124.0 m³
Common (virtual)
30.9 m³
Properties · people · dated roles
Who lived where, when – handled.
Mid-period move? Change of ownership? Empty unit? Every role has a start and end date – costs split by the days each party was responsible. Vacancies go to the cooperative, automatically.
owner
tenant
payer
care-of
vacancy → coop
Data quality
Your data is probably messy. That's fine.
Nothing here assumes a clean dataset. The problems surface as a readiness checklist before you settle – not as a wrong invoice three weeks later.
Readiness · March 2026
- Readings present for all 48 units
- Meter types mapped
- 2 outliers flagged for review
- 1 unit without a floor area
Period stays open until the blockers are cleared
Import from spreadsheets
Unit rosters and meter lists from Excel or CSV, with column mapping, alias detection and a staged preview before anything is written.
Validation before settlement
Missing readings, outliers, unmapped meter types, units without an area, units deliberately without a meter, conflicting readings – all surfaced up front.
Estimation and rebasing
Replaced meters, rollovers and gaps are handled without corrupting the history behind them.
Coverage gates
A period cannot be settled while known blockers remain.
Guided onboarding
A get-started checklist walks a new cooperative from an empty project to its first settled period.
Readings · automatic
No clipboard. No spreadsheet. No problem.
Meters send their readings in by themselves. The system takes an end-of-month snapshot – local time zones handled – and labels every value with where it came from. People sign in with the Divako accounts they already have.
automatic
mobile app
handover
estimate
March 2026
MTWTFSS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
↳ End-of-month snapshotEvery line on every invoice can be expanded into the readings, the rule and the numbers that produced it.
Next
Bring us the rule that broke your spreadsheet.
If you can describe how the cost should be split, we can usually build it during the call – and show you the invoice line it produces.