web
You’re offline. This is a read only version of the page.
close
  • Change project stage provide additional rules/polices

    At present, a project stage can be changed to finished or equivalent when there could be outstanding timesheet, requisitions etc. This means that transactions will not be able to be posted. The project stage rules or a policy framework should be added whereby rules such as a project cannot be closed when their are outstanding transactions to be approved/posted should be able to be configured. This reduces the amount of manual work a project manager would have to do to close a project. Some of this type of functionality is available for the elimination of fixed price project only (configurable for the elimination only). This should be extend to all types of projects including time and materials etc.

  • Vendor rebates based upon the sale of the item

    Current all Vendor rebate functionality is based upon the rebate accruing when the items is received or invoiced. Some vendor require the item to be sold either via the sales order or via the POS. This is known as "sold through" or scan. The complication can be if we sell the item to a Retailer, the rebates maybe recognized only when our customer sells the item. To me, to handled every scenario, the following would need to be handled: - Rebate accrued on sale through sales order or POS i.e. number of units or value sold for the given period - Rebate accrued on POS information provided by a customer i.e. this would be sales data manually entered. Ultimately, this data imported would be imported however, this could be achieved with standard DMF functionality.

  • Annual Limits for expense categories

    For many organisations there are limits to be amount of expenses which can be claimed in a year. For example, for gym membership, Microsoft has a limit of $300 per year. It would be good if these limits could be enforced by polices
  • Reuquisition requiring RFQ process

    The ability to accommodate workflow, mandatory fields and templates based on the thresholds listed below (inclusive of GST): 1.       Procurement Requisition: Requests from A$0 to $25K, three quotes not mandated - optional RFQ 2.       Request for Quotation: A$25K - $100K requires short RFQ document, A$100K-$400K requires long RFQ document, three quotes mandated 3.       Request for Tender: A$400K+, open to any number of quotes
  • Prospect Vendor for RFQ

    At present the RFQ process requires participants in the process to be Vendors. If the RFQ process is a market testing process, typically prospect vendors will be invited to quote. This idea is to extend RFQ process to prospect vendors.
  • Support Procurement Category within WBS

    At present, when creating a WBS with a line type of "item", only inventory items are available to be selected. This should be extended to procurement categories. For a lot of organisations, they raise purchase orders against a project including for subcontracting, and generally procurement categories are used. Once procurement categories where introduced, service items are not used as often unless there is a particular rate for the service
  • Employee reimbursed in currency of their location

    When reimbursing employees which are in locations with currencies other than the home currency, the reimbursement payment generated in Accounts Payable, default to the home currency. For example, the legal entity has a home currency of USD but has a office in Canada where employee would like to be reimbursed in CAD. The existing functionality allow a default currency on the vendor. What should occur is for employee vendors, is the currency of the vendor is used to generate the reimbursement payment,
  • Fixed Asset reports cannot be run as at a date or date range

    Fixed Assets reports are generally very good such as: Fixed Asset acquisitions Fixed Asset disposals Fixed Asset transactions Fixed Asset balances These reports typically cover all of the management and other requirements. The issue is none of the report can be ranged by date which is different from other sub modules such as Project etc. This means its difficult to complete processes such as month end and year end. In effect, all of the these reports must be run and saved for each month and year end because they are not date aware. This has an issue for every client implementing Fixed Assets. Most clients implementing Finance and Operations, implement Fixed assets and generates a lot of dissatisfaction. Add a date range or as at date for all of these reports.
  • Expense Management Report Posted Transaction report does not any date field

    The Expense Management Report Posted Transaction report does not have any date field for the individual transaction i.e. not the transaction or accounting date. Frankly, this makes the report useless, Accountants at a minimum want to know the period the transaction related too. The report should have both the transaction date (the date of the expense) and the accounting date (if the transaction date is corrected).
  • Expense Management Travel Requisition functionality is limited when reviewing and approving expense reports

    The current travel requisition/expense report works in the following way: There is a Expense Management parameter requires travel to be pre-authorized before claiming the expense. The flag is "Pre-authorization of travel is required". With this switched on, Expense reports must have a travel requisition mapped to each line before submitting for approval. When this setting is on, the system behavior is as follows: Raise travel requisition - Flights, $1000. Approved travel requisition Raise expense report. map to approved travel requisition. Create line with Flights, $800. Map line to travel requisition Submit Expense report Firstly, there is a bug in the functionality at present which means the pre-authorization can be switched off. I have logged this. Secondly, the way in which the functionality works means the following: All travel must be pre-authorized or none at all If the "pre-authorization required" flag this is not switched on, then the Expense report lines must be separately approved even through a travel requisition has been mapped to the expense line. There is nothing in the Expense report workflows to detect whether a travel requisition was mapped to an expense line. This is the biggest gap in functionality. This should work in a similar way to the invoice matching to purchase order workflow i.e. detect if there is a match and allow automatic approval. The functionality should be expanded. Some ideas are: Require pre-authorization on some categories but not others. Most organisation require pre-authorization of flights, accommodation and entertainment but not other minor categories such as taxis, etc. Provide attributes in the Expense report workflow which detect whether a travel requisition has been mapped to an expense line. This would allow automatic approval for lines with a travel requisition. To me, this is a simple change which covers almost all scenarios.