How to Process Credit Notes with Whitevision
Quick Summary
A supplier credit note that sits unmatched in your inbox creates confusion at month-end, since it distorts your accounts payable balance until someone reconciles it manually. Whitevision B.V. Declaraties solves this by recognizing credit notes automatically, linking them to the original invoice, and routing them through the same approval workflow your team already uses for purchase invoices. This guide explains how to process credit notes with Whitevision, from initial recognition through final posting in your ERP system. By the end, you will know how to configure credit note handling so that returns, price corrections, and refunds no longer require manual tracking in a spreadsheet.
| Quick Facts | Details |
| Platform | Whitevision B.V. Declaraties |
| Core function | SMART-OCR credit note recognition and invoice matching |
| Typical processing time per note | Under one minute once configured |
| Works with | Most major ERP and accounting systems |
| Best for | Finance teams handling recurring supplier returns and corrections |
Why Does Credit Note Processing Deserve Its Own Workflow?
A credit note is not simply a negative invoice. It reduces a specific supplier balance, often references an original purchase order or invoice number, and sometimes needs a different approval path than a standard purchase invoice. Consequently, treating credit notes as an afterthought in your invoice workflow creates reconciliation problems later, since an unlinked credit note leaves your accounts payable ledger overstated until someone tracks down the connection manually.
Whitevision addresses this by giving credit notes their own document type, recognition template, and matching logic. Therefore, once you configure credit note processing correctly, the platform links each incoming credit note to its original invoice automatically, which keeps your supplier balances accurate without extra manual work. This distinction matters most for companies that receive frequent returns, damaged-goods adjustments, or pricing corrections from the same suppliers.
How Do You Prepare Whitevision to Process Credit Notes?
Before credit notes start flowing through your workflow, a short setup phase ensures the platform recognizes them correctly and routes them to the right people.
What Access and Information Do You Need First?
Gather the following before you configure credit note processing:
- An administrator account with rights to edit document types and recognition rules
- A handful of real credit notes from your regular suppliers, so Whitevision can calibrate its recognition engine against your actual documents
- The original invoice numbers or purchase order references those sample credit notes relate to
- A list of the general ledger accounts your team uses to post credit adjustments
- Confirmation of who should approve credit notes, since this role sometimes differs from invoice approvers
How Do You Enable the Credit Note Document Type?
Once you confirm access, open the document type settings and enable the credit note category alongside your existing purchase invoice type. Whitevision treats credit notes as a distinct classification, so the recognition engine applies a separate template tuned to the fields credit notes typically contain, such as a credit note number, a reference to the original invoice, and a negative or refund amount. Activating this document type separately, rather than folding credit notes into your invoice type, keeps recognition accuracy higher for both document categories.
How Do You Configure Recognition Fields for Credit Notes?
Accurate recognition depends on telling Whitevision exactly which fields to extract from an incoming credit note. This step mirrors invoice configuration but focuses on the fields unique to credit adjustments.
Which Fields Should You Extract From a Credit Note?
Most companies configure the following fields as standard for credit note recognition:
- Credit note number
- Supplier name
- Original invoice number or purchase order reference
- Credit note date
- Credit amount and VAT adjustment
- Reason code, when your supplier includes one
How Does Whitevision Match a Credit Note to Its Original Invoice?
After extraction, Whitevision searches your invoice history for a document that matches the reference number, supplier, and amount pattern on the credit note. When it finds a match, it links the two records automatically, so your team can see the full transaction history — original invoice and corresponding credit — in one place. If no match exists, because the supplier omitted a reference number or the original invoice predates your Whitevision setup, the platform flags the credit note for manual linking instead of guessing. Consequently, you avoid the risk of Whitevision connecting a credit note to the wrong invoice, which would understate a different transaction’s balance.
How Do You Set Up Approval Workflows for Credit Notes?
Credit notes often need a different approval path than invoices, since they reduce a balance rather than create a new payment obligation. Configuring this separately keeps your controls appropriate for each document type.
Should Credit Notes Follow the Same Approval Chain as Invoices?
Many companies route low-value credit notes through a single approver, since the financial risk of a credit adjustment is generally lower than the risk of an incorrect payment. However, larger credit notes — particularly those tied to disputed goods or pricing disagreements — often warrant a second reviewer who can confirm the adjustment against the original purchase agreement. Set your thresholds within Whitevision’s workflow settings so that the system escalates only the credit notes that genuinely need extra scrutiny.
How Do You Assign Credit Note Approvers by Supplier or Cost Center?
Just as with invoices, you can link specific approvers to specific cost centers or supplier accounts. This matters particularly for credit notes, since the person who understands why a supplier issued a credit — a returned shipment, a damaged batch, a negotiated discount — is often different from the person who approves routine invoice payments. Assigning the right approver at this stage means the credit note reaches someone who can validate it accurately on the first pass, rather than bouncing between departments.
How Do You Handle Special Credit Note Scenarios?
Not every credit note follows the straightforward pattern of one credit tied to one invoice. A few scenarios come up often enough that it helps to plan for them during configuration.
How Does Whitevision Handle a Credit Note That Covers Multiple Invoices?
Some suppliers consolidate several small corrections into a single credit note that references multiple original invoices, particularly at month-end or quarter-end. Whitevision can split this type of credit note across the referenced invoices, provided the document lists each invoice number and its corresponding amount clearly. If the supplier’s formatting makes the individual amounts ambiguous, the platform flags the credit note for manual allocation rather than guessing how much applies to each invoice, which keeps your supplier balances accurate.
What Happens When a Credit Note Has No VAT Component?
Certain credit notes — for example, a goodwill discount or a rounding correction — do not include a VAT adjustment, while others recalculate VAT alongside the credit amount. Configure your recognition fields to treat VAT as optional rather than mandatory for the credit note document type, since marking it mandatory would stop every VAT-free credit note at the review stage unnecessarily. Whitevision still extracts and posts the VAT field whenever a credit note includes one.
How Should You Handle a Credit Note Issued in a Different Currency?
Companies working with international suppliers sometimes receive credit notes in a currency different from the original invoice, particularly after an exchange rate adjustment. Whitevision applies the exchange rate configuration already set up for that supplier, so the platform converts the credit amount consistently with how it converts invoices from the same source. Confirm this setting during your initial test batch if you work with suppliers who invoice in a foreign currency, since an incorrect rate at this stage compounds across every future credit note from that supplier.
How Do You Post Credit Notes to Your ERP System?
Once a credit note clears approval, Whitevision posts it to your ERP or accounting system using the same integration you already configured for invoices.
| Posting Scenario | What Happens | Result |
| Credit note matched to an invoice | Whitevision links the credit to the original transaction | Supplier balance adjusts automatically |
| Credit note unmatched | Flagged for manual review before posting | Prevents incorrect balance adjustments |
| Partial credit against an invoice | Posted against the specific line items affected | Original invoice balance updates proportionally |
| Credit note with VAT adjustment | VAT recalculated and posted alongside the credit amount | Tax records stay accurate |
To confirm your integration handles credit notes correctly, review the field mapping in your integration settings and verify that credit amounts post as negative entries or dedicated credit transactions, depending on how your ERP structures accounts payable. An incorrect mapping here can cause a credit note to post as a new invoice instead of reducing an existing balance, which inflates your payables rather than correcting them.
What Common Mistakes Should You Avoid When Processing Credit Notes?
A few recurring issues trip up companies as they scale their credit note volume through Whitevision. Addressing these early prevents reconciliation headaches later.
Why Does an Unmatched Credit Note Cause Reporting Errors?
When Whitevision cannot match a credit note to its original invoice, and no one follows up on the flagged item, the credit sits unposted while your accounts payable report continues to show the original, uncorrected balance. Consequently, assign someone to review unmatched credit notes on a regular schedule, rather than letting them accumulate in a queue that nobody checks.
Why Should You Avoid Manually Re-Entering Credit Note Data?
Some teams, uncertain whether Whitevision recognized a credit note correctly, re-enter the data manually into their ERP as a safeguard. This habit creates duplicate entries and defeats the purpose of automation. Instead, trust the platform’s recognition results after your initial test batch confirms accuracy, and use the manual-review flag for genuinely uncertain cases rather than as a default double-check.
Why Does Inconsistent Supplier Reference Numbering Cause Matching Failures?
Whitevision relies heavily on the reference number a supplier includes on a credit note to find the matching invoice. If your suppliers use inconsistent formats — sometimes including the full invoice number, sometimes only a partial reference — matching accuracy drops. Where possible, ask key suppliers to include the complete original invoice number on every credit note they issue, which improves automatic matching rates significantly.
How Can Solution for Guru Help You Configure Credit Note Processing?
Setting up credit note processing correctly requires more than enabling a document type — it involves designing matching rules, approval paths, and ERP posting logic that reflect how your specific suppliers issue credits. Solution for Guru specializes in CRM and financial software implementation, and its team has helped finance departments configure Whitevision B.V. Declaraties for exactly this kind of nuanced workflow. Rather than discovering matching gaps after credit notes start piling up unposted, you can work with Solution for Guru to build accurate recognition rules and approval routing from the outset, which reduces reconciliation work and keeps your supplier balances trustworthy.
Conclusion
Processing credit notes with Whitevision B.V. Declaraties turns a task that traditionally required manual spreadsheet tracking into an automated workflow that mirrors your invoice process. When you enable the credit note document type, configure recognition fields correctly, set up matching logic against original invoices, and assign the right approvers, your team gains confidence that every credit note gets accounted for accurately. Review unmatched credit notes regularly, avoid duplicate manual entry, and encourage consistent reference numbering from your suppliers to keep matching rates high. With this configuration in place, Whitevision handles the routine reconciliation work so your finance team can focus on resolving the exceptions that genuinely need human judgment.
Frequently Asked Questions
Yes, Whitevision searches your invoice history for a matching reference number, supplier, and amount pattern, and links the two documents automatically when it finds a confident match. If no match exists, the platform flags the credit note for manual review rather than guessing at a connection, which protects your supplier balances from incorrect adjustments.
Yes, Whitevision lets you configure separate approval workflows for credit notes, including different thresholds, approvers, and escalation rules than the ones you use for standard purchase invoices. Many companies route low-value credit notes through a single approver while reserving multi-level review for larger or disputed adjustments.
If a credit note arrives without a clear reference to the original invoice, Whitevision flags it for manual linking instead of attempting an automatic match. A designated user then reviews the credit note, identifies the correct original transaction, and links the two manually, after which the platform posts the adjustment to your ERP as usual.
