Explain apparent invoice-number gaps without renumbering records

Setup requirements

1. The owner defines the exact sequence interval; the largest observed number does not establish completeness.

2. Do not invent legal numbering requirements, recreate invoices or treat a missing number as fraud.

3. Before any pilot, confirm an actual unresolved need and approve minimized inputs, processing environment, retention and recipients. This design does not authorize execution.

Inputs and access

1. Name

   invoice_register.csv

   Source or owner

   Billing owner

   Scope

   Synthetic entity, series, sequence value, immutable ID and document status.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

2. Name

   lifecycle_log.csv

   Source or owner

   System owner

   Scope

   Synthetic creation, cancellation or renaming events and old/new IDs.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

3. Name

   series_policy.json

   Source or owner

   Billing owner

   Scope

   Authoritative series grammar, period boundaries and approved scope.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

Human approval boundaries

1. Before a pilot, the accountable owner approves exact synthetic/minimized copies, processing environment, retention and allowed recipients.

2. Owner validates identity mappings, authority, status definitions and all unresolved evidence.

3. Any source mutation, account access, upload, external communication, commercial commitment, payment or changed permission requires separate appropriate authorization.

The problem

Shared numbering or document lifecycle events can leave apparent invoice gaps that lack an evidence trail.

Suggested task

Classify each apparent sequence gap against entity, series, document-state and lifecycle evidence.

What you could produce

A sequence coverage register separating other-entity assignments, evidenced cancellations and unexplained gaps.

Why an agent / simpler alternative

Mixed narrative and structured evidence can benefit from assisted extraction and explanation. Identity joins, interval calculations and totals require deterministic checks. A supported native report, query or spreadsheet is preferable when it answers the owner’s question reliably.

When this work comes up

Role

Billing records clerk

Trigger

A reviewer asks why numbers are missing from a scoped series.

Human approval

Owner approves scope, rules and evidence interpretation. Any operational action requires separate appropriate authorization.

Finished output

A sequence coverage register separating other-entity assignments, evidenced cancellations and unexplained gaps.

Proposed evaluation scope — no pilot authorized

Scope

One explicit series interval of at most 300 numbers, two entities and 500 lifecycle events.

Limit origin

Editorial evaluation bound, not a verified platform limit.

Overflow action

Stop and ask for approved partitioning; no silent truncation.

Pilot authorized

No

Evidence boundary

Firsthand reports establish stated friction or concerns only. O*NET provides duty context. Official documents establish limited native features or general primitives. This workflow, safeguards, fixtures and outputs are original proposals, not source-documented executions.

Proposed steps

1. 1

   Lock series grammar, entity scope and expected interval from owner policy.

   Output: series_scope.json

   Expected output: series_scope.json

   Checkpoint: Separate numeric suffixes from literal prefixes and fiscal resets.

   Approval gate: Owner approves exact inputs and rule scope before any pilot.

2. 2

   Parse every supplied number with original text retained; isolate malformed and duplicate identities.

   Output: parsed_register.csv

   Expected output: parsed_register.csv

   Checkpoint: A sequence collision remains visible even if amounts differ.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

3. 3

   Generate the expected sequence set and attach all matching document IDs across authorized entities.

   Output: sequence_coverage.csv

   Expected output: sequence_coverage.csv

   Checkpoint: Do not treat another entity’s document as belonging to the selected entity.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

4. 4

   Join missing positions to lifecycle evidence and classify only supported causes.

   Output: gap_evidence.csv

   Expected output: gap_evidence.csv

   Checkpoint: Deletion, cancellation and never-issued are different states; absent logs prove none.

   Approval gate: Owner validates the calculation or decision rule before relying on its result.

5. 5

   Reconcile explained and unexplained positions to the full interval and prepare evidence questions.

   Output: coverage_totals.json

   Expected output: coverage_totals.json

   Checkpoint: Expected positions equal covered positions plus unresolved gaps.

   Approval gate: Owner reviews unresolved findings; no operational action is authorized.

6. 6

   Package a review register and policy questions without renumbering or producing substitute invoices.

   Output: numbering_review.json

   Expected output: numbering_review.json

   Checkpoint: No tax, audit assurance or legal compliance conclusion is made.

   Approval gate: Owner accepts the separate artifact; all live actions require separate authorization.

Original starter prompt — proposed

Origin

editorial_proposal

Execution authorized

No

Text

Using only {approved_synthetic_inputs} and {owner_rules}, Classify each apparent sequence gap against entity, series, document-state and lifecycle evidence. Follow the six-step design. Preserve exact identities, evidence spans and uncertainty. Use inspectable calculations. Write only separate review artifacts described by the output schema. Stop for missing authority, ambiguous evidence or out-of-scope data. Do not change source records, contact anyone, access live accounts, post transactions or execute recovery actions.

Expected output schema — proposed

Primary key

1. series_id

2. period_id

3. sequence_number

Columns

1. document_ids

2. entity_ids

3. observed_states

4. lifecycle_event_ids

5. classification

6. evidence_complete

7. source_spans

8. owner_decision

Record status

draft_review_only

Common provenance columns

1. input_snapshot_id

2. rule_version

3. source_document_id

4. source_row_or_span

5. reviewer_decision

Unknown value policy

Unknown values remain null, not zero. Keep raw identities and evidence. Unresolved rows do not silently enter approved totals.

Synthetic output illustration — not an executed result

Label

Synthetic authored example, not observed output

Synthetic

Yes

Executed

No

Input

Expected positions

5

Entitya

1. 1

2. 3

3. 5

Entityb

1. 2

Unexplained

1. 4

Expected

Covered positions

4

Unexplained positions

1

Missing invoice asserted

No

Limits

1. Original proposed and untested design; no source documents this complete agent workflow.

2. A reported problem is not proof of prevalence, willingness to pay, harm magnitude or current demand.

3. Historical product reports require current-installation checks; a current capability document only establishes general primitives.

4. Native reports or a deterministic script may be simpler. Exports, identity mappings, context size, privacy controls and actual tool compatibility remain untested.

5. Numerical fixtures are synthetic and have not been executed. Owner review is necessary; no time saving, cost saving or revenue outcome is asserted.

Candidate platforms — compatibility untested

1. Name

   ChatGPT Work

   Required capabilities

   1. Assess this plan’s input, operation and output requirements before selecting an account.

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   Selection basis

   Editorial candidate only. Shared source facts are general primitives; this plan remains unexecuted.

   Workflow compatibility

   BotCurrent has not tested this workflow.

Failure modes

1. A fiscal reset is parsed as a missing range.

2. A deleted draft is guessed from missing data.

3. The log is incomplete for another entity.

Recovery and troubleshooting

1. Signal

   A fiscal reset is parsed as a missing range.

   Recovery

   Partition by the approved series period before calculating gaps.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

2. Signal

   A deleted draft is guessed from missing data.

   Recovery

   Mark unexplained unless a retained lifecycle event establishes it.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

3. Signal

   The log is incomplete for another entity.

   Recovery

   Scope the conclusion and request authorized coverage; do not access more records automatically.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

Unexecuted validation plan

Sample setup

Expected positions

5

Entitya

1. 1

2. 3

3. 5

Entityb

1. 2

Unexplained

1. 4

Acceptance checks

1. Scope A-001 to A-005 with A-001/A-003/A-005 in entityA and A-002 in entityB leaves one unexplained position A-004.

2. A cancellation event for A-004 changes its classification to evidenced cancellation, not active invoice.

3. Duplicate A-003 IDs create a collision even when interval coverage is complete.

4. Coverage totals remain five positions, never six from duplicate IDs.

5. Every conclusion traces to a source row or an explicitly labelled owner rule; repeated evaluation of identical frozen inputs must preserve identities and totals.

6. All original copies remain unchanged. Output is a draft review artifact, not an operational decision.

Stop conditions

1. Required identity, source coverage, calculation policy or owner authority is missing.

2. Unexpected real sensitive data is supplied without approved handling.

3. Requested work would require live access, upload, external communication, accounting posting, payment, permission change or irreversible action.

Executed

No

Fixture status

Designed specification only. No acceptance fixture or business workflow executed.

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Plan access, model usage, tool runtime and storage costs unknown.

2. Export preparation, evidence cleanup, review and correction effort unmeasured.

3. No native integration, paid service, new account or software installation assumed.

4. Case-specific effort is unknown: source extraction, identity repair, owner-rule preparation, fixture design and review may dominate model cost.

Caveat

No measured time saving, current demand, ROI or price claim. Compare the simpler remedy first.

Canadian adaptation — proposed

Verify local privacy and organizational record-handling requirements before any real-data pilot; preserve original currency, business calendars and time zones. No Canadian deployment or compliance claim.