Comments
With the latest version of Business Central, the problem is still there:Version: CA Business Central 25.0 (Platform 25.0.25411.0 + Application 25.0.23364.24599)When we try to refund a customer on a payment journal by EFT it doesn't work. Even if we setup bank account information under customer card, it is impossible to Generate EFT file and also to send to many customer at the same time the remittance advice. We can't select this usage under Customer documents layout.Can you tell when it will be possible to Export a payment Journal by email also for a customer? The vendor remittance report indicate Customer and Vendor information but we can choose Output Method Email, only print or PDF to see the remittance advice.When we Generate EFT File, we can see the payment to be generate but there is an error message.Error message: The account type or balance account type should be vendor on the following General Journal Line: Journal Template Name = PAYMENT, Line No. = 10000.AL call stack: "EFT Recipient Bank Account Mgt"(CodeUnit 10200).ValidateAccountType line 3 - Base Application by Microsoft"EFT Recipient Bank Account Mgt"(CodeUnit 10200).GetRecipientVendorBankAccount line 2 - Base Application by Microsoft"EFT Recipient Bank Account Mgt"(CodeUnit 10200).GetRecipientVendorBankAccount line 6 - Base Application by Microsoft"Export Payments (ACH)"(CodeUnit 10090).CheckVendorTransitNum line 6 - Base Application by Microsoft"Generate EFT"(CodeUnit 10098).StartEFTProcess line 48 - Base Application by Microsoft"Generate EFT"(CodeUnit 10098).ProcessAndGenerateEFTFile line 17 - Base Application by Microsoft"Generate EFT Files"(Page 10810)."GenerateEFTFile - OnAction"(Trigger) line 7 - Base Application by Microsoft
. Request Details:Currently, there is no system validation occurring against the physical product during the Customer Order fulfillment process at the POS level.We request the ability to scan each line item on Customer Orders via a barcode scanner during the Picking process. D365 should then automatically validate the scanned product against the corresponding line item in the order.If the scanned item does not match the order's line item, the system should prompt the staff to rescan the correct item intended for the order.Before migrating to D365, our store staff used “Comestri OMS”, and this scanning validation feature was a key functionality that we find missing in D365 (OMS). 4. Pain Points:Currently, staff must visually validate each item by matching product labels (e.g.: item name, size, colour) with the details displayed on the POS screen during the Picking process.There is a risk of human error, where staff might accidentally pick and ship incorrect items to customers due to the lack of D365 validation, resulting in customer dissatisfaction.The manual validation process is time-consuming, reducing overall productivity.Handling a large number of orders without this feature increases the operational cost for the business. 5. Benefits:This feature will allow staff to efficiently pick and validate each line item, ensuring faster and more accurate order fulfillment.Reduced human error and minimized manual intervention.Improved productivity and reduced business costs.Improve customer satisfaction with the D365 ERP.