Method and system for calculating invoice opening date from invoice date for a business customer

Abstract

The application provides a method and system for calculating the invoice overdue of an enterprise client, wherein the method comprises: obtaining a service client set of a target enterprise; screening the service client set to obtain an invoice overdue client set; obtaining a historical bill set of a first client according to the invoice overdue client set; obtaining cumulative invoiced but unreimbursed amount information and invoice-reimbursement amount difference information of the first client according to the historical bill set; deducting the bills of the invoice-reimbursement amount difference information based on the cumulative invoiced but unreimbursed amount information to generate a first end instruction; ending the deduction of the cumulative invoiced but unreimbursed amount information according to the first end instruction, marking the deducted bills to generate a deducted bill set; and associating and tracing the invoiced bills of each deducted bill based on the deducted bill set to obtain the reimbursement status corresponding to the invoiced bills, and dynamically monitoring the reimbursement status.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of financial management, and particularly relates to a method and system for calculating invoice overdue of enterprise customers. BACKGROUND

[0002] In the process of developing business, an enterprise generally includes two charging modes. One is a prepayment sales mode, that is, the customer pays the enterprise first, and then the enterprise opens an invoice, and there is no situation of invoice overdue. The other is a mode of opening an invoice first and then charging, and in this case, there is a situation of invoice overdue.

[0003] Invoice overdue refers to the situation that after opening an invoice, the customer does not pay the enterprise in time according to the invoice amount. For the financial management of invoice overdue, the enterprise financial personnel generally performs summary and checking management through offline point-to-point mode.

[0004] However, in the process of implementing the technical scheme in the embodiments of the present application, the present application inventors find that the above-mentioned technology at least has the following technical problems:

[0005] In the prior art, the enterprise financial personnel performs summary and checking management on invoice overdue through offline point-to-point mode, and the artificial participation degree is large, which is time-consuming and laborious. In the case of a large number of customers and a large amount of transactions, it is difficult to accurately supervise the repayment of invoice overdue, and there is a technical problem that the financial management of invoice overdue cannot be efficiently and accurately supervised. SUMMARY

[0006] The embodiments of the present application provide a method and system for calculating invoice overdue of enterprise customers, which are used to solve the technical problem that in the prior art, the enterprise financial personnel performs summary and checking management on invoice overdue through offline point-to-point mode, the artificial participation degree is large, which is time-consuming and laborious, and in the case of a large number of customers and a large amount of transactions, it is difficult to accurately supervise the repayment of invoice overdue, and the financial management of invoice overdue cannot be efficiently and accurately supervised.

[0007] In view of the above problems, the embodiments of the present application provide a method and system for calculating invoice overdue of enterprise customers.

[0008] In a first aspect, a method for calculating invoice overdue of enterprise customers is provided. The method comprises: obtaining a service customer set of a target enterprise; screening the service customer set to obtain an invoice overdue customer set; obtaining a historical bill set of a first customer according to the invoice overdue customer set, wherein the first customer is any customer in the invoice overdue customer set; obtaining cumulative invoiced but uncollected amount information and invoice-uncollected amount difference information of the first customer according to the historical bill set; deducting bills of the invoice-uncollected amount difference information based on the cumulative invoiced but uncollected amount information until the cumulative invoiced but uncollected amount information is deducted to zero to generate a first end instruction; ending deduction of the cumulative invoiced but uncollected amount information according to the first end instruction, marking deducted bills, and generating a deducted bill set; and associating and tracing the invoiced bills of each deducted bill based on the deducted bill set, obtaining a corresponding collection state of the invoiced bills, and dynamically monitoring the collection state.

[0009] In a second aspect, a system for calculating invoice overdue of enterprise customers is provided. The system comprises: a first obtaining unit configured to obtain a service customer set of a target enterprise; a second obtaining unit configured to screen the service customer set to obtain an invoice overdue customer set; a third obtaining unit configured to obtain a historical bill set of a first customer according to the invoice overdue customer set, wherein the first customer is any customer in the invoice overdue customer set; a first processing unit configured to obtain cumulative invoiced but uncollected amount information and invoice-uncollected amount difference information of the first customer according to the historical bill set; a second processing unit configured to deduct bills of the invoice-uncollected amount difference information based on the cumulative invoiced but uncollected amount information until the cumulative invoiced but uncollected amount information is deducted to zero to generate a first end instruction; a third processing unit configured to end deduction of the cumulative invoiced but uncollected amount information according to the first end instruction, mark deducted bills, and generate a deducted bill set; and a fourth processing unit configured to associate and trace the invoiced bills of each deducted bill based on the deducted bill set, obtain a corresponding collection state of the invoiced bills, and dynamically monitor the collection state.

[0010] In a third aspect, the application provides a system for calculating invoice overdue of enterprise customers, comprising: a processor coupled with a memory, the memory being configured to store a program, when the program is executed by the processor, the system is configured to execute the steps of the method of the first aspect.

[0011] The one or more technical solutions provided in the embodiments of the application have at least the following technical effects or advantages:

[0012] In the embodiments of the application, the service customer set of the enterprise needing to calculate the invoice overdue is obtained, the invoice overdue customer set is further obtained, and the historical bill set of the first customer in the invoice overdue customer set is obtained. The cumulative invoiced but unreimbursed amount information and the invoice-reimbursement amount difference information are obtained based on the historical bill set. The invoice-reimbursement amount difference information is deducted based on the invoiced but unreimbursed amount information, and the deduction is stopped when the deduction is zero. The deducted bill set is obtained. The invoiced bills are obtained through the association and tracing of the deducted bill set. The reimbursement status of the invoiced bills is summarized and monitored. In the embodiments of the application, the association between the bills and the invoices is established from the invoice dimension. According to the first-in first-out principle of the financial caliber, the total invoiced but unreimbursed amount information is used to deduct the invoice-reimbursement amount difference information. All the unreimbursed bills and overdue invoices are obtained through tracing. The actual reimbursement of each bill of each customer is tracked and calculated. The calculation result is dynamically updated at regular intervals. A quantifiable method for calculating and planning the overdue invoices is established. The financial supervision labor cost is reduced, and the efficiency and accuracy of the supervision of the overdue invoices are improved.

[0013] The above description is only a summary of the technical solutions of the application. In order to more clearly understand the technical means of the application, the application can be implemented according to the content of the specification. In order to make the above and other purposes, characteristics and advantages of the application more obvious and easy to understand, the following specific embodiments of the application are described. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 A method flowchart for calculating the overdue invoices of the enterprise customers who have invoiced is provided in the embodiments of the application.

[0015] Figure 2 A flowchart for obtaining the historical bill set in the method for calculating the overdue invoices of the enterprise customers who have invoiced is provided in the embodiments of the application.

[0016] Figure 3 A flowchart for associating and tracing the invoices in the method for calculating the overdue invoices of the enterprise customers who have invoiced is provided in the embodiments of the application.

[0017] Figure 4A system structure schematic diagram for calculating the invoice opening overdue of an enterprise client is provided for the embodiments of the present application.

[0018] Figure 5 A structure schematic diagram of an exemplary electronic device of the embodiments of the present application is provided.

[0019] Label explanation: first obtaining unit 11, second obtaining unit 12, third obtaining unit 13, first processing unit 14, second processing unit 15, third processing unit 16, fourth processing unit 17, electronic device 300, memory 301, processor 302, communication interface 303, bus architecture 304. DETAILED DESCRIPTION

[0020] The embodiments of the present application provide a method and system for calculating the invoice opening overdue of an enterprise client, which are used to solve the technical problem that in the prior art, enterprise financial personnel manually collect and check the invoice opening overdue in an offline point-to-point manner, which is time-consuming and laborious, and it is difficult to accurately supervise the collection of the invoice opening overdue in the case of a large number of clients and transactions.

[0021] Summary of the application

[0022] Currently, a part of enterprises adopt a prepayment sales mode, that is, the client pays the enterprise first, and then the enterprise opens an invoice, and there is usually no invoice opening overdue situation. However, another part of enterprises adopt a post-charge business mode, and the management of the invoice opening overdue is usually performed in an offline excel file point-to-point checking manner, which is time-consuming and laborious. In addition to the fact that the business personnel themselves may be clear about the actual collection, the upper managers cannot clearly understand all the invoice opening overdue situations, and cannot implement management measures. Moreover, there is no universal method for solving the collection of invoices on the market.

[0023] After providing actual sales services for the client, the enterprise usually needs to open a service fee invoice according to the sales amount, and the client pays the enterprise after seeing the invoice. Inevitably, the sales mode of paying after opening an invoice produces the situation of invoice opening overdue. Many enterprises have no corresponding systematic measures for managing the overdue invoice. Especially when the number of clients is increasingly large, it is difficult to accurately supervise the actual collection of each invoice of each client. In addition, there are special situations such as prepayment invoice and initial historical invoice, and the rules for calculating the invoice opening overdue are more complex.

[0024] In view of the above technical problems, the general idea of the technical solutions provided by the present application is as follows:

[0025] obtaining a service customer set of a target enterprise; screening the service customer set to obtain an overdue invoice customer set; obtaining a historical bill set of a first customer according to the overdue invoice customer set, wherein the first customer is any customer in the overdue invoice customer set; obtaining cumulative invoiced but uncollected amount information and invoice-uncollected amount difference information of the first customer according to the historical bill set; deducting bills of the invoice-uncollected amount difference information based on the cumulative invoiced but uncollected amount information until the cumulative invoiced but uncollected amount information is deducted to zero to generate a first end instruction; ending deduction of the cumulative invoiced but uncollected amount information according to the first end instruction, and marking deducted bills to generate a deducted bill set; and associating and tracing the invoiced bills of each deducted bill based on the deducted bill set to obtain a corresponding collection state of the invoiced bills, and dynamically monitoring the collection state.

[0026] After introducing the basic principles of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, not all embodiments of the present application. It should be understood that the present application is not limited to the example embodiments described herein. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application. In addition, it should be noted that, for convenience of description, only parts related to the present application are shown in the drawings, not all.

[0027] Embodiment one

[0028] As shown in the figure, the present application provides a method for calculating the overdue invoice of the invoiced bills of the enterprise customer, which comprises: Figure 1

[0029] S100: obtaining a service customer set of a target enterprise;

[0030] Specifically, the target enterprise is an enterprise that needs to use the method provided by the present application to calculate the overdue invoice, which can include enterprises of any industry, and all can use the method provided by the present application. The service customer set is all customers who have business cooperation with the target enterprise and issue invoices according to the business amount. Exemplarily, the service customer set can be obtained through the customer relationship management system (CRM) of the target enterprise, or can be obtained through other channels.

[0031] S200: screening the service customer set to obtain an overdue invoice customer set;

[0032] ​Step S200 comprises:

[0033] S210: obtaining a set of cumulative invoiced but not paid amounts of each service client in the set of service clients;

[0034] S220: determining whether each cumulative invoiced but not paid amount in the set of cumulative invoiced but not paid amounts is greater than zero;

[0035] S230: if each cumulative invoiced but not paid amount in the set of cumulative invoiced but not paid amounts is greater than zero, screening each cumulative invoiced but not paid amount greater than zero to generate a set of overdue invoices;

[0036] S240: performing reverse matching on the set of overdue invoices to obtain a set of invoicing overdue clients corresponding to the set of overdue invoices.

[0037] Specifically, to calculate the invoicing overdue finance of the client invoices, the client with invoicing overdue needs to be obtained first. First, the set of cumulative invoiced but not paid amounts of all service clients is obtained through the above-mentioned set of service clients. The set of cumulative invoiced but not paid amounts can be calculated and summarized before the method provided in the present application is used, and only needs to be calculated once, and can be updated subsequently by using the method provided in the present application.

[0038] According to the set of cumulative invoiced but not paid amounts, the set of cumulative invoiced but not paid amounts of each service client is obtained, and it is further determined whether the cumulative invoiced but not paid amount of each service client in the set of cumulative invoiced but not paid amounts is greater than zero. If the cumulative invoiced but not paid amount of a certain service client is greater than zero, it proves that the client has the situation of invoicing overdue, and there is an invoice that has been invoiced but not completely paid between the target enterprise and the client. Or, if the cumulative invoiced but not paid amount of a certain service client is equal to zero, it proves that the client does not have the situation of invoicing overdue, and all invoices between the target enterprise and the client have been cleared and paid.

[0039] According to the screening and tracing of the cumulative invoiced but not paid amount greater than zero, the set of overdue invoices corresponding to each cumulative invoiced but not paid amount greater than zero is obtained, and then the reverse matching is performed on the set of overdue invoices to obtain each service client corresponding to the set of overdue invoices, thereby obtaining the above-mentioned set of invoicing overdue clients.

[0040] According to the set of cumulative invoiced but not paid amounts in the enterprise financial information, the set of invoicing overdue clients is obtained by judging and tracing each cumulative invoiced but not paid amount in the set of cumulative invoiced but not paid amounts, so that the invoicing overdue clients in the current enterprise cooperation clients can be accurately obtained, and the accurate client data basis for the invoicing overdue calculation and management is constructed.

[0041] S300: Obtain a historical bill set of a first customer according to the set of customers whose bills are overdue, wherein the first customer is any customer in the set of customers whose bills are overdue;

[0042] As Figure 2 illustrated, the step S300 in the method provided by the embodiments of the present application comprises:

[0043] S310: Obtain a set of existing bill distributions of a first customer according to the set of customers whose bills are overdue;

[0044] S320: Obtain a set of creation time distributions of each existing bill according to the set of existing bill distributions;

[0045] S330: Sort the set of creation time distributions based on a first time sequence logic to generate a first creation time sequence;

[0046] S340: Sort and reorganize the set of existing bill distributions according to the first creation time sequence to generate the historical bill set.

[0047] Specifically, based on the obtained set of customers whose bills are overdue, a set of historical bills existing between each service customer in the set of customers whose bills are overdue and the target enterprise is obtained, i.e., a set of existing bill distributions of a first customer, wherein the first customer is any customer in the set of customers whose bills are overdue.

[0048] According to the set of existing bill distributions between the first customer and the target enterprise, a set of creation time distributions of each existing bill is obtained according to the issue creation date of each bill in the set of existing bill distributions. According to a preset first time sequence logic, the set of creation time distributions is sorted, and exemplarily, the first time sequence logic is time in ascending order, i.e., sorting from earlier time to later time. In this way, the set of creation time distributions of the set of existing bill distributions is sorted according to the first time sequence logic to obtain a first creation time sequence. Further, according to the existing bill corresponding to each creation time in the first creation time sequence, each existing bill is sorted according to the time in the first creation time sequence to generate the historical bill set.

[0049] As an example without limitation, before sorting the set of creation time distributions, a binary tuple of creation time and corresponding existing bill can be constructed to obtain a set of binary tuples, each binary tuple being: <creation time, existing bill>, then the creation time is sorted according to the first time sequence logic to obtain a binary tuple sequence, then the existing bill in each binary tuple is obtained, and the existing bill is sorted according to the binary tuple sequence, i.e., the historical bill set is generated.

[0050] The embodiment of the application can obtain a historical bill set sorted according to a time sequence, and further obtain a historical bill with billing expectation, by obtaining historical bills of each billing overdue customer and sorting the historical bills according to a set of billing overdue customers, so as to achieve the technical effect of accurately processing data.

[0051] S400: obtaining cumulative billed but not repaid amount information and billing-repayment amount difference information of the first customer according to the historical bill set;

[0052] Specifically, according to the historical bill set of the first customer, the historical bill set includes bills with cleared repayment and bills without cleared repayment, the unclosed repayment amount corresponding to the bills without cleared repayment is summed and calculated, and the bills with developed invoices corresponding to all the bills without cleared repayment are obtained, so that the cumulative billed but not repaid amount information of the first customer is obtained.

[0053] The method provided in the embodiment of the application includes obtaining billing-repayment amount difference information of the first customer in step S400.

[0054] S410: obtaining first bill information of the first customer according to the historical bill set, wherein the creation time of the first bill information is the latest creation time in the first creation time sequence;

[0055] S420: obtaining first billing amount information and first repayment amount information according to the first bill information;

[0056] S430: performing difference calculation on the first billing amount information and the first repayment amount information to obtain the billing-repayment amount difference information.

[0057] Specifically, according to the historical bill set of the first customer, the historical bill set is a historical bill sequence obtained by sorting according to a first time sequence logic. According to the first-in first-out principle of the financial dimension, the most recently created bill in the historical bill set is obtained, and the most recent bill is processed first. In this way, the first bill information is obtained, and the creation time of the first bill information is the latest creation time in the first creation time sequence.

[0058] According to the first bill information, the first billing amount information and the first repayment amount information of the first customer are obtained. The first billing amount information is the amount value information set when the first bill information is billed. If the first repayment amount information is less than the first billing amount information, it proves that the repaid amount of the first customer has not cleared the first bill information. At this time, the first billing amount information and the first repayment amount information are subjected to difference calculation to obtain the billing-repayment amount difference information.

[0059] If the first repayment amount information is equal to the first billing amount information, it is proved that the repayment amount of the first customer has settled the first billing information, and there is no billing expectation, and no processing is needed. Based on this, the second billing information is obtained in turn from the billing information created most recently in the historical billing set except the first billing information, the creation time of the second billing information is before the creation time of the first billing information in the first creation time sequence, and the billing-repayment amount difference information of the second billing information is calculated. In this way, the above steps are cycled to obtain the billing-repayment amount difference information of all billing information in the historical billing set.

[0060] The embodiment of the application can obtain the billing-repayment amount difference information of the billing information created most recently based on the first-in first-out financial processing principle by the historical billing set of the service customer, and can improve the efficiency of financial processing and the accuracy of billing overdue calculation processing.

[0061] S500: based on the cumulative billed but unreimbursed amount information, deducting the billing-repayment amount difference information of the billing, until the cumulative billed but unreimbursed amount information is deducted to zero, and generating a first end instruction;

[0062] Specifically, based on the cumulative billed but unreimbursed amount information and the billing-repayment amount difference information obtained by the above calculation. The cumulative billed but unreimbursed amount information is the amount information of all billed but unreimbursed in the historical billing set, and the billing-repayment amount difference information is the amount information of the unreimbursed in a single billing.

[0063] The cumulative billed but unreimbursed amount information is used to deduct the billing-repayment amount difference information of the billing, that is, the amount corresponding to the cumulative billed but unreimbursed amount information is subtracted from the amount corresponding to the billing-repayment amount difference information of the billing created most recently, until the cumulative billed but unreimbursed amount information is deducted to zero, and a first end instruction is generated to end the deduction. When the amount corresponding to the cumulative billed but unreimbursed amount information is deducted to zero, it is proved that the cumulative billed but unreimbursed amount information has been deducted to the billing corresponding to all billing-repayment amount difference information, and the billed but unreimbursed amount information is correct.

[0064] The embodiment of the application can calculate the billing overdue data according to the first-in first-out principle of repayment by using the cumulative billed but unreimbursed amount information to deduct the billing-repayment amount difference information of the billing, and can ensure that the billed but unreimbursed amount can be completely and accurately deducted and calculated, and improve the accuracy of billing overdue financial calculation management.

[0065] S600: According to the first termination instruction, terminate the deduction of the cumulative invoiced but unpaid amount information, mark the deducted bills, and generate a set of deducted bills;

[0066] Specifically, the system uses the accumulated outstanding invoice amount information to offset the difference between the invoice and payment amounts on the bills until the total amount is zero. Then, the offsetting process ends according to the first termination instruction mentioned above. Based on the set of bills corresponding to the offset outstanding invoice amount difference information, the bills within that set are marked, generating a set of offset bills. Thus, the sum of the outstanding invoice amount difference information corresponding to all bills in this set of offset bills is the amount corresponding to the accumulated outstanding invoice amount information.

[0067] Based on the aforementioned set of deducted bills, the creation time of each bill within it within the first creation time sequence can also be obtained. Based on the bill creation time and the current time, the overdue time of the bill can be determined, and financial personnel can conduct further financial management based on the overdue time.

[0068] S700: Based on the set of deducted bills, the issued invoices of each deducted bill are linked and traced to obtain the payment status corresponding to the issued invoices, and the payment status is dynamically monitored.

[0069] like Figure 3 As shown, step S700 in the method provided in this application embodiment includes:

[0070] S710: Obtain the set of invoice records for the first user;

[0071] S720: Based on the set of deducted bills, trace the related issued bills in the set of invoice records to generate a set of related issued bills;

[0072] S730: Based on the associated set of issued invoices, obtain the sum of the relevant bill payment amounts;

[0073] S740: Calculate the corresponding payment status based on the sum of the relevant bill payment amounts.

[0074] Specifically, the process begins by obtaining the set of invoice records between the first user and the target company in historical data. These invoices refer to those issued by the target company to the first customer, for which the first customer needs to make payment. Based on this set of deductible invoices, each invoice in this set is linked to the invoices in the aforementioned set of invoice records. This allows for the identification of invoices in the set of invoice records that contain invoices from the set of deductible invoices. Once all invoices in the set of deductible invoices have been traced and their corresponding invoices obtained, the resulting sets of traced invoices are aggregated to obtain the aforementioned set of associated issued invoices.

[0075] According to the associated set of invoices developed above, the sum of the remittance amounts of all bills included in each invoice and the invoicing amount of the invoice are obtained, and the corresponding remittance state is calculated. The sum of the remittance amounts of all bills included in each invoice is the sum of the associated bill remittance amounts described above, and the sum of the associated bill remittance amounts of each invoice is less than or equal to the invoicing amount of the invoice. If the sum of the associated bill remittance amounts is equal to the invoicing amount of the invoice, the remittance of the invoice is complete. In addition, if the sum of the associated bill remittance amounts is less than the invoicing amount of the invoice, the remittance of the invoice is not complete.

[0076] The step S740 in the method provided by the embodiment of the present application comprises:

[0077] S741: If the sum of the associated bill remittance amounts is zero, a first remittance state is obtained, and the first remittance state is marked as an unremitted state.

[0078] S742: If the sum of the associated bill remittance amounts is greater than zero, a second remittance state is obtained, and the second remittance state is marked as a partially remitted state.

[0079] Specifically, if the sum of the associated bill remittance amounts described above is zero, a first remittance state is obtained, and the first remittance state is marked as an unremitted state, then the associated bill remittance amount corresponding to the invoice is completely unremitted. If the sum of the associated bill remittance amounts described above is greater than zero, a second remittance state is obtained, and the second remittance state is marked as a partially remitted state, and the sum of the associated bill remittance amounts corresponding to the invoice is not completely remitted. If the sum of the associated bill remittance amounts described above is equal to the invoicing amount of the corresponding invoice, the invoice corresponding to the sum of the associated bill remittance amounts is marked as a remitted state.

[0080] The step S720 in the method provided by the embodiment of the present application comprises:

[0081] S721: If the associated set of developed invoices in the invoicing record set does not exist, a third remittance state is obtained.

[0082] S722: The third remittance state is marked as a remitted state.

[0083] Specifically, when the bill trace of the developed invoice in the invoicing record set is performed according to the set of deducted bills, if the developed invoice corresponding to a certain deducted bill does not exist, the remittance amount of the invoice may have been remitted through other channels and not recorded in time, the amount of the invoice has been remitted, and the invoice has been eliminated, so the remittance state of the invoice can be considered as a remitted state.

[0084] In summary, the embodiment of the present application establishes the association between the bill and the billing from the billing dimension, uses the total amount of the issued bill and the unreturned money information to offset the billing-returning money difference information according to the first-in first-out principle of the financial caliber, traces all the unreturned bills and overdue bills, tracks the actual return of each customer and each bill, and realizes the dynamic update of the calculation results at regular intervals, establishes a quantifiable method for calculating the overdue financial of the billing, establishes the association between the bill and the billing, calculates the relevant values from the positive and negative directions respectively, achieves the purpose of financial management, reduces the labor cost of financial supervision, and is applicable to various business modes in practical application, and achieves the technical effects of improving the efficiency and accuracy of the overdue financial supervision of the billing.

[0085] Embodiment two

[0086] Based on the same inventive concept as the method for calculating the overdue billing of the enterprise customer in the foregoing embodiment, as shown in the method for calculating the overdue billing of the enterprise customer in the foregoing embodiment, the embodiment of the present application provides a system for calculating the overdue billing of the enterprise customer, wherein the system comprises: Figure 4 A first obtaining unit 11 is configured to obtain a service customer set of a target enterprise.

[0087] A second obtaining unit 12 is configured to filter the service customer set to obtain an overdue billing customer set.

[0088] A third obtaining unit 13 is configured to obtain a historical bill set of a first customer according to the overdue billing customer set, wherein the first customer is any customer in the overdue billing customer set.

[0089] A first processing unit 14 is configured to obtain the cumulative issued bill and unreturned money information and the billing-returning money difference information of the first customer according to the historical bill set.

[0090] A second processing unit 15 is configured to offset the bills of the billing-returning money difference information based on the cumulative issued bill and unreturned money information until the cumulative issued bill and unreturned money information is offset to zero, and generate a first end instruction.

[0091] A third processing unit 16 is configured to end the offset of the cumulative issued bill and unreturned money information according to the first end instruction, mark the offset bills, and generate an offset bill set.

[0092]

[0093] ​The fourth processing unit 17 is configured to, based on the deducted bill set, trace the invoiced bill of each deducted bill, obtain the remittance state corresponding to the invoiced bill, and dynamically monitor the remittance state.

[0094] Further, the system further comprises:

[0095] The fourth obtaining unit is configured to obtain a cumulative invoiced but not remitted amount set of each service client in the service client set;

[0096] The first judging unit is configured to judge whether each cumulative invoiced but not remitted amount in the cumulative invoiced but not remitted amount set is greater than zero;

[0097] The fifth processing unit is configured to, if each cumulative invoiced but not remitted amount in the cumulative invoiced but not remitted amount set is greater than zero, screen each cumulative invoiced but not remitted amount greater than zero to generate a set of overdue invoiced bills;

[0098] The sixth processing unit is configured to reversely match the set of overdue invoiced bills to obtain the set of invoicing overdue clients corresponding to the set of overdue invoiced bills.

[0099] Further, the system further comprises:

[0100] The fifth obtaining unit is configured to obtain a set of existing bill distributions of a first client according to the set of invoicing overdue clients;

[0101] The sixth obtaining unit is configured to obtain a set of creation time distributions of each existing bill according to the set of existing bill distributions;

[0102] The seventh processing unit is configured to sort the set of creation time distributions based on a first time sequence logic to generate a first creation time sequence;

[0103] The eighth processing unit is configured to sort and reorganize the set of existing bill distributions according to the first creation time sequence to generate the set of historical bills.

[0104] Further, the system further comprises:

[0105] The seventh obtaining unit is configured to obtain first bill information of the first client according to the set of historical bills, wherein the creation time of the first bill information is the latest creation time in the first creation time sequence;

[0106] an eighth obtaining unit, configured to obtain first billing amount information and first collection amount information according to the first billing information;

[0107] a ninth processing unit, configured to perform a difference calculation on the first billing amount information and the first collection amount information to obtain the billing-collection amount difference information.

[0108] Further, the system further comprises:

[0109] a ninth obtaining unit, configured to obtain a billing record set of the first user;

[0110] a tenth processing unit, configured to perform billing tracing on associated invoices in the billing record set based on the deducted billing set to generate an associated invoice set;

[0111] a tenth obtaining unit, configured to obtain a sum of relevant billing collection amounts according to the associated invoice set;

[0112] an eleventh processing unit, configured to calculate a corresponding collection state according to the sum of relevant billing collection amounts.

[0113] Further, the system further comprises:

[0114] a twelfth processing unit, configured to obtain a first collection state and mark the first collection state as an uncollected state if the sum of relevant billing collection amounts is zero;

[0115] a thirteenth processing unit, configured to obtain a second collection state and mark the second collection state as a partially collected state if the sum of relevant billing collection amounts is greater than zero.

[0116] Further, the system further comprises:

[0117] a fourteenth processing unit, configured to obtain a third collection state if the associated invoices in the billing record set do not exist;

[0118] a fifteenth processing unit, configured to mark the third collection state as a collected state.

[0119] Exemplary electronic device

[0120] The electronic device of the embodiments of the present application is described below with reference to Figure 5

[0121] ​Based on the same inventive concept as the method for calculating the invoice overdue of the enterprise client having developed an invoice in the foregoing embodiment, the embodiment of the application further provides a system for calculating the invoice overdue of the enterprise client having developed an invoice, comprising: a processor coupled with a memory, the memory being used for storing a program, when the program is executed by the processor, the system is caused to execute the steps of the method in the embodiment one.

[0122] The electronic device 300 comprises a processor 302, a communication interface 303, and a memory 301. Optionally, the electronic device 300 can further comprise a bus architecture 304. The communication interface 303, the processor 302, and the memory 301 can be connected with each other through the bus architecture 304. The bus architecture 304 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus architecture 304 can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, Figure 5 In the figure, only one thick line is used to represent the bus architecture 304, but it does not mean that there is only one bus or only one type of bus.

[0123] The processor 302 can be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the programs of the schemes of the application.

[0124] The communication interface 303 uses any transceiver-like device for communicating with other devices or communication networks, such as an Ethernet, a radio access network (RAN), a wireless local area network (WLAN), a wired access network, etc.

[0125] The memory 301 can be a ROM, or other type of static storage device that can store static information and instructions, a RAM, or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory can exist independently and be connected to the processor through the bus architecture 304. The memory can also be integrated with the processor.

[0126] The memory 301 is configured to store computer-executed instructions for implementing the solutions of the present application, and the processor 302 is configured to control the execution of the computer-executed instructions stored in the memory 301. The processor 302 is configured to execute the computer-executed instructions stored in the memory 301, so as to implement the method for calculating the invoice overdue of the enterprise customer developed invoices according to the embodiments of the present application.

[0127] Optionally, the computer-executed instructions in the embodiments of the present application can also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

[0128] The embodiments of the present application establish the association between the bills and the invoices from the perspective of the invoice, and use all the information of the invoices that have been issued but not yet paid to deduct the information of the difference between the issued invoices and the paid amount, trace all the unpaid bills and overdue invoices, track the actual payment of each customer for each invoice, and realize the dynamic updating of the calculation results at regular intervals, so as to establish a quantifiable method for calculating the overdue financials of the invoices, establish the association between the bills and the invoices, calculate the relevant values from the positive and negative directions respectively, achieve the purpose of financial management, reduce the labor cost of financial supervision, and be applicable to various business modes in actual application, thereby achieving the technical effects of improving the efficiency and accuracy of the supervision of the overdue financials of the invoices.

[0129] Those skilled in the art can understand that various numbers such as first, second, etc. involved in the present application are only used for the purpose of description and do not limit the scope of the embodiments of the present application, nor indicate the order of sequence. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one" means one or more. At least two means two or more. "At least one", "any one" or similar expressions mean any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c can represent a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0130] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, DVD), or semiconductor media (for example, solid state disk (SSD)) and the like.

[0131] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but, in the alternative, the general purpose processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a

[0132] The steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a terminal. In the alternative, the processor and the storage medium can reside as discrete components in a terminal. The steps of a method or algorithm can be embodied in a software module that can be executed by a processor, and the method or algorithm can be stored in a storage medium or memory that can be coupled to the processor. The software module can comprise a computer program product. The computer program product can comprise a computer readable storage medium having computer readable program instructions stored therein. Figure 1 The steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a terminal. In the alternative, the processor and the storage medium can reside as discrete components in a terminal. The steps of a method or algorithm can be embodied in a software module that can be executed by a processor, and the method or algorithm can be stored in a storage medium or memory that can be coupled to the processor. The software module can comprise a computer program product. The computer program product can comprise a computer readable storage medium having computer readable program instructions stored therein. Figure 1 The steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a terminal. In the alternative, the processor and the storage medium can reside as discrete components in a terminal. The steps of a method or algorithm can be embodied in a software module that can be executed by a processor, and the method or algorithm can be stored in a storage medium or memory that can be coupled to the processor. The software module can comprise a computer program product. The computer program product can comprise a computer readable storage medium having computer readable program instructions stored therein.

[0133] Although the present application has been described in connection with certain specific features and embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the foregoing description. Accordingly, it is intended to embrace all such alternatives, modifications, and variations that fall within the scope of the application. Obviously, many modifications and variations of the present application are possible in light of the above teachings. It is, therefore, to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method of calculating invoice opening age for enterprise customers invoiced, characterized by, The method comprises: obtaining a service customer set of a target enterprise; screening the service customer set to obtain an overdue invoicing customer set; obtaining a historical billing set of a first customer according to the overdue invoicing customer set, wherein the first customer is any customer in the overdue invoicing customer set; obtaining cumulative invoiced but uncollected amount information and invoicing-uncollected amount difference information of the first customer according to the historical billing set; deducting bills of the invoicing-uncollected amount difference information based on the cumulative invoiced but uncollected amount information until the cumulative invoiced but uncollected amount information is deducted to zero, and generating a first end instruction; ending deduction of the cumulative invoiced but uncollected amount information according to the first end instruction, marking deducted bills, and generating a deducted bill set; based on the deducted bill set, associating and tracing the invoiced bills of each deducted bill to obtain the corresponding payment status of the invoiced bills, and dynamically monitoring the payment status.

2. The method of claim 1, wherein, The screening of the service customer set comprises: obtaining a cumulative invoiced but uncollected amount set of each service customer in the service customer set; determining whether each cumulative invoiced but uncollected amount in the cumulative invoiced but uncollected amount set is greater than zero; if each cumulative invoiced but uncollected amount in the cumulative invoiced but uncollected amount set is greater than zero, screening each cumulative invoiced but uncollected amount greater than zero to generate an overdue invoiced bill set; performing reverse matching on the overdue invoiced bill set to obtain the overdue invoicing customer set corresponding to the overdue invoiced bill set.

3. The method of claim 1, wherein, The obtaining of the historical billing set of the first customer comprises: obtaining an existing billing distribution set of the first customer according to the overdue invoicing customer set; obtaining a creation time distribution set of each existing bill according to the existing billing distribution set; sorting the creation time distribution set based on a first time sequence logic to generate a first creation time sequence; reorganizing the existing billing distribution set according to the first creation time sequence to generate the historical billing set.

4. The method of claim 1, wherein, The invoicing-uncollected amount difference information comprises: obtaining first billing information of the first customer according to the historical billing set, wherein the creation time of the first billing information is the latest creation time in the first creation time sequence; obtaining first invoicing amount information and first uncollected amount information according to the first billing information; calculating the difference between the first invoicing amount information and the first uncollected amount information to obtain the invoicing-uncollected amount difference information.

5. The method of claim 1, wherein, The associating and tracing of the invoiced bills of each deducted bill comprises: obtaining an invoicing record set of the first customer; based on the deducted bill set, performing billing tracing on the associated invoiced bills in the invoicing record set to generate an associated invoiced bill set; obtaining the sum of related billing uncollected amounts according to the associated invoiced bill set; calculating the corresponding payment status according to the sum of related billing uncollected amounts.

6. The method of claim 5, wherein, The calculation obtains a corresponding repayment state, including: If the sum of the relevant bill repayment amounts is zero, a first repayment state is obtained, and the first repayment state is marked as an un-repayment state; If the sum of the relevant bill repayment amounts is greater than zero, a second repayment state is obtained, and the second repayment state is marked as a partial repayment state.

7. The method of claim 5, wherein, Bill tracing is performed on the associated invoiced in the set of invoice records, including: If the associated invoiced in the set of invoice records does not exist, a third repayment state is obtained; The third repayment state is marked as a repayment state.

8. A system for calculating invoice opening delinquencies for enterprise customers who have invoiced, characterized by, The system includes: A first obtaining unit is configured to obtain a set of service customers of a target enterprise; A second obtaining unit is configured to filter the set of service customers to obtain a set of invoicing overdue customers; A third obtaining unit is configured to obtain a set of historical bills of a first customer according to the set of invoicing overdue customers, wherein the first customer is any customer in the set of invoicing overdue customers; A first processing unit is configured to obtain cumulative invoiced-unrepaid amount information and invoicing-repayment amount difference information of the first customer according to the set of historical bills; A second processing unit is configured to deduct bills of the invoicing-repayment amount difference information based on the cumulative invoiced-unrepaid amount information until the cumulative invoiced-unrepaid amount information is deducted to zero, and generate a first end instruction; A third processing unit is configured to end the deduction of the cumulative invoiced-unrepaid amount information according to the first end instruction, mark the deducted bills, and generate a set of deducted bills; A fourth processing unit is configured to associate and trace the invoiced of each deducted bill based on the set of deducted bills, obtain a repayment state corresponding to the invoiced, and dynamically monitor the repayment state.

9. A system for calculating invoice opening delinquencies for enterprise customers who have invoiced, characterized by, It includes: A processor coupled with a memory, the memory being configured to store a program, when the program is executed by the processor, the system is configured to perform the steps of the method according to any one of claims 1 to 7.

Images