Home / Businesses / Invoice Number Gap and Duplicate Check
Invoice Number Gap and Duplicate Check
Find gaps and duplicates in a run of invoice numbers (prefix plus counter): the missing numbers by range, each repeated counter with its forms, and a signed record.
Testing
- What it does
- Find gaps and duplicates in a run of invoice numbers (prefix plus counter): the missing numbers by range, each repeated counter with its forms, and a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
invoice_number_sequenceat 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
Invoice Number Gap and Duplicate Check is for agents that issue or audit invoices for a business and must show every number in the series is used once, or explain each gap, before a VAT or financial audit. Check a run of invoice numbers for gaps and duplicates. Send the invoice numbers (up to 200, for example INV-0001, INV-0002, INV-0004) and the prefix in front of the counter (for example INV-; leave out when the numbers are digits only). Optionally the first and last counter you expect, to catch numbers missing at either end. Get back the missing numbers by range (first, last, how many), every counter used more than once with the forms seen, and any number that does not fit the prefix-plus-counter form. It is one of the Payments department tools LLPRO builds for the work agents do across business software (QuickBooks, Xero, Stripe, FreshBooks, NetSuite). 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 issue or audit invoices for a business and must show every number in the series is used once, or explain each gap, before a VAT or financial audit.
- 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, numbers up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not read invoices or your billing system: the numbers you send are taken as given. Does not know whether a gap is allowed (voided or cancelled invoices, several series, a yearly restart): a gap is a question to answer, not proof of a missing invoice. Does not check dates against the order of the numbers. Handles one prefix per call (send each series on its own). Not tax or legal advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "invoice_number_sequence", "arguments": {"prefix": "INV-", "numbers": ["INV-0001", "INV-0002", "INV-0004", "INV-0007", "INV-0007"]}}}For agents
Tool invoice_number_sequence on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:3xabfeyzxb33j2lr2ggfqnf4t4): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): CrncKqosgAejMn6cdlZe7j+IdmJPmNiBZyzy9jUmqc8=
For agents that search MCP registries for invoice numbering, invoice gaps, duplicate invoice numbers tools (listed in MCP registries, served by the LLPRO 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 LLPRO: A numbering check is one step of closing a billing period. Tell LLPRO 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