On a daily basis, the “Coda files” which are the Bank electronic files with information about the amounts received on CICC bank accounts are uploaded into SAP. The system does the first sorting and processes the payments in which there is some valid and correct information displayed on the bank statement. Therefore, all the payments that could not be processed by the system have to be allocated manually by OTC BO AR.
The first thing to do is to print the Coda files as soon as the files are available in SAP coda transaction.
Remark : Not all the files arrive at the same time. OTC BO AR should check it regularly and after 10:00 (PT time) if some file is missing, OTC BO AR should send an email to CICC BO (bo.cicc@solvay.com) and an incident should be created by the Team Leader in Salesforce.
After printing all bank statement files, payments have to be posted on customer accounts using FEBA transaction.
|
To process a payment, click twice on the concerned line and afterwards on the floppy disk . This will have to be done for each red item.
At this stage, 5 possibilities can occur:
It might happen that due to wrong information on bank statement, system will open a wrong customer account. We should always confirm if the account opened by the system is the correct one checking the information available on bank statement as customer name, address or some invoice numbers. Thus, a new search should be executed. Please refer to “Account not found” chapter, where all the possibilities of finding a customer are described.
In case system cannot identify customer account due to lack of information, there are several possibilities to find it but the most common ones is searching:
Sometimes a part of the invoice is missing or a number is wrong. However, we can try focus the search on the document using * and trying different numbers in order to find the correct customer
Open items= list of invoices not yet paid in the customer account
d. Search using “Customers and Regions specificities” Database
All specificities regarding customer and Regions can be found on the following link:
This database should be consulted before any dispute creation so that we can assure all specificities are taken into account. |
4. The system opens more than one customer account
Sometimes we receive payments made by customers before the goods are shipped and invoice sent and assigned to CICC. Therefore, we receive the payment and the invoice isn’t yet available on customer account.
There are three steps that should be considered when recording a payment in advance:
This gives the invoice numbers sent to the customer “6111221031” and “6111295868” which should be found on customer account in WARP (PI1). In case the information is not enough or in case you are not sure of the correct invoices, you can try to find by the order number that is mentioned in the assignment field in PI1.
In case of having an order with “Payment terms”: “Payment in advance”, we should check if the customer name and the amount of the order are the same as mentioned on the bank statement. If yes, we can record the payment in advance on customer account and inform Credit Manager/Credit Analyst through dispute (automatic). If not, we should create a dispute and ask confirmation from Credit Manager/Credit Analyst regarding the order number.
Then, check the last order and in case of non-conformity create a dispute/case.
There can be more than one proforma document mentioned in the bank statement and the numbers of the proforma documents can start with different numbers as 77… or 922…
The proforma references are different depending on the company that issues the document.
If there is more than one proforma document, all of them should be checked and orders found. The sum of all orders should be equal to the total amount of the payment. If the amount is not the same always create a dispute/ case asking for the confirmation of the orders and the amounts related to each of them. Check also if the difference is banking fees through customer masterdata.
If no useful information can be found or if there is the slightest doubt, create a dispute asking for details to the Credit Manager involved. |
The example described is related to PF1 system, however the same procedure should be executed for WP1 and RHO.
The first thing to do is to post the payment on customer account as a “DZ” document type entry (see procedure used to record a DZ on customer account -“Posting a payment as DZ on customer account”)
Remark: If the original payment was made via check, the document type entry recorded is “DK”. It may also happen that the document type entry recorded is “AB”, as a reconciliation resulting from using transaction F-32. This procedure only mentions document type “DZ”, but it applies exactly the same way for document types “AB” and “DK”.
After this posting, the information will be sent from WARP system to local system, which will create a payment in advance request (DI creation on customer account in local system – in this case doc. 2580000027). This DI will be extracted on a program and a new DI will be sent to WARP (doc. 2580000015). Then, a job in WARP will run automatically and will create an E5 document on customer account which will clear the DZ and the DI. This also will create a new E5 open with the special indicator A (doc. 7700000015) and text: “PMT. ADVANCE”. See below an example:

Afterwards, a dispute will be automatically created informing Credit Manager of the posting.
The same result can also be seen in local system (in this case PF1 - doc 2510000479 w/ Special GL A):

When the invoice is assigned and there is no difference or the difference is on the customer master data tolerance, an automatic job run every day and clears the E5 with the invoice (s). If there is a difference which is above the tolerance, the job will not clear and we should ask information to Credit Manager.
As soon as the invoice is cleared, the posting on customer account is as below:

To add another order for this payment, we should select
and fill with the information regarding the other order.

Then, we should click on
so that automatically the Net value field is updated (Sales order amounts) as below:

Finally, insert the correct amount on “PayAdvAmnt” field according the orders and press Save
. In case there are banking fees, the amount inserted should be changed so that the total amount of the orders is the same as the payment amount.


Choose Yes and the following message appears:

After this posting, the information will be sent from WARP system to local system, which will create a payment in advance request (DI´s creation on customer account – in this case doc. 2580000028 and 2580000029). This DI will be extracted on a program and a new DI will be sent to WARP (doc. 2580000016 and 2580000017). Then, a job in WARP will run automatically and will create two E5 document on customer account which will clear the DZ´s and the DI´s. This also will create two new E5 open with the special indicator A (doc. 7700000016 and 7700000017) and text: “PMT. ADVANCE”. See below:

Afterwards, a dispute will be automatically created informing Credit Manager of the posting.
When the invoices are assigned and there is no difference or the difference is on the customer master data tolerance, an automatic job run every day and clears the E5 with the invoice (s). If there is a difference which is above the tolerance, the job will not clear and we should ask information to Credit Manager.
As soon as the invoices are cleared, the posting on customer account is as below:

Differences on Payment in advance:
When Assistant Credit Managers give us instructions to perform a payment in advance and to post a difference as banking fees or discount, we should process the payment in advance and indicate banking fees/discount amount on the text. These differences can only be posted when the E5 is cleared against the invoice(s).
When processing cash allocation, it might happen we find a customer that is blocked. Therefore, the system will give an error message stating that the customer account is blocked for posting. Find below how this situation should be handled.
In this situation, OTC BO AR should analyse if the customer account suggested by the system is the correct one (in transaction FBL5N confirm if there is an open invoice, if there is another customer account with the same/ similar name or if there are Salesforce cases with the same issue) and in case of doubts contact Credit Manager before requesting the unblocking.
In case the blocked customer is the correct one, OTC BO AR will need to create a case and transfer it to Data Control team (Queue “Data Management”) asking to unblock the customer account. When Data Control team will transfer back the case to AR Level 1 queue saying that the account was unblocked, we should post the payment on the account and after we should return the case to them so that they can block the customer account again.
In order to register this payment as unallocated, we should create a case and classify it with status “Need of more information” and Status reason “Unallocated”. |
For all cases in which we receive a payment in CICC which should be transferred to other Solvay company, we should follow the described procedure.
|
The posting executed will clear automatically the TI’s in WARP and 0231 according to the clearing below:


Change the flag coda in Z_FLAG_CODA transaction |
Note: Use transaction Z3F_FA_AFF_INFO to understand if an IBA is created and weather it is available or blocked for posting:
In case the IBA doesn’t exist or it is blocked, we should search if there is an vendor account for that company and it has a bank account. If not, please send an email to treso.cicc@solvay.com |
Selecting this option, the objective is to use the payment to be transferred and paid back (ex: transfer to Solvay affiliate whenever there is not convention with CICC or to transfer to other entity that not Solvay as the case of de-migrations or companies which were sold).
Every time there is a return of a payment, a credit note, banking fees or a cancellation of a payment, we receive a negative amount on the CODA files.
When a negative amount arrives in FEBA statement list, the way to proceed depends on the subaccount on which the amount is posted. This chapter describes how to handle these transfers.
Before asking details to Credit Manager/CICC BO, we should first analyse the bank statement and the Sub-account related looking for a document number or customer number that could lead us to the Country/ Region related. Then, we should also try to see if it is related to banking fees or to a payment to customer, which could be already executed by OTC BO AR. |
For all payments that OTC BO AR is not able to find the correct customer account, some steps need to be followed:
CICC/RHODIA bank account should be mentioned on the email as well payment amount/date and bank statement. |
Then, order by amount on “Net value” column and try to find a similar amount with the payment amount we have received. After go to VA03 transaction with the order number to retrieve more details and finally go to customer account and analyse payment history and previous bank statements to confirm it is the correct one.
Afterwards, whenever the payment remains unallocated and we are waiting for information we should create a note with Salesforce case number in SAP PI1 entry document (900…), as follow:
In this case, we have mistakenly received a payment from other which is not a Solvay customer. Therefore the payment should be rejected. If we received that payment on a BNP bank account, it is possible to ask the transfer back asking it to bo.cicc@solvay.com. If not BNP, we should try to find a contact of the entity which made the payment so that we can request bank details and proceed with a manual reimbursement.
This section describes the main principle which must be respected concerning the monthly closing and explains how to proceed when an answer is received for a payment when the corresponding accounting period is already closed.
For clearings on F-32 transaction we should ALWAYS use payment date (see value date of DZ document) on the “Clearing date” field. In case the period is already closed, we should use first day of the current month. |
WARP closure starts on D-1 (last working day of the month). See below the impact of the closure on FI-AR-BO postings:
Postings with discounts, exchange and interests: The last day to perform with current month date is on D-1
Customers clearings: The last day to perform with current month date is on D+1 except the ones involving discounts, exchange and interest differences
In case we receive a payment on first day of the month which amount is high (> 200.000, 00EUR) that involves discounts or exchange we should clear the invoices (s) with D-1 clearing date, leave the discount (s) related and post it with D+1 clearing date on another clearing. In this way, we can clear the payment on the correct month and the discount will be re-invoiced on next month. |
Posting a payment in a closed period:
Sometimes we have to post a payment when the period is already closed. Please see below how to proceed: