Portfolio
Standardise the request.
Use a consistent RentLink record for amount, due date and tenant context.
Explore collectionFor build-to-rent
Standardise requests and payment status across buildings while keeping exceptions and agreed payout routes visible to the team.
Use these paths to compare the product, operating model and next decision.
Portfolio
Use a consistent RentLink record for amount, due date and tenant context.
Explore collectionOperations
Match batches and isolate the items that need review.
Explore reconciliationTechnology
Plan a supported PMS, accounting or no-API route.
Explore connectionsGrowth increases the cost of inconsistent references, manual matching and unclear ownership. CasaPay connects the rent request to status and downstream review.
The team can use common controls while retaining building, entity and recipient context in the agreed setup.
Automation should make uncertainty visible rather than hide it. A reconciliation batch can contain matched payments and items requiring review at the same time.
Define who owns each exception, the evidence required and how status reaches accounting and resident-facing teams.
Name an owner, select representative buildings and measure time to first live payment, reconciliation effort and settled TPV.
Confirm local rails, entities and payout requirements before making a regional rollout commitment.
The workflow is designed for portfolio operations, but entity, reporting and payout details must be confirmed for the proposed setup.
Recurring and direct-debit capabilities are market-dependent and must be confirmed during onboarding. The page does not assume universal availability.
Supported integrations vary. CasaPay can also begin with a portal or agreed no-API workflow.
Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.