Skip to main content
All updates
Bug fixCoursesPaymentsReceiptsReports·Sat Aug 15·

Course payments and merged client emails stay connected

Recording money received for a course now creates the payment, receipt, reporting, and participant balance records together, while inactive merged clients no longer block their survivor from adopting the correct email.

# Course payments and merged client emails stay connected

When a course participant is marked partly or fully paid without an existing payment record, the payment editor now asks how the money was received and saves everything in one action. The venue payment method, received date, reference, participant balance, payment history, sales reports, payment-method reports, receipt number, and client receipt are created together. Retrying the same save does not count the money twice.

Reversing one of these recorded payments keeps the audit history but removes it from settled sales and updates the participant balance. Receipts for cash, terminal, bank-transfer, and other configured external methods now show a clear payment-method label.

A surviving client profile can also adopt the email address left on its already-merged source profile when that source is inactive everywhere. Booking Bible still refuses the transfer if the retained identity is active at another venue. Normal duplicate-email validation remains visible to staff without creating a production issue alert.

Check-in now recognizes native course access as a valid booking entitlement. Course students who book through a paid preparation/access phase show their course on the roster and in Add Client instead of the misleading “No active pass” warning; their existing course grants and bookings remain unchanged.
Next update

More reliable course-payment records and releases

External course payments now keep a canonical payment link, while deployment checks can reproduce the same database structure in every environment.