Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Paul Ceely]

Could someone please explain how the Grace days in the Credit management checkpoint are supposed to work? I have tried using them but am not getting the results I expected.

Here’s my test scenario (with the Credit management checkpoint settings as shown in the attached screenshot):

Using a customer with a credit limit of $1,000, that has no open balances and no open activity (e.g. sales orders, packing slips, etc.)…

1. I create a first sales order (SO) with a value of $700. I am able to confirm this SO. I then create a load for the SO and release that load to the warehouse.
2. I then create a second SO for the same customer, this time with a value of $400. I am unable to confirm this SO, because the “order has been sent to credit management.” This makes sense ($400 + $700 > $1,000).
3. Then I post the picking list for the first SO. All good thus far…
4. However, when I subsequently try to post the delivery note for the first SO, this process fails and this first SO is also sent to credit management.

All the transactions and transaction attempts occur on the same day, so why am I not able to post the delivery note for the first SO?

Thanks in advance for any assistance!

——————————
Paul Ceely
Group ERP Functional Support Specialist
Britax
Fort Mill SC
——————————

[Tony Zeigler]

I haven’t been focused on the credit module for awhile – but I do know it used to be a common area to mod. The root issue that caused those mods sounds like what is impacting you now: Credit limits are held & maintained at the customer level – there is no “queue” for orders. Once a customer is over their limit, all checks fail for all orders. 
The typical mod I’ve seen was to remove orders held for credit from the calculation of the credit limit. That way, when an order gets sent to credit for review the other orders can continue to progress thru the system. 
I was really hoping the major revamp of the credit module was going to solve this – as it’s a major stumbling block for any company with a long manufacturing lead time.

——————————
Tony Zeigler
Senior Consultant
Strategic Solutions NW, LLC
Beaverton OR
——————————
——————————————-

[Brad Bertchie]

Paul;

Grace Day is the leeway window of overdue invoices.  So if you have an overdue invoice within the grace day period – it would still allow the order to go through (assuming the other variables are within tolerances).  Once you exceed that grace day – then it’s a hard stop.

——————————
Brad Bertchie
Senior Consultant
Western Computer
Oxnard CA
——————————
——————————————-

[Kelly (Kane) Gustafson]

Hi Paul,

Grace days in the new Credit management allow for a period of time where the blocking rules get bypassed during the grace period after a successful run at that specific level. For example, you confirm a sales order, D365 reviews the order against the blocking rules as established and everything passes without a credit hold. In your example, if you can run through the other examples selected (Release to warehouse and Delivery note) over the next two days, then credit management blocking rules will not be checked. 

This can be beneficial if there are long lead times on orders, for example. 

Ideally, the way I understand it, your example should’ve worked. This may be worth logging a bug with Microsoft.

——————————
Kelly Kane
Customer Experience Manager
Ellipse Solutions LLC
Dayton OH
——————————
——————————————-

[Shilpi Thakur]

Hi Paul,

A grace period adds value to the check per posting because it can allow you to only check outside of the grace period.

I.e. If grace period is set to 7 days and a sales confirmation was updated on 1st May and a delivery note was updated on the 4th July it would not recheck the credit rules, if the delivery note was processed after the 7th May it would check the rules once again.

The same rule applies to let’s say the cancellation of a Warehouse Management Work Order. I.e. If grace period is set to 7 days and a work order was released to the warehouse on 1 May and subsequently cancelled, then released to warehouse once again on the 4th May it would not recheck the credit rules, if released to the warehouse was processed after the 7th May it would check the rules once again.

In your case the confirmation grace period is 2 days and delivery note is set to a grace period of 1 day and the credit check should take place after the defined grace periods for confirmation and delivery note, so according to the above explained logic the delivery note posting in your example logic it should work [if all other parameters are set correctly].

Just curious have you setup any blocking rules for the overdue days or overdue amount under credit management setup?

——————————
Shilpi Thakur
Freelance AX/D365 Microsoft Consultant
Dynact Consulting Ltd
——————————
——————————————-

[Lori Holmes]

Hi Shilpi…I realize this is an old post, but your question intrigued me.  We are currently trying to determine why some of our Sales Orders that are Released, without posting, from Credit Management are going right back into credit management at the checkpoint.  We have one checkpoint for Release to Warehouse with a one day grace period. In our case, if we release from CM and attempt to Release to Warehouse immediately after releasing from CM, the order goes right back into CM. We expect the one day grace period to allow Release to Warehouse immediately after Release from Credit Management w/o posting.

In your post you asked if blocking rules for the overdue days or overdue amount under credit management were setup?  We do have an overdue blocking rule setup, but shouldn’t that also abide by the grace period?  I am wondering why you asked that question, have you seen anomalies surrounding overdue blocking rules?

Thank you in advance.

——————————
Lori Holmes
Hamamatsu Corporation
Bridgewater, NJ
——————————
——————————————-