Depending on the embodiment, the 320 cost accounting system receives the trading events sent by the 310 supply chain financial orchestration, performs the accounting of the trading events received and generates one or more trade accounting events based on the trading events received. Accounting may include the recognition of an item whose assets are converted from a first legal person to a second legal entity. Accounting can also be based on a transfer price agreed by both legal entities. The transfer price can be set as part of an agreement (also known as the “General Terms and Conditions of Purchase and Sale”) between the two legal entities. Specifically, cost accounting system 320 includes cost accounting component 321 and document accounting component 322. The cost accounting component 321 receives a first set of trading events, performs the accounting of the first set of trading events and generates one or more trade balance events based on the first set of trading events. Depending on the embodiment, the first group of trade events may include trade events used to record a.B buy-sell trade agreement (e.g., in-transit trade receipts, transit trade issues, transit trade issues, in-transit trade returns, and/or commercial sales returns). In addition, according to the embodiment shown, the cost accounting component 321 comprises a 323 intercompany trading accounting processor (“ICTA”) that is configured to process the first set of trading events, perform the accounting of the first set of trading events, and generate one or more trading accounting events based on the first set of trading events. The ICTA 323 processor can be a stand-alone component independent of a particular cost method. In this way, the ICTA 323 processor can be used as a single subcontractor in the 320 cost accounting system.
The 322 document accounting component can receive a second set of trading events, perform the accounting of the second set of trading events, and generate one or more transaction accounting events based on the second set of trading events. Depending on the embodiment, the second set of business events may include business events that are used to create internal company arrangements (e.g. B provisions for receipt of goods and/or provisions for commercial cancellations). The 322 document accounting component may also contain one or more interfaces for trading events received by the 310 Supply Chain Financial Orchestration System. The 700 user interface also includes the 720 transfer pricing option window. The Transfer Pricing Options 720 window allows a user to select one or more options to set a transfer pricing rule. One option for setting a transfer pricing rule is a pricing strategy-based transfer pricing option that defines a transfer pricing rule based on the pricing strategy. A transfer pricing rule based on the pricing strategy calculates a transfer price based on a pricing strategy, where a pricing strategy is a set of one or more pricing rules that define an approach to achieving a specific objective related to the sale and pricing of products, where the specific target can be targeted at a specific price segment and/or sales situation. One or more rules can be defined in a pricing system, and the set of one or more defined rules can form a pricing strategy. Another way to define a transfer pricing rule is a transaction cost-based transfer pricing option that defines a transfer pricing rule based on transaction costs.
A transfer pricing rule based on transaction costs calculates a transfer price by applying a positive or negative mark-up to the costs incurred by a selling entity for an item or service (i.e., transaction costs). Markup can be a default markup that can be specified as a percentage. The mark-up may be an extended mark-up defined using one or more price term rules of a pricing system. A price term rule is a rule that defines how the price of an item or service can be adjusted or set. Another way to define a transfer pricing rule is a price-based transfer pricing option for source documents that defines a transfer pricing rule based on a source document. A transfer pricing rule based on source document prices calculates a transfer price by applying a positive or negative mark-up to the price of a source document, for example. B a purchase order price or a sales order price. First, a forward flow generates a cost accounting event, the 701 commercial sales issue, and a physical execution event, the 702 sales order output.
At this point in the customer shipping flow, ownership of an item associated with the customer shipping flow belongs to the shipping entity. Subsequently, ownership of the item passes to the intermediary legal entity. For example, a receiving accounting event, accrual accounting 703, is generated and two analytical accounting events, the 704 in-transit trade number and the in-transit trade receipt 705, are generated. Subsequently, ownership of the item passes to the selling legal entity. For example, a document accounting event, the 706 commercial disclosure limit, is generated, and two cost accounting events, the 707 commercial sales output and the 708 commercial transport document, are generated. A physical execution event, Customer Inbound 709, is then generated. Fig. 1-17 illustrates a block diagram of an example architecture of a Supply Chain Financial Orchestration System 1700, according to an embodiment of the invention. Depending on the embodiment, the 1700 Supply Chain Financial Orchestration System is a configurable system that manages internal business relationships between companies owned by a company, with the company typically distributed across regions. The 1700 Supply Chain Financial Orchestration System can define a type of business relationship, business rules, internal controls, regulatory compliance, and other conditions necessary for the execution, monitoring, and evaluation of business transactions arising from those relationships. Specifically, the supply chain financial orchestration system can listen to 1700 events that occur during supply chain transactions in various external source systems and identify internal transactions (.
B inter-transaction transactions and intra-company transactions) based on predefined business relationships. Once internal transactions are identified, the Supply Chain Financial Orchestration System 1700 can create the necessary accounting and documentation that must be generated for internal transactions in accordance with the business rules defined in the 1700 Supply Chain Financial Orchestration System. FIG. Fig. 1-3 illustrates an example of integration of a supply chain financial orchestration system 310 with a cost accounting system 320, according to an embodiment of the invention. Depending on one embodiment, one or more legal/business entities can be defined as entities for a supply chain financial orchestration flow within the 310 supply chain financial orchestration system. A supply chain financial orchestration flow defines a business relationship between a first entity and a second entity. The business relationship can be a business-to-business business, and the first unit can be a profit center business unit of a first legal entity, and the second unit can be a profit center business unit of a second legal entity. Alternatively, the business relationship can be an intra-company business, and the first unit can be a profit center business unit of a legal entity, and the second unit can be a profit center business unit of the same legal entity. An example of the supply chain financial orchestration flow is given below in collaboration with ABB. 1-16, and the example architecture of a supply chain financial orchestration system is described below in collaboration with ABB. 1 to 17 described.
In addition, one or more terms and/or conditions for the supply chain financial orchestration flow can be defined in the 310 supply chain financial orchestration system. These terms and conditions may include documentation and accounting rules that may define one or more tasks to be performed in response to an event. In addition, those conditions may include transfer pricing rules that may define a transfer price to be used in a transaction between one or more units of the financial orchestration flow of the supply chain. .