---
title: Pre-Onboarding Checklist (Business Central)
slug: santander/pre-onboarding-checklist-bc365
docTags: kOBW7Pa05SaMsJIm9Vdtp
createdAt: 2022-08-18T20:17:08.000Z
---

## Confirm Administrator Access

In order to install your bank's Business Central integration for Cloud ([Dynamics.com](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. 

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/z5uka4eCAfZR0DElCa8Te_-dynamics-365-business-central-2023-04-05-12-55-14.png" size="22" width="800" height="283" position="center" caption="Help icon - question mark" darkWidth="800" darkHeight="283" showCaption="true"}

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 [Microsoft Documentation on Version Numbers](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/version-numbers). 

***

## Support Multiple Companies

If your organization manages multiple companies in Business Central, you may be using Binary Stream’s Multi-Entity Management (MEM), a separately licensed add-on that helps manage multiple entities within a single environment. If MEM is not being used, each company will need to be onboarded individually. This means creating a separate Fusion profile and installing and configuring the Fusion plug-in for each company’s Business Central environment.

If you are 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 plugin does not pick up the specific Remit Address, nor does it update the Vendor Card. The payment will still be issued to the address on the Vendor Card, rather than the address added to the bill.

***

## 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.

***

## Confirm Hardware & Software Requirements

**Browser support (minimum versions):**

- Chrome: 65
- Firefox: 66
- Safari: 12
- Edge: 79

**Operating systems (minimum versions):**

- Windows 7
- macOS - El Capitan

**Minimum screen resolution:**

- 1200x800px