How to Update Business Central GL Accounts in the Paystand Dashboard

Article type: How-to

Audience: Paystand Dashboard admins updating Business Central GL account mappings

Last reviewed: August 17, 2026

__________________________________________________

Summary

Use this guide to change the Business Central GL account where Paystand posts merchant fees, discounts, convenience fees, adjustments, disputes, or refunds.

For the example covered here, change GL account for Convenience Fees from 40998 to 64900. Leave all other connection settings unchanged. You must paste the existing Azure client secret Value into Client Value before the form can be saved.

If you do not have that Value, first follow Find Your Existing Business Central Client Value. Azure cannot display the existing secret Value.

__________________________________________________

Before you begin

• Paystand role: Dashboard Admin who can open and save Integrations
• Business Central access: User who can confirm the target account in Chart of Accounts
• Existing Client Value: Retrieve it from your organization’s secure storage using Find Your Existing Business Central Client Value
• Accounting approval: Confirm the new G/L account is correct for convenience fees

Do not change Environment, Company Name, Tenant Name, bank account IDs, Client ID, or any other GL mapping unless that is part of your approved change.

__________________________________________________

Step 1 — Validate the target G/L account in Business Central

1. In Business Central, open Chart of Accounts.
2. Find the target account (for this example, 64900).
3. Confirm with your controller or accountant that it is the correct account for convenience fees.
4. Confirm the account is not blocked and supports the posting setup your organization requires.

Important: Do not enable Direct Posting on every G/L account. Fee accounts that receive Paystand journal-style postings may require Direct Posting = Yes, while bank posting-group control accounts often should remain No. Follow your accounting policy.

__________________________________________________

Step 2 — Open the Business Central connection in Paystand

1. Sign in to the Paystand Dashboard as an Admin.
2. Go to Integrations. If a submenu opens, select Integrations again.
3. Scroll to Microsoft Dynamics 365 Business Central.
4. Confirm status is Connected.
5. Click Connect To Business Central to expand the form.

__________________________________________________

Step 3 — Change only the approved GL mapping

1. Locate GL account for Convenience Fees.
2. Replace 40998 with 64900.
3. Review the rest of the form and confirm every other value remains unchanged.

The same workflow can be used for another approved GL mapping change, but always change only the intended field.

__________________________________________________

Step 4 — Enter Client Value and save

1. Confirm Client ID remains unchanged.
2. Paste the existing client secret Value into Client Value. Do not paste Azure Secret ID.
3. Click Connect To Business Central.
4. Wait for the confirmation message Connected to Business Central.
5. Confirm the integration status remains Connected.

If Client Value is unavailable, stop and follow Find Your Existing Business Central Client Value. Do not create a new secret solely to complete this change without coordinating with IT.

__________________________________________________

Step 5 — Verify the change

1. Reopen Connect To Business Central.
2. Confirm GL account for Convenience Fees now shows 64900.
3. Confirm all other connection fields are unchanged.
4. For end-to-end validation, process a sandbox convenience-fee payment or verify the next new convenience-fee posting in Business Central.

Scope: The new mapping applies to new postings. Existing entries already posted to 40998 are not moved automatically.

__________________________________________________

Troubleshooting

Save / Connect remains disabled
A required field is empty—usually Client Value. Paste the existing secret Value and confirm all required fields are populated.

Authentication fails
Confirm that you pasted the client secret Value, not Azure Secret ID. If the Value is unavailable, follow Find Your Existing Business Central Client Value.

The form saves, but convenience-fee posting fails
Confirm account 64900 exists, is not blocked, and is configured according to your Business Central posting policy. Contact Paystand Support if the new posting remains stuck after the configuration is corrected.

__________________________________________________

Related articles

• Find Your Existing Business Central Client Value
• Create or Update the Business Central Client Secret (Azure + Paystand Dashboard) — only if the existing Value cannot be found or the secret has expired