Murouj Academy runs on Halqora and uses it daily. The central lesson for an online Quran academy is that schedules, class outcomes, invoices, and teacher pay need a shared class record so corrections stay connected.
Where do spreadsheets and chat start to strain?
Talt AI built Halqora around the practical jobs of running an online Quran academy: scheduling, class outcomes, invoices, and teacher pay. The useful lesson for another owner is the connection between those jobs: a changed lesson can affect the timetable, the family balance, and the teacher’s earnings.
A spreadsheet can hold a timetable clearly. A separate sheet can calculate a bill correctly. The difficulty comes when you need to know whether both sheets describe the same lesson after someone corrects an outcome.
Ask where your team records the final decision about a class. Then ask how that decision reaches the invoice and payroll. If the answer depends on someone remembering to copy a change, the process needs attention.
Use the signs your academy has outgrown spreadsheets to assess where your own workflow needs attention.
Why is a class time a place and a rule?
A recurring class needs a time zone as well as a clock time. If you save a fixed difference between countries, a clock change can make that difference wrong. Halqora stores scheduling rules in each IANA time zone. Admins see calendars in the academy’s zone, while teachers see their own zone. The examples below explain the scheduling problem; they are not accounts of incidents at any particular academy.
Example: a teacher’s lesson at 5 pm in Pakistan appears at 12 noon in the UK during winter and at 1 pm during British Summer Time. Pakistan remains 5 hours ahead in winter and 4 hours ahead during British Summer Time, as of 21 October 2026.
The important question is whose local time should stay fixed. A lesson anchored to the teacher’s Pakistan time has a different promise from a lesson anchored to the family’s UK time. Write that promise down before creating the recurring schedule.
Egypt adds another reason to use maintained time-zone rules. The IANA commentary records short-notice changes in 2014, 2015, and 2016. A permanent note saying “Cairo is this many hours ahead” cannot express a government changing the calendar rules.
Before a clock change, review affected recurring lessons and tell families the local time they should expect. When families and teachers follow different clock-change calendars, consult the explanation of the US-UK clock change gap weeks rather than relying on last month’s offset.
Why should invoices and pay use the same class outcome?
A class outcome should tell billing and payroll what happened without making either team reconstruct the lesson from messages. Halqora uses the same outcome record for both calculations, with different fixed outcome rules for charges and pay. A shared record does not mean every outcome produces equal amounts on both sides. The family charge and teacher earnings still answer different questions.
Teachers can record a completed class with a report, a student no-show, or a student cancellation. Admins resolve everything else. Admins also record teacher late minutes, wait minutes, and the emergency exception; classroom connection logs do not make those decisions.
For completed classes, teachers provide a 1 to 5 rating and written feedback. Admins see those internal reports. Families do not. Payroll for the period waits until the completed-class reports are in, so a missing report remains a visible task rather than disappearing into a payment total.
The fixed pay rules include a grace period of up to 2 minutes late. At 3 to 5 minutes late, the deduction is a flat 5% of that class’s pay. Beyond 5 minutes, the teacher loses a minute of pay for every minute late, with a floor of 0.
For a student no-show, full teacher pay requires a recorded wait of at least half the class. A missing wait time needs admin review. These details explain why the class outcome should drive invoices and payroll: a status without the required supporting information is not ready for settlement.
Why does matching transfers still need judgment?
Payment matching needs enough evidence to connect incoming money to the correct open invoice. Halqora matches incoming payments from Wise (wise.com); Halqora does not create Wise payments. An invoice number in the payment reference provides a direct connection. Without that reference, matching depends on the amount, currency, and payer name identifying a unique invoice. Ambiguous payments need an admin decision.
An amount alone is weak evidence. Families can owe the same amount, and a payment description may not contain the student’s name.
Halqora uses the invoice reference where possible, subject to currency and outstanding-balance checks. Otherwise, the exact amount, currency, and payer-name match must point to a unique invoice. Payments with plausible but unclear matches go to an unmatched queue for assignment or dismissal.
Access to provider data matters too. As of 21 October 2026, Wise’s personal API token documentation restricts balance-statement access to accounts in the US, Canada, Australia, New Zealand, Singapore, and Malaysia. A UK or EEA academy cannot pull those statements with a personal token.
Halqora falls back to the activities feed in that situation. Matching quality depends on the information Wise returns. Keep the unmatched queue as part of the payment process, and preserve a review step when the available evidence is incomplete.
Why should families be able to join without passwords?
Families need a clear route to their next lesson and their invoice. Halqora gives each student a permanent private class link and provides a private invoice page with a downloadable PDF. Parents and students do not need accounts. Admins and teachers sign in, keeping the family experience focused on joining class and understanding the bill.
The class link shows the next class. The link is not a class reminder, and Halqora does not send reminders about upcoming lessons. Families still need to know where they saved their link and when to check the page.
Private links need careful handling because possession of the link grants access. Class and invoice links do not expire. If a link is shared with the wrong person, an admin can replace it, stopping the old link from working. A class link can also be revoked.
What changed between spreadsheets and Halqora?
The comparison below contrasts the usual spreadsheet-and-chat routine with what Halqora does now. The left column describes a typical manual routine built from Zoom or Meet, Google Calendar, WhatsApp, spreadsheets and PayPal; it is not a record of any one academy’s files. The feature references point to the feature overview, where readers can explore the relevant area.
| Job | The usual manual routine | What Halqora does now | Feature page |
|---|---|---|---|
| Recurring schedules across time zones | A calendar per teacher, with time zones converted by hand | Stores scheduling rules in each IANA time zone | Feature overview |
| Recording what happened in each class | A sheet or chat message after each class | Teachers record supported outcomes; admins resolve other cases | Feature overview above: class outcomes |
| Monthly invoices | Counting classes per family in a sheet, then typing each invoice | Creates draft invoices for admin review and sending | Feature overview above: billing |
| Teacher pay | A payroll sheet rebuilt every month from the same records | Calculates class pay from hourly rates and fixed outcome rules | Feature overview above: payroll |
| Matching Wise and bank payments | Checking bank, Wise and PayPal statements against open invoices by eye | Matches Wise receipts; admins assign unclear receipts and record manual payments | Feature overview above: payments |
| Giving families class links and invoices | Sending links and PDF invoices to each parent on chat | Provides private class links and invoice pages with PDFs | Feature overview above: family access |
| Spotting unreliable patterns | Scanning the sheets for patterns when a problem comes up | Summarizes recorded cancellations, no-shows, and teacher lateness | Feature overview above: analytics |
What still needs an admin, and where are the limits?
Halqora keeps human decisions where the recorded evidence needs interpretation. Admins resolve incomplete class outcomes, review invoices before sending, and assign unclear payments. Payroll calculates what is owed; Halqora does not transfer teacher pay. Those boundaries matter when you assess the product, because replacing a spreadsheet should make responsibility clearer rather than hide unresolved decisions behind a total.
Keep these review tasks explicit:
- Resolve open class outcomes and missing supporting details before closing the period.
- Review draft invoices and any billing warnings before sending them.
- Check unclear receipts against the family and invoice before assigning payment.
- Complete teacher payments outside Halqora, then mark the payments paid manually.
Analytics also depends on what people record. Halqora summarizes cancellations, no-shows, and teacher lateness from recorded outcomes. Under 3 recorded classes, the reliability view shows “Not enough data.” An empty outcome history cannot support a useful judgment about reliability.
Halqora does not record classes or provide AI features. Halqora supports one-to-one classes with a fixed set of 5 Quran and Islamic subjects; group classes and non-Quran subjects are not supported today. These are current limits, not promises about future releases.
When moving an academy from spreadsheets to software, preserve the review responsibilities alongside the records.
How Halqora handles this
Halqora connects scheduling, class outcomes, billing, and payroll around the class record. Monthly billing runs create drafts; an admin reviews and sends them. Unpaid invoices receive automatic email reminders. Teachers see earnings calculated with the same rules as payroll, and families use private links without accounts. Our software for online Quran academies follows that operating model: record what happened, review what needs judgment, and let the connected calculations use the recorded decision.
Sources
- IANA time-zone data for Asia, checked 21 October 2026
- IANA time-zone data for Africa, checked 21 October 2026
- UK government clock-change guidance, checked 21 October 2026
- Wise personal API token documentation, checked 21 October 2026
