Bank Integration and Service-Charge Reconciliation: How Do Transfers Get Matched?

Maintenance-fee reconciliation is the process of identifying which unit and which debt each bank transfer and EFT received into the management account belongs to, then closing it in the records. Bank integration reads account transactions automatically and, by checking the amount, description, sender name and the sender's IBAN history, suggests a match for every payment. The manager makes the final call; an approved payment closes the debt and generates a receipt.

In this article we explain why reconciliation falls short when done by hand, what authority the bank integration uses to connect to the account, which clues are used for matching, and how overpayments, underpayments and unrecognised payments are handled. We covered the card payment side separately in our article on online service-charge collection.

What is maintenance fee reconciliation and why does it matter?

Reconciliation is the process of verifying that two records agree with each other. For maintenance fees, those two records are the bank statement and the resident ledger. If the bank shows 240,000 TL collected but only 228,000 TL of debt has been closed in the ledger, the 12,000 TL difference is either unmatched transfers or payments posted to the wrong unit.

When reconciliation breaks down, the consequences cascade. A resident who has already paid receives a payment reminder, late fees are applied to the wrong person, the aged receivables report no longer reflects reality, and the debt statement that could end up in legal collection proceedings becomes disputed. For a management team that doesn't reconcile monthly, presenting a clean set of accounts to the auditor at year-end also becomes much harder.

Why doesn't manual matching from transfer descriptions work?

Manual reconciliation relies on residents writing a proper note in the reference, such as "Block A Apartment 7 October service charge". In the field, this assumption frequently breaks down. The most common situations are:

• Missing description. The description says only "maintenance fee" or nothing at all. Without a unit number, the payer can only be guessed from the sender's name.
• Bulk payment. A unit owner sends three months of maintenance fees in one transfer, or an owner with two units pays both units' balances as a single amount. One bank transaction must be split across several charges.
• Payment under a different name. The payment is made by the owner's spouse, child, tenant or company. The sender name at the bank doesn't match the owner name in the system.
• Partial payment. A 1,000 TL payment is sent against a 1,750 TL maintenance fee. The amount doesn't match any debt exactly.
• Incorrect information. Another unit's number is written in the description, or the block letter is left out.

Each of these situations is small on its own. But imagine a 240-unit compound receiving nearly two hundred bank transfers a month, each resolved in a minute or two by checking it against the statement and the debt list; the manager spends close to a full working day every month on matching alone. What's more, errors cluster in the first week of the month — exactly where fatigue makes them most likely.

How does bank integration work, and can it withdraw money from the account?

Bank integration automatically transfers transactions from the management's bank account into the compound management software. This connection is set up with read-only access. In Türkiye, this type of access is known as an account information service under Law No. 6493 on Payment and Securities Settlement Systems, Payment Services and Electronic Money Institutions, and is part of the open banking approach.

With the account information service, the software can view the account balance and transactions; sending money, issuing payment orders or changing account settings are not covered by this permission. Access begins with the approval the account holder gives through their bank, and the account holder can withdraw that approval. The connection may be established directly with some banks and through an integration infrastructure with others. From the manager's point of view there is no difference: transactions are pulled at set intervals or on demand, and the same transaction is never recorded twice.

Where integration isn't possible, a bank statement can also be uploaded to the system as a file. This route requires more manual work, but the matching suggestions work in exactly the same way.

Which signals are used to match bank transfers?

A good matching engine does not rely on a single clue; it weighs several signals together and shows why it suggested each unit. The table below summarizes the most-used signals and the weak point of each.

When signals reinforce each other, the suggestion becomes reliable. Even if the description is blank, if money equal to B-12's outstanding balance arrived from an IBAN previously used for B-12, the suggestion is very likely correct. Conversely, a suggestion that matches only on amount should be reviewed carefully; if hundreds of units share the same monthly maintenance fee, the amount alone tells you nothing.

Why should the manager still approve the match?

A match suggestion is an estimate. If the estimate turns out to be wrong, the wrong unit's debt is cleared and the actual debtor receives no reminder. That is why the manager's approval should be required before a suggestion is posted to the debt. The approval screen should show the transaction date, amount, description, sender details and the reasoning behind the suggestion all together.

Approval needs to be fast; opening a hundred transfers one by one is no better than matching them manually. A productive setup is to review and approve suggested matches with strong signals in bulk, while examining uncertain ones individually. An incorrectly approved match should be reversible, and that action should be logged.

How are overpayments, underpayments and unrecognized payments handled?

• Overpayment. If 3,500 TL is paid against a 1,750 TL debt, the outstanding debt is cleared first, the remaining amount is recorded as a credit (advance) on the payer's account and offset against the next month's maintenance fee. Leaving the excess sitting on the side creates an unexplained balance at period end.
• Underpayment. If 1,000 TL is paid against a 1,750 TL debt, the amount paid is deducted from the debt and 750 TL remains outstanding. Any late-payment rules set out in the operating budget or management plan apply to the remaining amount.
• Bulk payment. A single transfer is allocated across multiple charges; allocation usually starts with the oldest debt, and the receipt clearly shows which month the resident paid.
• Unrecognized payment. A transaction that no signal points to stays on the pending list. A short announcement to residents naming the sender, or asking the bank for the transfer details, is usually enough. Money that cannot be traced to anyone should not be recorded as income; track it as funds held in trust.
• Non-fee inflows. Parking income, cell-tower rent or transfers between the management's own accounts also land in the same account. These must not be matched against maintenance-fee debt; they should be posted to the relevant income line or recorded as a transfer.

How do you reconcile maintenance fees step by step?

1. Connect the account. Register the management's collection account in the system via the bank integration and grant read permission.
2. Pull transactions. Make sure transactions arrive at regular intervals; during busy periods such as the first week of the month, refresh them several times a day.
3. Generate suggestions. For unmatched incoming transfers, wait for the system to suggest the unit and debt, or start the process in bulk.
4. Approve high-confidence suggestions. Review and approve suggestions supported by multiple signals, such as IBAN history and unit number.
5. Review the uncertain ones. Check one by one any suggestions based only on amount or only on name; ask the resident if needed.
6. Record the exceptions. Post overpayments as credit, underpayments as partial collections, and non-fee receipts to the relevant income or transfer record.
7. Close at month end. Check that the bank balance matches the collections in the ledger; if no transactions are pending, consider the period reconciled.

The biggest gain from this workflow is that communication with residents is accurate. Sending debt reminders before reconciliation is complete upsets residents who have already paid; sending reminders after reconciliation largely solves this problem. For the legal process against non-payers, see our article on service-charge debt collection.

How does bank reconciliation work in Çözüm Hanem?

In Çözüm Hanem, the property's bank account transactions are pulled automatically using the account information service approach; the connection is established directly with some banks and through an integration infrastructure with others. On the Bank Reconciliation screen, incoming wire transfers and EFTs are suggested for matching to the relevant unit and debt based on the description, amount, IBAN and sender information. With “Bulk Match,” suggestions are generated for all unmatched transactions in a single pass. Suggestions are not posted to debts without manager approval; an approved collection closes the debt and generates a receipt. Alerts are shown for transactions awaiting a match.

Reconciliation works on the same ledger as cash and bank accounts, current account statements and aged receivables reports; a compound manager only sees transactions for their own compounds. To set up the bank integration and migrate your existing data, get in touch with us, and explore our other finance features on the features page.

Summary

• Maintenance fee reconciliation ensures that the bank statement and the resident ledger match; if it slips, reminders, late fees and enforcement records all go wrong.
• Manual matching takes time and is error-prone because of missing references, bulk payments, payments made under a different name and partial payments.
• Bank integration connects to the account with read-only access; it cannot withdraw money or issue payment orders.
• A match is suggested by evaluating the IBAN history, the unit number in the payment description, the sender's name and the amount together; approval stays with the manager.
• An overpayment is posted as a credit and an underpayment as a partial collection; an unrecognized payment is tracked in the pending list until it is identified.