Know what your supplier
still owes you.
See what arrived. Track what’s still owed. Never guess.
Which promise did these 2 soaps fulfil?
What did you receive?
Let's check your delivery.
Enter the quantities from the supplier's bill and the goods you actually received.
Supplier says today's extra soaps are:
Why can't we settle both?
Tap a record to see why it matters.
Advanced workspace History · Claims · FalkorDB evidence · Agent
Billed for 50.
Received only 48.
When a shopkeeper receives goods, the supplier's bill and the actual delivery don't always match. SahiAaya finds what's missing and remembers what the supplier still owes—even on the next delivery.
It helps small shops catch shortages, track promised replacements and avoid closing a claim without proof.
The supplier sends 2 more soaps—but also owes 2 free promotional soaps. Which promise is fulfilled?
The shopkeeper spotted a shortage. Now the next delivery is here. See how SahiAaya checks whether the supplier really made it right.
Did the shopkeeper get the missing goods back?
The supplier hasn’t said which of the two promises these soaps fulfil.
What if the supplier says something different? Explore more examples
Same delivery, different supporting evidence.
See how SahiAaya checked this Supplier response · supporting evidence · recorded result
Today’s delivery
What to do next
Reading evidence…
These are simulated replies. A real supplier message and the shopkeeper’s confirmation are required in practice.
The agent will not turn a plausible allocation into proof.
Try a different delivery Enter your own example · local FalkorDB
Try your own delivery history.
Enter your own fictional promises and deliveries. SahiAaya builds the graph and works out what is still owed.
What is settled, what is still owed — across every delivery.
In plain words: a delivery is only marked as settling a claim when there is no other possible answer. If two answers both fit the evidence, SahiAaya settles nothing and asks the supplier instead.
FalkorDB runs one max-flow over Delivery → Claim. Then it blocks each link and re-runs it: units that vanish are carried by that link in every valid allocation. Only those forced units are proposed; everything else becomes a supplier question.
This is a synthetic response; a reference string is not independently verified supplier evidence.
Ask SahiAaya to investigate, not just check quantities.
It can choose graph tools, follow earlier supplier promises, discover competing claims and create a draft follow-up. Only the shopkeeper may approve settlement.
Why did SahiAaya make this decision? View evidence and settlement history
Why does the decision change?
An invoice and a quantity alone cannot prove which older promise was fulfilled.
Why did SahiAaya decide this?
Text evidence paths
Inspect machine decision and graph tool trace
What actually changed?
No money is shown as saved until a real adjustment is proven.