In Business Central SaaS, internal warehouse movements (Warehouse Movements, bin-to-bin transfers) generate Item Ledger Entries with quantities, even though:

• the total physical quantity does not change
• the inventory value does not change
• the movement is already fully tracked in Warehouse Entries
• Item Ledger Entries do not contain the BIN, therefore they cannot represent the warehouse movement
• the Item Ledger Entry table is a financial ledger, intended for accounting-relevant or value/quantity‑changing transactions

This behavior did not exist in NAV and introduces several issues in real-world warehouse environments.

Problems caused by this behavior

1. Unnecessary growth of the Item Ledger Entry table

Warehouses with frequent internal movements generate thousands of ILEs per day that have no accounting or costing relevance.

This leads to:

• performance degradation
• slower availability calculations
• heavier cost adjustment runs
• slower API queries
• increased storage usage

My customer has about 75% of useless record in ILE and VE related to internal warehouse entries.

2. Data duplication

The same movement is already recorded in Warehouse Entries, which correctly contain:

• BIN
• Zone
• warehouse logic
• physical movement information

The additional ILEs do not add any useful information.

3. Conceptual inconsistency

A bin-to-bin movement:

• is not a financial transaction
• does not change total quantity
• does not change value
• is not an accounting event
• is already tracked in the warehouse subsystem

Since the ILE does not contain the BIN, it cannot represent the movement and therefore becomes meaningless noise in a financial ledger.

4. No archiving or compression mechanism

The Item Ledger Entry table is considered a permanent accounting ledger.

It cannot be:

• archived
• compressed
• summarized
• cleaned up

This makes the accumulation of non‑accounting entries even more problematic.

Request

I kindly request that Microsoft:

Option A (preferred):

Remove the creation of Item Ledger Entries for internal warehouse movements, restoring the correct NAV behavior.

Option B:

Introduce a configuration setting allowing partners to disable ILE creation for internal warehouse movements.

Option C:

If the current design must remain, provide an official mechanism to archive or compress non‑accounting ILEs to prevent uncontrolled growth of the ledger.

Why this matters

Restoring the separation between warehouse logistics and accounting would:

• improve performance and scalability
• reduce unnecessary data growth
• maintain the integrity of the Item Ledger Entry as a financial ledger
• align with real-world warehouse processes
• reduce operational costs for customers

Warehouse Entries already contain all the information needed to track internal movements.

Duplicating these movements in the Item Ledger Entry table provides no functional benefit and creates long-term scalability issues.

Thank you for considering this request.