This is the first article in a guide that will walk you through the process of connecting Moss and Microsoft Dynamics 365 Business Central SaaS / Cloud (MS BC). If you follow this guide step by step, you will have successfully connected Moss and MS BC by the end.
Purpose of this article:
This article guides you through the steps you need to take before connecting Moss and MS BC. In order to sync data between Moss and MS BC, you will have to create a Moss Wallet GL account and a Moss Payment Journal, a dummy supplier account for transactions and give the right user the necessary permissions. This ensures that the data flow works from day one, without queries or manual corrections.
Supported systems:
Moss only integrates via API with Microsoft Dynamics 365 Business Central (Cloud / SaaS). The following systems are not supported by this API, but can be used in combination with CSV exports / scheduled SFTP downloads:
Microsoft Dynamics Business Central on-premise
Microsoft Dynamics Finance & Operations
Microsoft Dynamics Navision (on-premise / older versions)
Checklist (before you connect)
Ensure right level of user permissions, access rights & licenses are granted. A user must have an active BC license, we recommend Super rights in BC and Azure Global Administrator rights to connect the API.
Create a Moss Balance GL Account (e.g. Bank Account) in BC
Create a Payment Journal for Moss payments (e.g., MOSS_Wallet)
Create a "Default supplier" (“Collective Vendor”) for Moss card transactions without a specific vendor (e.g., MOSS DEFAULT SUPPLIER)
Authorizations & Required Permissions
The Moss API is authorized using an existing Microsoft Dynamics 365 Business Central user.
Detailed authorizations and required permissions
Detailed authorizations and required permissions
Business Central user requirements
The user must have an active Business Central license.
The license must remain assigned for as long as the integration is in use.
⚠️Removing the license will break the integration.
Azure AD application approval
To complete the connection, the Moss Finance Application must be approved in Azure Active Directory.
This approval requires an Azure Global Administrator.
If the user initiating the connection does not have Global Administrator rights, an Azure administrator must:
Review the consent request
Approve the application in the Azure Portal
The integration cannot be completed until this approval is granted.
Business Central permissions
We recommend that the user authorizing the API has SUPER permissions in Business Central.
This avoids issues caused by missing permissions during setup and runtime.
If you prefer a more restrictive permission model, you can assign permissions explicitly.
In that case, use the technical API documentation as guidance for:
Required endpoints
Required tables and operations used by the integration
Extension upload permission
The Moss integration uploads a Business Central extension automatically via the API to extend the integration scope.
For this step, the authorizing user additionally requires the following permission:
TableData 5447 "API Extension Upload" = IndirectInsert
(Exclude_APIV2_)
This extension is required for advanced integration capabilities.
Detailed technical behavior and scope are documented in the technical API documentation.
Creating a Moss Wallet GL Account
To correctly reflect Moss transactions in Microsoft Dynamics 365 Business Central (credit card transactions and/or wallet payments), you must create an account that represents your Moss Wallet balance.
This account:
Increases with wallet top-ups
Decreases with payments made from the Moss Wallet
⚠️ Important note for Moss Credit customers
If you are a Moss Credit customer and want to use:
Wallet payments for AP invoices or employee reimbursements, and
Moss credit cards
you must create two separate accounts:
One account for wallet payments
One account for credit card payments
The Moss credit line is only used for credit card transactions, not for wallet-based payments.
How to create a Moss Wallet GL account
How to create a Moss Wallet GL account
There are two ways in which you can set up the Moss Wallet
Moss Wallet as a Bank account (recommended)
We recommend setting up the Moss Wallet as a Bank Account in Business Central. This provides better visibility and aligns with how balances and cash movements are typically modeled.
Open “Search”, then go to “Bank Accounts”
Create a new Bank Account and Enter:
Bank Account No.: You may use your Moss top-up bank details
Bank Account Posting Group: Select a posting group that links the bank account to the appropriate G/L account
Alternative setup: G/L Account
If you do not want to use a Bank Account, you can alternatively create a G/L account to represent the Moss Wallet balance.
Open "Finance" then go to "Chart of Accounts"
Now create a Balance Sheet G/L account.
Configure the account as follows:
Direct Posting: Enabled (required for API usage)
Reconciliation Account: Disabled
⚠️ Do not enable Reconciliation Account.
Moss does not support Business Central’s bank reconciliation functionality.
Create a new Payment Journal
To record Moss Wallet payments in Business Central, you must create a dedicated Payment Journal.
Moss will:
Post wallet payment entries directly into this journal via the API
Automatically reconcile payments against expenses (e.g. Purchase Invoices) when the journal is posted in Business Central, using the Moss API extension
How to create a new Payment Journal
How to create a new Payment Journal
Open "Cash Management", go to "Payment Journals"
Recommended configuration
Name: Moss Wallet Payments (or similar, clearly identifiable)
Balance Account Type:
Bank Account → if you created the Moss Wallet as a Bank Account
G/L Account → if you created the Moss Wallet as a G/L account
Balance Account No.:
Select the Moss Wallet account created in the previous step
This journal will be used exclusively for automated Moss Wallet postings.
Create a Moss Default Supplier
All Moss Credit Card Transactions can be posted against a single “Default Supplier” in MS BC. Alternatively, you can post transactions against the respective supplier accounts of the merchants you pay or apply a hybrid approach where only larger transactions are posted against specific suppliers while smaller expenses get posted against the single credit card supplier.
⚠️ This account is also used to post Moss currency conversion fees or bank transaction fees if you pay invoices and reimbursements from your Moss Wallet.
You can leave the VAT Business Posting group for the collective supplier blank and code the VAT scenario per transaction if you want to use this vendor for all or many different credit card transactions.
You have finished the preparations.
You are now ready to start connection Moss and MSBC.