Chapter 1
Record the partial receipt
Ethan Brooks records the delivered quantity against the ERP-backed order reference. The shipment is partial, so the view shows ordered, received, and remaining quantities separately. Ethan attaches fictional packing evidence and records the receiving location. The receipt is operational evidence for matching; it does not itself establish invoice accuracy or payment readiness.
- Evidence visible
- ERP-backed order reference · Ordered quantity · Received quantity · Remaining quantity · Packing evidence · Receiver and timestamp
- Human action
- Ethan reviews and submits the partial receipt.
- Policy or system boundary
- Receipt evidence supports matching but does not approve an invoice or payment.
- Accessible alternative
- Chapter 1 shows Ethan recording a partial receipt with order, received, and remaining quantities, receiving location, date, and packing evidence.
Read the complete walkthrough
Record the partial receipt
Ethan Brooks records the delivered quantity against the ERP-backed order reference. The shipment is partial, so the view shows ordered, received, and remaining quantities separately. Ethan attaches fictional packing evidence and records the receiving location. The receipt is operational evidence for matching; it does not itself establish invoice accuracy or payment readiness.
Capture the invoice
The fictional supplier submits an invoice for the full order quantity. The captured fields remain linked to the source document so Michael Grant can compare supplier, order, line, quantity, price, tax, and total. Any extracted value requiring review is labeled for human verification. Capturing the document does not mean the invoice is correct, approved, or ready for payment.
Identify the match exception
The matching view compares the order, partial receipt, and invoice. Unit price agrees, but invoiced quantity exceeds the received quantity. The configured tolerance does not allow the variance, so the invoice enters an exception path. The screen explains the mismatch and identifies Michael as the exception owner. It does not infer fraud or supplier fault from the variance.
Request supplier correction
Michael confirms the partial receipt with Ethan and requests a corrected invoice for the received quantity. The original invoice remains in the record. The supplier can submit a replacement invoice or an approved credit or debit document according to the configured process. This illustration uses a replacement invoice. The exception remains open until the new document is captured and reviewed.
Rematch and approve
The replacement invoice is linked as a new version and matched against the same order and partial receipt. Quantity and price now agree within the configured rules. A duplicate-invoice check is available as an additional signal, with the source documents and rationale available for review. Michael verifies the result and completes the configured invoice approval. The platform does not make the accountable payment decision.
Reconcile the status
The final view links the partial receipt, original invoice, exception, correction request, replacement invoice, match result, and Michael's approval. The approved status can be handed to the configured ERP process, where agreed financial records and postings remain authoritative. VendrNova can show payment and reconciliation status received through the customer-specific framework. This walkthrough does not claim that VendrNova executes the bank payment.