Visma NetThe subaccount

The subaccount. Your own structure.

Your dimensions decide what you can track for as long as you have the system. Here is what they are, how they work and what a structure usually looks like. You can build your own further down.

Free workshop, 45 minutes. The process map is yours either way.

Set up in Visma Net Core: the whole system for SEK 75,000

What it is

One field, your values.

Every line you post in Visma Net is coded with your own dimensions. All your reporting rests on them: profit per project, costs per unit, revenue per location. Set them when the line is created and the reports fall out on their own. Leave them out, and the reporting gets rebuilt in Excel every month.

What it is

You choose the segments.

The subaccount is a field on every posted line, split into segments that you name and size yourselves. Thirty characters in total is the limit; the number of segments is a choice, not a system limit. Each segment becomes a dimension that every line can be tracked, approved and reported on, such as department, cost center, project, location or business area.

The subaccount · anatomy

This is what the subaccount looks like on every line you post. The example splits ten characters across three segments.

  1. 01 Location Where the job was done. Gives you revenue and margin per location without anyone splitting lists afterwards.
  2. 200 Cost center Which part of the business carries the line: installation, service or purchasing. Also controls who approves.
  3. 26004 Project Which job. Revenue, material cost and time spent are collected per project and can be tracked while it is running.
The structure is yours, not the system's. The only limit is 30 characters. How you split them, and what you call the parts, is up to you. Three segments of five characters works. Seven of four too. Thirty of one, if you like. Each segment becomes its own dimension in the reports and in the approval flow.
Step 1

Code the line when it is created.

The subaccount is set on the invoice line, not in the report afterwards. Account and subaccount follow it all the way into the general ledger, and if you change the project on the line, the amount moves with it. It is the only place where the reporting can be right without rework.

Visma Net · Accounts receivable · Customer invoices · Document details

Document detailsFinancial detailsInvoice addressVATSalesperson commissionDiscount detailsApplicationsAttachments
View recurring transaction
*Item IDDescriptionQuantityUoMUnit priceManual
amount
Discount,
%
Discount
amount
AmountManual
discount
*AccountAccount description*Subaccount
225,000.00202,500.00Sales of goods, Sweden 25% VAT
16,250.0016,250.00Sales of goods, Sweden 25% VAT
Two lines on the same invoice, editable as in the system. Change the item, account or subaccount, change quantity and price, or add a line with + in the toolbar. Everything you change here carries through to the panel below.
Step 2

Track without rework.

The balances are already split by location, cost center and project. Nobody exports, nobody pastes, nobody rebuilds the pivot table every month. You filter on the segment you want to see and read the result straight from the system.

Visma Net · General ledger · Account balances

BalancesTransactionsPeriods
Financial period: 08-2026
ValueDescriptionLinesAmount
26004Villa Lind 8 kW2218,750.00
Total2218,750.00
The amounts come from the lines above. Change the grouping to location, cost center or account, or filter on a single account. Same postings, no recoding and no export. Set a segment to None and the amount lands there instead: still in the ledger, but outside the reporting you wanted.

We set the first structure together with you in week one, before the first invoice is posted. The subaccount itself can be extended later, but values that were never set on old journal transactions cannot be filled in without reposting. That is why we ask the questions about your processes early instead of at go-live.

Build your own

What matters for you to track?

Enter the dimensions you want to be able to track. The example value sets how long the segment is, and together they cannot exceed 30 characters. That is the only limit: add as many as you like as long as the characters last.

Start from

10 of 30 characters

With that subaccount you can track by location, cost center and project.

The system sets no limit on the number of segments, only on the characters. Our advice is still to keep the number down: more segments give finer tracking but more fields to fill in on every line, and most companies land on three or four. We go through the choice with you before anything is set up, and include what you will need to answer in two years, not just today.

The project model

You test with your own data
from week one.

What makes implementations long is rarely the amount of work, but the waiting in between. With us, setup, testing and training run side by side from week one, so what you find changes the configuration every week instead of at go-live.

Typical ERP project ≈ 6 MONTHS
KickoffMonth 2Month 4Go-live
The consultant configures
You are in the system
months without you in the environment
Questions about the standard flows
How we do it 4 WEEKS
Week 1Week 2Week 3Go-live
We fetch, convert and import your registers
We configure as we go, to your needs
You test on your own data
What you find changes the configuration every week, not at go-live
Questions about the standard flows
Processes set together and adjusted until they fit
Automation where it makes a difference
Ongoing management, long after go-live

The environment is 75-90% complete with your own registers the first time you log in. After that, the same row exists in both models, and the difference is when it happens: the questions about the standard flows come in week two, while there is still time to act on them, instead of the morning you are supposed to start invoicing for real.

No big delivery at the end

You see the system take shape instead of having it presented in the final week. What feels wrong has time to become right.

Training runs in parallel

Not a full day at the end that nobody remembers. Every week, in the environment you will work in, with your own data.

Standard where it is best

We start from Visma's proven flows where they give you more than your old way of working, and set the system up around your processes where those work better. If something suits you better another way, we change it within the price.

The workshop

A workshop on your flows, free of charge.

Tell us briefly about your business and we will host a free workshop where we go through how work and money actually move through your company, from order to posted and reconciled, and draw it up step by step, like the excerpt next to this. The map is yours whether or not we build it.

What you get from the workshop

  • The process mapYour flows drawn step by step. Yours to keep, whatever you decide.
  • Our assessmentWhat is worth changing on your side, and what Visma Net should be shaped around.
  • A planBuilt around your calendar, starting when it suits you.
  • A fixed priceCalculated from the map and set before you say yes.

The workshop is free. If it's not a fit, we'll tell you.

Book your free workshop

CharlieTed

You'll meet Charlie and Ted. The same people from the first call to go-live.

We reply within one business day. Your details are only used for this.

1 · Order intake, auto-check 2 · Confirmation & delivery plan 3 · Delivery 4 · Invoicing 5 · Payment, posting & visibility no yes no yes no yes no Order from CRM Webshop / EDI ✨ Auto-check price · stock · credit Credit OK? To credit review Order created Confirmation sent automatic · to customer Delivery plan warehouse · logistics Awaiting delivery Delivered? Reminder to warehouse Complete? Backorder created End Packing slip Invoice created Finance overview Invoiced Invoice sent e-invoice · Peppol Payment tracked bank file · automatic Manual approval exceptions only Reminders sent automatic · escalating Paid? Reconciled posted · automatic