A status is a sentence. Make sure everyone reads it the same way.
The statuses
Pending, confirmed, released, rejected and failed are the payout statuses in Propto. Define each in your handbook.
Tell the partner
Notify partners when status changes. Silence breeds calls.
Review failures
Failed payouts need a reason and a fix, usually bank details. Track them until resolved.
Why statuses matter
Partners want to know not only what they earned but when they will be paid. Without clear statuses, they call repeatedly, and your team spends time checking spreadsheets. Clear payout statuses answer the question before it is asked.
Statuses also help finance manage the payout pipeline and spot delays.
The core statuses
A simple set works for most programmes: pending (earned but not yet eligible), eligible (trigger met), approved (verified for payment), paid (transferred) and on hold or failed (with a reason). Each status should have a clear definition.
Avoid creating too many statuses, which confuse partners.
Moving between statuses
Define what moves a payout from one status to the next: payment trigger met, KYC complete, approval recorded, transfer confirmed. Automate status changes where data allows, such as moving to eligible when the booking payment reaches the trigger.
Record who approved each payout and when.
Telling the partner
Notify partners when a payout changes status, especially when it is approved, paid or put on hold. Notifications reduce calls and build confidence.
Include the reason for any hold, such as missing KYC or a pending dispute.
Handling failures
Transfers sometimes fail because of incorrect bank details or bank issues. Record the failure, inform the partner and resolve promptly. Verify any bank detail changes carefully before retrying.
Track failures to identify recurring problems.
Reviewing the pipeline
Finance should review payouts by status weekly: how many are eligible but not approved, how many approved but not paid and how long items wait at each stage. Delays at a particular stage point to process issues.
Set target times for each stage.
Linking to statements
Show payout status on commission statements, so partners see earnings and payment progress together. Consistency between statements and notifications prevents confusion.
Use the same definitions everywhere.
Why it matters for partners
Many partners depend on commissions for their income. Predictable, visible payouts reduce financial stress and build loyalty. Uncertainty, even when payments eventually arrive, damages trust.
Partners who trust your payouts are more likely to prioritise your projects.
Getting the team involved
Finance owns payout processing, partner managers communicate with partners and sales ensures bookings and payments are recorded promptly so triggers are met on time.
Make status visible to partner managers so they can answer questions.
Building the habit
Process payouts on a regular schedule, review the pipeline weekly and resolve holds quickly. Regularity is what partners value most.
Report payout performance monthly.
A worked example
A partner’s commission shows pending until the buyer pays half the booking amount. When the payment is recorded, the status moves to eligible automatically. Finance checks KYC, approves and schedules the transfer. When the bank confirms, the status changes to paid and the partner receives a notification.
Another payout fails because of a closed bank account; the partner is informed, updates details through verified channels and receives payment the following week.
Common mistakes
Common mistakes include vague statuses, no notifications, unexplained holds and payouts processed irregularly.
Another mistake is changing bank details without verification.
Questions teams often ask
How often should payouts be processed? On a fixed schedule, such as twice a month.
Should partners see reasons for holds? Yes, clearly and promptly.
A payout status checklist
Clear statuses with definitions. Automated transitions where possible. Approvals recorded. Notifications at key changes.
Failures handled with verified bank details. Weekly pipeline review with target times. Statements showing status.
In practice
Define your statuses, configure automatic transitions from booking payments and set up notifications. Process payouts on a fixed schedule and review the pipeline weekly.
Ask partners after a month whether status visibility has reduced their need to call.
A final word
Payout statuses are a small feature with a large effect on partner trust. When partners can see exactly where their money is, they focus on selling rather than chasing.
Keep definitions stable, communicate changes early and treat every hold as a matter to resolve quickly rather than a reason to wait.
In short
Use a few clearly defined statuses, automate transitions, record approvals, notify partners, resolve failures carefully and review the payout pipeline weekly.
Why this builds a stronger network
Over time, a payout process that always does what it says becomes one of your strongest selling points when recruiting new partners. Experienced brokers ask other developers’ partners how reliably they get paid before deciding where to send their next buyer, and a clear answer backed by visible status wins that conversation before it even starts.
Invest in making that answer true.
In one line
Predictable payouts, visible at every stage, are one of the simplest ways to earn a partner’s long-term loyalty.
Review the pipeline every week without fail.
Automate where you can.
Consistency across every payout cycle is what ultimately earns trust.
Keep it steady.
Who processes payouts?
Admins review and process payout requests raised by agents, employees and leaders.