Finance | Project Operations, Human Resources, ...

Bank statement import creating reconciliation worksheets for multiple accounts

(3) Share

Report

Posted on by Rich

368

Has anyone seen the standard bank statement import action, with the Reconcile after import toggle on, create reconciliation worksheets for multiple statements/accounts, not just the statement/account most recently imported? This only seems to happen when we schedule a batch job to import the files from a configured ER source (i.e. not when the import is run interactively), so it's not obviously related to the ER format itself. Any ideas please?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

ERZeppelin 44 on at

Like (1)

Report
Copy link

Link copied!

It looks like you have not set moving the processed files to different folder, dont you?

The setup for processing source files can be found in here:

In my test environment I do have for ISO format Sharepoint created as a source of files. In settings, there are fields where you do specify location for already processed files - the folders should be different for non-processed & for processed/error files:

After import the files should no longer stay in sources folder & will not be processed again. If the folders are not differentiated, you will keep reimporting older files together with newly added.

Does this answer your problem?

Was this reply helpful? Yes No
Rich 368 on at

Like (0)

Report
Copy link

Link copied!

Thanks for input ERZeppelin: appreciate I wasn't explicit on that point. The 4 different document types have been configured, and the file is being moved from the input SharePoint folder to the configured imported whether the import is run in batch or interactively, so the ER element appears to be working reliably, it's the reconciliation process that's confusing. In other words, everything is the same for file movements, bank statement creation, whether or not the toggle below is left off. Things change when we look at the reconciliation worksheets: toggle batch on, and we get multiple worksheets. Leave it off, and only a single worksheet is created.

Was this reply helpful? Yes No
Suggested answer

ERZeppelin 44 on at

Like (1)

Report
Copy link

Link copied!

Thanks for clarification Rich.

Running import in batch mode may result in loosing part of context for import operation, so the import job might behave differently. There can be few factors impacting that behaviour:

1) When you run import interactively, you are explicitly doing it with context of current bank account & particular file. Batch job (even if it is not recurring one) might not be able to access those informations, so it is trying to import all found files in Sharepoint folder & move them after import to another location. Important difference is, that in interactive mode all operations are done sequentially, freezing UI for longer period. In batch mode, the work is balanced across multiple threads, which will import every file separately & generate separate reconciliation sheets. Potential workaround, that might help a bit, is running import with "Import statement for multiple bank accounts" = "No", but that depends if you do have just one account per file. In such a case - you can create separate jobs for every bank account - which in some way force quasi-sequential operation. Not sure if it can help here.

2) Performance improvements implemented in D365 related to posting large journals, can lead to splitting long bank statements into separate reconciliation sheets in batch mode (valid only if your statements contain 1000+ lines). Running in batch mode can potentially lead to such outcome, because reconciliation sheets are kind of journal. If that is the case - you rather always end with multiple sheets, no option to prevent it.

Let me know your thoughts about suggested root causes. As said - it is only "potential" cause, and there might be as well some other not found yet reasons for such behaviour. I would say point 1 is most probable in your case.

Was this reply helpful? Yes No