Small and medium business | Business Central, N...

Adjust Cost - Item Entries

(7) Share

Report

Posted on by InaB

We have a client on Business Central using Average Costing on their items. The Adjust Cost - Item Entries has been set up as a batch job to run every night (they have a large number of transactions daily, so the Automatic Cost Adjustment on the Inventory Setup has been switched to Never). The Post Inventory Cost to G/L job runs directly after. We have encountered an issue where the Adjust Cost - Item Entries job has been failing on a specific item due to a posting date issue (The posting date is not within the range of allowed posting dates). The user running the job is allowed to post from 01/03/2026 until 31/05/2026. On the Avg. Cost Adjmt. Entry Points, the first transaction where the cost has not been adjusted is on 31/03/2026. When I use the Costing Issues Detection Report on the item, no issues are found. Why is BC trying to post an adjustment prior to 01/03/2026 when the system shows the first entry that has not been adjusted is only on 31/03/2026? Any help would be appreciated - is there another report that will give me a better view of what the system still wants to adjust?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Sort by

AndrewThomas81 2,220 on at

Like (2)

Report
Copy link

Link copied!

The item may have value entries outside of the date range.

I would suggest closing inventory periods to prevent back posting

I’d also suggest running the adjust cost manually for that item

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,742 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @InaB

Can you check value Entries , First transaction might be prior 01/03/2026 . Because when you run the batch job it will consider those entries until "Adjusted " Boolean . set to false. Once adjusted it will set to true.

You need to set filters in report or allow posting date fo this job queue

check below link

https://learn.microsoft.com/en-us/dynamics365/business-central/design-details-cost-adjustment

Warm Regards

Pallavi Phade

www.linkedin.com/in/pallaviphade131116

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi, hope the following helps as well.

https://learn.microsoft.com/en-us/dynamics365/business-central/design-details-cost-adjustment?wt.mc_id=DX-MVP-5004336#manual-versus-automatic-cost-adjustment

The new adjustment and rounding value entries have the posting date of the related invoice. Exceptions are if the value entries fall in a closed accounting period or inventory period or if the posting date is earlier than the date in the Allow Posting From field on the General Ledger Setup page. If this occurs, the batch job assigns the posting date as the first date of the next open period.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

OussamaSabbouh 17,623 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hello,
this is normally because Avg. Cost Adjmt. Entry Points is not a full list of every value entry BC may adjust; for Average Cost it tells BC the average-cost period/item/location/variant that needs recalculation, but the actual adjustment value entry often takes the posting date from the original value entry it is adjusting, unless that date is outside the allowed posting range or in a closed inventory period, then BC moves it to the first allowed date. So even if the first unadjusted average-cost entry point is 31/03/2026, the cost change can still be flowing back to older outbound value entries, fixed applications, revaluations, production/order-level cost chains, or an older value entry related to that average-cost period. Also check both places: User Setup and General Ledger Setup / Inventory Periods; the batch job user may allow 01/03–31/05, but if the adjustment tries to land after 31/05, or another setup has a different range, it can still fail. For investigation I would use Inventory Cost Adjustment page first, then drill into the item’s Value Entries and filter Cost is Adjusted = No, Adjustment = Yes/No, posting dates before 01/03, and check Item Application Entries if there are fixed applications; the Costing Issues Detection Report mainly finds known costing data issues, not necessarily “which adjustment value entry will be created next.”
Regards, Oussama Sabbouh

Was this reply helpful? Yes No
Gerardo Rentería Ga... 27,261 Most Valuable Professional on at

Like (3)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Revalue Inventory
Adjust Item Costs
Reporting Costs and Reconciling with the General Ledger

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 17,024 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

Business Central is trying to post an adjustment before 01/03/2026 because, under Average Costing, cost adjustments follow the full item application chain—not just the “first unadjusted entry” shown on Avg. Cost Adjmt. Entry Points.

Even if that page shows 31/03/2026, BC may need to recalculate and post value entries against earlier transactions (e.g., February receipts) due to late invoicing, applications linking March transactions to earlier entries, or average cost propagation rules, and these backdated adjustments are blocked by the user’s posting date restriction.

So the issue is not a data error but a costing chain dependency that requires either widening the allowed posting date range or analysing value entries and item application entries to identify which earlier transactions are being affected.

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,514 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,
This is a tricky one with Average Costing. The Avg. Cost Adjmt. Entry Points table show the first entry that need adjustment, but the Adjust Cost - Item Entries job actually need to re-process all related entries chained backwards through the Item Application Entry table. So if your entry on 31/03/2026 is applied (linked) to an earlier inbound entry from before 01/03/2026, BC try to also re-adjust that earlier entry, and that fail due to the posting date restriction.
The Costing Issues Detection Report may not always surface this kind of situation, because the chain itself is technically valid, the problem is only the posting dates fall outside the user range. Worth verify on your specific case.

Few things to check:
First, look at the Item Application Entry table for that item, filter by Item No., and see if entries on or after 31/03/2026 are applied to older entries before 01/03/2026. This usually reveal the chain.
Second, the Item Ledger Entry "Cost is Adjusted = No" filter is more reliable than the Avg. Cost Adjmt. Entry Points for finding all entries that still need adjustment.

Third, temporarily expand the user posting date range to cover the older entries, run the job, then restrict it back after.
Hope this help,

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards

Gregory Mavrogeorgis

Work: GMSOFT Limited
Blog: Inside Business Central
LinkedIn: www.linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No