Operators input pending payments when creating bookings. The system keeps these as 'pending_verification' until the Finance module operator reviews and approves the receipt, updating the client's running balances automatically.

When registering new outcall bookings, the database automatically validates the timeframe against the lady's existing active tickets on that date. If she has an overlapping shift or is marked unavailable in the roster calendar, the system blocks the creation.

Saving a settlement creates a locked payout state. Calculated bookings are assigned the matching settlement ID in the database, locking them from future selection to completely eliminate double payment errors.

To prevent unauthorized access to internal databases, the system verifies all connections (admin portal & mobile APIs) against the IP whitelist config inside settings. Unauthorized IP ranges are immediately blocked with a 403 response.

The portal calculates a dynamic SHA-256 HMAC signature using a secret system key for every registered log entry. The Audit Viewer recalculates and compares these values to verify that operational records have not been altered.