A/P-A/R accounting > Payment orders > Manual reconciliation 

Use this function to reconcile notes payable/receivable issued by the bank with the notes payable/receivable in portfolio.

This process can also be launched automatically.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

A dialog box opens where you can specify the paying bank notice assignment criteria:

  • Bank
  • Statement number

The notes payable/receivable table of the payment is initialized. Each line represents a specific note.

It is possible to directly export the paying bank notice from this function using the Bank file button.

Warning: Any exported notice can no longer be modified (neither in the manual reconciliation function nor in the payment cycle - Enter the paying bank notice). This export must only be launched once all the lines in the notice have be correctly entered.

Notes payable/receivable table

With respect to the RAPLCR parameter, either all the lines in the paying bank notice issued by the bank are displayed or only non-reconciled lines (if the automatic reconciliation has already been run).

The notes payable/receivable is identified in the first five columns:

  • Due date
  • Currency
  • Amount
  • Drawer's name
  • Drawee's reference

The following columns are used to specify the acceptance of the submitted notes. Thus, the non reconciled lines can be accepted or rejected (in part or in full). It is also possible to specify which lines contain errors.

Accepted lines

The accepted lines must therefore have the Accepted field set to Yes.

  • If a payment number is specified in the field provided for that purpose, the reconciliation is carried out and the payment cycle is not broken (this line is then visible during paying bank notice entry, making it possible to continue the posting steps on the payment). When all the lines are assigned it is possible to export the notice either directly with the bank file button or upon paying bank entry (if modifications are still expected before the posting of payments).
  • It is still possible to directly export the notice to the issuing bank if the payment number is not entered on some of the lines. It is then necessary to manually process the payments to complete the missing information.
Rejected lines

The rejected lines must necessarily have the field Accepted field set to No. It is then necessary to specify a rejection code (miscellaneous table  no. 305) in the related field.

The rejected lines are also exported during the related bank notice export. The issuing bank is then notified that their submitted notes P/R have been rejected.

Lines with errors

It is possible to mark certain lines in the imported notice as being abnormal. This option is proposed by means of the right click menu.

These lines can neither be exported nor automatically reconciled.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Specify the bank of the LOC statement to be loaded.

  • Statement (field FRMNUM)

Specify the number of the LOC statement to be loaded. It must belong to the bank previously specified.

 

 

  • Payment date (field DATREG)

 

  • Return limit date (field DATRET)

 

Grid Details

  • field ANO

 

  • Due date (field DUDDAT)

 

 

  • Amount (field AMTCUR)

 

  • Payer name (field NAMCDT)

 

  • Drawee ref. (field REFDEB)

 

  • To (field ACP)

 

  • Payment (field PAYNUM)

Specify the payment number to be reconciled with the statement line.

This payment must be assigned to the same company and statement as mentioned on the statement.

  • Accepted (field PABFLG)

Specify if the notes payable/receivable will be paid fully or in part.

Choose the No for partial payments.

Enter here the reason why the payment will not take/has not taken place.

  • Paid amount (field PABAMTPRT)

Specify the amount actually posted upon deposit in the bank.

It is always equal to the payment amount.

Block number 3

  • Statement total (field AMTTOT)

 

 

  • Paid amount (field AMTPAY)

 

 

Close

 

Action icon

Problem

 

Close

 

Specific Buttons

The Save button is used to validate the reconciliation if and only if a payment is posted to the line where the Payment approval field is set to Yes. A paying bank notice is then created for the accepted payments on paying bank entry, which makes it possible to continue with the reconciled payments cycle (posting).
The End button is used to cancel the reconciliation.

It is used to launch the statement export.

Error messages

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

"Statement already exported"

The statement has already been sent to the bank.

"Bank XXX"

The statement relates to another bank than the one requested.

"No notes to be reconciled"

There is no notes payable/receivable to be reconciled assigned to the requested statement.

"Code already entered on line ##"

The payment entered has already been reconciled on line ##.

"Payment type not set up for this function"

The payment type assigned to the payment is not defined for the "Paying bank" phase.

"Status: XXXXX"

The payment has reached step XXXX, which either does not exactly precede the "Paying bank" step or is later than this step.

"Company XXX"

The payment does not belong to the same company as the statement.

"Bank XXX"

The payment does not belong to the same comapny as the statement.

"Payment type"

The payment is not of the same payment type as the other reconciled payments. In fact, a paying bank notice is a single payment type.

"Payment on the paying bank notice XXX Statement already exported"

The payment has been reconciled on another paying bank notice and the latter has already been sent to the bank.

"Payment on paying bank notice XXX"

The payment has been reconciled on another paying bank notice. This is a blocking message if this notice is being authorized on another workstation, if not it is a warning message. In this later case, the payment will be transferred onto the paying bank notice being processed.

"AmountM1 (Statement) M2 (Payment)"

The notes payable/receivable amount on the bank statement (M1) is different frm the amount of the reconciled payment (M2). This is a warning message.

"Due dateD1 (Statement) D2 (Payment)"

The due date on the notes payable/receivable on the bank statement (D1) is different from the due date of the reconciled payment (D2). This is a warning message.

Payment XXX Status YYYY Cancellation impossible

One of the lines in the reconciled payment has been changed on one of the lines of the statement. During an attempt to validate the reconciliation, the process has established that the previously reconciled payment has between times reached the next step (YYYYY). It is therefore impossible to modify the reconciliation.

Payment XXX status YYYYY

During an attempt to validate the reconciliation, the process has established that payment XXX has reached step YYYYY, which either does not exactly precede the "Paying bank" step or is later that this step.

Payment XXX Statement already exported YYY

During an attempt to validate the reconciliation, the process has established that payment XXX has already been reconciled on another statement and that this statement has been sent to the bank.

Tables used

SEEREFERTTO Refer to documentation Implementation