Pending Payments¶
The Pending Payments screen lists payment items that have been created but not yet billed or paid. It is the primary starting point for the daily billing workflow.
Navigation¶
Penzugyek (Finances) -> Fuggo tetelek (Pending Items) at /Club/PendingPayment.
A badge in the header shows the current count of pending items.
What Appears Here¶
Pending payments are records in the Payment table with PaymentStatus_ID = 2 (Created).
Billed-but-unpaid items
The system parameter PendingPaymentIncludesBilledButUnpaid controls whether items with PaymentStatus_ID = 3 (Billed) also appear in this list. The default is NO -- only Created items are shown.
Key Fields on Each Payment Record¶
| Field | Description |
|---|---|
| BillDate | Date the item was billed |
| DueDate | Payment deadline |
| InvoiceReference | External invoice identifier |
| InvoicePrepared | Flag marking the item as ready for invoice generation |
| LastGenerateInvoiceDate | Timestamp of the most recent invoice generation attempt |
| ActionDueDate | Administrative action deadline |
Source Links¶
Each pending payment is linked to the entity that created it. Exactly one of these foreign keys is populated:
- Reservation_ID -- single booking
- RecurringReservation_ID -- recurring booking series
- Attendance_ID -- attendance-based charge
- CoursePackage_ID -- course package purchase
- Subscription_ID -- subscription charge
Processing Workflow¶
flowchart LR
A[Select items] --> B[Review amounts]
B --> C[Generate invoice]
C --> D[Mark as Billed / Paid]- Select items -- use the checkboxes to pick one or more pending payments.
- Review amounts -- verify the net, VAT, and gross amounts are correct.
- Generate invoice -- trigger invoice generation (see Invoicing). The InvoicePrepared flag is set automatically.
- Mark as Billed / Paid -- the payment status advances from Created(2) to Billed(3) or directly to Paid(5).
Tip
Use the ActionDueDate column to prioritise items that require immediate attention.