See it on your setup
Acumatica

Acumatica, with the subaccount structure right first time.

In Acumatica the subaccount structure is configured early and is very hard to change once it is live, and one tenant or several decides what the companies can share. Your consultant runs the project and looks after the customer. In the background, Votis's AI agents work through those calls with the customer, the way your firm builds Acumatica.

Where Acumatica projects get stuck.

One tenant or several gets decided early and is painful to undo.

The subaccount segmented key is designed in a spreadsheet, then nobody can change it when the business adds a division.

Inter-branch accounts and approval maps get built from memory the week before go-live.

How an Acumatica project runs in Votis.

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

  1. 01Tenants and companiesWhat each legal entity needs, and how they are grouped.
  2. 02BranchesBranches, and whether they must balance.
  3. 03Subaccount keySegments, lengths and values, set before the chart.
  4. 04Chart and ledgersAccounts, ledgers and financial periods.
  5. 05Maps and approvalsInter-branch account maps and approval maps.

What Votis settles with your customer.

Tenants, companies and branches.

Whether the companies can agree on one chart of accounts and live in one tenant, or need separate tenants.

A subaccount key that lasts.

Every segment of the subaccount with its length and meaning, set up front, with branches kept out of it as Acumatica recommends.

Chart and ledgers.

The chart of accounts, actual and budget ledgers, and financial periods, captured as the customer answers.

Inter-branch and approvals.

Inter-branch account maps where branches balance, and approval maps for who approves what.

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 Acumatica Rollout · configuration, and the decision behind each line
5 lines configured · each traced to a decision
Configured
Value
The decision behind it
Decided by
Tenants
1 tenant, 3 companies
They agree on one chart, so companies in one tenant
Anna Meyer, September 2
Branches
6, balancing
Each branch produces its own balance sheet
David Chen, your consultant
Subaccount key
DEPT-PROD, 3 + 2 characters
Branch kept out of the subaccount
Agent, on your consultant's rule
Chart of accounts
188 accounts
Cleaned up from the old 610
From the workbook, September 3
Inter-branch map
Due to and due from, per pair
Branches balance, so every pair needs mapping
Agent, on your consultant's rule
Every configured line carries the decision behind it: who made it, when, and why.
Customer
We're adding a branch in Leeds from April.
Checked
Inter-branch account map rechecked. Seven branches, every pair mapped. The subaccount key does not change.
Captured
Signed off and posted to Acumatica. 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