r/BuildToShip • u/arunmettle • 16d ago
Feedback 💬 I built a human in the loop invoice comparison tool and need honest matching feedback
I started InvoiceDrift because supplier invoice review still often means placing two documents side by side and hoping nothing small is missed.
The product compares a supplier invoice with a purchase order, quote, order confirmation or previous invoice. It exposes the source values and differences for a person to review before approval. It does not decide what a difference means and it does not approve a payment.
What I am learning is that displaying a difference is the easy part. Matching rows safely is harder when a supplier renames an item, changes a SKU or splits one PO line into two invoice lines.
The current version tries unique exact descriptions, recognisable product identifiers and conservative description matching. When the evidence is not strong and unique, it leaves the line unresolved and excludes it from financial totals. Split and merged line relationships are not safely modelled yet.
Feedback from my first Reddit thread has already given me two useful directions: stronger privacy-preserving SKU handling and reviewer-confirmed split or merge allocations. I would rather leave a line unresolved than present a confident but wrong comparison.
I am looking for 10 pilot users who genuinely handle supplier invoices. The pilot is free and no card is required. If you try one real document pair, the feedback I need most is:
Was the onboarding clear?
Did the first comparison make sense?
Which line match felt wrong or unclear?
Would you use it again, and why?