A bank statement full of strangers
Upfront rent from international students arrives in lumps in the summer. The bank statement shows a transfer from a company you have never heard of, a payment from a parent with a different surname, and three amounts that are slightly less than any instalment on your system. The reference field says "ROOM" or a string of numbers from a foreign bank.
Your finance assistant has a spreadsheet of unmatched receipts. Meanwhile the student emails asking why they still have a payment reminder when their father paid a month ago.
Why the payments do not reconcile
The payment leaves the student's world through systems you do not control: a parent's bank, an international payment platform, an education agent, a sponsor. Each strips or changes the reference. Currency conversion and intermediary bank charges mean the amount that lands is not the amount due.
- The payer name is a parent, sponsor, agent or payment company, not the student.
- The reference is missing, truncated or mistyped.
- Amounts arrive short because of fees charged along the way.
- One transfer covers several students, for example siblings or an agent's group.
- Receipts through a payment platform land as one daily settlement, not one line per student.
What unmatched money costs
Students who have paid get chased, which is embarrassing for you and upsetting for them. Students who have not paid are hidden among those who have, so real arrears are found late. Finance spends days on detective work, and the rent ledger in the booking system is wrong until they finish. Short payments add up quietly because nobody decides whether to chase the difference or write it off.
The matching process we build
- Receipts are read from your bank feed, through Open Banking or your accounting software such as Xero, and from any payment platform you use, including the detail behind each settlement.
- Each booking's expected payments are read from your booking system: amounts, due dates and the student and guarantor details.
- Every receipt is scored against expected payments by reference, amount within a tolerance you set, payer name compared with student, guarantor and known agents, and date.
- Confident matches are applied and the student's balance is updated in your booking system where it allows.
- Short payments inside your tolerance are matched and flagged for your write-off or chase rule. Larger gaps go to a person.
- Anything uncertain goes to a queue showing the receipt and the two or three most likely bookings, so the decision takes seconds.
- Payer names confirmed by a person are remembered, so next time a transfer from that parent or agent matches on its own.
| Receipt looks like | What happens |
|---|---|
| Correct reference, correct amount | Matched and applied |
| Parent's name, amount matches one booking | Suggested match, one-click confirm |
| Amount a little short | Matched, shortfall flagged under your rule |
| One transfer for several students | Split suggested for a person to approve |
| No plausible booking | Held with the payer details for follow-up |
How you treat shortfalls and bank charges is your finance team's decision. We apply the rule you set.
A ledger you can trust in August
Most receipts match on the day they arrive. The finance assistant works through a short queue instead of a long spreadsheet. Payment reminders go only to students who genuinely owe money, and the arrears list is accurate enough to act on. Agents who pay for groups can be sent a statement showing exactly which students their transfer covered.
Is this what your receipts look like?
- Many summer receipts come from parents, sponsors or agents.
- References are missing or mistyped more often than not.
- Students get reminders for rent they have already paid.
- Small shortfalls are left sitting on accounts.
- Matching international payments takes someone days each summer.