1. Home
  2. Bluefort Enterprise
  3. Getting Started
  4. Understanding the LISA BusinessPro dependencies on Microsoft Dynamics 365 Finance and Supply Chain Management

Understanding the LISA BusinessPro dependencies on Microsoft Dynamics 365 Finance and Supply Chain Management

LISA BusinessPro is a Dynamics 365 Finance and Operations app and thus depends on at least one of the FinOps SKUs to be deployed, the preferred one
being Dynamics 365 Finance.

Since LISA BusinessPro leverages and extends products, released products and related products Dynamics 365 Supply Chain licensing is also required.

Integrations

LISA BusinessPro also integrates with the following Dynamics 365 products:

  1. Dynamics 365 Commerce
  2. Dynamics 365 Project Operations

The above integrations are optional add-ons that might require an add-on license commerce agreement to be purchased.

LISA BusinessPro Integrates with the following standard FinOps modules:

  • Organisation Administration
  • General Ledger
  • Sales Ledger
  • Purchase Ledger
  • Product Information Management
  • Credit and collections
  • Procurement and sourcing
  • Pricing management
  • Tax
  • Subscription Billing
  • Revenue Recognition (to be deprecated by Microsoft in 2023)
  • Retail and Commerce
  • Project Management and Accounting
  • Asset Management

Pre-requisite standard D365 setup:

  • Organisation Administration Module (Legal Entities)
  • General Ledger module
  • Payment journal names
  • Reason Codes
  • General Ledger journal names for accrual scheme posting (optional)
  • Accrual schemes (optional)
  • Revenue recognition module (optional)
  • Revenue and expense deferrals (optional)
  • Products
  • Released Products
  • Sales Tax (VAT)
  • Customers
  • Vendors
  • Currencies
  • Unit of Measures
  • Sales and Purchase Trade Agreements (optional)
  • Modern Design Reports – It is recommended to make the customer Sales
  • Invoice Report point towards the BFT template which comes as part of the LISA deployable package.

Parameters

Note-worthy standard Dynamics 365 Finance and Operations parameters

Accounts receivable (Sales Ledger) -> Setup -> Accounts receivable (Sales Ledger) parameters -> General -> Sales Default Values -> Order type.

For the LISA actions to be fully firmed and successfully posted the above field has to be set to “Sales order”. If for example, it is set to “Journal” this has to be set to “Sales order” manually before the LISA action can be posted. This is because standard functionality stops you from confirming and posting a sales order of type journal.

Procurement and Sourcing (Purchase Ledger) -> Setup -> Procurement and Sourcing (Purchase Ledger) parameters -> General -> Purchase Default Values
-> Order type.

For the LISA actions to be fully firmed and successfully posted the above field has to be set to “Purchase order”. If for example, it is set to “Journal” this has to be set to “Purchase order” manually before the LISA action can be posted.

This is because standard functionality stops you from confirming and posting a purchase order of type journal.

For smooth posting of actions it is recommended to set the “Enable invoice matching validation” field to false in the Accounts payable (Purchase ledger) parameters -> Setup options to validate invoices -> Invoice validation tab.

If the above policies are needed for other non-subscription process in the system then ensure to disable the invoice matching on a more granular level such as products or suppliers not involved in the subscription management module.

For more information about how to configure this functionality for your organization please visit this standard Microsoft Docs link.

Updated on December 19, 2023

Was this article helpful?

Related Articles

Leave a Comment