web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Bank Account Reconcili...
Small and medium business | Business Central, N...
Suggested Answer

Bank Account Reconciliation - Data Exchange definition

(5) ShareShare
ReportReport
Posted on by D365 Business Centr... 164
Hi all,
 
While importing Bank Account statement using Import Bank Statement action from Bank account reconciliation card Page I am getting an error as below : 
Can any one suggest me to resolve this .. ?
 
Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Suggested answer
    Sohail Ahmed Profile Picture
    Sohail Ahmed 11,169 Super User 2026 Season 1 on at

    The error message "Record(1220) is not compatible with Codeunit.Run(Record(81))" indicates that the system is trying to run a codeunit expecting a Record 81 (Gen. Journal Line) but instead it's being passed Record 1220 (Bank Acc. Reconciliation Line).

    This typically happens when the Data Exchange Definition or the Bank Statement Import Format is incorrectly mapped or customized. During import, the system is expecting a general journal context but is being given a reconciliation line record.

    How to resolve:

    • Check the Data Exchange Definition used for the import.
    • Make sure the processing codeunit specified in the related Bank Export/Import Setup or Data Exchange Definition expects the correct record type (Record 1220).
    • If a custom codeunit is used for import, ensure it’s designed to handle Record 1220, not Record 81.
    • If you're using a standard format (like CAMT.053 or MT940), revalidate the mapping fields and the selected Data Exchange Definition.
     

    If this setup was customized, ask your developer or partner to review the codeunit call and ensure it matches the expected record type.

     

    ✅ Mark this answer as verified if it helps you.

  • Suggested answer
    Khushbu Rajvi. Profile Picture
    Khushbu Rajvi. 22,132 Super User 2026 Season 1 on at
  • Gerardo Rentería García Profile Picture
    Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

    Hi, good day

    Can you share the error? Verify that the record type you are passing to the codeunit matches the type it expects.

    Share error details to get help from another user | Microsoft Learn

    Best Regards
    Gerardo

  • Suggested answer
    Jeffrey Bulanadi Profile Picture
    Jeffrey Bulanadi 9,112 Super User 2026 Season 1 on at

    Hi

    Thanks for sharing the screenshot

    It confirms that the error is a record compatibility issue between the Data Exchange Definition and the processing codeunit used during bank statement import. Specifically:

    Record(1220) is not compatible with Codeunit.Run(Record(81))

    This suggests that the system is trying to pass a record of type 1220 (likely Bank Account Statement Line) to a codeunit expecting a different record type most likely 81 (Bank Account). Here’s how to resolve it:

    1. Validate Processing Codeunit Assignment

    • Go to Bank Export/Import Setup
    • Confirm that the Processing Codeunit ID is set to 1270 for bank statement imports
    • This codeunit is designed to handle Bank Account Statement Line records and must match the structure of your Data Exchange Definition

    2. Check Data Exchange Definition Target Table

    • Open your Data Exchange Definition
    • Under Line Definitions > Field Mapping, confirm that the Table ID is set to 274 (Bank Account Statement Line)
    • If it’s incorrectly set to 81, the system will throw a compatibility error during import

    3. Review Column Definitions and Field Mapping

    • Ensure that required fields like Transaction Date and Statement Amount are mapped correctly
    • Use the correct Data Type and Date Format (e.g., dd-MM-yyyy or MM/dd/yyyy) depending on your bank file
    • Reference: Forvis Mazars – How to Set Up Data Exchange Definitions

    4. Assign the Format to the Bank Account

    • On the Bank Account Card, set the Bank Statement Import Format to the correct DED code
    • This ensures the import process uses the correct mapping and codeunit


    Helpful Community Threads

    Bank Statement Import Error – Record Compatibility
    Bank Reconciliation File with Two Columns – Debit and Credit

    If you find this helpful, feel free to mark this as the suggested or verified answer.

    Cheers
    Jeffrey

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,993 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,116 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 557 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans