Skip to content

Cash Advances

Jonas Breder edited this page Oct 27, 2026 · 1 revision

This feature manages the temporary provision of cash to experimenters conducting laboratory experiments.


1. Description

When participants are paid in cash immediately after a laboratory session, experimenters must receive physical cash in advance. The cash advance workflow tracks the amount of cash handed out to the experimenter, how much was paid to participants, and ensures that the remaining cash is returned and accounted for.


2. Configuration

  • Enable Vorschüsse/Budgets aktivieren (feature_advances) in Site Settings -> Finance (/admin/options/finance_settings).
  • When configuring an experiment session, set the payment type to a cash category and request an advance for the estimated total payout.
  • Once approved, the advance is logged as "issued".
  • After the session has concluded, the experimenter goes to the session report to input the actual cash payouts and settles the remaining balance.
  • Unprocessed Sessions Widget: If an advance is issued but the session report has not been finalized and balanced, the session is flagged as "unprocessed" on the central administrator dashboard.

3. Typical Use Case

An experimenter is scheduled to run a session on Monday with 10 participants, each receiving 15 EUR.

  • The experimenter requests a cash advance of 150 EUR.
  • The administrator approves and hands over the 150 EUR cash.
  • During the session, 9 participants show up and receive 15 EUR each (135 EUR total). One participant does not show up.
  • On the session completion page, the experimenter marks the session as finished, logs the payouts (135 EUR), and returns the remaining 15 EUR to the treasury. The administrator checks the report and marks the advance as settled, clearing the session from the "unprocessed sessions" widget on the dashboard.

HROOT - Hamburg Registration and Organization Online Tool

  1. Installation

    1. System Requirements and Prerequisites

    2. Docker (precompiled)

    3. Docker (self-compiled)

    4. Manual Deployment

    5. First steps after installation

    6. Backup and Maintenance

    7. Starting a local server and running automated tests

    8. Basic configuration

    9. Language configuration and timezone

    10. Custom field definitions

  2. Updating an existing installation

  3. Overview

    1. Roles: Users, Admins, Experimenters, Banking‐Administrators
    2. Experiments, Sessions, session types
    3. Monitoring, Dashboards and Reporting
  4. Subject pool and user management

    1. Pools Management
    2. Browsing the pool
    3. Exporting data
    4. Adding users
    5. Deleting users
    6. Finding duplicate users
    7. More user management
  5. Experiment management

    1. Managing Experiments
    2. Procedures (Ablaufpläne)
    3. Adding Sessions
    4. Experiment and Session Inheritance
    5. Assign participants from the pool
    6. Inviting participants
    7. Invitations Scheduling and Digests
    8. Session management
    9. Waiting list
    10. Admission
  6. Sending messages

    1. Invitation emails
    2. Confirmation emails
    3. Session reminder emails
    4. SMS and Push Notifications
  7. Managing your lab

    1. Calendar and Room Booking
    2. Staff Management
    3. Finance
  8. Settings

    1. Environment Configuration
    2. Default locale and date formats
    3. Shibboleth Integration
    4. Kimai Integration

Clone this wiki locally