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 postings, 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 with a strong position among Dutch SMEs and accountancy firms in particular. It manages the general ledger, accounts receivable and payable, VAT returns, fixed assets, project administration and, in many setups, time, cost centre and dimension administration as well. For accountancy firms the multi-administration set-up is attractive because a single installation can support dozens to hundreds of client administrations.
An AccountView integration stops this financial core from sitting as an island behind a desktop licence and has it work with the rest of your IT landscape. In practice, that means: web shop orders and invoices landing in AccountView daily from Magento, Shopify or WooCommerce; debtor balances visible in real time on the customer record in HubSpot, Salesforce or Pipedrive; incoming invoices captured by an invoice recognition solution arriving as booking proposals in the creditor ledger; project and time-tracking systems passing through hours, cost centres and projects; and payments via Mollie or Adyen being reconciled automatically against open items.
Appfront builds these integrations to order for organisations that want more than a standard connector. We work via the Visma API, XML/DTC import or, where necessary, a direct Pervasive bridge, align the mapping with your actual general ledger and cost centre setup, and make sure the integration grows with new web shops, new payment providers, e-invoicing via Peppol or a migration to a newer Visma platform. Our role is often that of the technical link between AccountView, the web shop platforms, the CRM and the OCR and payment APIs, and so the architect of the wider integration layer around your accounting. If you first want to understand the fundamentals of an integration like this, what is an API integration is a good place to start.
General ledger and VAT processing
Sales and purchase invoices are posted to the correct general ledger accounts, VAT codes and journals, automatically and consistently across all source systems. This keeps VAT returns and supplementary filing runs predictable and easy to audit.
Debtor status in your CRM
Debtor balances, open items and payment behaviour appear on the customer record in HubSpot, Salesforce or Pipedrive. Sales and account management can see at a glance who is falling behind and adjust negotiations or upsells accordingly.
Invoice recognition and posting
Incoming invoices scanned via OCR are proposed as booking lines against the correct creditor, general ledger account and cost centre. The bookkeeper reviews and confirms; the integration then writes the journal entry to AccountView.
Our development process for AccountView integrations
We follow a proven method that removes the first uncertainties early and ultimately delivers an integration your bookkeeper dares to trust. From the initial inventory of your AccountView setup, journals and master data through to go-live and ongoing management, every step is aimed at an integration that your team can understand, monitor and adjust itself.
We map out which systems need to connect to AccountView, which master data is authoritative, which direction the data flows need to go 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 see working builds along the way on an acceptance AccountView environment, using test data.
A controlled go-live with data validation, a 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 features we deliver most often 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 easiest to maintain for that specific flow.
Web shop → AccountView
Magento, Shopify and WooCommerce orders, customers, invoices and credit notes flow through to AccountView daily or in real time. With correct VAT codes per country category, recognition of existing debtors, and postings to the right sales journal and general ledger settings.
CRM synchronisation
Debtors, contacts, outstanding 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 in the CRM are created neatly as debtors, including VAT status and country.
Invoice recognition → posting proposal
Incoming invoices from an OCR tool are converted by the integration into proposed postings to the right creditor, general ledger account, cost centre and VAT code. The accountant reviews and posts; the integration writes the posting with an audit trail.
Time, project and cost centre administration
Hours from timesheet tools and projects from a PSA system are posted to the right projects, cost centres and dimensions in AccountView. This keeps realised hours, recharging and project results per assignment visible to both finance and project managers.
Mollie and Adyen payment reconciliation
Payments, refunds and chargebacks from Mollie or Adyen are matched to outstanding items in AccountView. Bank postings are proposed or processed automatically; differences, duplicate payments and currency conversions get their own workflow.
Peppol and UBL 2.1 e-invoicing
Outgoing sales invoices are delivered in UBL 2.1 format and exchanged via a Peppol access point with government bodies or business customers. Incoming e-invoices via Peppol arrive directly as a posting proposal in the creditor administration.
Typical use cases in practice
An AccountView integration turns out very differently for every organisation. We see a number of patterns come up again and again, and for each of them we have a working set-up with attention to master data mapping, journal choices and the right direction of the data flows. Below are four scenarios where 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 that produce hundreds to thousands of invoices a day and want to process them in AccountView without the accountant lagging behind. Orders, customers, invoices and credit notes flow through a controlled process, with VAT per country category and automatic reconciliation of payment orders from Mollie or Adyen.
B2B service providers with a CRM-driven approach
Consultancies, IT suppliers and business service providers that run sales and account management in HubSpot or Salesforce, but keep invoicing and administration in AccountView. The integration lets your sales colleagues see the debtor balance, outstanding items and payment behaviour in the CRM, without having to log in to AccountView.
Accountancy and bookkeeping firms
Firms that manage dozens to hundreds of client administrations in AccountView and want to pre-post incoming mail via an OCR flow. An integration connects scan-and-recognise tooling to the right client administration, reads the invoice and delivers a controlled posting proposal, including integrations with receipt apps and bank transactions from clients' banks.
Project organisations with time and project administration
Agencies, technical service providers and construction companies that record hours and project costs in a separate PSA tool and process the financial side in AccountView. Hours, projects, cost centres and recharges flow through the integration, so that project results and recharging per assignment stay visible.
Technology we use
AccountView historically runs on a Pervasive database (PSQL/Btrieve) under the hood; modern integrations preferably go through the Visma API or a structured XML/DTC import. For each data flow, we choose the most stable route. Where possible, we combine webhooks with a retry policy and idempotency keys, so the same entry never lands twice, even during network glitches or a restart of a source system.
Why choose Appfront for your AccountView integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, from e-commerce companies and B2B service providers to accountancy and bookkeeping firms. We always start with a thorough analysis of your AccountView set-up and existing processes. An integration must not only be technically correct, but also add practical value to your bookkeeping and the way your team works.
For every integration, we write clear documentation and make sure 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. For the tax and accounting side, we naturally work together with your accountant or AccountView consultant: we take care of the technology, and they safeguard the master data set-up.
You work with a single point of contact who understands both the technical and the functional side and speaks the language of accounting. That keeps communication lines short, prevents miscommunication between three parties and speeds up decisions when trade-offs have to be made during the build, for example the choice between the API and an XML import for a specific data flow.
Also take a look at our broader services around API integrations, automating invoice recognition, custom order management systems and what an API integration is.
- Experience with the Visma AccountView API, XML/DTC import and Pervasive bridges
- Specialist in web shop, CRM and payment integrations
- Familiar with Peppol, UBL 2.1 and e-invoicing
- Understands general ledger, journal, VAT and cost centre set-ups
- Secure by default — API key rotation, webhook signature validation, scoped permissions
- Idempotency keys and retry policy to prevent duplicate entries
- Structured error handling and clear escalation paths
- Extensive logging and monitoring from day one
- Clear documentation that your team and accountant can read
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach aligned with your existing IT landscape and with your accountant
Security, GDPR and the statutory tax retention period
Accounting data by definition contains personal data (customer names, contact persons, bank account numbers) and commercially sensitive information (revenue, margins, cost structure). This means every AccountView integration falls under the GDPR and under the Dutch statutory seven-year retention period 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 make sure sync logs, journal entries and corrections are recorded in an audit-proof way, so they remain traceable in the event of an inspection.
For outgoing and incoming e-invoices we follow the Peppol standards and UBL 2.1, so you can exchange invoices electronically with government bodies and business partners that require it, without any extra manual steps. Webhook signature validation, scoped OAuth permissions, encryption in transit (TLS 1.2+) and at rest, and strictly separated permissions per integration are a standard part of every 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 about our approach to security: information security policy and CVD policy.
- GDPR-compliant data processing and minimisation
- Seven-year statutory tax retention period 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 postings
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management following best practices
- Peppol- and UBL 2.1-compatible e-invoicing
Frequently asked questions about AccountView integrations
Answers to the questions we get asked most often about AccountView integrations for SMEs, e-commerce companies and accountancy firms.
An AccountView integration is a technical integration between Visma AccountView and another system, such as your webshop, CRM, invoice recognition tool, project and time administration or a payment provider. The aim is for accounting and master data to be synchronised automatically, without retyping between systems. In practice, that means daily invoice syncs from Magento, Shopify or WooCommerce, real-time debtor status in HubSpot or Salesforce, and automatic processing of receipts and incoming invoices classified by invoice recognition.
We see a fixed set of recurring patterns: webshop transfer of orders and invoices from Magento, Shopify, WooCommerce or a custom platform to 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 journal entries; time and project administration that passes through hours, cost centres and projects; and payment integrations with Mollie or Adyen that reconcile payments and chargebacks against open items.
AccountView has historically used a Pervasive database (PSQL/Btrieve) that custom tools talk to directly. Modern integrations preferably run through the Visma API or through an XML/DTC import that AccountView accepts on the input side. For each scenario we choose the most stable route: 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.
The scope depends on the number of systems to be integrated, the direction of the data flows (one-way or bidirectional), the required synchronisation frequency (real-time via webhooks versus periodic via batch), the complexity of the master data mapping (general ledger accounts, VAT codes, cost centres, debtor and creditor numbering) and the requirements for logging, monitoring and recovery. Any Peppol or UBL 2.1 integrations for e-invoicing also count. After a no-obligation analysis, we put together a clear quote covering scope, phasing and lead time.
Yes. Accounting data falls under the GDPR and under the seven-year statutory tax retention period. Appfront builds according 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 meet the retention period. For e-invoicing we follow the Peppol and UBL 2.1 standards, so outgoing and incoming invoices can also be exchanged electronically with government bodies 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 the management of existing AccountView integrations, even if they were originally set up by another party or put together by internal IT. We review the API calls or XML import flow, error handling, monitoring and data quality, document the current setup and draw up improvement proposals. From then on we can handle changes, extensions and ongoing maintenance, such as adding a new web shop, an extra payment provider or a Peppol integration without disrupting the existing booking flow.
AccountView is built for Dutch SMEs and accountancy. It suits bookkeeping firms that manage multiple sets of accounts under a single licence, mid-market companies that need in-depth general ledger and VAT functionality, and organisations with project or time administration. It is less suitable for multinational groups with multi-entity, multi-currency and centralised reporting needs — products such as Visma.net Financials, Exact Globe or a larger ERP platform are often a better fit there.
Yes. In most integration projects, an AccountView consultant, accountant or bookkeeper sits at the table alongside Appfront to oversee the functional side and the master data set-up — ledger accounts, VAT codes, journals, cost centres, dimensions. We focus on the technical link: integrations, mappings, error handling and monitoring. This division of roles works best, because tax and accounting decisions don't belong with a software company, yet they directly affect the integration.
Further reading
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 it needs to integrate with — webshop, CRM, invoice recognition, time tracking, payment providers or a Peppol bridge. We're happy to help you think through scope, priorities, master data mapping and coordination with your accountant. A no-obligation first conversation gives you a clear picture of the possibilities and the most stable route — Visma API, XML import or a direct database bridge.