LLPROBeta

Home / Businesses / Payment Batch Duplicate Check

Payment Batch Duplicate Check

Check an outgoing payment batch before release: every likely repeat (same payee, amount and reference, or a payee set up twice), the amount at risk and the amount clear to release, signed.

Testing

What it does
Check an outgoing payment batch before release: every likely repeat (same payee, amount and reference, or a payee set up twice), the amount at risk and the amount clear to release, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call payment_batch_dedupe at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Payment Batch Duplicate Check is for agents that prepare or release supplier payment runs for a business and must not send the same payment twice. Check an outgoing payment batch for likely duplicate payments before it is released. Send the payments (payee code, amount, optional invoice or remittance reference) and, if you have them, the payments already released recently with their dates. Get back every payment that looks like a repeat and why: the same payee, amount and reference; the same payee and reference with another amount; the same payee and amount with another or no reference; or the same reference and amount under another payee code (often a payee set up twice). Also the amount at risk, the batch total and the amount that is clear to release. It is one of the Payments department tools LLPRO builds for the work agents do across business software (QuickBooks, NetSuite, Xero, Sage, Stripe). 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 prepare or release supplier payment runs for a business and must not send the same payment 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, payments up to 200 entries, paid 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 your bank file or ledger: only the payments you send are compared (send recently released payments in paid to catch a repeat of one already made). Does not compare payee names, bank details or remittance lines, and does not catch a repeat whose payee code, reference and amount all differ. A flag is a reason to look, not a finding: two real invoices of the same amount to one payee in one batch are flagged by same_payee_and_amount on purpose. One currency. Does not stop, approve or reverse a payment; your release process decides. Not legal or accounting advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "payment_batch_dedupe", "arguments": {"payments": [{"payee": "P-100", "amount": "1250.00", "reference": "INV-0045"}, {"payee": "p-100", "amount": 1250, "reference": "inv 45"}, {"payee": "P-100", "amount": "1300.00", "reference": "INV-45"}, {"payee": "P-200", "amount": "1250.00", "reference": "INV-0045"}, {"payee": "P-300", "amount": "500.00", "reference": "A1"}, {"payee": "P-300", "amount": "500.00", "reference": "A2"}]}}}

For agents

Tool payment_batch_dedupe on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:otu2cfspnbhz5aoax5yfirs3pq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): Rbk7qedheUrKefaIDX00e12DG9o83VCnJxtIbxZiJaM=

For agents that search MCP registries for duplicate payment, payment run, 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

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card