Update 28.0.202619.164244

When Invoice Rounding is enabled in the SUPPLY company, the rounding amount is now included in the intercompany document sent to the SALES company. The auto-generated purchase invoice or credit memo will match the posted sales document exactly — including totals and VAT.

Setup requirement

The G/L account used for invoice rounding must have an IC G/L Account mapping. Open the Chart of Accounts, find the Invoice Rounding Account, and make sure the Default IC Partner G/L Account No. field is filled in. If the mapping is missing when you post, you will receive a clear error message identifying which account to configure.

No action needed if invoice rounding is off

Companies that do not use invoice rounding are unaffected.

The intercompany app previously supported a maximum of 10 custom field mappings per document type. You can now map up to 50 custom fields by enabling the Extended Custom Fields feature in the Abakion Feature Management page.

How it works

• Fields 1–10 continue to use the existing transfer mechanism — no change to existing setups.
• Fields 11–50 are serialized as JSON and transferred when the feature is enabled.
• The feature is disabled by default.

Before you enable

All intercompany partner companies must be running app version 28.0 or later. Partners on older versions will not receive custom field values above 10.

You can now post the invoice on an intercompany sales order in the SALES company after the order has been partially shipped, or when the shipment was posted through a combined shipment.

What changed

Previously, the IC partner check fired on every posting as long as any line still had a remaining quantity to ship. This blocked invoice-only postings even though no shipment was actually being created.

The check now triggers only when you post a shipment (or a ship-and-invoice). Posting an invoice on its own no longer raises the "shipment will be done in IC partner company" error.

How to use

No setup change. Open the intercompany sales order in the SALES company, set the posting to Invoice (or use Post… and select Invoice only), and post as usual.

Intercompany transactions with many lines (typically 200+) previously caused web service timeout errors. These documents are now automatically detected and routed to background processing via the Job Queue, so posting continues without interruption.

Automatic fallback when processing fails

If an IC Inbox Transaction cannot be processed immediately — for example due to a database lock — it is now silently queued for retry instead of showing an error. This reduces manual intervention in high-volume intercompany flows.

How it works

• Large or failing transactions are marked as "Scheduled for Handling" in the IC Inbox Transaction list.
• The background processor runs on demand and works through all queued transactions in a loop. It schedules itself automatically when retries are pending — no recurring job sits idle between runs.
• No setup is required — the Job Queue entry is created automatically when needed.

All public procedures and methods in the app's AL codebase now include XML doc comments covering summary, parameters, and return values. This makes the code self-documenting, improves IntelliSense hover information, and speeds up onboarding for new developers. No functional changes were made.

Legacy UPPERCASE AL keywords (such as IF, BEGIN, END, SETRANGE, FINDSET, etc.) have been normalised to PascalCase across the codebase, bringing the app in line with the Microsoft AL style guide and Abakion coding standards. This is a purely cosmetic change — there is no impact on runtime behaviour or functionality.