Change a landlord payout status
Move the payout through the supported status action.
Exact navigationAdmin Area → Customers → open landlord → Landlord Payouts → Status
Before you begin
- Use an account with Customers: Edit and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Move the payout through the supported status action. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Customers → open landlord → Landlord Payouts → Status.
- Open the exact setting, option or record named in this guide.
- Enter or select the required value; leave unrelated options unchanged.
- Save the form and wait for the success response.
- Reload the page or open a controlled record to confirm the stored value is being used.
Fields, choices and supported possibilities
Exact actionChange a landlord payout status
Exact navigationAdmin Area → Customers → open landlord → Landlord Payouts → Status
Module version1.0.0
Access ruleCustomers: Edit
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingConfirm the property owner/landlord, estate-agent company, listing type, transaction type, privacy and status before saving.
Address and mapComplete address, city, country and latitude/longitude where the map is used.
Commercial valuesReview price/rent, commission, fees, income/expense values, currency context and availability dates.
Financial recordClient/vendor/landlord, linked property/request/contract, date/due date, currency, items, taxes, discounts, totals and status.
Payment evidencePayment mode, amount, transaction ID, note/comments, date paid and email/PDF choices where exposed.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.
Code-backed validations and workflow rules
- Status changes should match actual settlement evidence.
- Property visibility and actions are controlled by real_property view-own/view/create/edit/delete capabilities.
- Property status, account status and approval workspaces are separate from the main listing form.
- Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
- The module hooks after_payment_added to write property-related activity when the payment is linked.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
Expected result and verification
- The supported change a landlord payout status flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.