Missing Invoice Sequences
Find gaps inside the observed minimum-to-maximum invoice-number sequence.
Description
Sequence gaps identify missing numbers between observed invoice endpoints.
Sequence gaps identify missing numbers between observed invoice endpoints. They do not establish missing or fraudulent transactions.1
Find gaps inside the observed minimum-to-maximum invoice-number sequence.
When to use Missing Invoice Sequences
Use this tool to find gaps inside the observed minimum-to-maximum invoice-number sequence.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Missing Invoice Sequences and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter invoiceNumbers using the field table and calculation rules, then run the tool.
- Read missingNumbers, missingCount, firstNumber, lastNumber. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| invoiceNumbers | Invoice numbers | list of number | Required |
Enter nonempty safe-integer invoice numbers. Sort/deduplicate and scan the inclusive span; return gaps/count/endpoints.
missing=integers between min and max absent from deduplicated list Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| missingNumbers | Missing invoice numbers | list of number |
| missingCount | Missing count | integer; minimum: 0 |
| firstNumber | First number | integer |
| lastNumber | Last number | integer |
{
"input": {
"invoiceNumbers": [
1001,
1002,
1004,
1005
]
},
"output": {
"missingNumbers": [
1003
],
"missingCount": 1,
"firstNumber": 1001,
"lastNumber": 1005
}
}Limitations and assumptions
Negative numbers are allowed; only internal gaps are checked. Keep spans small: the implementation scans every integer and performs repeated membership searches.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Duplicate Vendor Payment: Find duplicate vendor-payment candidates by normalized name and amount tolerance. For a complementary task, use Record Count Reconciliation: Reconcile source and target record counts within a caller-supplied tolerance.
References
-
Missing Invoice Sequences — tool.io
Similar or alternative tools
- Duplicate Vendor Payment
Find duplicate vendor-payment candidates by normalized name and amount tolerance.
- Record Count Reconciliation
Reconcile source and target record counts within a caller-supplied tolerance.