Dealer Casebook: Original and Carbon Copy Conflict

An original and its carbon or duplicate copy are supposed to tell the same transaction story. Here they do not. The difference may be an amount, reference, signature, mark, time, or another field that should have carried through the multipart process. Once the versions diverge, choosing the neater-looking one is not reconciliation.

The useful question is when the two versions stopped matching and which independent evidence can establish the transaction state before that divergence. Both documents matter because each preserves a different record state.

Keep the original and copy separate but linked, list every material difference, and rebuild the transaction from independent records before any authorised correction is made.

Preserve both versions before comparing them

When the two versions show different amounts, references, signatures, marks, or other transaction details, the first useful step is not to tidy the paperwork. Keep a controlled original and its carbon or duplicate copy in the condition in which the discrepancy was discovered. Note who noticed it, where it was, and what was physically present. This protects the difference between the transaction state and the later discovery state, which can matter when the responsible role reconstructs the sequence.

List the differences field by field

The open question is which version reflects the fact at the moment of transaction and when the divergence entered the record trail. Say that precisely. Broad labels such as “paperwork problem” or “bad handover” hide the decision that actually needs to be made. A dealer should separate what is visible from what is inferred and avoid turning a missing explanation into a claim about who caused the problem.

Do not force one version to match the other

The temptation is forcing one version to match the other before the discrepancy has been reconstructed. That may make the desk look cleaner while making the evidence worse. Do not add, remove, swap, rewrite, staple, un-staple, or refile controlled material simply to make the paperwork appear normal. A cosmetically complete packet can be less trustworthy than an openly incomplete one.

Keep original and copy identities unmistakable

Keep the identifying features of a controlled original and its carbon or duplicate copy visible: form or sequence number, table, shift, transaction reference, amount, role fields, and any marks that distinguish one version from another. If something is unclear, describe it as unclear. Do not invent a missing identifier from memory or from what “must have” happened.

Test the transaction independently of either version

Two inconsistent versions create a record-integrity problem, but they do not by themselves establish a value error. Recalculate or reconcile the transaction from independent evidence first, then determine which document state corresponds to that evidence and how the divergence should be documented. The paper conflict and the value question are linked, not interchangeable. Compare with a related Casebook reconstruction.

Limit each witness to the version they actually handled

Ask each person about the version they actually handled. Someone who signed the original can confirm that act; someone who received the carbon can describe what arrived. Do not ask either person to certify the contents of a version they never saw. The point is to locate the divergence, and broad retrospective statements make that harder.

Escalate the version conflict to the record owner

A conflict between an original and a copy belongs with the property role that can reconcile controlled records and the underlying transaction. The dealer should not let a quick show of hands decide which version “must be right.” Escalate the mismatch with both documents preserved so the responsible role can compare them with independent records.

Use independent records to locate the point of divergence

Compare a controlled original and its carbon or duplicate copy with independent records that legitimately exist: transaction logs, issue records, packet inventories, table identifiers, shift records, or system references. Use them to test the reconstruction. Do not alter the questioned document first and then use the altered version as evidence that everything agrees.

Do not cure a mismatch with a backdated signature

Do not ask a person to add a missing signature to one version simply to make it resemble the other. A current review mark may be appropriate if authorised and clearly dated as such, but it must not imply that the person signed or witnessed the transaction at the original time.

Protect sensitive data on both versions

Because two versions are now in circulation, the exposure risk is doubled. Keep both documents in authorised custody and avoid informal photos or messaging. If comparison requires another department, transfer the minimum necessary material through the property’s approved route.

Record which version was found where

Document which version was found where, the exact fields that differ, who controlled each version when discovered, the independent records checked, and the authorised decision. Avoid shorthand such as “copy wrong” unless the review has actually established that conclusion.

Carry both versions through handover if unresolved

If the issue remains open at relief or close, carry it forward explicitly. The handover should identify a controlled original and its carbon or duplicate copy, the unresolved question, current custody, and any action already taken. “Supervisor aware” is not enough if the next shift cannot tell what is missing, conflicting, extra, or still under review. The same handover discipline appears in this related custody case, where the next team needs the unresolved state, not a cleaned-up summary.

Make any correction preserve the superseded state

A correction should not erase the version conflict. If one record is voided, superseded or annotated under procedure, keep the relationship between the two versions visible. Destroying or silently rewriting one side can make the later audit trail less reliable than the original mismatch.

Explain the review without declaring a winner too early

Explain that two transaction records are being reconciled and that the responsible supervisor is reviewing them. Do not show both controlled versions across the table or announce that one is “fake” or “wrong” before the review is complete. Urgency should accelerate the authorised comparison, not pre-judge it.

Reconstruct from transaction facts back to the documents

Secure both versions, list every material difference, identify who last handled each one, compare the transaction against independent logs or system records, escalate to the record owner, and document the authorised correction without erasing the superseded state. The sequence should leave a reader able to see both the divergence and its resolution.

A clean resolution explains why the versions diverged

A strong close explains which transaction facts were verified, how the original and copy came to differ if that can be established, which record state is controlling, and what happened to the other version. Both the decision and the evidence path should remain visible.

Do not call one version false without proof

Do not claim that which version reflects the fact at the moment of transaction and when the divergence entered the record trail has been proved unless the authorised review actually establishes it. Do not label the event theft, tampering, falsification, negligence, or misconduct from the paperwork alone. Record integrity improves when observation, inference, decision, and allegation remain separate.

Keep both evidence states until the authorised decision is documented

In this case, the safest operational judgement is to preserve both versions as distinct evidence states, isolate every difference, and reconcile the transaction from independent supporting records. That approach protects both the employee and the casino because it preserves evidence, keeps authority visible, and allows the responsible role to resolve the actual uncertainty rather than a version that has already been cleaned up.