Release Date: May 26th 2026, build 28.0.202622.166596
Release Summary
- Two related fixes to Intercompany numbering and item tracking under concurrent inventory-pick posting.
- IC Transaction No. allocation now uses Business Central's
NumberSequenceAPI on platforms where the base app has moved to it, sharing the counter with standard BC; older platforms continue to use the legacy GLSetup pattern, now guarded against duplicates. - IC Item Tracking rows are moved to the Handled inbox/outbox line tables when a transaction is handed off, eliminating a duplicate-key error on re-send.
- Re-sending an Intercompany transaction that the receiver has already handled now stops with a descriptive error instead of silently producing a duplicate purchase order.
Bug Fixes
The Transaction Flow
Aligned IC Transaction No. assignment with Business Central's number sequence pattern.+
Intercompany now allocates IC Transaction Numbers using Business Central's built-in NumberSequence API on platforms where the base app has already moved to it — matching Microsoft's own IC inbox/outbox numbering pattern and sharing the same counter.
Why this matters
When users post Intercompany documents concurrently (for example multiple inventory picks posted in parallel), the previous logic could:
- Cause locking delays on the General Ledger Setup table.
- In rare cases produce primary-key errors when two postings claimed the same IC Transaction No.
On platforms where Business Central has moved to NumberSequence, these issues are removed by sharing the platform counter.
How it works
- No setup or manual action is required.
- Intercompany checks at runtime whether Business Central has provisioned the
'ICTransactionNo'platform sequence. - If yes, IC Transaction Numbers come from the platform sequence — the same counter base BC uses.
- If not, Intercompany continues to use the previous
"Last IC Transaction No."field on General Ledger Setup, now protected by the additional duplicate-key guard delivered in BC647-833.
Related
This change works together with the defensive guard delivered in the same hotfix under BC647-833. The independent IC Item Tracking Lines fix from BC647-833 is unaffected.
More reliable Intercompany posting under concurrent inventory picks.+
This hotfix addresses two errors customers could hit when several Intercompany shipments were posted at the same time, typically via concurrent inventory picks.
IC Item Tracking Lines duplicate-key error
When an Intercompany transaction was moved to Handled on the receiving side, SCB's IC Item Tracking rows were not moved alongside the header and line records. A re-send of the same transaction could then produce a primary-key error in "IC Item Tracking Lines". Tracking rows are now moved to the Handled IC Inbox/Outbox line tables automatically, in line with how Business Central moves the rest of the transaction.
Clearer error when re-sending an already-handled transaction
If the sender attempts to re-send an Intercompany transaction that the receiver has already accepted and moved to Handled, Intercompany now stops with a descriptive message instead of silently re-creating the inbox documents and producing a duplicate purchase order.
Related
The IC Transaction No. duplicate-key error from the same incident is fixed at the root by BC647-838 in this same hotfix.