CAMT053 LedgerInAccountStatement Import

(1) Share

Report

Posted on by nspiteri

547

In 'Bank statement import methods for general journal' one can choose different 'Import Format'. At the moment in 10.0.46 (10.0.2428.95) there is only FINNISH BASIC available.

Analysing the code there is a class called LedgerInAccountStatement and the dropdown shows any class that inherits from it..in this case there's only one: LedgerInAccountStatementFI_BASIC.

I need a new one for CAMT.053.

Does anyone know if there is one available already to import or a specification of the format that can be developed?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

CU03121747-0 8 on at

Like (0)

Report
Copy link

Link copied!

.

Was this reply helpful? Yes No
Suggested answer

Giorgio Bonacorsi 1,779 on at

Like (1)

Report
Copy link

Link copied!

Hello NSpiteri,

What is the exact business requirement? What is the purpose?
CAMT.053 is typically used to import bank statements via the Cash and bank management module (no GL). It's to perform then the bank reconciliation.

Here is the documentation's link: https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/import-bai2-er

Thank you,

Giorgio

Was this reply helpful? Yes No
Verified answer

Aziz Skhiri 259 on at

Like (1)

Report
Copy link

Link copied!

Hey,

The Import Format dropdown on “Bank statement import methods for general journal” only shows classes that inherit from LedgerInAccountStatement. The Finnish Basic is the last one left all other standard ones are obsolete.

No, there is no ready-made CAMT.053 class available in the standard app for that dropdown.

Microsoft has dropped the old general-journal import method for this. CAMT.053 is now fully built-in via Advanced Bank Reconciliation (Electronic Reporting / ISO 20022 format). Just import the standard CAMT configs under
Cash and bank management > Setup > Advanced bank reconciliation setup > Bank statement format
it works out of the box and is the recommended way.

If you really need it in the old general-journal flow, you’ll have to develop your own class (inherit from LedgerInAccountStatement and parse the XML). The spec is the public ISO 20022 camt.053.001.02 / .001.08 schema (full XSD + examples on iso20022.org; Microsoft’s field-mapping docs for SEPA CAMT are also a great reference).
Most people just switch to ABR it’s cleaner and already has CAMT.053 ready check this Field mapping when importing SEPA CAMT files - Business Central | Microsoft Learn

Was this reply helpful? Yes No
nspiteri 547 on at

Like (0)

Report
Copy link

Link copied!

@Aziz Skhiri

I understand, the customer wants to use the legacy functionality. I understand Finnish_BASIC is obsolete..can see that in the code. Instead of designing and redeveloping it from scratch, I was asking if someone has already done it as it would save some time.

They have looked at the new method using Electronic Reporting already but they prefer the old way.

Was this reply helpful? Yes No