Have you tried to import an Excel budget you’ve been using for YEARS into GP 2013 lately? If you’ve been using GP for a long time and have imported a budget for the last few years, this budget probably has a plethora of calculated fields and formatting.

You’ll notice that now these sheets will not import into GP. This is because of a functionality change in GP using Open XML (OOXML) to communicate with Office applications instead of using Inter-Object Communication (COM) to do so.

A short story of how they work is that COM will read the file as if you were opening Word, Excel or any Office application, whereas OOXML will read the file as if you were reading some sort of .csv file or text file, by opening up a stream in the application. COM opens the file in the background and reads the data from whatever Office application is running. The performance cost comes from having to open Word or Excel in the background. OOXML saves this performance by just having to read the XML data from the file.

For instance if you have the below in an Excel sheet:

COM will see the 300.00 value because the document is open in the background and the formulas calculate. OOXML will not see the value because the formulas don’t calculate and it’s stored as XML data. OOXML will see the following:

How can I import my old budget in GP?

The reason for the functionality change is for performance. Plain and simple, OOXML will read the data faster than COM will. You’ll see this performance increase when you export a SmartList, or when you import a very large budget.

Good news! There is a Dex.ini value you can add to the file that indicates whether to use COM or OOXML when communicating with Office applications. Just add the following value to your Dex.ini file and you can use whichever mode you want; maybe you want to keep the performance for SmartLists and only use the COM model to import your budget.

UseCOMForExcelExport=TRUE

TRUE indicates that COM will be used to communicate with Office, FALSE indicates that OOXML will be used.

Reference Material for OOXML

http://msdn.microsoft.com/en-us/library/office/bb448854(v=office.15).aspx

Reference Material for COM

http://msdn.microsoft.com/en-us/library/windows/desktop/ms693719(v=vs.85).aspx

Good luck importing!

Shawn K.

In order for the user to take advantage of the new Copy and Paste from Excel functionality, Open XML SDK 2.0 needs to be in place. By default, this is installed with GP 2013, so all users should have it.  Open XML SDK 2.0 was introduced in GP 2013 because it was much more performant than the old COM Object Model. However, some users still prefer to use the old method from GP 2010 in order to do imports for things like budgets from excel that have calculated cells.

I recently ran into an instance where the user was updating to GP 2013 R2.  When they tried to take advantage of the new Copy and Paste from Excel functionality in the GL Transaction Entry Window, nothing happened in GP. No reports or errors showed up like you would expect if the user had invalid or no information selected to be copied.

The reason for this issue was a setting that they had altered/added in the DEX.ini in order to use the old COM Object Model:

‘UseCOMForExcelExport = TRUE’

With this setting in place, they will not be able to use the Copy and Paste to Excel Functionality because it doesn’t allow GP to use Open XML SKD 2.0 which it needs in order to Paste the information from Excel to the Journal Entry. You can easily disable this setting so that you can use the Copy and Paste from Excel in GP by changing the line in the DEX.ini to ‘UseCOMForExcelExport = FALSE’, (If GP is open, make sure to close and re-launch GP). If for some reason a user would need to toggle between both the old COM object Model and Open XML SDK often, you could also create two launch files pointing each pointing at a different DEX.ini file.

I am excited about this new feature, and I hope the information above is helpful to you.  For more information on new features in GP 2013 R2 Financials please visit the link to our video below.

(Please visit the site to view this video)

Thanks,

Isaac Olson

The Microsoft Dynamics GP team will be creating blogs around our most common support topics.  We will be publishing these throughout the week in the month of September.  As the post publish I will make an active link here.

Below you will find the schedule of upcoming blog posts.

Payables

September 02, 2014 – FAQOpen apply table (PM20100) inPayables Management
September 03, 2014 – Custom fields for EFT

September 04, 2014 - Quick Setup Guide to send PM EFT Remittances in GP

Word Templates

September 09, 2014 – You must have the Microsoft Save as PDF or XPS Add-in for 2007 Microsoft Office installed to send documents
September 10, 2014 – Image Content Control in Word Templates

September 11, 2014 – Exchange E-mailing in GP 2013

GL/AA

September 16, 2014 – AA GL Issues

Encumbrance

September 18, 2014 – Everything you want to know about Approvals and Encumbrance used together

Payroll

September 23, 2014 – Employee Summary SmartList shows no data when copied/modified with SmartList Designer
September 24, 2014 – How to Process a Manual Check

September 25, 2014 – How to Troubleshoot Quarterly 941’s in Payroll!

September 30, 2014 - What Payroll changes are coming for ACA (Affordable Care Act) compliance reporting in Microsoft Dynamics GP?

Make sure to check back to this post or check back Dynamics GP Support and Services Blog at the dates listed. 

Enjoy :)

Many of the most common questions to the Dynamics GP Payables support desk involve the PM20100 table and how it affects check processing and printing. The purpose of this blog is to share some insight on this table and highlight the most common inquires we have on it.

Q. What is the PM20100 table?

The PM20100 is the PM Apply To OPEN Table for the Payables Module (PM) of Dynamics GP.  This is a table to simply hold apply or remittance information to be printed on the next check stub.
 
Q. What is the purpose of the PM20100 table?

The PM20100 will link Payment information for PM Payments in open status to open PM Invoices. This table is a temporary holding table until the Payment information is allowed to display (print) on a check in Dynamics GP. The PM10200 is the PM Apply Work table and the PM30300 is the PM Apply History table.

Q. When will PM20100 information be removed?

The Payment record will be removed from the PM20100 once it has been printed on a check.   Once the information is printed on the next check stub, it will be removed from this table.

Q. When will PM20100 information remain?

The PM20100 apply information will remain in the PM20100 table if this remittance information has not been displayed on a printed check.   This remittance information can remain in this table indefinitely if no future check is issued to the vendor.

EFT payments and manual check payments will remain in this table indefinitely until they have been printed onto a check in a future check run - or - they have been cleared out with SQL scripting.

These type of payments are stored as a REMITTANCE record (KEYSOURC field) in the PM20100 table and will appear in future Check Runs created from the Select Checks process when ‘Print Previously Applied’ documents is selected for a check run containing such Vendor.

For example, if you pay a lone $25 invoice for a Vendor with a $25 manual payment in GP the PM20100 will maintain this apply record. If you generate a payment batch in Select Checks for the same vendor with ‘Print Previously Applied’ selected (and no new invoices have been entered) it will create a “zero dollar” check to the Vendor. This occurs as it is the first opportunity the system has had to present the information on a physical check. Once this payment is posted the PM20100 will clear.

Q. What are the most common support issues seen in regards to PM20100?

As many users do not want to see a “zero dollar” check printed or past manual/EFT payments appear on a future printed check they clear the PM20100 of the REMITTANCE values prior to the check run. This is done with SQL scripting or a SQL job set to run on a scheduled basis.

This process is described in more detail in the following Knowledgebase articles:

860395 - Information about how manual payments, credit memos, and returns appear on the check stub and when they are removed from the PM20000 table and from the PM20100 table when you run the Select Checks process in Microsoft Dynamics GP

http://support.microsoft.com/kb/860395/EN-US

855957  How to prevent zero dollar remittances from printing in Payables Management in Microsoft Dynamics GP

http://support.microsoft.com/kb/855957/EN-US

Other inquiries we have are on reporting options associated with the table as users want to build reporting that will show a check number/invoice connection.

As the PM20100 table is basically a ‘temporary’ item we do not recommend linking it to any ‘historical’ PM reporting as it is likely not to contain any information after the post. You will want to use PM30300 (PM History Apply) only if creating such a report. Good reports can be built from PM20100 but they would be for open docments only (presenting Check Batch information prior to posting for example).

The following article outlines a common inquiry on reporting options after a post:

856280 - Information about the Check Remittance report in Payables Management in Microsoft Dynamics GP

http://support.microsoft.com/kb/856280/EN-US

Another common issue is when recovering from a PM Posting interruption the Check Links process is performed on the Payables Transaction Logical and History Logical tables to put the associated PM data into their correct table location. Often fully processed payments will not move via Check Links from the PM20000 (PM Open) to the PM30200 (PM History) series if the associated vendor has alternate record(s) in place in the PM20100 series. In this case we would recommend removing the PM20100 record with SQL only if it is a REMITTANCE record, which should allow Check Links to move the history document successfully afterward.

Q. What are the field contents of the PM20100?

The most current build of PM20100 (Dynamics GP 2013 R2) contains the following fields:

KEYSOURC – Key Source: System generated value, if it is a manual or EFT payment the content will be ‘REMITTANCE’.
DOCDATE – Document Date of the payment.
TIME1 – Time: Time the record was written, usually NULL.
VENDORID – Vendor ID associated with the payment.
POSTED – Indicates whether the distribution is for a posted transaction or not.
BCHSOURC – Batch Source: A string value indicating the batch source for the transactions in the batch.
USERID – User ID: often empty or NULL.
APTVCHNM – Apply To Voucher Number: the Voucher Number the payment record is applied to.
APTODCTY – Apply To Document Type: Often set to 0, only used for distributions generated by applying documents. 1 = Invoice, 2 = Finance Charge, 3 = Misc Charge, 4 = Return, 5 = Credit Memo, 6 = Payment.
APTODCDT – Apply To Document Date: Date the payment is applied.
APTODCNM – Apply To Document Number: the Document Number the payment record is applied to.
APPLDAMT – Applied Amount: the amount applied for the line.
DISTKNAM – Discount Taken Amount: amount of discount taken with the payment.
DISAVTKN – Discount Available Taken: the total amount of discounts available that have been taken.
WROFAMNT – Write Off Amount: Write Off amount included with a payment.
CURNCYID – Currency ID: Currency ID the payment was created in.
CURRNIDX – Currency Index: Currency Index the payment was created in.
ORAPPAMT – Originating Applied Amount: amount applied in transaction currency.
ORDISTKN – Originating Discount Taken Amount: Discount Taken in transaction currency.
ORDATKN – Originating Discounts Available Taken: Discount Available in transaction currency.
ORWROFAM – Originating Write Off Amount: Write Off taken in transaction currency.
Apply_To_Document_Amount – Apply To Document Amount.
Apply_To_Orig_Doc_Amount – Apply To Originating Doc Amount.
Apply_To_Discount_Date – Apply To Discount Date.
Apply_To_Due_Date – Apply To Due Date.
Apply_To_Description – Apply To Description.
Apply_To_IS_MC_Trx – Apply To is MC Trx: indicates if apply to document is not in functional currency.
ApplyToGLPostDate – Apply To GL Posting Date: can be referenced in ATB reporting.
APTOEXRATE – Exchange Rate of the Apply to Document.
APTODENRATE – Denomination Exchange Rate of the apply to document.
APTORTCLCMETH – Rate Calculation Method of the apply to document.
APTOMCTRXSTT – Transaction State of the apply to document, usually NULL.
ISMCTRX – Is Multicurrency Transaction: 1=Yes, not present in PM30300.
VCHRNMBR – Voucher Number: the Voucher Number of the associated payment record.
DOCTYPE – Document Type: usually 6 for Payment.
APFRDCNM – Document Number of the Apply From document.
FROMCURR – Currency ID of the Apply From document.
Apply_From_Document_Amou – Document Amount of Apply From document.
Apply_From_Orig_Doc_Amou – Originating Document Amount of Apply From document.
APFRMAPLYAMT – Functional Apply Amount of the Apply From document.
APFRMDISCTAKEN – Functional Discount Taken Amount of the Apply From document.
APFRMDISCAVAIL – Functional Discount Available Taken of the Apply From document,
APFRMWROFAMT – Functional Write Off Amount of the Apply From document,
ActualApplyToAmount – Actual Apply To Amount: originating currency.
ActualDiscTakenAmount – Actual Discount Taken Amount: originating currency.
ActualDiscAvailTaken – Actual Discount Available Taken: originating currency.
ActualWriteOffAmount – Actual Write Off Amount: originating currency.
APFRMEXRATE – Apply From Exchange Rate: Exchange Rate of the apply from document.
APFRMDENRATE – Denomination Exchange Rate of the Apply From document.
APFRMRTCLCMETH – Calculation Method of the Apply From document.
APFRMMCTRXSTT – Muliticurrency Transaction State of the apply from document; usually NULL.
Apply_From_Description – Apply From Description; usually NULL.
Apply_From_IS_MC_Trx – Apply From document is a Multicurrency document.
PPSAMDED – The amount of PPS deducted during the apply of a Return or Credit Memo document.
GSTDSAMT – The amount of GST discount taken during the apply of a Return or Credit Memo document.
TAXDTLID – The tax detail that the tax amount on the distribution should be posted to.
UPDTKNAM – Unposted Discount Taken Amount.
UPGSTDAM – Unposted GST Discount Amount.
UNPPPSAD – Unposted PPS Amount Deducted.
UPWROFAM – Unposted Write Off Amount.
PMDSTMSG – Used for tracking general transaction error messages during edit lists and posting.
MODIFDT – Most current Modified Date.
MDFUSRID – User ID of Last Modified User (referenced in Project).
POSTEDDT – Posted Date: Used for recurring batches, records last date the transaction was posted.
PTDUSRID – User ID: Used for recurring batches, records the last user to post transaction.
TEN99AMNT – 1099 Dollar Amount: used for 1099 statements for 1099 Vendors only.
RLGANLOS – Realized Gain-Loss Amount: records gain/loss from PM apply activity.
APYFRMRNDAMT – Round Amount of Apply From document.
APYTORNDAMT – Round Amount of Apply To document.
APYTORNDDISC – Round Discount of Apply To document.
XCHGRATE – Exchange Rate: rate used to translate amounts from an originating to functional currency (for Multicurrency Transactions only).
DECPLCUR – Number of Decimal Places to be used for a particular currency. Note: this value will be the decimal setting less one (1 = 0, 2 = 1, 3 = 2, 4 = 3, 5 = 4, 6 = 5).
RATECALC – Rate Calculation Method: Denomination Exchange Rate
Payment_To_Print_On_Stub – Payment To Print On Stub.
OAPYFRMRNDAMT – Originating Apply From Round Amount.
OAPYTORNDAMT – Originating Apply To Round Amount.
OAPYTORNDDISC – Originating Apply To Round Discount.
Settled_Gain_CreditCurrT – Settled Gain of Current Credit Transaction.
Settled_Loss_CreditCurrT – Settled Loss of Current Credit Transaction.
Settled_Gain_DebitCurrTr – Settled Gain of Current Debit Transaction.
Settled_Loss_DebitCurrTr – Settled Loss of Current Debit Transaction.
Settled_Gain_DebitDiscAv – Settled Gain of Discount Available Debit Transaction.
Settled_Loss_DebitDiscAv – Settled Loss of Discount Available Debit Transaction.
VADCDTRO – Vendor Address Code – Remit To: when an EFT invoice is entered this field is populated to record the remit-to Address ID information for the invoice.
Credit1099Amount – Credit 1099 Amount: holds credit amount information for 1099 vendors.
DEFTEN99TYPE – 1099 Type: holds 1099 Type information for 1099 report.
DEFTEN99BOXNUMBER – 1099 Box Number: holds box number for 1099 report.

I hope this document helps shed some light on the general use and purpose of the PM20100 table. As the Select Checks process is set to remain intact for upcoming versions of Dynamics GP, any current SQL activities and reporting designed around the content of the PM20100 should be also be valid for future releases.

There are many Electronic Funds Transfer (EFT) formats available in Microsoft Dynamics GP.  These formats were coded to make sure all the required fields in these formats are available, and intended to be used for 'EFT' transfer file purposes.  With that said, we know that many banks offer other services, such as Check Printing services, and we know that many of you are trying to use these EFT file formats to make flat files or xml files to provide to the banks to be used for these other services.  Our support policy is that we will help you with one field or error message per support case, or 30 minutes per custom field.  Not all fields are attainable with the current functionality in Microsoft Dynamics GP and some may require a consulting service to achieve.  The intent of this article is to share with you some of the fields that I have been asked to help with and provide information on whether specific fields can be achieved, provide a work-around, or simply to state if it can't be done with the current functionality in Microsoft Dynamics GP.  Hopefully this will save you some time so you don't have to test for these custom fields.

UNIQUE FILE IDENTIFIER / EFT DOCUMENT ID: 

A unique number per EFT file generated is not a requirement on the standard NACHA EFT format, and therefore, this functionality in not available in Microsoft Dynamics GP at this time. You will need a dexterity customization to achieve this unique number per file. Please consult your Partner, or open an Advisory/Consulting request with Microsoft to request this customization.

The work-around is a manual process to hard-code a constant value such as XX in the EFT file format as a placeholder.  Then the user must store this unique number in a different location outside of Microsoft Dynamics GP such as an Excel spreadsheet.  The user will need to edit the EFT file each time to replace the XX with a valid number, and save it, before sending the file to the bank each time.  (Be sure to hard-code as many X's as you need for the unique number, as the spacing is very important on a fixed format file.  You should not enter more or less digits than what you are overwriting as the bank may require the line to be a certain number of characters across.)

BATCH ID IN BATCH HEADER/BATCH CONTROL LINES:

Microsoft Dynamics GP is designed to put all payments into a single batch in the EFT file, and this is acceptable. (Most banks don't care how many individual batch ID's were included in Microsoft Dynamics GP.) So all the batches pulled into the file will appear as one big batch in the EFT file. Therefore, you will only see one  Batch Header , and one Batch Control line per file. This is by design and is acceptable to the bank. 

SEQUENCE NUMBER:

This field was designed to work in the Addenda  Line type only. If this field does not work in any other line types, you will need to request a customization. 

CHECK NUMBER:
The Check Number and Check Amount was intended to be in the Addenda Line and should be mapped as follows to pull the correct information:

Check Number:
Maps to:  Data Field
Table:  PM Apply To History File
Field:   Apply To Document Number

Check Amount:
Maps to:  Data Field
Table:  PM Apply To History File
Field:   Applied Amount

ANY 'COUNT' or 'SUM' fields in Header Lines:

As a general rule, any 'count' or 'sum' fields will only work in footer lines, or AFTER the lines have been listed. Therefore, most of the 'count' or 'sum' fields only work in the Batch Control and File Control footer lines, and do not work in Header or Detail lines. You will need to test to verify.

NUMBER OF ADDENDA RECORDS ON DETAIL LINE: 
The  Addenda Count will only work in an Addenda line type, and does not work in a Detail, Batch Control or File Control line. The Addenda lines can only be counted after they are consecutively listed, and not before. 

For example, the 'Addenda Count' will not work in a File Control header line, or the Detail payment line because the number of addenda records has not yet been listed. The system is unable to count or total them before they are listed.

As a work-around, there is an option for 'Detail + Addenda' available in the Batch Control and File Control lines that has been accepted by most banks instead. So verify with your bank if they would accept this field instead. Another option is to generate the EFT file using 'one check per invoice' instead of 'one check per vendor'. Since you will have one addenda line per Detail line with this option, you can then hard-code this as '1' in the Detail Line.

LINE COUNT:
The Line Count data field was designed to work in the File Control line and will count all lines of the file. This field does not work in any other line type.

For example, if you have 10 total lines in an EFT file, the Line count in the Batch Control line will list 9 because it can only list the preceding lines. The Line Count in the File Control Line will list the correct count of 10, as this field was designed to work in this line. However, the Line Count field will not work in the additional footer lines (Trailer Label 1 and Trailer Label 2) since these additional footer lines are not part of a standard NACHA format.

----------------------------------------------------------------------------------

ADDITIONAL RESOURCES:

•KB ARTICLES:  The above information is documented in KB 2956922.   For more information on EFT setup, troubleshooting tips, etc, I recommend to read the Commonly Asked Questions section at the end KB 945855.

• SUPPORT POLICY: Please review the support policy in the KB 850201 for Configurator File setup for eBanking modules.  Our support policy is that we will help you with one field or error message per support case, or 30 minutes per custom field/format.

• CONSULTING: If you need assistance to set up an EFT file, or a custom field, please create an Advisory request for a consulting service.  To open an advisory case to request a customization, please contact your Partner first.  An advisory case can be opened with Microsoft, but all customizations will be billed through the Partner. Partners can submit an advisory service online under the Support Benefits and Incidents page in PartnerSource.

• SUGGESTIONS: If there are any fields you would like to see considered for a future enhancement, please enter your suggestions in to the MS Connect product suggestion database.

--------------------------------------------------------------------------------

I hope this information will be helpful to you and save you time from having to test for these fields in the future.  For any additional questions on the above information, please open a support case so a Support Engineer can work with you directly. Thank you in advance.  

Best Regards,

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP Support

A few years ago, I wrote a similar article for Microsoft Dynamics GP 2010 (link at end of email) and I received such great feedback on it that I wanted to write an updated one for Microsoft Dynamics GP 2013.  I hope this information is helpful to all of you that just upgraded to Microsoft Dynamics GP 2013 and will be taking advantage of the e-mail functionality for PM EFT Remittances for the first time, as well as those wondering about Office 365.  Enjoy!

PREREQUISITES:

•Supported versions of Microsoft Office:

          •Microsoft Office 2010 - 64-bit Office must use Exchange only.  32-bit Office can use either Exchange or  MAPI.

          •Microsoft Office 2013 -  64-bit Office must use Exchange only.  32-bit Office can use either Exchange or  MAPI.

          •Office 365 - Both 64-bit or 32-bit must use Exchange.  (For an Online Exchange Server there typically isn't a MAPI client installed.)

•Verify in the Control Panel | Programs and Features that the 'Open XML SDK 2.0 for Microsoft Office'is installed.  (Required)

•The 'Microsoft Dynamics GP Add-in for Microsoft Word'is only needed if you will be modifying the Word Template.  (Optional)

STEPS:

Step 1.  For the sake of testing, it is recommended to first get the email functionality working by using the original canned Check Remittance in your initial testing.  This is important to verify the email functionality is working and to rule out any issues that may be due to an incomplete or damaged modified Word Template.  Use these steps to check the security settings:

     a.  Go to Microsoft Dynamics GP | Tools | Setup | System | Alternate/Modified Forms and Reports. and select the REPORT ID being used.  (Ex. DEFAULTUSER)

     b.  Leave Product as All Products.  For Type, select Reports.  For Series, leave as All or select Purchasing.

     c.  In the Report List, click to expand Purchasing.

     d.  Scroll down to the Check Remittance and make sure Microsoft Dynamics GP is marked.   (If it is not listed, then you do not have a modified check remittance in the system.) Click Save.

Step 2. Activate the E-mail functionality for the Check Remittance at the main setup level by using the following steps:

     a.  Go to Microsoft Dynamics GP | Tools | Setup | Company | E-mail Settings.

     b.  Mark the Document Options and File Formats you want to allow.  (This creates the pick-list you see at the vendor level so you can customize per vendor.)

     c.  Click on the PurchasingSeries link and mark the checkbox for Vendor Remittance. (Keep it simple as possible for testing.  Don't use a Message ID yet.)  Click OK.  Click OK again to close the window.

Step 3.  Complete the setup for each Vendor by using these steps:

    a.  Go to Cards | Purchasing | Vendor.  Select the Vendor ID that you want to send the EFT remittance to.

    b.  Next to the Address ID field, click on the 'World' button to open the Internet Information window.  For testing, enter your own email address in the TO: section for E-Mail Addresses at the top.  (Once it is working, you can edit it later to be the vendor's email address.)  Click Save and close the Internet Information window.

    c.  On the Vendor Maintenance window, click the E-mail button.  In the bottom section, mark the checkbox for Vendor Remittance and choose which Format to use.  (We recommend to test with .docx or .html first just to get it working.)  Click OK and then click Save.

Step 4.  Presumably, there are already posted invoices keyed against the EFT Address ID for this vendor ready to be paid out. During the Payables checkrun process:

 a. Outlook must be open on the same workstation that Dynamics GP 2013 is on.

 b. Build a computer check batch and select EFT as the Payment Method for the new batch.

 c. When you click to print checks, you will get a Process Payables Remittance window instead of a Print Checks window, since it is an EFT and not a check.  Mark the radio box for Remittance Form, and also mark the checkbox for Send Document in E-mail (Print if mail cannot be sent.).  Click Process.

 d.  In the Report Destination window, the Report Type of Template will default if a Word Template is being used.  Complete and post the checkrun.  

 e.  The Send Remittance Exception Report will display and hopefully each says Document sent successfully.  Review the report for any emails that did not sent successfully.

Step 5.  Go to Outlook to verify that you received the test email.  Check the Sent Items folder in Outlook to verify that the emails went out.  (They could still be in the Outbox too, so make sure they are not stuck there due to Outlook settings.)

If these steps don't work for you, open a support incident or refer to the Report Writer manual for more information on using Word Template functionality.  If you have questions on how to modify the Word Template, refer to the Report Writer manual or open a support case.  Please note that the assistance we will provide with Word Template modifications is outlined in Knowledge Base (KB) # 850201.  Anything beyond what is outlined in this KB article may be considered a consulting expense, and beyond what we can do in a regular support case.  Please refer to our policy outlined below:

850201 Guidelines that Microsoft support professionals use to determine when a support case becomes a consulting engagement for Report Writer, SSRS, Word Templates, SmartList Builder, SQL scripts, Business Alerts, VB Script, Modifier/VBA and Configurator Files
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;850201

Step 6.  If the test above worked successfully, then continue to grant security access to the modified Check Remittance and test again.

ADDITIONAL:

•To access the blog article for Microsoft Dynamics GP 2010, click HERE.

•For further assistance or troubleshooting tips for modifying Word templates, please search our blog site or the communities for other helpful articles published.  Here are the links to a few helpful blogs from Andy and Dave, and there are many more out there:

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2010/05/31/modifying-microsoft-dynamics-gp-2010-word-templates.aspx

https://community.dynamics.com/gp/b/dynamicsgp/archive/2012/09/11/how-to-display-more-than-four-line-item-comments-in-the-sop-blank-invoice-word-template.aspx

I hope these quick steps will be useful to you and get you on your way to using the e-mail functionality available to you in Microsoft Dynamics GP.

Thanks,

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP Support -Financials

I wanted to get this out there since we are seeing more and more cases come in on this. When attempting to email templates, users receive the following message:

"You must have the Microsoft Save as PDF or XPS Add-in for 2007 Microsoft Office installed to send documents.”

During troubleshooting, we ran through the list of items that typically cause this error;

-        Text boxes inserted on the template (https://community.dynamics.com/gp/b/dynamicsgp/archive/2012/03/20/word-templates-when-emailing-documents-as-pdf-a-save-as-window-opens-and-email-fails.aspx)

-        Selected all file formats available in Company E-mail Setup (Administration >> Setup >> Company >> E-mail Settings)

-        Checked the dll version of the Word Add-in to make sure they were up to date

-        Made sure the user had admin rights to the %temp% folder

After checking off the above, we were still unable to generate an email.

We found the issue lied within a missing Microsoft Office Interop in the following location:

(C:\Windows\assembly)

Once you path out to this folder, you should find Microsoft.Office.Interop.Word.dll, which allows for code to interact with the applications COM-based model. The client was missing this, so we downloaded the Interop from http://www.microsoft.com/en-us/download/confirmation.aspx?id=3508, and the emails started generating.

Hope this helps!

Kelsey

We get a lot of questions here in support about image assignment on Word templates. There are two ways in which you can place an image on your Word templates. You can use the image assignment that is built into GP, or you can place your image directly on the Word template.

The image assignment through Template Configuration is simple enough, upload your image and it’ll show up on the reports that are associated to that company.

Some customers only have one template and would like to keep it static. These customers, sometimes, put the image right on the template, then upload the template. The only problem with this is some customers have trouble removing that image control OR the image that is on the template is so big that the template will take some time to process.

Below you can find instructions on the image content control for Word Templates in GP. Hopefully this will help some in editing their Word templates

When editing the template, remove the content control from the image control.

This will remove the image control as well.

You can copy and paste your image onto the template and upload the template. Note that to use the image assignment, you will need to have the image control on the template. Also note that if you place your image directly onto the Word template, using the image control, the image will not display because the XML that is processed from Report Writer will overwrite the image and it will appear blank.

While the ability to use Exchange for sending emails from GP is not a new feature, there’s not much information out there about what it takes to get rolling with it. This blog should help to get you started, as well as give you some insight into common Exchange emailing issues we’ve come across in Support.

The first thing to determine is whether you are using Hosted Exchange, or on-premise Exchange. If you currently have an on-premise dedicated Exchange server, then your setup will be a bit easier. If you are using Hosted Exchange, note that Dynamics GP fully supports Hosted Exchange, if it’s hosted through Microsoft Exchange Online (Office 365). Exchange functionality has not been tested with other hosting providers, and is not supported.

https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/msdgpoffice365comp

Exchange emailing from inside GP leverages Exchange Web Services (EWS). If you already leverage EWS for Outlook functionality such as OOF, Folders, Unified Messaging, then you should be all set to go. This EWS URL has to be published through AutoDiscover. The quickest and most painless way to test this is to use Outlook’s built-in connectivity tests.

While holding the left CTRL key, right click the Outlook icon in the notification area of your taskbar. Select “Test Email AutoConfiguration”. Enter your email address and password, and tick just the box for “Use AutoDiscover.” Click the “Test” button. Once the test finishes, look for the “Availability Service URL:” line in the results. The address should be something similar to “https://server.domain.com/EWS/Exchange.asmx”. When you get a URL back, copy and paste that URL into your web browser. You should be prompted for your credentials, and then you should see a page similar to one of the following:

Exchange 2013:

Exchange 2010:

If the page looks familiar, that's because it's nearly identical to the landing page you get when testing Dynamics GP Web Services! Those familiar with WCF services and GP Web Services should feel at home with EWS. If you get some sort of error, or cannot view the page, this likely means that you don't have access to the EWS Virtual Directory, or the Directory is unavailable. 

You can test the Internal and External URL’s for EWS using Exchange PowerShell.

Get-WebServicesVirtualDirectory | FT Name, *URL*

If the URL’s are incorrect or pointing to the wrong server, you can modify them with a PowerShell command similar to the following:

Get-WebServicesVirtualDirectory -Server <servername> | Set-WebServicesVirtualDirectory –InternalUrl https://new.server.com/EWS/Exchange.asmx

Once you’ve confirmed through the Outlook Exchange tests that EWS and AutoDiscover are working, go ahead and enter one of the email setup screens in GP, such as Tools >> Setup >> Purchasing >> Email Setup. Enter your email address and password. You need to log in to Exchange once per each GP session. Closing and re-launching GP releases your connection to the Exchange server and will force you to log in again.

It is entirely possible that your credentials are accepted by the Exchange Server, but you are still unable to send emails. The last used EWS endpoint is cached in SQL in the DYNAMICS..SY04920 table to speed up the processes. If you are able to log in to Exchange, but are getting “Unknown Error”, or “Error Generating Email”, then it is highly likely that the EWS endpoint address being returned by AutoDiscover, and stored in SQL, is incorrect. The URL will likely not point to the EWS endpoint, or perhaps there’s some DNS routing issues with the URL.

The last thing to consider with enabling Exchange emailing for your GP users is that each email function in GP does require some additional configuration. For example, in order to email Sales and Purchasing documents, you must use Message ID’s for different Document Types, and must ensure that each Customer and Vendor has correct email addresses. To send Invoices via Word Templates or PDF’s, the same considerations apply with MAPI emailing in that you may need to have Office or Acrobat installed to send the emails. You should also check with your Email Administrator to ensure that your Exchange server allows attachments of whichever type you choose to email. Ensuring that your Exchange Server is returning an EWS URL through AutoDiscover is the first step to begin leveraging the Exchange emailing functionality in GP. '

Happy emailing!

Dan 

I wanted to give everyone a heads up on some awesome Partners only training coming up November 10-12^th in Fargo, ND! Don't miss this opportunity to sell more, market better, and create innovative solutions and applications.   reIMAGINE provides everyone on your team hands-on learning experience.  You might be asking “Who should attend?”…well EVERYONE!  We will have classes for Sales, Marketing, Consultants, and Developers.

Registration:

http://reimagine2014.com/registration/

Agenda:

http://reimagine2014.com/agenda/

Support is also doing 2 deep dive training classes after the reIMAGINE Conference (Nov 12-13^th).

Below are the topics that will be covered:

Reporting Deep Dive: Getting Data Out and Making it Valuable

Deploying, Managing, and Troubleshooting the Web Client for Microsoft Dynamics GP on Multiple Platforms

Here is the link to get more detailed information on these trainings.

http://reimagine2014.com/post-conference-training/

Here are the Top 10 reasons you should attend reIMAGINE!

10. There will be no snow on the ground (actually I can’t promise that)

  9.   You will need a break before we kick into Year End gear -fair warning of what is to come :-)

  8.   Awesome Post training around Reporting and Web Client.

  7.   Microsoft Dynamics GP 2015 is going to be the best thing since the Bakken Shale formation.

  6.   It will be the party of the century, just like old times.

  5.   Learn all the new technology…technology…technology…ramp up.

  4.  Try the Woodchipper named from the movie FARGO (I hear it is good) http://fargobrewing.com/beers/woodchipper/

  3.  Fall in Fargo, ND is the best (We have all 4 seasons here…but mostly winter though)      

  2.  We will be having a Support Help Desk!!!!

  1.  Doug Burgum is going to be our keynote speaker!

And for all you customers out there that wish you could get in on this....Just wait for Convergence:

Convergence 2015

http://www.microsoft.com/dynamics/convergence/atlanta15/

Hope to see you soon!

Andy

Hello!

I just wanted to write a quick post regarding an issue that has come to light in the last two weeks.  We’ve had a handful of reports from partners and customers who are saying that the process of logging in after upgrading to Microsoft Dynamics GP 2013 R2 is taking longer than it used to, specifically when the login is loading personal settings.

We’ve found that this is due to a series of duplicate Navigation List Views that may be created during the upgrade.  These duplicates occur in the following locations:

1) Under the Purchasing area page:

• Purchasing Requisition Transactions
• Purchase Order Transactions

2) Under the HR & Payroll area page:

• Historical Timecards
• Current Timecards

If you are experiencing a slow login and want to verify if this if you issue you will want to log into Dynamics GP and check each of the above Navigation Lists.  The screenshot below shows what these duplicates appear like under the HR& Payroll area page:

Note that the Views under these Navigation Lists are duplicated twice.  We’ve found that the duplicated are tied to the number of companies in Dynamics GP, so some customers with a large number of companies will see a huge number of duplicates, which causes the performance issue. All of these new items have been added to support the new Workflow functionality within the Dynamics GP client, which is the commonality between these particular Navigation Lists.

This issue has been reported to the Development Team and they’re working on a fix.  In the meantime you can open a support case with the Dynamics GP team, noting Problem Report 80223,  and we’ll be able to review, and as necessary clean up the affected tables for you.

Hello - I wanted to send a quick update on an issue we have recently seen in Support in regards to Project Time and Expense.  When a user clicks Save or Submit on a Timesheet they receive the following message:

An unexpected error has occurred.  Please contact your system Administrator.

During our investigation we found that changes made with a recent security patch from Windows Update is causing the issue.  Below are the KB's we found are causing this issue:

http://support.microsoft.com/kb/2894843

http://support.microsoft.com/kb/2894844

http://support.microsoft.com/kb/2894847

We suspect anything that starts with 289484 is causing our issue.

The temporary workaround is to uninstall these KB’s if they are found on your system. Below are the steps to uninstall the updates:

1.            On the BP Server go Start | Control Panel | Uninstall a program

2.            Click View Installed Updates

3.            Look to see if the KB is listed (i.e. 2894843, 2894844, 2894844, etc)

4.            Highlight the KB and click Uninstall.

5.            Check to see if the issue is resolved.  If not, perform an IIS Reset.  If this still does not work you will need to reboot the BP Server.

To ensure that these do not reload during Windows Update again you can do the following:

1. Launch Windows Update.

2. Click Check for updates.

3. The update should be in the list to select.

4. Right click the problem update and select Hide.

5. Next time you run the Windows Update it shouldn't be available to install.

We have brought this issue to Development's attention and at this time the workaround is to uninstall the patches. I will update this post with more information as it comes available.

Thank you, 

Andy S.

Hi everyone! Have you ever had an issue with an amount showing negative/positive on a report when it should be the opposite? If so, you should double check the account categories descriptions. 

There are 48 default GL Account Categories in GP.  While you can change the account category description for any of these, GP will always recognize the account category by the default Account Number in the GL00102 table for many reports.  This would include Management Reporter, along with Advanced Financial Analysis.  This is very important to remember if you want to change the Account Category description(s) for any reason. 

Reports that pull the account information will use the default category to determine if the account is revenue, expense, or a debit or credit in the balance sheet.  Changing account category 5 (Inventory) descriptions to Sales category for example, would cause a reporting issue.  Since the default for this category is Inventory, it would see it as a typical Debit Balance Sheet Account instead of a typical Credit Profit & Loss account.  

The first 48 categories are static, so remember to use caution if you need to change the description. 

Note that you can always add additional categories in this window if needed.  If you find your reports showing a negative/positive balance when it should be the opposite, this could very well be the cause.

I hope you find this useful,

Adam G.

Have you ever wanted to utilize the Encumbrance Management module but would like to put in more complex controls for individuals to approve the purchase order before applying it against a budget?  Well then this set up is for you!  Below I have outlined things to consider and the basic setup to utilize the Encumbrance Management module with the Purchase Order Enhancements Approvals to have more control over your budgets.

Steps to utilize Encumbrance module and PO Approvals

*This will allow users to have values against budgets in Encumbrance but control the POs thru Approvals. 

 You will first need to determine how you want the Approver to see or handle the Encumbrance piece.  If you navigate to Purchasing >> Setup >> Encumbrance Management, you will have some options when Approvals are on:

When Document is Approved

You can select what actions occur when a purchase order or general entry is approved. These options are available if you have activated Workflow or purchase order approvals in Purchase Order Enhancements.

Ask when over budget - Encumbers any purchase order lines that are under budget. Displays a message for lines that are over budget; the person who is responsible for approving the purchase order has the option to encumber those lines or leave them pre-encumbered.

Always pre-encumber - Pre-encumbers all purchase order lines, regardless of their budget status. With this option, one person does not need to approve purchase orders and manage encumbrances. After a purchase order has been approved, the person who performs the encumbrance tasks must review all pre-encumbered purchase order lines.

Pre-encumber when over budget - Encumbers any purchase order lines that are under budget and pre-encumbers lines that are over budget. With this option, one person does not need to approve purchase orders and manage encumbrances. After a purchase order has been approved, the person who performs the encumbrance tasks must review only those line items that are over budget. Under-budget lines are encumbered automatically.

Once this is set, this is what I recommend for processing:

Step 1: Enter the PO as you would like.

*Note, you should not Approve and Encumber from this step.  

At this point, once you hit save, the PO is not Approved or Encumbered so the line is sitting in a “Pre Budget” state.  You will not be able to print the PO as the PO needs to be approved first.  This is normal:

There are 4 Encumbrance status’ that exist:

1 = Encumbered– counted toward budget totals

2 = Pre Encumbered– has not been counted toward budget but one step forward to Encumbered status (typically means some kind of support action is needed)

3 = Invalid– Data entered is incomplete

4 = Pre Budget– has not been counted toward budget. (Typically means some kind of support action is needed)

*Pre Budget is used for approvals because the user needs to approve the PO to push it down the chain.  This status is considered a stepping stone and nothing more.

Step 2: The PO needs to be approved.  Navigate to Purchasing >> Transactions >> Purchase Order Enhancements Entry. From here, you can approve the PO and how we Encumber will be based on the settings under Purchasing >> Setup >> Encumbrance Management.  For my example, I would like to only see when I am over budget so this is what I see from the window once I approve:

 Once I select Yes to encumber, the report that comes out looks like this:

It even produces a report showing the PO coming out of Pre Budget and into Encumbered (some users like to be aware of this):

 Step 3: Now the PO is Approved and Encumbered so the PO can now be printed from the Purchase Order Entry window with no issues. 

 If you have any questions regarding this process, please contact Support and we would be glad to assist you further if needed.

Have a great day!

Hello,

I wanted to address an error we’ve had some reports of lately.  When eConnect integrations using the taPMDistribution stored procedure are run the following error is encountered:

Error Number = 11991 Stored Procedure= Error Description = Error Codes were not found in table DYNAMICS..taErrorCode. Please insure that the table taErrorCode is up to update.

The cause for this issue is that the upgrade to Microsoft Dynamics GP 2013 R2 added 4 new parameters (@I_vPAYTYPE, @I_vCAMCBKID, @I_vCHAMCBID, @I_vCARDNAME) to the taPMDistribution stored procedure. Unfortunately, that change was not fully reflected in all needed locations:

To be clear, this will only affect those customers on GP 2013 R2. Any build up to, but not include R2 (12.00.1745) is not affected by this issue.

The only real workaround at this point is to use the taPMDistributionPre procedure to populate those columns with valid values so that the errors do not occur. These are the definitions and valid values you would need to populate:

Right now this issue has been targeted to be addressed in the upcoming Dynamics GP 2015 release.

Let us know if you have any questions/comments on this.

Lucas

Hello,

We recently ran into a situation where we were trying to add Document Lines to the WF ASSIGN PO APPROVAL notification in Workflow 2.0. The issue we experienced was that the notification would only show one line in a multi-line Purchase Order. If you are ever looking to bring Document Lines into a Notification in Workflow 2.0, please follow the steps below to ensure it's setup correctly.

1.  First, in the Message Setup window click on Document Lines tab and add the field(s) you want to include from the lines into the Selected Fields section:

2.  Then, switch back to the Body tab.  The fields you’ve selected from the Document Lines can be added by selecting the Document Line Fields field and clicking Insert.

3.  As a result, the e-mail will look like the following:

Thanks,

Ross

The Payroll Employee Summary SmartList is linked with the UPR00901 (Reported Tips Table) on the core Employee Summary SmartList. When you modify/copy this list with SmartList Designer, no data appears due to no information in the tips table.

The GREAT news is you can create a SQL View to fix this!

Click HERE for an example of an Employee Summary View which pulls data from the UPR00900 (Payroll Employee Summary Table).

Always test any changes in a Test Company with a copy of live data prior to implementing any changes in production.

Here is a link to KB 871973 - "How to set up a test company that has a copy of live company data ":
 
http://support.microsoft.com/kb/871973

To use the Employee Summary View attached to this blog to create your own SmartList Designer list, take the following steps:

1.    Run the Payroll_Employee_Summary.sql script against your company database.

      *Be sure to replace ‘enter your company database here’ with your company database:

       USE [ENTER YOUR COMPANY DATABASE HERE]

      Now the view is available to be used in SmartList Designer!

2.    Log into Microsoft Dynamics GP, and click on Microsoft Dynamics GP >> SmartList to open the SmartList Window.

3.    Click the ‘New’ button to open the SmartList Designer Window.

4.    Next to ‘List Name’, enter a name for your new smartlist (I recommend Employee Summary View).

5.    Next to ‘Series’ choose ‘Payroll’.

6.    Under ‘Database View’, scroll down and expand the ‘+’ next to ‘Views’:

 

7.    Expand the ‘+’ next to ‘Company’, and scroll all down to ‘PAYROLL EMPLOYEE SUMMARY’ and expand to show all columns available for this list:

• Select the box next to ‘PAYROLL EMPLOYEE SUMMARY’ to select all available columns included in the view.

• OR, select only those columns you want to include individually.

8.    To preview the list, simply click on the ‘Execute Query’ button at the top of the window.

9.    Click the ‘OK’ button to save your new smartlist.

10.    View the new list in your SmartList Window by expanding the newly created folder under ‘Payroll’, and enjoy!

ENJOY!

IF your ‘core’ Employee Summary Smartlist is not showing expected data due to the link between the UPR00900 and UPR00901:

You can test running the following script against your Test Company database for the year in which data is missing:

INSERT INTO UPR00901 ([EMPLOYID],[YEAR1])

select EMPLOYID, YEAR1 from UPR00900 where EMPLOYID not in (Select EMPLOYID from UPR00901) and YEAR1 = 'XXXX'

IF Non-SA users are unable to view data in a SmartList that was generated via SmartList Designer, please see Sarah Purdy's BLOG:

SmartLists created using SmartList Designer return no results for users who are not ‘sa’ or not in the sysadmin Server Role

Thanks!

Andrea

Hi Everyone,

In Support, we get a lot of questions regarding Manual Checks.

As such, I'd like to provide you with detailed information regarding exactly what you should know about Manual Checks, steps you can take to enter/adjust various amounts, and explanations that detail how each adjustment will effect Payroll.

First, let's cover the basics.

Manual Checks - What You Should Know:

Manual Checks are exactly that: manual. Microsoft Dynamics GP will not make any automatic calculations for you.

Before you enter/post a Manual Check you’ll want to ensure you chose the appropriate ‘Check Type’ in the Payroll Manual Check Adjustment Entry Window (Transactions >> Payroll >> Manual Check).

Here’s what you need to know about each Check Type:

Manual Check – Will update Payroll, Bank Rec, and General Ledger. Use this if you are:

• Recording a manually written paycheck
• Making a negative adjustment
  • Note: Negative Manual Checks cannot be saved to a batch
• Most Commonly Used

Adjustment – Will update Payroll and General Ledger. User this if you are:

• Entering an adjustment.
• Adjustments can be posted only if the gross and net wage amounts are zero.
  • Note: There will be no check number associated with an adjustment.

Beginning Balances – Will NOT update Bank Rec or General Ledger. Use this if you are:

• Entering beginning balances.
  • Note: There will be no check number associated with a beginning balance.
  • Don’t want to update Bank Rec or GL

Now on to the FUN stuff: The Detail!

Click HERE for a DETAILED document that explains how to enter a manual check, and how amounts associated with each 'Transaction Type' will effect Payroll!

NOTE: Simply click on each 'arrow' in the attached document to contract or expand details regarding each transaction type:

I hope you find this helpful!

Enjoy!

Andrea

Hi Everyone,

It’s almost that time of year again! That’s right: time to print and submit the Quarterly 941!

It can definitely be frustrating to find that the amounts you see on the Quarterly 941 Report are not what you expect to see, and we get a lot of questions around this in support.

Before you can begin to troubleshoot incorrect values on this report, it is important to understand what the values mean, how they are calculated, and where they are coming from.

As such, I wanted to provide you with information that describes the following in regard to the Quarterly 941 Report:

• What each line means
• How each line is calculated
• Where you can see amounts associated with each line in Microsoft Dynamics GP
• What tables these amounts are being pulled from

Click HEREfor a DETAILED document that explains each line on the Quarterly 941 Report.

NOTE: Simply click on each 'arrow' in the attached document to contract or expand details regarding each line on the 941:

I hope this information is helpful!

Enjoy!

Stay tuned for my next blog which will address HOW TO TROUBLESHOOT incorrect values on the 941!

Andrea

What will Microsoft Dynamics GP do for the Affordable Care Act (ACA) changes mandatory for the 2015 year?

This is on many of your minds.  Below outlines some of these changes and how we intend to plan for the future. 

Keep in mind, these forms are NOT final as of yet, so we do not want to do a lot of work when items are not finalized.  What we need to get in place now is the tracking mechanisms for the future of the forms which are required next year end 2015.

There are two new forms that IRS released as draft:

1094-C – this is a summary the employer fills out of all the  employees that received the 1095-C.  A 1094-C should accompany any 1095-C ‘s to IRS.  It is a transmittal of Employer Provided Health Insurance Offer and Coverage Information Return
http://www.irs.gov/pub/irs-dft/f1094c--dft.pdf

1095-C – this goes to the employee from the employer (like a W2) Employer Provided Health Insurance Offer and Coverage
http://www.irs.gov/pub/irs-dft/f1095c--dft.pdf

Instructions - http://www.irs.gov/pub/irs-dft/i109495c--dft.pdf 

Forms 1094-C and 1095-C will be used by employers with 50 or more full-time employees or full-time equivalents to determine whether they are liable for penalties under the employer shared responsibility requirements of the ACA.  

When the Microsoft Dynamics GP 2014 year end update releases (target release end of November 2014) Microsoft Dynamics GP will support the ACA changes for versions of Microsoft Dynamics GP 2013 and beyond.  This means that Microsoft Dynamics GP 2010 will not get the ACA changes, but they will still get the regular year end update changes.
Tax and Year end changes for Microsoft Dynamics GP 2010 will end on October 13, 2015.

New Tables for both GP2013 & GP2015

UPR40105-   upr1095Setup
This new table is designed for the purposes of filling out the boxes on the federal government's 1095 form.

We have these tables as master tables that can be updated throughout the year.

UPR00904 - uprMstrDependentACA  
UPR00905 - uprMstrEmployeeACA

UPR10108 - uprYearEndDependentACAHistory
It will be used by the year end close process and populated from the  uprMstrDependentACA table.  This can be edited by the user after year end close takes place.

UPR10109 -  uprYearEndEmployeeACAHistory
It will be used by the year end close process and populated from the uprMstrEmployeeACA table.  This can be edited by the user after year end close takes place         

Existing table changes for both GP2013 & GP2015

BE010130 -     HR - HR_Benefit_MSTR
BE020230    - HR_Benefit_SETP
UPR10100 - UPR_Year_End_WORK_HDR

If you start to look at the form, you will notice it has checkboxes for each month.  This does indicate you need the update installed ASAP in January to start tracking.  This also leaves the Microsoft Dynamics GP 2010 customers in limbo as they may upgrade during the year end still not be able to use this functionality.  Do not fear we have this covered :-)  There will be an edit window off the year-end edit W2 window which will allow you to "edit" this information, just like you do today with the W2 to make sure it is correct before submitting.  This will then allow customers to edit any months that are not marked as covered for their employees.

Here are a few of the windows:

A new field will be added to the Dependent window to choose Covered or Not Covered.
When you install the update, we will mark all your dependents in the system Covered and you can change as necessary.  This is a required field.

These ACA fields will be added to the Benefit Setup in Human Resource to act as a roll down as well as the employee benefit window. 

The look up's of the benefit windows will give you pre-determined list of Affordable Care Act Codes

These last changes are for the year and will not be all built out this year, but we look to make these changes later in the 2015 calendar year, but it will put together the entire ACA changes for you.  When you create the year end wage file for the 2015 year (next year) all the information you have been tracking will be accumulated to the year end tables, just as we do W2 information.  Below you will see two new buttons 1095-C and Dependents.

Below are 2 new windows to allow 1095-C editing capability, will be populated from the year end close process and tracking from the year.

Now that you have viewed the forms, reviewed the instructions and previewed the window changes, you are probably noticing many of the changes are made in Human Resource.  Yes, Human Resource will be required for the ACA changes.  That is OK, Human Resource is free in Microsoft Dynamics GP 2013 and beyond so we need to start using it!

Well all of that was clear as mud!  I hope it will somewhat help tell you our initiative for ACA changes.

If you are a customer on Microsoft Dynamics GP 2010, please reach out to your partner on plans to upgrade.  Partners, if you feel overwhelmed, we are here to help and can assist with upgrade services for you, just email napa@microsoft.com for assistance during this busy time.

If you have any questions, you know where to find me!

Terry Heley - non-ACA-expert, pumped for 2014 payroll year-end!!