Recently, we received the question of whether a user could enter a journal entry for an adjustment to a closed year in Dynamics GP. The answer is that, this is possible depending on how far back you need to post. The rule follows that you cannot post to more than one closed year. So if I have closed 2012, I can only post back to 2011 and no further. As such, when closing the current year, it is a good idea to verify that all closing entries and adjustments to the previous year have been made.
Let’s say you are ready to close 2012 but need to post a JE adjustment for 2011. To do this, you will need to reopen the fiscal period in which you will be posting by navigating to the Fiscal Periods Setup window. Go to Microsoft Dynamics GP > Setup > Company > Fiscal Periods.
Select the year that needs to be reopened. Then, deselect the appropriate checkbox corresponding to the period and module you need to reopen. In my case, I have deselected the Financial module for December of 2011 because I need to make a journal entry adjustment to December 2011
Next, you will need to verify that you are allowed to post to history. Verify that the Allow Posting to History option in the General Ledger Setup window is selected. Go to Microsoft Dynamics GP > Tools > Setup > Financial > General Ledger.
Now, you are ready to create and post your transaction entry for the closed year. Once you are finished, go back to the General Ledger setup and unmark the Allow Posting to History option (you may leave it marked if that is the default setup), and close the same fiscal period that was opened earlier, using the Fiscal Periods Setup window.
General Ledger Setup – Microsoft Dynamics GP > Tools > Setup > Financial > General Ledger
Fiscal Periods Setup – Microsoft Dynamics GP > Setup > Company > Fiscal Periods
If you do need to post to more than one closed year, Microsoft does offer a service to achieve this. For more information, please contact firstname.lastname@example.org.
Corporate CFO’s, Controllers, Accounting Managers and IT professionals alike gathered in the mezzanine of Stone Brewing Co. last night to view demonstrations highlighting the new features of Microsoft Dynamics GP 2013. This was the third year that Tridea Partners has hosted a product launch event, and 7th customer event hosted at the local brewery, and Tridea client.
The night kicked off with hors d’oeuvres and drinks, and a networking session where industry professionals were able to socialize with peers from all industries.
Craig Crescas gave a Dynamic presentation on GP 2013, and had his audience on their feet about the new product launch. The night was an overall success, leaving attendees excited about GP 2013’s innovative new Web Client, and features like document attach, dashboards, enhanced integration to Excel and hundreds of new functionality features – to name a few.
For a more extensive Dynamics GP 2013 overview, click here.
If you were unable to attend the event and would like to request a demonstration or consultation on Dynamics GP 2013, please contact email@example.com.
Microsoft Dynamics AX 2012 offers multiple ways to simplify and expedite the procurement process. One of the many helpful features included in the procurement and sourcing module is the ability for purchase orders to be created automatically upon purchase requisition approval.
Two options are offered in the creation of a purchase order from a purchase requisition: manual or automatic. For a purchase order to be created manually, the purchase requisition must first move through the purchase requisition workflow approval process. This process varies from business to business. Once the purchase requisition has been approved, the purchasing agent navigates to the ‘Release approved purchase requisitions’ form, chooses the approved purchase requisition, and selects the ‘New Purchase Order’ button. This process can be time-consuming if your business handles numerous purchase requests.
Automatic creation of purchase orders is set up by navigating to the Procurement and Sourcing Purchasing Policies form.
Use navigation path: Procurement and Sourcing>Setup>Policies>Purchasing policies
-Edit the current purchasing policy or create a new purchasing policy
-Under Policy rule type, choose Purchase order creation and demand consolidation
-Select an existing policy rule (by double-clicking on the policy rule line) or create a new policy rule (by clicking on the ‘Create policy rule’ button)
This opens the Purchase order creation and demand consolidation rule form:
-Choose Manual purchase order creation
-Click the ‘Automatically create purchase orders’ radio button to select it
One of the biggest complaints from clients has been that Dynamics CRM does not have a built in spell checker like other Microsoft applications. However, with the release of an Internet Explorer add-on called Speckie, you can now spell check fields and web emails in Dynamics CRM. The add-on is free for personal use, but has a small fee for commercial use; please review the licensing agreement at http://www.speckie.com/license.
Once you have downloaded and installed Speckie.
Open Internet Explorer
Click on Tools
Select Speckie Settings
Check the box: “Enable spell check in single line edit fields”
Click “Apply” at the bottom of the page
Now you are ready to use Speckie with Dynamics CRM in an IE web browser. Fields on forms and web emails will have the distinct red wavy line (this option can be changed in Speckie Settings) if Speckie believes a word is misspelled. This can be a bit of a nuisance for names and places but can be a life saver for email correspondence or in notes/description sections.
It’s almost that time again. Soon it will be time to complete another year-end close in GP. Since GP will only allow adjusting entries to the SINGLE LAST closed year in GP, it can sometimes be a scary process for users. Due to ongoing audits or other various factors, it may be inevitable that adjustments will be needed for more than just one historical year. Without closing a year, the amounts for balance sheet accounts will not roll over as beginning balances for the next year. For those instances, here is a little trick that will allow for accurate balance sheet reporting, without having to complete the official year-end process in GP.
Below is an example of a Management Reporter column definition. In this example, column B is mapped to pull YTD data from the last month of the last fiscal year. Column C is mapped to pull YTD information for the current fiscal year. Both columns B and C are configured as “non-printing” columns. Finally, column D is a calculation that adds columns B and C. Voila! Accurate balances without closing the year in GP.