Microsoft Dynamics GP Budget Import Issue

Microsoft Dynamics GPBudgets in Microsoft Dynamics GP are easy to maintain using the Budget Wizard. However, we do regularly field calls from clients reporting that the budget import is not working.

The problem reported, was the same as the problem always is; the budget template was not in the correct format.

The first image is the header of the one they were trying to import and the second is the Master budget I exported from GP to show them:

Excel Budget

Excel Budget

As you can see the former budget template has an extra row in the header; this is sufficient to stop the import working.

Everytime we have had this error reported we have found that something was changed in the budget template: a new header row, a header row being deleted, a column being added (the latter is the most common.

The client removed the extra row and was then able to import the budget.

What should we write about next?

If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.

Your Name

Your Email

Suggested Topic

Suggestion Details

Looking for support or consultancy with Microsoft Dynamics GP?

I no longer work with Microsoft Dynamics GP, but the last company I worked for was ISC Software in the UK; if you’re looking for support or consultancy services with Microsoft Dynamics GP you can contact them here.

6 thoughts on “Microsoft Dynamics GP Budget Import Issue

  1. Cheryl says:

    HELP! I do not have extra lines in the header and my budget will not upload. I downloaded a new template and the only thing I changed was deleting two rows that had zero budget.

    1. Ian Grieve says:

      Hi Cheryl,
      The only times I’ve seen the import fail entirely, is when the template has been changed in some way; a change in header rows or a change in columns; simply removing a couple of lines should not cause it to fail.

Leave a Reply to Ian Grieve Cancel reply

Your email address will not be published. Required fields are marked *