If your payment setup feels messy, the problem is usually profile design, not staff effort. Payment profiles are where you define how money should move for each class type. This page gives you a practical way to design profiles that survive real term pressure, including mixed child and adult provision. It is written for UK studios where Direct Debit timing and card fallback questions arrive every week.
Start with a profile design checklist
Before creating or editing profiles, answer these six questions:
- Is this profile for full-term, single-class, or both?
- Do we need card, Direct Debit, or both methods?
- Are we collecting upfront or in instalments?
- What proration logic should apply if enrolment starts late?
- Who absorbs processing fees?
- How should receipts be handled?
If you cannot answer all six clearly, pause and agree billing policy first.
The fields that matter most in day-to-day operations
Usage scope
Usage scope controls where a profile can be applied:
- full term only
- single class only
- both
Pick one based on delivery pattern, not convenience.
Allowed methods
Allowed methods can be:
- card only
- direct debit only
- card or direct debit
Important rule: single-class enrolments need card-capable methods. A direct-debit-only profile is not valid for single-class enrolment type.
Deadline days
This sets payment deadline timing for schedule generation context. Keep it aligned with how you explain due dates to parents.
Installment anchor and count
For term plans, choose whether instalments anchor to term start, approval date, or enrolment start. Then set installment count where needed.
Proration strategy
Choose by sessions, by weeks, or by days. Keep this consistent across full-term profiles assigned to the same class group, because Classia enforces consistency there.
Fee handling and receipt policy
Decide whether account bears fee or payer absorbs fee. Decide whether receipts are always sent, never sent, or payer choice.
These two fields affect parent trust quickly. Keep wording clear.
Profile patterns that work in UK studios
Pattern A: term Direct Debit with card fallback
- usage scope: both
- allowed methods: card or direct debit
- installment count: 1 or staged by term preference
- fee handling: account bears fee (or clear payer rule)
Useful when families want flexible method choice.
Pattern B: single-class card-only drop-in
- usage scope: single class only
- allowed methods: card
- no complex instalment expectations
Useful for workshops, tasters, and occasional attendance.
Pattern C: full-term only conservative plan
- usage scope: full term only
- method based on studio policy
- clear deadlines and proration
Useful for structured programmes with steady attendance.
Assignment at class level: where profile design becomes real
A profile does nothing until it is assigned to classes. In class setup, add the profile under Payment profiles and make sure class prices are set for term and/or single class as needed.
Quick class-level check:
- term price present where full-term enrolment is offered
- single-class price present where one-off booking is offered
- assigned profiles match class offer and method expectations
If class pricing and profile scope do not align, approval-time billing will be noisy.
Examples
Example: Dance school with 12 Saturday trial places
The school used one broad profile for every class. Single-class trial requests failed when method choice did not fit. They split profiles into a card-first single-class profile and a mixed method term profile.
Fewer step-four enrolment drop-offs.
Example: Martial arts club with 7 classes and mixed fee expectations
Parents were surprised by processing fees in one class but not another. The club standardised fee handling rules and updated profile names to match policy.
Fewer billing disputes and clearer front-desk scripts.
Example: Tuition centre with 63 pupils and late joiners
Different profiles on the same class used different proration logic. Calculations became hard to explain. They aligned full-term profile proration for each class group.
Clearer due-item calculations and fewer manual corrections.
Naming profiles so staff can choose correctly
Avoid vague names like "Default" or "Plan A". Use names that describe method and scope.
Good examples:
- "Term plan - Direct Debit/Card"
- "Single class - Card"
- "Term upfront - Card only"
When names are clear, admin errors drop without extra training.
Related feature
Related guides
- Payments and billing (UK)
- Schedules, due items, arrears, and offline payments
- Payment checkout and verification issues
Avoid these slips
1. Using one profile for everything
This usually hides real billing differences and causes avoidable exceptions.
2. Assigning direct-debit-only profile to single-class expectations
Single-class enrolments need card-capable methods.
3. Leaving profile names vague
Staff choose the wrong profile when options are unclear.
4. Changing fee handling without updating communication
Parents then challenge charges they did not expect.
5. Mixing full-term proration strategies on one class group
Classia blocks this for good reason: conflicting calculations are hard to trust.
FAQ
How many profiles should a small studio start with?
Usually two to four clear profiles are enough for a first clean setup.
Can we deactivate a profile without deleting history?
Yes. Marking inactive is usually safer than deleting when records already depend on it.
Should we create separate profiles per class?
Only when policy really differs. Over-fragmented profiles are harder to maintain.
What does installment count do when left blank?
Term plans effectively behave as upfront where instalments are not explicitly configured.
Can profile fee policy change mid-term?
Technically yes, but plan and communicate changes carefully to avoid parent confusion.
Which page should we read next?
Read Schedules, due items, arrears, and offline payments to run collection week to week.
Related guides
- Payments and billing (UK)
- Schedules, due items, arrears, and offline payments
- Payment checkout and verification issues
Avoid these slips
1. Using one profile for everything
This usually hides real billing differences and causes avoidable exceptions.
2. Assigning direct-debit-only profile to single-class expectations
Single-class enrolments need card-capable methods.
3. Leaving profile names vague
Staff choose the wrong profile when options are unclear.
4. Changing fee handling without updating communication
Parents then challenge charges they did not expect.
5. Mixing full-term proration strategies on one class group
Classia blocks this for good reason: conflicting calculations are hard to trust.