Daily Transaction Log

The Transaction Log interface provides a comprehensive system for recording, tracking, and managing all financial transactions within your venue. This powerful tool allows authorized staff to process new transactions, review historical activity, and maintain accurate financial records for both registered and guest players.

What It Does

The Transaction Log serves as the central record-keeping system for all player financial transactions. It provides tools for creating new transactions, searching historical records, filtering by date ranges, and maintaining a complete audit trail of all financial activities. This interface ensures accurate tracking for both operational and compliance purposes.

Who It's For

Cashiers, cage managers, shift supervisors, and compliance staff who need to process financial transactions, review historical activity, and ensure proper documentation of all monetary exchanges within your venue.

Accessing Transaction Log

1. From the main CardOpz menu, click on the Player Cage icon (red icon)

2. Select "Transaction Log" from the dropdown menu

3. The Transaction Log interface will display with filtering options and transaction history

Interface Components

Filter Controls

Top section providing search and filtering capabilities:

• Transactions Between: Date range selectors with start and end dates

• Filter Button: Apply selected date range

• Date Range Display: Shows selected date range in readable format

• Search: Find specific transactions by various criteria

• Show Entries: Control how many records display per page

Transaction Grid

Displays transaction data in a detailed grid format:

• No.: Sequential listing number

• MTL Day: Date for Money Transaction Log compliance tracking

• Chip Up/Down: Chip transactions with amounts

• Cash Transactions: Cash movements with amounts and descriptions

• Details: Player identification information

• Picture: Player photo identification

• Actions: Quick access buttons for related functions

Transaction Details

For each transaction row, detailed information is displayed:

• Tournament BuyIn: Tournament entry details with amounts

• Chips Purchase/Cash Out: Chip transaction specifics

• Player Information: ID, name, and alias

• Staff Identification: Who processed the transaction

• Time Stamping: Exact time of processing

• Location: Where transaction was processed (Cage, Floor, etc.)

Action Buttons

Each transaction has action buttons for quick functions:

• Appearance: Record or view player physical appearance

• Edit Player: Access player profile editing

• Player Profile: View complete player details

• Transactions: View player's complete transaction history

New Transaction Modal

When creating a new transaction, a modal appears with fields:

• MTL Day: Date of transaction

• Transaction Amount: Dollar value

• Location: Where transaction occurs

• Transaction Type: Category selection

• Player Assignment: Registered or Guest player option

• Player Search: Field to locate specific player

• Action Buttons: Cancel or Save Transaction

Using Transaction Log

Filtering Transactions

1. Set date range using the "Transactions Between" date pickers

2. Click "Filter" to apply the selected date range

3. Optionally filter by specific cashier if needed (don't think we track this. If we do I don't see a way to filter it. Can someone confirm?)

4. Use search field to find specific transactions

5. Navigate between pages to view additional records

Creating New Transactions

1. Click the "+ New Transaction" button

2. Enter required information:

   • MTL Day: Date of transaction (always pre-populates to the day of)

   • Transaction Amount: Dollar value

   • Location: Where transaction occurs

   • Transaction Type: Category from available options

3. Select player assignment method:

   • Registered Player: Select from database

   • Guest Player: For non-registered customers

4. Search for and select the appropriate player

5. Click "Save Transaction" to process

Viewing Player-Specific Transactions

1. Click the "Transactions" button for any player

2. View the complete transaction history for that specific player

3. Note in/out values and net transaction amounts

4. Export data for reporting or documentation

5. Return to the main Transaction Log when finished

Accessing Player Information

1. Click "Player Profile" to view complete player details

2. Click "Edit Player" to modify player information

3. Review player information for verification purposes

4. Update information as needed and permitted

5. Return to Transaction Log after viewing or editing

Player Appearance Recording

An important compliance function available from the Transaction Log interface:

Accessing Player Appearance

1. Click the "Appearance" button for the relevant transaction

2. The Player Appearance modal will open for data entry

Appearance Interface Components

Physical Characteristics Section:

• Gender, Race, Age, Height, Weight

• Eye Color, Hair Color, Facial Hair

Clothing Section:

• Outfit type and color options

• Top, Bottoms, Jacket details

• Headwear, Eyewear specifications

Additional Features Section:

• Scar location and description

• Tattoo placement and designs

• Piercings, Birthmarks

• Other distinctive features

Recording Appearance Information

1. Complete all applicable fields in each section for the gaming day

2. Focus on visible and distinctive characteristics

3. Be specific but objective in descriptions

4. Click "Save Player Attributes" to record the information

Best Practices

Transaction Processing

• Verify player identity before processing any transaction

• Count all cash twice before finalizing transactions

• Document reason for transaction clearly in comments

• Ensure proper approvals for transactions above thresholds

• Follow consistent procedures for all transaction types

Compliance Documentation

• Record player appearance for all transactions near reporting thresholds

• Document all transaction details accurately and completely

• Maintain consistent MTL day designation for proper tracking

• Flag suspicious transaction patterns according to venue policies

• Follow all regulatory requirements for transaction recording

Operational Efficiency

• Process transactions promptly to maintain accurate real-time records

• Use transaction codes consistently for reporting accuracy

• Train all staff on proper transaction categorization

• Maintain organized physical documentation

• Reconcile electronic and physical records regularly

Appearance Documentation Best Practices

• Record appearance for all transactions near reporting thresholds

• Follow consistent documentation protocols for all customers

• Maintain objectivity in all descriptions

• Document only observable characteristics

• Update appearance information with each new transaction

• Conduct documentation discreetly to maintain customer experience

Common Questions

How do I process a transaction for a player not in the database?

Use the "Guest Player" option when creating a new transaction. Enter all required information manually. For repeat guests, consider registering them in the patron database for more efficient future transactions.

What is an MTL Day and why is it important?

MTL (Multi Transaction Log) Day refers to the gaming day for compliance tracking purposes. Properly tracking transactions by MTL Day is critical for regulatory compliance, especially for monitoring transaction thresholds that require reporting.

How do I void or correct an incorrect transaction?

For recent transactions, use the transaction history view to locate the transaction, then select the void option. Document the reason for voiding and create a new corrected transaction if needed. Voiding may require supervisor approval based on your venue policies.

When is appearance documentation required?

Appearance documentation is typically required for cash transactions approaching or exceeding regulatory thresholds (often $10,000 or venue-specific limits). Many venues also require documentation for multiple transactions that appear to be structured to avoid thresholds, or for any transactions flagged as unusual or suspicious.

How are appearance records used?

These records serve multiple compliance purposes: they document that the person was physically present for the transaction, provide verification that proper identification procedures were followed, create an audit trail for regulatory review, and help identify patterns of activity across multiple transactions or visits.

Related Features

For more information on financial transaction management, see:

• Player Cage Overview

• Player Accounts

• Cage Summary

• MTL Documentation Requirements

• Regulatory Reporting Procedures