Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/community/knowledge/finance/post-ledger-entries-through-posting-codeunits.md
Jesper Schulz-Wedde 3cb00e4d2d Add Finance posting domain-knowledge pilot 
Adds three atomic domain-rule knowledge files under community/knowledge/finance/ as a pilot for Type-A (normative) Business Central domain knowledge: post through the posting engine, treat posted ledger entries as immutable, and treat the Dimension Set ID as the source of truth for dimensions. Includes a good/bad AL sample pair for the posting rule.

These encode BC-specific invariants that LLMs reliably get wrong, fitting the existing remedial/atomic knowledge grain with no schema or contract changes. Passes the repo frontmatter validator and is discovered by the knowledge index.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-06-26 10:40:50 +02:00

2 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
finance
posting
g-l-entry
ledger-entry
gen-jnl-post-line
journal-line
balancing
entry-no
al
w1
finance

Post ledger entries through the posting engine, never by inserting them directly

Description

Ledger entries — G/L Entry, Cust. Ledger Entry, Vendor Ledger Entry, Item Ledger Entry, and their detailed counterparts — are the output of Business Central's posting engine, not ordinary tables an extension writes to. The supported way to create them is to populate a journal line (for example Gen. Journal Line) and run the matching posting codeunit (Gen. Jnl.-Post Line, codeunit 12, for general-ledger postings). The posting routine enforces double-entry balancing, allocates Entry No. safely under concurrency, creates the register, resolves dimensions, applies VAT, and links source and application data. None of that happens when a row is inserted into the ledger table directly.

Best Practice

Build the transaction as one or more journal lines and hand them to the posting codeunit. Let the engine assign Entry No., create the G/L Register, and write the balancing entries. When you need a reusable entry point, wrap the journal-line setup in your own codeunit but still post through Gen. Jnl.-Post Line — or through the document-posting routines (sales, purchase, service) that ultimately call it. See sample: post-ledger-entries-through-posting-codeunits.good.al.

Anti Pattern

Calling Insert on a ledger table — typically after a FindLast to guess the next Entry No. Detection signal: any Insert on a *Ledger Entry or G/L Entry record, or an Entry No. computed in AL rather than returned by the platform. Such code produces an unbalanced, registerless, dimensionless row that reconciliation and reporting will treat as corrupt, and the hand-computed Entry No. races under concurrency. See sample: post-ledger-entries-through-posting-codeunits.bad.al.