Custom AccountView integration development
Appfront builds custom integrations around Visma AccountView, the accounting and ERP package that many Dutch SMEs and accountancy firms use as their financial core. We connect AccountView to your webshop, CRM, invoice recognition, project administration and payment providers via the Visma API, XML/DTC import or a direct Pervasive bridge, so that bookings, debtors and master data are recorded once and are correct everywhere.
What is an AccountView integration?
AccountView is an accounting and ERP package from Visma that has a strong position mainly among Dutch SMEs and accountancy firms. The package manages the general ledger, debtor and creditor administration, VAT returns, fixed assets, project administration and, in many setups, hours, cost centre and dimension administration. For administration firms, the multi-administration setup is attractive because a single installation can host dozens to hundreds of client administrations.
An AccountView integration ensures that this financial heart does not become an isolated island behind a desktop licence, but works together with the rest of your IT landscape. In practice that means: webshop orders and invoices flowing daily from Magento, Shopify or WooCommerce into AccountView; debtor balances visible in real time in HubSpot, Salesforce or Pipedrive on the customer record; incoming invoices read by an invoice recognition solution that land as booking proposals in the creditor administration; project and hours administrations that post hours, cost centres and projects; and payments via Mollie or Adyen that are automatically matched against open items.
Appfront builds these integrations to measure for organisations that want more than a standard connector. We work via the Visma API, XML/DTC import or, where needed, a direct Pervasive bridge. We align the mapping with your actual general ledger and cost centre setup and make sure the integration grows with new webshops, new payment providers, e-invoicing via Peppol or a migration to a newer Visma platform. Our role is often that of technical link between AccountView, the webshop platforms, the CRM and the OCR and payment APIs, and therefore the architect of the wider integration layer around your accounting. If you first want to understand the basics of such an integration, what is an API integration is a good starting point.
General ledger and VAT posting
Sales and purchase invoices are posted to the correct general ledger accounts, VAT codes and journals, automatically and consistently across all source systems. VAT returns and correction runs therefore stay predictable and easy to check.
Debtor status in your CRM
Debtor balance, open items and payment behaviour appear on the customer record in HubSpot, Salesforce or Pipedrive. Sales and account management can immediately see who is behind on payments and align negotiations or upsells accordingly.
Invoice recognition and posting
OCR-scanned incoming invoices are proposed as posting lines against the correct creditor, general ledger account and cost centre. The bookkeeper reviews and confirms; the integration writes the posting document to AccountView.
Our development process for AccountView integrations
We work to a proven methodology that removes early uncertainties and ultimately delivers an integration your bookkeeper can trust. From the initial review of your AccountView setup, journals and master data through to go-live and ongoing management, every step is aimed at an integration your team can understand, monitor and adjust itself.
We map out which systems need to connect to AccountView, which master data takes precedence, which direction the data flows should take and which tax and accounting rules apply.
We design the integration architecture, choose between the Visma API, XML/DTC import or a direct database bridge for each flow, and define the retry, idempotency and error-handling strategy.
Implementation with automated tests, structured logging and monitoring from day one. You will see working builds along the way on an acceptance AccountView environment, with test data.
Controlled go-live with data validation, parallel run and a safety net, followed by ongoing management, monitoring and further development together with your bookkeeper or accountant.
What an AccountView integration delivers in practice
Every AccountView integration is set up specifically for your type of organisation, journal structure and adjacent systems. Below are the functionalities we most often deliver for SMEs, e-commerce organisations and accountancy firms that use AccountView as their financial core. For each scenario we choose between the Visma API, XML/DTC import or a direct Pervasive bridge, depending on what is most stable and maintainable for that specific flow.
Webshop → AccountView
Magento, Shopify and WooCommerce orders, customers, invoices and credit notes flow into AccountView daily or in real time. With correct VAT codes per country category, recognition of existing debtors, and postings to the correct sales journal and general ledger setting.
CRM synchronisation
Debtors, contact persons, open items and payment behaviour from AccountView appear in real time on the customer record in HubSpot, Salesforce, Pipedrive or Zoho CRM. In the other direction, new customers created in the CRM are neatly set up as debtors in AccountView, including VAT status and country.
Invoice recognition → posting proposal
Incoming invoices from an OCR tool are converted by the integration into proposed bookings against the correct supplier, general ledger account, cost centre and VAT code. The bookkeeper reviews and posts; the integration records the booking with a full audit trail.
Timesheet, project and cost centre administration
Hours from timesheet tools and projects from a PSA system are posted to the correct projects, cost centres and dimensions in AccountView. This keeps actuals, recharges and project results per engagement visible to both finance and project managers.
Payment reconciliation for Mollie & Adyen
Payments, refunds and chargebacks from Mollie or Adyen are matched to open items in AccountView. Bank entries are either suggested or processed automatically; discrepancies, duplicate payments and currency conversions each get their own workflow.
Peppol & UBL 2.1 e-invoicing
Outgoing sales invoices are generated in UBL 2.1 format and exchanged via a Peppol access point with government bodies or business customers. Incoming e-invoices received via Peppol arrive directly as booking proposals in the supplier ledger.
Typical use cases in practice
An AccountView integration looks very different from one organisation to the next. We often see a number of recurring patterns, and for each we have a working setup that pays close attention to master data mapping, journal choices and the right direction of data flows. Below are four scenarios in which AccountView typically forms the financial heart, and integrations make the difference between manual retyping and a scalable administration.
E-commerce with Magento, Shopify or WooCommerce
Online retailers producing hundreds to thousands of invoices a day who want to process them in AccountView without the bookkeeper falling behind. Orders, customers, invoices and credit notes flow through a controlled process, with VAT handled per country category and automatic reconciliation of payment orders from Mollie or Adyen.
B2B service providers working with a CRM
Consultancies, IT suppliers and business services firms that run sales and account management from HubSpot or Salesforce, but keep invoicing and administration in AccountView. The integration ensures that the sales colleague in the CRM can see the debtor balance, open items and payment behaviour, without having to log in to AccountView.
Accountancy and administration firms
Accountancy firms that manage dozens to hundreds of client administrations in AccountView and want to pre-book incoming post through an OCR stream. An integration connects scan-and-recognition tooling to the correct client administration, reads the invoice and produces a checked booking proposal, including links to receipt apps and bank transactions from client bank accounts.
Project organisations with timesheet and project administration
Agencies, technical service providers and construction companies that record hours and project costs in a separate PSA tool and handle the financial side in AccountView. Hours, projects, cost centres and recharges flow through the integration, so project results and recharges per engagement remain visible.
Technology we use
AccountView has historically run on a Pervasive database (PSQL/Btrieve) under the hood, so modern integrations preferably go through the Visma API or a structured XML/DTC import. For each flow we choose the most stable route. Webhooks are combined with a retry policy and idempotency keys wherever possible, so that the same booking is never posted twice, even after network interruptions or a restart of a source system.
Why Appfront for your AccountView integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, from e-commerce businesses and B2B service providers to accountancy and administration firms. We always begin with a thorough analysis of your AccountView setup and existing processes. An integration must not only work technically, but also add practical value to your bookkeeping and to the way your team works.
For every integration, we write clear documentation so that your own team, or a future supplier, can understand and manage the integration. No black box that only we understand, but transparent code and clear agreements on monitoring, alerting and maintenance. On the tax and bookkeeping side, we of course work with your accountant or AccountView consultant. We handle the technology, and they oversee the master data set-up.
You work with a dedicated point of contact who understands both the technical and the functional side, and who speaks the accounting terminology themselves. This keeps lines short, avoids miscommunication between three parties and speeds up decisions when trade-offs arise during the build, for example when choosing between the API and XML import for a particular flow.
See also our wider services on API integrations, automating invoice recognition, custom order management systems and what is an API integration.
- Experience with the Visma AccountView API, XML/DTC import and Pervasive bridges
- Specialist in webshop, CRM and payment integrations
- Familiar with Peppol, UBL 2.1 and e-invoicing
- Understands general ledger, journal, VAT and cost centre set-up
- Secure by default: API key rotation, webhook signature validation, scoped permissions
- Idempotency keys and retry policies to prevent duplicate bookings
- Structured error handling and clear escalation paths
- Comprehensive logging and monitoring from day one
- Clear documentation that your team and accountant can read
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
- A way of working tailored to your existing IT landscape and to your accountant
Security, GDPR and the tax retention obligation
Accounting data inherently contains personal data (customer names, contact persons, bank account numbers) and business-sensitive information (revenue, margins, cost structure). This means every AccountView integration falls under the GDPR and under the Dutch seven-year tax retention obligation for financial records. Appfront builds every integration in line with the OWASP ASVS and limits personal data to what is strictly necessary for the process. On the tax side, we ensure that synchronisation logs, source documents and corrections are recorded in an audit-proof way so they remain traceable during an inspection.
For outgoing and incoming e-invoices, we follow the Peppol standards and UBL 2.1, so you can exchange electronic invoices with government bodies and business partners that require them without any extra steps. Webhook signature validation, scoped OAuth permissions, encryption in transit (TLS 1.2+) and at rest, and strictly separated rights per integration are standard parts of the delivery. We document the data flows between AccountView and the connected systems for your record of processing activities, so you can demonstrably comply with the GDPR.
More on our security approach: information security policy and CVD policy.
- GDPR-compliant data processing and data minimisation
- Seven-year tax retention obligation respected in archiving
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows per booking
- Idempotency keys prevent duplicate financial bookings
- Automatic retries and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management in line with best practice
- Peppol- and UBL 2.1-compatible e-invoicing
Frequently asked questions about AccountView integrations
Answers to the questions we are asked most often about AccountView integrations for SMEs, e-commerce businesses and accountancy firms.
An AccountView integration is a technical connection between Visma AccountView and another system, such as your webshop, CRM, invoice recognition tool, project and time administration, or a payment provider. The goal is for bookkeeping and master data to be synchronised automatically, without manual re-entry between systems. In practice, this means daily invoice sync from Magento, Shopify or WooCommerce, real-time debtor status in HubSpot or Salesforce, and automatic processing of receipts and incoming invoices that have been classified by invoice recognition.
We see a consistent set of recurring patterns: order and invoice transfer from Magento, Shopify, WooCommerce or a bespoke platform into AccountView; CRM synchronisation of customers, contacts and debtor balances with HubSpot, Salesforce or Pipedrive; invoice recognition flows in which OCR-scanned incoming invoices are automatically proposed as bookings; time and project administration that posts hours, cost centres and projects; and payment integrations with Mollie or Adyen that match payments and chargebacks against open items.
AccountView has historically used a Pervasive database (PSQL/Btrieve) that custom tools connect to directly. Modern integrations preferably go through the Visma API or an XML/DTC import that AccountView accepts on the input side. For each scenario we choose the most stable route: a REST API for real-time, XML import for batch and bulk flows, and a direct database bridge only where the API and import are too limited. Authentication, a retry policy with idempotency keys and clear error handling are standard parts of every integration.
Scope depends on the number of systems to integrate, the direction of data flows (one-way or bidirectional), the required synchronisation frequency (real-time via webhooks versus periodic via batch), the complexity of master data mapping (general ledger accounts, VAT codes, cost centres, debtor and creditor numbering), and requirements for logging, monitoring and recovery. Any Peppol or UBL 2.1 integrations for e-invoicing also count. After a no-obligation analysis, we will prepare a clear quote covering scope, phasing and timeline.
Yes. Bookkeeping data falls under the GDPR as well as the seven-year statutory retention obligation. Appfront builds to OWASP ASVS, limits personal data to what is strictly necessary, logs every synchronisation in an audit-proof way, and ensures that backups and archiving comply with the retention period. For e-invoicing we follow the Peppol and UBL 2.1 standards so that outgoing and incoming invoices can also be exchanged electronically with government and business partners. We document the data flows between AccountView and the connected systems for your record of processing activities.
Yes. Appfront regularly takes over existing AccountView integrations, including those originally set up by another party or built in-house by internal IT. We review the API calls or XML import flow, error handling, monitoring and data quality, document the current setup and propose improvements. From there, we can handle changes, extensions and ongoing management, such as adding a new webshop, an additional payment provider or a Peppol integration, without disrupting the existing booking flow.
AccountView is built for Dutch SMEs and accountancy firms. It suits accountancy practices managing multiple bookkeeping administrations under one licence, mid-market businesses that need in-depth general ledger and VAT functionality, and organisations with project or time-recording administration. Less suitable for multinational groups with multi-entity, multi-currency and centralised reporting requirements; products such as Visma.net Financials, Exact Globe or a larger ERP platform are often a better fit for those.
Yes. Most integration projects also involve an AccountView consultant, accountant or bookkeeper who oversees the functional side and master data setup, including general ledger accounts, VAT codes, journals, cost centres and dimensions. We focus on the technical link: integrations, mappings, error handling and monitoring. This division of roles works best, as fiscal and bookkeeping decisions are not the responsibility of a software company, yet they directly affect the integration.
Read more
Explore related topics around AccountView, API integrations and the broader financial automation we build for SMEs and e-commerce organisations.
Talk to us about your AccountView integration
Tell us how you use AccountView and which systems the package needs to connect with: webshop, CRM, invoice recognition, time registration, payment providers or a Peppol bridge. We are happy to help with scope, priorities, master data mapping and alignment with your accountant. A no-obligation first conversation will give you a clear picture of the options and the most stable route, whether that is the Visma API, XML import or a direct database bridge.