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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Issue importing bank statements

(0) ShareShare
ReportReport
Posted on by 487

Greetings Everyone,

Another day, another challenge!

We are trying to import bank statements using a Belgian specific format: CODA

From going through the code, it seems a lot of the regular code is used, except for the coda mapping.

Now, we have setup the transaction codes to map the bank statements, but when we import the bank statements, they still import as G/L account, instead of customer.

Transaction coding

6013.PNG

However, the record is still a G/L account type. Although, as you can see:

0083.PNG

What am I missing? Why is he still importing everything as G/L account?

Also, after the import, the description field is empty.

Only after clicking on "process CODA statement lines" does it fill in the description.

Also, after clicking "process coda statement lines", records with already posted bank statements will be recognised. But only those with statements mapped in the past.

So, any help would be greatly appreciated

Cheers

I have the same question (0)
  • Verified answer
    Vanessa Garcia Profile Picture
    on at

    Hello John,

    the Transaction Coding you setup up in the Belgian database is used only in case of Automatic Application: So when you use "Process CODA Statement lines":

    docs.microsoft.com/.../coda-bank-statements

    Otherwise it's considered manual application, and the Transaction Coding is not checked.

    In the Transaction Coding table, to get a Customer matched, you need to select "Account Type" = Customer

    pastedimage1603439253811v1.png

    If you have all the Transaction Coding lines setup with G/L Account, you won't get Customer/Vendor matching.

    When you import the CODA file, if there is no description, is because your CODA file does not contain any. If it's filled afterwards is because is using the description from Transaction Coding, not from your file.

    The Transaction Coding in the CODA file you import and in the database should match to be able to apply the lines automatically.

    And the Customer and the possible Document to be applied is selected following the criteria of IBAN on the Customer Bank, Account No., Statement message, etc...as well.

    So if a document is found for Customer 10000, for example, then the line is matched automatically (when using Process CODA Statement lines) to the document for Customer 10000.

    (Status will be Applied and the "Amount" field will be filled in. If a document is NOT found for Customer 10000, you will get Status: Partly Applied for Customer 1000, and the amount still under "Unapplied Amount", because it's matched to a Customer, but not applied to any document)

    I hope it helps ,

  • Hedi Daneels Profile Picture
    487 on at

    Hi Vanessa,

    Thank you for the very detailed response. It is clear now.

    Also, we were missing one vital info that you provided, it is the IBAN that is used, and not the bank account number, as mentioned in the documentation.

    Thank you so much!

    Cheers

  • Hedi Daneels Profile Picture
    487 on at

    Can I ask you if you can help us a little further please? You seem to know this topic very well.

    Do you know by any chance how the Statement message is linked with an existing document?

    We are trying to setup a system to link the statements with invoices.

    We now can link the correct customer using the IBAN thanks to you, but what about the correct invoice?

    CODA seems to be very limited in the information it gives, so except for the statement message, we do not see how to link coda statements with invoices.  

    Since we are selling subscriptions (amongst other things), amounts are recurring, so it cannot be used alone to identify a document.

    Cheers

  • Verified answer
    Vanessa Garcia Profile Picture
    on at

    Hello again

    Sure, no problem. Let me try.

    For Vendors, I guess we can match using the Vendor No, IBAN on the Vendor Bank account and Statement message (which we can relate in the "Posting Description")

    For Customers, I guess we can match using the Customer No, IBAN on the Customer Bank account and the "Customer Reference" (check CODA Statement lines). For the "Customer Reference" you can relate it to the field "Your Reference" in the document.

    Let me know if that works

  • Hedi Daneels Profile Picture
    487 on at

    Thank you so SO much. You made us win HOURS of searching.

    I just managed to link a coda statement with its final invoice, by creating an invoice with a reference, similar to the statement message!

    Thanks again.

  • Hedi Daneels Profile Picture
    487 on at

    I am so sorry, but... I have another question

    We see that credit card statements have no account number. Did you manage to link them with customers or invoices in any way?

  • Verified answer
    Vanessa Garcia Profile Picture
    on at

    Hello again

    sorry for my late response on this way. This was not so obvious to me.

    So, I can confirm that this is not supported by the standard in such a way...

    What you can do is to post those amounts using G/L Accounts and use the Statement Message to put the Credit Card details.

    In order to integrate this part with Credit Cards, I guess a customization will be needed.

  • Hedi Daneels Profile Picture
    487 on at

    Hi Vanessa,

    Thank you.

    Also, there seem to be no link between statement messages and invoices, sadly. This also has to be implemented.

    Thanks a lot for all your help!

    Cheers

  • Verified answer
    Vanessa Garcia Profile Picture
    on at

    Hi again :)

    well, there is some mapping with the Statement Message, but I guess the "Type Standard Format Message" should be <> 107.

    You may want to check the Codeunit 2000042 - Post Coded Bank Statement / Function DecodeCustLedgEntry, for example...

    There the Document No. is taken into account if "Type Standard Format Message" = 107, otherwise it's extracted from the Statement Message.

    WITH CodBankStmtLine DO BEGIN

     IF "Type Standard Format Message" = 107 THEN BEGIN

       IF Type = Type::Global THEN

         DocNo := DELCHR(COPYSTR("Customer Reference",1,10),'<','0')

       ELSE

         DocNo := DELCHR(COPYSTR("Customer Reference",14,11),'<','0');

     END ELSE

       DocNo := DELCHR(COPYSTR("Statement Message",1,10),'<','0');

  • Suggested answer
    Hedi Daneels Profile Picture
    487 on at

    Thank you for all the help! :)

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,917

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,161 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,025 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans