!--a11y-->
Transferring SD Bills to FI-CA 
If you want to transfer SD bills to Contract Accounts Receivable and Payable, you have to make various settings in the implementation guides for both Contract Accounts Receivable and Payable and Sales and Distribution (SD).
For each account group, you define whether a bill is to be transferred to Accounts Receivable Accounting (FI-AR) or to Contract Accounts Receivable and Payable (FI-CA). In the account group you define whether the related customers are to be transferred to FI-AR or FI-CA during SD billing.
● You have to specify the receivables accounts for Contract Accounts Receivable and Payable in the reconciliation account determination in Sales and Distribution (see IMG structure: Sales and Distribution ® Basic Functions ® Account Assignment/Costing ® Reconciliation Account Determination).
● The customer master record must contain a reconciliation account for customers (in the FI-AR sense), even if you do not want to transfer to FI-AR. Due to the general checks during transfer, you have to enter a reconciliation account for customers (in the sense of FI-AR reconciliation accounts) in the company code-relevant data for customers.
● When entering an SD order, you must select a contract account. This contract account must be assigned to the FI-CA business partner. If there is exactly one contract account for the payer, this is transferred automatically to the order.
● When you create a business partner for the customer in Contract Accounts Receivable and Payable, you must specify an SD sample customer so that the SD views required for creating the order are available in the background. An SD customer is created whose customer number is identical to that of the FI-CA business partner.
●
The transfer from SD to FI-CA is
activated at the accounts receivable account group level. This means that for
each account group, you define whether SD bills for these customers should be
transferred to FI-AR or to FI-CA (see IMG structure Contract Accounts Receivable and
Payable ® Integration
® Sales and Distribution ® Define Posting in FI-CA for Customer
Account Groups).
Note that when you create an order, you can only
enter customers from one of the two account groups as being the payer. This
means only customers that trigger a posting in FI-AR during invoicing or
customers that trigger a posting in FI-CA. Note that you cannot activate the
SD/FI-CA transfer for one-time account groups.
● The main and subtransactions used in Contract Accounts Receivable and Payable are derived from the SD bills during transfer (see IMG structure Contract Accounts Receivable and Payable ® Integration ® Sales and Distribution ® Derive Main/Subtransaction with SD Information).
● The document type with which SD bills are posted in Contract Accounts Receivable and Payable is derived from the SD bills during transfer (see IMG structure Contract Accounts Receivable and Payable ® Integration ® Sales and Distribution ® Derive Document Type with SD Billing Document Data).
● Using event 4000, you can add the billing data (see IMG structure Contract Accounts Receivable and Payable ® Program Enhancements ® Define Customer-Specific Function Modules).
The reconciliation key is determined automatically during the transfer of SD bills. There is no difference between individual bills or mass runs. In both SD billing methods the reconciliation key is assigned according to the same procedure. Composition of reconciliation key: SDxxxxyyy_zz.
Part of key |
Meaning |
XXX |
Current year |
YYY |
Current day in year |
ZZ |
Sequence number |
A new reconciliation key is assigned to SD bills for every day of the year. If this reconciliation key is closed during the course of the day, or if two processes try to open the same reconciliation key simultaneously, a new or a second reconciliation key is opened with the next higher sequential number. Reconciliation keys generated this way are only permitted for posting SD bills. The reconciliation key is not closed automatically.
The reconciliation account is determined automatically when SD bills are created for Contract Accounts Receivable and Payable. (See the IMG structure: Sales and Distribution ® Basic Functions ® Account Assignment/Costing ® Reconciliation Account Determination).
In the SD order, the default value for
payment conditions is derived from event 4010 in Contract Accounts
Receivable and Payable, provided that a corresponding function module has
been defined in this event. If no function module has been defined, or if no
default value can be found, then the payment conditions are determined in the
standard SD manner.
For IS-U and IS-T a function module has been defined in event 4010 in
Contract Accounts Receivable and Payable. This determines the default
value for payment conditions from the contract account named in the order
header. Depending on the order type, either the payment conditions for
incoming payments or for outgoing payments are determined in accordance with
the relevant payment conditions defined in the contract account.
In the SD order,
the contract account field has been included as a new entry field for
Contract Accounts Receivable and Payable. This field is in both the
header and in the item section of the order. The SD business partner whose
contract account is specified is the payer of the order. If there is exactly
one contract account for the payer, this is transferred automatically to the
order. If there is more than one contract account, a selection list appears
when an order is created. You can define your own payer/contract account
combination for each order item. The bills are then split for different
contract accounts.
The contract account from the accounting viewpoint is specified in the order
header.
From the accounting viewpoint, the following entry fields are not considered during transfer to Contract Accounts Receivable and Payable:
● Dunning Key
● Dunning Lock
● Payment Method
● Assignment
In event 4040, you can restrict the selection of contract accounts when you create/change an SD order.
In the SD order, the default value for
the business area is derived via event 4020 in Contract Accounts Receivable
and Payable, provided that a corresponding function module has been
defined in this event. If no function module has been defined, or if no
default value can be found there, then the business area is determined in the
standard SD manner.
For IS-U and IS-T a separate function module has been defined that determines
the default value of the business area from the contract account specified in
the order header.
In view of the payment control in Contract Accounts Receivable and Payable (due date for cash discount + discount% /due date for net payment), not all standard FI payment conditions can be used. The following restrictions apply:
● Only one cash discount date can be defined. The second cash discount date is interpreted as being the net due date and must have 0.00 as the discount percentage rate.
● The payment conditions must be defined for the entire month and valid throughout this period.
● No installment payment conditions are supported.
● The IS-U feature of including a factory calendar in conversion of payment conditions to the corresponding due dates is not supported.
A check is made to ensure that a payment condition is suitable for use with FI-CA. This check is made during assignment of the payment condition in the sales and distribution area data (customer billing), and also when the SD order is created.
Reconciliation between the individual components can only be made for closed posting periods and for points in time at which all Contract Accounts Receivable and Payable reconciliation keys have been transferred completely to the general ledger.
The customer line items in the SD billing document transferred to the financial accounting interface are supplemented with the following information:
● General information (for example, reference details)
● Information from the contract account (for example, account determination ID)
● Information on main and subtransactions for each company code and division (such as dunning, interest, or payment)
The business partner item in Contract Accounts Receivable and Payable is created from the customer line item.
Information is derived via event 4000, which is called to supplement customer items and G/L account items.
The main and subtransactions of an SD document are determined in event 4030. In this event you have access to all of the information in an SD billing document, which means that a more detailed transaction determination is possible here in contrast to Customizing.
You can use the functionality implemented in SD for creating down payment requests from billing plans as well as the subsequent down payment clearing for down payments made.
You can use the function for invoicing external transactions. For this, the contract account must also be included in the communication structures.
When reversed bills are transferred to accounting, the accounting documents arising out of this are flagged as reversed and the open items are cleared immediately. If this cannot be done, an accounting document is created that has a reversed +/- sign. This may happen, for example, if the bill has already been cleared or if the payment order has already been created.
No Reversal of
SD Bill in the Case of Subrogation
If the customer changes and the receivables (open items) are transferred, the SD bill can no longer be reversed. The bill cannot be reversed as the open item(s) were cleared in Contract Accounts Receivable and Payable with reason 21 (subrogation).
Display FI-CA Documents
In the document flow for Sales and Distribution (SD), you can display FI-CA documents and archived FI-CA documents.
The function scope of the interface between SD and Contract Accounts Receivable and Payable was enhanced to meet requirements in Argentina. For more information, see SAP Note 211917.
