...
...
...
...
...
4. Reversals
Scope
ERP
References
Attachments
4. Reversals
| Warning | ||
|---|---|---|
|
...
- For transition reversals (bank statement received in WARP for an invoice in 5763/5976), please consult the google file below:
https://docs.google.com/spreadsheets/d/17YSvipbEzSPgcNqnOvqtVnIcp5e9621okHWer1chMMQ/edit
This should be very rare and only related old open items in old Factoring Companies – 5763 and 5976
- Before doing a reversal, we should be sure that we really need to reverse especially if the clearing was done in a previous period which is already closed. Reversing a clearing will imply that all documents will be re-open, which will have an impact in the GBU (invoices will appear as overdue as there isn't anymore a payment linked)
Before doing a reversal, we should be sure that we really need to reverse, especially if the clearing was done in a previous period which is already closed. Reversing a clearing will imply that all documents will be re-opened, having an impact in the GBU (invoices will appear as overdue as there isn't anymore a payment linked) |
Reversals guidelines
There are two cancellation transactions that can be used to reverse the documents:
- FBRA – When the reversal already includes cleared items. Ex: A payment (DZ) was already cleared with invoices
- FB08 – When the reversal
Reversals guidelines
There are two cancellation transactions that can be used to reverse the documents:
...
- does not include cleared items. Ex: An open payment (DZ) on customer's account
There are
...
two reversal reasons
...
depending on the period:
- 01 code –
...
- If the document is reversed during the current opened period
- 02 code –
...
- If the document is from a period that is already closed
...
...
document before the others |
4.1 Bank transfer reversal
Due to a wrong clearing between a payment and one or more invoices, sometimes it is needed to cancel a matching on customer's account. In order to reverse the erroneous reconciliation, it is necessary to know the following items:
- Document type «700…. » which corresponds to the reconciliation item on customer's account;
- Document type «870.... » which corresponds to the reconciliation item of the bank sub-accounts (if
...
- the sub-account was reconciled already)
...
...
...
...
...
...
...
...
...
Choose 
and Execute
...
WARP sub-account
In WARP, a new DZ with opposite sign is created and clears the original one
0231 sub-account
In 0231 when we reverse a payment, an U3 is created with an opposite sign. See below:
...
| title | Warning |
|---|
...
| Warning | ||
|---|---|---|
| ||
In order to post again the payment in FEBA transaction, we should change the flag using transaction Z_FLAG_CODA. After this, the payment will be available again to be posted. See below the steps to be executed |
...
. |
...
...
...
...
...
...
...
...
...
the 
icon).
When you are sure of the payment, remove the tick from the "Test" box and click on
...
the 
icon.
The payment is now available again on FEBA transaction to be posted.
4.1.1 Local Payment reversal
There might be the need to reverse payments which were received
...
in local bank accounts. In this case, there are three situations of local cash application which can trigger a reversal:
...
- Finance team download the bank statements and leave the payment open on customer account or clear it with the invoice
...
- AR team does a manual posting in customer account following information in Bank
...
- site
- Finance team
...
- inform us that a payment was received and we clear the bank account with customer account (ex. Procter and Gamble)
...
...
...
...
...
...
...
cleared it with customer invoices (Procter and Gamble):
In the case above, the payment was allocated by
...
Finance team in
...
G/
...
L account 5080900000 and we have cleared the G1 (payment) with the invoices in customer account.
In case we need to reverse, we should reverse document 2510139708 in FB08 transaction which will re-open the invoices and the DZ and then it is possible again to clear other invoices.
If the wrong clearing is due
...
to a clearing in a wrong customer, then we should use FBRA transaction in order to cancel the DZ. In this case, the payment should be allocated again in the correct customer account using FB05 transaction.
4.2 Reconciliation invoice/credit note reversal
There is an automatic job which runs in all customer accounts to clear invoices vs credit notes which have the same assignment. The principle is that all these clearings are correct as based on the assignment number which corresponds to the order number.
Therefore these reversals should be limited to the cases in which the customer pays an invoice which was already cleared by a credit note or if there are more than one invoice or credit note with the same assignment which might
...
have been assigned after and that the system cleared the wrong documents.
...
In case customer pays an invoice already cleared by a credit note and in order to have the same open accounting items as the customer for audit purposes, we should reverse this clearing and leave the credit note open to be deducted by the customer in other payment.
This section explains the steps that should be followed to reverse the reconciliation.
...
...
...
...
...
...
...
...
- on
The reconciliation has been cancelled
...
...
...
...
...
and
Save 
4.4
Save
Cheque reversal
The cases for reversing a clearing with a cheque should be rare as normally we receive the information regarding the invoices in advance. However, in case of insufficient funds on customer bank account, we should proceed the same way as for bank transfer reversal explained in the chapter related (the only difference is the document type of the cheque is DK).
| Warning | ||
|---|---|---|
| ||
After the reversal, FF68 or FB05 transactions should be executed again in order to create a new DK document in customer account |
4.5 Misdirected payment reversal
A misdirected payment is a payment received in local bank accounts for a customer assigned
...
to SOLVAY SA (CC 0231) or Solvay Finance America (Cc 4044).
In case of a wrong clearing, we might need to reverse the document.
...
The reversal that needs to be done depends on the necessary correction:
- The customer's account is correct, just the wrong invoice was cleared, we should
...
- make a reset only using FBRA transaction and then clear the DT document
...
- that became open on the customer's account with the correct invoice using transaction F-32.
2. The clearing was done on the wrong customer's account, the reversal to be done is different (the example below):
First of all using transaction FBRA we should reset the 7000029074 document that is clearing these items:
The document that needs to be reset can be found as follows:
Double click on the DT document, press 
button and double click on the first line:
In this window you can see the document that needs to be reset:
After the document is reset, the next step is to fully reverse the clearing on customer's account. It can be done using transaction FB08. The document to be reversed is 7000029073:
The next step is to go to transaction FB05 and make the posting between the correct customer's account and G/L account of misdirect payments:
Once this is done, we should clear the item that was reset in the first place with the new item generated on the G/L account 5080930000.
4.6 Direct debit reversal
For direct debits there is an automatic job through F110 transaction which clears the invoices which are due and create a file which is then handled by IHB team (bo.ihb@solvay.com). In case of unpaid, we would need to make the necessary corrections in customer account.
An unpaid in direct debit can be detected through three ways:
- Negative amount in Feba transaction
- Credit Manager/ Business or Cash Collections team request
- During sub-accounts reconciliation detecting a debit movement
| Warning | ||
|---|---|---|
| ||
Even if we are informed by someone that customer will refuse a direct debit, we should always check if we have received the debit in our bank account (TO) |
Example of an unpaid:
Checking the flag we can see the invoice details:
In order to reverse the clearing, go to customer account in FBL5N transaction and identify the document that needs to be reversed.
In this case we need only to reset the original DZ document using FBRA transaction:
After that payment method of invoice should be changed to "A".
With transaction FB05, we should make the following posting:
Document type: DZ
01 - Customer's account - Amount of unpaid
50 - Subaccount - Amount of unpaid
Clear DZ (original) with DZ (created) using F-32 transaction.
Then go to F-03 to clear the G/L account: TO with DZ.
| Warning | ||
|---|---|---|
| ||
|
4.7 Draft reversal
We have manual and automatic drafts for France (Traites) and Spain (Pagarés and Recibos). For this payment method, we might receive an unpaid from a customer due to several reasons: customer didn't agree with the debit for some reason; a credit note was created after the amount was sent to the Bank; liquidity issues, etc.
In case we receive an unpaid, we should detect it through a debit in our sub-account (TO). In this case, we should check the flag related with the TO. See below an example:
Checking the flag, we can see all the details:
It is possible to retrieve in the bank statement the original document (in this case 7630000683) for which we should check in FB03 transaction:
Click on the second line to retrieve all the details:
Following the confirmation that the amount of the TO is the same of the draft amount, we can proceed with the reversal. For drafts (except Pagarés) we should use transaction Z3F_FA_RFBITB01_BOE in order to re-open the invoice:
When the window opens, please insert the Customer number and the Document Type:
and press 
.
Select the line related to unpaid and press 
.
| Warning |
|---|
|
4.8 Pagarés reversal
The reversal related to unpaid of pagarés depends on the fact if we receive a TO on G/L account or not:
- If we receive a TO document, we should only reset the DE document using FBRA transaction.
- If we do not receive a TO or TI document, we should reverse all generated documents 76600..., 76400... and 76100... using FBRA and FB08 transactions.
4.9
| Warning | ||
|---|---|---|
| ||
Due to a technical constraint, all the unmatched misdirected payments which were left on customer account due missing details should be reversed and allocated again in case of a clearing which includes leaving a residual. If the unmatched payment will then be cleared totally (no residuals), there is no need to reverse and allocate it again. |
Direct debit reversal
There are direct debits for Switzerland, Germany and UK. In these countries, there is an automatic job through F110 transaction which clears the invoices which are due and create a file which is then handled by CICC BO. In case of unpaid, we would need to make the necessary corrections in customer account.
An unpaid in direct debit can be detected through three ways:
- Negative amount in Feba
- Credit Manager/Business or Collections team request
- During sub-accounts reconciliation detecting a debit
| Warning | ||
|---|---|---|
| ||
Even if we are informed by someone that customer will refuse a direct debit, we should always to check if we have received the debit in our bank account (TO) |
Example of an unpaid:
Checking the flag we can see the invoice details below:
In order to reverse the clearing, go to customer account in FBL5N transaction and identify the following documents:
- Bank sub-accounts clearing
- DZ document
Use transaction FBRA for both documents in order to re-open the invoice.
| Warning | ||
|---|---|---|
| ||
|
See example below:
Open FSEPA_M1 transaction and insert customer number:
Click on 
and click twice under the mandate
Click on 
and change the mandate status from Active to Canceled
Draft reversal
We have manual and automatic drafts for France (Traites) and Spain (Pagarés and Recibos). For this payment method, we might receive an unpaid from a customer due several reasons: customer didn't agree with the debit for some reason; a credit note was created after the amount be sent to the Bank; liquidity issues, etc.
In case we receive an unpaid, we should detect it through a debit in our sub-account (TO). In this case, we should check the flag related with the TO. See below an example:
Checking the flag, we can see all the details:
It is possible to retrieve in the bank statement the original document (in this case 7630014037) for which we should check in FB03 transaction:
Click on the second line to retrieve all the details:
Following the confirmation that the amount of the TO is the same of the draft amount, we can proceed with the reversal. For this, use FB08 transaction in 7630014037 document as below:
Save 
This will re-open the original DY and the invoice. We should then create a "false" DY document to clear the original one in the customer account using FB05 transaction as below:
Click on "Choose open items" and select the original DY. Then credit sub-accounts related (in this case 50533EUR17") in order to clear the unpaid (TO).
Click on Enter
Insert the amount of the draft, the value date (today's date) and in the text insert" UNPAID Inoice x".
Click on 
Afterwards , the TO should be cleared with the DY in the sub-account
| Warning | ||
|---|---|---|
| ||
The payment method of the invoice should be changed to "A" and a dispute to Collections with reason "Unpaid" and status "Call by collector" should be created in order to ask customer the reason of the unpaid and agree in a new payment |
RIBA reversal
RIBA is a payment method used only for Italian customer for which there is an automatic job running through F110 transaction which will clear in customers' accounts all the invoices due within 1 month. The invoices will be cleared with a DY and a positive DY will stay open until due date of the invoice is reached.
For this payment method, we might receive an unpaid from a customer due
...
to several reasons: customer didn't agree with the debit for some reason; a credit note was created after the amount
...
being sent to the
...
Bank; liquidity issues, etc.
The process of the unpaid in RIBA is fully automatic. There is one file received in SAP with the information of the RIBAs unpaid.
...
| Warning |
|---|
Afterwards, there is an automatic SAP job which will "read" this file and the documents unpaid and will do the resetting of RIBA document in customer account and re-open the invoice and the original DY. |
...
Then, it will clear automatically the original DY with another |
...
DY which will also credit the sub-account (50513EUR17) to be cleared with the unpaid (TO). The payment method of the invoice is also automatically changed from "B" (RIBA) to "A" (Bank transfer) and a dispute is created to Cash Collections team informing about the unpaid. Cash Collections team will then contact the customer to understand the reason of the unpaid and agree in a new payment. Finally, there is an email, which is sent automatically to AR mailbox, every time there are RIBA unpaids for which we should check if all the items have ✔, meaning that all steps went correctly. |
See example below
...
Freshdesk ticket number 698973:
...
If all the documents have ✔ it means that the reversal was done successfully and nothing needs to be done further by AR team.