General journal entry workflow in Dynamics 365 Finance

Posting a journal entry is the bread-and-butter of finance work in F&O. The workflow has more validation, approval, and audit-trail steps than it appears at first glance — understanding them is the difference between a clean monthly close and a queue of stuck postings.

General journal architecture.

• Journal name — a template defining defaults (voucher series, posting layer, currency, approval workflow, default account/offset). Examples: GenJrn for general; Adjmt for adjustments; Accruals for accruals.
• Journal — an instance of a journal name; one journal per day or per close step typically.
• Journal lines — the actual debit/credit entries.

Creating a journal. From General ledger → Journal entries → General journals:

1. Click New, pick a journal name.
2. The system generates a journal number (sequence per journal name).
3. Enter lines.

Line structure. Each line has:

• Date — posting date.
• Voucher — the voucher number; multiple lines can share a voucher if they balance.
• Account type and Account number — Ledger, Customer, Vendor, Bank, Fixed Asset, Project.
• Debit / Credit amounts.
• Offset account type and number — the contra side.
• Description — narrative.
• Financial dimensions — department, cost centre, project, etc.
• Currency / Exchange rate — for foreign currency entries.
• Tax group / Tax code — when tax applies.

Account types. F&O extends the basic G/L model to allow account types beyond Ledger:

• Ledger — direct G/L posting.
• Customer / Vendor — posts via the AR/AP subledger; creates a vendor or customer ledger entry.
• Bank — creates a bank ledger entry.
• Fixed Asset — creates a fixed-asset transaction.
• Project — posts to project actuals.

Multi-type single-voucher entries are common: a vendor invoice journal has Vendor and Ledger lines; a fixed asset acquisition has Fixed Asset, Vendor, and Ledger lines.

Voucher and balance. The voucher is the grouping unit:

• All lines with the same voucher must net to zero (debits = credits).
• The voucher series is configured per journal name.
• One journal can contain multiple vouchers.

Posting validates the balance per voucher before committing.

Validation chain. Before posting:

1. Field validation — required fields, valid values, date in open period.
2. Account validation — account exists, not blocked, dimension combinations allowed.
3. Tax validation — taxes computed and balanced.
4. Voucher balance check — debits = credits per voucher.
5. Period status — period must be open or sub-ledger-open.
6. Approval status — approved if workflow required.

Any error stops the post; the journal returns to draft.

Approval workflows. Many companies route journals through approval before posting:

• Conditional workflows — only journals above threshold or in certain categories require approval.
• Approval levels — single approver, multi-step, or parallel.
• Delegation — when an approver is out of office.

Approval workflow is configured in the journal name; per-instance overrides are not allowed.

Posting restrictions. Various controls limit who can post what:

• User group on journal name — only certain user groups can use the journal.
• Posting layer — Current, Operations, Tax — restricts which layer the journal posts to.
• Single voucher number per posting — prevents one journal from posting multiple vouchers (forces structural cleanliness).

Recurring journals. A common need: posting the same accrual or allocation every month. Recurring journal lines save the template; per period, create a journal from the template, adjust amounts, post.

Reversing entries. For accruals, the reverse entry flag posts a reversing journal in the next period automatically. Avoids manual reversal of the prior month's accrual.

Approval audit trail. Every approval action is logged:

• Who submitted.
• Who approved (or rejected).
• Comments.
• Timestamps.

Auditors look for evidence of approval before posting; the audit trail is the evidence.

Common pitfalls.

• Wrong journal name selected. Different journal names have different defaults, dimensions, approval workflows; using the wrong one bypasses controls.
• Unbalanced voucher. Posting fails; user gets a cryptic error; the cause is usually one line missing its offset.
• Dimension combinations invalid. F&O's account structure rules can disallow certain account+dimension combinations; posting fails until corrected.
• Posted into closed period. Auto-routing to next open period or rejection per setup.
• Posted to wrong posting layer. Tax adjustments to Current layer rather than Tax; reporting mismatches.

Posted vs draft. A journal exists in three states:

• Open — being edited.
• Posted — committed; voucher numbers are now permanent.
• Rejected / not approved — workflow returned for changes.

Once posted, a journal can't be edited; corrections require a reversing journal.

Operational rhythm. Daily journals for routine activity (cash transfers, accruals); monthly journals for period-end adjustments; quarterly journals for tax reconciliations. A well-designed journal name taxonomy makes this rhythm sustainable; ad-hoc journal posting in a single "General" journal name makes audit trails painful.