Come to this page when week-to-week billing work gets squeezed between classes. It explains how to manage due items, arrears, and offline payments in Classia without losing track of what is actually owed. The focus is practical UK studio operations where parents pay by mixed methods and admins need reliable records by the end of each day. If your current process still depends on separate spreadsheets, this page helps you move that control into one place.
Common mistake first: waiting until month end to check due items
By the time many studios look at arrears, they are already handling parent complaints and class-level confusion. Classia is built for continuous control, not month-end firefighting. This guide shows how to manage due items, overdue states, and offline payments in small weekly blocks. It is practical and built around the actual behaviour of schedule and payment records.
How the schedule model works in plain terms
A payment schedule is the overall plan for one payer. Inside it sit payment schedule items with specific due dates, amounts, and statuses.
You will usually see these item statuses:
- due
- paid
- overdue
- void
Schedule status then reflects the item mix:
- overdue items present -> schedule overdue
- due items present -> schedule active
- no due/overdue items left -> schedule completed
This means item quality drives schedule quality.
Daily due-item triage in 20 minutes
Use this order for quick control:
- review due today and already overdue items
- check upcoming items for high-risk classes
- verify offline entries from the last 24 hours
- assign contact follow-up on unresolved arrears
This is faster than large weekly catch-up because context is still fresh.
Why checkout may not include all unpaid items
Classia checkout targets the next due-date group for a schedule, not every future item in one go. That keeps collection focused and clearer for payers.
If staff expect one checkout to settle the whole term, explain this rule upfront. It prevents repeated "why didn't it take everything?" support messages.
Using offline payment recording correctly
For due or overdue items, staff can use "Mark paid offline" and select method:
- cash
- card (offline)
- bank transfer
- other
Always add a short internal note when context might be queried later.
Exact amount paid
Item moves to paid and allocation is recorded.
Underpayment
Item is split: paid amount is recorded, and a new adjustment due item is created for remaining balance.
Overpayment
Due item is paid, and the excess is added to credit balance for future application.
This is much safer than editing amounts manually in spreadsheets.
Arrears handling pattern that keeps trust
When arrears appear, work to a repeatable script.
- confirm item status and due date
- confirm whether any payment attempt exists
- send clear message with exact amount and next step
- log outcome and review in next arrears block
Do not send broad "you are overdue" messages with no dates or amounts. Specificity reduces conflict.
UK language for arrears conversations
Use practical wording:
- "This item was due on 4 November and remains unpaid."
- "Amount outstanding is GBP42.00 for this due item."
- "If you have paid by bank transfer, please share the reference so we can match it."
If Direct Debit was expected, be explicit about submission and bank timing before treating it as missed.
Payment flow diagram (structured text asset hook)
Second diagram-ready version focused on arrears and reconciliation:
- Input: schedule with due items sorted by due date.
- Branch A (online): launch checkout for next due-date group -> webhook success marks item paid -> schedule status refresh.
- Branch B (offline exact): record offline payment -> item paid -> schedule status refresh.
- Branch C (offline underpayment): record payment -> split line items proportionally -> create adjustment due item -> schedule status refresh.
- Branch D (offline overpayment): record payment -> item paid -> add credit balance -> next checkout applies credit automatically.
- Branch E (refund/dispute): webhook updates payment state -> affected items returned to due/overdue path.
This text can be turned into a swimlane diagram later.
Examples
Example: Dance school with reception cash payments
Three families paid cash after class. Admin logged each offline payment same evening with note and method.
No "we already paid" dispute at end of week.
Example: Martial arts club with partial bank transfer
A parent transferred GBP25 against a GBP40 due item. Staff recorded offline underpayment. Classia created adjustment for remaining GBP15.
Shortfall stayed visible and traceable.
Example: Swim school with accidental overpayment
A family paid one extra lane fee in error. Offline record captured full amount, and excess moved to credit balance.
Next due item reduced automatically, with no manual spreadsheet credit ledger.
Safeguarding and role control in payment operations
Where child records are involved, keep payment updates within authorised roles and account scope. Payment notes should be factual and minimal. Do not include unnecessary child-sensitive details in payment notes or email summaries.
A calm rule: enough detail to reconcile, not enough detail to expose.
Related feature
Related guides
- Payments and billing (UK)
- Payment profiles: Direct Debit and card
- Payment checkout and verification issues
Avoid these slips
1. Marking payments offline without method context
You lose reconciliation clarity when disputes appear.
2. Ignoring underpayments after they are recorded
Adjustment items still need active follow-up.
3. Treating all overdue items as the same problem
Some are timing issues, some are true arrears, and each needs different communication.
4. Delaying arrears checks until the end of term
Small overdue items become large backlog quickly.
5. Using spreadsheet edits to "fix" schedule mismatches
This breaks trust in the live schedule data.
FAQ
Can upcoming items be marked paid offline early?
Operationally, due and overdue item flows are the intended offline payment path.
Where should arrears owners look first each morning?
Start with due and overdue items sorted by due date and class concentration.
Does offline payment change schedule totals automatically?
Yes, schedule totals and status are refreshed as part of offline recording flow.
What if checkout says no payment is currently due?
It usually means no due items exist for the next due-date group at that moment.
Should we keep separate offline ledgers outside Classia?
Only for temporary migration support. Day-to-day live tracking should stay in Classia.
Which page should we read next?
Read Payment checkout and verification issues for diagnosis patterns when payment attempts fail.
Related guides
- Payments and billing (UK)
- Payment profiles: Direct Debit and card
- Payment checkout and verification issues
Avoid these slips
1. Marking payments offline without method context
You lose reconciliation clarity when disputes appear.
2. Ignoring underpayments after they are recorded
Adjustment items still need active follow-up.
3. Treating all overdue items as the same problem
Some are timing issues, some are true arrears, and each needs different communication.
4. Delaying arrears checks until the end of term
Small overdue items become large backlog quickly.
5. Using spreadsheet edits to "fix" schedule mismatches
This breaks trust in the live schedule data.