Skip to main content
Sparkrock

Altus Dynamics NAV

This release includes the following enhancements, functional changes, and hot fixes each listed with reference to the Task ID:

General

Menu and Page Optimizations (2820)
  • Vendor Card Optimization
    • Added "Invoice Type" to the Vendor Card.  This functionality was available in 2009 but this field was missing in earlier versions on 2013
    • Modified the “No. of Changes” on the Vendor to include tracking of changes to related tables such as Vendor Bank Account and Order Addresses. 
  • Optimized Changed Log Entries page
  • Optimized the Cheque Ledger Entries page 
  • Optimized Posted Deposits Page
  • Optimized Vendor Card
  • Optimized Vendor Bank Account
  • Optimized Budget Commitments page
  • Accounting Manager (Accounting Supervisor) Role Center
    • Optimized Cash Management Area
    • Added Charitable Tax Receipt Report to the Menu
  • Accounts Receivable Admin Role Center
    • Added Cash Receipt functionality
  • Payroll Role Center
    • Added a view to Cheque Ledger Entries
  • Clarified the Departments Menu captions for Dimensions area
Purchase Request List, Fact box improvements (3209)

Corrected issue with links in the FactBox so that links work correctly to Payment and Expense Request as well as Purchase Requests. 

General Ledger

Altus Dim. Combos only Allow Posting Type G/L Accounts (3373)

Modified the Dimension Combination setup so that only G/L Accounts with a Type of “Posting” can be selected.   This will prevent non-posting accounts from being used inadvertently. 

Integration of Microsoft corrections to NAV Reports (3272)

Integrated Microsoft updates to reports that corrects various issues.  Reports included are:

  • 10022 - Trial Balance
  • 10023 – Trial Balance, per Global Dim.
  • 10025 – Trial Balance, Spread G. Dim.
  • 10026 - Trial Balance, Spread Periods

Accounts Payable

Annual Filter A/P Batches (2958)

The Posted A/P Batch list has been enhanced to allow the user to Filter by year.  Use the “A/P Batches Processing” Page available from /Departments/Financial Management/Payables and “A/P Batches” under “Tasks” to see a list of Batches.   Select the “View/Status” of “Posted” and the “Posting Year” list will be populated with Years that can be filtered on. 

EFT and Email Remittances – Additional Validation (3266)

The Vendor Bank Account and EFT Export process has been modified to included additional validation to reduce possible errors in the EFT process created by incorrect setup.  

Vendor Bank Account Changes

The Vendor Bank Account has been modified so that if the user places a checkmark in the "Use for Electronic Payments" the "Email Remittance Advice" is automatically checked (but can be removed later).  

EFT Export Process

The EFT “Export” process has been modified to include the following validation before the files have been created:

  • “Exported” is only updated once all records pass the entries validation process.
  • Entries are checked to ensure a Vendor Bank Account exists for all entries with a Bank Payment Type of “Electronic Payments”. 
  • All Electronic Payment as validated for:
    • At least one record set up with “Electronic Payments” checked.
    • That entry has the following fields completed
      • Bank Institution No. is filled in
      • Bank Account No. is filled in
      • Transit No. is filled in
      • If Email Remittance Advice = Yes, then validate that an email address has been specified. 

Payment Journal Posting Validation

Added a final check and WARNING to the posting process.   If there are lines in the Journal that have been set up for Email Remittances, but the Email Send field = No, the user will be warned and will have the opportunity to stop the posting process. 

Transmit

Added functionality to move the file at the time of Transmitting.    

A/P Remittance Advice Improvements (3077)

Made improvements to the layout of the EFT Remittance Advice report (23020108). 

Close PO Function and Blank (Comment) Line Types (3268)

Corrected issue with the Close PO function when “Blank” line types were included.  

Dimension Value Deletion Issues (2891)

Corrected issues with delete of Dimension Values.   The delete process has been expanded to prevent deletion when the Value is in use on a Purchase/Payment/Expense Request Line.   I has also been expanded to evaluate if the value is used on a Project or Grievance and will prevent deletion if it has. 

Accounts Payable Coordinator Role Center Improvements (3337)

Changed Role Center ID 23020150 and added a Stack section for “Payment/Expense Requests" with the following stacks:

  • Open
  • Awaiting Approval
  • Approved
  • Completed

Purchasing

Auto PO Creation Scheduled Process (3164)

Created functionality that supports the auto creation of Purchase Orders from approved Purchase Requests.   This functionality can be scheduled and will automatically create Purchase Orders and Email them to the vendor specified on the header of the Purchase Request. 

Purchase Order/Invoice - Insert Allocations Issues (3269)

Corrected issues with Insert Allocation feature.  

Request Inbox: Re-open and E-mail (827)

Optimized the text of the email generated for this process.

Undo Receipts with G/L Accounts (3159)

Extended the Undo Receipt functionality to support entries with an Account Type of G/L Account. 

Purchase History - Optimization (3203)

Corrected inconsistencies with what document were presented in the Purchase History lookup. 

Purchase Line Dimension Combination Code w/o G/L issues (3270)

Corrected issues when Dimension Combination Codes that did not include the G/L Account were used. 

Purchase Invoice - PO Information Fact Box (3271)

Corrected/enhanced drill downs and lookups from the FactBox.

2013 Get Receipts - AEP Receipt Comment (3008)

Added warning to the user when the Get Receipts process is used for lines generated by AEP receipts that have comment lines.   This was created to ensure that users are aware of comments for the receipts if the exist. 

Human Resources

HR/Payroll: Progression date is not populating in HR requests in NAV (2905)

Corrected an issue where the date was not being populated consistently.

Employee Location Code (2902)

HR Representatives have been linked to Location Codes. When an employee is hired, the portal displays their HR representative for the respective Location.

HR Request Reassignment (3043)

Added functionality to support using HR Request Reassignments. 

HR Employee - Time Attendance Fast tab (2957)

Optimized the Employee Card by Removing the Time and Attendance Fast Tab and moving it to its own page.  This change makes the layout of the employee card more practical and supports more flexibility with permissions. 

HR Request Reassignment (2916)

Created functionality that allows a user to define the fields that are populated as defaults when using an HR Request for a Position Change (Reassignment).   This allows user setting such as step and grade or progression details to be copied to the new assignment. 

HR Request List - Ability to Filter on Employee Name (3324)

Enhanced the HR Request list to display the Employee Name and support searching and filtering on this field. 

Payroll

Cancelling AEP Paystubs when Paycheque is Financially Voided (3242)

Enhanced the voiding process (Unapply and Void Check option only) to ensure that entries created in the Employee Pay Stub Header and Line tables, which are used by the employee portal to display pay stubs, are deleted also and therefore no-longer displayed on the portal as the payment has been completely reversed.

Employee Pay Stub Header before above-noted Financial Void:

After above-noted Financial Void is processed:

Check Ledger Entry:

Employee Pay Stub Header:

Note: All Employee Pay Stub Detail records are deleted as well when the corresponding header is deleted.

Payroll Cheque - Obfuscate Bank Account No.  (3325)

Modified the Payroll Cheque and the Payroll Cheque Re-Print so that in the Distribution section the last 4 digits of the Bank Account number are displayed to the end user. 

My Paystub - Change when a Paystub is displayed based on setting (3240)

Modified the Altus HR Setup to add a new option field whereby the user can select when the employees’ paystub will be made visible on the portal.  The options are a) When the EFT is created or b) on the actual Pay Date.

Payroll Journal Pre-Load - Needs to allow entries already entered (3327)

Enhanced the Payroll Journal preload functionality such that it will now load the appropriate entries into the journal even when there are pre-existing entries that were manually inserted.  The Preload functionality is now skipped only if there are records in the journal for which the preload has already been run.  This prevents the user from running it multiple times and potentially multiplying the employee’s earnings.  The identification of records that were added to the payroll journal through the preload function is based on a new field added to the table titled “Preloaded”.  This new field is not visible on the page, but can be seen in the table fields.

HR Request Issue that prevents execution of specific process functions when run individually (1606)

Enhanced the processing of HR Requests such that individual HR Functions can be run in sequence even if the HR Request page was closed part way through the process.  This resolves the issue where key data is lost and is no longer available for use later in the processes that follow if the HR Request page was closed before all steps have been successfully completed.  NOTE:  It is still strongly recommended that users process “ALL” steps at the same time and if errors occur, the user should correct the problem that instigated the error and again run the Process All Steps routine again to complete the remaining procedures relative to that HR Request.  Here is an example of where the link to process individual lines is found:

2013: Retro Pay Calculation (2959)

This functionality allows the user to calculate the employees’ retroactive pay amount in situations where there is a pay structure change (perhaps based on a contract that was settled well past its original expiry date) that has a date that is retroactive to the current pay cycle.  Under normal circumstances, the employee would just be progressing through the various pay structure steps/grades as per our progression functionality (or manual if that is what the client prefers), but this functionality covers the case where the entire pay structure itself is completely updated, but is effective for a period covered by payrolls already processed.  Its’ intent is to re-calculate the earnings of that person as they would have been if the new, retroactive pay structure had been in place at its effective date (in the past), deduct what has already been paid to the employee during that time, and create entries for the difference to be paid as retroactive pay.  This functionality was previously released in 3.9SP1 has now been included in NAV 2013.

Employee tax exemption defaults when blank (3323)

A new HR Request HR Function was added to create the ability to automatically apply current and future Basic TD1 Exemptions to newly hired employees during the processing of their HR Request.  A new Table called “Default Tax Authority was created for system administrators to enter the exemptions as they are approved by the Federal/Provincial governments which will then be applied to employees hired from that point forward.  Note: HR Reason codes that are configured to add HR Positions to employees should not include the new HR Function as those records will already exist and could be manually modified to include additional exemptions.

Where to find it:

Enter the default basic exemptions by reporting authority and by effective date:

Ensure that the appropriate HR Reason Codes of Process type = “Hire” have the following HR Function added:

Payroll Allocations (3189)

A completely new functionality was created to allow users to allocate by dimension the calculated results of their payroll controls either according to one or more allocation splits associated with the employee’s individual HR Position ledger entry(ies), or based on the allocation split that is recorded on the Payroll Control Code.  Note that where any allocation entries have been entered against a payroll control, they will always take precedent against any other allocation in the system.  This additional functionality in no way affects the existing Altus Allocation method which is based on the employee allocation table entries that are loaded into the journal immediately following the preload.  The new functionality allows the user to complete their payroll processing as they normally would while viewing the summarized version of the calculation results and then when either the Cheques are printed, or the Remittance Advices are printed, and the EFT File sent to the bank, approved and transmitted, they can create an allocated “Posting” batch from that data which is posted normally as per NAV Payroll’s standard process.

Payroll Journal - Default and Filter fast tabs (3074)

Further enhanced the payroll journal page by removing fast tabs and adding a worksheet style view, and in addition added two buttons to the ribbon allowing the user to toggle on/off the Default fields (e.g. Employer, Pay Cycle and Calculation Order) as well as the filter fields (e.g. Employee, Pay control, bank payment type, Pay Cycle Code etc.).

Create Schedule and Payroll Controls (3346)

Enhanced the schedule generation process such that if the payroll control code associated with the Schedule Template has been entered by the user and is not blank, then this payroll control will be used in the actual schedule.  Only if this field does not have a value will the payroll control be then taken from the HR Position record instead.

Employee Scheduling

Upgrade Scheduling module to NAV2013 (3130)

Upgraded the Location Functionality to NAV 2013.   Added some new features and reports. 

My Schedule - Hide entries in "Open" Status     (3360)

Modified the “My Schedule” and “Location Schedule” pages to support only displaying the pay stubs on or after the support date. 

  • Was this article helpful?