PO, receipt, and invoice checked before payment
Invoice matching software for accounts payable and procurement teams
Invoice matching software compares a supplier invoice with the purchase order and the goods receipt it relates to, so the business pays only for what it ordered and received. Krayuv lets your team run a 3-way match on each invoice, line by line, see the variance, and work mismatches through an exception queue before the invoice goes to payment.
Illustrative — mismatches route to an exceptions dashboard
What you get
Line-by-line 3-way match
Compare purchase order, goods receipt and invoice for each line, with a match summary and overall variance.
Exception queue
Mismatches get a severity and are resolved with notes, tracked on a dashboard.
GST and duplicate checks
Check duplicates, validate the invoice and validate GST before matching.
Approval to payment
Approved invoices can be scheduled for payment, in full or in part.
What invoice matching software does
Invoice matching software checks that an invoice agrees with the purchase order and the goods or services actually received, and flags any difference for a person to resolve.
Without a system, accounts payable staff check invoices against paper or scanned copies of the purchase order and the receiving note, or against separate spreadsheets. It is slow, it varies by person, and differences are easy to miss when a purchase order has many lines or a delivery arrives in parts.
A matching tool brings the three documents together on one screen, compares them line by line, and puts differences in a queue with a severity and a place for notes. Matching sits in the middle of the procure-to-pay flow, after receipt and before approval for payment. For a plain-language explanation of the concept itself, read 3-way matching explained.
How 3-way matching works in Krayuv
In Krayuv, a user runs the 3-way match on an invoice and sees the purchase order, goods receipt and invoice compared line by line, with a match summary and an overall variance.
Step 1: Raise and approve the PO
The purchase order records what was ordered, at what quantity, and from whom.
Step 2: Record the goods receipt
A GRN captures received quantity against the PO, with received-so-far and remaining shown. It is submitted for verification and verified or rejected with a return reason.
Step 3: Capture the invoice
Enter the invoice or let the supplier submit it from the portal, including line items with HSN or SAC and GST amounts.
Step 4: Run the match
The user runs the 3-way match for that invoice and reviews the line-by-line comparison and summary.
Step 5: Resolve exceptions
Any mismatch lands in the exception queue with a severity. The reviewer resolves it with notes.
Step 6: Approve for payment
Matched or resolved invoices continue through approval, then payment scheduling.
Matching is something your team runs per invoice. It is not applied silently in the background, which keeps the person doing the check in control and visible in the record.
What gets matched and what shows up as a mismatch
Krayuv compares the three documents at line level, so a difference on one item is not hidden by an overall total that looks right. The match summary shows the result for the invoice, together with the overall variance.
| Mismatch type | What it means | Typical response |
|---|---|---|
| Quantity billed above received | Supplier invoiced more than was delivered | Hold, ask the supplier for a credit note or confirm the receipt |
| Price different from PO | Unit price on the invoice differs from the order | Check agreed price, dispute or amend the PO with history |
| Item not on the PO | A line was invoiced that was never ordered | Reject the line or raise a change with the buyer |
| No receipt recorded | Invoice arrived before goods receipt | Wait for the GRN or chase the receiving site |
| Duplicate invoice | The same invoice number appears again | Reject the duplicate and keep the original |
| Tax details differ | GSTIN or GST amounts do not validate | Request a corrected invoice |
The type of mismatch usually tells you who has to act: the receiving site, the buyer, or the supplier. The exception queue keeps that work visible instead of spread across email.
Invoice exception management
Invoice exception management is the process of sorting, assigning, resolving and recording every invoice that does not match, so nothing is paid or lost by default.
In Krayuv, exceptions go to a queue with a severity level. A reviewer opens an exception, investigates, and resolves it with a note. A dashboard shows matches and open exceptions, so a finance lead can see where the backlog is without asking around.
Beyond matching, an invoice can be approved, rejected, sent back with a request for changes, or marked as disputed. Suppliers can respond in the portal and submit corrected invoices, which keeps the conversation attached to the document.
- Severity on every exception, so serious mismatches are reviewed first
- Resolution notes stored with the exception
- Dispute and request-changes statuses on the invoice itself
- A dashboard of matched invoices and open exceptions
- Supplier follow-ups linked to the invoice, with priority, due date and escalation
Invoice capture, duplicate checks, and GST validation
Matching works best on clean invoice data, so Krayuv supports the steps before it. Invoice types include standard invoices, credit notes, debit notes and freight bills. Line items carry HSN or SAC codes and GST amounts. Users can check for duplicates, validate the invoice, and validate GST.
When a user uploads an invoice image, OCR pre-fills the invoice number, invoice date, due date and GSTIN for review. It fills these header fields only, so line items and totals are still entered or checked by the user, and every pre-filled value should be reviewed before saving. A GST compliance view shows validated, pending and invalid GSTINs across your invoices.
Approval before payment
A matched invoice is not yet a paid invoice. Invoices follow configurable approval workflows, with multi-step approval, routing rules and an inbox for approvers, as described on the procurement approval workflow page. The approval history, with who acted at which step and any notes, stays on the invoice.
After approval, eligible invoices can be scheduled for payment in full or in part, and payments follow their own approval workflow before they are completed, with a payment reference recorded against each one.
Who uses invoice matching software
- Accounts payable teams who verify invoices before payment
- Procurement and buyers who own the purchase order and answer price queries
- Receiving and site teams who record goods receipts
- Finance managers watching open exceptions and payment readiness
- Suppliers who submit invoices and respond to queries in the portal
Invoice matching rate also appears in procurement analytics, so management can see how smoothly invoices flow through the process over time. Supplier records, follow-ups and portal access come from vendor management, and the full chain is described under Source-to-Pay.
How to evaluate invoice matching software
A short checklist helps you separate real matching from a document inbox with a status field.
- Does it compare PO, receipt and invoice at line level, not only at total level?
- Does it handle partial deliveries and received-so-far quantities?
- Is there an exception queue with severity, ownership and notes?
- Can suppliers submit invoices and respond to queries themselves?
- Are duplicate and tax checks available before matching?
- Does approval and payment scheduling sit in the same system?
- Is it clear whether matching runs automatically or is triggered by a person?
Invoice matching software vs manual matching
| Invoice matching software | Manual matching | |
|---|---|---|
| Documents | PO, receipt and invoice compared in one view | Checked across paper, PDFs and spreadsheets |
| Level of check | Line by line, with an overall variance | Often total only, depending on time |
| Mismatches | Exception queue with severity and notes | Email threads and memory |
| Duplicates and GST | Built-in checks before matching | Spot checks by the clerk |
| Evidence | Match result and resolution stored with the invoice | Hard to reconstruct later |
| Visibility | Dashboard of matches and open exceptions | Manual status reports |
Frequently asked questions
What is invoice matching software?
Invoice matching software compares a supplier invoice with the purchase order and goods receipt, flags differences, and manages them until they are resolved, so the business pays only for what it ordered and received.
What is 3-way matching?
3-way matching checks an invoice against the purchase order and the goods receipt note. For the concept and examples, see [3-way matching explained](/resources/guides/3-way-matching-explained).
Does Krayuv match invoices automatically?
No. A user runs the 3-way match on each invoice. The system then shows the line-by-line comparison, a match summary and the overall variance, and sends mismatches to the exception queue.
What happens when an invoice does not match?
The mismatch goes to the exception queue with a severity. A reviewer investigates and resolves it with notes, or the invoice is rejected, sent back for changes, or disputed with the supplier.
Does it handle partial deliveries?
Goods receipts show received quantity, received-so-far and remaining against the purchase order, so partial deliveries are recorded and the match uses the receipt data.
Does it read invoices with OCR?
When you upload an invoice image, OCR pre-fills the invoice number, invoice date, due date and GSTIN for you to review. It does not extract line items or totals.
Does it support GST invoices?
Yes. Invoices carry HSN or SAC codes and GST amounts, and users can validate GST and view GSTINs as validated, pending or invalid.
Can suppliers submit invoices themselves?
Yes. Suppliers submit invoices from the portal and can answer follow-ups linked to an invoice.
Does it connect to my ERP or bank?
Yes. ERP connectors for systems such as SAP, Oracle, Microsoft Dynamics and Tally are delivered during implementation, alongside Excel and CSV imports and Excel and PDF exports. We configure the connection to your finance setup at onboarding.
Related resources
- 3-way matching explainedHow 3-way matching works: the three documents compared, what counts as a match, how tolerances and exceptions are handled, and why it matters for paying invoices correctly.
- GST E-Invoicing for Procurement Teams: A GuideWhat GST e-invoicing means for buyers: IRN and QR checks, matching supplier invoices to POs and receipts, handling mismatches, and keeping payables clean.
- Procurement Approval Workflow Software and RulesProcurement approval workflow software for requisitions, POs, contracts, invoices and payments: multi-step routing rules, delegation and approval history.
See an invoice matched from PO to payment
Bring a recent invoice with a mismatch. We'll show the comparison, the exception queue and the approval step.
