Public Profile
  • Outbound load reconciliation process

    It is typical for distribution companies to reconcile an outbound load when a truck returns to the distribution centre (DC).  Typical requirements for this reconciliation process include:

    1. Ability to create / post invoices from the Load planning workbench 

    2. Link all sales invoices to a load such that on return to the DC users can register the invoices brought back.  This helps users to monitor / audit / control that all the invoices on truck (load) have been addressed / returned from the delivery run

    3. Ability to post a credit note for an entire invoice to reflect an uncompleted delivery - example shop closed when truck arrived to deliver at shop

    4. Ability to record the total payments received for a specific load (this means that a driver deposits an amount of money with the clerk - this money reflects the money collected during the delivery), issue receipts to driver for the money collected

    5. Ability to record total undelivered quantities - customers may not accept items on invoices.  To record these items /  quantities in a load reconciliation process

    6. Reconcile each invoice on truck : allocate payments (from deposit amount to customer), undelivered quantities, credit notes used to pay invoice, etc

    7. Display variances to reconciliation clerk - help to identify the variances by invoice

    8. Automatically generate credit notes, payments and settle the same to the invoice being reconciled

    etc

  • Load planning workbench - generate sales invoices for outbound loads

    It should be possible to issue / generate the sales invoices for all the sales orders added to an outbound load.

    System currently allows to generate the delivery notes but it should be possible to generate the sales invoices too - Distribution companies usually issue invoices immediately such that these are given to truck drivers for collection of payments upon delivery.  At the moment users must navigate to different forms to issue these invoices as well as it is difficult to issue / generate / post sales invoices by Load number.  When multiple trucks are leaving a Distribution Centre the truck drivers need to be given their invoices in a quick and easy fashion

  • Centralised Logistics

    We are having demands about solutions that allow users working with a multiple company setup in D365FO to have functionality that allows users to centrally manage the distribution of products (primarily delivery to customers) through a distinct / different Logistics company. 

    The idea is that users create sales orders in different retail companies then are able to aggregate / load these sales order lines(items) from different companies onto 1 truck (load) using the load planning workbench in the Logistics company.  The need to have multiple retail companies include taxation, legislation, brand requirements, company strategies, etc.

    The reasons for this request are various and range from cost cutting exercises (personnel, warehouse facilities, etc.), maximise and optimise the use of trucks, personnel and warehousing capabilities, etc

  • Compute sales commission when an invoice is settled not only when posted

    Apart from computing sales commission on posting of a sales invoice, can we have an option to compute commission based on settled (paid / matched) sales invoices?  We are receiving this request quite often from customers and the idea is to pay a commission to the salesrep when the customer pays for the sale invoice.  There are good reasons for this method of commission computation including reducing fraud, addressing sales bloating to meet end-of-month commission targets, etc

    System should compute commission on part-settlement as well as reverse commission if invoice is unsettled / unmatched.  A method to accrue for commissions to be paid is also appreciated

  • Allocation of miscellaneous charges by weight and volume - all countries

    Can you please make available the functionality to allocation miscellaneous charges by weight and volume to all countries?  My understanding is that this is restricted by country but we find this requirement as a common request from most customers.

  • Formalise the counting of fixed assets

    Can we have some function in the application that allows users to formalise the counting of fixed assets?  Information required during counting include the ability to choose which asset groups need to be counted, date of asset count, the person who counted, use of mobile devices to perform count (such as reading barcodes), segregation of counts by location / person responsible for asset, approval to account for discrepancies, posting journals for discrepancies, etc

  • Sales and purchases default order settings by account and/or group

    We come across requirements where the default order settings are to be configured by a group of items for a customer / vendor or group of the same.  Companies in retail / distribution create such contracts based on minimum sales / purchases for every order based on the item group (such as a specific brand) to specific groups of customers / vendors.  Furthermore lead times can be assigned to the same contracts.  The default order settings are item based and do not support configuration for group of items / customer or vendor groups.  It also takes a lot of time to configure lead time on trade agreements in case we need to work with specific lead times by vendor or customer.    This can also create configuration errors as prices need to be considered when creating such lead times.  A company which sells 1000s of SKUs finds this hard to manage.

    Would be good to have some standard function to assist in completing such a configuration which is not dependent on the trade agreements as well as enhances the default order settings setup to incorporate groups

  • Number sequence for product receipt

    Can we have the option to manually input a product receipt number (as is today) and a number sequence to automatically generate the product receipt number on posting of the product receipt?

    Not all customers wish to input this manually and this can be easily automatically generated like other number sequences we have in the application.

  • Credit control on overdue balances

    Can we have the possibility to block the creation of new sales orders in case a customer is within the credit limit but has outstanding invoices that are due (past the due date).  For example a customer may be assigned a credit limit of €10,000 and has an outstanding balance of €6,000.  This customer has requested a new sales order worth €3,000 but has an outstanding invoice of €2,500 which should have been paid 3 months ago.  We need a configuration to block this sale.  Further more the following needs to be taken into consideration:

    • a tolerance such that overdue invoices can be ignored if the outstanding value is within certain limits;
    • an overdue invoice should be ignored if there are unmatched / unsettled credit notes / payments that can cover the balance of the overdue invoice
  • Allow end users to easily add fields to forms - to eliminate basic customisations

    It would be great to give the users (application administrators) to add fields to forms.  For example our customers are asking to customise forms (such as customers / vendors / fixed assets / products / sales order / purchase orders / etc) just because they wish to add some extra information - fields to keep a specific contact name, an address (such as ports of departure, arrival), any form of dates, some status, etc

    Features that we wish to assign to these fields include:

    - support for date fields, text fields, number fields, address fields, etc

    - assign some tooltip / help text which can be displayed to users when hovering on the field

    - determine where to show the field (that is which form should display)

    - if possible, determine the ability to copy the value of field to a secondary form.  such as the customer sales order defaults are copied to the sales order form

    - determine behaviour such as mandatory, limited to a list of pre-determined values, populate with a default value (such as today's date); this behaviour should be configurable by form