While electronic methods of payment are becoming increasingly popular everywhere for quick payments, check payments are still popular across the world, especially post dated checks, which can be cashed out only after a specified date, giving them an edge over electronic payment methods. D365 Finance has a very simple process to create post dated checks and account their entries.  Since post dated checks are cleared after a certain date, known as the maturity date, the amount is not directly accounted in the bank account, but to a bridging account instead. A bridging account serves as a ‘bridge’, for the transaction amount between the bank account and the vendor/customer account till the maturity date of the PDC. When a payment entry with a PDC is made, the system will store the amount temporarily in the bridging account till the maturity date. On the maturity date, the system will transfer the amount from the bridging account in the bank account. The accounting process of the PDC is summarized below: – For Vendor:- PDC (Before Maturity) Dr Cr Vendor XX   Bridging Account   XX PDC (After maturity) Dr Cr Bridging Account XX   Bank   XX For Customer: PDC (Before Maturity) Dr Cr Customer   XX Bridging Account XX   PDC (After maturity) Dr Cr Bridging Account   XX Bank XX   The steps to set up and use PDC are as follows: – 7. Select the Account type as Bank. 8. Enable the parameters for Bridging posting and Post Dated check clearing posting. 9. The bridge account gets selected automatically by default based on the one defined in the Cash & Bank management parameters defined earlier. 10. Do the exactly same setup in AR module -> Methods of payment as well. This concludes the setup part. Now we can proceed with the transactions. Process: – Go to Postdated Checks tab and enter the maturity date for the PDC. Until the maturity date is reached, we cannot settle the PDC. So either we can wait till that date or for the sake of testing purposes, we can set the system clock to a future date. This concludes the configuration and process for PDC in D365 Finance.

Australia based Kloudify Technologies has partnered with CloudFronts to introduce the D365 Sales Quick Start Programme, which is expected to improve sales capabilities for their client in the talent solutions industry. Through this partnership, Microsoft Dynamics 365 Sales Quick Start will be used to provide the talent solution organisation with an expedited and effective onboarding process. Kloudify Technologies is a Microsoft Gold Partner and the leading provider of Microsoft productivity solutions and cyber security services in Australia, helping small and medium enterprises modernise their technology by implementing Microsoft solutions and increasing their efficiency and competitiveness. Learn more about Kloudify Technologies at https://kloudify.com/ The goal of CloudFronts is to align Microsoft Dynamics 365 Sales features with the needs and requirements of the client. The collaboration focuses on expediting the onboarding process and ensuring a rapid integration of D365 Sales into their existing systems by offering the client an accelerated timeline for implementation to quickly leverage the benefits of the Microsoft Dynamics platform. On this occasion, Priyesh Wagh, Dynamics 365 Practice Manager at CloudFronts, said, “We are excited about the possibilities that this partnership opens up. The D365 Sales Quick Start Program is designed to bring immediate value to the organisation, and our collaboration with Kloudify Technologies ensures a seamless and effective implementation of Microsoft Dynamics 365 Sales.” About CloudFronts  CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S. Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.  Please feel free to connect with us at transform@cloudfronts.com

In any ERP, any accounting user might want to set up periodic journals on a monthly/quarterly/year basis for recording the costs of any services, like AMC charges, rents, subscription fees, etc. It can get tedious to manually create such entries every single time indefinitely. This can lead to errors and unnecessary time consumption if the entries are very long and made to multiple business partners. Dynamic 365 Finance offers an easy way out through the use of periodic journals. Periodic journals help the user create entries periodically in the system. With periodic journals, users can: The process of configuring and using periodic entries is very simple. Setup 1. First, configure a journal name with the Journal type as ‘Periodic’ as shown below: 2. Then go to General Journal -> Journal Entries -> Periodic Journals Here, we define the template for the periodic journal entry to be created in future. Create a new entry. 3. Select the date on which you want the periodic journal entry to be created. 4. Select the GL accounts and their amounts. You can create a single line journal entry with an offset account or you can create a multi-line entry with as many GL accounts as required. 5. Select the Unit. Unit stands for the period of the journal entry – days, months or years. 6. Enter the number of units. This is the frequency of recurrence of the journal entry. For e.g., if you select Unit as months and enter the number of units as 3, then the periodic journal entry will be set to repeat every 3 months from the beginning date. Working 1. Open a General Journal entry. 2. Create a new entry. 3. On the top, click on Period Journal. 4. There are 2 options – Retrieve Journal and Save Journal. Retrieve journal is used for retrieving a periodic journal that we have just setup. Save journal is used if you want to save any existing journal entry as a template for a future periodic journal entry. 5. We use Retrieve Journal to retrieve the template we have created above. 6. In the ‘To Date’, enter the date of recurrence, i.e., the date for which the entry repeats for the period. In the Periodic Journal number, select the Periodic Journal which was created earlier. In the last field, there are 2 options – Copy or Move. Copy will fetch the periodic journal data into the journal entry and update it for use in the next period. Move will also fetch the journal data but will block the periodic journal from being used in future. Use the move option if you know that the periodic journal is not going to be used anymore. 7. The system will load the data as shown below:- 8. As you may notice, the date field is as per the date selected in the Retrieve Periodic Journal, while all the other details like the GL account and amounts are fetched exactly as per the template. 9. Once you post this journal entry, the journal date in the periodic journal template will be updated to the next period, in this case, to 1st of December. 10. In order to check if the date has been updated or not, simply go to the Periodic Journal once more and check the date. As you may have noticed, the date got updated to the next period of recurrence. So when you retrieve this journal for the next time, it will fetch the journal based on this date. This can go on as many times until you select the option to Move instead of Copy. After that, the periodic journal will stop updating and won’t be able to be used again. Through this process, the user can fetch the journal entries periodically instead of creating them manually every time. While the fetching of the data is automatic, the user will have to make sure to run the periodic journals as per their dates. There is an option to automatically generate the entries in the system through Power Automate but that is a separate Add-on to be setup and configured. The standard process is just as good enough to reduce the hassle for making entries manually every period.

Introduction In any accounting software, it is always important to keep track of all real-time bank transactions and record them in the ERP. Since bank transactions are booked manually in the ERP, it is necessary to ensure that the bank statements and ERP records are matched on any given date. This is where bank reconciliation comes into play. Bank Reconciliation Bank reconciliation is an activity done by any finance user for the purpose of reconciling book transactions w.r.t bank statements and ensuring that both are as closely matched as possible. D365 Finance offers two ways of performing bank reconciliations. One is by entering the bank statement amount manually and reconciling the ERP statements for each record against the amount. The other is by importing the bank statement into the system and letting the system match the records of the statement against the ERP based on a certain criteria. The blog is made with the assumption that the reader is already aware of the manual bank reconciliation process in D365 Finance. The second method is undoubtedly easier, flexible, and time-saving for any user. While there are several widely used bank statement format types which can be processed in D365 Finance like MT490, CAMT.054, BAI2 and others, this blog post will be focused on the MT490 format only. Moreover, D365 Finance also enables the user to reconcile not only payments/receipts, but also transactions from the bank’s side, like bank charges, interest fees or reversals and post those entries into the ledger automatically. There is also a flexibility to create a set of rules that can allow for minor amount/date variations of the system w.r.t the bank statement. Steps to perform the bank reconciliation in an automated manner Setup We have to enable the system to accept bank statements in MT940 statement first. In order to do that, navigate to, Organization Administration > Workspaces > Electronic Reporting Click on Repositories. Select Global and click Open on top. Filter the Configuration name by searching for ‘MT940’. The above list of formats will be displayed. Select them all and click on Import. The system will import the bank formats in D365 Finance. Next, we have to map the format in a setup. Go to Cash & Bank Management > Advanced Bank Reconciliation Setup > Bank Statement Format Create a new record and specify the Statement Code, Name and map the Import format which was imported in the previous step. Now this is done, the only part left is to configure the Bank master to enable advanced bank reconciliations for any transactions. Open the Bank Account Master. Turn on ‘Advanced Bank Reconciliation’ and select MT940 in the field Statement format. Once this is done, we are ready to use Advanced Bank Reconciliation. Working To start with advanced reconciliation, we will take a scenario of a bank where the following transactions have occurred: The above 3 transactions are created in the system and will be reconciled with the use of a bank statement. The bank statement will be a notepad file that will be imported in the system. While the bank statement is always provided by the bank, it is important to know the bank statement format so we can setup and test any scenario with dummy records. The above screenshot specifies the structure in which the bank statement is accepted by the system. We will be using this format to import bank records and reconcile them with the system records. From the above image, 3 types of bank transactions have been made in the system with the respective amounts and dates. Now the bank statement file for the above transactions is as follows: As you may observe, all three transactions are recorded one below the other, and the opening and closing figures are manually entered here. In real-time scenarios, this is provided by the bank and the user does not open or make any changes to the file. In order to import the file, go to Bank Account > Bank Statements > Import Statement In the parameters, select the bank account, browse the text file from your PC and click on upload, then click on OK. The bank statement is imported with the above transactions. Select the transactions and click on Validate on top. Now we proceed with the reconciliation. Go back and click on Bank Reconciliation in the Bank Account screen. Create a new reconciliation. Then click on Worksheet at the top. The reconciliation screen is opened. Here, the user is presented with the option to manually match any record to reconcile or let the system match the records based on a certain matching rule. While any variation of rules can be defined, the most commonly used rules are: Based on the above, we will define a matching rule based on date and amount difference and re-import the statement. To define a matching rule, navigate to Cash & Bank Management > Advanced Bank Reconciliation Setup > Reconciliation Matching Rules Based on the above image, the criteria for the match amount and match date is defined where a variation of 2 INR and 3 days will be allowed in reconciliation. Once it is saved, click on Activate. Next, navigate to Cash & Bank Management > Advanced Bank Reconciliation Setup > Reconciliation Matching Rule Sets Create a new rule set and link the matching rule that was created earlier. As you may observe, we can link multiple rules here. This is useful when it is necessary to reconcile statements with a variety of rules instead of a single rule. Next, go to Bank Account > Scroll down to Reconcilation section and link the matching rule set in the Default Matching Rule Set Now we are ready to run the reconciliation once more with some variations of amounts and days in the bank statement. Import the statement once more and validate it. The bank statement is imported as follows: Now create a reconciliation worksheet. On the top, select the option ‘Run Matching Rules’. Once the matching rules … Continue reading Advanced & Auto Bank Reconciliation in Dynamics 365 Finance →

Introduction Invoices and shipments are frequently handled differently by different businesses. Processes, for example, can range from one person posting everything on a purchase order to numerous employees working on their own sites. On the User Setup page, you can now select how each user can handle invoices. Steps to achieve the goal 1. Go to User Setup select the users you want to give this restriction and then there are two columns Sales Invoice publishing Policy and Purch. Invoice Posting Policy 2. There are three values in these options Below is the impact of the above three options in different documents of purchase and Sales transactions. Document Option 1: Allow Option 2: Prohibited Option 3: Mandatory   Displays a series of options Confirmation dialog Confirmation dialog Sales Order Ship Do you want to post the shipment? Do you want to post the shipment and invoice?   Invoice       Ship and Invoice     Sales Return Order Receive Do you want to post the receipt? Do you want to post the receipt and invoice?   Invoice       Receive and Invoice     Inventory Pick Ship Do you want to post the shipment? Do you want to post the shipment and invoice?   Ship and Invoice     Purchase Order Receive Do you want to post the receipt? Do you want to post the receipt and invoice?   Invoice       Receive and Invoice     Purchase Return Order Ship Do you want to post the shipment? Do you want to post the shipment and invoice?   Invoice       Ship and Invoice     Inventory Put-away Receive Do you want to post the receipt? Do you want to post the receipt and invoice?   Receive and Invoice     Warehouse Shipment Ship Do you want to post the shipment? Do you want to post the shipment and invoice?   Ship and Invoice     Note: If you are trying to post invoice transactions from the general journal the above restriction would not be used in the General journal table. Conclusion Thus we saw how we can restrict the users to post the purchase and sales transactions. Thank you very much for reading my work. I hope this helps!

References FlowFields – Business Central | Microsoft Learn Creating an RDL Layout Report – Business Central | Microsoft Learn Pre-requisites Microsoft Dynamics 365 Business Central Cloud/On-Premises Introduction In this blog, I am going to showcase how to flow Media (Picture) from one table to another and how to display it on the RDLC report. Flow Media data from one table to another table For this example, I’ve made a simple Mediadatatype table with a few fields and kept the ‘Image’ field as a Media data type. Additionally, I created the ‘Image’ field as a Media datatype to the Purchase header table extension and used the Fieldclass property as a flowfield and the Calcformula for the flow Image on the ‘Image’ field. The Image flows on the Purchase order ‘Image’ field, where my assigned user Id is PD, thus the image will appear on the Image field. How to display Media data type (Image) on RDLC report. In the following example, I’ve added an Image column to the MediaDatatype report Open the report on RDLC layout. On an Image property, select the image source as a database, use an ‘Image/bmp MIME type, and set the Image expression.      Output Conclusion Thus, we saw how to flow Media datatype from one table to another and how to display it on the RDLC report. I hope this helps!

Introduction In multi entity environment having separate legal entities for head quarter & regional entities, having separate sets of employees for each legal entity. & only head quarter employees taking decisions for which & how much inventory to be maintained at regional level & same employee having purchasing authority for all regional entities. In this case to keep track, post & report of what & how much purchase made for respective regional entity, need to create Purchase requisition for respective buying legal entity. i.e. USMF is headquarter entity & PM is regional entity. Problem Statement While creating Purchase requisition from headquarter employee’s login, it is created with buying legal entity as headquarter entity. i.e. Julia is employee of Headquarter USMF entity who will be going to issue Purchase requisition for regional entity PM. When Julia login in PM entity & create Purchase requisition then entity will automatically change to USMF. Solution Steps Follow below steps, in order to create Purchase requisition with buying legal entity as respective regional entity & to maintain all details on respective entity. 1. Select employee of headquarter which is going to issue Purchase requisition. i.e. select Julia in USMF entity – Go to Human resource -> Workers -> Employees -> 2. Select required employee. i.e. Julia – 3. Go to Work History 4. Click on Add employment to add respective entity to history. i.e. Add PM entity in Julia’s history 5. Add details of Legal entity i.e. Entity PM, Employment start date & click on Create employment. 6. History is added of PM entity Create Purchase Requisition Go to Procurement & sourcing -> Purchase requisitions -> All purchase requisitions & create new Purchase requisition from PM entity then Purchase requisition will be created for PM entity & window will not switch back to USMF. Now all Items added in this Purchase requisition will be ordered & maintained for PM entity.

In this blog, we are going to address the issue that can be seen in the recent update in Microsoft Dynamics 365 Finance & Supply Chain Management. To solve this issue please follow below steps. Currently If we see before the setup there is no tax information showing in Stock Transfer Transaction. Only the Administrator can see this Tax information. To overcome this issue, in Dynamics 365 F&SCM new update we have to enable “Private” field in the warehouse address tab. For this, Go to Inventory Management Setup->Inventory Breakdown->Warehouses. Go to Address. Click on Advanced. Right click In Address section and Click Add field. Add a field as “Private”. Once it is on the address section just disable the private field. By this every user will be able to see the Tax information on the Stock Transfer. After this, the user will be able to see the Tax Information on the Stock Transfer. That’s it for this blog. Thank you!!!

Introduction In this blog, I will demonstrate how to copy data between different companies using configuration worksheet. Previously we could only use Configuration packages or copy the company to copy data between companies. By using the Configuration worksheet users can copy data from specific tables in companies to their respective table in the current company. Pre-requisite Microsoft Dynamics 365 Business Central (On-premise/SaaS) Steps Globally search for “Configuration Worksheet” and click on the related link. Configuration Worksheet page opens up. Fill in the table you want to copy. Then click the ‘Copy Data from Company’ button on the action bar as shown in the below screenshot. Also, to use this function the ‘copy data from’ company table must have records and the ‘copy data to’ company table must have no records. A Pop- up page appears allowing the user to select the company from which data will be copied. The no. of records will be shown of the selected table. If the table selected has no records then the line won’t appear. If there are no issues, click on ‘Copy data’ action and a confirmation message will pop up before proceeding. A confirmation message pops up mentioning the data has been copied successfully. Other Actions Get Tables: Click on ‘Prepare’ on the action bar, there you will find the ‘Get Tables’ button. This lets the user add tables by using filters as shown in the below screenshot. Get related tables: User can find another button by clicking ‘Prepare’ and in that ‘Get related Tables’. This function adds all Vendor-related tables and fields anchored on other tables. Please note: Table relation with filtered view and conditional table relations are not considered here. Delete Duplicate lines: Users will find this button under the ‘Prepare’ action. This function deletes duplicated lines as shown in the below screenshot. The vendor line was repeated, by using this function it deleted duplicate lines. Conclusion: In this blog, we learned about copying data from multiple companies into the current company by using a configuration worksheet. Hope this helps!

Hi All, Did you know you can use JavaScript to trigger Power Automate flows and pass input data? So, I’ll show you how to do that, as well as how to pass strict structured data and dynamic schema in Power Automate. In the next blog, I’ll talk about Trigger Power Automate Flow using JavaScript – Bi-Directional Steps to follow for Initial Setup Step 1: Let’s create a Power Automate Flow and define the input JSON schema.Go to: Power Automate Create an Instant Flow with the trigger ‘When a HTTP request is received‘ Step 2: Let’s outline the input schema and then focus on the output in a ‘Compose’ block. I’ll describe two types of inputs. (Strict and Dynamic).Our strict schema will be identified by a specific pattern indicating how the input should be given.Our dynamic schema will be recognised by an unknown pattern, and input will not always be fixed. Click on ‘Use sample payload to generate schema’. Apply the following code, click on Done and you will see the schema in ‘Request Body JSON Schema’. Add a Compose Block to check the output of the request and save the Flow. URL will be generated and is ready to be used. Let’s now proceed to create JavaScript to trigger this flow Steps to follow for calling Flow using JavaScript Since I’ll show the code snippet, adjust it as per your use case. Note: Copy your HTTP Post URL from the trigger as it will be used in the JavaScript Step 1: Type the following code Step 2: Execute the JS with ‘TriggerFlow.Main()‘. Note: Make sure you pass Execution Context to the JS Step 3: Check your Power Automate Flow History and open the Run. That’s how Power Automate is triggered using JavaScript. Hope this has helped you 🙂 Next blog – Trigger Power Automate Flow using JavaScript – Bi-Directional