9.1 Bank Account Cards & Posting Setup

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:

1. 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.
2. 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:

[!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:

1. Code: A unique alphanumeric code (e.g., CHECKING, SAVINGS, PAYROLL, OPERATING).
2. 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:

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

1. The organization prints and posts computer checks to vendors via the Payment Journal.
2. The treasury team accesses the Bank Account Card and executes the Positive Pay Export action.
3. 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.
4. The organization transmits this file to the bank's corporate banking portal.
5. 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:

1. Open the Bank Account Card and expand the Payment / Transfer FastTab.
2. In the Positive Pay Export Code field, select or create a profile linked to Table 1231 Positive Pay Export Detail.
3. 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