This topic provides examples of intercompany organizations with different options. In these scenarios, you choose to track intercompany compensation for companies with values of 3000 and 4000 to separate the intercompany accounts. To do this, you configure specific rules at the value level of the primary balancing segment. A chart of accounts rule is created for all other intra-group activities. Select a type of conversion rate to use when transferring foreign currency intercompany transactions to general ledgers, receivables, and accounts payable. In this example, Vision Corporation has a legal entity, Vision Operations Legal Entity, which is connected to multiple intercompany organizations within the company structure. In the following configuration, the Vision Operations intercompany organization provides assets to the Vision Administration intercompany organization, and in other circumstances, Vision Administration provides services for Vision Operations. The corporation requires that each of these intercompany organizations be able to invoice the other and enter a statement payable received from the other intercompany organization. Uses log import to process intercompany mappings when you select posts for unique non-fiction account creations.
Submit the Generate Intercompany Mappings process to create intercompany transactions. If you need invoices for your allocations, choose a type of intercompany transaction that requires invoicing so that intercompany transactions are routed to receivables for invoice generation. You cannot resubmit rejected intercompany transactions. However, you can copy, edit, and resubmit them in a new batch. Approve transactions that need to be approved manually. As soon as the transactions are in the “Approved” status, you execute the corresponding transfer processes: Customers and suppliers for intercompany invoicing are derived from the business-to-business customer and supplier missions. You can assign a legal entity to a customer account or a vendor, or both. Only one customer account and one provider can be assigned to each legal entity. During the accounting process, the general ledger identifies unbalanced transactions such as the one shown above and automatically creates additional intercompany balance entries. Then the invoice and balance entries are recorded. Intercompany uses the transaction type, the vendor rights unit, the recipient`s legal entity, the value of the primary balance segment of the first vendor distribution, and the value of the primary balancing segment of the first recipient distribution to determine which rule to apply.
Intercompany then uses the rule segment and balancing values of the first vendor distribution to create the combination of intercompany customer accounts for the vendor side of the transaction. Similarly, Intercompany creates the intercompany liability account for the recipient side of the transaction, based on the recipient`s first distribution account. Locate the appropriate batch. Lots in the Submitted state with all transactions in the Received or Sent state can be removed. Allow recipients to reject intercompany transactions. This topic provides examples of additional options for intercompany balancing and clearing, system requirements, and logging before and after balancing. This topic provides examples of intercompany accounting rules and the generated intercompany accounting lines. These rules are used to generate the accounts necessary for the balance of logs that are unbalanced by legal entities or primary balance segment values. Set intercompany system options to configure enterprise-level intercompany processing rules based on the specific needs of your business. That is a good thing. Select the type of transactions grouped and identified by the type of intercompany transaction. 1.
Reverse lot (allowed only if all transactions in the lot are completed; The lot has already been cancelled; Batch was not created from an inversion) The same rules are also used to generate the intercompany customer account and the intercompany supplier account of the transactions entered in the intercompany module. The attributes of the transaction type determine how the intercompany transaction is processed. You can use a transaction type to define whether a transaction is transferred directly to the general ledger or whether billing for receivables and accounts payable is required. The transaction type also determines whether a transaction needs to be approved manually. You can have an intercompany calendar separate from the general ledger calendar. This ensures that the opening and closing of intercompany periods can be controlled separately from the general ledger calendar. You can restrict the creation of intercompany transactions by using the intercompany calendar to close periods by task type. Like what.
B you can prevent users from creating intercompany sales transactions beyond the 20th of each month by closing the period for this type of transaction on the 20th, but leaving the period open for other types of transactions until the 25th of the month. . . .
