Dealer Casebook: Duplicate Controlled Form Number

Two transaction records are on the desk, in a packet or attached to separate table events. At first they appear ordinary. Then someone notices that both carry the same controlled form number or sequence identifier even though they describe different transactions.

That duplicate can trigger an immediate conclusion: one record must be fake, copied, reused or wrong. The duplicate certainly needs investigation, but it does not by itself tell the dealer which record is valid or how the duplication happened.

Preserve both records exactly as found, stop the duplicate identifier from being propagated into new paperwork, reconcile each underlying transaction on its own facts, and let the authorised process determine how the numbering discrepancy is corrected.

Treat the duplicate as an identity conflict

The first fact is not that one transaction is invalid. The first fact is that one controlled identifier appears to point to two different records. State that discrepancy plainly and avoid deciding which record “owns” the number until the supporting facts are reconciled.

Keep both originals together with their separate histories

Do not separate one record as the “bad copy” before review. Preserve where each record came from, which packet or table it belonged to, and who had custody. Two papers with the same number can have very different transaction histories.

Do not renumber either record on your own

Changing one number may seem like the fastest fix, but it can create a third version of the problem. The original duplicate is part of the history. Any authorised correction should remain traceable to the state that was discovered.

Reconstruct transaction A and transaction B independently

Identify amount, table, type of movement, people involved, time window and supporting records for each transaction. If both value movements are legitimate, the numbering problem may be administrative rather than financial. If one value movement is unresolved, that requires separate attention.

Do not use visual appearance as proof

A cleaner form is not automatically the original. A handwritten form is not automatically the duplicate. Printing quality, ink colour, fold marks or neatness may be observations, but they are not enough to decide authenticity or intent.

Check whether the number was carried forward elsewhere

The same sequence number may have been entered in a log, packet list, system note, fill/credit reference or another document. Do not copy it into more places until the identity conflict is contained. Additional propagation makes later correction harder.

Compare with the surrounding sequence

The neighbouring numbers can provide context, but they do not automatically identify the correct record. The earlier case Gap in a Controlled Slip Number Sequence is useful here: sequence patterns help reconstruction, but a gap or duplicate should not be turned into an accusation without evidence.

Separate duplicate numbering from duplicate value

Two different transactions carrying one number is not the same as two records representing the same value movement. Compare this case with Two Records for the Same Value Movement. In one case identity collides; in the other value may be duplicated. The controls overlap, but the questions are different.

If the dealer issued one of the records

Confirm only what you actually did: which form you handled, what number you saw, what transaction it supported and when you passed it on. Do not “fix” the other record merely because your memory of your own transaction is strong.

If both records appear properly completed

That does not remove the discrepancy. Signatures, witness marks and amounts may all be internally consistent while the sequence number conflicts. Preserve that uncomfortable state instead of forcing one document to become void simply because two complete records cannot share the same identity.

If one record has already been processed

Do not assume processing proves priority or validity. Note what has already moved through the authorised workflow and what remains open. A later correction may need to preserve the fact that one record was acted upon before the duplicate was discovered.

Keep player and credit information controlled

If the records contain marker, account or player data, do not lay them side by side in a public area or photograph them for convenience. The need to compare two documents does not widen who should see them.

Use neutral language about cause

Possible explanations include printing, numbering, manual issue, packet assembly, copy handling or other process errors. Do not label the duplicate “fraud,” “reuse” or “forgery” unless an authorised investigation establishes that conclusion.

Make the correction visible, not magical

If the responsible role decides one number should be corrected, voided, cross-referenced or supplemented, the final record should still reveal that a duplicate was discovered and how it was resolved. The purpose of correction is accurate history, not a perfect-looking sequence.

Carry unresolved duplication into close or relief

If the shift changes before reconciliation, hand over both record identities, both transactions, their custody location, what has already been processed, and who owns the next step. Do not summarize the situation as “duplicate fixed later” if no authorised correction has happened yet.

Resolve the duplicate number without erasing either record

A duplicate controlled form number creates an identity problem that must be preserved before it can be solved. Protect both records, stop further propagation, reconstruct each transaction independently, avoid assumptions about which paper is valid, and make the authorised correction traceable to the original conflict.

Check pre-numbered stock or issuance context without assuming cause

If the property uses pre-numbered forms, the responsible role may need to compare issue records, unused stock or surrounding numbers. The dealer should preserve the evidence and provide factual context, not conduct an informal hunt through controlled stock or decide that a printer or employee caused the duplicate.

Do not void one record merely to restore a tidy sequence

A void decision can affect the transaction trail. If both underlying transactions occurred, voiding one document solely because the number is duplicated may falsely suggest the transaction itself did not happen. The authorised correction needs to preserve both the value history and the numbering discrepancy.

Watch for downstream packet counts

A duplicate identifier can make packet counts look correct while identity is wrong, or make two legitimate records appear to be one. When closing or handing over, state that two separate records exist even if the identifier count would otherwise collapse them into a single line item.

If the duplicate is discovered much later

Do not rewrite the old transaction from today’s memory. Record when the duplicate was discovered, preserve the historical records, and let the authorised review reconstruct the earlier events from controlled evidence. Discovery date and transaction date should remain distinct.

Check manual and system references without forcing them to agree

If one transaction is also referenced in a system or departmental log, compare those records as supporting evidence rather than automatically making the paper match the screen. A duplicated form number may exist only on paper, only in a downstream entry, or in several places. Preserve where the conflict actually appears before correction.

Keep each person to their own observation

The dealer who handled transaction A should describe transaction A; another employee should describe transaction B. Do not ask one person to certify that the other record was issued incorrectly. Separating witness scope prevents the duplicate-number problem from turning into unsupported cross-certification.

Close with both identities explicit

If reconciliation cannot finish immediately, the handover should name both documents, both underlying transactions, the shared number, their current custody and any processing already completed. A later reviewer should not have to rediscover that two physical records existed simply because one identifier appears in the summary.