Power Community

Power Community

5 scenarios that show how credit limits are determined in Dynamics 365 Finance

In Dynamics 365 Finance, you can use the credit management capability to define a credit limit at the customer level. However, the same customer might also be part of a customer credit group that has its own credit limit. So how does Dynamics 365 Finance determine which limit to use for sales orders when there’s a limit set in both places?

Here are five scenarios that describe how customer credit groups and individual customer credit limits affect each other.

Scenario 1: Individual limit is lower than the group limit

  • Individual customer credit limit = 10,000
  • Customer credit group limit = 15,000

How the credit limit is determined: The customer’s effective credit limit is 10,000 because it’s less than the group limit. Blocking rules first check the group limit, and the customer passes these rules. Blocking rules then check the individual customer credit limit and blocks any orders greater than 10,000.

Scenario 2: Individual limit is higher than the group limit

  • Individual customer credit limit = 20,000
  • Customer credit group limit = 15,000

How the credit limit is determined: The customer’s effective credit limit is 15,000 because blocking rules always check the customer group credit limit first.

Scenario 3: Individual limit is 0.00 and mandatory credit limit is enabled

  • Individual customer credit limit = 0.00 and mandatory credit limit option is set to Yes
  • Customer credit group credit limit = 15,000

How the credit limit is determined: Even though the customer is part of a group, their effective credit limit is 0.00. This supports a scenario where the customer is part of a group, but all orders must go through credit management for additional review.

Scenario 4: Individual limit is 0.00 and unlimited credit is enabled

  • Individual customer credit limit = 0.00 and unlimited credit limit option is set to Yes
  • Customer credit group credit limit = 15,000

How the credit limit is determined: This supports a scenario where the customer is part of a group but their effective credit limit is unlimited.

Scenario 5: Individual limit is 0.00, and neither unlimited credit nor mandatory credit limit is enabled

  • Individual customer credit limit = 0.00 and unlimited credit option is set to No, and mandatory credit limit is set to No
  • Customer credit group credit limit = 15,000

How the credit limit is determined: The customer’s effective credit limit is 15,000 (the same as the group limit).

All these scenarios still have to meet the applicable blocking rule criteria for the customer, table, or group before the order can be sent to credit management.

Next steps

Check out the documentation for Customer credit groups for more information.

The post 5 scenarios that show how credit limits are determined in Dynamics 365 Finance appeared first on Microsoft Dynamics 365 Blog.

- Advertisement -spot_img

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisement -spot_img
- Advertisement - Advertisement

Latest News

Power Fx: Error handling graduates to preview

We are thrilled to announce that the long-time experimental feature Formula-level error handling has moved forward to preview. As a result, you and your end users will enjoy higher reliability and more transparency about what is happening in your apps. It’s a huge step. Adding error handling to an existing language turned out to be a very tall order, touching almost everything, from data types, to functions, to the runtime. Thank you for all of your support, feedback, and patience as we got this done. What does it mean for you? Your apps will more reliably detect and report errors.You can write blank/null values to a database.You can detect and replace errors with the IsError, IsErrorOrBlank, and IfError functions.You can control error reporting and logging at a central location with App.OnError.You can create and throw your own custom errors with the Error function. Error handling is a big change in behavior. By entering preview, we are signaling that we believe we are done, that we anticipate no further significant changes from here. Many of you already use error handling in production and this move to preview should only embolden more of you to do so. If significant changes are needed from here, we will treat them as a separate feature. We are rolling this out slowly as it is such a big change. All of you will soon see that the Formula-level error handling switch has moved from experimental to preview in the settings (as of version 3.22082). It will still be default to off for most tenants. Over the coming weeks we will slowly change the default for new apps only to on across the tenants. Makers can still disable this feature and will be able to do so for a long time. I say again: we are changing the default for new apps only. Existing apps will continue running as they always have. We have no plans at this time to turn this on for existing apps, and as this is such a big change, we may never do this and make this a permanently available switch. Your feedback will guide us. The documentation for Error, IfError, IsError, IsErrorOrBlank functions and the App.OnError property covers these changes. IfError and IsError are very similar to their Excel counterparts. We are also working on overview docs that will be released shortly. But before that, let’s take a brief tour. Let’s start with what Excel does, the inspiration for Power Fx. For an error like division by zero, Excel is very clear that something has gone wrong with a # error message that shows right in the cell. This error will propagate to other cell formulas if A1 is used in a formula: Today, without error handling, Power Apps won’t report anything in this scenario, instead treating the division by zero error as a blank value. That’s not good, as the maker and the end user of the app have no idea something may have gone wrong: Errors happen. Unexpected data flows in, networks go down, storage fills up, to name just a few situations that an app may encounter in the real world. Makers don’t often think through all the ways that things can go sideways which makes default error handling even more important. Returning a blank for an error is also a problem because blank is a legitimate value in our type system and in many databases. Without error handling, Power Apps won’t allow you to write a blank to a database instead thinking it is an error. So, instead of returning an easy to ignore or misinterpret blank value, with error handling turned on we now report an error to the end user (the error banner) and show the formula as having an error to the maker (the red filled in circle on the control): Further, if you look at the value of the formula, it is not a blank but an error value. Just as any formula can result in a blank, now any formula can also result in an error: Now, we still aren’t showing an error in the label control itself as Excel does. We couldn’t do this generically because, unlike Excel, the error could be on a property of a control for which there is no way to display the error. For example, where should an error on a slider control? Where should an error be shown for an imperative operation in the middle of a button’s OnSelect formula? We settled on showing the end user banner and flagging the control in the design experience. That’s not to say you can’t detect and display an error in that label control. Error handling provides a wealth of mechanisms to control how errors are handled and reported. For example in this case, we can wrap the division by zero with an IfError function to return a custom message in the label: The Text function call is required for type compatibility. Or we can use IfError to throw a different, more specific error with the Error function: Or we can have a catchall for all errors in the app with App.OnError. For example, we can log the error and present a different message to the end user: If we look at the log, we see the details of the captured error from FirstError (and there is also an AllErrors), including where it happened and when it was detected: The possibilities are endless! You now have all the tools you need to detect, replace, report, and log errors, including a good default behavior if you never take advantage of these tools. And, bonus, you can also now write blank (or null) values to databases. Please let us know what you think in the Power Apps community forum. There is a dedicated and active space for error handling discussions at Error Handling – Power Platform Community (microsoft.com).

More Articles Like This

- Advertisement -spot_img