Dealer Casebook: Records Show Conflicting Times

Two records appear to describe the same controlled transaction. The amount and table match, but the times do not. One says 18:42. Another says 18:57. Or one document appears to show that a credit happened before a fill that staff remember occurring first.

Someone may immediately say, “One of these is obviously wrong. Change it.”

That response moves too quickly. A time difference can mean many things: event time, preparation time, posting time, receipt time, delayed entry, relief timing, or a genuine error.

Conflicting timestamps do not tell you which record is wrong. They tell you the sequence must be reconstructed before either record is changed.

Start with the underlying event, not the two clocks

Ask what actually moved.

Was there one fill, one credit, one cash exchange, or another value movement? Which table and amount were involved? Who delivered it? Who received it? What did the rack look like before and after? Was the game paused? Did relief happen between preparation and completion?

The records are evidence about the event. They are not the event itself.

Different timestamps may represent different moments

A transaction can have several legitimate times associated with it.

A slip may be prepared at 18:42, chips may reach the table at 18:49, a receipt field may be signed at 18:51, and a system entry may be posted at 18:57. If two records use different definitions of “time,” the difference may not be a contradiction at all.

Do not assume the labels mean the same thing until you know what each field represents.

Do not change one record just to match the other

If the paper says 18:42 and another controlled record says 18:57, overwriting 18:42 with 18:57 may make the documents look consistent while destroying the original information.

A later reviewer then cannot see that a discrepancy ever existed.

If a correction is authorised, it should remain traceable as a correction rather than pretending the original entry was never there. The same principle appears in Obscured Original Entry on a Record.

Separate event time from entry time

A useful reconstruction may identify at least two concepts:

• when the physical or controlled event occurred; and
• when a person recorded, posted, signed, received or corrected information about that event.

Those moments may be close together or several minutes apart.

If the property has defined fields for both, use them correctly. If it does not, do not invent a private convention. Escalate the ambiguity through the authorised role.

Sequence can matter even when the amount is correct

Suppose both documents show a 10,000 fill, and the rack now reconciles. It may be tempting to dismiss the time discrepancy because no value appears missing.

But sequence can still matter to handover, table ownership, transaction matching, duplicate detection, or later investigation. A correct amount does not automatically make the sequence irrelevant.

The goal is to preserve enough information that the event can be reconstructed accurately.

Compare the transaction identifiers before comparing handwriting

Look for the controlled details your property actually uses: table number, transaction type, amount, denomination, slip or reference number, preparer, receiver, witness, and other authorised identifiers.

Do not jump straight to handwriting speculation or personality-based assumptions.

If the identifiers show that the two records are actually different transactions, the apparent time conflict may disappear. If they show one underlying event, the reconciliation becomes more focused.

Watch for duplicate-record risk

Two records with different times may be mistaken for two separate transactions later.

That can create a second problem if someone posts, files, or reconciles both as independent value movements.

Before any new posting or adjustment is made, establish whether there was one underlying event or two. The guidance in Duplicate Transaction Records for the Same Value applies: preserve both records and reconcile the single event before creating another movement.

Do not “average” or guess the time

If one record says 18:42 and another says 18:57, do not choose 18:50 because it seems plausible.

Likewise, do not use the time you personally think is “close enough.” A guessed time becomes false precision.

If the exact event time cannot be established, the correct record state may need to say that timing is unresolved or approximate through the property’s authorised process.

Use your own observation carefully

If you were dealing when the transaction happened, state what you actually remember and what you do not.

You may remember that the fill arrived shortly before relief, that a particular player had already left, or that the rack was counted before a break. Those observations can help reconstruct sequence.

But avoid turning memory into a precise clock time unless you actually have a reliable basis for it.

If relief occurred between the two times

Relief can explain why records appear out of sequence.

The outgoing dealer may have seen preparation; the incoming dealer may have received the value. A supervisor may have posted the transaction after the table changed hands.

Do not force the entire event into one person’s shift merely because one timestamp falls before relief and another after. Preserve who observed each stage.

If a system entry and paper record differ

Neither medium automatically wins just because it is electronic or handwritten.

A system clock may reflect posting time, while the paper shows event time. A paper entry may be written late. Either may contain an error.

Use the authorised reconciliation process to determine what each record represents. Do not create a new duplicate posting merely to make one side match the other.

Keep accusation separate from discrepancy

Conflicting times may result from a late entry, misunderstanding, interruption, wrong field, relief, transcription error, or deliberate conduct. At first, you usually do not know which.

Say, “The records show different times.” Do not jump to “someone changed the time” or “someone falsified the slip” unless the evidence and authorised review support that conclusion.

Record the discrepancy before assigning motive.

If a correction is authorised

A good correction preserves three things: the original entry, the corrected information, and the fact that the correction happened later.

Do not backdate the correction so it looks contemporaneous. Do not erase the original time. Do not replace the entire form merely for cosmetic consistency unless the property’s controlled process specifically requires that while retaining traceability.

For the timing boundary, see Asked to Backdate a Table Record.

Handover the sequence conflict as an open item

If the discrepancy is unresolved at relief or close, hand it over explicitly.

Identify the transaction, both times, the records involved, what is already confirmed, what remains unclear, where the original documents are, and which authorised role is following up.

Do not leave two conflicting records in a packet with no explanation and assume the next shift will discover the problem safely.

If you need to document the timestamp conflict

A useful note might say:

“At approximately 19:10 I was asked to review two records relating to the same 10,000 fill for Table 3. The paper slip showed 18:42 and the second record showed 18:57. I did not alter either record. I confirmed that I received the fill shortly before my 19:00 relief but could not independently confirm the exact minute. The floor retained both records for reconciliation.”

That explains what you know without inventing a single “correct” time.

Sequence must be reconstructed, not invented

Sequence integrity matters because controlled records are used to reconstruct events later.

When two records for the same transaction show conflicting timestamps or order, preserve both, identify what each timestamp actually represents, reconstruct the underlying value movement, and keep any later correction traceable. Never alter one record merely to make the documents agree.