Skip to main content

ERPNext how-to & fixes

ERPNext Blocks Backdated Stock Entries After a Reconciliation (2026)

From v15.80, ERPNext blocks a backdated stock entry when a later Stock Reconciliation exists. When the block is right, and the correct unwind sequence.

Updated 12 Oct 202610 min readBy ManojFirst published 29 Jul 2026

You try to post a stock entry dated last week and ERPNext refuses, because a Stock Reconciliation exists after that date. The entry is a legitimate correction, the quantities are real, and the system will not take it. This validation arrived on the v15.80 line and has annoyed enough people to earn its own issue. It is also, more often than not, doing what it should. This guide separates the cases where the block is protecting you from the cases where the reconciliation itself was wrong, and gives you the unwind sequence for the second.

A validation that people complain about is not automatically wrong — sometimes it is the first thing stopping a process problem from becoming a ledger problem. I am Manoj, and I lead ERPNext and Frappe implementation programmes at MithTech, a team of Frappe specialists in Bengaluru. This block is the one clients most often ask me to switch off, and most often should not.

Why is the ERPNext backdated stock entry blocked at all?

A Stock Reconciliation is not a movement. Every other stock document says "this much came in" or "this much went out"; a reconciliation says "regardless of everything before this instant, the quantity here is now 120". That absolute assertion is what makes it useful for correcting drift between the system and a physical count.

It is also what makes earlier insertions incoherent. If a reconciliation on the 15th asserts 120 units based on someone walking the aisle and counting, and you then insert a receipt of 30 units dated the 5th, one of two things must be true: either the count on the 15th was wrong, or those 30 units were already among the 120 counted. The ledger cannot represent both a physical count of 120 and an unrecorded 30 that preceded it.

The behaviour ERPNext exhibited before the validation is the reason it exists. A reconciliation is not modified by later transactions with an earlier posting date. So a backdated entry would post successfully, then be silently overridden by the reconciliation. Users met this as a stock-ledger mismatch: an entry they had definitely made simply did not affect the closing balance.

Interactive

Posting Order Simulator

Set the stock entry and reconciliation dates and quantities to see whether the entry is blocked, and what the closing balance becomes in each case.

Day 1 · entry (day 5) · reconciliation (day 15) · Day 30

Blocked on v15.80 and later

The entry sits before a Stock Reconciliation, so the validation refuses it. Note what would happen if it were allowed: the reconciliation on day 15 would still assert 120, so your backdated 30 units would be absorbed and vanish from the closing balance — the mismatch reported on the forum.

Illustrative model of the validation from PR #49549 as described in #49861 (ERPNext v15.80.0). Confirm behaviour on your own release before designing a process around it.

Move the entry date across the reconciliation date and watch what happens to the closing balance. Before the reconciliation, the quantity is absorbed and disappears. After it, the quantity lands in stock. That difference is the whole argument for the validation: the blocked posting was never going to do what the user expected.

Which case are you in?

The block has one behaviour and five quite different underlying situations. Only one of them justifies cancelling the reconciliation.

Interactive

Backdated Block Decider

Select why you are trying to post a backdated entry to see why the validation is refusing it and what the correct response is.

Pick why you are trying to post a backdated entry.

The pivotal question is the one in the middle: did the physical count behind that reconciliation already include the stock you are now trying to add? If it did, posting the entry at all would double-count — the reconciliation is right and your correction is redundant as a quantity movement, however real the underlying paperwork is. If it did not, the reconciliation was measured against an incomplete picture, and it is the reconciliation that needs to go, not the validation.

That distinction is worth taking seriously because it is answerable. Someone counted. Ask them what they counted.

How do you unwind it correctly?

Which path you take depends on one fact — whether the count already included the stock:

The situationWhat to doWhy
Count already included this stockPost after the reconciliation (or record for costing only)Posting before would double-count
Count taken before this stock arrivedCancel the reconciliation, post backdated, re-runThe reconciliation asserted a wrong number
Correction targets a closed periodPost in the open period, narrate the true dateNever reopen a period to satisfy the ERP

Code recipe

Diagnose · Correct · SOP · Prevent

Copy-paste diagnosis steps, the two correction sequences, a draft backdated-entry policy, and the process changes that stop the block firing.

Find the reconciliation that is blocking you, and check whether it already accounts for what you are trying to post.

text
1. Find the blocking reconciliation:
     Stock > Stock Reconciliation
     Filter: Item + Warehouse from the error
     Sort:   Posting Date ascending
   The earliest one AFTER your intended posting date
   is what is blocking you.

2. Open it. Note the counted qty it asserted and who
   submitted it.

3. The decisive question:
     Did the physical count behind that reconciliation
     ALREADY include the stock you are now trying to
     backdate?

   YES → do not post it at all. You would double-count.
         Record it for costing only, dated after.
   NO  → the reconciliation was measured wrong.
         See "Correct properly" — cancel it first.

4. Check the accounting period status for your target
   date before planning anything.

0 of 5 steps done

Tick a step’s number when it is done; the ticks stay on this device.

Find the blocking reconciliation

Filter Stock Reconciliation to the item and warehouse from the error, sorted by posting date ascending. The earliest one after your intended posting date is what is refusing you. Open it, note the counted quantity it asserted, and find out who submitted it — you are going to need to ask them what the count covered.

Answer the double-count question

Did the physical count already include the stock you want to backdate? If yes, stop: the quantity is already in the ledger via the reconciliation, and posting it again inflates stock. Record the document for costing or audit purposes with a date after the reconciliation, and note why. If no, continue.

Cancel the reconciliation before anything else

Where the reconciliation was measured wrong, cancel it first. Everything after it inherits an assertion that was never true, so correcting around it produces a second wrong number rather than a right one. Cancelling a submitted reconciliation should be an approved action with a logged reason — this is not a routine operation.

Post the backdated entry, then let the repost finish

With the reconciliation gone, post the entry with its true posting date and time. A backdated insertion triggers a Repost Item Valuation across everything after it. Let it complete before proceeding — a queued or failed repost means the valuation you are about to reconcile against is not yet settled, which is covered in our Repost Item Valuation guide.

Re-run the reconciliation and verify

Re-run the Stock Reconciliation with the correct counted quantity, then confirm the Stock Ledger balance at the reconciliation's posting instant matches it. If those disagree, something else is outstanding — most often a second backdated entry nobody mentioned, or a negative-stock condition of the kind covered in our negative stock guide.

What happens when stores, accounts and the ERP owner are different people?

The person hitting this block is usually in stores, at the end of the day, holding a delivery challan from last week. The person who submitted the blocking reconciliation is in accounts. The person who could cancel it is neither.

Left unresolved, the predictable outcome is that the stores user posts the entry with today's date and says nothing, because that is the only action available to them. The quantity is then right and the timing is wrong — usually the lesser evil. But it happens silently. Nobody knows the ledger holds a movement attributed to the wrong week, and nobody can explain the variance when a customer queries a delivery date three months later.

The pattern that works is a documented escalation with a named owner and a short queue. Give stores one sanctioned action — post after the reconciliation, narrate the true date — plus a log. Then have whoever owns inventory review that log weekly and decide which entries warrant cancelling a reconciliation and which do not. You are not trying to give stores the power to cancel reconciliations. You are trying to stop them from needing to make the decision alone at six in the evening.

Draft policy for your inventory and finance leads to ratify. Stock Reconciliation is a scheduled period-end control, not a routine correction tool. No stock entry is posted with a date earlier than the most recent Stock Reconciliation for that item-warehouse; where the reconciliation is believed wrong, it is cancelled and re-run under approval from the inventory owner, with a logged reason — it is never worked around. Corrections belonging to a closed accounting period are posted in the current open period, referencing the original date in the narration; periods are not reopened to satisfy the ERP. Data entry runs no more than two working days behind physical movement, and routine backdating is treated as a process defect rather than a system limitation. The entry-lag window and approval threshold are a starting point — set them against your own volumes and have your auditor confirm the period-close treatment before adoption.

Should you post after, or cancel and re-run?

The physical count already included this stockThe count was taken before this stock arrived
Quantity is right, only the date is wrongThe closing balance is genuinely understated
The reconciliation was a scheduled period-end countThe reconciliation was posted reactively to fix a number
The target period is closedThe whole sequence sits inside the open period
Valuation impact is immaterialCosting depends on the true receipt date

Frequently asked questions

Why can't I post a backdated stock entry in ERPNext?

Because a Stock Reconciliation exists later in the timeline for that item and warehouse. The validation added in PR #49549 refuses backdated entries in that situation, since a reconciliation asserts an absolute counted quantity that an earlier insertion would contradict.

Can I turn off the backdated entry restriction?

There is no supported setting to disable it. Making it optional is exactly what #49861 requests, and the issue is still open. Note that #47673 asks for the opposite — more restriction on backdated entries — so the maintainers are balancing two contradictory requests.

What happens if a backdated entry is posted before a stock reconciliation anyway?

The reconciliation overrides the balance regardless of what precedes it, so the backdated quantity is absorbed and does not affect the closing balance. Users meet this as a stock-ledger mismatch where an entry they definitely made appears to have had no effect — which is the behaviour the validation now prevents.

How do I correct a stock reconciliation that was wrong?

Cancel it, post the backdated entry that should have existed with its true posting date, let the resulting Repost Item Valuation finish, then re-run the reconciliation with the correct counted quantity. The order matters: correcting around a wrong reconciliation produces a second wrong number rather than a right one.

Which ERPNext version introduced this validation?

It was reported on ERPNext v15.80.0 in issue #49861, arriving via PR #49549. If you have recently upgraded and this behaviour is new to your team, that is why — it is a deliberate change rather than a regression.

What if the correction belongs to a closed accounting period?

Do not reopen the period. Post the correction in the current open period with a narration referencing the original date, which is the standard treatment for a prior-period stock correction. Whether it needs any further disclosure depends on materiality, and that judgement belongs with your auditor.

What is the bottom line?

This is one of the rare cases where the right response to a blocking validation is to leave it alone. The block exists because the alternative — a backdated entry silently absorbed by a later reconciliation — was worse and harder to detect. The way to stop hitting it is process, not a setting: reconcile on a schedule rather than reactively, and close the gap between goods moving and paperwork landing. Do that and the validation stops being something you meet at six in the evening.

Live demo

Your next step

Stock corrections piling up behind reconciliations nobody wants to cancel?

Buying

Low stock reorders itself

4 screens · about 6 min · you end with a purchase order sent

See it live

Material RequestPending

Stock fell below its reorder level, so ERPNext raised a request on its own.

Raised by
The reorder level
For
The warehouse that ran low

Mith Demo Traders · demo company

ERPNext how-to & fixes

Now see what an audit finds in yours

When the same problems keep coming back, tick what you see and get an audit of the ERPNext you have, then fixes in order of what costs you most.

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 29 July 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.