MS Dynamics SL Credit Card Security Fix

Microsoft Dynamics SL users have encountered a problem in which their application crashes when they attempt to transmit a credit card transaction. The problem is rooted in the TLS (Transport Layer Security) protocol, the cryptographic protocol that provides security over a computer network.

The steps to resolve the issue are as follows:

  1. Open Windows Powershell as an administrator
  2. Run the following script: [Net.ServicePointManager]::SecurityProtocol which should return the following results:

As you can see, only include Tls as opposed to Tls12

  1. Run the following scripts:

Set-ItemProperty -Path ‘HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319’ -Name ‘SchUseStrongCrypto’ -Value ‘1’ -Type DWord

Set-ItemProperty -Path ‘HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319’ -Name ‘SchUseStrongCrypto’ -Value ‘1’ -Type Dword

  1. Restart Windows Powershell and run the first script once again: [Net.ServicePointManager]::SecurityProtocol, which should now return results that include TLS 1.2

References to TLS 1.2:

Example of Merchant’s requirement to move to TLS 1.2:

MaxQ Technologies is a  Microsoft Gold Business Partner and creator of advanced Microsoft Dynamics business solutions. Contact us to learn more about how MaxQ solutions for Microsoft Dynamics can help your business.

Statistical Forecast for Better Demand Planning

Using a statistical forecast as a starting point often proves to be a solid start to a collaborative Demand Planning process. First, why do companies forecast? There are several benefits of more accurate forecasts;


  • Improve customer service levels.
  • Increased sales.
  • Reduced cost of carrying inventory.
  • Improved cash flow projections.
  • Production smoothing (level loading).
  • Reduced employee costs.
  • Increased return on investment.

In basic terms, all manufacturing/distribution companies want to do the same thing. They wish to have the right stuff in the right place, at the right time. So then is it better to use a statistical forecast or one made by a person? Well, a statistician would call this a choice between statistical and empirical estimate. The statistical forecast gets generated by software that calculates that forecast strictly by applying statitical techniques to the sales/booking history while an individual or a group of people uses judgment to formulate a collaborative forecast.

So then, how does the statistical forecast fit in a collaborative process? Some experts recommend using a statistical estimate as a starting point rather than asking someone such as sales person, to create a forecast from scratch. This statistical forecast, should not be the final answer; rather it is the starting point of that collaborative forecasting process. It’s a great input to start cross-functional demand planning.

Another question that people ask is; are there other cases where we should not use a statistical forecast? And the answer there is yes.  Any product that its history is not indicative of the future cannot use statistics effectively. Items that can be considered fads are particularly hard to predict. Many companies that have forecast increasing sales based on past sales trends for items that were a fads. They get stuck with inventory that can possible bankrupt a company. Remember the Atkins diet craze from a few years ago, Atkins Nutritionals went bankrupt after being to force to throw away millions of dollars of inventory.

New products, for example, pose a challenge for statistical forecast in that there’s no history, in this case, we suggest using a similar or like product, to model the projections for that new product.

Short life cycle products can also be a challenge because there’s a little history, and little history does not yield strong statistical forecasts. In other cases, volatility of historical demand can result in unstable or unusual trends that do not have any statistical correlation. And finally significant changes in demand patterns caused by acquisitions or other either company or external events can drive unreliable forecasts.

In summary, a statistical forecast can be an excellent tool but should not be the only method used to create an accurate forecast.

MaxQ Charge It! – Credit Card Accounting Demystified

Credit Card Accounting Demystified

MaxQ Charge It! for Dynamics SL


  • Invoice for $100 processed for Customer ABC using a Credit Card
  • Credit Card Fee of 3%



Step 1: Invoice to Customer ABC processed  – $100 balance in AR for Customer ABC

Debit                      Credit
A/R $100              Sales $100

Step 2: Batch Close – Customer Credit Memo
– Credit Memo ($100) created for Customer ABC leaving $0 balance on their account
– Credit Card Fees ($3) captured & booked to the expense account defined in Charge It! Setup
– Clearing Account is defined in Charge It! Setup

Debit                       Credit
Clearing $97           A/R $100
Fees $3

Step 3: Batch Close – Invoice to Credit Card Company
– Invoice ($97) created for Credit Card Customer defined in  Charge It! Setup
– $97 AR balance for Credit Card Customer

Debit                      Credit
A/R $97                 Clearing $97

Step 4: Payment from Credit Card Company

Debit                      Credit
Cash $97               A/R $97

– Payment ($97) for Credit Card Customer  created & applied