• Approval workflow for Job G/L Journal

    Currently if you create a workflow for general journal batch approval, you have to create an option to select Job in the Template Type in the workflow. But there is no option to submit for approval or to approve on the Job G/L Journal page.
  • VAT/GST calculation for Prepayment Invoices should be based on VAT/GST Posting Group in the Purchase/Sales Order lines

    The VAT/GST calculation for Prepayment Invoices are based on the VAT/GST Prod Posting Group of the Purch./Sales Prepayment Account setup in the General Posting Setup. Even if the VAT/GST Prod. Posting Group is changed in the PO/SO lines, VAT/GST amount for Prepayment Invoice is calculated based on the VAT/GST Prod Posting Group of the Purch./Sales Prepayment Account setup in the General Posting Setup. The VAT/GST calculation should be based on the VAT/GST Prod. Posting Group in the PO/SO lines.
  • Posted Sales Shipment report should be prompted to Save when using Custom Word layout

    Currently, if Custom Word Layout is selected for Sales Shipment Report and the Sales Shipment is printed from the Inventory Pick, the system does not prompt to Save the Posted Sales Shipment. The scenario is as below: 1. Select Custom Word Layout for Sales - Shipment (Report ID = 208) 2. Create a Sales Order for a Location with Require Pick = True. 3. Release Sales Order and create Inventory Pick 4. Post and Print > Ship and Invoice Only the Posted Sales Invoice is prompted to Save and not the Posted Sales Shipment. If the standard RDLC report is selected for Sales - Shipment it will prompt to save both the Sales Shipment and Sales Invoice.
  • Posted Approval Entries does not exists for Journal Batches where Increment Batch Name = Yes.

    Posted Approval Entries are not created for Journal Batches when Increment Batch Name = Yes. 1. Create a new Journal Template: a. Increment Batch Name = Yes. b. Copy to Posted Jnl. = Yes. 2. Create a new Batch for the Journal Template Name = BATCH001 Copy to Posted Jnl. = Yes. 3. Setup Workfow for Journal Batch 4. Go to General Journal and select the Journal Template created in step 1 and Journal Batch in step 2. Create Journal Lines Send the Journal Batch for Approval 5. Post the Approved Journal Batch 6. Check Posted Approval Entries There will be no Posted Approval Entry with the Batch Name = BATCH001. As a result the Audit Trail for the Approvals will not exist. The Posted Approval Entries for the Journal Batches should be created when Increment Batch Name = Yes.
  • EFT Payments for Employees

    The feature to pay Employees through Electronic Fund Transfer (EFT) should be available in the Australian version of D365 Business Central. Currently the feature is only available for Vendor Payments.
  • Option to select Draft Invoice for Customers

    There should be an option to select Draft Invoice in Document Layouts drop down list to define Customer specific Custom Layout Description for it. Currently only the below options are available are Quote Confirmation Order Invoice Credit Memo Customer Statement Job Quote Reminder Shipment Draft Invoice is missing.
  • Difference field should be populated in Payment Reconciliation Journal when Applied to Bank Ledger Entries

    The Difference field in the Payment Reconciliation Journal lines when the line is Applied to a Bank Ledger Entry and Transaction Amount is less than the Applied Amount i.e. the Bank Account Ledger Amount. When the Bank Statement line amount is less than the Bank Ledger Amount, the Bank ledger need to be closed based on the Bank statement hence need to post the difference to a G/L Account same as what happens when Statement line Amount is higher than Bank ledger Amounts. This is quite common in customers using NAV in retail practise otherwise the Bank Ledger will be open for ever which defeats the purpose of Bank reconciliations. This results in lot of unreconciled Balk ledgers which leads to AUDIT issues for complying best practise of bank reconciliations in accounting application. The Bank Account Reconciliation age supports this scenario.
  • Provision to enter ARN (ATO Reference No.) for Foreign Vendors to calculate GST - Australia localization

    There is a need to calculate GST on Purchases made from Foreign Vendors. The Foreign Vendors will not have ABN but ARN (ATO Reference No.) and are registered with ATO under ‘Simplified GST Registration’. GST credit cannot be claimed against these transactions. In the current design, ABN field in the Vendor card cannot accommodate ARN. The logic for ARN is different from that of ABN and does not meet the validation setup for ABN in the Vendor card. So there is a need to accommodate ARN in the Vendor card for these Vendors so that they can lodge GST returns and pay GST quarterly and can pay electronically via SWIFT, bank transfer, credit or debit card. Please refer to the below link: https://www.ato.gov.au/business/international-tax-for-business/in-detail/doing-business-in-australia/australian-gst-registration-for-non-residents/ The expectation is to enter ARN for Foreign Vendors in the Vendor Card. Currently the feature is missing in Business Central - Australia localization.
  • Quantity field in Physical Inventory Journal lines should be editable for manually entered lines

    The Quantity field in Physical Inventory journal line is non-editable. While this makes sense for lines that are suggested by the calculate inventory, it does not allow to add lines which were not suggested. Example: Item A has a calculated quantity of 1 for Bin B01. During the count, we discover that the item is not in B01 so we set that to zero. However we find item A in Bin B10. To handle this we need to add line to the journal. If we do this, we are not allowed to edit the Qty. (Physical) so we need to edit the quantity.
  • Customer/Item Sales filtered on Ship-to Address of the Customer

    A Customer can have multiple Ship-to Address and the user would like to print the Customer/Item Sales report based on Ship-to Address.

    Currently the Customer/Item Sales cannot be filtered based on Ship-to Addresses of the Customer and printed. The Ship-to Code filter available in the Request page is for the Customer table but Ship-to Addresses reside in Ship-to Address table.

    The design should be changed so that Users are able to print the report based on the Ship-to Address of the Customer where the Items were sold.