Skip to documentation
OneClickRooms Documentation OneClickRooms School ERP
Academic Operations

Create and manage school events, RSVPs, and payments

School ERP is the school management product in OneClickRooms Education ERP Solutions. The other product is Higher Education ERP.

Follow a school event from audience setup and invitation through student decisions, invoices, payment, reporting, and post-event feedback.

Portal path Sign in Academic or Campus Administration Event Management My Tasks My Events My Finances

School ERP supports campus-wide and class-wide events. A Campus Admin creates a General campus-wide event. A Coordinator creates an Academic class-wide event for the selected campus, Board, and Class. School ERP does not use Programmes.

Workflow at a glance: configure an event type → publish the event → queue invitations and show the My Events unread badge → record the student's decision → create an invoice when the fee rules require it → record and verify payment → complete the event, report results, and add feedback. The class-level event role is called Coordinator in School ERP.

Before you begin

  • Confirm the campus and class audience, mandatory-attendance setting, event time zone, and fee before publishing.
  • For paid events, check the campus Event Fee tax application before invoices are created.

Follow the event from setup through completion

  1. Configure the event type

    An authorized settings administrator opens System Settings > Event Types and selects New Event Type. Enter its name, choose Academic or General, choose the matching Class-wide or Campus-wide scope, select the campuses where it may be used, and optionally set a default fee per student. Academic types are class-wide; General types are campus-wide. Leave the default fee blank when the creator should set it for each event.

  2. Create the event and choose its audience

    A Coordinator opens Academic > Event Management for a class-wide event. A Campus Admin opens Event Management for an assigned campus to create a campus-wide event. Select New Event, choose the campus, then choose the Board and Class for an Academic event. A General event uses the selected campus and has no Board or Class selector. School ERP does not use Programmes.

  3. Enter the schedule and event details

    Choose an eligible event type, enter the event name, select the start and end dates with the date-range field, and add the location and description. Times may be left blank; if you enter one time, enter both start and end times. Attach supporting documents if needed. Dates follow the institution's configured date format.

  4. Set attendance and fee details

    For mandatory attendance, every student in the saved audience is marked Required and cannot submit an RSVP decision. For non-mandatory attendance, students start Pending and can decide in My Events. Carries Marks and Maximum Marks are event metadata; they do not create a marks-entry workflow. Set or confirm the per-student fee; enter zero for a free event.

  5. Publish and notify the audience

    Saving publishes the event and snapshots the eligible students. The system queues invitations for students and available linked-parent email addresses, with event details and a calendar invitation attachment. The event appears with an unread badge at Hamburger menu > My Tasks > My Events. Queueing an email does not prove inbox delivery.

  6. Student acknowledges and records a decision

    The student opens My Tasks > My Events. Acknowledge marks the event as read and clears its unread badge; it is separate from the attendance decision. For a non-mandatory event, select Make Decision and choose I will attend or I'm not interested. Each choice opens a final Yes/No confirmation. For I will attend, the confirmation explains that Yes will create an invoice on a paid event; Yes records Interested and creates an invoice only if the event has a fee, while No leaves the decision unchanged. Confirming I'm not interested records Not Interested and creates no invoice; selecting No cancels. Revert decision returns Not Interested to Pending so the student can choose again before the decision window closes.

  7. Create an invoice when required

    For a newly created mandatory event with a fee, an individual invoice is created for every eligible student when the event is saved. For a newly created non-mandatory event, Pending and Not Interested responses have no invoice. Only after the student confirms I will attend does the system create that student's event invoice and queue its invoice email. Free events create no event-fee invoice. This policy does not rewrite invoices for older events.

  8. Pay and verify the invoice

    The student reviews the event invoice in My Finances and follows the school's payment instructions. If the payment workflow requests evidence, submit it for Finance review. Finance verifies or records the payment; the invoice and student finance record update, and a receipt is available in My Finances. A submitted but unverified payment remains pending.

  9. Review the roster and send the attendance report

    In Event Management, open the event three-dot menu and select Student attendance. The large attendance modal shows event details, attendance counts, a green Total collected badge, and a student table with profile pictures, decisions, and payment statuses. Selecting a student picture opens the person information card. Email attendance report queues the current report for the event owner; an automatic report is also queued after the event ends.

  10. Complete the event and add feedback

    After the event end date, My Events marks the event Completed and Coordinator Feedback becomes available from its three-dot menu. The Coordinator can enter student-specific remarks and upload one picture. A first feedback submission can queue an email notice to the student and linked parent. There is no separate staff Finalize Event button.

Keep decisions, payment, and check-in distinct

Acknowledge clears the unread badge. Make Decision records the student's RSVP and may create an invoice. Payment records the financial transaction; none of these actions verifies on-site attendance.

Decision and payment statuses

  • Pending means the student has not decided. Payment status is also Pending, and no invoice exists yet for an optional event. Do not interpret Pending as Not attending.
  • Not Interested means the student declined. No event invoice is created and payment status is Not attending.
  • Interested on a paid optional event creates an individual invoice. Payment remains Pending until the charge is fully paid and recorded, then shows Paid.
  • Required on a paid mandatory event has an invoice from event creation. Free events have no event-fee invoice.
  • The RSVP-based invoice rule applies to newly created events and leaves invoices already posted for older events unchanged.

Decision cutoff and event completion

Students can make or revert an eligible decision until two hours after the event's local start time. If no start time was entered, the cutoff uses 09:00 local time, so decisions lock at 11:00 on the start date.

The event is shown as Completed after its end date. Feedback becomes available after the end date. An RSVP, a payment, and the owner report do not verify on-site attendance.

Attendance report and collected amount

Starting at 08:00 local time on the day after the event end date, the system queues a detailed report to the event owner. It includes the roster, Required/Interested/Not Interested/Pending totals, paid attendees, students who are attending with payment pending, and the amount collected from recorded event payments.

The report reflects RSVP decisions and recorded payments, not physical check-in. Staff can also queue a current report from the attendance modal. Automatic email requires a valid event-owner email address.

Payment reminder

On the local calendar day before the event, starting at 08:00, the system queues a reminder to students who confirmed Interested and still have an outstanding event balance. The reminder directs them to My Finances.

Event fee and tax setup

The event-type fee is a default per student, not a total for the whole class. If no default is set, the Coordinator or Campus Admin enters the amount during event creation. Each Required or Interested student charge is an individual invoice when the attendance and fee rules call for one.

Tax is configured separately under System Settings > Taxes > Tax Applications. Apply the required tax to the Event Fee fee type for the correct campus and effective period. Event creation has no tax picker; the campus fee-type tax application determines the tax on the invoice.

Email and calendar invitations

The invitation includes an .ics calendar attachment. Gmail and Outlook may present calendar actions differently; downloading or importing the file adds a calendar copy. Calendar controls in an email do not replace the in-portal Make Decision action, which records Interested/Not Interested and controls optional-event invoice creation.

Linked parents may receive event or invoice messages when the student-parent link and an email address are available. Email queueing does not prove delivery. Check later school messages if the event changes or is cancelled.

Who is included?

  • A class-wide event is for students in the selected campus, Board, and Class.
  • A campus-wide event is for the selected campus and does not require a Board or Class.
  • A linked parent can receive a copy of the student's invitation or invoice email when the student-parent link and email address are available.

Coordinator Feedback

The event three-dot menu shows Coordinator Feedback after the event end date. Use it for post-event comments, not attendance check-in. The Coordinator can add remarks and a picture for a student; the first feedback submission can notify the student and linked parent.

If an event or invoice is missing

  • Check the student's active campus and class against the event audience, and confirm the event was saved.
  • For a class-wide event, confirm that the selected Board and Class match the student roster.
  • Check that the event type has the Academic or General category and scope needed for the intended creator.
  • For an unpaid or pending invoice, review My Finances and contact Finance to confirm whether payment has been recorded or evidence verified.

Active status controls event audiences

New event audiences include active students in the selected campus and, for class-wide events, the selected Board and Class. Suspended, inactive, and graduated students are excluded from new invitations and feedback choices. The server checks audience eligibility when an event is saved and when a student is selected for feedback; changing the visible page cannot add a former student. This eligibility rule is enforced within School ERP and its own student records.

Recommended next step

For student invoices and evidence, see Student fees and payments and Payment evidence and receipts.