Cross Company Code Payment explained

A cross company code payment happens when a company code within the group (Paying Company Code) for some business reason, pays the open items of another company code (s) (Sending Company Code).
This post discusses the configuration settings involve in Cross Company Code Payments and its pre-requisites. It also includes explanation to end users on points to note when executing the automatic payment run (F110) for cross company payments.

Pre-requisite

It is important that these conditions are present before you attempt cross company payments between company codes:

1) The paying company code and the sending company code (the company code whose open item is being paid) must have the same local currency and if applicable, same parallel currencies.
If this is not the case you may get the error below if you attempt to do your assignment of paying and sending company codes in your configuration settings
“Company code xxxx is not permitted as the paying company code”

2) The paying company code and the sending company code (the company code whose open item is being paid) must be in the same country.

 

Configuration Settings

The following settings should be done in the system before you can execute cross company code payment:

I) Maintain the Cross company code settings

A cross company payment will result in a cross company posting that will record a receivable in the paying company code and a payable in the sending company code. For a cross company postings to happen, irrespective of whether it is a payment transaction (cross company payment), an invoice posting or just a G/L posting etc. this configuration setting has to be in place.
Follow the menu path below, for cross company setting:

IMG — Financial Accounting (New) — General Ledger Accounting (New) — Business Transactions — Prepare Cross-Company Code Transactions
Or use transaction OBYA

 

ccp1

ii) Maintain the company code relationship in the payment program setting

The “paying company code” must be define as such in automatic payment program settings (FBZP), and the same applies to the “sending company code”. See the settings below:

ccp2

ccp3

 

Processing a cross company payment through F110

Post an invoice in the Sending Company Code

After all the necessary settings and other pre-requisite are done, post an invoice with FB60, FV60 etc. in the sending company code
Display the invoice posted on the vendor using transaction FBL1N (Vendor line item display) as below:

 

ccp4

 

The Vendor in the sending company code has an invoice posted on it.

Now execute the APP Run (F110)

Note: in the parameter selection during the automatic payment run, the company code to select is the Sending Company Code and the Vendor is also the vendor of the Sending Company Code on which the invoice is posted.

 

ccp5

 

However, in the edit proposal the house bank and the house bank account to select will be the one for the Paying Company Code (hence the cross company situation) as below.

 

ccp6

ccp7

 

 

Payment run successfully executed.

As can be seen below, two documents are generated by the payment run, one in the paying company code and the other in the sending company code. See below:

 

ccp8

 

In addition, if you display one of the documents you will see a third document, which is the cross company document. See below:

 

ccp9

 

Display the cross company document with FBU3 to see the complete posting in one display.

 

ccp10

 

As you can see the Vendor in the sending company code is debited and the House Bank account in the paying company code is credited .The intercompany account between the two company codes is debited in the paying company code (representing a receivable) and credited in the sending company code representing a payable (to the paying company code).

Note: That if a company code is defined as a sending company code in APP configuration you cannot now pay open items from that company code through APP, all the open items on this company code have to be paid through the paying company code defined for it in configuration. If for any reason you want to do this, you have to change the configuration and define the company again as a paying company code.

 

 

Sapgurus.com

8 thoughts on “Cross Company Code Payment explained

  1. Thank you very much for your valuable post. All of your posts are so easy to understand that now I am eagerly waiting for your next post to learn.
    Kind regards,
    Rajani

  2. This is a brilliant forum for learning as such intricate topics are picked and discussed in detail. Please keep the inflow of such a huge knowledge bank coming.
    Thanks for this support

  3. Does anybody know how this should be done for cross company payments. Currently we have a paying company UK and branches in Europe with no bank accounts and want to automate the intercompany as much as possible.

  4. Hi all,
    As per SAP Standard FBZP allows one relationship from the Sending Company to Paying Company.
    We need help for the options:
    Sending Company Paying Company
    1) ABC Ltd XYZ Ltd
    2) ABC Ltd ABC Ltd

    The 2nd option is not possible as we have already assigned paying company as XYZ. We need to use the 2nd option also for processing F110 for the user to pick up the Sending company as the Paying company also even though FBZP is assigned with different Paying company – XYZ.
    Please through your ideas to fix.

  5. Sorry the space in the options in the Sending and Paying company is taken correctly.
    ABC is the sending company and XYZ is the Paying company.

  6. Hi thanks for detailed steps. However I got stuck at the edit payment proposal where the payment control screen with home bank is defined. Could you please help with that ?

Leave a Reply

Your email address will not be published. Required fields are marked *