Codename GP "12" Preliminary Features Series – 2 of 4

November 18, 2011

Codename GP “12” Preliminary Features – Part 2 

This is article is part 2 of 4 from the series Codename GP “12” Preliminary Features. Some images and content reproduced with express permission from Microsoft Business Solutions, a division of Microsoft Corporation.

DISCLAIMER: These features are subject to change.

Yesterday, in Part 1 of the Series we saw some of the new features in the Simplicity pillar: Select printer at Print Time, improvements in the Fixed Assets calendar setup process, reprinting of check remittances, and the ability to print SSRS reports directly from within Microsoft Dynamics GP, in what seems to be a race to replace Report Writer reports.

Today, we will take a look at some of the features in the Productivity pillar, whose aim is to “enhance productivity from application configuration to frequently performed tasks”.

Productivity Features

System Enhancements

Among the features being worked, the Named System Database and Multi-tenant Applications are two of the most important features aimed to change Microsoft Dynamics GP architecture. I have covered these two features extensively in my Microsoft Dynamics Communities column articles:

Microsoft Dynamics GP “12” Named System Database Architecture
Microsoft Dynamics GP “12” Multitenant Service Architecture

Bank Reconciliation Enhancements

In the Bank Reconciliation front, you can expect the new Sub Ledger Reconcile BR to GL feature. If you are worried about your checkbook balance and GL cash account not matching, this new option will present you with reason for the out of balance conditions: a batch not posted, a voided GL entry, etc. This new feature also looks at the Receivables and Payables module.

By adding the checkbook ID as a field, you can compare the checkbook balance to the Cash Account in GL. This new reconcile tool will attempt to match records on transaction source, date, and amount and will report matched transactions, unmatched transactions, and potentially matched transactions, with the capability to drill back to the document and/or journal entry.

You can then save the output file and date when the reconciliation was performed so you don’t need to run the reconcile again. This option has been retrofitted to the other reconciliation processes.

Fixed Assets Enhancements

Yesterday I talked about the Fixed Assets Calendar Setup enhancements. You can expect other enhancements in the Fixed Assets GL Posting process – you will now be able to create batches of fixed assets transaction. As with every other batch in the system, you will now be able to review what is going to post to GL before it is posted, via an edit list.

You can build the batch, insert restrictions – today, you are only able to enter a date range and Fixed Assets pulls everything – such as dates, transaction type (depreciation, transfer, retire, addition) review the batch, make changes, and post. You can post in detail vs. post in summary – the only option available today. Going forward, each distribution line in Fixed Assets will have an equivalent distribution line in GL.

Other enhancements in Fixed assets will entail Mass Depreciation Reversal. This one is much needed as, if you have depreciated 1,000 assets through the end of the year by mistake, you would have to manually back out each of the 1,000 assets. In GP “12”, you will be able to perform a mass reversal of the depreciation – all assets at once.

EFT Enhancements

EFT Payables and Receivables will see the introduction of the Bank Administration Institute (BAI). The process will use the current Configurator to setup an EFT file based on BAI standards.

Distribution Enhancements

Purchasing Receivings will now see Tolerance Levels handling for quantities being received. If you setup a tolerance level, any quantities not received within the tolerance limits will automatically be cancelled on the Purchase Order. You will have the option to setup whether you want to do this automatically or prompted.

SOP and POP Drop Ship for Serial/Lots items – GP “12” will allow you to track serial/lot numbers from vendors. Users will have the ability to enter the serial numbers for any product being drop-shipped, unlike current released versions of GP. If you have a SOP invoice linked to a PO then the Serial/Lot will come across onto the SOP invoice.

As you can see, there are tons of enhancements in all of the above modules. GP “12” is geared towards solving some of the complexities in business processes that were a bit neglected in current releases.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC


Wise up with Wiseguy

September 6, 2011

Just a few days aback, I wrote an article referencing the acclaimed 1984 movie, Ghostbusters. In this occasion, my friend and fellow MVP, Mark Polino, makes an appearance with his new short fictional story, Wiseguy.

Wiseguy is a new twist to the classic mob tale. Prospective mobster Joey is stunned to learn that the family business is going to start filing tax reports with the IRS due to the power of Microsoft Dynamics GP. With the help of Jersey girl, Isabella, Joey must learn to collect cash using Microsoft Dynamics GP, instead of the traditional baseball bat method.

Wiseguy highlights some powerful features in Microsoft Dynamics GP including the Collections module, Accounts Receivable, EFT, and Scheduled Payments. It also highlights The Closer and The Validator. The story shows how learning Microsoft Dynamics GP can be fun and entertaining.

You can download Mark’s work for free using a code from Reporting-Central – With a name like Gianmarco Salsano backing up Mark, you can understand why Wiseguy is becoming so popular.

By the way, Wiseguy was one of my favorite 80’s TV series, featuring Ken Wahl as agent Vincent Terranova. You can read a bit more about that series here.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC

International ACH Transaction (IAT) functionality for Microsoft Dynamics GP 10.0

August 20, 2009

For those of you awaiting key EFT enhancements in Microsoft Dynamics GP, here is a bit of news published back in July — a bit late, but still worth sharing.

The National Automated Clearing House Association (NACHA) and Office of Foreign Assets Control (OFAC) have published new specifications for International ACH Transactions (IAT). As of September 18, 2009 the new IAT code will need to be in place that requires participants to identify international transitions and to code these transactions as IAT transactions.

Additional information regarding the specification can be found at

Microsoft Dynamics GP 10 will support the new International ACH Transaction (IAT) ACH format changes with the release of Microsoft Dynamics GP 10 service pack 4. The electronic file transfer (EFT) formats will be changed for Microsoft Dynamics GP Payables and Receivables modules.

Note: The Royal Bank of Canada file format specification changes will also be included in 10 service pack 4.

The latest word on service pack 4 is that it will be available on the week of August 24.

Until next post!

Mariano Gomez, MIS
Maximum Global Business, LLC

Implementing PayPal exports with EFT for Payables

October 7, 2008

Recently I had a chance to look into a post on the Microsoft Dynamics GP newsgroup where the consultant required the ability to upload hundreds of payments into PayPal as a business process using the EFT for Payables module.

At first, I thought the issue was more related to the interfacing abilities with PayPal, but soon discovered this was not API-related — PayPal also provides an API that can be called via web services.

It turns out, PayPal allows its customers, in its simplest form, to upload a mass payment tab-delimited text file containing the email of the payee or recipient, the amount to be paid, currency, a unique identifier for the recipient (which can easily be the vendor ID from GP), and a note or transaction description. For more information on PayPal’s formatted file click here.

Knowing this, the first limitation with EFT Payables is its ability to generate tab-delimited files. However, it does provide the ability to create fixed length files and XML files which can certainly be converted to tab-delimited with either Microsoft Excel. Nonetheless, I decided to explore what it would take to implement PayPal and here are the steps I came up with.

Setting Up the EFT Payables Options for PayPal

NOTE: the following steps are for Microsoft Dynamics GP v10. However, they can easily be adapted for previous releases.

1) Setup a checkbook ID for PayPal. Go to Cards > Financial > Checkbook and enter minimal information as shown below.

2) Click on the EFT Bank button to add EFT information for PayPal. Choose Other 1 from the Bank Country/Region drop-down. Also, set the ISO Currency Code field to one of the supported PayPal currency codes and preferably that of your functional currency. For a list of PayPal supported currencies click here.

NOTE: PayPal only supports payments made in one currency code per file.

Leave all other fields empty.

3) Click on the Payables Options button to open the Checkbook EFT Payables Options window to setup the file format and the default file output options for the EFT file. Set the EFT Payment Numbers radio group to Use EFT Numbers — this information is irrelevant to PayPal, but necessary to configure EFT; setup the Default Output Files as needed.

In the File Format radio group select Single Format and type PAYPAL in the field. Add the new format when prompted. This will open the EFT File Format Maintenance window. You will add 5 fields at the Detail line type level as shown in the following illustration.

NOTE: I used a flat file format, but XML can also be used as a format defining the tags and mapping the data in a similar manner.

For each field map the following data:

* Email Address maps to Address Electronic Funds Transfer Master.EFT Bank Account
* Amount maps to PM Paid Transaction History File.Document Amount
* Currency ID maps to Checkbook Transaction Electronic Funds Transfer.ISO Currency Code
* Vendor ID maps to PM Paid Transaction History File.Vendor ID
* Description maps to PM Paid Transaction History File.Transaction Description

4) Click on the Save button to continue. Click here to download a copy of the PAYPAL file format that can be used to be imported into EFT File Format Maintenance window.

5) On the Checkbook Payables Options window, click OK to save and exit the window.

6) On the Checkbook EFT Bank Maintenance window, click OK to save and exit the window.

7) On the Checkbook Maintenance window, click on Save to save the changes.

Setting Up the Vendor Card

1) Open the Vendor Maintenance window. Go to Cards > Purchasing > Vendor and select a vendor ID.

2) Click on the Address button, then choose an address ID (typically the one used for remittances).

3) Click on the EFT Bank button to open the Vendor EFT Bank Maintenance window. Choose Other 1 from the Bank Country/Region drop-down list. Since PayPal uses emails instead of bank accounts, the Bank Account Number field will be replaced with the Vendor Email address.

NOTE: Internet Address information is not exposed to EFT; hence the email address associated to the Vendor Address cannot be used.

This should complete the setup! Save all information and close all windows.

Testing it All!

Use the EFT Prenotes window to generate the prenotes. This will pick up all transactions created in the past and will allow you to get a glimpse at the new PayPal file. Use Microsoft Excel to convert the generated payments file to a tab-delimited file, required by PayPal.

Until next post!

Mariano Gomez, MIS, MVP, MCP, PMP
Maximum Global Business, LLC