Hi Yatin S ,

Thanks for reaching out. It seems you're encountering a version error when trying to import transactions into Sage 50 using a .CSV file that you've converted to an .IMP file. This could be happening due to a formatting issue or a version mismatch.

Here are a few steps to help resolve your issue:

1. Ensure that the .IMP file format is correct. The file needs to have proper header information and transaction details formatted as per the Sage 50 requirements.

2. Check the version number in your .IMP file. According to the Sage 50 documentation, you should be using "12001" for the version if you are dealing with Sage 50 version 2005. Make sure the country code is also correct (1 for Canada).

3. Verify that the dates in your import file match the fiscal year dates in Sage 50.

4. If you're adding customers or vendors, make sure the mandatory fields are filled in correctly as per the specifications.

5. Check to ensure that the transaction type you're importing is enabled in your Sage 50 Accounting company settings.

6. For detailed instructions on formatting the .IMP file, you can refer to the article "How do I import transactions into Sage 50 using a .IMP file format?".

7. If you're still encountering issues, you may consider reaching out to a Sage Development Partner for a special solution or use Community Hub to connect with Certified Consultants for advice.

Please try the above solutions, and if you need further assistance, don't hesitate to reach out.

If this helps, please mark it as verified :)

Warm Regards,
Erzsi

Hi Yatin S ,

Thanks for reaching out. It seems you're encountering a version error when trying to import transactions into Sage 50 using a .CSV file that you've converted to an .IMP file. This could be happening due to a formatting issue or a version mismatch.

Here are a few steps to help resolve your issue:

1. Ensure that the .IMP file format is correct. The file needs to have proper header information and transaction details formatted as per the Sage 50 requirements.

2. Check the version number in your .IMP file. According to the Sage 50 documentation, you should be using "12001" for the version if you are dealing with Sage 50 version 2005. Make sure the country code is also correct (1 for Canada).

3. Verify that the dates in your import file match the fiscal year dates in Sage 50.

4. If you're adding customers or vendors, make sure the mandatory fields are filled in correctly as per the specifications.

5. Check to ensure that the transaction type you're importing is enabled in your Sage 50 Accounting company settings.

6. For detailed instructions on formatting the .IMP file, you can refer to the article "How do I import transactions into Sage 50 using a .IMP file format?".

7. If you're still encountering issues, you may consider reaching out to a Sage Development Partner for a special solution or use Community Hub to connect with Certified Consultants for advice.

Please try the above solutions, and if you need further assistance, don't hesitate to reach out.

If this helps, please mark it as verified :)

Warm Regards,
Erzsi

Hi Erzsi,

I already sent Purchase Invoice information in my question. Can you please let me know my mistake in above format? Also please let me know about the format of Purchase and Sales Invoice with payment.

Thanks,

Yatin

This part #2

Erzsi_I said:

Check the version number in your .IMP file. According to the Sage 50 documentation, you should be using "12001" for the version if you are dealing with Sage 50 version 2005. Make sure the country code is also correct (1 for Canada).

should have read

Check the version number in your .IMP file. You should be using "12001" for the version if you are dealing with Sage 50 version 2005 and later. Make sure the country code is also correct (1 for Canada).

The current documentation in the help file indicates 20001 but I haven't tried it myself.  That is the version for Sage 50 2013.  I always use 12001.

There was a problem importing imp files in 2023.0 but a later release of 2023 did correct this issue.

This Knowledgebase Article will show you the file formats.  However there is no way I know of to import a purchase invoice with payment.  You can do this with a sales invoice.

Your format presented will likely continue with errors after you fix the version number.  The Knowledgebase Article will help you correct that.

This is a quick idea of what a file looks like

<Version>
"12001", "1"
</Version>

<PurInvoice>
"Bob Smith", , , , , , , , , , ,
<! "no. of details", "quote/Order no. Optional", "InvoiceNo", "entry date mm-dd-yyyy", "total amount", "discount rate",
<! "discount days", "net days", "freight amt", "tax information"
"1", ,"RMay2020","5-1-2020","150.00", "0", "0", "0", "0.00"
<! "item no.", "quantity", "price", "amt", "tax information"
"1001","1", "150","150.00"
</PurInvoice>

Please note though that the Vendor Address and Sales Tax information are missing from the file as it was not needed when I created it.  The Freight amount is $0 and therefore no sales tax info is included either.  The Knowledgebase article includes these elements.

You can add more sections from <PurInvoice> to </PurInvoice> to import more invoices at one time.

This is the error showing while importing.

Did you change your import format to resemble the sample I posted and the information in the Knowledgebase article?

eg. did you include the tags <Version></Version> or did you just change the version number?

Hi Richard,

Below is my code with version number for 2024.2

<Version>
"31201","1"
</Version>

<PurInvoice>
"Bob Smith, , , , , , , , , , ,"
"<! ""no. of details"", ""quote/Order no. Optional"", ""InvoiceNo"", ""entry date mm-dd-yyyy"", ""total amount"", ""discount rate"","
"<! ""discount days"", ""net days"", ""freight amt"", ""tax information"""
"1, ,""RMay2020"",""5-1-2020"",""150.00"", ""0"", ""0"", ""0"", ""0.00"""
"<! ""item no."", ""quantity"", ""price"", ""amt"", ""tax information"""
"1001,""1"", ""150"",""150.00"""
</PurInvoice>

Above is the error.

Erzsi_I said:

you should be using "12001" for the version

Richard S. Ridings said:

I always use 12001.