Home / Businesses / Duplicate Supplier Invoice Check
Duplicate Supplier Invoice Check
Flag likely duplicate supplier invoices before they are paid: same number after normalizing, same amount within a window, or the same invoice under a second supplier code, with a signed record.
Live
- What it does
- Flag likely duplicate supplier invoices before they are paid: same number after normalizing, same amount within a window, or the same invoice under a second supplier code, with a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
duplicate_invoice_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Live: open today. Free
New to this? Start here.
What it does
Duplicate Supplier Invoice Check is for agents that run accounts payable for a business and must not pay the same supplier invoice twice. Flag likely duplicate supplier invoices in a batch before they are paid (accounts payable duplicate-payment check). Send the invoices (supplier code, invoice number, invoice date, amount) and a window in days. Get back every invoice that looks like a duplicate of an earlier one and why: the same supplier and the same invoice number after normalizing (case, spaces, dashes, dots, slashes, # and leading zeros), or the same supplier and the same amount within the window, or the same invoice number and amount under a different supplier code (often a supplier set up twice). Also the number of matching pairs and the amount on the flagged invoices. It is one of the Accounting department tools LLPRO builds for the work agents do across business software (Quickbooks, Xero, Netsuite, Bill Com, Sap). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that run accounts payable for a business and must not pay the same supplier invoice twice.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, invoices up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not read invoices or your payment history: only the batch you send is compared (send the open batch together with recently paid invoices to catch a repeat of a paid one). Does not compare supplier names, bank details or line items, and does not catch a duplicate whose number and amount both differ. A flag is a reason to look, not a finding: recurring charges of the same amount (rent, subscriptions) are flagged by rule (b) on purpose when they fall inside the window. Does not block or approve a payment. Not accounting advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "duplicate_invoice_check", "arguments": {"invoices": [{"supplier": "SUP-A", "invoice_number": "INV-0012", "date": "2026-04-01", "amount": "1500.00"}, {"supplier": "sup-a", "invoice_number": "inv12", "date": "2026-04-20", "amount": "1500.00"}, {"supplier": "SUP-A", "invoice_number": "5531", "date": "2026-05-15", "amount": "1500.00"}, {"supplier": "SUP-B", "invoice_number": "5531", "date": "2026-05-16", "amount": "980.00"}, {"supplier": "SUP-C", "invoice_number": "77", "date": "2026-04-02", "amount": "300.00"}]}}}For agents
Tool duplicate_invoice_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:qkzaakuhfpehzlld36xkhxodam): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): 3fqEnVIvQNTwCIZ773adliDVJza7xiR1f9ThjdYyIrM=
For agents that search MCP registries for duplicate invoice, duplicate payment, accounts payable tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: A duplicate check is one step of paying suppliers. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card