The identity column cannot be added to. You need to allow it to autogrow the way it wants (or you can override, but often leads to further problems).
If you are inserting new rows into the destination table, then best to simply ignore that identity column in the insert altogether and allow SQL to take care of it for you.
I believe you should always use a staging table for this type of process, regardless of the current identity column usage. That way you can validate the import before committing to the live table.
1) Import CSV to Staging Table
2) Validate data in Staging Table (can include checking for dupes and other yucky bits like datatype conversions)
3) Insert into Live Table (spell out columns that you want to populate leaving out the identity column of the destination "live table" ) select from staging table
4) Tidy up / archive CSV when all processing is complete