AviontéCLASSIC Back Office Release Notes - OCTOBER 2023

Updated November 03, 2023 18:33

🚀 What's New

Release Date: 10/26/2023

1. Avionte Classic has removed the decommissioned Vertex Geocodes from the existing customer base.

Why? Our third party decommissions geocodes that are no longer valid. To assist the existing customer base, the decommissioned geocodes have been cleared from the addresses so that the users are notified when they try to process with the addresses that had the invalid geocodes with the accurate geocode for the particular address.
How does this impact you? When processing a transaction, a notification will occur by the Data Requirement Message [DRM] of a missing geocodes for an Order or Employee, allowing the user the opportunity to update the employee or order with the accurate geocode for that address.

2. Avionte Classic's Customer > Address > Sales Tax field can now be configured with multiple Sales Taxes to accommodate those circumstances where multiple Sales Taxes are calculated on an invoice.

Why? Prior to this improvement, only a singular Sales Tax could be configured requiring additional configuration to calculate the combined amounts.
How does it impact you? Under Customer > Address > Sales Tax, the customer will now be able to Choose one or many of the Sales Taxes for that customer, that are made available through the Admin Tool > Sales Tax configuration.
Screenshot:
KB Article: Customer Address – Avionte Classic (zendesk.com)

Release Date: 10/12/2023

1. Avionte Classic's Employee > Payroll > Accrual screen has been updated to display the Supplier in which the accrual has been configured for.

Why? It was not clear which supplier the employee's accrual is configured against.
How does this impact you? Prior to this improvement, an employee could be under multiple suppliers. It was not clear which supplier the employee's accrual is configured for.
KB Article: Employee Payroll - Accrual – Avionte Classic (zendesk.com)
Screenshot:

2. Avionte Classic's Standard GL has been updated with the addition of GroupNames for Employer Contributions and Accrual Payouts.

Why? Prior to this enhancement, a request to the Technical Services team was needed to accomplish this task.
How does this impact you?
- Under Weekly Process > GL > Journal Entry, a new GroupName of EmployerContribution can be seen with respective balances.
- For CA suppliers with accrual plans with the Pay Type equal to Accrue For Later Payout, under Weekly Process > GL > Journal Entry, a new GroupName of AccrueForLaterPayout can be seen with respective balances.
Screenshot:

3. Avionte Classic's Standard GL has been updated with column options to aid in the balancing of biweekly transactions.

Why? Prior to this enhancement, a request to the Technical Services team was needed to accomplish this task.
How does this impact you? Under Weekly Process > GL > GL Account Option, four new columns have been made available:
- Unbilled Transactions (Revenue, SalesAndAR) - items that had not been billed in that period based on biweekly pay.
- Current Unpaid Transactions (Expense, Payroll) - items that had not been paid at that time.
- Previously Unpaid Transactions (Expense, Payroll) - items that were paid in this period as a part of biweekly pay.
- Previously Unbilled Transactions (Asset, SalesAndAR) - items that were billed in this period based on biweekly billing cycles.

4. Avionte Classic's Standard GL has been updated with a new Select Group Option of Discount Name.

Why? Prior to this improvement, a request to the Technical Services team was needed to accomplish this task.
How does this impact you? Under Weekly Process > GL > GL Account Option > GL Category of Revenue > Select Column of Discount, a new option for DiscountName is now available. When made active, the Journal Entry Description column will now include the Discount Name.
Screenshot:

5. Avionte Classic's Standard GL has been updated with the ability to see the Sales Tax broken down by Sales Tax Name.

Why? Prior to this enhancement, a request to the Technical Services team was needed to accomplish this task.
How does this impact you? Under Weekly Process > GL > GL Account Option > GL Category of Revenue > Select Column of Sales Tax, a new option for SalesTaxName is now available. When made active, the Journal Entry Description column will now include the Sales Tax Name.
Screenshot:

6. Avionte Classic's Employer New York Local Metropolitan commuter transportation mobility tax [NY Local MCTMT] legislation has been updated effective July 1, 2023, to require employers to file the New York Local Counties by Zone starting in Quarter 3 of 2023. To accommodate this new requirement, the NY Local MCTMT ER Tax Name will now be reflected by the County.

Why? Prior to this improvement all applicable counties were reflected under a singular tax name of NY Local MCTMT ER.
How does this impact you?
- The NY Local MCTMT ER Tax Name will now reflect the county based on the worksite geocode. The following are the Tax Names that will occur:
  - BRONX MCTMT ER
  - RICHMOND MCTMT ER
  - QUEENS MCTMT ER
  - NEW YORK MCTMT ER
  - KINGS MCTMT ER
  - ROCKLAND MCTMT ER
  - WESTCHESTER MCTMT ER
  - SUFFOLK MCTMT ER
  - PUTNAM MCTMT ER
  - ORANGE MCTMT ER
  - NASSAU MCTMT ER
  - DUTCHESS MCTMT ER
Screenshot:

7. Avionte Classic's Invoice Correction has been updated to not allow the ability to do an invoice correction in error on an unposted invoice.

Why? Prior to this improvement, if an invoice had not been posted, the Invoice Number had not been permanently set, and the invoice can still be reprocessed, which would result in a different invoice number and/or amount. Users should not be able to act on an invoice from an unposted billing batch.
How does this impact you? The user will be notified that the action Invoice Correction cannot be made on an unposted invoice.
KB Article: Invoice Corrections – Avionte Classic (zendesk.com)
Screenshot:

8. Avionte Classic's Emailing Invoices has been updated to not allow the ability to email an unposted invoice.

Why? Prior to this improvement, if an invoice had not been posted, the Invoice Number had not been permanently set, and the invoice can still be reprocessed, which would result in a different invoice number and/or amount. It could cause confusion when payments are being made if the wrong copy of the invoice is used, it is hard to match up what they have, and what the final result for the invoice number was after posting. Users should not be able to act on an invoice from an unposted billing batch.
How does this impact you?
- The user would need to update Admin Tool > Config Option > System > System Setting > AllowEmailingUnpostedInvoices to be equal to False. [System currently defaults to True]

- The user will be notified that the action [Email Invoice] cannot be made on an unposted invoices for:
  - Invoice > Summary > Email Invoice
  - Billing > Home > Actions > Email Invoice
Screenshot: