Is it practical to import sale invoice headers and lines together? Trying to do both but on the header column it's expecting an item where there wouldn't be, that's on the next line down. The suiteanswers is really basic here

Yeah you need header and line level on each line if you do it as one file. So the header info just repeats each line.

better option is 2 file import, use unique external key value in header file and reference it in line level file. Single file import can be daunting

@Sam-I-Am - curious why you say 2 file import is better. We've been using single file invoice import (successfully we hope!) but wonder if we're missing something.

Over the years (15 yrs) working in Netsuite I came to a realization that 2 file transaction import is more efficient than single file. Reasoning Below: • You don't have to repeat header info for every single line thus lowering the chances of errors • Assigning of an external ID in the header level file and reference that in the line level ensures correct transaction structure, also setting an external ID allows you to have easier time for future update or any suitescript needs. • Major reason is here is to keep the header and line level data sperate and clean, so makes it easier to manage and validate data • Also always try to use internal ID's for entities, subs, dept, items, accounts etc whenever possible in your load file. This will save you bigtime from import headaches

Thank you @Sam-I-Am. We do use external IDs on the combined file and internal NS IDs where possible. I've been scared of 2-file imports for some reason but had to use it recently to import Kit Items, and it did work great. Based on your feedback, I will use the 2-file import for an upcoming Opportunity import. I was going to splice together header and line level data or import header level first and then do an update to add line level. But I will use a single import with 2 files.