Often, clients will ask why a particular Cash Receipt is not displaying in the Bank Reconciliation when it comes time to close the month. Many times, users will forget that a Bank Deposit is required before the transactions will display in the Chequebook subledger. This is an important security step as the same person receiving funds should not be the same person depositing those funds into the bank. Further, cash receipts are often grouped together when deposited into the bank, thus, making one single large bank transaction instead of many small transactions which may need to be reconcile.
To complete a Bank Deposit, navigate to Transactions > Financial > Bank Deposit. In this window, you will find three Types: Deposit with Receipts, Deposit without Receipts, Clear Unused Receipts. We recommend all clients use only Deposits with Receipts as this forces users to perform Cash Receipts from a Customer in order to deposit funds into the Bank. Depositing without Receipts can cause differences between the General Ledger and the Chequebook subledger due to the fact that the Bank Deposit Entry window does not have General Ledger distributions associated with it. Clear Unused Receipts only applies to situations where a Cash Receipt should not be deposited in the Bank which can also lead to differences between the General Ledger and the Chequebook subledger.
Our clients will often have the need to attach supporting documentation to transactions within Dynamics GP. These might be for odd / correcting entries, entries required by auditors, or large dollar value entries. Further, it is good practice to attach supporting documentation for transactions if possible.
To attach supporting documentation to a transaction within GP, select the yellow paper icon beside the transaction number within the entry window for that transaction. This icon is also available within master data setup widows & essentially every other window within GP. Once within this window, select the paperclip icon at the bottom of the window (Note: Your system admin may have to enable this functionality to have this icon appear). This will open a new OLE Container window wherein one can select Edit > Insert New Object. From here, the process is as simple as selecting the file & clicking Attach within the note window.
WebSan has found this feature very helpful to our clients whenever they need to track down the supporting documentation for a transaction. As transactions move throughout there life-cycle in Dynamics GP, they will maintain the supporting documents attached to them, making audits a breeze.
Once a project is finished, user should close out that project within Dynamics GP. This helps to avoid errant postings to the project & ensures accurate reporting.
To close a project within Microsoft Dynamics GP, first set the status of your project to Completed within the Project Maintenance window. Then, navigate to Project > Transactions > Project Closing to access the Project Closing window. Within this window, select the Contract Number that the completed project belongs to. All the completed projects for that contract should then appear in the listing below. To close a project, check the box under the Close column & select Process.
Users should note that even though a project is set to status of Completed, there may be additional transactions that may need to be completed prior to closing the project. If additional transactions are required, the box under the C* column will be blank. To obtain a listing of the transactions yet to be completed for a 'Completed' project, select the blue arrow beside the Project number field within the Project Closing window. This will open the Project Closing More info window wherein users are presented with a check list of all the tasks required prior to closing the project.
There are times when users may have completed check list items, but they do not display within GP as completed. If this occurs, it is good practice to run the PA Reconcile Utility. This utility will search through the GP transaction tables to verify what activities have truly been completed. To access this window, select Project > Utilities > PA Reconcile. Select a data set to reconcile and then click Process. The utility is fairly quick depending on the volume of data within your Dynamics GP environment.
It's a Friday afternoon, 3pm, going into a long weekend. You are already going to hit traffic heading up to the cottage if you leave now, however it won't be as bad as in a couple of hours. You just finished a modified SOP Blank Invoice Form and would like to import it into your client's production environment. As you click the import button in Customization Maintenance, your heart starts to race as you cross your fingers and pray that the REPORTS.DIC file is not locked by any users....and you get the "Unable to open customizations dictionary" message. The afternoon sun will have to wait until tomorrow.
When importing customized reports through Customization Maintenance, users accessing the reporting dictionary will need to log out of Dynamics GP to have the report import successfully. This can be a pain and a scheduling nightmare for users and yourself alike. "There has to be a better way!" Well, luckily, there is. If you have access to the REPORTS.DIC file found in the "Microsoft Dynamics/GP/Data" directory, then you can import the modified report straight from this dictionary file using Report Writer (this is assuming that you developed the report in a test environment and would now like to push it through to production). To do this, follow the steps below:
Step 1: Copy the REPORTS.DIC file from your test environment to a local or network shared drive that is accessible from the production server.
Step 2: Log into the production environment with 'POWERUSER' access and launch Report Writer (Microsoft Dynamics GP menu >> Tools> Customize >> Report Writer).
Step 3: Click 'Report', then click the 'Import' button:
Step 4: It will ask you to browse to the path of the REPORTS.DIC file that contains the modified report you would like to upload. Click the ellipse (...) and select the reporting dictionary that you saved from the test environment.
Step 5: All modified reports from this dictionary file will be displayed in the left menu. Select the one you would like to import and click 'Insert'. If a modified version of that report already exists in the production environment, it will ask you if you would like to overwrite the existing report. Click the 'Import' button.
Step 7: Close Report Writer and if prompted to save, click 'Yes'. If this is a newly modified report, don't forget to set the ID in Alternate/Modified Forms and Reports in the Administration module.
That's it! No more waiting for all users to log out of the system. The next challenge is sneaking by your boss's office without him noticing.
Our Time and Expense Management System offered by WebSan Solutions Inc. allows the employee to easily include and process any expenses that he or she may incur on a company credit card, along with any expenses that were not processed through the company credit card.
This feature is great for the finance department, as they don’t need to do any additional work on their end to process the expense, or to make sure that the appropriate amounts get paid to the employee and the credit card issuer. All that work is done by the employee who incurred the expense.
When an employee is set up with a company credit card, all he or she needs to do when entering in an expense, is to select the option in the drop down box that is provided and the system automatically sets up payments in Microsoft Dynamics GP to be paid to the credit card vendor for the marked entries.
By: Matt Locke, Application Developer, WebSan Solutions Inc. a Microsoft Dynamics GP Partner and 2013 Canadian Channel Elite Awards Finalist.
Want to learn more about Dynamics GP, enroll in one of our WebSan University courses. Course are instructor lead, contain certification tests & all students receive a certification of completion.
Our next course in August 29th from 1 - 5 pm.
Check out our YouTube page for great Dynamics GP Training videos and other informative tips!
WebSan Support plans are available for purchase online using PayPal and all major credit cards. Enable your team to get the cost-effective support it needs. Get started now!
When a user posts an individual transaction in GP, that transaction will likely display in the Financial Series Post, saved to a batch with an odd, automated ID. These IDs are auto-created by Dynamics GP & are based on the source document / originating module from which the transaction was posted. Generally, the first 2-3 characters of the these Batch IDs are based on the module, with 3 or so more characters to identify the transaction type. this is or course followed by a numeric counter.
If one reviews the Source Document listing in GP, that will generally tell them what all the abbreviations represent. For those more technical, source documents can be found in SY00900 in the database.
Below, I have listed a number of the more common prefixes to an automated Batch ID and have noted the module which they represent.
|POP||Purchase Order Processing|
|RMA||Return Materials Authorization|
|SOP||Sales Order Processing|
Many companies have a need to grant Dynamics GP users access to a window, but not all functionality within that window. For example, many clients will want users to be able to input invoices, but not post them individually. Instead, they will force users to save invoice transactions to a batch such that a manager can review the source documents and post. An easy way to achieve this is through Field Level Security which allows the Dynamics GP admin to restrict user access to singular buttons within a window (such as the Post button).
To configure Field Level Security, navigate to Microsoft Dynamics GP > Tools > Setup > System > Field Level Security
This will open up the Field Level Security window. Within the window, select Add to create a new restriction.
This will open the Field Security Maintenance window wherein one defines a the window and field to restrict. Within this window, enter an ID and Description for the restriction. Then select the Product Name, Form Name, Window Name & Field Name using the look-ups within the window.
This will open the Resource Explorer window that makes finding & selecting the appropriate window and field much easier. All windows are organized by module & then alphabetically. Once a window is selected, all fields within that window will display alphabetically as well. Select the appropriate window and field & select OK.
Back in the Field Level Security window, one can now select Users & Companies to which the restriction should apply. Then, select the Field Security ID created to apply to the user / company combination. Once complete, select Apply & the restrictions will instantly be in place for the users.