BC -> CG Setup Guide

"Txn" means Transaction

This BC (Business Central) development enables integration with three action of banking operations:

1. Get Account Balance - Retrieve current account balances
2. Get Account Statement - Download transaction history
3. Execute Transfers - Process intra-bank and inter-bank transactions
   • ⚠️Important: Carefully verify approval requirements for high-value transactions

Post-Production Requirement: After deploying to production, all three operations must be tested. But Execute Transfer action not working in Testing environment. It works only production.

CG Implementation Sequence

Step 1: EM API Setup Card Configuration

Screen Name: EM Api Setup Card

1. Navigate to Microsoft Azure Portal: https://portal.azure.com/
2. Go to App Registration and either:
   • Create a new application, OR
   • Select an existing application
3. Collect the following information and register it in the EM Api Setup Card screen:

Fields description:

• EM Company Name: Select company name
• EM Tenant ID: BC Tenant
• EM Enviroinment: BC Enviroinment (Production, Sand-251012 etc…)
• EM Client ID: Entra App Client ID
• EM Client Secret: Enter the Azure app's Secret key value
  • ⚠️ This value is only visible once upon creation
  • Store it securely as it will require renewal for subsequent views
• User Bridge Server: Yes
• EM Bridge Server URL
  • Testing (UAT): https://stg.cg.api.emconsulting.mn/
  • Production (Real): https://cg.api.emconsulting.mn/

Verify Configuration:

• Click: Actions → Connect to Bridge Server
• Success message: "Successfully modified" confirms successful Bridge Server connection

Step 2: Microsoft Entra Applications Setup

Screen Name: Microsoft Entra Applications

1. In your organization's BC system, open Microsoft Entra Applications
2. Create a new registration using the Client ID from your Microsoft Azure App
3. Add the following three permissions to User Permission Sets:
   • D365 BASIC - Company: @CurrentCompany
   • D365 FULL ACCESS - Company: @CurrentCompany
   • EM.BC.SHARED.CG
4. Set State: Enabled

Step 3: Web Services Configuration

Screen Name: Web Services

Add the following two Page APIs to BC Web Services:

API 1:

• Object Type: Page
• Object ID: 70804
• Service Name: EMBankCFGAPI

API 2:

• Object Type: Page
• Object ID: 70801
• Service Name: EMBankRequestHistAPI

Step 3 A: Update Bank List (If bank list is empty)

Navigate to: CG Bank → UPDATE BANK LIST

Step 4: Bank Configuration

Screen Name: CG Bank Cfg List

Each bank configuration Field Names and Field Values are different. Show bellowed tables.

1. (CGolomtTxn)

2. (CKhanTxn)

3. (CKhasTxn)

Bridge Server :

Khas Bank uses ssl verification on the bridge server (skip this)

4. MBank (CMBankTxn)

5. 
   TDB  (CTdbTxn)

Verify Configuration:

1. Navigate to: Bank Accounts (Khan Bank) → Bank Account Card
2. Click: Actions → Check CG Connection
3. Success message: "Successfully connected" confirms successful bank connection

Testing Checklist

• [ ] Bridge Server connection verified
• [ ] Microsoft Entra Application configured with proper permissions
• [ ] Web Services APIs registered
• [ ] Bank list updated
• [ ] Khan Bank credentials configured
• [ ] Bank connection test successful
• [ ] Account balance retrieval tested
• [ ] Account statement retrieval tested
• [ ] Small-value transaction tested (if applicable)

Support & Troubleshooting

• Ensure all credentials are stored securely
• For high-value transactions, verify approval workflows are properly configured
• Test all operations in a non-production environment before going live
• Keep Azure App Secret keys backed up in a secure location