Overdue fees are a problem in almost every housing community — and it almost always follows the same script: six months of “it’ll sort itself out”, then a tense conversation in the stairwell, and finally a dispute with no paperwork to stand on. In reality, effective collection is 90% consistent procedure and solid documentation, not confrontation. Below is the complete flow — from the first day of delay to the debt register — with the legal basics and a “what to document” table.
This is not legal advice — and it describes Polish law. The rules below come from the Polish Act on Ownership of Premises (ustawa o własności lokali, “UWL”) and the Civil Code, as they apply to Polish housing communities (wspólnoty mieszkaniowe). For unusual situations, consult a lawyer.
01Basics: when the debt falls due
Unit owners contribute to the upkeep of the common property through advances payable in advance by the 10th day of each month (art. 15(1) UWL). From the 11th day the advance is overdue — and from that day you may charge statutory interest for delay (art. 481 of the Civil Code). Two things communities forget:
- The charge must be communicated. The advance amount follows from a resolution — the owner has to know how much they owe and from when. Changing the rate without effective notification is a straight road to a lost dispute.
- Charge interest on the principal, separately for each overdue advance, at the rate in force in the given period. In court you will be asked for a calculation broken down by periods — have it ready.
02Allocating payments — art. 451 of the Civil Code
The debtor pays 500 zł, but the arrears span three months plus interest. What does the payment cover? The order is governed by art. 451 of the Polish Civil Code:
- The debtor may indicate which debt they are paying (e.g. “July advance” in the transfer title). That indication is, in principle, binding.
- Within the indicated debt, the creditor may first credit the payment against overdue ancillary amounts (interest, costs), and only then against the principal.
- With no indication — the payment is credited against the longest-overdue debt.
This matters more than it looks: incorrect allocation can “zero out” interest the community was owed, or the reverse — artificially keep alive a debt that no longer exists.
03The stages of the procedure
Stage 0 — monitoring
Define, in the community’s own collection policy, the trigger for opening a case (e.g. principal arrears above X zł, or two full periods) and apply it identically to everyone. Selective collection breeds conflict and accusations of unequal treatment.
Stage 1 — a reminder
Short, polite, cost-free: e-mail, SMS or an in-app notification. A large share of arrears is simple oversight — a reminder 7–14 days past the due date settles it without souring the relationship.
Stage 2 — a demand letter
A letter with specifics: the principal (broken down by periods), interest as of the letter date, a payment deadline, the account number and a note on next steps. Send it by registered mail (ideally with return receipt) to the owner’s correspondence address and keep the proof of posting. An advised-but-uncollected letter matters too — document the advice-note and return dates.
Stage 3 — a final demand
The same, with the stakes raised: an announcement that the case will go to court and possibly to the debt register. If the community’s policy provides for demand-letter fees, charge them per the policy and show them in the letter.
The alternative — an installment agreement
When the debtor wants to pay, installments are usually faster and cheaper than court. Put the schedule in writing (amounts, dates, consequences of default), watch the payments, and react to the first missed installment. Include a clause that default makes the whole balance immediately due.
Stage 4 — the debt register and court
Registering a consumer debtor with a Polish debt register (BIG) requires, jointly: a debt of at least 200 zł, overdue for at least 30 days, and a demand letter with a registration warning, at least 30 days after its delivery (or advice note). In parallel or instead — a payment claim: for straightforward cases the electronic writ-of-payment procedure (e-court, EPU) works well. For the claim you need the full set: the fee resolutions, the charges, the demand letters with delivery proofs, and the interest calculations.
04What to document — the cheat sheet
| Item | Document / proof | Why |
|---|---|---|
| Fee amounts | resolution + proof owners were notified | the basis for charges |
| Charges | statement per unit and period | the principal for the claim |
| Payments | bank statement + allocation method | a balance that survives objections |
| Interest | calculation with rate sub-periods | the interest claim |
| Demand letters | letter text + proof of posting/delivery | debt-register precondition, credibility in court |
| Agreement | signed schedule + installment history | enforceability of the settlement |
05The most common mistakes
- Case-by-case collection — no thresholds or deadlines in a written policy; decisions driven by emotion.
- Thresholds computed on the total including interest instead of the principal — inflates arrears status and skews the statistics.
- No delivery trail — a demand “sent by e-mail, probably arrived” will not satisfy the debt-register precondition.
- Balances kept by hand in Excel — one typo and the unit’s whole history must be reconstructed from scratch.
- Delay — the older the debt, the worse the recovery. A procedure that starts automatically doesn’t “forget” any unit.
This entire procedure — on autopilot
The Finance module watches the thresholds, computes statutory interest with a full calculation trail, generates demand letters as PDFs, records deliveries, runs installment agreements and blocks a premature debt-register entry. The board only approves each step.
Explore the Finance module (PL)