Workflow guide

Automated rent reconciliation without hidden exceptions.

The goal is not to mark every line green. It is to match what can be supported and give the team a clear queue for everything else.

By CasaPay Editorial TeamReviewed by CasaPay ProductUpdated Global English

In this guide

  1. Define the objects being matched.
  2. Automate confidence, not uncertainty.
  3. Design the exception queue.
  4. Connect accounting and payouts.
  5. Measure the result.

Define the objects being matched.

A reliable process matches a confirmed payment event to a specific tenant obligation or RentLink. The reference data usually includes tenant, property, amount, due date, currency and payment identifier.

Decide how the system handles partial amounts, combined payments, duplicate references, refunds and payments received outside the expected method.

  • Obligation: what was requested and when due.
  • Payment event: what was confirmed by the payment source.
  • Match: the evidence connecting the two.
  • Exception: the reason human review remains necessary.

Automate confidence, not uncertainty.

Use deterministic identifiers and approved rules where possible. Do not force a match simply because two amounts are similar or because the tenant name appears in a note.

A batch can contain both matched and unresolved items. The interface and reporting should preserve that mixed state and avoid presenting the batch as fully reconciled.

Design the exception queue.

Each exception needs a reason, owner and next action. Common categories include missing reference, unexpected amount, duplicate event, currency mismatch, partial payment and payment linked to the wrong obligation.

Track when the item entered review, the evidence used and the final resolution. This reduces repeated investigation and creates an audit trail for accounting and operator support.

  • Prioritise by due date, amount and tenant impact.
  • Avoid silent edits to historical payment events.
  • Require review for material changes to recipient or amount.
  • Keep refunds and reversals visible after resolution.

Connect accounting and payouts.

Reconciliation does not by itself create an accounting entry or confirm a payout. Define the source of truth, export or integration event and the point at which an allocation becomes eligible for downstream routing.

Test the workflow with the real chart of accounts, entities, payout recipients and month-end process. A clean demo with one account does not prove portfolio fit.

Measure the result.

Track auto-match rate with its confidence rules, exception volume, median time to resolution, reopened items and time from payment confirmation to accounting readiness.

Use these measures with settled TPV and operator effort. A higher auto-match rate is not valuable if incorrect matches increase downstream correction.

Questions operators ask.

Can every rent payment be matched automatically?

No. Missing or conflicting evidence should remain in an exception queue.

Is reconciliation the same as settlement?

No. Reconciliation links payment to obligation; settlement confirms a relevant funds event.

Should staff be able to override a match?

The workflow can allow controlled review, but material changes should preserve actor, reason, timestamp and prior state.

Can reconciliation start without an integration?

Yes. A portal, export or agreed no-API workflow can prove the process before deeper integration.

Bring CasaPay into your operation.

Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.