How to reconcile association-fee payments by unit

Summary

Reconciling association-fee payments by unit means matching each confirmed payment to the correct obligation and retaining evidence of how the match was made. The process must handle partial payments, grouped payments, incomplete references, duplicates, reversals, and receipts submitted by different residents.

The goal is not to force a match to empty a queue. It is to apply high-confidence cases and send ambiguity to review before stopping contact or changing receivables.

1. Define stable identifiers

Maintain identifiers for the community, tower or block, private unit, owner or authorized party, charge and period, obligation or invoice, and bank transaction or receipt.

An apartment number alone may be insufficient when towers repeat, occupants change, or third parties pay. Use a unit key that does not change with the resident's name.

2. Keep sources separate

Receivables and money usually come from different systems. Accounting stores charges, balances, and applications. The bank or payment gateway confirms transactions. Receipts add evidence but may be cropped, duplicated, or later reversed.

Certeza is not a payment gateway and does not receive or hold funds. It can work in front of the bank or processor already used by the community and coordinate the available reconciliation data.

3. Normalize before matching

Convert amounts, dates, references, documents, and names into consistent formats without deleting the original value. Keep the received data for audit and the normalized value for comparison.

Useful normalization includes preserving significant zeroes in references, storing time with a known time zone, separating gross and net values, mapping tower and unit variants to an internal key, and detecting the same receipt submitted more than once.

4. Use confidence levels

Confirmed

The reference identifies the obligation or unit, and the amount and date are consistent. Approved rules may apply it and stop related follow-up.

Probable

Several fields match, but a definitive identifier is missing. Present the candidates and evidence for review instead of marking it reconciled.

Unmatched

Evidence is insufficient or multiple obligations are equally possible. Keep it as an exception until more information is available.

Reversal or duplicate

The source reports a reversal, the transaction appears more than once, or a receipt was already used. Treat it separately to avoid overstating collections.

5. Cover real payment scenarios

The process should handle an exact payment, partial payment, payment covering multiple periods, one transaction for several units, third-party payment, additional concepts, valid references after the reporting cutoff, and reversals after initial application.

Management decides how partial and grouped payments are applied in accounting. Automation must not invent an accounting rule.

6. Connect reconciliation and collection

A reliable collection workflow checks reconciliation status before contact:

1. confirmed payment: stop or recalculate the relevant sequence;
2. probable payment: pause the delinquency message and request review;
3. unmatched: keep the exception visible without assuming the balance is gone;
4. reversal: restore the appropriate obligation state and retain evidence;
5. corrected balance: resume only from the new official source.

This prevents one of the most damaging failures in resident relationships: collecting an assessment that has already been paid.

7. Design an exception queue

Each exception should show the payment, candidate obligations, evidence, uncertainty reason, and available action. It also needs an owner, creation date, and elapsed time.

Human decisions must remain auditable. When a user confirms a match, keep who approved it and which fields were available at that time.

8. Measure a controlled pilot

Start with one period or a limited group of units. Measure confirmed automatic matches, false positives, exception-resolution time, duplicate or incomplete receipts, confirmed payments that stopped contact on time, and differences among bank, gateway, and accounting data.

Do not optimize for automation alone. A high match rate with errors is worse than a moderate rate with safe review.

The association-fee collection and reconciliation solution explains how Certeza coordinates this flow without replacing accounting or the payment processor. The receivables policy should define what happens after each state.

Frequently asked questions

Is a receipt enough to stop collection?

Only when approved rules and evidence confirm the payment. If multiple matches exist or information is missing, pause for review without final application.

Does Certeza process the fee?

No. The bank or gateway contracted by the community processes and holds the money.

Can a partial payment be reconciled?

Yes, when the source confirms the transaction and management has defined how to apply partial payments. The remaining balance returns to the workflow with updated context.