Due date modification reasons

The due date modification is a critical process with potential impact in AR performance (Pastdues & DSO), possible detrimental of GBU action plans to improve DSO and Lack of Control. 

As so, there should be maximum restriction of due date modifications. The request should come from GBU, Collections and validated by CM:

It is up to AR team to control and change if the request is according to the reasons validated and with the necessary Documentation or Evidence:

Here also some examples of other reasons which are not valid to change the due date:


 

AR should only change the due date if validated by CM and if the request contains the documentation required. If a case is not compliant with the valid reasons it Should be escalated to  François Rublon.

 

Due date modification in SAP

After running the transaction for the due date modification, please assure that the modification was successful executed in both systems. If not, please create an IS ticket

Access transaction Z3F_FA_CHGE_DOCS_ERP in local system

You should choose the options “Change customer documents” and “Due date/Calculated paym. Date” according the screen above. 

Then insert the customer number and company code. 

Execute . The following screen will be shown:

 

Choose Yes

 

 

In the screen below, you should check which are the documents which were requested to be changed:

 

 

Add the new Due date and the status will become green: 

Press   to complete the operation:  

It is possible to see the modification in the log  

In case there are more than one document to be modified with the same value, select all the lines to modify and press 

 

Add the due date and 

Press   to complete the operation. The due date will be changed in WARP and Local System.

 

For some documents you will not have the “Due date (new)” field editable meaning that you will not be able to change it though this transaction. This can be due several reasons which the most commons are related to the fact that it is a credit note already due or a document with special g/l indicator. In these cases, an IS ticket should be created asking IS to proceed with the change (we should assure that the date is correct in WARP and local system).