How to Configure Invoice Processing in Whitevision
Quick Summary
Manual invoice entry drains hours that your finance team could spend on analysis instead of data entry. Whitevision B.V. Declaraties removes that burden by scanning, recognizing, and routing every incoming invoice through a configurable digital workflow. This guide walks you through the exact steps for configuring invoice processing in Whitevision, from preparing your account to connecting the platform with your ERP system. By the end, you will know how to set up document types, approval routes, and integration settings so that invoices move from inbox to payment without manual intervention.
| Quick Facts | Details |
| Platform | Whitevision B.V. Declaraties |
| Core function | SMART-OCR invoice recognition and workflow automation |
| Typical setup time | 1–3 business days |
| Works with | Most major ERP and accounting systems |
| Best for | Finance teams processing recurring purchase invoices |
Why Does Invoice Processing Configuration Matter?
Before you touch a single setting, it helps to understand why configuration determines the outcome. An invoice processing tool only performs as well as the rules you give it. When you configure Whitevision correctly from the start, the software recognizes supplier data accurately, routes invoices to the right approver, and posts entries to your ERP without duplication errors. Skip this step, or rush through it, and your team ends up correcting mismatched fields by hand anyway — which defeats the purpose of automation in the first place.
Consequently, treating configuration as a one-time project rather than a checkbox task pays off over the following months. A properly configured account adapts as your supplier list grows, as your approval hierarchy changes, and as your invoice volume increases. Therefore, this guide follows the order that Whitevision recommends: account preparation, document type setup, approval workflow design, ERP integration, and testing.
How Do You Prepare Your Whitevision Account Before Configuration?
Preparation determines whether the rest of the setup goes smoothly. Before you open the configuration menu, gather the information Whitevision needs and confirm that your account has the right access level.
What Documents and Access Do You Need First?
Gather the following before you begin:
- An administrator account with full configuration rights — standard user roles cannot edit document types or workflow rules
- A handful of sample invoices from your regular suppliers, which Whitevision uses to calibrate its SMART-OCR recognition engine
- Your company’s cost center list and general ledger codes
- The names and email addresses of everyone who needs to approve invoices
- Confirmation of which ERP or accounting package your company uses, since integration options differ by system
How Do You Set Up Company and User Roles?
Once you confirm access, move to the user management section of the platform. Here, you create a role for every person involved in invoice processing: administrators who manage settings, approvers who authorize payments, and viewers who only need read access. Assign each user to the correct cost center or department so that Whitevision routes invoices to the right people automatically. Also, set up email notifications for each role so that approvers receive an alert the moment an invoice reaches their queue rather than checking the dashboard manually.
How Do You Configure Document Types for Invoice Processing?
Document types tell Whitevision how to interpret each incoming file. Consequently, this step forms the foundation of accurate invoice recognition.
What Document Types Should You Enable First?
Whitevision organizes incoming files into categories such as purchase invoices, credit notes, service orders, and packing slips. For invoice processing specifically, enable the purchase invoice document type first, then add credit notes if your suppliers issue them regularly. Each document type carries its own recognition template, so activating only the types you actually receive keeps the recognition engine focused and reduces misclassification.
How Do You Customize Recognition Fields?
After you enable a document type, define which fields the SMART-OCR engine should extract. Most companies start with these standard fields:
- Invoice number
- Supplier name
- Invoice date and due date
- VAT amount
- Total amount
Whitevision then compares each incoming invoice against your supplier master data and cost center list, so accuracy improves as the system processes more invoices from the same senders. Moreover, you can mark specific fields as mandatory, which stops an invoice from advancing through the workflow until someone confirms the missing information. This step matters because a mandatory field check catches errors before an invoice reaches an approver, rather than after.
How Do You Set Up Approval Workflows for Invoices?
Once document recognition works reliably, the next step configures how invoices move through your approval chain. A workflow determines who reviews an invoice, in what order, and under which conditions.
How Do You Define Approval Levels and Thresholds?
Whitevision lets you build multi-level approval chains based on invoice amount, supplier, or cost center. For example, you might set a rule so that invoices under 500 euros only need one approver, while anything above that threshold requires sign-off from a department head and a finance manager. Consequently, higher-value invoices receive more scrutiny automatically, without your team tracking thresholds manually.
How Do You Assign Approvers to Cost Centers?
Next, link each cost center to a specific approver or approval group. When an invoice arrives tagged with a particular cost center, Whitevision routes it directly to the assigned approver’s queue. If that person is unavailable, you can configure a backup approver so that invoices never sit idle waiting for one person to return from leave. Additionally, set escalation rules that automatically forward an invoice to a manager if it remains unapproved after a defined number of days.
How Do You Connect Whitevision to Your ERP or Accounting System?
Invoice processing only delivers full value once approved invoices post automatically to your financial records. Whitevision connects to most major ERP and accounting systems through pre-built integrations.
| Integration Method | Best For | Setup Complexity |
| Native ERP connector | Companies using a supported ERP (Exact, AFAS, Twinfield, and similar platforms) | Low |
| API integration | Custom or less common ERP systems | Medium |
| Export/import via file | Legacy systems without direct connectors | Medium to High |
| E-invoicing via Peppol | Companies exchanging structured e-invoices | Low |
To configure the connection, navigate to the integration settings, select your ERP system from the supported list, and authenticate the connection using your ERP credentials. Whitevision then maps its internal fields — supplier, cost center, VAT code, and general ledger account — to the corresponding fields in your ERP. Review this mapping carefully, since an incorrect field mapping causes invoices to post to the wrong account even when recognition and approval worked correctly.
How Do You Test and Validate Your Configuration?
Before you roll out invoice processing to your entire team, run a test batch through the system. Upload five to ten real invoices that represent your typical supplier mix, and confirm that Whitevision recognizes each field correctly, routes the invoice to the right approver, and posts it to the correct ERP account after approval. If any step fails, revisit the relevant configuration section rather than working around the error manually. Once your test batch processes cleanly from upload through posting, you can extend the configuration to your full invoice volume with confidence.
What Common Configuration Mistakes Should You Avoid?
Even a well-planned rollout can run into friction if a few common mistakes slip through. Knowing these pitfalls in advance saves you a second round of adjustments after go-live.
Why Do Incomplete Supplier Records Cause Recognition Errors?
Whitevision matches incoming invoices against your supplier master data, so an incomplete or outdated supplier list leads to mismatched fields even when the OCR engine reads the invoice correctly. Before you go live, export your current supplier list and confirm that names, addresses, and VAT numbers match what appears on real invoices. Outdated entries — a supplier that changed its legal name, for instance — cause the system to flag invoices for manual review that should have passed through automatically.
Why Should You Avoid Overcomplicating Approval Chains?
Some companies add too many approval levels in an attempt to cover every possible scenario. While thorough oversight sounds appealing, an approval chain with five or six steps for routine invoices slows down payment cycles and frustrates approvers who receive requests for amounts well within their authority. Instead, reserve multi-level approval for invoices above a meaningful threshold, and let lower-value, routine invoices move through a single approval step.
Why Does Skipping the Test Phase Create Problems Later?
Teams under deadline pressure sometimes skip the test batch and roll out configuration directly to full volume. This shortcut often surfaces mapping errors, missing mandatory fields, or approval routing issues only after dozens of invoices have already entered the system, which then requires manual correction on every single one. A short test phase, by contrast, catches these issues while the fix only affects a handful of invoices rather than an entire month’s volume.
How Can Solution for Guru Help You Configure Whitevision Invoice Processing?
Configuring invoice processing involves more than clicking through menus — it requires mapping your specific approval hierarchy, cost centers, and ERP fields correctly the first time. Solution for Guru specializes in CRM and financial software implementation, and its team has guided finance departments through Whitevision B.V. Declaraties setup across a range of industries. Rather than troubleshooting mismatched fields after go-live, you can work with Solution for Guru to design your document types, approval chains, and ERP integration correctly from the start, which shortens your time to full automation and reduces the risk of costly configuration errors.
Conclusion
Configuring invoice processing in Whitevision B.V. Declaraties transforms a repetitive manual task into a streamlined digital workflow. When you prepare your account correctly, set up document types with accurate recognition fields, build approval workflows that match your company’s hierarchy, and connect the platform to your ERP system, your team gains back the hours it once spent on data entry. Test your configuration with a real invoice batch before full rollout, and revisit your settings periodically as your supplier list and approval structure evolve. With the right configuration in place, Whitevision handles the routine work so your finance team can focus on decisions that actually require human judgment.
Frequently Asked Questions
Most companies complete the core configuration — document types, approval workflows, and ERP integration — within one to three business days. However, the timeline depends on how many suppliers, cost centers, and approval levels your company needs to set up. Companies with a straightforward approval hierarchy typically finish faster than those with multiple departments and thresholds.
Yes, Whitevision allows administrators to edit approval workflows at any time. You can add new approvers, adjust amount thresholds, or reassign cost centers as your organization grows. Changes take effect immediately for new invoices, though invoices already in an active workflow continue through the process under the rules that applied when they entered the queue.
If the SMART-OCR engine misreads a field, the invoice pauses at the review stage instead of advancing automatically. A designated user then corrects the field manually, and Whitevision uses that correction to improve recognition accuracy for future invoices from the same supplier. This built-in feedback loop means recognition accuracy typically improves the longer you use the platform.
