Suggest a new Idea

    • 2

      POP Prepayments - Partially Apply Invoices to Outstanding Prepay Balance

      Suggested by Kyle MaloneNew 0
      Category: Distribution - Purchase Order Processing

      As it stands currently, you can issue a prepayment against a PO.

      However, when invoices are processed against that PO, they are automatically 100% applied towards the outstanding prepayment balance available.

      In many business scenarios, there should at least be the flexibility to adjustment how much of the invoice goes towards the prepayment and how much of the invoice is still to be left as payable to the vendor.

      Please provide the ability to adjust the purchase order prepayment balance applied to vendor invoices.
    • 1

      Have option to roll down PO Date changes to PO line items

      Suggested by Kerry HataleyNew 0
      Category: Distribution - Purchase Order Processing

      When a date change has occurred in the Purchase Order header, there should be an option to allow this new date to be pushed to the line items on the purchase order. Used by Requisition Date, Required Date, Promised Date and Promised Ship Date)
    • 0

      Employee Address Field Limited to 22 Characters

      Suggested by Monica TerrellNew 0
      Category: Human Resources/Payroll - Payroll

      Please limit the employee address lines to 22 characters since the SSA restricts the length for W-2's.
    • 0

      Fixed Assets Bug - Unbalanced G/L Entry & Subledger

      Suggested by Kyle MaloneNew 0
      Category: Financials - Fixed Assets

      Logged this w/ Microsoft support desk (SR # 118120319409654) but was directed here.

      There's a bug in the asset retirement window that allows a user to enter 2 lineitems of detail (say 1 line for Proceeds & 1 line for Expenses of Sale) by manually clicking into an amount field on the 2nd line.

      When retiring with this type of incorrect split, the user will receive a 'Return Code 17' error but more significantly, there will be an UNBALANCED set of G/L distributions created (which can be posted to G/L) AND creates an UNBALANCE FA00902 table which is relied on heavily for all subledger reporting.

      Outside of training, there's nothing to do from stopping users from incorrectly processing this way and the impact is significant...