Feature identity
Receipt Generation
An illustration, not a screenshot. The interactive example below shows what this capability actually does.
Sequential shareable receipts
Fee receipt output. Rendered by the shipped receipt PDF renderer from fictional invoice and collection records.
Recorded collection proof · Sample
Receipt output remains tied to the recorded collection
Product scope
Every payment mints a sequential receipt number (RCP0001…) from one atomic per-school register — gap-free on rollback, never burned by a webhook retry — and renders a branded PDF shared over WhatsApp and email at pay time. Re-download any past receipt with a DUPLICATE watermark; the Receipt Builder customises masthead, signatories and declarations.
The school problem
School teams need a dependable way to handle Receipt Generation: Sequential shareable receipts. The required records, assigned roles and review boundary must remain explicit.
Day-to-day work
Sequential shareable receipts.
Operational result
Sequential branded receipts tied to recorded payment evidence, with controlled reprints and tax breakup where applicable.
Access and ownership
What each person can actually see depends on the role you give them and which classes or records you assign.
Availability and setup
Finance catalogue capability
Connected operating context
These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.
Buyer questions
The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.
Fee Collection, Payment Gateway, Export PDF, Accounting Reports are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.
Recorded payment evidence and receipt-template configuration. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.
No AI capability is asserted for Receipt Generation. Its documented work remains controlled by school records, roles and permissions.
Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.
Related evaluation guides
See it in your school context
See how this workflow fits your school's current records, roles, plan and rollout requirements.