Why Your E-Shikshakosh Salary Got Deducted in 2026

You open your salary slip on E-Shikshakosh and the number is lower than last month — no warning, no notice, nothing. This happens more than people admit.

I remember when a teacher from Muzaffarpur messaged me about this exact problem at 11 PM. She had marked attendance every single day, never took an unplanned leave, and still her salary showed a deduction of nearly ₹4,200. No explanation on the portal. No SMS alert. Just a smaller number and a lot of anxiety. That message led me down a rabbit hole of understanding exactly how this system processes salary — and what I found was something most guides never explain clearly.

The 3 Real Reasons Your E-Shikshakosh Salary Got Cut

There are more than a dozen technical reasons the system can flag, but honestly, in 2026, three root causes cover about 90% of all salary deduction cases I have seen. Here they are, in plain language.

Reason 1: Attendance Pending — The Chain Nobody Explains

This is the big one. And what I have seen happen is that teachers who did mark their attendance still get hit by this — because the issue is not whether you marked it, but whether it synced and got approved on the HM dashboard.

Here is the chain, step by step:

You mark your selfie attendance on the app → the app tries to upload it to the BEPC server → the HM dashboard receives it and it shows as “Pending” → the HM must review and approve it → only after HM approval does the attendance count as “Present” in the salary calculation engine.

The thing most teachers miss is this: if even ONE day of your attendance shows “Pending” on the HM dashboard at the time salary processing runs for that month, the entire month’s salary can be placed on hold. Not reduced by one day — fully held. This is the most painful and least-documented behavior of the E-Shikshakosh payroll module.

Why does attendance stay “Pending”? Three common sub-reasons:

• Your GPS location showed “Out of Range” during selfie upload (very common in rural blocks)
• The app was on an older version (pre-v3.5.0) and the sync failed silently
• The HM simply did not log in to approve the batch — which happens more than the Education Department will admit

Reason 2: Attendance Sync Failure (The Silent Error)

Different from “Pending,” a sync failure means the data never even reached the server. When you check your dashboard you will notice something like “Upload Failed” or the attendance date simply missing from the calendar — no entry at all, not even a pending one.

This happens when:

• You marked attendance in offline mode but never went to a network zone to trigger the “Upload Saved Data” function
• The app crashed mid-upload and the local saved record got corrupted
• You were using E-Shikshakosh App version 2.x, which had a documented high failure rate in low-bandwidth areas

The 2026 App v3.5.0 update fixed much of this with a 40% faster sync engine, but if you are still on the old version, sync failures are very much alive.

Reason 3: DCF Mismatch — The Paperwork Ghost

DCF — the Data Capture Format — is essentially your digital service record. It holds your name exactly as in Aadhaar, your bank account details, your UDISE-linked school code, and your appointment information.

When any of these fields do not match what the salary disbursement system expects, the salary module flags your record. What I have seen happen is that a mismatch as small as a middle name spelled differently between your Aadhaar and your appointment letter — something you might not even notice — can cause a “Data Mismatch” flag that freezes salary processing.

The system does a stricter cross-verification than it did in 2024–25. The BEPC tightened DCF validation as part of the new payroll audit compliance. If your DCF was submitted before the November 2025 update and never re-verified, you are in the risk zone.

How to Check WHICH Reason Caused YOUR Deduction

Do not guess. The portal actually gives you the information — you just need to know where to look. Follow these steps:

1. Log in to your E-Shikshakosh Teacher Dashboard at eshikshakosh.bihar.gov.in using your 12-digit Teacher ID and password (or OTP login).
2. Go to the “Salary / Payment” module. Look for your latest salary slip. Open it and note the exact amount, any deduction row, and whether there is a remark or reason code written alongside the deduction figure.
3. Now open the “Attendance” section. Check the calendar view for the month where you saw the deduction. Look for any dates marked in yellow or grey — yellow typically means “Pending,” grey typically means “Absent/No Data.” If you see even one yellow date, you have found your culprit.
4. Check your “Service Records” or “DCF Status.” If this section shows any field highlighted in red or flagged as “Mismatch” or “Under Verification,” your deduction is DCF-related.
5. Cross-check the HM dashboard status if you have access, or ask your Headmaster directly to log in and check whether any of your attendance entries are sitting in the “Pending Approval” queue. This single check resolves many deduction cases.
6. Screenshot everything. Before you do anything else, take screenshots of the attendance calendar, the salary slip with the deduction, and any error messages. You will need these when you file a complaint or escalate.

Who to Contact — Depending on Which Reason

This is where most teachers waste days going to the wrong person. Let me map it clearly.

If the issue is Attendance Pending or Sync Failure → Contact Block MIS Officer first.

The Block MIS (Management Information Systems) officer is your first stop for attendance-related data corrections. They have backend access to approve or correct attendance records at the block level. Your HM can also directly escalate a pending batch from their own dashboard. Do not go to the DEO for this — it is below the DEO’s jurisdiction and they will send you back down.

If the issue is a DCF Mismatch → Contact the DEO Office (District Education Officer).

DCF corrections require district-level authorization. Carry a written application, a copy of your Aadhaar, your appointment letter, and screenshots of the mismatch. The DEO’s office processes DCF corrections and re-submits for salary clearance. Expect 7–10 working days for this to cycle through.

If the issue is unclear or you have been bounced around → Contact BEPC directly.

The Bihar Education Project Council is the body that manages the E-Shikshakosh system. Their official helpline numbers as of 2026 are 0612-2215181 / 0612-2233973. You can also reach the BEPC helpdesk at 9523300520. Use these only after the block and district channels have failed or been unresponsive.

Will the Deducted Amount Come Back?

Most websites skip this question entirely. Let me answer it honestly: Yes — but the timeline depends on the reason, and it is not automatic.

For attendance-related deductions

Once the HM approves the pending attendance or the Block MIS officer corrects the sync error, the next salary cycle should process the corrected amount. In some cases, you will receive the held amount as a supplementary credit in that same month’s revised disbursement. In others, it rolls into the following month. The system does not pay interest or compensation for the delay — that is just the reality.

For DCF mismatch deductions:

After the DEO verifies and re-submits your corrected record, restoration typically takes one full billing cycle — meaning if the correction happens mid-month, you may wait until the month after to see the money. Again, no automatic notification — you need to keep checking your dashboard.

What does NOT come back automatically:

If there was a legitimate absence flagged — meaning you actually were absent, or your GPS placed you outside the school boundary on a day you were physically present — that deduction requires a formal Leave Regularization request through the portal, supported by documentation like an official intimation letter or medical certificate.

If Your Deduction Is Still Unexplained After 72 Hours of Filing the SHAKTI Ticket — Here Is What Actually Works

Filing a SHAKTI ticket (through the “Grievance” or “Service Request” module on your dashboard) is the official first step. But what I have seen happen is that tickets sit unresolved for weeks when they are mis-categorized or under-documented at the time of filing.

Here is the escalation path that actually moves things:

Step 1 — File the SHAKTI ticket correctly.

When selecting category, choose “Salary Payment Issue” specifically — not the generic “Other” category. In the description field, write the exact month affected, the deduction amount, and which of the three reasons (Attendance Pending, Sync Failure, DCF Mismatch) you believe applies. Attach screenshots. This is not optional — tickets without attachments get lowest priority in the resolution queue.

Step 2 — Note your SHAKTI Ticket ID and set a 72-hour reminder.

If no action has been taken after 72 hours, do not re-file. Instead, escalate.

Step 3 — Escalate to the Block Education Officer (BEO) in writing.

Go physically if needed. Bring a printed copy of your SHAKTI ticket confirmation. A written application with your ticket ID attached forces an acknowledgment on record. This is the step that most online guides don’t tell you — digital escalation alone is easy to ignore, but a written application at the BEO office creates a paper trail that moves faster.

Step 4 — If BEO escalation yields no result in 5 working days

escalate to the District Education Officer (DEO) with both your SHAKTI ticket ID and your BEO acknowledgment letter. At this level, most salary issues get resolved within a week.

Step 5 — Last resort:

Contact the BEPC helpline (0612-2215181) and quote your SHAKTI ticket ID directly. Request the ticket be re-assigned to a senior resolver.

FAQ

For official grievance submission and salary slip access, use the official portal: eshikshakosh.bihar.gov.in. For technical support, contact BEPC at 0612-2215181 or 9523300520.