CBSE Circular No. 12/2026, dated 30 September 2026, asks affiliated schools to move more of their money onto digital payments. That covers fees, canteens, libraries and staff salaries. The circular is advisory: schools "may" enable UPI and RuPay cards, "may" onboard onto BBPS, and "may" connect their ERP for recurring payments. If you already take fees online, you can cover most of the fee side this week. BBPS onboarding and digital salary payouts need your bank, so treat those as separate projects.
No. Read the circular itself, not the headlines.
Some news coverage says CBSE is "mandating cashless transactions". Other reports say schools "must" set up UPI, RuPay and BBPS. The circular does not use those words. It says Heads and Managers "are advised to promote the digital payment system for various financial activities pertaining to their school". Then it lists measures schools "are advised to take", and each one uses "may".
The circular follows a Digital Payments Promotion Plan from the Department of Financial Services (DFS), Ministry of Finance. It sets no deadline and no penalty. It still tells you where expectations are heading, so use the time to plan.
The circular groups its measures under three headings.
i. Universal Acceptance Infrastructure
ii. BBPS Integration for Fee Payments
iii. Awareness and Digital Literacy
For most schools, fees are where the most money moves, so start there.
If your school already takes fees online through its ERP, these steps need no new contract.
1. Make online payment the default in every fee notice. Each reminder should include the amount, the fee head, the due date and a way to pay. Paying should not mean a trip to the counter. In ConnectEdu, parents pay through the parent app by UPI, cards or net banking. The payment is confirmed automatically and a receipt is issued.
2. Schedule reminders before the due date. Send an advance notice, a reminder on the due date and a short follow-up for anyone still unpaid. Our post on reducing fee defaulters with reminders and UPI explains the full cycle.
3. Stop accepting UPI screenshots as proof. A screenshot in WhatsApp is not a ledger entry. When parents pay through the fee module, the student's fee status and payment history update on their own.
4. Set up instalments to match how you actually bill. Separate tuition, transport and activity fees, and set them by term where you need to. For the full checklist, see school fee management software for Indian schools.
5. Count the cash still coming in. List which fee heads and classes still pay mostly at the counter. Focus your awareness drive there.
6. Run one assisted-payment desk. The circular suggests "demonstrations and assisted usage models". At the next PTM, have a staff member show parents how to pay a fee in the app. It costs nothing.
For quick checks at the desk, ConnectEdu's Admin AI Agent answers questions from live school ERP data using secure database queries. You can ask in any language, and answers come back in English. It can also add or update student and staff records. It does not send reminders or contact parents. Fee reminders and collection run through the fees and communication modules.
The circular lists them as payment touch-points alongside fees. Many schools run them on cash or a contractor's own QR code. Decide two things. First, should this money go through school accounts at all? Second, does each payment need to appear against a student? Library fines and lost-book charges often do. Where they do, record them as a fee head so they appear in the same student ledger.
Some measures are not a setting you can turn on in your ERP.
BBPS onboarding. The Bharat Bill Payment System is a separate bill-payment network. A school joins it as a biller, normally through a bank or an authorised operating unit. This involves paperwork, agreements and settlement setup. Ask your bank what it involves. Then ask your ERP vendor, in writing, how BBPS payments would be recorded against student ledgers. Do not assume any software already does this.
Staff salary payouts. Most schools already pay salaries by bank transfer. The real question is whether payroll data in your ERP goes straight to your bank's bulk payout facility, or whether someone re-enters it. That link usually depends on your bank's corporate banking product, so speak to your bank first.
RuPay, UPI Lite, UPI LiteX and UPI 123PAY. Which of these you can accept depends on your bank and payment gateway. UPI 123PAY is meant for feature phones. UPI Lite is meant for small payments. If many parents live in areas with poor connectivity, ask your bank or gateway what they support for school collections.
The circular uses "are advised to" and "may" throughout and sets no deadline. Some news reports call it a mandate, but the circular's wording is advisory.
No. The circular says schools "may onboard" onto BBPS. You can keep collecting fees online through your existing fee module. BBPS is an extra channel that needs biller onboarding through a bank.
Canteens, libraries and other services. Low-connectivity options such as UPI Lite and UPI 123PAY. Staff salaries through ERP-linked processes. Awareness drives for teachers, students and parents.
No. It answers office questions from live ERP data and can add or update student and staff records. Fee reminders, payment links and receipts run through ConnectEdu's fees and communication modules.
Start with what you control. Make online fees the default, schedule the reminders and run one parent demonstration. Treat BBPS and salary payouts as bank conversations with their own timelines.
To see how fees, reminders and receipts work in ConnectEdu, book a 30-minute demo or visit connectedu.in.