Validation of Invoice Import is awful

Dawn Asbury

Not a fan of the NXT import function for invoices. The database version had a lot more visibility at the line level. I ran an import and 5 of my transactions did not validate. The validation report was no help because it does not tell me which specific records did not validate. Is there a box I forgot to check which will tell me which items are not validating? Basically it said it was the last 5 lines but I know that is incorrect because I accidentally ran it instead of validating first and some of those uploaded. Thanks!

Sannyasin Siddhanathaswami

@Dawn Asbury
It's not just importing Invoices. All the imports have a horribly inefficient way to validate then actually import. So many clicks, saves, views, repeat.

Sharon Sherman

@Dawn Asbury
My biggest headache is I have multiple line item distributions that don't always have the same number of lines and I have to manually change the extension on 6 fields and I often have distribution lines that exceed 20 lines . in the Database you could click update fields but not in NXT what a waste of time.

Dawn Asbury

@Sannyasin Siddhanathaswami Agreed. Posting subledgers was so much better in database. I could validate and post in the same screen. Now I have anxiety posting subledgers in NXT because you have to get out of the selection and hope you don't post the wrong one if you work with multiple versions with different filters/queries. I could spend half a day listing various things that worked better in database.