Dynamics Community Forum Thread Details

Hi guys

Disclaimer: I'm not a Business Central developer or consultant, I'm an integration developer working on connecting an external system to BC. Everything I know about BC's API surface has come from online research, so I may well be missing something obvious to those of you in the BC ecosystem. Please bear with me, and I'd really appreciate being pointed in the right direction.

Scenario

We're integrating daily transaction batches from a core banking system into Business Central Online. The volumes are significant:

Test environment: ~400,000 records per day
Projected production: ~2,500,000 records per day

Current Approach

Based on what I could find in Microsoft's documentation, our workflow uses the standard BC API:

Create a General Journal Batch
Insert General Journal Lines via the $batch endpoint (max 100 records per call)
Post the batch
Delete the batch

Performance Observed

8,900 records in 10 minutes
Extrapolating linearly (assuming no timeouts or failures): 7.5 hours for 400K records, and 48 hours for 2.5M records, obviously not viable for a daily process.
We attempted parallelizing (5 concurrent requests of 100 records each) but encountered key conflict errors.

What we've Explored

From my research, the $batch endpoint appears to be the fastest standard method for bulk ingestion, but again, I'm not a BC expert and may simply not know what I don't know.
I've read references to custom web services, staging tables with job queues, and polling patterns, but I'm not in a position to evaluate or recommend these without hands-on implementation experience in BC.

Questions

Are there faster standard endpoints or built-in BC functionality for bulk data ingestion that I'm not aware of? If so, I'd be grateful for a point in the right direction, documentation links, feature names, anything to get me started.
If the $batch endpoint is indeed the ceiling for standard API throughput, what customization approach would you recommend for ingesting this volume? Staging tables + job queues? Custom web services? Something else entirely?
Has anyone successfully handled similar daily volumes (hundreds of thousands to millions of journal lines) in BC Online? What architecture did you land on, and what pitfalls should we watch out for?

I just want to be as sure as possible that we've exhausted all options in terms of increasing performance using BC's standard API surface, before advising the client to go down the customization path. We also logged a support call with Microsoft but were advised to post here for community guidance.

Any help is hugely appreciated. Thanks in advance.

Categories:

Dynamics 365 Business Central

Community site session details

General Journals - Integrating 2.5 million records per day

Helpful resources

News and Announcements

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2025 Community Spotlights

Congratulations to the January Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates