Share
Report
7I have provided case study i have build Properly but when i synchronize database it getting 50 Error and all are Log Error ..Please help me
Case Study: Customization in D365 F&O – Vendor Payment Restriction for Specific Invoice
Business Scenario
USMF required a control mechanism in D365 F&O to prevent payment processing for specific vendor invoices under certain conditions. These conditions included:
- Invoices under dispute
- Invoices pending internal approval
- Invoices flagged for audit or compliance review
The standard D365 F&O functionality did not support invoice-level payment blocking without manual intervention, which posed risks of accidental payment and compliance issues.
Standard Behaviour in D365 F&O
In standard D365 F&O, the Vendor Payment Proposal process includes all open invoices based on filters like due date, vendor group, and payment method. There is no out-of-the-box feature to automatically exclude specific invoices unless manually removed during proposal review.
Accounts Payable 🡪 Invoices 🡪 Open Vendor Invoices
Customization Objective
Introduce a “DoNotPay” flag on vendor invoices.
Ensure flagged invoices are excluded from:
- Payment proposals
Vendor Payment Journal 🡪 Payment Proposal
- Manual payment processing
Vendor Payment Journal -> Select Vendor 🡪 Settle transaction
Solution Design
1. Data Model Extension
- Add a custom boolean field
DoNotPayto theVendTranstable (Vendor Transactions). - Field exposed on the Vendor Invoice Journal and Open Vendor Invoices form.
2. UI Enhancements
- Checkbox labeled “DoNotPay” added to invoice entry and inquiry screens.
- Tooltip and validation to ensure users understand the impact.
3. Payment Proposal Logic
- Modify the VendPaymProposalController class to filter out invoices where
DoNotPay = true. - Ensure compatibility with batch jobs and recurring payment proposals.
Note: This Customisation should be applicable for Existing invoices also
All responses (
Answers (
