Share
Report
13Hi community,
We're running Business Central (cloud) and have an issue with COGS not being applied on a specific sales invoice, which is causing errors in our Chart of Accounts.
Item Info
- Costing Method: FIFO
- Items involved: Assembled bundles (Assemble-to-Stock, not Assemble-to-Order)
- Location: AMZ CA
- Sales Invoice: 26-002006, posted 3/31/2026
The problem
When we filter Item Ledger Entries by document no. 26-002006, almost all rows show Cost Amount (Actual) = 0.00. We have already run "Adjust Cost – Item Entries" (full run, no filter) and "Post Inventory Cost to G/L" — cost is still 0 on these entries.
What we found when drilling down
Drilling into the Value Entries for a zero-cost ILE shows two entries: one original (Adjustment = No) with Cost Amount = 0.00, and one adjustment entry (Adjustment = Yes) that is also 0.00. So Adjust Cost ran but wrote 0 because the source was already 0.
Opening the Application Worksheet for the document shows that the outbound sale entries ARE applied — they link to a Posted Assembly Order (P-ASSEMBL-004652, posted 2/9/2026). However, that assembly output ILE also has Cost Amount (Actual) = 0.00.
Opening the Posted Assembly Order shows the component lines DO have costs:
- item1: Unit Cost 6.216, Cost Amount 1,864.80
- item2: Unit Cost 6.032, Cost Amount 1,809.60
So the component costs exist, but they have not rolled up to the assembled item's ILE. The assembled item was posted on 2/9/2026 and the sale was posted 3/31/2026.
The questions
1. Why did the assembly output ILE get posted with 0.00 cost even though components had costs at the time?
2. Is there a way to force BC to recalculate/revalue the assembly output ILE from the component costs without undoing and reposting?
3. Would "Undo Assembly" and repost be the correct approach here, or would that cause further issues given the sales invoice is already posted against this assembly?
4. Is this a known issue with Adjust Cost not cascading through Assembly output ILEs?
Any guidance appreciated.
Thanks
We're running Business Central (cloud) and have an issue with COGS not being applied on a specific sales invoice, which is causing errors in our Chart of Accounts.
Item Info
- Costing Method: FIFO
- Items involved: Assembled bundles (Assemble-to-Stock, not Assemble-to-Order)
- Location: AMZ CA
- Sales Invoice: 26-002006, posted 3/31/2026
The problem
When we filter Item Ledger Entries by document no. 26-002006, almost all rows show Cost Amount (Actual) = 0.00. We have already run "Adjust Cost – Item Entries" (full run, no filter) and "Post Inventory Cost to G/L" — cost is still 0 on these entries.
What we found when drilling down
Drilling into the Value Entries for a zero-cost ILE shows two entries: one original (Adjustment = No) with Cost Amount = 0.00, and one adjustment entry (Adjustment = Yes) that is also 0.00. So Adjust Cost ran but wrote 0 because the source was already 0.
Opening the Application Worksheet for the document shows that the outbound sale entries ARE applied — they link to a Posted Assembly Order (P-ASSEMBL-004652, posted 2/9/2026). However, that assembly output ILE also has Cost Amount (Actual) = 0.00.
Opening the Posted Assembly Order shows the component lines DO have costs:
- item1: Unit Cost 6.216, Cost Amount 1,864.80
- item2: Unit Cost 6.032, Cost Amount 1,809.60
So the component costs exist, but they have not rolled up to the assembled item's ILE. The assembled item was posted on 2/9/2026 and the sale was posted 3/31/2026.
The questions
1. Why did the assembly output ILE get posted with 0.00 cost even though components had costs at the time?
2. Is there a way to force BC to recalculate/revalue the assembly output ILE from the component costs without undoing and reposting?
3. Would "Undo Assembly" and repost be the correct approach here, or would that cause further issues given the sales invoice is already posted against this assembly?
4. Is this a known issue with Adjust Cost not cascading through Assembly output ILEs?
Any guidance appreciated.
Thanks
Categories:
I have the same question (0)
All responses (
Answers (
