Import batch of similar invoices via Visual Integrator for A/P Invoice Data Entry?

SOLVED

For context, I tried searching these forums for at least an hour to find an answer on this, but the only active discussions that popped up were 8+ years old. Either I was using the wrong search terms, or this is an uncommon issue. Apologies in advance if this is being posted in the wrong place - I'd appreciate being pointed in the right direction.

In any case, hypothetically let's say I have a large number of similar invoices (50+) I need to enter in the AP module. Normally I'd do these vendor by vendor in "Invoice Data Entry". Nearly all the info for these invoices is the same, just spread across multiple vendors.

If the ONLY differences between these invoices was the vendor number, Invoice number, and invoice amount, what would I have to do to process them all at once? GL account, due date, etc., etc., would all be the same. I can have the vendor number, invoice number, and invoice amount easily generated in a single excel spreadsheet, but I don't know how to use visual integrator or any other tool in Sage to do so. If someone could point me to a tutorial or any other resource that could help me figure this out I'd greatly appreciate it!

Cheers.

Parents Reply Children
  • 0 in reply to Kevin M

    Kevin,

    Thanks for the info, this is definitely helpful. The only thing I'm struggling with (my novice is definitely showing here) is how to format the sourcefile before running the job. Off the top of my head I wonder if it would be possible to use VI to export Invoice Data Entry I've manually completed in Sage, that way I'd be able to base the formatting of my sourcefile off of that. Clearly I have more research to do...

  • 0 in reply to LWAcct

    CSV files are easiest to work with, and column order only needs to be consistent.  Have whatever column data you need in the file (whatever differs from line to line) and hard code anything which is always the same into the VI job.

  • 0 in reply to LWAcct

    Please note that while the import calls for the account key you can actually use the unformatted GL account number. If it is longer than 9 characters be sure to check the box on the header to skip truncating the source file.