Payment reconciliation means matching incoming payments to the invoices they pay and updating each balance. Match bank transfers by invoice reference first; otherwise use exact amount, currency and payer name, assigning a payment only when the match is unambiguous and keeping uncertain payments in a review queue.
What is payment reconciliation for an academy?
Payment reconciliation connects money received with tuition charged. An invoice tells you what a family owes; a payment record tells you what arrived. Reconciliation connects those records so the remaining balance reflects actual receipts. Money in your account is not enough evidence to mark a particular invoice paid: you also need a defensible link between the payment and that invoice.
Keep the original payment identifier, date, amount, currency and available payer details. Record the invoice allocation alongside that evidence. A note saying “parent paid” is hard to check later because the note does not identify the transaction.
Keep invoice corrections separate from payment matching. If a class was charged incorrectly, resolve the charge. Moving an unrelated receipt onto the invoice hides the original problem and makes the next review harder.
Why are bank transfers harder to match than card payments?
Bank transfers can arrive separately from the invoice that prompted them. A parent may send money from another person’s account, omit the reference or pay a different amount. A payment attached to a provider’s invoice already has an invoice connection. A plain transfer needs evidence that connects the bank entry to the family and the charge.
The distinction is about the payment route. A bank transfer can still be reconciled automatically when the invoice provider supports that route, as Stripe says its invoicing service does for ACH credit and wire transfers.
According to Wise (wise.com)‘s invoice help page, checked 21 October 2026, business invoices can include a payment link and local account details, including the reference you set. Clear instructions give you better evidence when the money arrives.
Keep payment instructions beside the amount due. Use invoice references that match rather than asking families to invent their own descriptions. Keep the same reference visible wherever the family checks the invoice.
In what order should you match references, amounts and names?
Match the strongest evidence first: a recognizable invoice reference, checked against the currency and outstanding balance. Without a usable reference, require the exact amount, the same currency and a payer name that identifies an open invoice unambiguously. An amount alone is weak evidence because families can owe identical amounts. A familiar name alone does not identify the billing period.
Use a consistent review order:
- Check whether the payment already exists in the ledger.
- Read the reference and locate the invoice it names.
- Confirm the currency and compare the payment with the unpaid balance.
- Without a usable reference, check exact amount, currency and payer name together.
- Hold competing matches or conflicting details for review.
When a match is unclear, ask the family which invoice the transfer covers. Save the answer with the payment record so another admin can understand the decision.
For Halqora’s incoming Wise (wise.com) matching, a reference-based payment must not exceed the invoice balance. A smaller payment can match as a part payment when the candidate is unambiguous. Wrong-currency and overpayment candidates need review.
What does each payment channel give you to match?
| Payment channel | Invoice ID attached automatically? | Payer reference available? | Payer name available? | Typical matching method | Automation level |
|---|---|---|---|---|---|
| Stripe invoice | Yes, through the provider invoice | Depends on payment route | Depends on returned details | Read payment status and amount against the stored invoice | Automatic |
| PayPal invoice | Yes, through the provider invoice | Depends on payment record | Depends on returned details | Read invoice payments against the stored invoice | Automatic |
| Mercury invoice | Yes, through the provider invoice | Not needed for status matching | Not needed for status matching | Read paid status for the USD invoice | Automatic |
| Wise (wise.com) incoming transfer | No attached academy invoice ID | When returned by the provider | When returned by the provider | Reference, otherwise exact amount, currency and name | Rule-based |
| Plain bank transfer | No guaranteed invoice connection | Check the bank entry | Check the bank entry | Review bank evidence against open invoices | Manual |
| Cash/manual | Recorded by the admin | Record the evidence supplied | Record who paid | Assign the receipt to the confirmed invoice | Manual |
Payment channels differ in how the invoice connection reaches your ledger. The table describes Halqora’s connected-provider workflow and a manual process for other receipts. Provider invoice status can identify the invoice directly; incoming transfer matching depends on the details returned. Missing payer information should reduce your confidence rather than encourage a looser matching rule.
Halqora’s Mercury sync is USD only. Halqora reads incoming Wise (wise.com) payments and matches them; Halqora does not create those payments. The Wise Business for academies guide covers the payment provider separately.
How should you handle partial payments, overpayments and sibling payments?
Partial payments should reduce the invoice balance without making the invoice appear fully paid. Overpayments need a decision about the excess before you close the review item. A transfer for siblings needs either a shared family invoice or confirmed allocations across separate invoices. Keep the received amount visible throughout the process so allocations do not create extra money on paper.
Use these checks for exceptions:
- For a partial payment, preserve the unpaid balance and the original receipt.
- For an overpayment, confirm the family’s intention before deciding how to handle the excess.
- For sibling payments, confirm whether the transfer covers a shared invoice or separate invoices.
Halqora supports siblings sharing a family invoice for separate one-to-one classes. Halqora does not have a stored credit wallet. Do not describe an excess payment as an available wallet balance.
Keep currencies separate. Halqora gives each student a currency and does not convert invoices or accept a payment in another currency against them. Approximate USD dashboard totals are unsuitable for deciding whether a specific invoice is settled.
How do you prevent double counting?
Double counting happens when the same receipt becomes another payment record during a later import, provider update or manual review. Prevent duplication by keeping a stable transaction identifier and checking that identifier before adding money to the ledger. Calculate the invoice balance from recorded payments instead of repeatedly reducing a balance whenever an update arrives.
Halqora uses an idempotent ledger: processing the same provider payment again does not add the money again. Provider-prefixed identifiers let webhooks and daily sync recognize the same receipt.
Manual work needs the same discipline. Before entering a receipt by hand, check whether a connected provider already recorded it. Keep the provider transaction identifier with any review decision. A payment screenshot is supporting evidence; confirm the receipt before recording money as received.
What should a weekly reconciliation routine include?
A weekly reconciliation routine should clear ambiguous receipts, verify outstanding balances and leave a record of unresolved questions. Automatic matching reduces the transactions you inspect, but the review queue still needs an owner. Finish the review before chasing families so your reminder list reflects payments already received and assigned to the correct invoices.
- Check connected-provider sync errors and confirm the relevant payment records are available.
- Review unmatched receipts against references, names, currencies and balances.
- Ask families about ambiguous payments and record the evidence received.
- Check partial payments, excess amounts and sibling allocations.
- Review overdue invoices after assigning confirmed receipts.
- Leave a clear note for every unresolved payment, including the next action.
Use an accounts receivable aging routine to organize follow-up after reconciliation. Keep “money not received” separate from “money received but not assigned.” The family conversation differs, and the admin should know which problem needs solving.
How Halqora handles this
Halqora is management software for online academies. Its automatic payment matching reads payments from PayPal, Stripe, Mercury and Wise (wise.com), without an accounting add-on for incoming international transfers.
Wise (wise.com) matching checks the invoice reference first, with matching currency and an amount no greater than the balance. Otherwise, exact amount, currency and payer-name evidence must identify an invoice unambiguously. Unclear candidates enter a queue for assignment or dismissal. The idempotent ledger prevents repeat updates from adding duplicate payments.
Billing runs create draft invoices for admin review and sending. Payment matching updates balances afterward.
Sources
- Stripe Invoicing pricing and bank-transfer reconciliation, checked 21 October 2026
- PayPal Invoicing API documentation, checked 21 October 2026
- Wise (wise.com) help: get paid by invoice, checked 21 October 2026
