Invoice generation method and computing device

Abstract

The application provides a method for generating an invoice to be received and a computing device, the method comprising: determining an invoice allocation file, the invoice allocation file comprising contract information of at least one first order contract and cumulative trigger identification of each first order contract, the first order contract being an order contract that needs to be managed by the invoice to be received, and the cumulative trigger identification being all triggered or not all triggered; querying a second order contract with the cumulative trigger identification not all triggered according to the cumulative trigger identification of each first order contract in the invoice allocation file; and generating the invoice to be received of a current accounting period for the second order contract in the case that the second order contract meets the entry condition of the current accounting period.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method and computing device for generating accounts receivable invoices. Background Technology

[0002] In the financial field, issuing accounts receivable invoices is a common business requirement. An accounts receivable invoice is a bill issued by a company to a customer after the sale of products or services, requesting payment. It is a formal invoice generated during the sales process and is used to record the amount due from the customer. Specifically, an accounts receivable invoice can list detailed information about the products or services sold, such as the quantity, unit price, total price, and payment terms.

[0003] Currently, accounts receivable invoices suffer from problems such as inaccurate invoice amounts and low invoice generation efficiency. Summary of the Invention

[0004] This application provides a method and computing device for generating accounts receivable invoices.

[0005] According to a first aspect of the embodiments of this application, a method for generating accounts receivable invoices is provided, including: Determine the invoice allocation file, which includes contract information for at least one first order contract and cumulative trigger identifiers for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management, and the cumulative trigger identifier is whether all have been triggered or not. Based on the cumulative trigger flags of each first order contract in the invoice allocation file, query the second order contracts whose cumulative trigger flags have not been fully triggered; If the second order contract meets the accounting conditions for the current accounting period, generate an invoice for the current accounting period for the second order contract.

[0006] In this embodiment, the cumulative triggering of each first order contract is managed through an invoice allocation file, and a cumulative triggering identifier is used to determine whether all order contracts have been triggered. By accurately filtering second order contracts with cumulative triggering identifiers that have not been fully triggered from the invoice allocation file, precise filtering of accounts receivable invoice generation objects is achieved. Furthermore, for the second order contracts, a check is performed to see if they meet the accounting period's posting conditions. This posting period check makes the invoice generation process more standardized, ensuring the compliance and smoothness of the invoice process. This effectively avoids the problem of missed or incorrect invoices. The entire process can be completed through document scanning and posting condition checks, improving the accuracy, relevance, and efficiency of accounts receivable invoices.

[0007] In one embodiment of the first aspect, generating an invoice for the current accounting period for a second order contract includes: Obtain the current accounting period and service cycle of the second order contract to calculate the accounting percentage and accounting amount of the current accounting period relative to the service cycle; Based on the amount received, generate an invoice for the second order contract in the current accounting period.

[0008] In this embodiment of the application, by obtaining the current accounting period and service cycle of the second order contract, the accounting period is used to calculate the accounting ratio and the accounting amount of the current accounting period to the service cycle. This achieves refined accounting by allocating the accounting amount according to the service cycle, which not only ensures that the accounting amount is accurately matched with the current service progress, but also meets the accounting requirements, avoids phenomena such as one-time accounting or uneven allocation, and improves the accuracy of the amount of accounts receivable invoices.

[0009] In one embodiment of the first aspect, generating an invoice for the second order contract in the current accounting period based on the recorded amount includes: In the event of an adjustment to the service period of the second order contract, the new amount recorded for the second order contract in the current accounting period shall be obtained; Query the original recorded amount of the second order contract in the current accounting period, and calculate the difference between the new recorded amount and the original recorded amount; If the difference is greater than or equal to 0, the invoice creation program is invoked to create a positive invoice corresponding to the recorded amount. If the difference is less than 0, the invoice creation program is invoked to create a credit invoice corresponding to the recorded amount.

[0010] In this embodiment, when the service period of an order contract is adjusted, the new recorded amount of the second order contract in the current accounting period can be obtained, as well as the original recorded amount of the second order contract in the current accounting period can be queried. This allows for the acquisition of recorded amounts before and after the service period adjustment, calculation of the difference between the two recorded amounts, and confirmation of the specific type of invoice by the sign of the recorded amount. For scenarios where the recorded amount is greater than or equal to 0, a positive invoice can be generated. For scenarios where the recorded amount is less than 0, a credit invoice can be generated. When adjusting the service period, the type of invoice to be generated can be automatically determined based on the difference in recorded amounts before and after the adjustment, and the invoice can be automatically generated, improving the efficiency and accuracy of invoice generation.

[0011] In one embodiment of the first aspect, the invoice allocation file further includes: a cumulative trigger ratio; after generating an accounts receivable invoice for the second order contract in the current accounting period based on the recorded amount, the method further includes: Increase the cumulative trigger ratio of the second order contract by the accounting percentage; If the cumulative trigger ratio equals 1 after increasing the revenue ratio, reset the cumulative trigger flag of the second order contract to "all triggered".

[0012] In this embodiment, a cumulative trigger ratio is also set in the invoice allocation file. The cumulative trigger ratio increases according to the accounting entry ratio when each invoice is generated. By automatically updating the cumulative trigger flag to "all triggered" when the cumulative trigger ratio reaches 1, real-time tracking and intelligent synchronization of contract performance accounting progress are achieved. This accurately reflects the cumulative accounting completion status within the contract service period, avoiding duplicate or incomplete accounting issues. It also provides a clear status basis for subsequent screening of contracts that have not been fully triggered and for advancing the generation of invoices for the remaining accounting period, ensuring the continuity and standardization of the accounting and invoice generation process, and improving the automation and accuracy of the entire financial processing process.

[0013] In one embodiment of the first aspect, obtaining the current accounting period and service cycle of the second order contract to calculate the accounting percentage of the current accounting period relative to the service cycle includes: To find the accounting period corresponding to the second order contract at the current time, obtain the current accounting period. The number of service days in the current accounting period is determined based on the start and end times of the service period and / or the last day of the current accounting period. Calculate the number of service days and the total number of days in the service period, and calculate the accounting percentage of the current accounting period in the service period.

[0014] In this embodiment, by automatically querying the current accounting period corresponding to the second order contract, and combining the start time, end time and / or the end date of the current accounting period to accurately calculate the number of service days in the current period, the accounting ratio is calculated by the ratio of service days to total days. This achieves automated and refined calculation of the accounting ratio, which avoids errors caused by manual calculation, ensures the accuracy of the ratio data, and ensures that the accounting ratio is accurately matched with the actual service performance in the current period, in accordance with the accrual basis accounting requirements, and improves the accuracy and efficiency of the entire accounting ratio calculation.

[0015] In one embodiment of the first aspect, the invoice allocation file further includes the next trigger time for each order contract; the method further includes: If the last day of the current accounting period for the second order contract is later than or equal to the next trigger time, the second order contract is determined to meet the accounting conditions for the current accounting period. After generating the accounts receivable invoice for the current accounting period for the second order contract, the following also includes: Determine the next accounting period from the current accounting period; The next trigger time for the second order contract will be reset to the last day of the next accounting period.

[0016] In this embodiment, the criterion is that the last day of the current accounting period is later than or equal to the next trigger time. This accurately determines whether the second order contract meets the accounting entry conditions for the current accounting period, thereby completing the accounting entry and automatic invoice generation. If the next accounting period is determined, the next trigger time for the second order contract is reset to the last day of the next accounting period. This achieves intelligent verification of the accounting entry timing and automated iterative setting of subsequent trigger nodes, avoiding accounting confusion or redundant entries, ensuring the accuracy of the accounting sequence. The next accounting entry for a unified order contract can be initiated without manual intervention, creating a complete cyclical link for invoice generation throughout the contract service cycle, improving invoice generation efficiency and accuracy.

[0017] In one embodiment of the first aspect, it further includes: Determine the contract trigger file, which includes contract information for at least one order contract and the trigger result for each order contract, indicating whether the trigger has been triggered or not. The first order contract that was not triggered was found in the contract trigger file. Add the first order contract to the invoice allocation file and reset the trigger result of the first order contract in the contract trigger file to "triggered".

[0018] In this embodiment, before determining the invoice allocation file, a contract trigger file is also determined. The initially collected order contracts are managed through this contract trigger file. Triggering means adding the order contract to the invoice allocation file to facilitate automatic invoice generation. The triggering results of each order contract determine whether it has been triggered. If an order contract has been triggered, it does not need to be triggered again. If an order contract has not been triggered, it needs to be added to the invoice allocation file. This ensures accurate identification of the first contract file that requires automatic invoice generation, avoiding omissions in order contract processing. The status update of the triggering results effectively ensures timely updates to the triggering status of order contracts, achieving real-time synchronization between triggering results and status, effectively preventing duplicate triggering of order contracts. This improves the completeness and processing efficiency of the automatic invoice generation process, ensures consistency between the contract triggering status and the invoice allocation process, and promotes the standardized and orderly advancement of financial processing procedures.

[0019] In one embodiment of the first aspect, determining the contract triggering file includes: Collect order contracts, add the collected order contract information to the contract trigger file, and set the trigger result of the order contracts to not be triggered.

[0020] In this embodiment, order contracts are collected automatically. By continuously incorporating contract information into a contract trigger file and setting the trigger result of newly added order contracts to "not triggered," accurate access and initialization of order contracts to the invoice allocation section is achieved. This avoids omissions and errors caused by manual data entry, ensuring the integrity and accuracy of order contracts and effectively improving the data synchronization efficiency of the financial pre-process.

[0021] In one embodiment of the first aspect, querying the contract trigger file for a first order contract whose trigger result is not triggered includes: Periodically scan the contract trigger file to retrieve the first order contract that has not been triggered. Based on the cumulative trigger flags of each first order contract in the invoice allocation file, query the second order contracts whose cumulative trigger flags have not been fully triggered, including: Once the contract triggering documents have been scanned, the invoice allocation documents are scanned to query the second order contracts whose cumulative triggering identifiers have not been fully triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation documents.

[0022] In this embodiment, contract triggering files are scanned periodically to filter out first order contracts that have not been triggered. After the scan is completed, the invoice allocation file scan is started to further filter out second order contracts whose cumulative triggering flag is not fully triggered. This achieves hierarchical and precise filtering of contracts to be credited and process-linked verification. The periodic scanning ensures timely identification of unprocessed contracts and avoids omissions, while the scanning of invoice allocation files accurately completes the filtering of second order contracts that have not been fully triggered, reducing manual intervention and improving the automation efficiency of the filtering process.

[0023] According to a second aspect of the present application, a schematic diagram of an accounts receivable invoice generation device is provided, which may include the following units: The first determining unit is used to determine the invoice allocation document. The invoice allocation document includes contract information for at least one first order contract and cumulative triggering identifiers for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management. The cumulative triggering identifier indicates whether all have been triggered or not.

[0024] The contract filtering unit is used to query second order contracts whose cumulative triggering identifiers are not all triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation file.

[0025] The invoice generation unit is used to generate an invoice for the current accounting period for the second order contract if the accounting conditions for the second order contract are met.

[0026] According to a third aspect of the embodiments of this application, a computing device is provided, including: a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program to implement any of the above-described accounts receivable invoice generation methods.

[0027] According to a fourth aspect of the embodiments of this application, a communication device is provided, including a transceiver and a processor, wherein the transceiver is used to receive or send data, and the processor is used to execute any of the accounts receivable invoice generation methods of the embodiments of this application.

[0028] According to a fifth aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, it implements any of the accounts receivable invoice generation methods.

[0029] According to a sixth aspect of the present application, a computer product is provided, comprising: a computer program that, when executed by a processor, implements the steps of any accounts receivable invoice generation method.

[0030] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0031] The above and other objects, features, and advantages of the embodiments of this application will become more apparent from the more detailed description of the embodiments in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the embodiments of this application and do not constitute a limitation on the embodiments of this application. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0032] Figure 1 The figure shows an example diagram of an accounts receivable invoice generation system according to an embodiment of this application; Figure 2 The figure shows a flowchart of an accounts receivable invoice generation method according to an embodiment of this application; Figure 3 The figure shows another flowchart of an accounts receivable invoice generation method according to an embodiment of this application; Figure 4 The figure shows another flowchart of an accounts receivable invoice generation method according to an embodiment of this application; Figure 5 The figure shows a schematic diagram of an accounts receivable invoice generation device according to an embodiment of this application; Figure 6 The figure shows a hardware block diagram of a computing device according to an embodiment of this application. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of the embodiments of this application more apparent, exemplary embodiments according to the embodiments of this application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the embodiments of this application, and not all embodiments of the embodiments of this application. It should be understood that the embodiments of this application are not limited to the exemplary embodiments described herein.

[0034] The technical solution of this application embodiment can be applied to the field of ERP (Enterprise Resource Planning). By automatically scanning documents, it triggers the automatic generation of invoices. The entire process does not require manual intervention, which greatly improves the efficiency of invoice generation.

[0035] This application embodiment retrieves order contracts that have not been fully triggered by accumulating trigger identifiers. Then, it generates accounts receivable invoices for the current accounting period.

[0036] The technical solutions of the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0037] like Figure 1 The diagram shown is an application example of an accounts receivable invoice generation system provided in an embodiment of this application. The accounts receivable invoice generation system may include: a service provider 10, a service recipient 20, and an ERP system 30.

[0038] Among them, service provider 10 can sell products or services to external parties. For example, server provider can provide server installation, relocation, upgrade and other products, and service provider can also sell AI computing power services, software or solutions, training services and other services.

[0039] Service recipient 20 can be the purchaser of products or services. After the service provider 10 and service recipient 20 have a transaction intention, they can sign an order contract. Some contract information of the order contract can be collected by the ERP system 30. The contract information of the order contract may include at least one of the following: sales information, contract number, product code, total contract amount, service period, order type, customer code, transaction currency, material code, or material description, etc.

[0040] ERP system 30 can collect contract information for orders. For example, the ERP system can collect order contracts from service provider 10, or intercept order contracts sent by service provider 10 to service recipient 20.

[0041] ERP system 30 also maintains an invoice allocation file. This file contains contract information for at least one first order contract and a cumulative trigger flag for each first order contract. The first order contract refers to the order contract requiring accounts receivable invoice management. The cumulative trigger flag indicates whether all have been triggered or not.

[0042] If the cumulative trigger flag is "All triggered," it means that all invoices for the corresponding order contract have been generated, and no further processing is needed. If the cumulative trigger flag is "Not all triggered," it means that all invoices for the contract order have not been generated, and further processing is required.

[0043] Afterwards, the ERP system 30 can query the second order contracts whose cumulative triggering identifiers are not all triggered based on the cumulative triggering identifiers of each first order contract in the invoice allocation file; if the second order contract meets the accounting conditions for the current accounting period, it can generate an accounts receivable invoice for the current accounting period for the second order contract.

[0044] like Figure 2 The diagram shown is a flowchart of an accounts receivable invoice generation method provided in an embodiment of this application. The method may include the following steps: S201. Determine the invoice allocation file. The invoice allocation file includes contract information for at least one first order contract and cumulative trigger identifiers for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management. The cumulative trigger identifier is whether all have been triggered or not.

[0045] Alternatively, the invoice allocation document can be an invoice allocation schedule. Table 1 below shows an example of an invoice allocation schedule.

[0046] Table 1

[0047] Referring to Table 1, the invoice allocation file may include: primary key ID, management unit, contract number, product code, cumulative trigger identifier, service start time, service end time, cumulative trigger ratio, and next trigger time.

[0048] The primary key ID can refer to the index of the first order contract in the invoice allocation file.

[0049] The management unit is used to distinguish the management unit ID of different services or products of the service provider. It can refer to the ID of the service provider in the contract, such as management unit 1 for providing AI training services and management unit 2 for providing server update services.

[0050] The contract number can refer to the contract code or serial number of the order contract. The product code can refer to the code of the contracted party, such as the code for server upgrade services or AI training services.

[0051] The cumulative trigger flag is used to indicate whether all flags have been triggered (not all triggered I or all triggered S).

[0052] The service start time is the start time of the service period in the order contract. The service end time is the end time of the service period in the order contract. Taking a service period from July 1, 2025 to October 20, 2026 as an example, July 1, 2025 is the service start time, and October 20, 2026 is the service end time.

[0053] The cumulative trigger ratio is the ratio of the amount of invoices already generated for the order contract to the total order amount for the service period. For example, if invoices have been generated 3 times, the ratio of 3 invoices is 58%.

[0054] The next trigger time refers to the last day of the accounting period after the same order contract generates an accounts receivable invoice this time. Taking a monthly accounting period as an example, the next trigger time is the last day of the next month. For example, if the next accounting period is August, then the next trigger time is August 30, 2025.

[0055] The first order contract may include order contracts selected from the contract trigger file, and the first order contract requires accounts receivable invoice management.

[0056] S202. Based on the cumulative triggering identifiers of each first order contract in the invoice allocation file, query the second order contracts whose cumulative triggering identifiers are not all triggered.

[0057] If the cumulative trigger flag for the first order contract is set to "all triggered", then the first order contract will no longer be required to generate an invoice.

[0058] If the cumulative trigger flag for the first order contract is not fully triggered, then the first order contract becomes the second order contract.

[0059] S203. If the second order contract meets the accounting conditions for the current accounting period, generate an invoice for the current accounting period for the second order contract.

[0060] Optionally, it may also include: whether the second order contract meets the accounting conditions for the current accounting period may refer to whether the second order contract has been recorded in the current accounting period, or whether an invoice for accounts receivable for the current accounting period has been generated.

[0061] For example, if the second order contract has been recorded or an invoice has been generated in the current accounting period, then the second order contract is determined not to meet the recording criteria for the current accounting period. If the second order contract has not been recorded or an invoice has not been generated in the current accounting period, then the second order contract is determined to meet the recording criteria for the current accounting period.

[0062] The current accounting period can refer to the accounting period at the time the invoice allocation document was triggered. For example, the current accounting period can be determined based on the current query time. Specifically, the accounting period is the cycle in which the invoice is generated, typically one month. However, the accounting period needs to be divided according to the service time of the order contract. If it is less than one month, the start time of the service cycle or the end time of the service cycle will be used as the start time of the accounting period, or the end time of the service cycle will be used as the end time of the accounting period. For example, if the current query time is October 20, 2025, and the service cycle is from July 1, 2025 to October 20, 2026, then the current accounting period is from October 1, 2025 to October 31, 2025. If the current query time is October 2, 2026, then the current accounting period is from October 1, 2026 to October 20, 2026.

[0063] Following the invoices receivable for the current accounting period, the process also includes: sending the invoices receivable for the current accounting period, combined with the contract information of the second order contract, to the terminal corresponding to the service recipient of the second order contract, so that the service recipient can view them in a timely manner. This allows for actions such as making payments or transfers based on the accounts receivable / amount. Alternatively, the corresponding amount can be directly obtained from the bank account provided by the service recipient based on the invoice amount, and used as the recorded amount.

[0064] In this embodiment, the cumulative triggering of each first order contract is managed through an invoice allocation file, and a cumulative triggering identifier is used to determine whether all order contracts have been triggered. By accurately filtering second order contracts with cumulative triggering identifiers that have not been fully triggered from the invoice allocation file, precise filtering of accounts receivable invoice generation objects is achieved. Furthermore, for the second order contracts, a check is performed to see if they meet the accounting period's posting conditions. This posting period check makes the invoice generation process more standardized, ensuring the compliance and smoothness of the invoice process. This effectively avoids the problem of missed or incorrect invoices. The entire process can be completed through document scanning and posting condition checks, without manual intervention, improving the accuracy, relevance, and efficiency of accounts receivable invoices.

[0065] like Figure 3 The diagram shown is a flowchart of an accounts receivable invoice generation method provided in an embodiment of this application. The method may include the following steps: S301. Determine the contract triggering document. The contract triggering document includes the contract information of at least one order contract and the triggering result of each order contract, wherein the triggering result is either triggered or not triggered.

[0066] Optionally, the contract trigger file can be a contract trigger table. Listing 2 below shows an example of a contract trigger table.

[0067] Table 2

[0068] Referring to Table 2, the contract trigger table may include keys such as: Trigger instruction primary key ID, Trigger instruction ID, Management unit, Contract number, Product code, Cumulative trigger amount, Service start time, Service end time, Billing date, Trigger result, and Trigger failure reason.

[0069] The trigger instruction primary key ID can refer to the primary key of a key table, which can be used to distinguish different key tables. The trigger instruction ID can also refer to the trigger index of an order contract.

[0070] The meanings of parameters such as contract number, product code, service start time, and service end time can be found in Table 1, and will not be repeated here.

[0071] The cumulative trigger amount can refer to the total contract amount. The posting date can refer to the date the invoice receivable is generated. If a posting date can be specified in the order contract, when scanning the invoice allocation file, the order contract can be scanned on the specified posting date and an invoice receivable for the order contract can be generated. For order contracts whose scanning date and posting date are inconsistent, such order contracts can be filtered out.

[0072] The trigger result can be used to identify whether an order contract has been triggered. For example, the trigger result can be "triggered successfully (S)," "triggered failed (E)," or "not triggered (U)," which is the initial data.

[0073] A trigger result of S or E indicates that the event has been triggered. A trigger result of U indicates that the event has not been triggered.

[0074] S302. Query the contract trigger file to find the first order contract that has not been triggered.

[0075] The order contract whose query result is marked as U is the first order contract.

[0076] S303. Add the first order contract to the invoice allocation file and reset the trigger result of the first order contract in the contract trigger file to "triggered".

[0077] Once the first order contract is successfully inserted into the invoice allocation file, the trigger result of the first order contract in the contract trigger file can be reset to "triggered".

[0078] Furthermore, if the first order contract is identified as the second order contract and an invoice for the current accounting period is successfully generated, the trigger result for the first order contract in the contract trigger file can be set to S, indicating successful triggering. If the first order contract is identified as the second order contract but an invoice for the current accounting period is not successfully generated, the trigger result for the first order contract in the contract trigger file can be set to E, indicating failed triggering. A trigger result of either S or E indicates that the trigger has been successful.

[0079] S304. Determine the invoice allocation file. The invoice allocation file includes contract information for at least one first order contract and cumulative trigger identifiers for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management. The cumulative trigger identifier is whether all have been triggered or not.

[0080] S305. Based on the cumulative triggering identifiers of each first order contract in the invoice allocation file, query the second order contracts whose cumulative triggering identifiers are not all triggered.

[0081] S306. If the second order contract meets the accounting conditions for the current accounting period, generate an invoice for the current accounting period for the second order contract.

[0082] In this embodiment, before determining the invoice allocation file, a contract trigger file is also determined. The initially collected order contracts are managed through this contract trigger file. Triggering means adding the order contract to the invoice allocation file to facilitate automatic invoice generation. The triggering results of each order contract determine whether it has been triggered. If an order contract has been triggered, it does not need to be triggered again. If an order contract has not been triggered, it needs to be added to the invoice allocation file. This ensures accurate identification of the first contract file that requires automatic invoice generation, avoiding omissions in order contract processing. The status update of the triggering results effectively ensures timely updates to the triggering status of order contracts, achieving real-time synchronization between triggering results and status, effectively preventing duplicate triggering of order contracts. This improves the completeness and processing efficiency of the automatic invoice generation process, ensures consistency between the contract triggering status and the invoice allocation process, and promotes the standardized and orderly advancement of financial processing procedures.

[0083] As one embodiment, prior to S301, the following may also be included: Collect order contracts, add the collected order contract information to the contract trigger file, and set the trigger result of the order contracts to not be triggered.

[0084] Optionally, collecting order contracts may include collecting order contracts from an ERP system. Alternatively, the ERP system itself may perform the collection of order contracts. For example, a non-ERP system may read order contracts from the ERP system. Or, the ERP system may collect order contracts to execute the accounts receivable invoice generation method provided in this application embodiment.

[0085] Optionally, order contracts can be collected in real time to obtain contract information. If an order contract is initially added to the contract trigger file, the trigger result for the order contract can be initially set to not be triggered.

[0086] In this embodiment, order contracts are collected automatically. By continuously incorporating contract information into a contract trigger file and setting the trigger result of newly added order contracts to "not triggered," accurate access and initialization of order contracts to the invoice allocation section is achieved. This avoids omissions and errors caused by manual data entry, ensuring the integrity and accuracy of order contracts and effectively improving the data synchronization efficiency of the financial pre-process.

[0087] The amount on the invoice is a crucial parameter in the accounts receivable invoice. Therefore, in this embodiment of the application, generating an accounts receivable invoice for the current accounting period for a second order contract may include: Obtain the current accounting period and service cycle of the second order contract to calculate the accounting percentage and accounting amount of the current accounting period relative to the service cycle.

[0088] Based on the amount received, generate an invoice for the second order contract in the current accounting period.

[0089] Optionally, the amount recorded for the current accounting period can be determined based on the recording ratio and the contract amount of the order contract.

[0090] For example, if the service period is (service start time 2025-07-21 to service end time 2026-07-21), then the accounting percentage for the July accounting period is calculated from the service start time: 2025-07-21 to the last day of the July accounting period.

[0091] Revenue sharing ratio = (July 31, 2025 - July 21, 2025 + 1) / (July 21, 2026) 2025.07.21+1) ×100%.

[0092] Optionally, it further includes: receiving a time adjustment request for a service period, wherein the time adjustment request refers to a request to adjust the service start time or service end time of the service period. In response to the time adjustment request, adjusting the service start time or service end time of the service period.

[0093] Optionally, generating an accounts receivable invoice for the second order contract in the current accounting period based on the recorded amount may include: generating a standard invoice for the second order contract in the current accounting period based on the recorded amount, and identifying this standard invoice as an accounts receivable invoice. Under normal circumstances, accounts receivable invoices are standard invoices generated through an invoice creation program. The invoice format or template for a standard invoice can be pre-defined; after filling in the recorded amount and contract information according to the standard invoice format or template, a standard invoice is obtained.

[0094] In this embodiment of the application, by obtaining the current accounting period and service cycle of the second order contract, the accounting period is used to calculate the accounting ratio and the accounting amount of the current accounting period to the service cycle. This achieves refined accounting by allocating the accounting amount according to the service cycle, which not only ensures that the accounting amount is accurately matched with the current service progress, but also meets the accounting requirements, avoids phenomena such as one-time accounting or uneven allocation, and improves the accuracy of the amount of accounts receivable invoices.

[0095] As mentioned above, the service period may be adjusted during the order contract service process. This adjustment may result in an adjustment to a specific accounting period. Therefore, based on the recorded amount, an accounts receivable invoice for the second order contract in the current accounting period is generated, including: In the event of an adjustment to the service period of the second order contract, the new amount recorded for the second order contract in the current accounting period shall be obtained; Query the original recorded amount of the second order contract in the current accounting period, and calculate the difference between the new recorded amount and the original recorded amount; If the difference is greater than or equal to 0, the invoice creation program is invoked to create a positive invoice corresponding to the recorded amount. If the difference is less than 0, the invoice creation program is invoked to create a credit invoice corresponding to the recorded amount.

[0096] Optionally, when adjusting the accounting period, the new and original recorded amounts can be obtained sequentially to calculate the difference between them. If the difference is less than 0, it indicates that the service period for the current accounting period has been extended, and there is a balance between the current recorded amount and the recorded amount for the current accounting period, which can be offset by a cash refund. If the recorded amount is greater than 0, it indicates that the service period for the current accounting period has been shortened, and the current recorded amount is sufficient to pay for the orders in the current accounting period, with a surplus. Therefore, a positive invoice can be generated. A positive invoice can be an invoice with a positive recorded amount. A credit invoice can be an invoice with a negative recorded amount. Regardless of whether it is a positive or credit invoice, the invoice amount can be the difference between the new and original recorded amounts.

[0097] If the service period of the second order contract remains unchanged, the accounts receivable invoice can be generated according to the original invoice generation process. The amount of the accounts receivable invoice generated during this accounting period is the original recorded amount.

[0098] In this embodiment, when the service period of an order contract is adjusted, the new recorded amount of the second order contract in the current accounting period can be obtained, as well as the original recorded amount of the second order contract in the current accounting period can be queried. This allows for the acquisition of recorded amounts before and after the service period adjustment, calculation of the difference between the two recorded amounts, and confirmation of the specific type of invoice by the sign of the recorded amount. For scenarios where the recorded amount is greater than or equal to 0, a positive invoice can be generated. For scenarios where the recorded amount is less than 0, a credit invoice can be generated. When adjusting the service period, the type of invoice to be generated can be automatically determined based on the difference in recorded amounts before and after the adjustment, and the invoice can be automatically generated, improving the efficiency and accuracy of invoice generation.

[0099] As one example, the invoice allocation file also includes: cumulative trigger ratio. After generating the accounts receivable invoice for the second order contract in the current accounting period based on the recorded amount, the method further includes: Increase the cumulative trigger ratio of the second order contract by the accounting percentage; If the cumulative trigger ratio equals 1 after increasing the revenue ratio, reset the cumulative trigger flag of the second order contract to "all triggered".

[0100] In this embodiment, a cumulative trigger ratio is also set in the invoice allocation file. The cumulative trigger ratio increases according to the accounting entry ratio when each invoice is generated. By automatically updating the cumulative trigger flag to "all triggered" when the cumulative trigger ratio reaches 1, real-time tracking and intelligent synchronization of contract performance accounting progress are achieved. This accurately reflects the cumulative accounting completion status within the contract service period, avoiding duplicate or incomplete accounting issues. It also provides a clear status basis for subsequent screening of contracts that have not been fully triggered and for advancing the generation of invoices for the remaining accounting period, ensuring the continuity and standardization of the accounting and invoice generation process, and improving the automation and accuracy of the entire financial processing process.

[0101] Optionally, obtain the current accounting period and service cycle of the second order contract to calculate the accounting percentage of the current accounting period relative to the service cycle, including: To find the accounting period corresponding to the second order contract at the current time, obtain the current accounting period. The number of service days in the current accounting period is determined based on the start and end times of the service period and / or the last day of the current accounting period. Calculate the number of service days and the total number of days in the service period, and calculate the accounting percentage of the current accounting period in the service period.

[0102] Optionally, querying the accounting period corresponding to the second order contract at the current time may include: calling a time query program to query the accounting period corresponding to the current time. The time query program may be a pre-built computer program or plugin for querying the accounting period for a specific time.

[0103] The current time can be obtained through a time lookup program. For example, you can use this program to obtain the current time and determine the current accounting period based on it and the accounting cycle. For instance, assuming the current time is 9:00 AM on July 2, 2025, and the service period is from July 1, 2025 to October 20, 2025, then the current accounting period is from July 1, 2025 to July 31, 2025.

[0104] Optionally, the number of service days for the current accounting period can be determined based on the start time, end time, and / or the last day of the current accounting period. This includes: if the start time of the service period falls within the current accounting period, then the number of days from the start time of the service period to the last day of the current accounting period is obtained as the number of service days. Alternatively, if neither the start nor end time of the service period falls within the current accounting period, then the number of days between the first and last day of the current accounting period is obtained as the number of service days. Alternatively, if the end time of the service period falls within the current accounting period, then the number of days between the first day of the current accounting period and the last day of the service period is obtained as the number of service days. Alternatively, if both the start and end times of the service period fall within the current accounting period, then the number of days between the start and end times of the current accounting period is obtained as the number of service days.

[0105] The total number of days in the service period is the number of days between the start and end dates of the service period. After obtaining the accounting percentage for the current accounting period, the product of the contract amount of the second order contract and the accounting percentage is calculated to obtain the accounting amount.

[0106] For example, suppose there is a second service order contract with a contract amount of 400 yuan. The service period starts on July 1, 2025, and ends on October 20, 2025, for a total of 112 days. An accounts receivable invoice needs to be created in July, August, September, and October respectively.

[0107] The amount received in July was: 400 ((2025.07.31-2025.07.01+1) / (2025.10.20-2025.07.01+1))-0 = 110.71 (yuan) The amounts received in August, September, and October are calculated similarly as follows: The amount received in August was: 400 ((2025.08.31-2025.07.01+1) / (2025.10.20-2025.07.01+1))-110.71=110.72 (yuan) The amount received in September was: 400 ((2025.09.30-2025.07.01+1) / (2025.10.20-2025.07.01+1))-(110.71+110.72)=107.14 (yuan) The amount received in October was: 400 ((2025.10.20-2025.07.01+1) / (2025.10.20-2025.07.01+1))-(110.71+110.72+107.43)=71.43 (yuan) In this embodiment, the current accounting period corresponding to the second order contract is automatically queried. The number of service days in the current period is accurately calculated by combining the start time and end time of the service cycle and / or the end date of the current accounting period. Then, the accounting ratio is calculated by the ratio of the service days to the total number of days. This realizes the automated and refined calculation of the accounting ratio, which not only avoids the errors caused by manual calculation and ensures the accuracy of the ratio data, but also makes the accounting ratio accurately match the actual service performance in the current period, which meets the requirements of accrual accounting and improves the accuracy and efficiency of the entire accounting ratio calculation.

[0108] Accounts receivable invoices are typically generated automatically multiple times per accounting period, but only one invoice needs to be generated per accounting period. However, the invoice allocation file is triggered by scanning, such as every two hours. If an invoice is generated with each trigger scan, there is redundancy in invoice generation, resulting in wasted resources. To avoid generating multiple accounts receivable invoices for the same accounting period, this application embodiment includes the next trigger time for each order contract in the invoice allocation file; the method also includes: If the last day of the current accounting period for the second order contract is later than or equal to the next trigger time, the second order contract is determined to meet the accounting conditions for the current accounting period. After generating the accounts receivable invoice for the current accounting period for the second order contract, the following also includes: Determine the next accounting period from the current accounting period; The next trigger time for the second order contract will be reset to the last day of the next accounting period.

[0109] For example, if the time obtained in the current accounting period is greater than or equal to the next trigger time, an invoice is generated.

[0110] If the time obtained in the current accounting period is less than the next trigger time, no invoice will be generated.

[0111] For example, suppose the date of the second order contract is July 2nd, the last day of the current accounting period (Enddata) is July 30th, and the next trigger time is 7:30. If they are equal, an invoice will be generated. The next trigger time will then be updated to 8:30.

[0112] If the same second order contract is found again on July 3, the last day of the current accounting period is Enddata=7.30, and the next trigger time is 8.30, which no longer meets the generation conditions, and the invoice will no longer be generated.

[0113] After August, such as August 1st, the same second order contract is found with Enddata=8.30, and the next trigger time is August 30th, generating an invoice.

[0114] For example, if on September 1st, the same second order contract is found with Enddata=9.30, but the next trigger time is August 30th, an invoice is also generated, and the next trigger time is updated to October 30th.

[0115] In this embodiment, the criterion is that the last day of the current accounting period is later than or equal to the next trigger time. This accurately determines whether the second order contract meets the accounting entry conditions for the current accounting period, thereby completing the accounting entry and automatic invoice generation. If the next accounting period is determined, the next trigger time for the second order contract is reset to the last day of the next accounting period. This achieves intelligent verification of the accounting entry timing and automated iterative setting of subsequent trigger nodes, avoiding accounting confusion or redundant entries, ensuring the accuracy of the accounting sequence. The next accounting entry for a unified order contract can be initiated without manual intervention, creating a complete cyclical link for invoice generation throughout the contract service cycle, improving invoice generation efficiency and accuracy.

[0116] As an example, querying the contract trigger file for the first order contract whose trigger result is not triggered includes: Periodically scan the contract trigger file to retrieve the first order contract that has not been triggered. Based on the cumulative trigger flags of each first order contract in the invoice allocation file, query the second order contracts whose cumulative trigger flags have not been fully triggered, including: Once the contract triggering documents have been scanned, the invoice allocation documents are scanned to query the second order contracts whose cumulative triggering identifiers have not been fully triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation documents.

[0117] Optionally, contract trigger files can be scanned at a preset scan frequency, such as once every two hours. The scan frequency can be specifically set according to scanning needs.

[0118] In this embodiment, contract triggering files are scanned periodically to filter out first order contracts that have not been triggered. After the scan is completed, the invoice allocation file scan is started to further filter out second order contracts whose cumulative triggering flag is not fully triggered. This achieves hierarchical and precise filtering of contracts to be credited and process-linked verification. The periodic scanning ensures timely identification of unprocessed contracts and avoids omissions, while the scanning of invoice allocation files accurately completes the filtering of second order contracts that have not been fully triggered, reducing manual intervention and improving the automation efficiency of the filtering process.

[0119] like Figure 4 The diagram shown is a flowchart of an accounts receivable invoice generation method provided in an embodiment of this application. The method may include the following steps: S401. Collect order contracts, add the collected order contract information to the contract trigger file, and set the trigger result of the order contracts to not be triggered.

[0120] S402. Periodically scan the contract trigger file to query the first order contract that has not been triggered.

[0121] S403. Add the first order contract to the invoice allocation file and reset the trigger result of the first order contract in the contract trigger file to "triggered".

[0122] S404. After completing the scanning of the contract triggering documents, start scanning of the invoice allocation documents to query the second order contracts whose cumulative triggering identifiers are not all triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation documents.

[0123] S405. Obtain the current accounting period and service cycle of the second order contract.

[0124] S406. Determine whether the last day of the current accounting period of the second order contract is later than or equal to the next trigger time. If yes, execute S407; otherwise, execute S417.

[0125] S407. Based on the current accounting period and service cycle of the second order contract, calculate the accounting percentage and accounting amount of the current accounting period relative to the service cycle.

[0126] S408. In the event of an adjustment to the service period of the second order contract, obtain the new amount recorded for the second order contract in the current accounting period.

[0127] S409. Query the original recorded amount of the second order contract in the current accounting period, and calculate the difference between the new recorded amount and the original recorded amount.

[0128] S410. Determine if the amount received is greater than or equal to 0. If yes, proceed to S411; otherwise, proceed to S412.

[0129] S411. Call the invoice creation program to create a positive invoice corresponding to the amount to be recorded, and then execute S417.

[0130] S412. Call the invoice creation program to create a credit invoice corresponding to the recorded amount, and then execute S417.

[0131] S413. Increase the cumulative trigger ratio of the second order contract by the accounting ratio.

[0132] S414. Determine whether the cumulative trigger ratio after increasing the revenue ratio is equal to 1. If yes, execute S415; otherwise, execute S416.

[0133] S415. Reset the cumulative trigger flag of the second order contract to "all triggered", then execute S417.

[0134] S416. Maintain the cumulative trigger flag of the second order contract as not fully triggered, then execute S417.

[0135] S417. Continue scanning the next first order contract in the invoice allocation file until the scanning is complete.

[0136] This embodiment employs processes such as automatic order contract collection, timed scanning of contract trigger files, linked scanning of invoice allocation files, determination of accounting entry conditions, calculation of accounting entry ratio and amount, intelligent generation of invoice types, and dynamic updating of trigger status and identifiers. This achieves automated generation from order contract access to accounts receivable invoices, accurately filters invoices requiring accounting entry, and enables automated accounting, intelligent judgment, and status publication, avoiding technical problems such as errors caused by manual processes or low efficiency. This improves the efficiency, accuracy, and standardization of invoice generation.

[0137] like Figure 5 The diagram shown is a structural schematic of an accounts receivable invoice generation device provided in an embodiment of this application. The accounts receivable invoice generation device 500 may include the following units: The first determining unit 501 is used to determine the invoice allocation file. The invoice allocation file includes contract information for at least one first order contract and cumulative triggering identifiers for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management. The cumulative triggering identifiers indicate whether all have been triggered or not.

[0138] Contract filtering unit 502 is used to query second order contracts whose cumulative triggering identifiers are not all triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation file.

[0139] Invoice generation unit 503 is used to generate an accounts receivable invoice for the current accounting period for the second order contract if the second order contract meets the accounting conditions for the current accounting period.

[0140] As one embodiment, the invoice generation unit may include: The accounting calculation module is used to obtain the current accounting period and service cycle of the second order contract in order to calculate the accounting ratio and accounting amount of the current accounting period to the service cycle. The invoice generation module is used to generate accounts receivable invoices for the second order contract in the current accounting period based on the amount recorded.

[0141] As one example, the invoice generation module includes: The accounting adjustment submodule is used to obtain the new recorded amount of the second order contract in the current accounting period when the service period of the second order contract is adjusted. The difference determination submodule is used to query the original recorded amount of the second order contract in the current accounting period and calculate the difference between the new recorded amount and the original recorded amount. The first generation submodule is used to call the invoice creation program to create a positive invoice corresponding to the amount to be recorded when the difference is greater than or equal to 0. The second generation submodule is used to call the invoice creation program to create a credit invoice corresponding to the recorded amount when the difference is less than 0.

[0142] As one embodiment, the invoice allocation document further includes: a cumulative trigger ratio; the device further includes: The cumulative increase unit is used to increase the cumulative trigger ratio of the second order contract by the accounting ratio; The trigger update unit is used to reset the cumulative trigger flag of the second order contract to "all triggered" when the cumulative trigger ratio after increasing the revenue ratio is equal to 1.

[0143] As one example, the accounting calculation module includes: The query submodule is used to query the accounting period corresponding to the second order contract at the current time and obtain the current accounting period; The Days submodule is used to determine the number of service days for the current accounting period based on the start time, end time, and / or the last day of the current accounting period. The Proportion submodule is used to calculate the number of service days and the total number of days in the service period, and to calculate the proportion of revenue recorded in the current accounting period relative to the service period.

[0144] As one embodiment, the invoice allocation file also includes the next trigger time for each order contract; the device also includes: The condition judgment unit is used to determine whether the second order contract meets the accounting conditions of the current accounting period if the last day of the current accounting period of the second order contract is later than or equal to the next trigger time. The cycle extension unit is used to determine the next accounting cycle of the current accounting cycle; The time setting unit is used to reset the next trigger time of the second order contract to the last day of the next accounting period.

[0145] As one embodiment, it also includes: The second determining unit is used to determine the contract triggering file. The contract triggering file includes contract information for at least one order contract and the triggering result for each order contract, wherein the triggering result is either triggered or not triggered. The contract query unit is used to query the first order contract whose trigger result is not triggered from the contract trigger file; The contract triggering unit is used to add the first order contract to the invoice allocation file and reset the triggering result of the first order contract in the contract triggering file to "triggered".

[0146] As an example, determining the contract triggering document includes: Collect order contracts, add the collected order contract information to the contract trigger file, and set the trigger result of the order contracts to not be triggered.

[0147] As one embodiment, the contract query unit includes: The first scanning module is used to periodically scan the contract trigger file to query the first order contract that has not been triggered.

[0148] The contract screening unit includes: The second scanning module is used to start scanning the invoice allocation file after the contract triggering file has been scanned, so as to query the second order contracts whose cumulative triggering identifiers are not all triggered based on the cumulative triggering identifiers of each first order contract in the invoice allocation file.

[0149] In the embodiments of this application, Figure 5 The device shown can also be a chip or a chip system, such as a system on chip (SoC) or a baseboard management controller (BMC).

[0150] Figure 6This is a hardware block diagram of a computing device provided in an embodiment of this application. The computing device 600 according to an embodiment of this application includes at least a memory 601 and a processor 602. The memory 601 is used to store computer programs. The processor 602 is used to execute the computer programs to implement the accounts receivable invoice generation method of any of the above embodiments.

[0151] In addition, both memory 601 and processor 602 are electrically connected to bus 603.

[0152] Furthermore, embodiments of this application also provide a computer-readable storage medium for storing a computer program. When executed by a processor, this computer program implements the accounts receivable invoice generation method of any of the preceding embodiments of this application.

[0153] Computer-readable storage media include, but are not limited to, volatile storage media and / or non-volatile storage media. Volatile storage media may include, for example, random access storage media (RAM) and / or cache storage media. Non-volatile storage media may include, for example, read-only storage media (ROM), hard disks, flash memory, optical disks, magnetic disks, etc.

[0154] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the accounts receivable invoice generation method of any of the preceding embodiments of this application.

[0155] The basic principles of the embodiments of this application have been described above with reference to specific examples. However, it should be noted that the advantages, benefits, and effects mentioned in the embodiments of this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the embodiments of this application from necessarily employing the aforementioned specific details.

[0156] The block diagrams of devices, apparatuses, devices, and systems involved in the embodiments of this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context explicitly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0157] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0158] It should also be noted that in the systems and methods of this application embodiment, each component or step can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions of the embodiments of this application.

[0159] Various changes, substitutions, and modifications can be made to the technology herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the embodiments of this application is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0160] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use embodiments of this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of embodiments of this application. Therefore, embodiments of this application are not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0161] The above description has been given for illustrative and descriptive purposes. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A method for generating accounts receivable invoices, characterized in that, include: The invoice allocation file is determined, which includes contract information for at least one first order contract and a cumulative trigger identifier for each first order contract. The first order contract refers to the order contract that requires accounts receivable invoice management, and the cumulative trigger identifier indicates whether all have been triggered or not. Based on the cumulative trigger identifiers of each first order contract in the invoice allocation file, query the second order contracts whose cumulative trigger identifiers have not been fully triggered; If the second order contract meets the accounting conditions for the current accounting period, an invoice for the current accounting period is generated for the second order contract.

2. The method according to claim 1, characterized in that, The process of generating an accounts receivable invoice for the current accounting period for the second order contract includes: Obtain the current accounting period and service cycle of the second order contract to calculate the accounting percentage and accounting amount of the current accounting period relative to the service cycle; Based on the recorded amount, generate an invoice for the second order contract for the current accounting period.

3. The method according to claim 2, characterized in that, The step of generating an accounts receivable invoice for the second order contract in the current accounting period based on the recorded amount includes: In the event of an adjustment to the service period of the second order contract, the new amount recorded for the second order contract in the current accounting period shall be obtained; Query the original recorded amount of the second order contract in the current accounting period, and calculate the difference between the new recorded amount and the original recorded amount; If the difference is greater than or equal to 0, the invoice creation program is invoked to create a positive invoice corresponding to the recorded amount; If the difference is less than 0, the invoice creation program is invoked to create a credit invoice corresponding to the recorded amount.

4. The method according to claim 2, characterized in that, The invoice allocation file also includes: a cumulative trigger ratio; after generating the second order contract based on the recorded amount, the method further includes: Increase the cumulative trigger ratio of the second order contract by the revenue recognition ratio; If the cumulative trigger ratio after increasing the revenue ratio is equal to 1, the cumulative trigger flag of the second order contract will be reset to "all triggered".

5. The method according to claim 2, characterized in that, The step of obtaining the current accounting period and service cycle of the second order contract to calculate the revenue recognition ratio of the current accounting period to the service cycle includes: Query the accounting period corresponding to the second order contract at the current time to obtain the current accounting period; The number of service days in the current accounting period is determined based on the start time, end time, and / or the last day of the current accounting period. Calculate the number of service days and the total number of days in the service period, and calculate the accounting percentage of the current accounting period in the service period.

6. The method according to any one of claims 1-5, characterized in that, The invoice allocation file also includes the next trigger time for each order contract; the method further includes: If the last day of the current accounting period of the second order contract is later than or equal to the next trigger time, it is determined that the second order contract meets the accounting conditions for the current accounting period. After generating the accounts receivable invoice for the current accounting period for the second order contract, the method further includes: Determine the next accounting period for the current accounting period; The next trigger time for the second order contract is reset to the last day of the next accounting period.

7. The method according to any one of claims 1-6, characterized in that, Also includes: Determine the contract trigger file, which includes contract information for at least one order contract and the trigger result for each order contract, wherein the trigger result is either triggered or not triggered; The first order contract that was not triggered was retrieved from the contract trigger file. Add the first order contract to the invoice allocation file, and reset the trigger result of the first order contract in the contract trigger file to "triggered".

8. The method according to claim 7, characterized in that, The determination of the contract triggering document includes: Collect order contracts, add the collected order contract information to the contract trigger file, and set the trigger result of the order contract to not be triggered.

9. The method according to claim 7, characterized in that, The step of querying the contract trigger file and finding that the first order contract has not been triggered includes: The contract trigger file is scanned periodically to query the first order contract that has not been triggered. The step of querying second order contracts whose cumulative trigger identifiers are not all triggered based on the cumulative trigger identifiers of each first order contract in the invoice allocation file includes: Upon completion of the scan of the contract triggering file, the scan of the invoice allocation file is initiated to query the second order contracts whose cumulative triggering identifiers are not all triggered, based on the cumulative triggering identifiers of each first order contract in the invoice allocation file.

10. A computing device, characterized in that, include: A processor and a memory, the memory storing a computer program that is invoked by the processor to execute the accounts receivable invoice generation method according to any one of claims 1-9.

Images