Looking for a how to guide on running the year end close in NAV? Here are 3!

All your journal entries are done, all of your modules balance to the general ledger, and your inventory period is closed. You are ready to get that income statement rolled up and close the year. Now where were those instructions? It’s not unusual to be a little unsure about the year end close process – we only get to do it annually, so no one will blame you if you can’t remember exactly what you did last year, and in what order. Here are a couple of resources to help you out.

ABC Computers, Inc. has a nice entry on their technology blog, “How to Close a Fiscal Year in Microsoft Dynamics NAV:  Instructions for Annual Closing Operations“. This goes through a quick top level summary and then a deep dive into the closing process with field by field instructions.

If video learning is more your style, Archerpoint has a short 3-4 minute video out there, “Closing the Fiscal Year in NAV” that shows the annual closing process screen by screen.

customer sourceFinally, you can always get the full manual on the year end closing process straight from Customer Source.  Log in and type in 80041 into the search box. This will get you directly to the “Finance in Microsoft Dynamics 2009” Microsoft course. Download the course and go straight to the file for Chapter 10 – Year End Closing Processes.

Remember, you can always make entries after you’ve gone through your initial income statement rollup. You don’t need to wait for that very last entry to get this process going.


Tips and tricks for a flawless budget load in NAV

Hopefully, you’ve completed your budget work for 2013 and all you need to do to finish is to load all that information to NAV so you can begin to report against your actual financial numbers. If you’ve done this before, you might already know that NAV’s budget tool can be a bit fussy and also a bit cryptic about why it won’t accept your carefully prepared data. Here are four quick tips to help you with getting that data into NAV quickly, correctly, and in one try.

1.  Export first, then import. This is the single most important detail about getting budget data loaded into NAV. You can choose to export an existing budget or even choose to export a blank new budget. Exporting a budget as your first step establishes a working template you can populate your data into, including dimensions. As long as you start with this template, you are already most of the way there to a successful NAV budget load.

budgetload

2.  If you’re using dimensions, validate your data against the provided drop downs. Make sure all budget lines that use dimensions are only using valid dimension names. Any deviation from the allowable values that already exist in NAV can cause your budget load to error out or load without balancing.

budgetload2

3.  Clear the formats from your numbers. Once you’ve copied and pasted or typed your numbers into your Excel template, use the Excel “Clear Formats” function on all cells that contain a numeric value to make sure they are all returned to a formatted status of general. NAV does not accept any other format than the one in the template, and use of other formats, including use of commas in the numbers, will cause the budget tool to give an error and keep you from loading your budget successfully.

budgetload3

4.  Use the “Add Entries” option for a brand new budget load and the “Replace Entries” option for a subsequent version. The add entries option should only be used for a brand new budget load, otherwise the entries will be added on top of the already existing entries, doubling or tripling them. If you need to load a second or third version or some type of correction, always use the replace entries option instead of the add entries option. If you really get stuck with a bunch of errors, the best thing you can do is delete your budget and reload from scratch.

budgetload4

Take one last look through your data to make sure it’s accurate and exactly what you expected. You can use the budget tool to do this, or even better, put together a quick account schedule that shows your entries using “G/L Budget Entries” instead of “G/L Entries”. Make sure to look at your total balances, balances by fiscal period, and balances with dimension filters applied. Once you’re satisfied that all your budgeted data has loaded correctly and completely, you’re ready to produce financial reporting showing actual versus budgeted numbers!

This posting is one of the Top 20 Most Viewed in the last year! Follow this link to see the entire list.


Learning about Microsoft Dynamics NAV 2013

My company has started seriously discussing what we’re going to do about upgrading our NAV ERP system. With NAV 2013 released to market in October, we’ve got plenty to talk about. Of course, just like you and your companies, we’re nailing down exactly what the benefit of upgrading will be to our company specifically. We’ve talked about performance improvements and greater ability to get to data needed for reporting, but some of those concepts can get pretty intangible in these beginning discussions.

We’ve already talked about the big concepts, but what people really want to know about right now are the real concepts:  exactly how will an upgrade in the software increase our productivity, make us more efficient in our jobs, and ultimately, help us to drive revenue, decrease costs, or increase cash?

So, I’m beginning to gather ways to start to show people at my company, in a tangible way, what the upgraded version can do for them. Here’s where I’m at so far:

1)  Get groups of stakeholders to start to attend webinars about NAV 2013. I’ve had to chance to attend Microsoft Convergence and see all this stuff, they haven’t. I need to get them exposed to seeing this incredibly different version and what it can do for them. One way I’ll do this is to have them attend webinars sponsored by the NAV user group, NAVUG. They’ve got one scheduled called “A Guided Tour of NAV 2013”, and I’ve got a group organized to attend already.  I’m betting we’ll see quite a bit of material about NAV 2013 from the user group in the next year. One of the best things about the user group webinars is that they’re recorded, so if we want to review the webinar later, anyone in my company has that option.

2)  Learn as much as I can about the nitty-gritty details so I can promote them in a real way. I’m constantly searching the web (seriously, I “Bing” everything) for new information about just about anything. Right now, I’m focusing on NAV 2013. I just found a great YouTube video, “What’s New Dynamics NAV 2013 – User Productivity Enhancements“. In six quick minutes I got about five takeaways that I can start to use. My favorite?  NAV 2013 has improved error messages to help end users resolve problems. I’m going to take this info back to work with me and make sure people know we could have less help desk traffic because the new NAV version makes it a lot easier for end users to solve their own errors on the spot.

3)  Get a test copy of NAV 2013 installed so I can start to play around with it myself. I’ve done this with previous versions, so now it’s time. I can get a demo copy installed and start touring the menus, trying things out, and teaching myself how to use the new version. What’ll I try out first?  I can’t wait to get my hands on the cash flow forecast!  Once I’ve got some level of mastery of the new version, I can start showing folks what improvements will apply to them personally, in their jobs.

I’ll keep posting here as I find useful things to share with you.  Hopefully, as you begin your process to discuss the upgrade plan for your company, you’ll find some ideas on things that’ll work for you and your companies.

This posting is one of the Top 20 Most Viewed in the last year! Follow this link to see the entire list.


Aging methods in NAV – which buckets are you looking for?

When running any type of financial report, it’s important to ask the right question in order to get the right answer. When running your accounts payable or accounts receivable aging reports, it’s especially important since there are three available options that will give you the same total answer but will break your transactions down into different aging bucket categories. Choosing the correct option for the question you actually want to answer is the key.

Question #1:  How overdue is the invoice?

By choosing the Aging Method of Due Date, you are asking NAV to age each bucket on your aging in intervals based on the Due Date of the invoice. Remember the due date is based on a calculation that applies payment terms against the document date of the invoice.

Question #2:  How many days have passed since the invoice was posted?

By choosing the Aging Method of Transaction Date, you are asking NAV to age each bucket on your aging in intervals based on the Posting Date. This is sometimes confusing to new users since on both the purchase and sales invoice forms, the two available dates are posting date and document date. The posting date should always be the date you want to post the invoice to your books and therefore the fiscal period the invoice will report in. For the purposes of your aging reports, posting date is equivalent to transaction date.

Question #3:  How many days have passed since the vendor billed us – or – since we billed the customer?

By choosing the Aging Method of Document Date, you are asking NAV to age each bucket on your aging in intervals based on the Document Date. This one makes a little more sense to folks because at least the terms are the same. But darn us accountant types, we often call the document date the invoice date when we’re referring to it. Basically, this date should be the date your vendor has provided on the invoice, or from the customer side, the date you shipped and therefore the date you provided on the invoice to the customer. Any payment terms defined on the account will use the document date to calculate the due date.

An example of two invoices shown with all three aging methods

In a perfect world, our posting dates and document dates would all be the same. Let’s pick a perfect example with posting date of 11/01/10 and document date of 11/01/10 and payment terms of Net 21. This would calculate a due date of 11/22/10 on this invoice.

Then let’s pick an imperfect example. Let’s pretend someone at our company turned in that 11/01/10 invoice sometime in December, after the November books were closed. We still need to book this late invoice, so we’ll choose a posting date of 12/01/10, but since it was not the vendor’s error, we’ll use their invoice date of 11/01/10 in order to calculate the payment terms correctly.

Now, let’s look at an aging as of December 15th, 2010, all three ways. Take note that for all three methods, the balance due is exactly the same. The differences appear in how the aging buckets are defined and how transactions age into the different buckets.

Aging Method of Due Date

Key difference here is the aging buckets start calculating at the due date, so you’ll see column headers of current, up to 30 days, 31-60 days and over 60 days only when using this aging method.

Aging Method of Transaction Date

This aging is based on the posting date, the date that corresponds to the fiscal period you posted the invoice in. Note the late invoice with a 12/1/10 date shows as current.

Aging Method of Document Date

This aging has the same buckets as the one run with transaction date, but is based on the document date or invoice date.

This posting is one of the Top 20 Most Viewed in the last year! Follow this link to see the entire list.


Business Intelligence and Reporting Track helps solve user challenges at NAVUG Forum.

Jason Chance, Senior Programmer/Analyst at Seventh Generation and Business Intelligence and Reporting Track Leader for NAVUG Forum, guest blogs today on what the BI and Reporting Track has to offer end users at NAVUG Forum, the annual NAV end-user conference held in Seattle, October 15-18 2012.

Without fail, whenever I lead a NAV roundtable discussion or training class, people talk about the reporting. I’ve only met a handful of people who are completely happy with their business reporting and most of them have spent significant resources developing reporting solutions outside of NAV. But before you throw in the towel on reporting in NAV, and spend a lot of time and money, you owe it yourself and your organization to understand what’s available in NAV. This is where NAVUG Forum 2012 comes in.

NAVUG Forum is an excellent event led by NAV users and professionals. It’s not a sales pitch. It’s not a glossy brochure full of fluff. It’s real NAV users sharing their experience and insight gained through years working with NAV. In the reporting and BI track we’ll focus how you can get the most out of the existing tools in NAV. With sessions like Reporting 101 and Reporting 102, you’ll learn how to create and modify NAV reports. Sessions on the Role Tailored Client will show you how to use the RTC to customize the data that you see in NAV. The Analysis Views and Jet Reports session will highlight two often under utilized reporting tools in NAV. The NAV 2013 sessions will give you a preview of what to expect in the newest version of NAV.

If you have issues and concerns with your reporting capabilities, chances are someone else has the same concerns, who knows, maybe they’ve already solved their problems. Come to NAVUG Forum, learn from your peers, build a network of colleagues that can help you get the most out of NAV.

See you in Seattle.


Microsoft’s concept of how 2019 will look like

Microsoft Dynamics NAV users have already gotten the chance to see Jesper Lachance Raebild’s video demo using Microsoft Kinect in a NAV manufacturing environment.  If you missed it, find the link to the video here.

What else does Microsoft have in store for us?  Take a five minute break to see what 2019 could look like.