Page 1 of 5312345678910...2025303540...Last »

Setup information for Electronic Reconcile Format Configurator

Hi everyone,
Found a very important article on Format Configurator in Electronic Bank Reconciliation
Cheers..
This article contains information about setting up the Electronic Reconcile Configurator.

MORE INFORMATION
General Setup for Electronic Reconcile Format Configurator

The process of setting up the Format Configurator in Electronic Reconcile is very lengthy and the following detailed steps will help to make this setup easier. Before setting up the Format Configurator, you must have a printed copy of the download file format specifications from your bank. Because bank formats vary greatly, you must contact your bank and request these specifications for the file format. The format specifications will contain details about each field being downloaded and values of all relevant codes for the bank. This information is necessary to be able to setup the Format Configurator as each bank is different and there is no standard format to enter.

Electronic Reconcile Format Configurator (Routines | Financial | Electronic Reconcile | Configurator):

Section 1 – Enter Format Information

Bank Format - The Bank Format field is an identifier for your format. Enter a unique name for this format, but typically this is the name of your Bank.

Description - This is a required field. Enter an additional description for the Bank Format.

File Format - Follow the steps below for the version you are using:

 -Microsoft Dynamics GP 2010 and prior versions – The File Format field can be selected from the drop-down list as Fixed Field, Comma Delimited, or Tab Delimited. The bank determines which option from the list that you will select. Therefore, you must contact them if the format specifications do not state the format to use.

-Microsoft Dynamics GP 2013 - The File Format field has a choice of BAI or User Defined. If you are using the Bank Administration Institute format, select BAI. For all other formats/banks, select User Defined. In the File Type field, you can choose Fixed Field, Comma Delimited or Tab Delimited as specified by your bank.

Uses Status Codes option is marked only if your bank uses Status Codes to additionally define Transaction Codes. This information is also determined by each bank. Therefore, if the format specifications do not state if your bank uses Status Codes, you must contact the bank. (This is not used very often.)

Record Type Identifier – The Record Type Identifier will contain Start Position and End Position fields if you are using the Fixed Field format and a Field Number field if you are using Comma Delimited or Tab Delimited file formats. This will be where the system should look in the line to determine what type of line (header, footer or detail) it is. If the bank doesn’t use a record type code, then you can improvise by selecting a fixed value in the file.

-Fixed Field – Enter the starting and ending position of the field that will contain the value for the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

-Comma Delimited or Tab Delimited – Enter the number of the field that contains the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

Save the Format after Section 1 has been completed before moving on to Section 2 of the Electronic Reconcile Format Configurator window.

Section 2 – Enter Record Types
Note You will only have to define the Record Types that are relevant to Electronic Reconcile. If a section is labeled as optional on the bank specifications, you do not have to set it up in the Format Configurator. The Detail Record Type is always a required section in a bank’s specifications.

Bank ID - The Bank ID will default in with the Bank Format from section 1 as soon as you tab into the Record Type field in the second column. This field cannot be changed or edited.

Record Type - The Record Type field can be selected from the drop-down list as Header, Detail, or Footer. All bank formats will require a Detail Record Type, but the header and footer Record Types may be optional. You may only setup each of the Record Types one time as multiple headers or footers are not available.

Record Type Code from Bank – The Record Type Code from Bank field is defined in your bank’s specifications. This field must be a unique and constant identifier for the format to match the information in the Detail Record Type. This is the most important field in setting up the Format Configurator to correctly match the download file with the reconciliation.  (So the Record Type Identifier will tell the system which column to look in to see what type of row it is, and then to look at the value in Record Type Code from Bank field to read if it is a header, detail or footer line.)
# of fields – The number of fields indicates how many fields are to be defined in Section 3. Enter the number of fields contained on the line for the Record Type being defined. This information must be entered for each Record Type that is required in the bank’s specifications.

Section 3 – Enter Field Information

When you click on a Record Type in Section 2, the corresponding number of fields will display in Section 3.

Record Type – The Record Type field in the left-most column of Section 3 will default in when you select a Record Type in Section 2.

# – The number field will default in with the number of fields that you entered in Section 2.

Field Type – The Field Type field is used to define each of the relevant fields for each of the Record Types. Select the Field Type from the drop-down list that includes options for Accounts, Dates, and amounts. If the exact name of your field from your bank’s specifications does not appear in the list, you may have to either select an option that is similar or use the Filler/Ignore option. Again, you only need to define the relevant fields, most importantly: Account Numbers, Check Numbers, Check Dates, Check amounts, Transaction Codes, Record Type Codes, etc.

Note Just as with Record Types, you will only have to define the fields that are relevant to Electronic Reconcile. If there is a field on the bank’s specifications that cannot be defined with an existing Record Type or does not have to be defined, use the Filler/Ignore option.

Format - The Format field defines the type of output format for certain fields. Formats only have to be set for Field Types that contain dates or a currency amount, as these are the only options for Formats. There are no options for text or string. Therefore, if the field is not a date or a currency amount, just leave the Format field blank. The From and To fields are used to enter the character positions of the field. Enter the starting and ending character position for each field in each Record Type. The From and To fields must be entered if using the Fixed Field File Format, so if you are using Tab Delimited or Comma Delimited File Formats you can leave these fields as zero.

Transaction Codes (Codes Entry – Transaction Codes Entry)

While still in the Electronic Reconcile Format Configurator window, go in the Transaction Codes Entry window through the path listed above in the top Menu Bar. If you have not defined the Transaction codes, you will get the message “Record Type match not found” on the error report.

Transaction Codes identify the type of transaction that each Detail line represents. Electronic Reconcile requires a Transaction Code in a configured Bank Format to work correctly. You must have Transaction Codes or Record Type Codes defined to use Electronic Reconcile. These codes must come from the bank and must be listed on the bank’s specifications.

Transaction Type – The Transaction Type field is used to define each of the different types of transactions that appear on your bank’s specifications. Select a Transaction Type from the list to match or to closely match your bank’s specifications. Note that the options in the list are the only currently supported types. At this time, the two options that will match using Electronic Reconcile are Check Paid and Deposit Cleared.

Note: In Microsoft Dynamics GP 2013, options for Transfer Credit and Transfer Debit have also been added and will electronically match in Electronic Reconcile. However, you must enter the Bank Transaction Type Codes in as defined by your bank. Additional functionality in Microsoft Dynamics GP 2013 is also that you can have multiple Transaction Type Codes for each Transaction Type.

Transaction Type Code – The Transaction Type Code field is used to enter the value for each Transaction Type and this value is given to you as part of the file specifications from your bank. Enter the Transaction Type Code value that corresponds to the selected Transaction Type. This information must come from the bank and cannot be improvised if it is not available on the bank’s specifications.

G/L Account - The G/L Account field is available only for the following Transaction Types: Interest Income, Other Income, Other Expense, and Service Charge. Enter the G/L Account Number of a General Ledger Posting Account for the adjustment that will be generated. Electronic Reconcile will automatically create adjustments for these transaction types if they appear in the downloaded file from your bank.

Note The Interest Income, Other Income, Other Expense, and Service Charge transaction types do not electronically match, and instead will create Adjustment entries on the reconciliation. (Click the Adjustments button on the Select Bank Transactions window).

Account Description – The Account Description field will default in with the description of the account from General Ledger and is not editable.

Distribution Reference – The Distribution Reference field can be used to enter an additional reference for the adjustment that will be made. You can enter a Distribution Reference if you want, but it is not a required field.

Document Type - The Document Type field will default in with the Transaction Type that you selected at the top of the Transaction Code Entry window: Interest Income, Other Income, Other Expense, or Service Charge. This field cannot be changed unless you go back and change the Transaction Type field.

Define Status Codes - The Define Status Codes button only becomes available if you have marked the Uses Status Codes option in the Electronic Reconcile Format Configurator window. Define Status Codes is only available for certain Transaction Types: Check Paid and Deposit Cleared. After selecting one of these 2 Transaction Types, you would select the Define Status Codes button to go into the Status Codes Entry window. Here you would select: Paid Check, Check Reversal, Stop Pay, or Stop Pay Reversal for the Status Type and enter the corresponding Status Code from your bank’s specifications. Again this information has to come from your bank and cannot be improvised or Electronic Reconcile will not work correctly.

Special notes to remember when setting up Electronic Reconcile:

  • You must have a printout of the file format specifications from your bank before setting up the Electronic Reconcile Format Configurator.
  • Every bank is different. Therefore, you cannot follow one standard format for all banks.
  • If you open the .TXT or .CSV file with Notepad, the system will typically not read any information after position 245. So make sure all the required fields to be mapped are in the first part of the line if your lines are more than 245 characters. The information after 245 will be read as a new line and appear on the Unprocessed Data Record error report as “Record Type match not found: Record Type = ” because there isn’t one. This would be acceptable if no fields after position 245 are not needed. If there are fields that are needed, you will need to contact your bank to see if they are able to reconfigure the file to be smaller and not exceed 245 characters.
  • The Electronic Reconcile Format Configurator only needs to be setup once when first starting to use Electronic Reconcile, and then you just keep downloading .TXT or .CSV files from the bank to match this Format Configurator.
  • The following fields must be present in your bank format: Transaction Code, Account Number, Check/Serial Number, Transaction Amount, Record Type Code, and the Bank Cleared Date. If your format uses Status Codes, then the Transaction Status Code must also be present in the configuration.
  • If you have gone through all of the Electronic Reconcile process and no transactions are marked off as cleared in your Bank Reconciliation module, most likely something is not set up correctly in the Electronic Reconcile Format Configurator. The most common error message that will be received is a “Record Type Match Not Found” error on the Unprocessed Records report that prints after trying to download.
  • If you try to re-download after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates instead of just downloading new transactions.
  • If you try to delete a Reconcile and re-enter the information after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates.
  • Make sure the Bank Account Number is unique for the checkbook that is set up with Electronic Reconcile. If the Bank Account Number is set up with a different checkbook, Electronic Reconcile will not be able to match the downloaded transactions and you will receive a message stating that the Bank Account Number is not set up.
  • In the Codes Entry window of the configurator, the types that will automatically match are: Check Paid, Deposit Cleared, Transfer Debit and Transfer Credit.
  • If you enter an increase adjustment or a decrease adjustment in the Reconcile Bank Adjustments window, the following adjustment types create an adjustment transaction in the Reconciliation Bank Adjustments window: (For example, ‘interest’ or a ‘misc fee’ on your bank statement would not be in GP (so nothing to match to), so you need the system to book the adjustment/journal entry in GP for these types.)
    • Interest Income
    • Other Income
    • Other Expense
    • Service Charge
  • If you enter an increase adjustment, a decrease adjustment, or a withdrawal in the Bank Transaction Entry window, you are prompted to manually mark the adjustment. When you receive this message, you must manually mark the records in the configurator file.
  • Checks will be matched by the Check Amount and Check Number. Deposits will be matched by the Deposit Amount and Deposit Date (within a default 8 day range, but you can override that when prompted to be a different day range.) 
  • The Bank Cleared Date can affect the matching process. GP will only clear checks in which the Bank Cleared date is AFTER the Check Issue Date in GP. GP would not clear a check on a date prior to the date it was actually issued in GP.  
  • GP will ignore any leading zeroes on a check in the matching process and in fact, will strip them off the check number when importing. Leading zeroes will not affect the matching process for the check number. GP is able to match the check number, regardless of any leading zeroes.

This article was TechKnowledge Document ID: 19396



Applies to
  • Microsoft Dynamics GP 2010
  • Electronic Reconciliation Management, when used with:
    • Microsoft Dynamics GP 10.0
    • Microsoft Dynamics GP 9.0
    • Microsoft Business Solutions–Great Plains 8.0
    • Microsoft Business Solutions–Great Plains 7.5
    • Microsoft Great Plains Dynamics 7.0
    • Microsoft Great Plains eEnterprise 7.0
    • Great Plains Dynamics 6.0
    • Great Plains eEnterprise 6.0

Read more here:
Setup information for Electronic Reconcile Format Configurator

March 25, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 5

Workflow Engine in GP 2013 R2 and GP 2015

I’ve seen a lot of activity recently on the Dynamics GP Forum, indicating confusion over what version of SharePoint works with the new GP Workflow 1.0 and 2.0.  Quick answer – none of them.  GP 2013 R2 and GP 2015 both have a native workflow engine built in, eliminating the need for SharePoint altogether.

 
Additionally, Reviewers and Approvers need not be GP users to Review and Approve workflow steps if Email Actions  is enabled.  Approval can be initiated from within email notifications generated by the workflow.

Read More:
Workflow Engine in GP 2013 R2 and GP 2015

March 11, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 18

Considering an Upgrade from Dynamics GP to Dynamics AX?


Recently I’ve delivered Dynamics GP training to new users who came from a company using Dynamics AX.  In my own experience, other than the additional features that Dynamics AX offers over Dynamics GP (which are considerable) and getting accustomed to the ability to post a transaction initiated in the General Ledger backto a subsidiary module in AX, there is a lot of commonality in the User Interface (UI) between the two applications.  This is particularly important for companies that have perhaps outgrown Dynamics GP and are considering a move to a more full-featured ERP system such as AX.  Microsoft has done a commendable job of unifying their ERP system UI’s, which offers the client the benefit of quicker and easier user adoption when moving from one application to another.
Additionally, both applications are tightly integrated with Microsoft Office tools, further easing the transition to a new system.
The first image below is of the Dynamics GP 2015 Financial module, with the menu items arranged in basically the same sequence as the Dynamics AX 2012 R3 image below it.  Notice how the menus and the Navigation Pane layout are quite similar in both applications, albeit the AX UI is cleaner, in my opinion.  Maybe the GP development team can get together with the AX dev team on that one.
Based on their comments, my recent trainees report the same experience.  They’ve indicated that adapting to Dynamics GP from AX has been much quicker than they thought it would be, primarily because of the similarities between the two UI’s. 
 
In considering an upgrade from Dynamics GP to Dynamics AX, user adoption and performance ramp-up can be relegated to the bottom of the list of concerns.

More:
Considering an Upgrade from Dynamics GP to Dynamics AX?

March 3, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 25

SOP Quick Print feature does not work when window ribbons are enabled

Happy New Year!! Hope all of you had a great time with family and friends and that you are back getting used to the daily grind once more.

Today, I want to kick off the year with an issue in Sales Transaction Entry window related to the cool ribbons implemented since Microsoft Dynamics GP 2013 R2. By now, you are probably getting used to the absolutely gorgeous user interface which features Microsoft Office style ribbons on every window. Furthermore, you probably already know that the use of such ribbons is actually customizable and in many ways optional – albeit being the default configuration – as described by fellow Microsoft Dynamics GP MVP, Leslie Vail in her article GP 2013 R2 Ribbons. As it turns out, there’s a Dex.ini switch, EnableWCRibbons=FALSE, that controls whether ribbons are enabled within Microsoft Dynamics GP or not. When ribbons are enabled, users can further customize the appearance of the action pane or return to the traditional menu bar for each window.

User Preferences window

Yesteryear (2009), I wrote an article talking about The wonders of CTRL+Q: saving and printing SOP documents in one step and how the Quick Print feature made life easier to the poor souls out there who needed a quick shortcut to printing SOP documents from the Sales Transaction Entry window. In that article I detailed the mechanics behind the feature, written by my good friend David Musgrave.

As fortune would have it, when ribbons are enabled and you are either using the Action Pane or the Action Pane Strip layouts, the Quick Print feature does not work. However, if the User Preference is returned to Menu Bar (you will need to exit Dynamics GP and re-launch for the changes to take effect), the Quick Print option (and CTRL+Q keyboard combination) works just fine.

While clearly an inconvenience, this can hardly be labeled a bug since the feature is still present within the application when the Window Command Display setting is set to Menu Bar as part of the user preferences. It would be nice, however, to have this fixed for Dynamics GP in desktop client mode. I can see how this may or may not work under web client mode as the browser keyboard shortcut combinations take precedence over the application’s shortcuts.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Read more here:
SOP Quick Print feature does not work when window ribbons are enabled

January 7, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 39

Management Reporter 2012 CU11 Company Integration with Microsoft Dynamics GP 2015

I was testing out the new CU 11 for Management Reporter 2012 today with Dynamics GP 2015. After the installation and configuration, I was trying to enable the integration and I noticed that the option to add the companies to MR for the DataMart adaptor was missing in Management Reporter Configuration Console.

More here:
Management Reporter 2012 CU11 Company Integration with Microsoft Dynamics GP 2015

December 30, 2014 · Sivakumar V · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 99

Considering a Microsoft GP Cloud Solution In 2015 | Dynamics GP …

Subscribe. Enter your E-mail address in the box below and subscribe to our blog feed. Email Address … Search Dynamics GP Blog. ← Dynamics GP Year-End Closing – General Ledger – Tips & Tricks …

Continue Reading:
Considering a Microsoft GP Cloud Solution In 2015 | Dynamics GP …

December 17, 2014 · tidestone · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 29

Microsoft Dynamics GP backups with Windows Azure Blob Storage Service

With the introduction of Dynamics GP 2013 R2, Microsoft delivered support for application database backups onto Windows Azure blob storage service from within GP itself.

Azure Blob storage is a service for storing large amounts of unstructured data, such as text or binary data, that can be accessed from anywhere in the world via HTTP or HTTPS. You can use Blob storage to expose data publicly to the world, or to store application data privately. Common uses of Blob storage include:

• Serving images or documents directly to a browser
• Storing files for distributed access
• Streaming video and audio
• Performing secure backup and disaster recovery
• Storing data for analysis by an on-premises or Azure-hosted service

In turn, Dynamics GP takes advantage of capabilities introduced in SQL Server 2012 SP1 CU2 to enable SQL Server backup and restore directly to the Windows Azure Blob service. See SQL Server Backup and Restore with Windows Azure Blob Storage Service for more information.

Note: Starting with SQL Server 2012 SP1 CU4, you can also use PowerShell to backup to and restore from Windows Azure Blob storage services.

As part of the backup and restore process, Microsoft Dynamics GP calls the syGPAzureBackupRestoreProcess system database stored procedure.


Configuring Microsoft Dynamics GP backups with Windows Azure Blog storage service

To take advantage of Windows Azure Blob storage service, you must begin by setting up an Azure storage account. The storage account is the starting point for all storage services. The storage account requirements are fairly straight forward: setup a URL prefix, associate a location or affinity group for your storage account, and determine the type of replication. See How To Manage Storage Accounts for additional information on replication options.

Note: The full URL will be the URL prefix followed by blob.core.windows.net.

Storage Account Setup

Upon creation of the storage account, the storage account name and its access key properties are required to authenticate to the Windows Azure Blob Storage service and its components.

Following the creation of the account, you will need a storage container. A container provides a grouping of a set of Blobs, and can store an unlimited number of Blobs. To write a SQL Server backup to the Windows Azure Blob service, you must have at least the root container created.

Container tab

Click on the Containers tab to setup a new container. Enter a name for the container, and select the type of access that will be provided to the container.



New Container setup

For more information on setting container access types, see Restrict Access to Containers and Blobs. Once the container has been setup, you should see your new container listed.

Container is now setup

Return to the storage account dashboard and click the Manage Access Keys option at the bottom of the window for the storage account you setup. You can copy the primary access key, which will be used to setup Microsoft Dynamics GP.

Manage Access Keys

In Microsoft Dynamics GP, go to Microsoft Dynamics GP | Maintenance | Backup to open the Back Up Company window. Follow these instructions:

1. Select the company you wish to backup
2. Choose Use Microsoft Azure storage as the destination for your backup
3. Enter the storage account name you created in Windows Azure
4. Paste the access key from the previous section.
5. Enter the URL to the container. The URL format is as follows:

https://storage-account.blob.core.windows.net/container-name

Back Up Company

6. Click on Verify account to validate your account settings and connectivity to the container then click OK to continue. The backup performance will depend on your internet connection speed.

Now that you have a pretty good grasp on the configuration, you can begin taking advantage of Windows Azure as a secure, always available option for your Microsoft Dynamics GP data. The best part is, the data geo-redundantly stored (if this option was selected when creating the storage account) and you no longer need to rely on tapes being exposed to damage.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

More:
Microsoft Dynamics GP backups with Windows Azure Blob Storage Service

December 15, 2014 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 58