Pre-Onboarding Checklist (BC365)

confirm administrator access in order to install your bank's business central integration for cloud ( https //urldefense proofpoint com/v2/url?u=http 3a dynamics com\&d=dwqfaq\&c=eugzstcatdllvimen8b7jxrwqof v5a cdpgnvfiimm\&r=j25mqvooxbwmzp6puiltqcoq31reytt3nxzd2cxgxf4\&m=jyvgjieiqux859vsruwmtk22pnasewkjgtzmov6tj8s\&s=fjqp21btrgpxtitrms8umfdml9cqp3e qmvsjzxeikc\&e= ), the installing user is required to have the cloud application administrator role within their microsoft active directory profile you also must have a business central license (premium or essentials) please request that your microsoft administrator apply this role before proceeding the installation cannot be completed without this role ensure the microsoft azure admin is present on the onboarding call, or that someone on the call has the necessary permissions to install extensions and manage permissions compatible business central version please verify that you are on the cloud (dynamics com) version of business central and that you are running version 18 or later the business central version can be found by selecting the (?) icon in the top right when logged in select help & support found under the other resources section scroll to find the troubleshooting section and observe the platform version for example, 21 0 53597 54893 describes a system on major version 21 for more information, visit the https //learn microsoft com/en us/dynamics365/business central/dev itpro/administration/version numbers support multiple companies if the organization has multiple companies, you should be utilizing multi entity management (mem) by binary stream if they are not using mem, we cannot onboard you at this time if using mem, please note that users will not be able to write into the check ledger entries batch payments overwrite the "doc no " for check payments compatible third party solutions is your organization using any third party integrations or extensions? extensions that impact core cash management pages or vendor objects will likely cause conflicts there are known compatible solutions that include mem by binary stream and lanham (edi, e ship, e receive) note your approval processes if you have an invoice/payment approval process in business central, it may interfere with the plugin's expected behavior please identify this early so we can determine the correct testing scenarios to ensure the plugin works alongside their specific approval workflow using business central's remit feature using business central's remit to code on a bill does not impact the success of the payment however, the specific remit address set in business central is not picked up by the plugin the payment will be issued to the address on the vendor card instead configure payment journals does every company within the production environment have a payment journal configured? if any company lacks a configured payment journal, the plugin installation will fail—even if you only intend to use bank feeds please confirm this for each company before installation review known limitations please review the following limitations to ensure they align with your business needs multiple extensions or scheduled jobs microsoft limits the number of api calls a single user can make within a specific time range if the client has multiple extensions or scheduled jobs making a high volume of api calls, they may conflict with the plugin we highly recommend testing in a sandbox with all extensions and scheduled jobs running to ensure full compatibility credit memos credit memos cannot be applied at the time of payment via the plugin to have credits appear at the time of payment, please apply the credit memo to the posted purchase invoice before making the payment this can be done through the vendor ledger entries or by using the applies to doc no method azure government cloud the plugin is not hosted on azure and currently does not meet azure government cloud requirements support for non ap payments the plugin currently only supports payments to posted purchase invoices other payment types (e g , customer refunds, employee expenses) are not supported