Use this function to extend the due date of customer notes payable/receivable entered for a payment.

The due date specified on the corresponding entries (e.g. entry generated on notes P/R posting) is also updated.

Prerequisite

See also Refer to documentation Implementation

Screen management

Entry screen

The customer open item due date extension is carried out in a grid where each line represents a payment.

Only the first column (payment number) has to be assigned. To search for a payment number, a Selection context menu opens a selection window for payments by type of payment, BP, etc.

Once the payment number has been entered, the information relating to this payment is displayed. The cursor is directly positionned on the Open item column where the new due date needs to be entered for this payment.

Once all the payments to be processed and the new extended due dates are displayed, you use the Save action to validate your change and apply it to the payment and journals generated for this payment.

Block number 1

Accounting date (field ACCDAT1)

Posting date of extension entries that are going to be generated. By default, the current date is displayed.

Grid Details

Payment no. (field NUM)

Number of the payment to be extended.
The following payments can be extended:

  • non domiciled, not on deposit slips
  • not validated on an intermediate account, bank account, doubtful receipts
  • and which due date can be entered (see Payment transaction).
BP (field BPR)
Date (field ACCDAT0)
Amount (field AMTCUR)
Currency (field CUR)
Due date (field DUDDAT0)
Due date (field DUDDAT1)

New payment due date. This extension date can be prior to the previous due date or later.

Description (field DES)

Document header description

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

 

"Function not authorized"

This message appears if the user does not have the correct access rights.

"Journal pending validation"

This message appears if the batch processing for journal validation has not generated an entry referring to the payment yet.

"Unsettled payment"

Impossible to extend a payment that has not been settled.

"Payment deposited in the bank"

Impossible to extend a payment that has been deposited in the bank.

"Payment number already entered"

The payment has already been entered in the grid.

"Invalid customer"

The BP entered is not a customer.

"Due date not managed for this type of payment"

The DACDUDDAT field is set to 3 in the TABPAYTYP file for the entered settlement type.

"You have no rights for this site"

You do not have access to the payments carried out for this site.

Tables used

See also Refer to documentation Implementation