Study guide

9.1 Bank Account Cards & Posting Setup

Microsoft Dynamics 365 Business Central Functional Consultant MB-800

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Company Creation & Data Migration

1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies

2 Chapter 2: Security, Profiles & Auditing

2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing

3 Chapter 3: Core System Configuration, Number Series & Copilot

3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities

4 Chapter 4: Dimensions Architecture & Governance

4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities

5 Chapter 5: Workflows & Approvals

5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration

6 Chapter 6: Financial Setup, Periods & Currencies

6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates

7 Chapter 7: Chart of Accounts, Categories & Allocations

7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing

8 Chapter 8: Posting Groups & Posting Setup

8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups

9 Chapter 9: General Journals & Recurring Methods

9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods

10 Chapter 10: Accounts Payable & Accounts Receivable Setup

10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup

11 Chapter 11: Fixed Assets Setup & Depreciation Books

11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods

12 Chapter 12: Inventory Setup, Costing & Locations

12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)

13 Chapter 13: Logistics Master Data, Pricing & Discounts

13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds

14 Chapter 14: User Interface, Views, Inspection & Excel

14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode

15 Chapter 15: Purchase & Sales Order Execution

15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders

16 Chapter 16: Invoices, Credit Memos & Document Corrections

16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows

17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications

17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules

18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting

18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals

9.1 Bank Account Cards & Posting Setup

Key Takeaways Explain This Topic AI

The Bank Account Card (Page 370) manages company financial institution accounts, where leaving the Currency Code field blank designates a Local Currency (LCY) account, while populating it locks the account strictly to that foreign currency.

The Bank Acc. Posting Group links bank subledger transactions to a specific General Ledger cash account; Direct Posting must be disabled on that G/L account to prevent unreconciled balance variances.

External banking identifiers—including Transit No., Bank Account No., SWIFT Code, and IBAN—are required to support electronic funds transfers and automated clearinghouse operations.

Payment integration relies on Data Exchange Definitions, mapping Bank Statement Import Formats (e.g., SEPA CAMT.053, CSV, Yodlee) for reconciliation and Payment Export Formats (e.g., SEPA Credit Transfer, NACHA, EFT) for automated disbursements.

Positive Pay Export generates standardized electronic check issuance files transmitted to financial institutions to prevent check fraud by verifying check numbers, dates, and amounts prior to clearing.

Last updated: September 2026

9.1 Bank Account Cards & Posting Setup

Quick Summary: In Dynamics 365 Business Central, bank accounts function as dedicated financial subledgers configured via the Bank Account Card (Page 370). A bank account configured with a blank Currency Code operates strictly in Local Currency (LCY), whereas assigning a currency code restricts all postings to that foreign currency. Each bank account links to the General Ledger through a Bank Account Posting Group , where the underlying G/L cash account must have Direct Posting set to No to maintain subledger integrity. Electronic banking automation leverages Data Exchange Definitions for statement import feeds (SEPA CAMT, CSV, Envestnet Yodlee), payment export protocols (SEPA Credit Transfer, NACHA, EFT), and Positive Pay fraud prevention exports.

Bank Account Architecture & Subledger Governance

In Microsoft Dynamics 365 Business Central, cash and banking operations are managed within a dedicated subledger architecture. Rather than posting cash transactions directly to General Ledger accounts, transactions are recorded against Bank Accounts (Table 270 Bank Account ).

When a transaction involving a bank account is posted, Business Central simultaneously writes records to two ledgers:

Bank Account Ledger Entry (Table 271): Contains the granular banking transaction details, including payment method, check number, currency amount, remaining amount, and statement reconciliation status.

G/L Entry (Table 17): Contains the financial debit or credit posted to the designated cash balance sheet account in the General Ledger. Bank Transaction Flow:

  • [Journal Line / Payment / Invoice]
  • │
  • ▼
  • [Post Action Executed]
  • ├──► Writes to Bank Account Ledger Entry (Subledger: Table 271)
  • └──► Writes to G/L Entry (General Ledger: Table 17 via Bank Acc. Posting Group)

This dual-ledger architecture ensures that the organization maintains detailed audit trails for check printing, electronic fund transfers (EFT), bank statement imports, and periodic reconciliations without cluttering the Chart of Accounts.

The Bank Account Card: Core FastTabs & Parameters

Consultants set up and manage bank accounts on the Bank Account Card ( Alt+Q -> type Bank Accounts -> select or create a record). The card is divided into several FastTabs governing operational parameters, currency handling, and reporting metrics. UI Navigation Path:

  • Tell Me (Alt+Q) -> Bank Accounts -> Action Bar: New (opens Page 370 Bank Account Card)
  • 1. General FastTab: Account Identity & Currency Rules

No.: The unique primary identifier for the bank account, typically generated automatically from a designated No. Series .

Name / Name 2: The official legal name and descriptive label of the banking institution or account.

Bank Acc. Posting Group: A mandatory code linking the bank account to a record in the Bank Account Posting Groups table, which identifies the underlying G/L balance sheet cash account.

Blocked: Controls transaction posting restrictions. Options include:

[Blank]: Fully open for all operational postings.

Payment: Prohibits payments and outbound disbursements while permitting deposits and incoming receipts.

All: Completely blocks all debit and credit postings to the bank account.

Last Check No.: A text/numeric tracking field that records the last pre-printed check number issued. When computer checks are printed via payment journals, Business Central validates and increments this value sequentially.

Last Statement No.: Tracks the alphanumeric identifier of the most recently finished bank reconciliation statement. When creating a new bank reconciliation, Business Central suggests the next sequential statement number.

Balance & Balance (LCY): Real-time FlowFields reflecting the net sum of all open and closed Bank Account Ledger Entries. If the account operates in foreign currency, Balance reflects the foreign currency amount, while Balance (LCY) dynamically calculates the local currency equivalent based on current exchange rates.

Currency Code: LCY vs. Foreign Currency Accounts

A foundational principle tested on the MB-800 exam is how Business Central handles bank account currencies:

Currency Configuration Setup Value Operational Rules & Behavior

Local Currency Account (LCY) Currency Code is left BLANK The bank account operates exclusively in the company's base local currency. All deposits, checks, and transfers post in LCY. Foreign currency transactions cannot be posted directly against this bank account unless converted at transaction entry.

Foreign Currency Account (FCY) Currency Code is set to a valid code (e.g., EUR , USD , GBP ) The bank account operates strictly and exclusively in the specified foreign currency. Every transaction posted to this bank account must match this foreign currency code. Business Central maintains dual balances: foreign currency units and calculated LCY.

Warning

Immutable Currency Rule: Once a transaction ledger entry has been posted to a Bank Account, the Currency Code field is permanently locked and cannot be changed or cleared. If an account was initialized with an incorrect currency code and transactions have posted, the account must be blocked and a new bank account card configured.

Bank Account Posting Groups & Direct Posting Control

The integration between the bank subledger and the General Ledger is governed by Bank Account Posting Groups (Page 373 / Table 277). UI Navigation Path:

Tell Me (Alt+Q) -> Bank Account Posting Groups

Each Bank Account Posting Group record contains two primary fields:

Code: A unique alphanumeric code (e.g., CHECKING , SAVINGS , PAYROLL , OPERATING ).

G/L Account No.: The specific balance sheet asset account in the Chart of Accounts representing the cash position of that bank account. Posting Group Mapping Architecture:

  • Bank Account Card: 'BNK-01' (Checking)
  • └── Bank Acc. Posting Group: 'CHECKING'
  • └── G/L Account No.: '10100' (Operating Cash Account)
  • The Critical Rule of Direct Posting

On the G/L Account Card for account 10100 (Operating Cash Account), the Direct Posting boolean field must be set to No (unchecked).

When Direct Posting = No (Standard Best Practice): Users cannot manually select G/L Account 10100 on General Journal lines, Purchase Invoices, or Sales Orders. All entries affecting cash must specify Account Type = Bank Account and select Bank Account BNK-01 . This guarantees that every debit or credit written to G/L Account 10100 has an identical corresponding entry in the Bank Account Ledger Entries table.

When Direct Posting = Yes (Severe Operational Risk): Users can enter manual journal entries directly to G/L Account 10100 . These entries write to G/L Entry without creating a record in Bank Account Ledger Entry . As a result, the General Ledger cash balance will permanently diverge from the Bank Account balance, making automated bank reconciliation impossible.

Communication, Transfer & International Coordinates

To facilitate payment processing, wire transmissions, and electronic statement matching, the Bank Account Card captures both domestic and international banking coordinates:

FastTab / Section Field Name Functional Definition & Regulatory Standards

Communication Address, City, Post Code, Country/Region Code The physical branch or mailing address of the financial institution. Printed on remittance advices and bank letters.

Communication Phone No., E-Mail, Contact Operational contact details for corporate treasury and branch relationship managers.

Transfer / Payment Bank Branch No. / Transit No. The domestic routing transit number (e.g., 9-digit ABA routing transit number in the United States, sort code in the United Kingdom, or transit/institution number in Canada).

Transfer / Payment Bank Account No. The external account number assigned to the company by the financial institution. Distinct from the internal BC No. identifier.

Transfer / Payment SWIFT Code (BIC) The Society for Worldwide Interbank Financial Telecommunication code (Business Identifier Code), consisting of 8 or 11 alphanumeric characters used for cross-border wire routing.

Transfer / Payment IBAN The International Bank Account Number, an internationally standardized format up to 34 alphanumeric characters used across the European Union and globally for cross-border settlement.

These coordinates are mapped directly to electronic output files when processing vendor disbursements and customer direct debits.

Payment Integration: Statement Import & Payment Export Formats

Modern enterprise cash management relies on automated electronic data interchange (EDI) between Business Central and commercial banks. This functionality is configured through Data Exchange Definitions linked on the Bank Account Card under the Bank Statement Import and Payment Export settings. Electronic Banking Architecture:

  • [External Bank]
  • │
  • ├── Statement File (CAMT / CSV / Yodlee) ──► Bank Statement Import Format ──► [Bank Acc. Reconciliation]
  • │
  • └── Electronic Payment (SEPA / NACHA) ◄── Payment Export Format ◄── [Payment Journal / EFT]
  • 1. Bank Statement Import Configurations

Under the Payment Match or Bank Statement Import settings on the Bank Account Card, organizations configure how bank statements are ingested into the Bank Acc. Reconciliation page (Page 379) or the Payment Reconciliation Journal (Page 1290):

Bank Statement Import Format: A code referencing an underlying Data Exchange Definition configured for statement parsing. Standard formats include:

SEPA CAMT: Standardized XML formats (e.g., CAMT.053 end-of-day bank statement or CAMT.054 debit/credit notification) widely used in Europe and global corporate banking.

Generic CSV / Text: Delimited files mapped via the Data Exchange Framework where column positions are mapped to transaction date, amount, payee, and external document number.

Envestnet Yodlee Bank Feeds: An automated cloud banking service extension that securely connects directly to over 15,000 global financial institutions, retrieving statement feeds automatically on a scheduled recurring background job without manual file downloads.

Automatic Bank Statement Import: A toggle on the Bank Account Card allowing automated statement retrieval upon opening bank reconciliation worksheets.

2. Payment Export Configurations

To execute vendor disbursements electronically without printing physical paper checks, the Bank Account Card defines payment export protocols:

Payment Export Format: Links to a Data Exchange Definition that structures outgoing payment files generated from the Payment Journal (Page 256):

SEPA Credit Transfer: XML format compliant with ISO 20022 ( pain.001.001.03 ) for euro-denominated disbursements across the SEPA zone.

NACHA (ACH): Standard fixed-width 94-character record format utilized by the National Automated Clearing House Association for direct electronic payments within the United States.

EFT Formats: Regional standard electronic formats such as Canadian CPA005 or UK BACS.

Bank Clearing Standard: Specifies the regulatory clearing code required by the domestic clearinghouse (e.g., US: Fedwire/ACH or ISO20022 ).

Positive Pay Export Configuration & Fraud Prevention

Check fraud remains a persistent risk for organizations issuing physical paper checks. Business Central provides native support for Positive Pay , an automated fraud-prevention service offered by commercial banks.

The Positive Pay Workflow

The organization prints and posts computer checks to vendors via the Payment Journal.

The treasury team accesses the Bank Account Card and executes the Positive Pay Export action.

Business Central evaluates all newly issued, non-exported check ledger entries and generates an encrypted text or CSV file structured to the bank's exact layout specifications.

The organization transmits this file to the bank's corporate banking portal.

When a check is presented to the bank for payment, the bank matches the check number, issue date, payee, and dollar amount against the transmitted Positive Pay file. Any discrepancy results in the check being flagged and held for company authorization before funds are cleared. Positive Pay Workflow:

  • [Print & Post Checks in BC]
  • │
  • ▼
  • [Positive Pay Export Action on Bank Account Card]
  • │
  • ▼
  • [Generates Structured Flat File (Check No., Date, Payee, Amount)]
  • │
  • ▼
  • [Transmit File to Bank Portal] ──► [Bank Validates Checks Before Clearing]
  • Positive Pay Configuration Setup

To enable Positive Pay on a Bank Account Card:

Open the Bank Account Card and expand the Payment / Transfer FastTab.

In the Positive Pay Export Code field, select or create a profile linked to Table 1231 Positive Pay Export Detail .

The export definition establishes mandatory header, detail, and footer record structures, including check status codes (e.g., O for Open/Issued, V for Voided).

Common Implementation Pitfalls & Exam Traps

Implementation Issue Root Cause System Impact Corrective Action

Bank Subledger & G/L Out of Balance Direct Posting was enabled on the cash G/L Account, and an accountant posted a manual general journal entry directly to the account. The General Ledger balance does not equal the Bank Account Ledger Entries balance. Bank reconciliation cannot balance. Disable Direct Posting on the G/L Account card immediately. Post an adjusting journal using Account Type = Bank Account to re-align balances.

Cannot Change Bank Currency Code An administrator attempts to update or clear the Currency Code on a bank account after opening balance entries have posted. Business Central throws a runtime validation error: "You cannot change Currency Code because ledger entries exist for this bank account." The Currency Code field cannot be edited once entries exist. Block the bank account and create a new bank account with the correct currency configuration.

Payment Export Fails in Payment Journal The Bank Account Card lacks a designated Payment Export Format , or the Payment Journal Batch lacks the Allow Payment Export toggle. The Export Payments to File action is disabled or errors upon execution in the Payment Journal. Verify that Payment Export Format is populated on the Bank Account Card and that Allow Payment Export is enabled on the General Journal Batch.

Foreign Currency Bank Rec Mismatches Bank statement imported in LCY for an account configured with a foreign currency code. System rejects imported statement lines due to currency code mismatch between the bank card and statement file. Ensure external bank statement files match the Bank Account Card's Currency Code exactly.

Loading diagram... Bank Account Setup Architecture and Transaction Engine