Odoo vs AccountView.
What does your next decade run on?
AccountView is trusted Dutch accounting software: decades of history, tens of thousands of businesses and accounting firms, solid bookkeeping. It is actively maintained by Visma - no end-of-life has been announced. But two facts deserve the table. One: AccountView is built on a Visual FoxPro database core, a Microsoft technology that left support in January 2015 - the foundation has had no vendor for over a decade. Two: Visma itself positions AccountView as the 'trusted' option next to its 'future-oriented' cloud products - the vendor is pointing at the exit. The escape route Visma offers is Visma Net, and in our experience that is a heavy implementation, clearly designed with other (larger, Nordic) organisations in mind. So if a move is coming anyway, the real question is what your next ten years should run on. In one line: AccountView works today. The question is the foundation under tomorrow.
How long can you stay on AccountView?
Few comparisons on this site can I write from first-hand experience the way I can write this one. I was an AccountView partner for years and converted hundreds of companies and many hundreds of administrations - a lot of them precisely TO AccountView. In its early days it was a very good company - strictly, hierarchically run, as I remember it, but with a very good product because of it. So when I am critical of where it went, that is not an outsider talking.
What is remarkable is how old the shelf-life question already is. Around 2005, 2006, the first stories went round that Visual FoxPro - the technology underneath AccountView - would reach end-of-life. That is twenty years ago, and to this day plenty of companies still run on it. That says something positive: the interface is so friendly that people do not want to leave. But it also says something uncomfortable: all those companies sit on software whose foundation has been living on borrowed time for two decades.
The real problem is the exit Visma offers. There is no online version of AccountView. Visma eAccounting is a stripped-down product - fine for a small administration, no successor for anyone using AccountView seriously. And Visma.net, the intended step up for larger companies, is a beast of an application to implement; I have experienced that first-hand. When I recently did a commercial interim assignment for an AccountView Expert Center, the same picture emerged there: hardly any of its clients had actually made the move to Visma.net. The upgrade path the vendor points to is, in practice, massively not being walked.
Why we see Odoo as the natural successor: it has the likeability AccountView always had - accessible, friendly to the user - combined with everything you may expect from a modern online application. And on top of that, the part that was never in AccountView: the full ERP layer, plus marketing and HR, in the same database as your books.
We are an Odoo partner, so read this with that lens. But the AccountView clients we have moved to Odoo are, without exception, very happy - and coming from someone who moved hundreds of administrations the other way, that should count for something. If you are on AccountView and nothing hurts yet: no acute reason to panic, it runs today too. Just do not wait until the foundation makes the decision for you.
- 01 The foundation: a core without a vendor since 2015 No acute problem today - and that is exactly how foundations age: quietly, until something around them moves. Windows, drivers, security baselines all keep moving.
- 02 What the vendor itself signals When the vendor's own brochure frames your package as the traditional option, the question is not if there is a next step - only when, and to what.
- 03 The escape route Visma offers - and our experience with it If the official next step is a heavy implementation anyway, compare it against every next step - not just the one in the same brochure.
- 04 Accounting package versus business platform For pure administration the package model is fine. For a trade business, the platform model removes the gaps instead of bridging them.
- 05 The accountant dimension Choose your platform for your operation, and bring your accountant along. Not the other way around.
At a glance
| Criterion | Odoo | AccountView |
|---|---|---|
| Positioning | Broad ERP / business platform | Dutch accounting software (Visma) |
| Best fit | SMB / mid-market integrating the whole business | SMBs and accounting firms, accounting-first |
| Technology base | Open source, Python/PostgreSQL, yearly releases | Visual FoxPro core (Microsoft support ended 2015) |
| Deployment | Browser-first (Odoo Online, Odoo.sh, self-host) | On-premise / hosted Windows application |
| Accounting | Native, on one ledger across the business | Strong and proven - the core |
| Orders & inventory | Native, flowing into purchasing and finance | Trade modules around the accounting core |
| eCommerce & portal | Native Website, eCommerce, Customer Portal | Via connectors |
| CRM & service | Native CRM, Helpdesk, Field Service | Not the natural core |
| Production | Native Manufacturing / MRP | Not the focus |
| Vendor's own direction | One platform, one codebase | Visma steers new growth to its cloud portfolio |
| Strongest point | Business-wide coherence on one model | Decades of trusted Dutch accounting |
Five questions that decide it
The foundation: a core without a vendor since 2015
Odoo runs on actively developed open-source technology (Python, PostgreSQL) with yearly releases - the foundation itself has a roadmap, thousands of contributors and no single point of abandonment.
AccountView stores and manages its data in Visual FoxPro tables - Visma's own integration documentation describes the FoxPro database underneath. Microsoft ended Visual FoxPro support in January 2015. Visma keeps maintaining the application, but the core technology has had no vendor for over a decade.
No acute problem today - and that is exactly how foundations age: quietly, until something around them moves. Windows, drivers, security baselines all keep moving.
What the vendor itself signals
Odoo puts all development into one platform: the version you buy is the version being developed, for every customer segment.
Visma maintains AccountView but markets it as the 'trusted, proven' choice next to its 'agile, future-oriented' cloud products. Read that as a roadmap: the energy and the new functionality go to the cloud portfolio, not to the FoxPro-based desktop line.
When the vendor's own brochure frames your package as the traditional option, the question is not if there is a next step - only when, and to what.
The escape route Visma offers - and our experience with it
Odoo is built for the European SMB and mid-market: implementations in weeks to months, per-user pricing, and Dutch accounting that matured years ago (banking, VAT, ICP).
Visma's intended successor is Visma Net. On paper a serious cloud ERP - we compare it honestly in our Visma comparison. In our experience, though, implementations are heavy for Dutch SMBs and the product is clearly designed with other (larger, Nordic) organisations in mind. That is our practice speaking, not a benchmark.
If the official next step is a heavy implementation anyway, compare it against every next step - not just the one in the same brochure.
Accounting package versus business platform
In Odoo, accounting is the result of the operation: orders, inventory, purchasing, invoicing and the webshop write to the same ledger, so the books reconcile by default.
AccountView is accounting-first, with trade modules and connectors around it. That model works - it is also the model where the webshop reads different stock than the sales desk, and Excel fills the gaps.
For pure administration the package model is fine. For a trade business, the platform model removes the gaps instead of bridging them.
The accountant dimension
Odoo gives the accountant a real-time view of the same environment the business works in - no exports, no period files, with bank feeds, VAT and ICP filings native to Dutch practice since v16.
AccountView is loved by accounting firms, and that matters: many businesses run it because their accountant does. But the accountant relationship survives a platform change - the data exchange becomes simpler, not harder.
Choose your platform for your operation, and bring your accountant along. Not the other way around.
Which one fits?
Choose Odoo if…
- You want your next decade on an actively developed foundation.
- Orders, inventory or a webshop belong with the accounting.
- You want browser-first working instead of a Windows install.
- You are consolidating separate tools onto one platform.
- You want per-user pricing and an open, extensible system.
- A move is coming anyway and you want to choose once, properly.
Choose AccountView if…
- Pure Dutch accounting is all you need, and it works today.
- Your accountant runs your administration in it and that suits you.
- You accept an on-premise/hosted Windows application.
- Your trade processes are light and well-served by the current setup.
- You prefer to wait for clarity on the Visma roadmap.
- Minimal change matters more to you than a future-proof base.
The best AccountView alternatives
We are an Odoo partner, so we are not neutral. But we come with history: our founder was an AccountView partner himself in the early 2000s and knows the product from the inside. The question is not whether AccountView keeps solid books - it does - but whether a standalone bookkeeping package still fits what your business needs today.
| Alternative | Business around the books | Dutch accounting | Cloud & modern | Accountant-friendly | Cost at scale | Short verdict |
|---|---|---|---|---|---|---|
| OdooTop pick | Yes - CRM, projects, inventory, sales native | Strong since the 2023 NL localisation: RGS, VAT, UBL, audit file | Fully cloud, modern | Own login + XAF export | Max ~€20/user/month all modules | Best if the books should be part of one platform |
| Exact Online | Partly (trade/project editions) | Strong, the NL standard | Cloud | Very common | Climbs per module | The safe Dutch middle road; breadth costs extra modules |
| Visma.net / Visma eAccounting | Limited | Good | Cloud | Good | Mid | The stay-within-Visma route; a logical sidestep, not a platform |
| AFAS | Broad (strong HRM/payroll) | Strong | Cloud | Good | Pricey as you grow | Broad Dutch suite, strong in HRM; rigid outside its own frames |
| AccountView (stay) | No - bookkeeping | Solid | Desktop heritage, cloud via hosting | Strong (accountant base) | Low | Fine if pure bookkeeping is genuinely all you need |
Which alternative fits which situation?
Briefly per option, so you can shorten the shortlist faster:
Odoo
Strongest if the books should become part of one platform: projects, inventory, quotations and CRM on the same system as the numbers. Since the Dutch localisation of Odoo Accounting (2023) - RGS, VAT filing, UBL, audit file - it is a fully-fledged Dutch accounting solution, with the rest of the business around it. Our founder, once an AccountView partner himself, felt the same thing at that release as he did with AccountView back then: finally a package that thinks from the customer’s perspective again.
Exact Online
The common Dutch cloud route. Solid and widely carried by accountants. Breadth (trade, projects) is bought per edition and module, and at its core it stays a bookkeeping package with extensions.
Visma.net / Visma eAccounting
AccountView is owned by Visma, so the stay-in-the-family route is Visma.net or eAccounting. A logical sidestep if you purely want modern bookkeeping - but it stays a sidestep within the same category, not a platform for the whole business.
AFAS
Broad Dutch suite, rock solid in HRM and payroll. Rigid outside its own frames, and costs climb as you grow. See also our AFAS alternative.
AccountView (stay)
Genuinely an option if pure bookkeeping is all you need and your accountant works comfortably in it. The boundary is the category: the business around the books keeps living in loose tools.
From AccountView partner to Odoo partner: why this page is honest
A personal note from our founder: "In the early 2000s I became an AccountView partner, switching over as an Exact partner. I was genuinely impressed at the time: well thought out, solid, and it thought along with the user. I did not get that feeling again for a very long time - certainly not with Exact or AFAS. Until Odoo shipped the Dutch localisation of Odoo Accounting in 2023. That same enthusiasm came back: finally a package that thinks from the customer’s perspective." So this page is not written by someone who only knows AccountView from the outside.
Why companies look for an AccountView alternative
In the leads we analysed the pattern was consistent: AccountView did the books just fine, but the business around it ran in Excel and loose tools. A wholesaler: "only running Accountview, but that is too little." A machine shop paired a thirty-year-old ERP with AccountView; an installer planned in a separate tool alongside; a construction firm complained that "changes are needed, but they do not get implemented". The bookkeeping is rarely the problem - the category is: a bookkeeping package does not run your business.
Odoo: accounting that thinks from the customer, on one platform
Since the Dutch localisation in 2023, Odoo Accounting is a fully-fledged Dutch accounting solution: RGS chart, VAT and EC sales filings, UBL invoicing, bank feeds, audit-file export and an own login for your accountant. The difference with AccountView is not the bookkeeping quality but what surrounds it: quotations, projects, hours, inventory and CRM on the same data model as the numbers. Every invoice, project and stock movement posts straight through - no re-typing between the operation and the administration.
How do you choose?
Three rules of thumb. One: if you purely want more modern bookkeeping and the rest of your business is well handled elsewhere, Exact Online or the Visma cloud route are fine sidesteps. Two: if your accountant leans heavily on AccountView and nothing else changes, staying can be the cheapest option. Three: if your business runs around the books in Excel and loose tools, the category is the problem and Odoo is usually the strongest choice - one platform instead of a bookkeeping package with satellites. Start from your biggest pain: for most AccountView users it is not in the books but next to them.
Odoo vs AccountView, frequently asked questions.
Is AccountView end-of-life?
Is AccountView really built on Visual FoxPro?
What is the best alternative to AccountView?
Is Visma Net not the logical successor?
Can I take my AccountView data to Odoo?
What does switching to Odoo cost?
Is Odoo Accounting fully-fledged for the Netherlands?
Can my accountant work in Odoo?
What is the easier switch: Visma.net or Odoo?
Is AccountView bad software?
Trusted today, or future-proof for tomorrow?
AccountView is not broken - that is what makes the decision easy to postpone. But foundations age quietly, and the vendor is already pointing at the exit. Book a fit-gap call and we will map what AccountView (and the tools around it) does for you today, and what one Odoo platform would look like - so you can decide on facts, not on the next brochure.
The most expensive software is the software that 'just works'.
Because the work around it - double entry, Excel checks, waiting time, errors - never shows up on your software invoice. It does land on your P&L, as labour cost and lost hours; you just never add it to the software bill. And the frustration your team feels every day stays completely invisible. Work out what it costs you per year: you can't capture work satisfaction in a spreadsheet. 60 seconds, no sales pitch - just a number that sticks.
Curious about realistic hours, cost and timelines? See the Odoo implementation benchmark →