Drag and Drop Question You are setting up the general journals and batches for an accounting department. The accounting department has multiple users who will work simultaneously within different…

Question

Exhibit

Answer Area

Explanation

Dynamics 365 Business Central: General Journal Setup for Multiple Users

This question tests knowledge of journal template and batch configuration in Business Central, specifically for multi-user environments.

Context: The Setup Problem

When multiple users work simultaneously in general journals, you need separate journal batches per user (to avoid conflicts) with specific settings that control balancing, numbering, and validation behavior.

Placement Explanations

Requirement 1 → Suggest Balancing Amount

What it does: When enabled on a journal batch, BC automatically proposes a balancing entry amount as users input lines.

Why it fits here: This is a per-batch setting, meaning each user's batch can independently have this toggled. It reduces manual effort and entry errors for users working simultaneously. The requirement here is typically: "Users should have balancing amounts automatically proposed to minimize data entry errors."

Common mistake: Confusing this with Force Doc. Balance. Suggest Balancing helps the user; Force Doc. Balance enforces a rule.

Requirement 2 → Posting No. Series

What it does: Defines the number series applied to posted documents (not the journal lines themselves). Each batch can have its own Posting No. Series.

Why it fits here: With multiple users posting simultaneously, you need separate number series per batch/user to avoid duplicate document number conflicts. The requirement is typically: "Each user's posted entries must receive unique, non-conflicting document numbers."

Common mistake: Choosing No. Series instead. No. Series controls the journal line/entry numbering (the draft), not the posted document numbering. For multi-user simultaneous posting, Posting No. Series is the correct field.

Requirement 3 → Force Doc. Balance

What it does: Set at the journal template level, this prevents posting unless each document (grouped by Document No.) is fully balanced (debits = credits).

Why it fits here: The requirement is typically: "The system must enforce that each document balances before it can be posted." This is a template-level control that applies as a validation rule across all batches using that template.

Common mistake: Thinking this is a batch-level setting. It lives on the template, not the batch, so it applies globally to all users using that journal type.

Why the Unused Items Don't Fit

Key Takeaway

The hierarchy matters: Template settings (like Force Doc. Balance) apply globally; Batch settings (like Suggest Balancing Amount and Posting No. Series) are per-user and enable simultaneous, conflict-free work.

No community discussion yet for this question.