2

Currently only ER level errors or warnings will cause import process move the file to the Failed or Warning folder that set on the ER source (File states for the sources also just show this level and not clear enough.). But after ER validate and read file, we may get errors like bank account not found, bank statement was not imported...this time, the file was moved to Imported folder that set on the ER source and the batch job status on the batch history is End, but actually files not imported successfully.

This makes customer hard to monitor the importing status of the files. Can we please make a more clear/accurate log for bank statement?

For example, we have a form to show exact import state of file--full imported, partial imported, failed, imported with warnings, what's kind of validation messages thrown out during the import process on the exact file, the file has been moved to which folder after import process.


STATUS DETAILS
New