Introduction: Electronic payment to vendors can be done using Navision 2017. This reduces manual work and also errors that can be caused during payment. After specifying the payment details in the payment journal, the file can be exported. This file then has to be transmitted and uploaded to the bank to process the payment. Once it is confirmed that the payment is received and processed by the bank, it has to be posted. The details of the exported file are visible in Credit transfer registers. This helps to find what has been exported and by whom. In this article, we will be demonstrating steps required for doing Electronic Payment to vendors. Prerequisite: Microsoft Dynamics Navision 2017 Purpose of the setup: Our goal is to do Electronic payment to Vendors for their unpaid Invoices in Navision. Steps: Electronic Payment to Vendors basically consists of the following steps: Setup Setup the bank account Bank account needs to be setup to do payments. In order to be able to use credit transfers with this bank account, SWIFT code and IBAN should be valid. Payment export format should be SEPACT. Setup the vendor along with appropriate bank account details Go to bank accounts of the vendor. Make sure valid Swift code and IBAN is assigned. Choose preferred bank account for this vendor. Generate Electronic payment We will be creating a new General Journal Batch. Bal. account type should be ‘Bank Account’. Bal. Account no. is the Account from which payment will be done to the vendor. Allow Payment export should be selected. Select the newly created batch as the ‘Batch Name’. ‘Applies to Doc. Type’ should be selected as ‘Invoice’. When ‘Applies to Doc. No.’ is clicked, a list of all the unpaid invoices for this vendor will be displayed. The invoice for which Electronic payment has to be done is selected. Export Electronic payment When you are ready to post payments to your vendors using the payment journal, you can export a file with the payment information on the journal lines. Transmit Electronic payment The bank payment file is exported to the location that you specify, and you can proceed to upload it to your electronic bank account and make the actual payments. When you receive confirmation that the payments are successfully processed in the bank, you can post the exported payment journal lines. Post Electronic payment Payments should not be posted until it is confirmed from the bank that the payment is received. Once it is posted, check the vendor ledger entries of the vendor for which the payment is made. Select the payment which is made and click on applied Entries. The vendor invoice for which this particular Electronic payment is done will be displayed and vice versa is applicable. The GL Entries for this particular vendor will be visible by selecting the Payment and then clicking on ‘Navigate’ in the ribbon. The amount has been deducted from our bank account and added to the vendor bank account. In the credit transfer register, the details of the exported file will be visible. Conclusion: Thus, Electronic payment is a very beneficial way of doing payments to vendors since it makes the entire process of doing payment easier and faster. Also, all the exported files history can be viewed anytime as it gets saved in the Credit transfer registers.  

Introduction: The NAV 2017 has a new feature that uses OCR technology with added item line capture functionality to automate the data entry process for vendor invoices. OCR is an abbreviation for Optical Character Recognition. Lexmark ICS (Invoice Capture Service) provides OCR Services in NAV 2017. The OCR Service feature enables the user to take a picture of a vendor invoice document, sends it to Lexmark ICS Corp. and then imports the invoice back into NAV with the captured details. This saves a lot of time spent on manual entry of data into the system. In this article, we will see how to set up and implement OCR Services in NAV 2017 in three different ways. Prerequisite: Microsoft Dynamics NAV 2017. Lexmark ICS login credentials. Purpose of the Setup: Our goal is to setup and implement the three different ways of using OCR Services in MS Dynamics NAV 2017. Steps: OCR Service by Manual Process: The User will click on Incoming Document option or type ‘Incoming Documents’ to open the Incoming document page. User will have to upload the Document(PDF/Image) that is to be used in the OCR Service by clicking on ‘Create from File’ option which will upload the file to the ‘Main Attachments’ of the Incoming Document in   NAV. To Send the document to the OCR Service the user will have to click on the Send to ‘OCR Service’ option. After waiting for some time till the document processing is completed, User will click in the Receive form OCR Service. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Image 1.1 Process from uploading to sending the document using OCR Service in NAV Image 1.2 Process of receiving to creating the document using OCR Service in NAV OCR Service Using NAV Phone Application: In this case of using OCR Service the User uses a camera application instead of manually receiving the document. The User takes a picture of the Invoice Document. (‘Office Lens’ is a The User will upload the document file(Image) into the Incoming Documents in the NAV mobile app. User will then click on Send to OCR Service option once the document is successfully uploaded. After waiting for some time till the document processing is completed, User will click in the. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Image 2.1 Process of Sending Document in OCR Service using NAV Phone Application Image 2.2 Process of Receiving Document OCR Service using NAV Phone Application OCR Service using Email Feature OCR Services can also be performed by sending an Email. Over here the user Emails the softcopy of the Invoice Document as an attachment to the Lexmark ICS Corp. (Note: the user in this case send the email to Lexmark corp. on the email address provided by Lexmark when the user completes the registration on the Lexmark website.) An Incoming document is automatically inserted into the Incoming Document Page once it is processed by Lexmark Corp. (OCR Service Provider) in NAV. The incoming document is already processed when it is created. So User needs to Click on Receive from OCR Service. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Conclusion: The OCR Service in NAV 2017 has benefited by reducing the amount of time spent in the manual work of data entry. The more the OCR Service system is trained the more accurate results can also be obtained. The best use of OCR Service in NAV 2017 is capturing of line items in the document sent to OCR Services.  

Introduction User security can be achieved by assigning different permission sets to users. Permissions can be assigned to users as per their role. A permission set is a collection of database permissions for one or more objects in the Microsoft Dynamics NAV database and Dynamics 365 Financials that you can assign to one or more users. This article summarizes User security capabilities and differences in Navision 2017 and Dynamics 365 Financials. And can be used as guide when evaluating which platform to select for an implementation, when you have specific security requirements. We have implemented User Security for our Client Titan Labs. You can read its case study here. The following is a Scenario for a Sales User: Administrator User having Super permissions creates a Sales user who will have access to only Sales, Customers and Items. Other information on Finance, Purchase etc. should be hidden from this Sales user. Prerequisite: 1. Microsoft Dynamics Navision 2017 2. Microsoft Dynamics 365 Financials. User Security in NAV 2017 In Navision 2017, Administrator user having Super Permissions creates a new permission sets which include access to only those objects i.e. tables, pages etc. which the user should access. E.g. A sales user can access sales orders, sales quotes etc. The new permission set created is assigned to the user. This will ensure that the user does not have permissions to access any tables, pages or any other objects regarding finance, purchase etc. Depending on the setting in theUI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only UI elements on objects in the license or on objects that the user has permissions to will appear in the user interface. LicenseFileAndUserPermissions is selected for the UI Elements Removal field in the NAV Server Instance. This ensures that a UI element is removed if the related object is not included in the license file and the user does not have permissions to the object as defined in the AccessByPermission property for the related UI element. A copy of permission sets can be created and edited. Dynamics 365 Financials In Microsoft Dynamics 365 Financials, the Administrator user having super permission can create users in the Admin centre but only the default permission sets available in Dynamics 365 Financials can be assigned to the users, it is not possible to edit or add to the existing Permission Sets. Permissions Sets are assigned to each user in the User Card either by directly adding them or by associating a User Group which has Permissions sets assigned. It is suggested to give D365 BASIC permission set to all users. This will allow users to get into Dynamics 365 for financials and open the home page without permission errors. It does give READ (but not INSERT, MODIFY, or DELETE) access. Sales User is assigned a Predefined User group D365 Sales. This user has following permissions D365 BASIC D365 CUSTOMER EDIT D365 CUSTOMER, VIEW D365 ITEM, EDIT D365 ITEM, VIEW D365 SALES DOC, EDIT D365 SALES DOC, POST D365 DYN CRM MGT, LOCAL After assigning D365 Sales User Group to the Sales User, the Role Centre displays information with respect to the User group assigned i.e. D365 Sales but the User will still have access to Information like Finance, Purchase etc. when he tries to find it using the search bar which actually should be disabled. A copy of permission sets cannot be created. Permission error is displayed. Error displayed while creating new permission set. Note: The above error was raised at Dynamics 365 Business edition community, and we received a response from Microsoft employee that the functionality to fine-tune permissions for users will be added in a future update. Conclusion Microsoft Dynamics Navision 2017 allows an Administrator user to create Users with limited permissions by creating new permission sets and assigning it to the User. Dynamics 365 Financials allows an Administrator user to create Users but is not allowed to create new permissions sets. The default permissions sets can only be assigned to the User.