Small and medium business | Business Central, N...

Performance issue on General journal posting

(7) Share

Report

Posted on by Dynamics_Decoded_Gokul

487

We are experience a performance issue with Indian version of business central.

It is taking about 6 minutes to post 6,000 lines. Given their business requirements, they need to post 40,000 to 50,000 lines in a week, which is extending to around 30 minutes. This extended time is causing table lock issues on occasion.

Is there any way to reduce the timing of this same. We have found in the profiler that Tax engine and it usecases are very high time. however those entries are not coming under any tax scenarios.

by skipping the tax part also still we found its had to post for more than a lack of general journal taking time of 4-6hours in business central SAAS latest versions.

We would like to know any workaround on the same.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Ramesh Kumar 7,547 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

I think Gen. Jnl.-Post Line, Dimension Set, Tax engine take longer time as its validate the data in the respective tables. I would say if this going to on going process I would suggest creating custom code where you post this entries using Job queue in the backend.

Thanks!

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,269 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Check if you have Analysis View setup and if the Update On Posting is set to true because that will cause delay in posting. You can disable them and run it manually.

https://learn.microsoft.com/en-us/dynamics365/business-central/bi-how-analyze-data-dimension

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 11,757 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Root Cause Analysis
1. Indian Localization Tax Engine

The Indian localization includes GST logic, which hooks into posting routines even if tax is not applicable.

The Tax Engine extension often evaluates tax applicability per line, adding overhead.

Even when tax is not used, the event subscribers and validation logic still execute.

2. Journal Posting Design

Business Central posts line-by-line, and each line triggers:

Dimension validation

Tax evaluation

Posting group resolution

Ledger entry creation

This is not optimized for bulk posting in SaaS environments.

3. Table Locking

Long posting durations increase the risk of SQL table locks, especially on:

Gen. Journal Line

G/L Entry

VAT Entry

Tax Entry (India)

Recommended Workarounds & Optimizations
🔹 1. Disable Tax Engine for Non-Tax Journals

If tax is not applicable, consider:

Creating a separate journal template with a posting routine that bypasses tax logic.

Customizing the Tax Engine subscriber to skip execution when tax fields are blank or marked as non-taxable.

⚠️ This requires AL customization or a conditional subscriber logic.
2. Batch Posting via Codeunit

Instead of posting via UI, use a custom batch posting routine using Codeunit 12 (Gen. Jnl.-Post) with:

Chunked posting (e.g., 5,000 lines per batch).

Background task queuing via Job Queue or Power Automate.

🔹 3. Optimize Journal Line Structure

Avoid unnecessary fields like:

Dimensions not used in reporting.

Blank tax fields.

Use simplified journal templates for high-volume postings.

🔹 4. Use Temporary Tables for Staging

Load journal lines into a temporary table first.

Validate and clean data before moving to Gen. Journal Line.

Reduces locking and improves throughput.

🔹 5. Microsoft Support & Performance Tuning

Raise a ticket with Microsoft to:

Review Tax Engine performance in Indian localization.

Suggest extension-level optimizations or patches.

They may offer performance tuning or recommend disabling certain event subscribers.

🔹 6. Use Power Platform or Azure Functions

Offload posting logic to Azure Functions or Power Automate for asynchronous processing.

Helps avoid UI timeouts and improves user experience.

Example Strategy for 100,000 Line Journal

Split into 20 batches of 5,000 lines.

Use custom posting routine that skips tax logic.

Schedule via Job Queue during off-peak hours.

Monitor using Telemetry (Application Insights).

Note: This response was created in collaboration with Microsoft Copilot to ensure clarity and completeness. I hope it helps to some extent.
Mark the Answer as Verified if this is Helpful.

Was this reply helpful? Yes No
Suggested answer

RockwithNav 8,967 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
This is on a higher side though.

Happening for all the users?

How many concurrent users we have?

How many posting operation going on at that time?

Any other custom process?

How many Job queue running and the timeframe?

Few things needs to be cleared before you dive in to any route to fix this.

Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,090 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

If no customization is included, you can submit an SR and ask Microsoft to help investigate.

In addition, the table locking problem should be solved in future versions. In the current version, it has been solved mainly for item posting.

https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-setup-general?wt.mc_id=DX-MVP-5004336#allow-workers-to-post-transactions-at-the-same-time

https://www.youtube.com/watch?v=64_cQzp8BP4

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,169 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Performance issues in journal posting often come from custom extensions or heavy tax engine calls. I’d suggest first checking if any custom extensions are adding extra logic during posting — try disabling them in a sandbox and see if performance improves.

If the issue still persists after that, the best way forward is to raise a support ticket with Microsoft, since they can analyze the backend (especially for India localization where tax engine is involved).

✅ Mark this as the verified answer if helpful.

Was this reply helpful? Yes No