Never test only the button
A successful checkout is not complete until the ledger, receipt, notification, and support trail agree.
Implementation guide
Payment and email readiness
Validate gateways, receipts, SMTP, scheduled reminders, failure handling, and support ownership before collecting real fees. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
Match modules to your board, size, and priorities.
Product screenshots
The Schoolyi screen for this work
Captured from a demo school, at a size search engines can fetch. Open the module for the rest of the workflow.
At a glance
A useful page should answer the next operational question
Validate gateways, receipts, SMTP, scheduled reminders, failure handling, and support ownership before collecting real fees.
Who this is for
- Finance teams
- IT coordinators
- School leadership
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
Configure
Set gateway, currency, tax, sender, domain, receipt, and environment values for the target deployment.
- 02
Test success
Run a payment, verify the fee state, receipt PDF, email delivery, and family history.
- 03
Test failure
Rehearse timeout, duplicate attempt, declined payment, missing email, and reconciliation cases.
- 04
Operate
Assign who monitors scheduled jobs, gateway callbacks, mail delivery, and parent support.
Practical artifact
Leave with something your team can use
Copy these checkpoints into a kickoff, vendor demo, or readiness review.
- Sandbox payment script
- SMTP delivery test
- Webhook/reconciliation checklist
- Incident owner map
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.
Validate for your rollout
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
- Finance teams
- IT coordinators
- School leadership
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Environment boundary
Simulated and live payment behavior must be clearly labelled so test transactions never masquerade as collections.
Reconcile the whole chain
Record the gateway response, fee state, receipt, email result, webhook or dead-letter outcome, and family history for both a success and a failure.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can we go live without SMTP?+
Do not promise receipt or reminder email until the sender, domain, and delivery path are tested in the deployment.
Validate credentials, permissions, and failure handling in a non-production environment before connecting live school records. Assign an owner for monitoring the handoff after launch.
Who owns failed payments?+
Name a finance owner and an IT owner; families should receive a clear next step rather than a generic error.
Before the first collection cycle, reconcile one paid, partially paid, and overdue student account so the family receipt and finance view agree. Keep any tax, gateway, refund, or accounting boundary as an explicit deployment decision.
Does the readiness page prove a live gateway is configured?+
No. It is a test plan. The target deployment must still provide and verify its own gateway, sender, webhook, and reconciliation settings.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Fees to receipt
Configure fee structures, generate installments, collect online or counter payments, and give families a receipt that finance can reconcile.
Read the pageAvailability and support
What the product gives you for monitoring and scheduled jobs, which of those jobs you must wire up yourself, and why there is no uptime figure on this page.
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