Recognize COGS in intercompany billing process

Dear expert,
I read the intercompany billing process and have some confuse.
The process like that: CC1(company code 1) sells to end customer, CC2 (conpany code 2) (internal relationship) issues good.
1, CC1 sells to end customer. CC1 create the SO
2, CC2 creates the DO and PGI, that recognize the COGS at CC2 for the internal sales.
3. CC1 creates the billing to end customer --> record the revenue of CC1
4. CC2 creates the internal billing to CC1 --> record the internal revenue of CC2
My question is, follow this process, I don't see the COGS of CC1, there is only a outbound delivery create by CC2 and COGS of CC2.
I read the document about cross transaction, but it guide me only for steps above.
Are there any mistake here?
Please give me a help.
Thank you in advance!
HongDM

Dear expert,
I have some question about the document flow of the intercompany billing process.
Company code 1 (CC1) sell to customer
CC2 issue goods to customer of CC1, then internal billing to CC1.
the step as below:
1. CC1 create SO (sell to customer)
2. CC2 create outbound delivery to Customer of CC1, recognize COGS of CC2
3. CC1 bill to customer, recognize revenue of CC1
4. CC2 create internal invoice to CC1, recognize revenue of CC2
in internal invoice of CC2, update the output RD04. Does it recognize COGS and goods receipt to CC1? Because as above document flow, I see that, the CC1 don't have COGS, not receipt goods to plant of CC1 and Account Payable for CC2. There my thinking as logic of flow, but I'm not sure what the EDI and RD04 can do. Can you tell me about that.
Thank you very much, this is very helpful for me.
Best regard,
HongDM

Similar Messages

  • Accounting entries for intercompany billing process

    hi,
    can any body explain what it intercompany billing process and intra company billing process and STO processess.
    and their individual accounting entries of these three business with excise impact.
    regards,
    balajia

    > Total Questions:  494 (232 unresolved) 
    Perhaps you should reconsider the quality of your questions? In this one you seem to have put in absolutely no effort of your own, but I will put some effort into tracking down your next question for you...
    Please read the forum rules before continuing further.

  • CIN Pricing Procedure for Intercompany Billing Process

    Hello All,
    Please suggest me what Pricing procedure I can use for Intercompany Billing for CIN.
    I have created a ZPricing Procedure coping the JINFAC but its for normal sales what CIN configuration I have to do for Intercompany billing.
    Please suggest..
    Regards
    Venkat

    Not Answered

  • Pricing error in intercompany billing

    My client is using the intercompany billing process.
    There is a BOM item with item category group LUMF and the pricing happens at sub item level. In the sales order and the customer billing document the pricing happens at sub item level only.
    But in the intercompany billing the pricing happens at both main item and sub item levels. The pricing procedure is dfferent here.
    Both the sales pricing procedure and intercompany pricing procedure has the condition type ZI11. The requirement 22 is attached to the condition type at both the pricing procedures.
    In the intercompany pricing procedure, subtotal L is assigned to the condition type ZI11.
    The condition type ZI11 is configured as under.
    Access Seq : ZI11
    Condition class : B (Prices)
    Cond category : C (Qty)
    Rounding rule : commercial
    Manual Entries : B (Automatic entry has priority)
    Item condition
    Amount / percent
    Int-comp Billcond
    Can anyone tell me why the item is priced at both main & sub item level in the intercompany billing.
    Regards,
    Bala

    Hi,
    Please check with the defination of the Item cateogry for the Main Item for the InterCompany Invoice.
    The relevance for pricing should be ticked off.
    Reward points if it helps.
    Regards,
    Harsh

  • Inter Company Billing process

    Hi,
    We are testing the Inter Company Billing process.
    Please clarify the below my doubts: what are we doing in these below two transactions? and what kind of documents will get created after executing both the transactions?
    1) /N/DSD/DE_ENTRY
    2) /DSD/SL_COCKPIT
    I am FI Consultant, so not able to understand clearly the above transactions.
    Please explain in detail.
    Regards,
    Vidya

    Dear Vidya,
    The transactions which you have mentioned are not related to intercompany billing process. as suggested by our friend above.
    I will try to elaborate the use of the metioned transactions. These both transactions are used in case of direct store delivery componant, and are based on the tour data.
    1) /N/DSD/DE_ENTRY :
    Generally in direct store delivery process, material is loaded on the trucks and check out from warehouse is done, this material is delivered by driver to several customers on his way and he also collects cash payments, cheques form several customers. he can also pick up empties from the customers and then he comes back to the warehouse with empties and payments. where check in is done.and all data is entered regarding empties and payments.
    Now whtever he has delivered and brought back has to be entered in the system, which is nothing but tour data entry which is above transaction.
    2) /DSD/SL_COCKPIT
    Based on the tour data entered the system will carry out the settlement. and for the settlement you need to use above transaction.
    here you will enter the data in check in and check out as tour entry.
    then system will compare  the data and creates different kinds of documents like
    debit memo's to customer , credit memo's in customer incase some returns, empties credit memo, billing documents against received payments, and most importantaly credit or debit memo against driver if empties quanity differs from wht is signed by customer.
    I hope this gives you some insight of these transactions and helps to clear your doubt. But there is more which you can read about it.
    Regards,
    Paresh

  • Intercompany billing Delivery to Billing document

    Dear all,
    I have scenario intercompany billing process where in the proces as follows
    - customer billing is fine with 2 line items from different plants and i have 2 deliveries and i have 1 invoice
    - when it comes to intercompany billing with the delivery related system is not picking the first line item but it is picking the 2nd line item only.
    i need both the line items to appear in the intercompany billing document.
    i have checked the copy control in VTFL, my settings are as follows
    004  Deliv-related item               
    003  Single invoice
    can any body suggest me a solution, this is very urgent for me
    Thanks & Best Regards
    Naveen

    sorry my settings for the above scenario are
    015  Itm dlv.rel.IC bill         copy control
    001  Inv.split (sample)
    Thanks & Best Regards
    Naveen

  • INTERCOMPANY BILLING & Contract

    Dear guru
    what is mean intercompany billing & Contract? and give me the steps to config. in sd module.
    regards
    Mohammedrenu
    [email protected]

    INTER COMPANY BILLING
    Definition:
    A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
    To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
    It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
    Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
    Sales organizations and plants assigned to each other need not belong to the same company code.
    In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
    PARTIES INVOLVED
    1) End Customer 2) Ordering Company code 3) Supplying Company Code.
    End customer:
    Customer who orders goods from the ordering company code.
    Ordering Company Code:
    Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
    Supplying Company Code:
    Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
    CONFIGURATION SETTINGS
    Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
    DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
    Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
    Assign Organizational units by Plant:
    Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
    Define Internal Customer Number By Sales Organization:
    Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
    Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
    Transaction Code: XD01
    The ordering sales organization is represented as Internal customer of Supplying company code.
    We need to create customer master in Account Group - Sold to Party and maintain minimum required financial & Sales Area data.
    This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
    PRICING:
    We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
    We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
    This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.We maintain PR00 condition type to represent the ordering company code's price to the end customer.
    Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
    Eg: Sales Org. of Ordering company code + End customer + Material.
    We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    Pricing Procedure ICAA01is determined at Intercompany billing processing level.
    Pricing Procedure ICAA01 - Pricing Procedure for Inter company billing is assigned to the combination of:Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
    Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
    PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    ILLUSTRATION:
    STEP 1: Create Sales Order
    Manually Enter the Delivery Plant of the Supplying Company Code:
    OBSERVE CONDITIONS SCREEN FOR ITEM:
    PR00 represents Price to the end customer (in other words, revenue for the ordering company).
    PI01 represents cost to ordering company (in other words, revenue for the supplying company). It is represented as statistical item only.
    DELIVERY:
    Delivery is carried out from the supplying point & hence we can observe that it is done from shipping point assigned to the supplying point.
    Subsequently, Picking & PGI are carried out.
    BILLING TO END CUSTOMER:
    T-Code: VF01
    Create Intercompany Billing:
    T-code: VF01
    OBSERVE THE CONDITIONS SCREEN OF THE INTERNAL INVOICE:
    IV01 Condition type represents revenue for the supplying company code.
    VPRS condition type represents cost to the supplying company code.
    PR00 in intercompany billing document displays amount billed to the end customer. It serves as just an information item and is inactive.
    If the ordering company enters the incoming invoice manually, the delivering company can print out an invoice document with the help of output type RD00, which is then sent to the Payer.
    If automatic invoice receipt has been agreed, we must use the SD output control functions to ensure that output type RD04 is found in internal billing. In R/3 system, output determination procedure V40000, which includes this output type, is assigned to Intercompany billing type IV.
    The automatic posting to the vendor account is initiated when output type RD04 is processed. The system uses the EDI output type INVOIC in the FI variant.
    To ensure that payables are posted in financial accounts of the ordering company, the delivery company must be created as a vendor.
    <b>Contracts</b>
    Follow the links
    http://help.sap.com/saphelp_47x200/helpdata/en/06/57683801b5c412e10000009b38f842/frameset.htm
    Master Contract:
    The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
    Use
    You group contracts as lower level contracts under a master contract to ensure that
    The terms in the master contract are granted in all the lower level contracts
    The data in all lower level contracts remains consistent
    You can group the following documents under a master contract:
    Quantity contracts
    Value contracts
    Service contracts
    The link between the master and lower level contracts is controlled by the referencing procedure which is assigned to the master contract type in Customizing. The referencing procedure determines which data is copied from the master contract into the lower level contracts
    Structure
    A master contract contains header data only. In the master contract, you can record:
    Business data
    Partner data
    Contract data
    Billing plan data
    On the overview screen of the master contract, there is a list of all the lower level contracts which refer to it. You can branch from this list into the individual contracts.
    Master Contract: The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
    Check these links on Master Contract
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd0d545a11d1a7020000e829fd11/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd34545a11d1a7020000e829fd11/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd27545a11d1a7020000e829fd11/content.htm
    Details about contracts:
    Lets take standard CQ contract type:
    First maintain customer - material info record in VD51 T-code
    Secondly maintain pricing for customer / material or only material combination in VK31 / VK11 T-code
    Then use VA41 T-code to create a contract
    VA42 to change contract
    VA43 to display / view contract
    In VA41, enter the document type CQ, followed by the sales area details,
    Enter Sold to party.
    Enter PO number
    Enter PO Date
    Enter Validitiy from Date
    Enter Validity to Date
    Enter Material
    Enter Quantity say 999,999,999 or any other higher quantity as it is referred again and again
    Hit Enter.
    Save.
    For further info refer below
    : CONTRACTS
    Contracts
    Reward if Helpful...
    Regards,
    Praveen Kumar D

  • Intercompany billing in Is-Retail

    at present we are having one company code, we are planning for one more company code let say we are having 9000 company code and planning new business with new company code 6000
    we are planning existing comapny code will become customer for new co.code 6000
    in this case we need to set up intercompany sales/billing, as part of this acctivity we need to map part of 6000 co.code DC as vednro for stores of 9000 code and part of 9000 co.code stores will become customers for 6000 co.code DC.
    how to map this in SAP?
    if i will not map this ccustomer-vendor relation what is the impact on intercompany billing?

    Hi Charan,
           You can check the below link which might of help
    IS Retail Intercompany billing process
    Rgds,
    Aram.

  • Create Intercompany billing without Good Issue

    Hi Gurus,
    I use Cross Company purchasing process with One step configuration. Normally it's used to be like this:
      1. Create Outbound delivery with reference to PO (t.code VL10B)
      2. Post good Issue --> automatic generate GI & Good Reciept document
      3. Create Intercompany billing with reference to the Delivery above.
    But now I want to go directly from step 1 to step 3 that means I want to create Inter. Billing with reference to Delivery which has not been post Good Issue. What should I do to solve this problem?
    Thank you very much,
        Hong Trinh

    Hi,
    You need to initially decide if you want to go with Cross company STO process through Purchasing or Intercompany Sales/Billing through Sales.
    Directly going from step 1 -3 is not possible.
    Only after you do a GI from the replenishment delivery and GR at the receiving plant will you be able to create an Invoice.
    If you are going with the Intercompany billing process, the sold to party/ship to party in your delivery should be the internal customer/plant and not the external customer. In this case you first need to create a F2 invoice and then IV invoice.
    Regards,
    Amit

  • Billing posting for intercompany delivery process

    Hi all
    we configured a new process for intercompany billing to use a standard PO for delivery between a warehouse and a store both in different co codes. Process is based on vendor and customer defined in retail sites both WH and store. Eg. WH site code D002 with assigned vendor D002 and customer D002. Similar for receiving store RA01, vendor and customer RA01.
    Financial entries for delivery and billing posting are done between thses AP/AR accounts. As we have several warehouses and lots of stores will become difficult for finance to reconcile it.
    Request is to have one generic customer assigned to all warehouses and one generic vendor assigned to all stores, this reducing (in FI view only).
    my questions:
    1. is any way to configure in FI or Billing for a several customers with different codes FI entry to be posted to one AR account only in issuing company and similar for several vendor accounts during MIRO FI entry to be posted in one AP acount only?
    2.  On standard intecompany delivery, since we use only one document in both companies (PO) what is the way to do a reconciliation betwen PO issued and booked at receiving site. Like transaction codes eyc.
    Thank you in advance for help
    Silviu J

    Hi,
    My suggestion would be to go with the DIP Profile with the material determination.
    In your case it would be the travel expenses.
    Create a WBS elemenent where these services are being used and make it as billing element.
    Assign a sales order with this this material and assign this DIP Profile in Sales Tab-B.
    DP81, ODP1 are the Tcodes you can look for..
    Reward points if found useful.
    Thanks..

  • Intercompany billing -accounting process

    Hi,
    I would like to know the best way of accounting the intercompany transactions.
    From my understanding, intercompany billing transactions accounting should be handled as below;
    1. in Provider OU, debit cost to provider's P&L a/c when cost is incurred
    2. While generating receivable invoice, credit revenue to Provider's P&L a/c.
    3. this way, The profit margin (if margin is charged over the cost by provider OU) reached to provider P&L a/c. (Net effect between cost and revenue)
    4. In receiver OU, debit cost to P&L a/c and create liability for payment while AP invoice is generated
    5. Settle provider and receiver a/c by cash payment/receipt throgh receivable/payable invoice.
    somebody please validate my understanding, or please suggest any other possible way of doing this.
    Thanks
    Mukesh

    Hi
    You are right with your understanding
    Dina

  • Intercompany billing document setup

    Hi,
          I would like to enquire on intercompany billing document setup.
          We have customized billing type ZIV for intercompany invoice, and ZIG for intercompany credit memo.
           Is is possible to set up the cancellation for each billing type as
              - ZIG for ZIV and
              - ZIV for ZIG
    min

    Hello MIN,
    For practice & understanding or test purpose, this can be ok.
    But, in actual or real time scenario, I don't think it hold good.
    See, you said ZIG is a Credit Memo for Inter-company right?
    How you are going to use it for cancellation?
    As I know, a Credit Note or Credit Memo is a document used to adjust or rectify errors made in a sales invoice which has already been processed and sent to a customer. If you have already sent an invoice to a customer but now need to provide a credit for that invoice, you would send them a Credit Note or Credit Memo. You can think of a credit note as a "negative invoice."
    But not CANCELLATION INVOICE.
    Logically, if you see, there will be a number range issue. So, just visualise, when you have to book an actual credit note, then what you are going to do? And how is you end user and auditor is going to recognize the credit memo?
    For your your purpose of having a different cancellation doc for inter-company sales invoice and credit memo, you can create a Z Cancellation Billing Doc, say, ZIC and assign it to ZIV & ZIG billing Doc.
    Hope it assist you.
    Thanks & Regards
    JP

  • Free goods in intercompany billing

    Hi,
    I customize free goods functionality in SAP and all seems to be all right. A sales order makes a delivery with the two itens and after that the invoice have two itens one of then with condition TANN. Everything is perfect...
    But may question is: how can i do this in intercompany billing once in this kind of billing i haven´t the sales order but a purchase order?
                   Best Regards
                         João Fernandes

    Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
    This is the Limitation of setting up free goods
    Cheers

  • Credit Memo Request for intercompany sales process

    Hi Experts
    I try to find SAP notes regardsing the credit memo request for intercompany related issue but I can
    not find any nates. The customer return the goods with 2 different
    scenario :-
    -Return with credit
    -Return with replacement.
    Can anybody explain how this 2 scenario perform in the SAP
    intercompany sales process. Appreciate for your help. Thanks in advance.
    Regards,
    Jennie Tan

    Already answered
    Enter IG (internal credit memo) as the billing type for intercompany
    billing for order type RE.
    Cust-Sales/distrib-Transactions-Billing-Intercompany billing-Order types
    Intercompany billing always refers to a delivery
    Processing flow will be:
    1. Create returns request invoice receipt (with or w/out reference)
    2. Create returns delivery and goods receipt
    3. Create credit memo invoice receipt for customer for 1.
    4. Create internal credit memo for 2.
    Therefore you must make the following entries in the document flow
    for billing documents:
      Target BillType        DlvType              ItemCat
    a)    IG                  LR
    b)    IG                  LR                    REN
    Parameters for entries:
    For a) Copying requirement:  14  Dlv.-rel.header IV
          Copy item no.: x  (Check and decide yourself)
    For b)Copying requirement: 15 Dlv.rel. item IV
          Data VBRK/VBRP      : 1  Inv.split (sample)
          Billing quantity    : B
          Qty/itm val.pos/neg : +
          Pricing type        : G
    Also, refer following SAP Notes
    13160 - Returns with intercompany billing
    24756 - Credit memo requests with inter-company billing
    652007 - Reporting internal credit memos on arrival side
    11980 - Intercompany billing with order-related billing document
    164074 - Problems for internal invoices on returns
    Thanks & Regards
    JP

  • Automate creation of Intercompany billing document

    Hello All,
    We have a requirement to automate the intercompany billing document to be created whenever F2 billing document is created ( without using VF04).
    Any input regarding this will be greatly appreciated.
    Thanks,
    Nagaraju

    After goods issue has taken place, you can process the delivery for billing. You can create the billing documents just like any other billing document on the Billing screen:
    for a single billing document with the menu path Billing document ---Create.
    for several billing documents with the menu path Billing document -
    Billing due list.
    The delivery may have to be processed for billing twice.
    The delivering plant processes the delivery to create an intercompany billing document (billing document type IV) for the selling company. This company code posts invoice entry for this billing document.
    The billing document is automatically billed to the internal payer that is assigned to the sales organization. The intercompany charges that appear in the intercompany billing
    document represent the actual amount that the delivering plant is charging the sales organization.
    If the selling company is selling the goods to a customer, it processes the delivery to create an invoice for this customer. The system can take the prices from the order or determine new prices. It takes the quantity to be invoiced from the delivery.
    The billing due list for the intercompany invoice is generated after the customer invoice has been created.

Maybe you are looking for