What's New: Fixed and Variable G/L Allocations (2023 release wave 2)

Overview

The video presents allocation accounts, a way to split cost and revenue across dimensions and G/L accounts. Fixed allocations use predefined percentages. Variable allocations calculate shares from statistical accounts or G/L balances. Inherit from parent lets you allocate an existing G/L account with an allocation key without creating a dedicated allocation account.

Demos show allocations in general journals, combined with deferrals, and on purchase invoices, including editing the proposed split before posting. The later chapters walk through setup, the share UI pattern, decimal precision, dimension handling, and the code structure and integration events for developers.

Key points

• Three allocation types: fixed (predefined percentages), variable (based on statistical accounts or G/L balances), and inherit from parent (existing G/L account plus an allocation key).
• Inherit from parent requires the destination account number to be blank.
• Variable allocations let you choose how the balance is calculated: balance at date, fiscal year, week, quarter, previous year and other options taken from cost allocations.
• Allocation accounts work in general and recurring journals, with deferrals (allocate and spread over periods in one transaction), and in sales and purchase documents.
• Proposed splits can be adjusted before posting: amounts, G/L accounts and dimensions can be changed, and lines deleted.
• The share UI keeps percentages summing to 100%. Calculations use up to five decimals internally while the UI shows whole percents; amount rounding applies on the G/L lines.
• Dimensions defined on allocation lines override dimensions on the line. Variable allocation lines can be filtered on global dimensions.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• table “statistical accounts” at 1:42
• codeunit “General Journal Account Management” at 21:20
• codeunit “Sales Allocation Account Management” at 21:20
• codeunit “Purchase Allocation Account Management” at 21:20

Not found in BC28-30: table “statistical accounts”, codeunit “General Journal Account Management”, codeunit “Sales Allocation Account Management”, codeunit “Purchase Allocation Account Management”.

Quotes

• 1:02 “in last release we introduced a new feature called statistical accounts and that is a feature that can hold nonfinancial numerical data”
• 2:58 “a new feature that you can also use statistical accounts for the new feature is called allocation accounts”
• 5:37 “when I post it it will get split into three individual lines and of course there’s a debit and credit so we end up”
• 7:09 “allocation is done uh because you want better uh data for uh a later analysis of of your your business”
• 13:43 “helps you to change the percentages in an easy way and ensure that they are always adding up to 100”
• 15:06 “in the background we are calculating it up to five decimals so these calculations are going to be very accurate and we are also”
• 17:42 “you can specify how you are calculating the balance it can either be a balance set date fiscal year week quarter previous year”
• 19:59 “if you would like to use inherit from parent then we cannot Define the destination account number so these needs to be blank”
• 21:00 “the allocation account is actually implemented in the base app and it is going to be under Financial Management’s allocation account folder”
• 22:22 “we have added the integration events two of them one is on before create General joural line which you can use if you are”

Presenters (as heard): Brian Nelson, Nicola.