How to Connect Whitevision to Accounting Software
Quick Summary
Scanning and recognizing invoices only solves half the problem if your team still keys every transaction into your accounting system by hand. Whitevision B.V. Declaraties closes that gap by connecting directly to your accounting software, so approved invoices, credit notes, and expense claims post automatically once your team signs off on them. This guide explains how to connect Whitevision to accounting software step by step, covering authentication, field mapping, sync settings, and the checks you run before trusting the connection with real data. By the end, you will know exactly how to set up a reliable, ongoing link between document recognition and your financial records.
| Quick Facts | Details |
| Platform | Whitevision B.V. Declaraties |
| Core function | Automated posting of approved documents to accounting software |
| Typical setup time | 1–2 business days |
| Common connections | Exact Online, Twinfield, AFAS, Snelstart, e-Boekhouden, and similar platforms |
| Best for | Finance teams that want document processing and bookkeeping to work as one system |
Why Does Connecting Whitevision to Your Accounting Software Matter?
Recognition and approval only cover the first half of the invoice lifecycle. Once an invoice clears your workflow, someone still has to enter it into your general ledger, and that step is exactly where manual work reintroduces the errors automation was supposed to eliminate. Consequently, a direct connection between Whitevision and your accounting software removes that final manual step, so approved documents flow straight into your books without a second round of data entry.
Furthermore, this connection benefits more than just speed. When Whitevision posts directly to your accounting software, it uses the same supplier records, cost centers, and VAT codes your books already rely on, which keeps your financial data consistent across both systems. Therefore, the setup steps below focus on building a connection that stays accurate over time, not just one that works during the initial test.
How Do You Prepare Your Accounting System for Integration?
A successful integration starts before you open Whitevision’s settings menu. Taking a few preparatory steps in your accounting software first prevents mapping errors later.
What Access Do You Need in Your Accounting Software?
Before you begin, confirm that you have administrator-level access to your accounting platform, since the integration requires permission to create API credentials or authorize a connected app. Additionally, check whether your accounting software requires a specific subscription tier to support third-party integrations — some platforms restrict API access to their higher-tier plans. Finally, note your company’s administration or environment identifier, since Whitevision needs this to connect to the correct company file if your accounting software hosts multiple administrations.
How Do You Organize Your Chart of Accounts Beforehand?
Review your chart of accounts, cost centers, and VAT codes before connecting the two systems, because Whitevision maps its internal fields to whatever structure already exists in your accounting software. If your general ledger accounts use inconsistent naming or duplicate codes, clean these up first, since Whitevision cannot resolve ambiguity on your behalf during posting. A tidy chart of accounts at the start of integration saves you from correcting misposted entries later.
How Do You Choose the Right Integration Method?
Whitevision supports several ways to connect with accounting software, and the right choice depends on which platform your company uses.
| Integration Method | Best For | Setup Complexity |
| Native connector | Widely used platforms like Exact Online, Twinfield, and AFAS | Low |
| API-based connection | Accounting systems with an open API but no pre-built connector | Medium |
| Peppol e-invoicing | Companies exchanging structured electronic invoices | Low |
| Scheduled file export/import | Legacy or on-premise accounting systems | Medium to High |
Should You Use a Native Connector or a Custom API Connection?
A native connector is almost always the faster and more reliable option, since Whitevision‘s team has already built and tested the field mapping for that specific accounting platform. Choose the API-based route only when your accounting software lacks a native connector, and expect a slightly longer setup process, since your team or a technical partner needs to configure the field mapping manually. Consequently, checking whether your platform already has a native connector should be the first thing you confirm before starting the setup process.
How Do You Configure the Connection Step by Step?
Once you know which integration method fits your accounting software, the actual connection setup follows a consistent sequence.
How Do You Authenticate the Connection?
Navigate to the integration settings within Whitevision and select your accounting software from the supported platforms list. Whitevision then redirects you to your accounting software’s authorization screen, where you log in and grant Whitevision permission to read and write financial data. This authentication step uses your accounting software’s own security protocols, so Whitevision never stores your accounting login credentials directly.
How Do You Map Fields Between the Two Systems?
After authentication, Whitevision presents a field mapping screen where you match its internal fields — supplier, cost center, VAT code, payment terms, and general ledger account — to the corresponding fields in your accounting software. Review each mapping carefully rather than accepting the defaults automatically, since a supplier record with a slightly different name in each system can cause Whitevision to create a duplicate supplier instead of matching the existing one. Once mapped correctly, this configuration applies to every future document Whitevision posts, so getting it right during setup saves ongoing correction work.
How Do You Set the Sync Frequency and Direction?
Decide how often Whitevision should sync with your accounting software and which direction data flows. Most companies sync supplier and cost center data from the accounting system into Whitevision, so recognition stays current with any new suppliers, while approved documents flow from Whitevision into the accounting system after approval. Set the sync frequency based on your invoice volume — real-time syncing suits companies processing invoices daily, while a scheduled sync every few hours works fine for lower-volume operations.
How Do You Handle Multiple Company Administrations or Entities?
Companies that manage several legal entities or administrations within one accounting platform need to confirm that Whitevision connects each entity separately rather than mixing documents across administrations. During setup, select the specific administration or environment identifier for each entity, and repeat the authentication and field mapping steps for every additional administration you want to connect. This separation matters because a supplier that exists under one entity’s chart of accounts may not exist under another, so treating each administration as its own connection keeps postings accurate across your full company structure.
How Do You Test the Connection Before Going Live?
Before you rely on the integration for your full invoice volume, run a controlled test to confirm the connection behaves as expected.
What Should You Include in Your Test Batch?
Select five to ten real documents that represent your typical mix — a few standard purchase invoices, a credit note, and an invoice from a supplier with unusual payment terms. Process this batch through your normal Whitevision workflow, then confirm that each document appears correctly in your accounting software with the right supplier, amount, VAT code, and general ledger account. If anything posts incorrectly, revisit your field mapping rather than correcting the entry manually in your accounting software, since a manual fix does not resolve the underlying mapping issue.
How Do You Confirm the Connection Stays Reliable Over Time?
After your initial test succeeds, monitor the connection for the first few weeks of live use. Check periodically that new suppliers created in your accounting software also appear correctly in Whitevision, and that documents continue posting to the right accounts as your supplier list grows. This ongoing check matters because a connection that works perfectly during testing can still develop gaps as your business adds new cost centers, suppliers, or general ledger accounts.
What Common Issues Should You Watch For After Connecting?
A working integration can still run into a handful of predictable issues as your document volume grows. Knowing what to watch for helps you catch problems early.
Why Do Duplicate Supplier Records Appear After Integration?
Duplicate suppliers usually appear when a supplier’s name is entered differently in Whitevision than in your accounting software — for example, with or without a legal suffix like “B.V.” or “Ltd.” Review your supplier mapping periodically, and standardize supplier names across both systems where possible, since consistent naming is the single biggest factor in preventing duplicate records from accumulating.
Why Does a Document Sometimes Fail to Post Automatically?
A document occasionally fails to post because a required field, such as a VAT code or cost center, does not have a corresponding match in your accounting software. When this happens, Whitevision holds the document in a queue rather than posting it with missing information. Check this queue regularly, since documents waiting there do not appear in your accounting system until someone resolves the missing mapping.
Why Should You Review Your Integration After a Chart of Accounts Change?
If your company restructures its chart of accounts, adds new cost centers, or renames general ledger accounts, the existing field mapping in Whitevision may no longer align correctly. Revisit your mapping settings whenever you make a significant change to your accounting structure, rather than assuming the connection will adjust automatically. This habit prevents documents from posting to outdated or discontinued accounts.
How Can Solution for Guru Help You Connect Whitevision to Your Accounting Software?
Connecting Whitevision to your accounting software involves more than authorizing an app — it requires accurate field mapping, a sync strategy that matches your invoice volume, and ongoing maintenance as your chart of accounts evolves. Solution for Guru specializes in CRM and financial software implementation, and its team has guided finance departments through connecting Whitevision B.V. Declaraties to a wide range of accounting platforms. Rather than troubleshooting misposted entries after go-live, you can work with Solution for Guru to design the connection correctly from the start, which shortens your setup time and keeps your financial data consistent across both systems.
Conclusion
Connecting Whitevision B.V. Declaraties to your accounting software closes the final gap between document recognition and your general ledger, so approved invoices and credit notes post automatically instead of requiring a second round of manual entry. When you prepare your chart of accounts, choose the right integration method, map fields carefully, and test the connection with a real document batch, you build a link that stays reliable as your business grows. Monitor the connection after go-live, watch for duplicate suppliers or missing mappings, and revisit your settings whenever your accounting structure changes. With this integration in place, Whitevision and your accounting software work as one continuous system, freeing your finance team from repetitive data entry.
Frequently Asked Questions
Whitevision offers native connectors for widely used platforms such as Exact Online, Twinfield, and AFAS, along with API-based connections and Peppol e-invoicing support for other systems. If your accounting software is not listed among the native connectors, Whitevision‘s team can typically confirm whether an API-based connection is available for your platform.
Most companies complete authentication, field mapping, and initial testing within one to two business days when using a native connector. An API-based connection or a platform with a complex chart of accounts can take longer, particularly if your team needs to clean up supplier records or general ledger codes before mapping begins.
If a document fails to post, Whitevision holds it in a review queue rather than posting incomplete information. A designated user then reviews the flagged document, corrects the missing field mapping — often a VAT code or cost center without a match — and the document posts automatically once the correction is in place.
