See it on your setup
Unit4

Unit4 ERPx, with attributes and relations settled properly.

Unit4 ERPx is built to be reconfigured, which makes the early modelling of attributes, relations and account rules the decisions that matter most. Your consultant runs the project and looks after the customer. In the background, Votis's AI agents work through them with the customer, the way your firm builds Unit4, then post the result by Unit4's own API.

Where Unit4 projects get stuck.

Attributes and relations are where Unit4 projects get clever, and where they get stuck.

Account rules are worked out in workshops weeks apart, then keyed in by someone who was not there.

Projects run a year or more, and the reasons behind early decisions are long gone by testing.

How a Unit4 project runs in Votis.

The order your consultant sets out, followed on every project.

  1. 01CompaniesThe client and companies, currencies and periods.
  2. 02AttributesEvery attribute the business reports on, and its values.
  3. 03RelationsHow attributes relate to each other.
  4. 04Account rulesWhich attributes each account requires.
  5. 05Post and checkSigned off, posted by Unit4's API, and read back.

What Votis settles with your customer.

Attributes that mean something.

Which attributes the business reports on, and the values in each, settled with the reason behind them.

Relations that hold.

How attributes relate to each other, so a cost centre always carries the right department, written down before anything depends on it.

Account rules.

Which attributes every account requires, captured as the customer answers and checked against your firm's rules.

Built for long projects.

A record of every decision that still makes sense twelve months in, whoever is on the project by then.

Every line, and the decision behind it.

Each configured line carries who decided it and why. When something changes, everything that depends on it is rechecked.

Tavelon Unit4 Rollout · configuration, and the decision behind each line
5 lines configured · each traced to a decision
Configured
Value
The decision behind it
Decided by
Companies
4 companies, one client
Shared attributes across the group, separate legal books
Anna Meyer, September 2
Attributes
Cost centre, Project, Activity, Region
The four things the business reports on
From the workbook, September 3
Relation
Cost centre → Department
A cost centre always rolls up to one department
David Chen, your consultant
Account rule
Expenses need a cost centre
No cost lands without an owner
Agent, on your consultant's rule
Account rule
Revenue needs Project and Region
Margin is reported by project and region
Anna Meyer, September 2
Every configured line carries the decision behind it: who made it, when, and why.
Customer
Attached the new cost centre list. Three have been added for the new team.
Checked
Relations rechecked. Every new cost centre rolls up to one department, and the account rules that need a cost centre still hold.
Captured
Signed off and posted to Unit4. Every line still traces back to a name and a reason.
ConfigurationBuild or buy

See it on your own setup.

A 20-minute call. We'll show you Votis on a system set up like the ones you implement.

See it on your setup