Skip to content
Sentinel 1.5 | Preview

Clear bridged customer payments automatically during bank reconciliation

2026 Release Wave 1 · Cash and Bank Management

Microsoft source
Score 74/100 · HighImpact MediumSwiss relevance MediumGenerally Available

Dx365 Analysis

Our interpretation — not a Microsoft statement

What is changing?

Completing a bank reconciliation is expected to trigger the accounting needed to remove eligible customer receipt amounts from the bridging account. In centralized payment structures, that accounting is expected to be created in the payment-processing legal entity. Reconciliation and inquiry pages should also expose the companies and related-party context behind the transaction.

Current state today

Customer payment journals can temporarily post receipts to a bridging ledger account while the corresponding bank movement is pending. Even when the bank statement transaction is matched and the reconciliation is completed, the bridge balance generally requires a separate clearing step. Finance teams therefore use bridge-clearing functions or manual journals and must investigate differences between the reconciled bank account and uncleared bridge entries. Centralized and intercompany payment arrangements add further company-level tracing and balancing work.

Future state after release

For qualifying customer receipts, reconciliation completion should also initiate the bridge-clearing posting. The intended scope appears to include receipts belonging to the payment company itself and receipts processed centrally for another company. Users should gain more company and related-party information when reviewing the reconciliation and subsequent accounting.

Why it matters

This can remove a recurring manual step between bank reconciliation and ledger close. It should reduce aged balances in bridge accounts, duplicate clearing entries and timing differences caused by users completing the accounting later. The largest benefit will be for organizations processing high receipt volumes or operating centralized payment models. It also changes reconciliation from a matching-only activity into an event that may generate additional ledger postings, making controls, posting dates and exception handling important.

Who is affected?

Cash and bank management consultantsAccounts receivable consultantsTreasury and bank reconciliation usersCustomer payment processing teamsGeneral ledger accountantsCentralized payment teamsIntercompany accounting teamsFinancial controllersInternal and external auditorsSupport teams maintaining bank statement integrations

Consultant impact — Medium

The feature is administrator-enabled and mainly affects customers that use bridged customer receipts with bank reconciliation. Adoption will require setup assessment, posting and period-control testing, security review, reconciliation procedure changes and regression coverage for customer settlement, bank accounting and intercompany postings. Customers not using bridge accounts or centralized payment processing should see little or no impact.

Likely required work

  • Identify legal entities using customer payment bridging and determine whether their bank accounts are reconciled in Dynamics 365 Finance.
  • Document the present bridge-clearing process, including accounts, journal names, posting dates, dimensions, ownership and close controls.
  • Confirm the centralized payment and intercompany design before enabling the feature in multi-company environments.
  • Test same-company and cross-company receipts from payment posting through statement matching, reconciliation completion, bridge clearing and customer settlement.
  • Verify behavior when periods are closed, exchange rates differ, financial dimensions are required or the clearing posting fails.
  • Update reconciliation instructions, support procedures and control documentation if the feature is adopted.

Swiss relevance — Medium

The capability is relevant to Swiss entities that import bank statements and use temporary accounts for customer receipts, particularly shared-service or multi-company groups. It may improve the handling of receipts originating from Swiss banking channels, but the available description does not indicate any Swiss localization, QR-bill, Swiss VAT or Switzerland-specific ISO 20022 behavior.

What should customers do now?

  • Add the feature to the 2026 Wave 1 regression plan for customers with material bridge-account balances.
  • Use production-like statement files and receipt volumes during testing rather than relying only on simple manually entered examples.
  • Reconcile the bridge account before activation so legacy open items can be separated from entries processed by the new logic.
  • Define monitoring for failed or unexpected clearing journals during the initial rollout.
  • Pilot in one lower-risk legal entity before extending it to a centralized payment organization.
  • Review the feature documentation again near September 2026 for final prerequisites, limitations and activation details.

Release Radar score — 74/100 (High priority)

This is a meaningful Finance automation affecting bank reconciliation, customer payments, ledger accuracy and potentially intercompany accounting. It can benefit many payment-intensive customers and has moderate implementation and control implications. The score is limited because it applies only where bridged customer receipts are used, has no identified Swiss-specific behavior, is administrator-enabled and is not scheduled for general availability until September 2026.

Assumptions, not Microsoft-confirmed facts

  • The supplied release information does not specify the exact feature-management switch, required configuration or dependency on advanced bank reconciliation.
  • The precise criteria used to decide whether a bridge transaction is eligible for clearing are not yet clear.
  • The posting date, voucher numbering, journal name, financial-dimension inheritance and exchange-rate treatment are not described.
  • Behavior for partial matches, reversals, rejected payments, reconciliation cancellation and failed journal posting requires confirmation.
  • It is not clear whether historic bridge entries created before activation can be processed by the new capability.
  • No public preview date is currently supplied, so hands-on validation may not be possible before general availability.

Microsoft information

Quoted from the release plan

Business value

Automatic clearing of customer payments streamlines the bank reconciliation process by eliminating manual clearing of bridge transactions, reducing reconciliation errors and ensuring general ledger balances are accurate and up to date. This improves operational efficiency, strengthens auditability in payment scenarios, and increases confidence in using automated bank reconciliation at scale.

Feature details

The feature automatically clears bridge transactions generated from customer payments when the bank reconciliation completes. It posts clearing journals in a centralized payment legal entity. The legal entity and related party details are displayed on reconciliation and inquiry pages, improving traceability and auditability. The feature supports all customer types, including both same-company and intercompany scenarios.

Change history

Differences detected between scans

  • status01 Sept 2026

    The release status moved from Upcoming to Generally Available.

    Previous
    Upcoming
    Current
    Generally Available
  • added12 Aug 2026

    Microsoft added this feature to the Dynamics 365 Finance release plan.

    Previous
    —
    Current
    Upcoming
Back to Release Radar³