Article type: How-to
Audience: Paystand Dashboard admins and IT or security teams that maintain the Business Central integration
Last reviewed: August 17, 2026
__________________________________________________
Summary
The Paystand Business Central form requires Client Value whenever you save connection settings. Client Value is the Microsoft Entra ID client secret Value that was shown once when the secret was created.
You cannot retrieve the current secret Value from Microsoft Azure or from the Paystand Dashboard. Retrieve it from your organization’s password manager, secrets vault, or implementation records. Azure can show the app’s Application (client) ID and secret metadata (description and expiration), but not the current secret Value.
Do not create a new secret just to save a GL account change. Rotation can affect other systems that use the same app registration.
__________________________________________________
Before you begin
- Paystand role: Dashboard Admin who can open Integrations
- Internal access: Permission to view your organization’s password manager or secrets vault, or help from the IT/security owner
- Optional Azure access: Application owner or an Entra administrator who can inspect the Paystand app registration
__________________________________________________
Step 1 — Check where your organization stored the Value
Ask your IT, security, or implementation owner to search these locations:
- Company password manager or secrets vault
- Business Central implementation runbook or onboarding checklist
- Secure implementation records created when the Entra app was registered
Use search terms such as Paystand, Business Central, Client Value, or client secret.
Security: Do not send the Value through email, chat, screenshots, or a support ticket. Keep it in approved secure storage.
__________________________________________________
Step 2 — Know what Azure can and cannot show
In Microsoft Entra ID, open App registrations → Paystand → Certificates & secrets → Client secrets.
- Azure can show: secret description, expiration date, Secret ID, and the app’s Application (client) ID
- Azure cannot show: the existing client secret Value after its creation screen has been closed
- Do not use: Secret ID as Client Value; they are different values
This screen is useful only to confirm that a non-expired secret exists. It cannot recover or verify the stored Value.
__________________________________________________
Step 3 — Confirm why the Paystand field is blank
Paystand does not redisplay a saved Client Value. An empty field is expected even when Business Central status is Connected.
A blank field does not mean the secret is missing from the active connection. It means you must paste the existing Value again before saving a configuration change.
__________________________________________________
Step 4 — Use the recovered Value
- Keep the recovered Value in your approved password manager or vault.
- Open the Paystand Dashboard as an Admin.
- Go to Integrations → Microsoft Dynamics 365 Business Central.
- Click Connect To Business Central.
- Paste the recovered secret Value into Client Value.
- Complete the intended configuration change using How to Update Business Central GL Accounts in the Paystand Dashboard.
__________________________________________________
If the existing Value cannot be found
Neither Paystand Support nor Microsoft Azure can reveal the existing Value. Ask your organization’s IT/security owner to coordinate the next step.
If a new secret is required, review every system that uses the same Entra app registration before rotating. Then follow Create or Update the Business Central Client Secret (Azure + Paystand Dashboard).
__________________________________________________
Related articles
- How to Update Business Central GL Accounts in the Paystand Dashboard
- Create or Update the Business Central Client Secret (Azure + Paystand Dashboard) — only if the existing Value cannot be found or the secret has expired