Coverage Control 

Purpose

When you want to pay vendor open items, you create a Multiple Payment Order (PAYMUL) message and send it to the bank (see Payment by Payment Order, step 1). One of the first things the bank does is to check whether your bank account contains enough money to cover the payment. This check is known as “coverage control.”

The process flow below illustrates how you use SAP ECC in the coverage control process. The exact coverage control process varies from bank to bank. The process shown is that followed by BBS.

Process Flow

...

       1.      You send a PAYMUL message to BBS with payment instructions.

       2.      BBS processes as many payment orders as it can before your account runs out of money. It then sends you a Banking Status (BANSTA) message.

       3.      When you receive the message, you load it onto your file system and then read it.

The message lists the payment orders that it could not carry out. You now have one working day to transfer the necessary money to your account.

       4.      Later the same day, BBS runs another check.

If, in the meantime, you have transferred more money to your account, BBS carries out the remaining payment orders. You can now await the arrival of the Multiple Debit Advice (DEBMUL) message (see Payment by Payment Order, step 5).

Otherwise, it sends you another BANSTA message, informing you that the payment order has failed again.

       5.      The following day, BBS runs a third and final check.

If you have still not transferred any money, BBS cancels the payment orders and sends you a BANSTA message to inform you that it has done so.

       6.      You delete the payment order in the system (see Payment Orders).

       7.      The bank sends you a DEBMUL message with details of the payment orders that it has carried out.

Result

If at the end of this process you have still not paid the invoices, you include them in the next payment run.