How Do You Process Purchase Orders with Whitevision?
Quick Summary
Whitevision B.V. Declaraties is a Dutch document-processing platform that extends beyond invoice handling to cover the earlier stages of procurement, including purchase orders, order confirmations, and the three-way matching that ties an order to its delivery and invoice. Consequently, processing purchase orders with Whitevision is less about scanning a single document and more about maintaining an accurate thread that runs from the initial request through to final payment. This article reveals how purchase order processing works within Whitevision, covering how orders are recorded and approved, how order confirmations and e-orders are recognized, how three-way matching connects orders to deliveries and invoices, and how discrepancies are flagged before payment is made.
What Role Do Purchase Orders Play in Whitevision’s Process?
Why Record Purchases as Purchase Orders in the First Place?
When employees purchase goods or services, it is often convenient to record these purchases as formal purchase orders rather than letting them arrive as an unexpected invoice later. Because a purchase order requires a responsible person to give approval before the order is placed, this approach agrees the terms of the purchase in advance, which helps avoid disputes or surprises once the invoice eventually arrives. Therefore, purchase orders act as an early checkpoint in the broader procure-to-pay process, rather than simply as paperwork.
How Does Whitevision Fit Into the Wider Procurement Process?
Whitevision is designed to serve as a central point where all procurement-related messages and documents arrive and are processed, from the initial request through to payment. Since this includes e-orders, PDF confirmations, delivery receipts, and invoices, organizations benefit from one consistent flow across the full purchasing journey, rather than treating purchase orders as a separate, disconnected step from invoice processing.
How Are Purchase Orders Created and Approved?
How Does the Request-to-Order Workflow Typically Work?
In organizations using Whitevision’s broader e-procurement capabilities, employees typically request products or services through an internal catalog or directly from a supplier. Each request then runs through a workflow that the organization configures itself, meaning approval steps and thresholds can be tailored to match existing purchasing policies rather than forcing a generic process onto every department.
What Happens Once a Purchase Order Is Approved?
Once a request has been approved, a purchase order is generated automatically, after which deliveries and invoices related to that order can be linked to it without additional manual effort. As a result, this creates a clear, structured record from the moment a request is made, giving finance and procurement teams greater insight and control over commitments that have not yet resulted in an invoice.
Why Does This Matter for Decentralized Purchasing?
Many organizations, particularly in sectors such as healthcare, government, and business services, struggle with decentralized purchasing, where orders are placed informally through email or spreadsheets, and approval responsibility is unclear. Since this often results in unnecessary costs, so-called maverick buying, and invoices that cannot be properly matched to any order, structuring purchase orders through Whitevision’s workflow helps bring order and accountability back into the process.
How Are Order Confirmations and E-Orders Recognized?
How Does Whitevision Handle Order Confirmations?
The way order confirmations are recognized depends on how they are delivered. If order confirmations arrive as PDF documents, Whitevision scans and recognizes them. It does this in order to match the confirmation against the corresponding invoice. In some cases, the process is fully digitally supported through structured XML transaction messages. When this happens, order confirmations and their corresponding invoices can be matched automatically, without requiring a manual comparison step.
What Are E-Orders and How Do They Differ from Paper-Based Orders?
E-orders refer to purchase orders exchanged digitally in a structured format rather than through email attachments or paper documents. Structured data can be read directly by software. Because of this, e-orders generally require less manual interpretation than PDF or paper-based orders. PDF and paper-based orders still rely more heavily on OCR to extract the relevant details. As a result, organizations that can encourage suppliers toward structured e-ordering formats often see faster and more accurate processing. This benefit extends throughout the entire order-to-invoice cycle.
How Does Three-Way Matching Work for Purchase Orders?
What Is Three-Way Matching?
Three-way matching refers to the process of checking incoming documents, such as an order confirmation or purchase invoice, against other records. Specifically, it checks whether the lines on that document correspond to both the original purchase order and the goods receipt. In practical terms, this means confirming that what was ordered, what was delivered, and what was invoiced all align with one another. This check happens before payment is made.
How Does Whitevision Perform This Comparison?
Whitevision‘s matching feature automatically compares invoices against purchase orders and delivery receipts, using order lines as the basis for comparison. When everything aligns, the system completes the booking automatically without requiring manual review. For example, this happens when ten units were ordered, delivered, and invoiced consistently. However, sometimes a discrepancy exists, such as a price difference or a quantity mismatch. When this happens, it is flagged clearly, often through a visual indicator such as color coding. This makes it possible to distinguish a complete match from a partial mismatch at a glance.
Why Does This Level of Automation Matter?
The comparison happens instantly as documents are processed. Because of this, discrepancies are identified before an invoice is paid, rather than being discovered afterward during a reconciliation review. As a result, finance and procurement teams gain the opportunity to intervene early. This might mean querying a supplier about a pricing difference, or confirming that a partial delivery genuinely accounts for a lower invoiced quantity.
How Do You Handle Discrepancies Between Orders, Deliveries, and Invoices?
What Are the Most Common Types of Discrepancies?
While three-way matching catches a wide range of issues, some discrepancies appear more frequently than others in practice:
| Discrepancy Type | Example |
|---|---|
| Price mismatch | Invoiced unit price differs from the agreed order price |
| Quantity mismatch | Fewer or more units invoiced than were delivered |
| Missing delivery receipt | Invoice arrives before goods receipt is recorded |
| Unmatched order | Invoice references an order number that cannot be found |
Since each of these situations requires a slightly different response, it is helpful for finance teams to establish clear guidance on how staff should handle each type before it becomes a recurring source of delay.
How Should Flagged Discrepancies Be Resolved?
When a discrepancy is flagged, the recommended approach generally involves:
- Reviewing the specific line item highlighted by the matching feature.
- Comparing it against the original purchase order and any available delivery documentation.
- Contacting the supplier or the internal requester if clarification is needed.
- Adjusting or approving the invoice only once the discrepancy has been resolved or explained.
Consequently, treating flagged discrepancies as a required checkpoint, rather than something to be bypassed under time pressure, helps prevent incorrect payments from slipping through.
How Does Purchase Order Processing Connect to the ERP System?
Why Does This Integration Matter for Procurement Teams?
Since a purchase order is only useful as a control mechanism if it remains visible throughout the entire purchasing cycle, integrating this data with the ERP system ensures that outstanding commitments, partial deliveries, and matched invoices are all reflected accurately in financial records. Because Whitevision maintains partnerships with several ERP providers, purchase order data, delivery information, and invoice matching results can generally be synchronized without requiring separate manual updates in each system.
What Should You Confirm Before Relying on Automated Matching?
Before fully relying on automated three-way matching, it is worth confirming a few details with your implementation team:
| Item to Confirm | Why It Matters |
|---|---|
| Order number consistency | Ensures invoices can be matched reliably to the correct order |
| Tolerance thresholds | Defines how much variance is acceptable before a flag is raised |
| Delivery receipt process | Confirms goods receipts are recorded promptly and accurately |
| ERP synchronization | Verifies commitment and order data update correctly across systems |
Because these settings directly affect how often discrepancies are flagged, testing the configuration against a sample of recent orders before full rollout is generally a sound step.
Conclusions
Processing purchase orders with Whitevision B.V. Declaraties extends automation upstream of the invoice itself, covering how requests are approved, how orders and confirmations are recognized, and how three-way matching connects orders, deliveries, and invoices before payment occurs. Although some discrepancies will always require manual review, particularly around pricing or partial deliveries, the majority of straightforward purchases can move from order to booking without repetitive manual checks. By maintaining clear purchase order records and monitoring flagged discrepancies promptly, organizations using Whitevision B.V. Declaraties can bring greater structure, accountability, and financial control to their procurement process.
Frequently Asked Questions
Not necessarily. While formal purchase orders provide the strongest level of control and matching accuracy, some organizations reserve this process for higher-value or recurring purchases, while smaller, ad hoc expenses may still be processed as standard invoices or expense claims without a preceding order.
Yes, in most configurations. Since matching compares invoices against order lines and delivery records, a partial delivery can be reflected as a partial match, allowing the corresponding portion of the invoice to be processed while the remaining balance is tracked against the outstanding order.
