Dynamics Community Forum Thread Details

How to calculate exact overdue values for the customers

Dear Community,

I would appreciate your guidance on the best approach to accurately calculate the customer overdue amount using the Aged Balances form in D365 Finance and Operations.

Could anyone assist me in understanding:

Which specific fields or filters should be used?
How to distinguish between the total balance and the truly overdue portion?
Any recommended reports or best practices to ensure accuracy?

Aging period definition setups:

I added the "Overdue amount" field at the end using personalization, but I'm not sure if the system calculates the same value for this field as it does for the "Amount due balance" field, as shown below.

We have a customer requirement to block Sales Orders based on a defined range of overdue values. To meet this, I am planning to:

Configure blocking rules based on the overdue value thresholds.
Create a workflow to trigger approvals for Sales Orders that fall within the specified overdue range.

Could anyone assist with:

Best practices or recommended setup for this scenario?
How to properly configure the conditions for overdue value-based blocking?
Any considerations or challenges to be aware of while integrating with workflow?

Your guidance would be greatly appreciated.

Regards,
Abhijit Das

Categories:

Dynamics 365 Finance

Good morning, afternoon, or evening depending on your location!

To accurately calculate overdue values for customers using the Aged Balances form in Dynamics 365 Finance and Operations, and to implement blocking rules based on overdue thresholds, here’s a detailed approach:

Calculating Overdue Values:

Fields and Filters:
- Use the Aging Period Definitions to define intervals such as "Current," "30 days overdue," "60 days overdue," etc.
- Ensure the Overdue Amount field is personalized and added to the form. This field calculates overdue balances based on the aging period setup.
- Use filters like Due Date or Transaction Date to distinguish between total balance and overdue amounts.
Distinguishing Overdue vs. Total Balance:
- The Amount Due Balance field represents the total outstanding balance, while the Overdue Amount field isolates balances that fall into overdue categories.
- Verify the calculation logic in the Aging Period Definitions to ensure the overdue amount aligns with customer requirements.
Recommended Reports:
- Generate the Customer Aging Report to view overdue balances by aging periods. This report provides a clear breakdown of overdue amounts.
- Use Customer Aging Snapshots to analyze overdue balances at specific points in time.

Blocking Sales Orders Based on Overdue Values:

Configure Blocking Rules:
- Navigate to Credit and Collections > Setup > Blocking Rules.
- Define thresholds for overdue amounts and specify actions (e.g., block sales orders or require approval).
Create Workflow for Approvals:
- Set up a workflow in Accounts Receivable > Workflows to trigger approvals for sales orders exceeding the defined overdue thresholds.
- Include conditions based on the Overdue Amount field.
Best Practices:
- Regularly update aging snapshots to ensure accurate overdue calculations.
- Test blocking rules and workflows in a sandbox environment before deploying to production.
- Communicate the blocking rules to relevant teams to avoid disruptions in sales order processing.

Considerations and Challenges:

Integration with Workflow:
- Ensure workflows are configured to handle exceptions, such as urgent orders requiring manual overrides.
Customer Communication:
- Notify customers about overdue balances and provide options for resolution to avoid blocking sales orders.
System Performance:
- Large volumes of transactions may impact performance. Optimize aging snapshots and workflows to minimize delays.