Very much like Jay said.  One thing to know is that if your import file contains a column that matches a field then your field values will override the business logic (where allowed) unless you override your column logic on the mapping screen.  e.g. If you're importing customers and you're happy to have the tax group code that the customer group defaults to, then don't include the tax group column in your import file. If you include it then whatever you have in your sheet will override the default value. Unless in the mapping screen you tell Sage that you want to ignore what is in that column and to go with the default value (or a single hardcoded value).

Good luck and add comments to your Excel workbooks to keep track of what the columns are used for.

Very much like Jay said.  One thing to know is that if your import file contains a column that matches a field then your field values will override the business logic (where allowed) unless you override your column logic on the mapping screen.  e.g. If you're importing customers and you're happy to have the tax group code that the customer group defaults to, then don't include the tax group column in your import file. If you include it then whatever you have in your sheet will override the default value. Unless in the mapping screen you tell Sage that you want to ignore what is in that column and to go with the default value (or a single hardcoded value).

Good luck and add comments to your Excel workbooks to keep track of what the columns are used for.

I figured that it was as you wrote but Jay is right as well. Thank you.