AI agentIntake-to-pay

AI receiving discrepancy agent

An AI receiving discrepancy agent compares delivery documents, receipt entries and PO lines, and lists each discrepancy by type: short, over, wrong item, damaged or undocumented.

  • People stay in control
  • Every action is logged
  • Start with a small sample
PO and receipt lines
Delivery notes and photos
Receiver notes
Related invoices
AI receiving discrepancy agentPrepared for review
  • ✓Discrepancy case with type and evidence
  • ✓Draft supplier claim
  • ✓Hold flag for related invoice lines
Handed toBuyer receives the case and draft claim
5inputs it reads
6steps in the walkthrough
2points where a person decides
3outputs it prepares
See it run

Watch it work

Agent Record Person
Live walkthrough
  1. 1Detect mismatchAgent
  2. 2Gather factsAgent
  3. 3Classify causeAgent
  4. 4Buyer decidesPerson
  5. 5Message supplierPerson
  6. 6Track resolutionRecord

Notices short, over, damaged or wrong goods.

Adds order, receipt, photos and delivery note.

Proposes a type such as shortage or damage.

Chooses return, credit, replacement or acceptance.

Draft claim goes out after buyer review.

Outcome and credit expectations are recorded.

The basics

What is an AI receiving discrepancy agent?

It gathers the evidence together, including the PO line, the delivery note, any photos or notes from the receiver and prior messages.

Read the full explanation

It drafts the claim or query for the buyer and tracks the outcome, such as credit, replacement or acceptance.

Where it breaks

Why this step is hard by hand

Discrepancies are noticed by receiving staff, handled by buyers and resolved by suppliers, with little shared record along the way.

Photos, notes and documents are spread across tools.

Suppliers may only accept reports within a limited window.

Credit, replacement or acceptance each have a different follow-up.

The same supplier or item repeats the problem.

Payment can run ahead of the resolution.

The path

How the agent does it

  1. 01Detect the difference

    Compares received quantities and items with PO lines and flags each variance.

  2. 02Classify it

    Labels the discrepancy as short, over, wrong item, damaged or undocumented.

  3. 03Assemble evidence

    Attaches the PO line, delivery note, receipt entry and receiver comments to a single case.

  4. 04Draft the claim

    Writes a clear message to the supplier stating the problem and the resolution requested, held for review.

  5. 05Track to closure

    Monitors the reply and records whether it ended in credit, replacement, return or acceptance.

Want to see this flow on your own items?

Bring a small sample and watch Flo work through it.

Book a demo
Under the hood

Inside the work

AspectBy handWith the agent
Raising itReceivers email the buyer with partial facts.A discrepancy record is created with order, receipt and evidence.
CategorisingCauses are named differently by each person.Each case carries a consistent type.
Claim wordingSupplier messages are written from scratch.A draft claim states what was ordered, received and expected.
Follow-upOpen discrepancies drift without owners.Each case has an owner and a status.
Invoice effectAP pays before the issue is settled.Related invoice lines are flagged for holding.
People and control

Who decides, and what to watch

What stays with people

  • ✓
    Receivers record the factsThey report what they saw and counted.
  • ✓
    Buyers choose the remedyCredit, replacement or acceptance is a commercial decision.
  • ✓
    Quality owners assess damageTheir findings drive returns and claims.
  • ✓
    AP sets payment holdsHolds follow policy and approval.

Mistakes to avoid

  • ×
    Reporting lateA claim made weeks after receipt is easily rejected.
  • ×
    No photos or countsWithout evidence, disputes become opinion.
  • ×
    Accepting the shortage and paying in fullThis loses money quietly.
  • ×
    Fixing the case but not the causeRepeat issues need a supplier conversation.

Not sure where receiving discrepancy fits in your process?

Talk it through with the team. We will map it to your steps and show where a person stays in control.

  • Works from a sample of your real items
  • Shows what Flo handles and what it hands over
  • No commitment to start
Rollout

Rolling it out

  1. 1Log shortages first

    Begin with simple quantity differences where evidence is clear.

  2. 2Add damage and wrong items

    Include cases that need photos and carrier notes.

  3. 3Draft claims

    Offer claim drafts for buyers to edit once cases are well formed.

  4. 4Connect to AP holds

    Tie cases to invoice holds so payment waits for resolution.

Signs you would benefit

Issues live in emailReceivers write to buyers without a record.
Payment outruns resolutionInvoices are paid before credits are agreed.
Causes are inconsistentReporting cannot show what goes wrong.
Claims are rewrittenEach one starts from a blank page.
The numbers

How to measure it

Set your own baseline first. We do not publish benchmarks without a source you can check.
Metric 1

Discrepancy rate

Discrepancy rate (%) =
receipts with at least one discrepancytotal receipts× 100

This shows how reliable inbound deliveries are. Break it down by type and supplier to find where to focus.

  • Track average days from discovery to resolution.
  • Review recurring discrepancies by supplier each quarter.
Questions

Frequently asked questions

Quick answers to what people ask most about receiving discrepancy.

Book a demo
What is a receiving discrepancy?

It is a mismatch between what was ordered and what was delivered or documented. Common types are shortages, overages, wrong items, damaged goods and delivery notes that do not match the PO.

What should happen when a discrepancy is found?

It should be recorded with evidence, the supplier should be told within the allowed window, and a decision made on credit, replacement or acceptance. Invoices for the affected lines should be held.

Does the agent contact the supplier?

It prepares the message with evidence. A buyer reviews and sends it.

Can it decide whether to accept over-delivery?

No. It flags the excess and shows the order terms. A person decides whether to accept, return or pay for it.

Try receiving discrepancy on your own data

Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.

  • People approve, sign and pay
  • Every action is logged
  • Start with a small sample