These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Vendor Scorecard
- Features
- Invoice Matching
Invoice Matching
Match a supplier invoice reference to unused accepted scope and follow the reviewed amount into its downstream handoff.
OverviewInvoice References×
SCM with Vendor Scorecard · Invoice Matching
New
Invoice References
Purchase lines
| Parent | Line number | Item description | Accepted quantity | Accepted at | Unit price USD | |
|---|---|---|---|---|---|---|
| PR-22187 | 140 | Line 1 | 60 | 20 Oct | 340 | |
| PR-18190 | 140 | Line 2 | 80 | 16 Oct | 240 | |
| PR-88922 | 580 | Line 3 | 370 | 17 Oct | 310 | |
| PR-36573 | 940 | Line 4 | 210 | 20 Oct | 90 | |
| PR-99874 | 120 | Line 5 | 40 | 08 Oct | 380 |
6 of 6 records
Line 1Purchase lines · PL-28280
ParentPR-22187
Line number140
Accepted quantity60
Accepted at20 Oct
Unit price USD340
What you can do
Establish which accepted scope the invoice concerns
Finance Officer begins with the actual accepted purchase lines and the supplier invoice reference. The matching action checks unused accepted scope before handing off the reviewed eligible amount. An invoice referring to an order does not establish that all requested material has been accepted or remains available for another match.
The invoice reference stays on the purchase line alongside accepted quantity and date. This gives the team a way to follow the financial claim back to the receiving evidence. The parent request identifies the supplier and commercial authorization used to understand that claim.
The downstream result needs its own evidence. The app does not fabricate a payment or a local inventory receipt when matching succeeds. Finance Officer follows the recorded operation result and the authoritative receiving system where a connection is configured, retaining the distinction between a reviewed handoff and the external system’s execution.
How the work is organized
- Accepted basis. Finance Officer reads the line’s accepted quantity and date before matching. Requested quantity alone is insufficient to establish eligible invoiced scope.
- Unused scope check. The action prevents the same accepted scope from being consumed again. Repeated requests retain their operation identity and must not produce another eligible financial handoff.
- Reviewed handoff. Only the reviewed eligible amount proceeds to the configured downstream process. Its real reference and effect evidence support the result recorded in the operation receipt.
What to agree during setup
Agree how supplier invoice references are normalized and how Finance Officer identifies the exact accepted lines they concern. A similar invoice number from another supplier or request must not be enough to select the scope. Keep the reference and parent identity together during reconciliation.
Name the destination for the eligible amount and the person responsible for confirming its outcome. Agree the review evidence required before handoff and the procedure for an uncertain response. The external financial process retains responsibility for its own payment execution and any later compensation.
Check the handoff on an actual case
Use the purchase line where 80 components were accepted from a request for 100. Finance Officer matches an invoice reference only to the eligible accepted portion, then follows the reviewed handoff result. The unaccepted portion must not become eligible simply because it appeared on the original request.
Repeat the same matching command and attempt another match against scope already consumed. The action should preserve the original result and refuse duplicate use. Then try a reference associated with a different request and confirm that the parent check prevents an unrelated match.
Finally, rehearse an uncertain downstream response. Inspect the operation receipt and authoritative reference before requesting another effect. The team should be able to explain what has been reviewed and handed off without claiming that a payment occurred merely because the local action completed.
What your team sees
- Invoice References — Lines carrying an invoice reference with their accepted scope and parent request.
- Accepted Scope — Recorded accepted quantities and invoice references, including already matched lines; the matching action checks which scope remains unused.
- Receipt Exceptions — Pending, failed or disputed operation results needing investigation.
Follow the work through
What it keeps track of
Data model- Purchase lines
- Line items under a purchase request with requested and accepted quantities.
- Purchase requests
- Demand records carrying requested amount, lifecycle status and supplier counterparty.
- Operation receipts
- Idempotent receipts for guarded operations and their downstream effects.
- Review decisions
- Independent approver decisions recorded against a purchase request revision.
- Record attachments
- Evidence files attached to a purchase request with visibility scope.
- Suppliers
- Approved supplier parties eligible for purchase commitments.
Who uses it
Permissions- Finance Officer
- Requests eligible matches and follows their results.
- Receiving Officer
- Supplies actual acceptance evidence.
- Procurement Reviewer
- Provides the relevant authorization, and Auditor reads the retained trail.
Set up SCM with Vendor Scorecard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.