Automatic synchronization
Understand which postings are queued and how they reach NTMP.
Automatic queueing starts when the company's facility is Mapped - Complete. It monitors transactions created through Business Central's general journal posting process, including postings originating from documents and journals.
From posting to submission
Check the transaction
The extension checks the G/L entries in the new register. If no account in a transaction has an NTMP mapping, it creates no sync record for that transaction.
Require complete mapping
If any account is mapped, every account in that transaction must be mapped. Otherwise, posting stops with an error naming the first unmapped account.
Queue locally
A Pending sync record and its nonzero G/L entry lines are created in the same database transaction as the posting. The row captures the current submission mode.
Send in the background
The recurring job processes pending rows, normally every five minutes. It sends each batch through the HA integration server and records the response.
No HTTP call is made during posting. An unavailable external server therefore does not cause a network wait inside that posting. Local mapping validation can still block a posting.
When posting is blocked
The message begins:
Posting blocked: G/L account X is posted together with NTMP-mapped accounts but is not itself mapped.
Map the named account to the correct active NTMP ledger account, then post again. See account mapping. Do not remove valid mappings just to bypass the check.
Duplicate handling
Each queued line has a stable Facility Ledger Id, built from the company identifier and G/L entry number. Retrying the same row preserves those identifiers. When NTMP returns its duplicate-ledger-identifier response, the extension marks the row Duplicate.
The extension also avoids creating a second sync header for the same facility and Business Central transaction number.
Scope of automatic queueing
- Queueing applies to new postings after the facility is ready.
- The current interface does not include a historical backfill action for older G/L entries.
- Transactions without mapped accounts do not enter the queue.
- A failed row must be re-queued with Retry before the background job processes it again.
Continue to monitor synchronization.