One family view
Guardians can switch between linked children while finance retains student-level fee lines and payment history.
Workflow journey
Fees to receipt
Configure fee structures, generate installments, collect online or counter payments, and give families a receipt that finance can reconcile. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
A useful page should answer the next operational question
Configure fee structures, generate installments, collect online or counter payments, and give families a receipt that finance can reconcile.
Who this is for
- Bursars
- Finance teams
- Parents
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Structure
Define fee heads, class rules, concessions, tax settings, and installment dates.
- 02
Generate
Create fee instances for the active academic year and review exceptions before publishing.
- 03
Collect
Families pay online or through the office while finance monitors outstanding balances.
- 04
Reconcile
A PDF receipt and ledger entry close the loop for the family and the bursar.
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Available now
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Bursars
- Finance teams
- Parents
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Boundaries to confirm
Gateway, SMTP, tax, and scheduled dunning settings require deployment-specific validation before go-live.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can siblings share one parent login?+
Yes. The parent dashboard can show linked children while balances remain separated by student.
What does finance receive after payment?+
The workflow provides payment history and receipt output for the same fee instance the family paid.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Fee-only tools vs a connected school SMS
Decide whether fee collection alone is enough or whether finance should share student, family, calendar, and reporting context.
Read the pagePayment and email readiness
Validate gateways, receipts, SMTP, scheduled reminders, failure handling, and support ownership before collecting real fees.
Read the page
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in