Using the journal entry import feature in NXT, we are running into an issue where transactions are being duplicated into existing open batches because the previous import file remains in the parameters from whoever did the last import. So staff are seeing a file pre-loaded and forgetting to add their import file -- so if they forget to update the file path, previously imported batches are duplicating in the transactions if that batch is unposted. This is causing several of our entries to be overstated and/or out of balance due to multiple imports. Is there a way it can be set up that the file path does not retain the previous imported file to avoid this confusion and errors? This has happened 15-20 times already since moving to the new feature. We have asked staff to be more cognizant of this but still finding it happening periodically. If it can be removed by default, or having a setting that we can choose to retain or not, that would be helpful for us to avoid these potentially major errors from occurring.