Transaction settlement method between associated companies in group
Through SAP ABAP development language, the settlement process of related transactions between companies is automated, which solves the problems of cumbersome operations and inconsistent data in the existing technology, improves efficiency and accuracy, simplifies multi-department collaboration, and expands the scope of project management.
Patent Information
- Application Number
- CN202410990158.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-08
AI Technical Summary
When handling service-related transactions, existing project management software and inter-company related transactions, the operation is cumbersome and easily leads to data inconsistency, which increases audit risks and additional reconciliation workload, affecting project execution efficiency.
Using SAP ABAP development language, the settlement process of related transactions is simplified by analyzing information from the contract, automatically creating sales orders and purchasing orders, calculating payment amounts, and automatically confirming service costs and invoices.
It improves project and settlement execution efficiency, reduces manual operation errors, reduces communication complexity in multiple departments, expands the breadth of project management, and ensures data accuracy and transparency.
Smart Images

Figure CN118917952A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of SAP data interaction, and in particular to a transaction settlement method between associated companies within a group. Background Art
[0002] After years of development, the theory of project management has summarized several methodologies and frameworks, which mainly include the Waterfall Model for traditional engineering and construction industries, Agile Methods and Scrum methods for information technology and Internet industries, PRINCE2 methods for consulting industries, and Incremental Methods for marketing industries.
[0003] Project management software developed by major software vendors for these methodologies has been very mature at home and abroad. For example, Microsoft's Microsoft Project is suitable for large and complex projects and provides traditional resource management, schedule planning, budget management and other functions. Asana's cloud-based Asana is an intuitive and easy-to-use project management tool that emphasizes team collaboration and task allocation. Atlassian's Jira is suitable for software development teams and supports agile development and SCRUM framework. These project management software implement project management methodologies and frameworks from different perspectives.
[0004] On the other hand, with the continuous development of the national economy, group-type enterprises continue to emerge and grow. For different companies in the same group, the economic activities between them are called inter-company related transactions. At present, the mainstream software that supports inter-company related transactions includes SAP (Systems, Applications & Products in Data Processing, SAP) ERP (S4HANA) and Oracle ERP Cloud, which integrate finance and business.
[0005] However, in practice, no matter which project management software and inter-company transaction software are used, if it involves project management and settlement of inter-company transaction of services, it often requires many cumbersome processes and transaction operations to complete. For the same business, the buyer and the seller need to perform a series of transaction operations in the system respectively: sales order creation (purchase order creation), project execution, sales invoicing (service confirmation), invoice confirmation (clearing) and payment, etc., which involve multiple manual confirmation steps of multiple departments. This not only affects the execution efficiency of the project, but may also cause inconsistency in the settlement amount due to manual errors, such as inconsistency in costs (income) between buyers and sellers, thereby increasing additional reconciliation workload and potential audit risks. Summary of the invention
[0006] In order to solve the above problems, the present invention proposes a transaction settlement method between related companies within a group, which takes into account the advantages of high efficiency and low error rate.
[0007] The present invention proposes a transaction settlement method between affiliated companies within a group, which is implemented using the SAP ABAP development language and includes the following steps:
[0008] S1. Parse the contract information from the contract into the internal form;
[0009] S2. extracting structured data from the internal form;
[0010] S3. Calling the first program to automatically create a sales order and a purchase order based on the extracted structured data;
[0011] S4. Calculate the payment amount according to the time agreed in the contract or the completion of the task;
[0012] S5. Based on the payment amount, the second program is called to automatically confirm the service cost and internal sales order invoicing;
[0013] S6. Call the third program to automatically confirm and clear the invoice;
[0014] S7. The buyer creates a payment proposal and makes payment.
[0015] Furthermore, the step S4 also includes performing work time management or milestone management according to the contract type.
[0016] Furthermore, step S4 includes: if the contract type is priced by working hours, the contract amount is calculated every other month; if the contract type is priced by task, the contract amount is calculated based on the completion of milestone nodes.
[0017] Furthermore, if the contract type in step S4 is priced by working hours, the following steps are included:
[0018] S401, perform work time management to form work time files, and synchronize the data of the work time files to the cat2 and cat5 time sheets of the SAP enterprise management system;
[0019] S402. Automatically run a custom job at the end of each month: including calculating the payment amount for the month based on the seller's employees' reported working hours for the month multiplied by the personnel rate.
[0020] Furthermore, if the contract type in step S4 is based on task pricing, the following steps are included:
[0021] S411, assign internal project codes and automatically create subcontracted internal projects and contract milestone tasks in the project plan;
[0022] S412. In the project plan, the internal project code is associated with the external project number of the buyer in the internal form;
[0023] S413, perform milestone management to form milestone files, and synchronize milestone progress data to the cj20n project builder of the SAP enterprise management system;
[0024] S414. When the milestone node of the internal project is actually completed, the fourth program is called to calculate the payment amount by multiplying the payment ratio after the milestone node is completed in the contract by the contract amount.
[0025] Furthermore, the step S4 is to transfer data by calling the webservice soap interface, including: transferring time data of the working time file by calling the webservice soap interface in step S401; or transferring milestone progress data of the milestone file by calling the webservice soap interface in step S413.
[0026] Furthermore, the step S4 also includes project release after performing work time management or milestone management.
[0027] Furthermore, the contract in step S1 is an electronic contract in PDF format, and the OCR interface is called through an HTTP RESTful request to parse the json data containing the contract information generated by the OCR interface into a form.
[0028] Furthermore, the internal table includes at least the following information: contract type, contract name, contract notes, buyer, seller, contract date, outsourcing project number, tax rate and total contract price; and at least one of the internal table rate table information and the internal table milestone table information.
[0029] Furthermore, the step S2 also includes: extracting different structured data according to different contract types in the internal form.
[0030] Furthermore, the step S3 includes: running a verification subroutine to ensure that the amounts and tax rates of the sales order and the purchase order are consistent, and if they are inconsistent, deleting the sales order and the purchase order.
[0031] Furthermore, the step S5 further includes:
[0032] Run the verification subroutine to ensure that the amounts and tax rates of both parties are consistent. If they are inconsistent, the service confirmation document and the billing document will be offset.
[0033] The present invention has the following beneficial effects:
[0034] It has opened up the connectivity and integration of different companies within the same group in service-related related transactions, so that the relevant executors of the project only need to focus on the task itself, without having to pay too much attention to whether the project is a related transaction. The tedious settlement process of related transactions can be automatically handled by the system, thereby improving the execution efficiency of the project and settlement.
[0035] The system simplifies the tedious operations of related-party transactions between companies. Based on the contract information of related-party transactions, the system automatically checks and creates sales orders and purchase orders. While ensuring data consistency and transparency, it avoids the possibility of errors caused by manual operations and improves efficiency.
[0036] The system simplifies the tedious operations of inter-company related transactions. During the execution of the project, the system automatically checks and confirms the service costs and invoicing documents. While ensuring data consistency and transparency, it avoids the possibility of errors caused by manual operations and improves efficiency.
[0037] It has automated the steps in multiple links and simplified multiple operations of the marketing, procurement, engineering, and finance departments, thereby reducing the complexity of communication and collaboration among multiple departments.
[0038] The automated settlement processing of related transactions involved extends the breadth of project management from early contract creation and mid-term project execution to late project settlement, expanding the breadth of project management involved in existing technologies.
[0039] Integrated project management conducts project management activities from the perspective of the group enterprise, consolidating the depth of milestone management and work time management in the existing technology when different companies within the same group are involved in related transactions. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 It is a traditional service-type inter-company related transaction flow chart;
[0041] Figure 2 is a schematic flow chart of the method;
[0042] Figure 3 It is a detailed logic diagram of this method;
[0043] Figure 4 It is the work time management flow chart of this method;
[0044] Figure 5 It is the milestone (progress) management flow chart of this method. DETAILED DESCRIPTION
[0045] The transaction settlement method between affiliated companies within a group proposed by the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.
[0046] like Figure 1 As shown in the figure, an example of the traditional transaction settlement method between related companies within a group is shown. The main methods are as follows:
[0047] 1) The buyer and seller within the group create sales orders (seller's marketing department) and purchase orders (buyer's purchasing department) respectively based on the signed related-party transaction contract.
[0048] 2) The seller’s engineering department creates subcontracted internal projects and performs internal project management.
[0049] 3) The seller’s marketing department communicates with the seller’s engineering department and notifies the buyer’s procurement department to confirm actual results as needed based on the progress of internal projects.
[0050] 4) The buyer's purchasing department communicates with the buyer's project manager and confirms the cost of the purchase order based on the actual results, and then notifies the seller's marketing department to invoice based on this amount.
[0051] 5) After the seller's marketing department completes the invoicing based on the sales order, it sends the invoice voucher to the buyer's purchasing department.
[0052] 6) The buyer's purchasing department confirms and clears the invoice based on the seller's invoice voucher and generates a clearing voucher.
[0053] 7) The buyer's finance department runs the payment proposal based on the clearing voucher and makes the payment.
[0054] The traditional method requires multiple departments on both sides of the transaction to manually handle multiple transactions, which is cumbersome. In addition, since it is a manual operation, it is possible to cause inconsistency in the data between the buyer and the seller. For example, the amount and tax rate of the sales order in step 1) are inconsistent with the amount and tax rate of the purchase order. In step 4), the purchase order amount confirmed by the buyer is inconsistent with the invoice amount issued by the seller. In addition, a lot of communication time is required. For example, in steps 3 and 4), the buyer and seller (involving multiple departments) need to communicate and confirm the actual results and progress of the internal project offline and reach an agreement.
[0055] The purpose of the present invention is to overcome the defects of traditional methods and improve execution efficiency and ensure data consistency by proposing an automated method and settlement procedure. Figure 2 , 3 As shown, the present invention proposes a transaction settlement method between affiliated companies within a group, which is implemented using the SAP ABAP (Advanced Business Application Programming) development language and specifically includes the following steps:
[0056] S1. Parse the contract information from the contract into an internal form, wherein the contract is an electronic contract in PDF format, and call the OCR interface through an HTTP RESTful request to parse the json data containing the contract information generated by the OCR interface into the form.
[0057] S2. extracting structured data from the inner form. Due to different contract types, the extracted structured data is also different, that is, different structured data is extracted according to different contract types in the inner form.
[0058] S3. Based on the extracted structured data, the first program is called to automatically create a sales order and a purchase order; the first program may be a custom BAPI function that can exchange data with the SAP management system, and the first program may recognize the structured data to automatically create a sales order and a purchase order. After the sales order and the purchase order are created, the amount and tax rate of the two may be checked. Specifically, the verification subprogram may be run to ensure that the amount and tax rate of the sales order and the purchase order are consistent. If they are inconsistent, the sales order and the purchase order are deleted.
[0059] S4. Calculate the payment amount according to the time agreed in the contract or the completion of the task. The payment amount calculation process can be roughly divided into hourly pricing and task-based pricing according to different contract types.
[0060] If the contract type is priced by working hours, the contract amount is calculated every month; if the contract type is priced by task, the contract amount is calculated based on the completion of milestone nodes. Specifically, if the contract type is priced by working hours, the following steps are included:
[0061] S401, perform work time management to form a work time file, and synchronize the data of the work time file to the cat2 and cat5 timetables of the SAP enterprise management system. The cat2 and cat5 timetables can be called by the SAP enterprise management system;
[0062] S402. Automatically run a custom job at the end of each month: including calculating the payment amount for the month based on the seller's employees' reported working hours for the month multiplied by the personnel rate.
[0063] If the contract type is task-based pricing, the following steps are included:
[0064] S411, assign internal project codes and automatically create subcontracted internal projects and contract milestone tasks in the project plan;
[0065] S412. In the project plan, the internal project is associated with the external project of the buyer in the internal form, that is, the internal project code is associated with the external project number;
[0066] S413, perform milestone management to form milestone files, and synchronize milestone progress data to the cj20n project builder of the SAP enterprise management system;
[0067] S414. When the milestone node of the internal project is actually completed, the fourth program is called to calculate the payment amount by multiplying the payment ratio after the milestone node is completed in the contract by the contract amount.
[0068] It should be noted that as a manager, time management and milestone management need to be managed by the corresponding project leader and form management documents, such as time documents or milestone documents. After determining the contract type, time management and milestone management should be used as integrated project management. Figure 4 As shown, in time management, the project manager is the actual person in charge of the project. The project manager prepares the project plan, assigns tasks, and releases the project. After receiving the task, the project team members fill in and submit the time for approval by the project manager. When it is a contract priced by task, the employee submits the time. If it is an internal project (sub-project), it is approved by the seller's project manager, and if it is an external project (parent project), it is approved by the buyer's project manager. When it is a contract priced by time, the specific buyer's project number is not specified in the contract. The project manager of the buyer's company can assign tasks to the employees of the seller's company, and then follow the above time management process. After the time is approved, a time file can be formed, which can be used to synchronize to the cat2 and cat5 timetables.
[0069] like Figure 5 As shown, in milestone management, the seller's project manager is the actual person in charge of the internal project (sub-project). The seller's project manager maintains the actual completion date of the milestone and publishes the internal project (sub-project) to release the project. The buyer's project manager is the actual person in charge of the external project (parent project). The buyer's project manager approves the milestone of the sub-project. After the approval is completed, a milestone file is formed that can be synchronized to the cj20n project builder.
[0070] S5. Based on the payment amount, the second program is called to automatically confirm the service cost and the internal sales order invoice. This step also includes running the verification subprogram to ensure that the amount and tax rate of both parties are consistent. If they are inconsistent, the service confirmation voucher and the invoice voucher are offset.
[0071] S6. Call the third program to automatically confirm and clear the invoice;
[0072] S7. The buyer creates a payment proposal and makes payment.
[0073] Wherein, the step S4 is to transfer data by calling the webservice soap interface, including: in step S401, the time data of the working time file is transferred by calling the webservice soap interface; or in step S413, the milestone progress data of the milestone file is transferred by calling the webservice soap interface. The webservice soap interface is an interface protocol, and its implementation is often based on the SOAP protocol, using XML as the transmission format, and the returned result is also in XML format. By parsing the XML format data, the data of the working time file is synchronized to the cat2 and cat5 timetables, or the milestone progress data is synchronized to the cj20n project constructor.
[0074] Furthermore, the internal table includes at least the following information: contract type, contract name, contract notes, buyer, seller, contract date, outsourcing project number, tax rate and total contract price; and at least one of the internal table rate table information and the internal table milestone table information.
[0075] The processing process of the BAPI function zbapi_createSOPO() run by the first program can be roughly as follows:
[0076] 1) Input parameters:
[0077] Internal form header information: contract type, contract name, contract remarks, buyer, seller, contract date, outsourcing project number, tax rate and total contract price;
[0078] Internal table rate table information: rate type and personnel rate;
[0079] Internal form milestone table information: milestone name, delivery date and delivery price;
[0080] 2) Processing:
[0081] Find the corresponding service material in the material master data based on the tax rate;
[0082] Sales order: the buyer is mapped to the customer number, and the seller is mapped to the company code, sales organization, and plant;
[0083] Assign sales order header information (sales order type, customer number, company code, sales organization, sales group, contract name and contract remarks);
[0084] Assign sales order line item information (service material, contract price and tax rate);
[0085] Assign invoice schedule information (milestone name, delivery date and price) or (rate type and personnel rate);
[0086] Purchase order: Map payment terms type based on contract type
[0087] The buyer is mapped to the company code, purchasing organization and plant; the seller is mapped to the supplier number;
[0088] Assign purchase order header information (purchase order type, supplier number, company code, purchasing organization, purchasing group, order name, order remarks and condition type);
[0089] Assign purchase order line item information (service material, contract price and tax rate);
[0090] Assign service line item information (milestone name, delivery date, price) or (rate type and personnel rate) in the purchase order line item;
[0091] Commit the database.
[0092] 3) Output parameters: return result (success or failure), return sales order number line item number, purchase order number line item number, return message (details of error reason).
[0093] The custom BAPI function zbapi_confirmcost_createinvoice() run by the second program generally includes the following processes:
[0094] 1) Input parameters:
[0095] Sales order, sales order line item; purchase order, purchase order line item; amount, tax rate
[0096] 2) Processing:
[0097] Find the supplier number and company code of the purchase order based on the purchase order number;
[0098] Build service confirmation credentials:
[0099] Header: document type, posting date, company code;
[0100] Debit line item: production cost and manufacturing overhead account, amount;
[0101] Credit line item: Estimated account payable, amount;
[0102] Find the customer number and company code of the sales order based on the sales order;
[0103] Construct an invoice document:
[0104] Header: document type, invoice date, posting date, company code;
[0105] Debit line item: customer receivable account, amount;
[0106] Credit line item: Taxes payable output tax account, amount (calculated based on tax rate);
[0107] Credit line item: main business income account, amount;
[0108] Amount of customer receivables = amount of output tax payable + amount of main business income
[0109] Commit the database.
[0110] 3) Output parameters: return result (success or failure), return service confirmation voucher number, invoice voucher number, return message (details of error reason).
[0111] The custom BAPI function zbapi_confirminvoice() run by the third program generally includes the following processes:
[0112] 1) Input parameters:
[0113] Service confirmation voucher number, amount and tax rate;
[0114] 2) Processing:
[0115] Find the supplier number and company code of the purchase order based on the service confirmation document number;
[0116] Build invoice confirmation document: document type, invoice date, posting date, service class, amount, tax rate, purchase order number, purchase order line item number and company code;
[0117] Construct clearing document:
[0118] Header: document type, invoice date, posting date, company code and invoice confirmation document number;
[0119] Debit line item: supplier number control account, amount;
[0120] Debit line item: input tax account payable, amount (calculated based on tax rate);
[0121] Debit line item: supplier payable account, amount;
[0122] Supplier number unified account amount = Tax payable input tax account amount + supplier payable account amount;
[0123] Commit the database.
[0124] 3) Output parameters: return result (success or failure), return invoice confirmation voucher number, clearing voucher number, return message (details of error reason).
[0125] The above method connects the entire process of contract creation, project execution, and amount settlement end-to-end, and automatically completes the creation of sales orders, purchase orders, and internal projects. Specifically, it means that the process is completely connected from the starting point to the end point, ensuring that all links in the entire process can be smoothly connected and interacted. Specifically, the entire business process of contract creation, project execution, and amount settlement has been completely connected, so that these links can be seamlessly connected and data can flow smoothly. Through integration with project time and milestone management, invoicing and invoice confirmation are automatically completed, reducing manual operation steps and improving data transparency and accuracy.
[0126] Compared with the prior art, the present invention has the following beneficial effects:
[0127] It has opened up the connectivity and integration of different companies within the same group in service-related related transactions, so that the relevant executors of the project only need to focus on the task itself, without having to pay too much attention to whether the project is a related transaction. The tedious settlement process of related transactions can be automatically handled by the system, thereby improving the execution efficiency of the project and settlement.
[0128] The system simplifies the tedious operations of related-party transactions between companies. Based on the contract information of related-party transactions, the system automatically checks and creates sales orders and purchase orders. While ensuring data consistency and transparency, it avoids the possibility of errors caused by manual operations and improves efficiency.
[0129] The system simplifies the tedious operations of inter-company related transactions. During the execution of the project, the system automatically checks and confirms the service costs and invoicing documents. While ensuring data consistency and transparency, it avoids the possibility of errors caused by manual operations and improves efficiency.
[0130] It has automated the steps in multiple links and simplified multiple operations of the marketing, procurement, engineering, and finance departments, thereby reducing the complexity of communication and collaboration among multiple departments.
[0131] The automated settlement processing of related transactions involved extends the breadth of project management from early contract creation and mid-term project execution to late project settlement, expanding the breadth of project management involved in existing technologies.
[0132] Integrated project management conducts project management activities from the perspective of the group enterprise, consolidating the depth of milestone management and work time management in the existing technology when different companies within the same group are involved in related transactions.
[0133] Although the content of the present invention has been described in detail through the above preferred embodiments, it should be appreciated that the above description should not be considered as a limitation of the present invention. After reading the above content, it will be apparent to those skilled in the art that various modifications and substitutions of the present invention will occur. Therefore, the protection scope of the present invention should be limited by the appended claims.
Claims
1. A method of settling transactions between affiliated companies within a group. It is characterized in that The transaction settlement method is implemented using the SAPABAP development language and includes the following steps: S1. Parse the contract information from the contract into the internal form; S2. extracting structured data from the internal form; S3. Calling the first program to automatically create a sales order and a purchase order based on the extracted structured data; S4. Calculate the payment amount according to the time agreed in the contract or the completion of the task; S5. Based on the payment amount, the second program is called to automatically confirm the service cost and internal sales order invoicing; S6. Call the third program to automatically confirm and clear the invoice; S7. The buyer creates a payment proposal and makes payment.
2. The transaction settlement method between affiliated companies within a group as claimed in claim 1, It is characterized in that The step S4 also includes performing work time management or milestone management according to the contract type.
3. The transaction settlement method between affiliated companies within a group as claimed in claim 2, It is characterized in that The step S4 includes: if the contract type is priced by working hours, the contract amount is calculated every month; if the contract type is priced by task, the contract amount is calculated based on the completion of milestone nodes.
4. The transaction settlement method between related companies within a group as claimed in claim 3, It is characterized in that If the contract type in step S4 is priced by working hours, the following steps are included: S401, perform work time management to form work time files, and synchronize the data of the work time files to the cat2 and cat5 time sheets of the SAP enterprise management system; S402. Automatically run a custom job at the end of each month: including calculating the payment amount for the month based on the seller's employees' reported working hours for the month multiplied by the personnel rate.
5. The transaction settlement method between affiliated companies within a group as claimed in claim 3, It is characterized in that If the contract type in step S4 is task-based pricing, the following steps are included: S411, assign internal project codes and automatically create subcontracted internal projects and contract milestone tasks in the project plan; S412. In the project plan, the internal project code is associated with the external project number of the buyer in the internal form; S413, perform milestone management to form milestone files, and synchronize milestone progress data to the cj20n project builder of the SAP enterprise management system; S414. When the milestone node of the internal project is actually completed, the fourth program is called to calculate the payment amount by multiplying the payment ratio after the milestone node is completed in the contract by the contract amount.
6. The transaction settlement method between affiliated companies within a group as claimed in claim 4 or 5, It is characterized in that The step S4 is to transfer data by calling the webservice soap interface, including: in step S401, transferring time data of the working time file by calling the webservice soap interface; or in step S413, transferring milestone progress data of the milestone file by calling the webservice soap interface.
7. The transaction settlement method between affiliated companies within a group as claimed in claim 4 or 5, It is characterized in that The step S4 also includes project release after performing work time management or milestone management.
8. The transaction settlement method between affiliated companies within a group as claimed in claim 1, It is characterized in that The contract in step S1 is an electronic contract in PDF format, and the OCR interface is called through an HTTP RESTful request to parse the json data containing the contract information generated by the OCR interface into a form.
9. The transaction settlement method between affiliated companies within a group as claimed in claim 1, It is characterized in that The internal form includes at least the following information: contract type, contract name, contract notes, buyer, seller, contract date, outsourcing project number, tax rate and total contract price; and at least one of internal table rate table information and internal table milestone table information.
10. The transaction settlement method between related companies within a group as claimed in claim 1, It is characterized in that The step S2 also includes: extracting different structured data according to different contract types in the internal form.
11. The transaction settlement method between related companies within a group as claimed in claim 1, It is characterized in that The step S3 includes: running a verification subroutine to ensure that the amounts and tax rates of the sales order and the purchase order are consistent, and if they are inconsistent, deleting the sales order and the purchase order.
12. The transaction settlement method between affiliated companies within a group as claimed in claim 1, It is characterized in that The step S5 further comprises: Run the verification subroutine to ensure that the amounts and tax rates of both parties are consistent. If they are inconsistent, the service confirmation document and the billing document will be offset.
