Public Profile
  • When you void a payroll check the Employee Yearly Accrual window in HR attendance is not updated properly with hours worked accruals

    When you void a check for an hours-used transaction, the Employee Yearly Accruals HR window is incorrectly updated. When the check is voided, the hours are added back to the employee’s hours available balance as they should be, but the hours are also incorrectly added to the Employee Yearly Accruals window again in error. So now the amount tracked against the maximum yearly accrual hours is incorrect and overstating the accrual for the year. Also when you do an HR adjustment or beginning balance those are ADDED to the yearly accrual window and typically you do not want them to be, example you first go live with HR. It would be nice to have an option to not add to this window/maximum. Workaround is to manually go edit the window for the maximum.

  • Receivables transaction entry VCR buttons do not function when you have 2 batches and the document number in the batches are not is sequence

    When you have 2 batches and the document number in the batches are not is sequence. You open TESTB batch in the RM Batch Entry screen and then clicked on Transactions button, It opened the RM Transaction Entry window and then you change the lower left option from by Document to by Batch ID and then click on the left Arrow. At this time, when you use the VCR button the trx does not pull up, if you change it back to by document and use the VCR button it works fine.

  • Voiding a debit memo in Receivables Management does not update the chequebook in Bank Management.

    Voiding RM Debit Memos created as Cashbook AR Payments not update Cashbook Management in Dynamics GP The 'AR' Credit Memos can be voided in RM and update the Cashbook side without issue but Debit Memos won't.

  • Bank Management ERM Import Payment window locking source file

    When you use the ERM Import Payment window to import a payment from a csv file, the source csv file being imported is then locked and cannot be renamed, or saved over, until the user exists GP. Once the user exits GP the file again becomes available for rename or saving over. It would be nice to be able to rename the file while you are still in GP
  • You may receive an error message Return code 17 when you retire an asset at 100% and bypass the user warning you cannot create a 2nd line

    In the fixed asset retirement window, if you enter proceeds w/ 100% of asset on the first line and then tab-through to the second line, there is a prompt that denotes you cannot create a second line when there is no % and/or qty associated w/ that line. If you BYPASS the warning to the user and manually click in the 'Expenses of Sale' field on the 2nd line, you won't receive the error message, you'll receive the 'Return Code 17' error message after clicking 'Retire', AND you'll receive a G/L batch that does NOT balance.
  • Ability to allow EI Rebate to go into box 40 as it is a taxable benefit in Canadian Payroll

    In municipal government for some of our customers, there is a need to allow EI Rebates to update box 40 as a taxable benefit. However, when you select EI Rebate as the Pay Type, you are unable to key in an additional box. Here is guidelines around this https://www.canada.ca/en/revenue-agency/services/tax/businesses/topics/payroll/benefits-allowances/employment-insurance-premium-rebate-5-12-benefit-returned-employee.html

  • Ability for Days and Weeks Worked to post from Project to Payroll batches

    Today when you key in a project of example 20.00 hours and you post it to payroll the Days and Weeks worked do not calculate correctly as it is not stored on the payroll batch for it to know how to calculate. If we stored the default in the payroll batch header, then the trx would come over to payroll correctly just as if you keyed the trx. This is important to be correct for payroll state reporting of days and weeks worked.
  • Changes to EE Employee Expense Document Number fields no long allow joins in Report Writer for Billing Invoices PA Billing ITEM TEMP

    Due to changes made on the Employee Expense tables in recent years with PTE, the document number field is now 31 characters instead of 17 in dexterity, which is fine in the application, but with this change users can no longer join the PA30501 table to the PA Billing ITEM TEMP table in Project Accounting. In previous versions users could pull the description of their employee expense history lines onto their billing invoices for visibility. Now if you attempt to do this, you cannot join the PA Cost Document No. on the PA Billing ITEM TEMP to the PA Empl Expense Document No. field, even though they hold the exact same values in SQL. I also tried to create this table relationship directly in DEX, and I could not. Something changed that will no longer let us join the PA Cost Document Number in the PA Billing ITEM TEMP table to the Employee Expense History table. From what I can tell when PTE came out, the number of characters in the PA Employee Expense Detail History for the PA Empl Expense Document Number was updated to 31 characters (used to be 17 in previous versions) since it was updated there but not in the billing tables, Dex will no longer let us join.
  • Ability to choose what to roll down from Class ID in HRP

    When you assign a class ID to employee there are times we do not want all items rolled down from the class. It would be nice to have the ability to choose what you want to roll down to the employee. Similar to what we do when you re-activate an employee. Give the user the option more than the auto roll down and data getting lost, such as department and position.
  • Add fields to applicant process in HRP

    It would be nice to have the location field added to the requisition window during hire, it is on the applicant, but not requisition. Also add the supervisor field to the applicant window, which is on the req window now, need to add to applicant.