Request.
A supplier payment request sets out the recipient, amount, purpose and supporting invoice. These are the details the reviewer is asked to approve.
Payment-control software designed to connect what was requested, what was approved and what the payment record shows.
02 / CLVR SYSTEMSAn invoice, an approval and a payment reference can each tell part of the story. Verified is designed to bring them together, so a reviewer can compare the payment with the original decision.
The recipient, amount, purpose and supporting invoice.
Who reviewed the request and the details they authorised.
The check against the approval, with any differences recorded.
An illustrated payment review showing how Verified is designed to keep a supplier request, its approval and the verification result together.
Illustrative product workflow. No payment is processed in this example.
A supplier payment request sets out the recipient, amount, purpose and supporting invoice. These are the details the reviewer is asked to approve.
The intended approval record identifies the reviewer and the agreed payment details. Its reference follows the request into the payment record.
Verification is designed to compare the recorded recipient, amount and reference with the approval. A difference needs investigation before the review is complete.
In this example, the details match. The request, approval, payment reference and check result form one history for a later reviewer to inspect.
Explore the proposed payment workflow and contact the product team about your requirements and current availability.
Visit CLVR VerifiedHave a question about one of our products? Tell us which one you’re interested in and what you need.
Email CLVR hello@clvrsystems.com