Batch posting in Business Central

Posting one sales invoice is fast. Posting 500 at month-end is not — unless you use batch posting, BC's feature for queueing multiple documents for unattended posting, typically in background. Understanding when batch helps and when it just hides problems matters for posting performance.

What batch posting means.

• A user selects multiple documents (sales orders, sales invoices, purchase invoices, etc.).
• Invokes Batch Post action.
• BC queues each for posting.
• Posting happens sequentially, often in a background session.
• Results summarised — successes, failures.

The user doesn't wait for each post; they get a notification when the batch completes.

Where batch posting is available.

• Sales orders (post and ship).
• Sales invoices.
• Purchase invoices.
• Purchase orders (receipt or invoice).
• General journals.
• Item journals.

Each list page typically has a Batch Post action.

Foreground vs background.

• Foreground — user's session processes the batch; user waits.
• Background — BC's task scheduler processes; user continues working.

Background is the modern default for batch posting. Configured via the Job Queue entry that runs batch posting tasks.

Performance comparison.

• Single posting — one document at a time, user-driven, sub-second to few-seconds each.
• Batch posting — multiple documents, queued; per-document time similar but no user wait.
• Bulk SQL operations — would be faster but bypass business logic; not supported.

Batch doesn't make individual posts faster; it removes user wait time.

Error handling.

• One document failing doesn't stop the batch.
• Failed documents listed in the batch results.
• User reviews failures and reposts or fixes.

This is critical — without batch, a failure means user manually retries; with batch, failures isolated automatically.

Concurrency considerations. Background batch posting runs in its own session:

• Locks tables briefly during each post.
• Concurrent user activity may conflict.
• Some posts may retry due to lock conflicts.

For high-volume batches, schedule during off-hours to avoid concurrency.

Per-document type considerations.

• Sales invoice batch — straightforward; each invoice independent.
• Sales order with shipment + invoice — two steps per order; batch handles both.
• General journal — batch posts each journal as a unit; if one journal has imbalanced lines, the journal fails as a unit.
• Item journal — similar.

The job queue. Batch posting often configured as a job queue entry:

• Runs on schedule (nightly).
• Picks up documents flagged for batch posting.
• Posts and reports.

This is the unattended pattern — users mark documents during the day; nightly batch posts them.

Posting via REST API. External systems often batch post via the BC API:

• API call per document.
• Throttling considerations.
• Async error handling.

For external automation, this pattern is common; API rate limits apply.

Common pitfalls.

• Batch hiding problems. Persistent failures buried in batch results; no one triages.
• Background batch competes with users. Mid-day batch slows user activity; schedule for off-hours.
• Posting period closed during batch. Documents fail when the period closes mid-batch.
• Number series exhaustion. Heavy batch posting can outpace number series; configure adequately.
• No alerting on failures. Batch completes; failures ignored.

Optimisation tips.

• Smaller batches — 50–100 documents per batch; easier to recover from errors.
• Pre-flight validation — run report identifying likely-to-fail documents before batch.
• Scheduled retry — for known transient failures.

Configuration: Sales & Receivables Setup, Purchase & Payables Setup. Several batch-posting options:

• Post with Job Queue — enable background processing.
• Notify on Success — send notification when batch completes.
• Notify on Failure — alerts for failures.

When NOT to batch.

• Time-critical posting — single posts are faster end-to-end for one document.
• Reviewer-required workflow — each document needs review.
• Tiny volumes — five documents, just post each.

Strategic positioning. Batch posting is essential for any operation with significant daily posting volume — wholesale distributors, e-commerce, B2B services. Configured properly with background processing, error monitoring, and scheduling discipline, it dramatically improves user experience and posting throughput. Configured carelessly, it becomes a source of hidden errors and operational confusion. Invest in the setup; treat batch as a production process, not a one-click convenience.