VendorAccountVerify

Who it's for

Small-business finance people / accounts payable clerks who today manually inspect emails, PDF invoices, and banking details — or ask the vendor by phone — to avoid BEC and invoice-rewrite fraud.

The problem

Payment risk (losing funds to fraud) and time cost: teams spend 5–30 minutes per suspicious invoice to verify bank-account changes and still sometimes pay the wrong account; legal/operational cost of reclaiming funds is high or impossible.

How to build it

Browser extension + a tiny hosted verifier: drag-drop invoice PDF or forward invoice email to a verifier address; outputs a one-page PDF verdict and a 1-click 'do-not-pay' flag integration for Slack/QuickBooks/Xero (webhook).

How it makes money

Who pays: small businesses / bookkeeping firms via a per-seat SaaS ($15–$40/month per seat, or $150/mo for a 5-seat team). Why they pay: the expected prevented loss per prevented fraud > monthly fee (BEC losses are often thousands); they can't use a free option because free tools either miss real fraud (low trust) or require heavy manual verification; vendor refuses to accept liability so teams will pay to reduce risk.

Why it doesn't exist yet

Banks and ERP vendors avoid building this because payment verification requires fast access to many fragmented public registries, vendor websites, and heuristics (plus privacy/false-positive liability); large vendors don't want the edge-case liability and require deep integrations. An indie can fill the gap by shipping a narrow, conservative verification product that leans on public registries, heuristics, and permissive UX (e.g., recommended 'call vendor' when uncertain) to avoid liability.

First users

The first 10 users will be AP leads at 10 small businesses who saw a colleague hit a BEC loss or receive a suspicious invoice in the last 6 months; they adopt because it saves ~10–20 minutes per suspicious invoice, plugs into their Slack/QuickBooks workflow, and demonstrably prevents one near-miss during the trial.

Build size

2 people × 10 weeks (MVP): includes PDF/email parser, IBAN/ACH extractor, heuristic matching engine (name vs. payee vs. registry), evidence-scraper (company registry/website), browser extension for drag-drop + forwarding inbox integration, and a hosted verdict PDF generator; excludes deep bank/PSD2 integrations and automated micro-deposits/refunds.

Biggest risk

Platform or major accounting vendors (QuickBooks/Xero/Stripe) ship a native, reliable vendor-account-verification feature or banks provide an instant payee-veracity API, making a small indie redundant.

Conditions for a hit (all 3 required)

• Given an invoice PDF or forwarded vendor email, outputs (within 60s) parsed payment fields (IBAN/Account Number, Routing/Sort Code), payee name, and a numeric match-score (0–100) comparing invoice payee name vs. registered company names within the extracted country (observable by feeding a test invoice).
• Produces a one-page 'matched-payee proof bundle' PDF within 60s that contains 1) invoice snapshot with highlighted extracted fields, 2) up-to-3 evidence items (registry/company website page or previous invoice on file) showing the expected bank details or registered name, and 3) an explicit 'recommendation' (Pay / Verify by Call / Do Not Pay).
• Generates a machine-readable webhook (JSON) for each verdict containing extracted fields, match-score, evidence URLs, and a unique verdict ID; integrates with QuickBooks/Xero/Slack to set a 'hold' flag on the invoice within 120s after user acceptance (verifiable by observing the webhook calls).

How it's judged (in 6 months)

Product Hunt daily top 5 or 50 paying small-business customers (Stripe/Chargebee dashboard) — measurable by public PH ranking or a public case-study page listing 50 paid customers.(judgment date 2027-03-10)

AI self-confidence 55/100 — self-reported likelihood of meeting the criterion, not a business success rate