Bundles (Revenue recognition)

Bundles (Revenue recognition)

Introduction


Update 2023: The bundles in the sales order are gone, I have not been able to use them for a few months, because the Revenue recognition module may not be activated anymore: Removed or deprecated features in Dynamics 365 Finance – Finance | Dynamics 365 | Microsoft Learn

The Revenue recognition module acquired by Microsoft from Armanino LLC comes with some real-world goodies which do not necessarily have to do with the IFRS regulations but address evergreen Trade & Logistics topics. One of them is a bundling /de-bundling of products.

The problem is well introduced in an older popular blog of mine. In short, the customer is sold a bundle (e.g. the proverbial cat in the sack) with a total price. The customer doesn’t need to know exactly what a single cat costed versus a single sack. Internally the revenues still need to be allocated among the products.
The solution (3) described in the blog is exactly what was implemented in Dynamics 365 in August 2019: an automatic BOM explosion for kits/bundles. The exploded components in the sales order are posted individually into the General Ledger – all with their unique GL accounts and accounting rules – while the sales invoice obscures the details and only presents the bundle and the total price to the customer.

You have to enable the Revenue recognition module first, which is available but hidden in all versions since Dynamics 10.0.5. Check out this source to learn how to do it.

Step by step

Once the module is activated, a new checkbox Bundle appears prominently on the General tab on in the Released product form:
Bundle item
A bundle item must be stock-able, it must be marked with the Bundle = Yes, and it must possess an active and approved bill of material (BOM) with the components inside. The bundle components may be either tangible products or services items, yet those must be stock-able too:
Bundle BOM

The bundle item is then added to the sales order normally:
Bundle before confirmation

The BOM of the bundle is automatically exploded whenever a sales confirmation is posted (to be honest, this is not ideal as we encourage our users to preview sales confirmations first).
The stock parameters, VAT settings etc. are taken from the individual components’ item master. This can be both right and wrong: in the case of a hypothetical ‘chicken in the sack’ the VAT rate for the chicken may indeed differ from the sack. However, in the case of a supplementary service (e.g. transportation) the service shares the fate (i.e. the tax rate) of the master product being shipped, according to the European legislation.

The total bundle price (note the Bundle net amount column far to the right) is allocated to the components in the ratio of their quantities in the BOM and the standard sales prices (not ideal, as the price of a component may vary). The divisor is the total of all components’ (sales prices * quantity) found in the BOM.
In the below example, the promotional sales price of 950 USD for a “Surface Pro tablet with an extra guarantee” is split at the ratio of 899*1/99,89*1 = 9:1 between the tangible Surface SKU and a service item:
Bundle after confirmation
Obviously, the bundle components are picked individually by the Warehouse management, which stands out in comparison to a Retail kit i.e. a “kit from the stock” scenario.

Bundle confirmationThe sales confirmation and the sales invoice printouts only show a summary line with the master bundle item and its description:
Bundle invoice
In contrast, the Delivery note (aka Packing slip) contains all the lines (to remove intangible service lines from the delivery note one may use the classic Quantity = Picked only mode):

This makes sense, as the Delivery note (repurposed to a Commercial invoice) may need to be presented to the customs authorities on export/import operations.

Bundle Delivery noteThat said, the bundles are well supported in the sales business documents, but not necessarily in the T&M or PSA project invoices.

Conclusion

A bundle/kit explosion T&L functionality implemented by partners myriad times through a customization is now available at the D365 Finance / SCM application core, which is great news. Yet the Revenue recognition module has more to offer: how about an accrual of the revenue from the above guarantee service? Check out the upcoming blog.

Make yourself an Admin in Dynamics 365 Fin/SCM

Make yourself an Admin in Dynamics 365 Fin/SCM

How many times have you been given a VM for D365FO development, but no interactive user in the local Web application? You can program X++ code, you can build, but you cannot test. The AdminUserProvisioning tool on the desktop requires local Administrator rights, which is a separate account on new cloud VMs. Fortunately, with an access to the SQL server you can make yourself an Admin.
In essence, the trick is the same as in the past: update the USERINFO table.

  1. Secure an access to the AxDB database in the Microsoft SQL Management Studio. Recent VMs may require a separate admin account, e.g.
    RUNAS /user:Administrator@builtin "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe"
  2. Connect to the AxDB database and locate the USERINFO table, then Edit top 200 rows, find and start editing the Admin record. You may also use the SQL pane to pass the below command:
    SELECT ID, NAME, ENABLE, SID, NETWORKDOMAIN, NETWORKALIAS, DEFAULTPARTITION, EXTERNALUSER, EXTERNALID, IDENTITYPROVIDER, OBJECTID FROM USERINFO WHERE (ID = 'Admin')
    There will be most likely 4 Admin records, the last 3 non-interactive logons are created by the D365 Object server automatically and may have the SID = S-1-5-20 (NT AUTHORITY). We only need to edit the 1st – interactive – account:
    SQL UserInfo table
  3. As in the past (Dynamics AX 2012), the SID is the most important. The easiest way to deduct this ID and other information is to copy and paste it from another cloud environment you have an access to, for example via the table browser: https://xxx.yyy.operations.dynamics.com/?mi=SysTableBrowser&tableName=UserInfo
    UserInfo in the Table browser
  4. Update the following fields in the target record:
    ColumnRemark
    SIDS-1-19-123456789-1234567890-1234567890-1234567890-1234567890-1234567890-1234567890-1234567890-1234567890-1234567890
    The long SID is a unique identifier of your user in the Azure Active Directory (see also “Immutable ID”). It it sufficient to only replace it in the 1st [interactive] logon out of 4.
    NETWORKDOMAINhttps://sts.windows.net/
    This one looks most probably https://sts.windows.net/ but may also be like https://sts.windows.net/erconsult.eu or even https://erconsult.eu/ and refers to the Azure tenant. Apparently, the syntax depends on who owns the tenant and whether your AAD is trusted by the AAD of your client.
    NETWORKALIASname.surname@yourdomain.xyz
    This is your [e-mail] account in the Office 365 tenant.
    DEFAULTPARTITION1
    Set to “1”.
    IDENTITYPROVIDER“”
    This can be the same https://sts.windows.net/ or a https://sts.windows.net/ab123456-123a-456b-789c-abcde1234567/ address, where the GUID at the end is the tenant id of your Office 365 subscription (see https://www.whatismytenantid.com/). From experience, you may keep it blank.
    OBJECTIID“”
    This seems to be a GUID of your user in the Active Directory. Keep it blank, the system populates it on the first logon automatically.
    EXTERNALUSER
    EXTERNALID
    0
    “”
    Whatever that is, you can keep the 2 columns empty. Upon the first logon the system is going to set EXTERNALUSER = 1, and EXTERNALID = some alphanumeric value.
  5. Update the USERINFO record and try to connect to the D365 Web application. Experiment with the SID and the NETWORKDOMAIN if it doesn’t work.