Status
Know what happened.
Distinguish requested, pending, paid, overdue and failed states before contacting a tenant.
Arrears workflow
CasaPay helps teams identify outstanding rent, separate payment failures from unpaid obligations and keep the next action connected to the original request.
Use these paths to compare the product, operating model and next decision.
Status
Distinguish requested, pending, paid, overdue and failed states before contacting a tenant.
Exceptions
Keep unclear references, partial amounts and other exceptions visible for review.
Explore reconciliationTenant experience
Avoid treating every unpaid obligation as a failed payment attempt.
Read the guideA request can be unpaid without a payment attempt having failed. A payment can be processing without being complete. Arrears work should begin with the confirmed event, amount and due date rather than a generic red flag.
CasaPay keeps the rent request and payment status together, helping the operator decide whether the next action is a clarification, a payment retry, an evidence review or a separate tenancy process.
Local notice, enforcement and debt-recovery rules vary. CasaPay does not claim to automate legal enforcement or replace operator judgement, counsel or required tenant communication.
Where contractual payment protection applies, eligibility, evidence, disputes and recovery rights follow the agreed terms. The website should not imply that every overdue amount becomes an automatic payout.
Track time from due date to first review, exception volume, resolved payment references, successful retries and the share of outstanding rent with a documented next owner.
Use these measures to improve the process without adding unnecessary friction to tenants who simply need a clear payment route or accurate status update.
CasaPay supports the rent-payment workflow and status context. Legal recovery or enforcement depends on the operator's process, market and agreed service scope.
The content and status model treat these as different events. Production labels must map to confirmed payment-provider and back-office states.
No. Only obligations meeting the agreed eligibility, evidence, limit and dispute conditions can enter the applicable protection workflow.
Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.