Bank feeds and statement import in Business Central

Reconciling a bank account by hand is a slow, error-prone afternoon. Business Central provides two paths to automate the inbound side: bank feeds (live API connections to financial institutions) and statement file import (MT940, BAI2, CAMT.053, and similar formats). Both ultimately load lines into the Bank Account Reconciliation or Payment Reconciliation Journal for matching against ledger entries.

Envestnet Yodlee bank feeds. Microsoft's standard bank feed service is built on Envestnet Yodlee, the financial-data aggregator. With the Envestnet Yodlee Bank Feeds extension installed, a Business Central user can:

1. Link a bank account in BC to the corresponding account on the user's bank portal.
2. Authenticate (OAuth or username/password) via Yodlee's flow.
3. Schedule daily refresh — Yodlee fetches the latest transactions and pushes them into BC's Bank Stmt Service Trans records.
4. Run reconciliation against the imported transactions.

Coverage is broad in North America and Western Europe but uneven elsewhere — verify the bank is supported before committing. Some banks require additional consent or appear in degraded mode (limited fields).

Statement file import. The alternative is to upload a file the bank produces — MT940 (legacy SWIFT), CAMT.053 (XML, ISO 20022, the modern standard), or country-specific formats (Norwegian Bankgiro, German MT940 variants). BC's Data Exchange Definition framework parses the file:

1. On the bank account card, set the Bank Statement Import Format field.
2. Use the Import Bank Statement action on a bank reconciliation; pick the file.
3. The data exchange parses XML or text into reconciliation lines.

Data Exchange Definitions. BC ships with several built-in formats (CAMT.053, SEPA CT, NACHA). Country-localised formats add more. For unsupported banks, partners often build custom definitions:

• A Data Exch. Def record names the format.
• Data Exch. Line Def records describe each line type (header, balance, transaction).
• Data Exch. Column Def records map XML paths or text positions to fields in BC tables.
• Data Exch. Field Mapping records map data-exchange columns to target table fields with optional transformation expressions.

The framework is configurable but tedious; modifying it requires understanding both the file format spec and BC's data exchange model.

Payment Reconciliation Journal vs Bank Reconciliation.

• Bank Reconciliation — designed for full bank-statement vs G/L reconciliation. Reconciles every transaction over a period; produces a reconciliation report; closes the period balance.
• Payment Reconciliation Journal — designed for incoming customer payments. Suggests applications against open customer invoices using algorithms (name match, amount match, reference match).

Both consume the same imported lines but apply them differently. Most teams use both: payment reconciliation for incoming customer cash, bank reconciliation for full month-end reconciliation.

Matching logic. The payment reconciliation journal scores potential matches:

• Exact reference match (CID, OCR, ISO reference) — high confidence.
• Customer name match + amount — medium.
• Amount only — low; needs human review.

The Apply Automatically action auto-applies high-confidence matches and leaves the rest. Tunable thresholds determine where the line is drawn.

Bank account balance reconciliation. The bank reconciliation page compares:

• The bank's reported balance.
• BC's bank account balance.
• The cumulative effect of matched and unmatched transactions.

Outstanding items (a check issued but not cleared, a deposit in transit) are flagged. When totals match and outstanding items are explainable, the reconciliation can be posted, closing the period.

Common pitfalls.

• Daily feed with weekly reconciliation cadence. Transactions accumulate; daily review keeps it manageable.
• CAMT.053 versions. ISO 20022 has multiple versions (.001.02, .001.08); banks support different ones. Confirm the data-exchange definition matches your bank's output.
• Manual journal entries against the bank account. Reconciliation impossible to balance. Discipline: every bank account movement must originate from a payment, receipt, transfer, or reconciliation entry — never a manual G/L journal.
• Yodlee re-authentication. Banks rotate session tokens; Yodlee links break periodically. Build a monitoring step into the AR rhythm.
• Duplicate imports. Importing the same statement twice creates double entries. The Statement No. field on a bank reconciliation should be unique; system warns but doesn't always block.

When to invest in custom integration. For high-volume cash management (large multinationals, treasury operations), a direct host-to-host bank integration through Azure Logic Apps or a partner connector typically beats both Yodlee and file import. The setup cost is high but the daily operational cost is near zero.