How to create a residential community receivables policy

Summary

A residential community receivables policy turns scattered decisions into a repeatable process. It should identify the valid data source, the trigger for every collection stage, the people allowed to approve exceptions, the evidence required to confirm a payment, and the point at which an administrative case is handed to the community's legal provider.

It is not a collection of message templates. It is the operating agreement that lets management execute, the board supervise, and accounting explain why each obligation received a particular treatment.

Notice: this is operational information, not legal or accounting advice. Each community should review its policy with its advisors and governing documents.

1. Define the objective and scope

Start with a testable objective: reduce delinquency and make receivables progress visible without sending incorrect notices or confusing administrative follow-up with court action.

At minimum, define:

• which ordinary or special assessments and other charges enter the workflow;
• which system or report holds the official balance;
• which units, agreements, disputes, or payments in transit are excluded;
• who may correct a balance or approve a special condition;
• which channels and hours may be used;
• what evidence confirms a payment;
• when contact stops or a case is escalated.

Colombia's Law 675 of 2001 regulates the horizontal-property regime, but each community must also consider its governing documents, valid decisions, and the facts of each obligation.

2. Establish one receivables source of truth

The process breaks when accounting, management, the bank, and the collection provider use different balances. Maintain stable identifiers for the unit, authorized party, charge, period, and obligation.

Every update should retain the old and new balance, source, date, related payments or adjustments, person responsible, and validation status. A receipt sent in a chat should not change the official balance on its own. It belongs in the association-fee reconciliation workflow as confirmed, probable, or unresolved.

3. Create observable stages

Preventive

Before the due date, provide the statement, deadline, and access to the community's existing payment method. The goal is to prevent avoidable delinquency.

Administrative

After the due date, coordinate reminders, responses, promises, partial payments, and exceptions. Contact must use the current balance and stop for a confirmed payment, dispute, or review instruction.

Pre-legal and out of court

This is persuasive follow-up before any court proceeding. It needs entry rules, duration, contact controls, owners, and exit rules. It does not include lawsuits, seizures, or legal representation. See the guide to pre-legal collection for residential communities.

Legal

Legal action remains with the attorney or legal provider selected by the community. The policy should define the handoff package and authorization process, not attempt to turn administrative messages into a court case.

4. Approve contact and data rules

The policy should incorporate the requirements that apply to the specific relationship. Colombia's Law 2300 of 2023 addresses channels, schedules, and frequency for collection activities within its scope. Law 1581 of 2012 establishes personal-data principles including purpose, quality, restricted access, security, and confidentiality.

Document the source of contact details, allowed channels, maximum frequency, approved tone, correction process, access roles, and retention conditions.

5. Build an exception circuit

Create explicit states for payment under review, ambiguous receipt, active agreement, disputed balance, wrong contact, existing legal process, and data-correction request. Each exception needs an owner, deadline, and permitted next action. Automation should not treat an unresolved exception as an ordinary delinquent account.

6. Give the board decision-grade metrics

A useful monthly report separates opening, new, and recovered receivables; manageable and excluded accounts; attempted and effective contact; open, fulfilled, and broken promises; confirmed and unmatched payments; exceptions and resolution time; and cases prepared for legal review.

Do not confuse activity with outcomes. One hundred messages are not one hundred managed accounts or recovered balances.

7. Version and test the policy

Record the date, version, approving body or person, and changes from the prior version. Test a limited sample before applying the policy to every account. Review incorrect notices, payments that failed to stop contact, stale data, and ownerless exceptions.

Certeza's residential community receivables solution can translate an approved policy into segments, sequences, controls, and reports. Management retains the decisions and accounting source of truth.

Checklist

• One official source exists for balances and obligations.
• Every stage has entry and exit criteria.
• Channels, hours, and templates are approved.
• A confirmed payment stops the relevant contact.
• Exceptions have an owner and deadline.
• Pre-legal work remains separate from legal action.
• The board receives outcome metrics, not only activity counts.
• The policy has a version, date, and approver.

Frequently asked questions

Must the policy contain every message?

It may include templates or point to a controlled appendix. It should always state who approves them, which variables they may use, and how updates are governed.

Can one sequence cover the entire portfolio?

It is rarely appropriate. Aging, balance, active agreements, payments in transit, disputes, and contact quality change the correct treatment.

Who approves exceptions?

The policy assigns that role by exception type. Certeza does not independently approve discounts, accounting adjustments, or legal conditions.