Invoice cancellation method, device, electronic device and storage medium

Abstract

The present application provides an invoice cancellation method, device, electronic device and storage medium, the method comprising: obtaining the invoice to be cancelled corresponding to the target customer within the target cancellation cycle; determining the oil bill identification corresponding to each oil bill in the invoice to be cancelled, obtaining the oil bill collection record corresponding to each oil bill based on the oil bill identification, the invoice to be cancelled includes the amount receivable of each oil bill; for each oil bill, determining the confirmation collection information corresponding to the oil bill based on the oil bill collection record of the oil bill, the oil bill collection record is used to associate the oil bill with the confirmation collection information corresponding to the oil bill, the confirmation collection information includes the actual amount received of the oil bill; comparing the actual amount received of the oil bill with the amount receivable of the oil bill in the invoice to be cancelled, and generating the cancellation record of the target customer within the target cancellation cycle based on the comparison result. By adopting the above-mentioned invoice cancellation method, device, electronic device and storage medium, the problem of low invoice cancellation efficiency in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the technical field of financial management, and in particular to an invoice cancellation method, device, electronic device and storage medium. Background Art

[0002] Payment verification is a work to calculate and record the matching of sales and receipts. It is an important way to ensure accurate settlement and clear accounts. The verification of aircraft refueling in aviation fuel companies is to match the sales amount of fuel products with the amount of receipts. In daily work, aviation fuel companies mainly verify invoices manually based on the payment list provided by customers.

[0003] However, when manually reconciling invoices based on payment lists, it is necessary to manually select and match invoice information, resulting in low invoice reconciliation efficiency. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide an invoice verification method, device, electronic device and storage medium to solve the problem of low invoice verification efficiency.

[0005] In a first aspect, an embodiment of the present application provides an invoice cancellation method, comprising:

[0006] Obtain the invoices to be written off corresponding to the target customers within the target write-off cycle;

[0007] Determine the oil bill ID corresponding to each oil bill in the invoice to be written off, and obtain the oil bill collection record corresponding to each oil bill based on the oil bill ID. The invoice to be written off includes the receivable amount of each oil bill.

[0008] For each oil bill, determining the confirmation receipt information corresponding to the oil bill based on the oil bill receipt record of the oil bill, the oil bill receipt record is used to associate the oil bill with the confirmation receipt information corresponding to the oil bill, and the confirmation receipt information includes the actual receipt amount of the oil bill;

[0009] The actual amount collected on the oil bill is compared with the receivable amount of the oil bill in the invoice to be written off, and the write-off record of the target customer within the target write-off cycle is generated based on the comparison result.

[0010] Optionally, before obtaining the invoices to be written off corresponding to the target customer within the target write-off cycle, it also includes: for each oil bill, generating confirmation receipt information of the oil bill when the target customer successfully pays the payment for the oil bill; associating the oil bill with the corresponding confirmation receipt information to generate an oil bill receipt record for the oil bill.

[0011] Optionally, obtaining the invoices to be written off corresponding to the target customers within the target writing-off cycle includes: generating invoices corresponding to all customers on that day at a preset time point every day; treating all customers' unwritten invoices on different dates as historical invoices to be written off; and selecting the invoices to be written off corresponding to the target customer's customer ID and the target writing-off cycle from the historical invoices to be written off as the invoices to be written off for the target customers within the target writing-off period.

[0012] Optionally, the confirmation receipt information includes a fuel bill identification; the fuel bill is associated with the corresponding confirmation receipt information to generate a fuel bill receipt record of the fuel bill, including: extracting the fuel bill identification and the confirmation receipt information identification of the fuel bill from the confirmation receipt information; matching the fuel bill identification with the confirmation receipt information identification to generate a fuel bill receipt record of the fuel bill.

[0013] Optionally, based on the comparison results, a write-off record for the target customer within the target write-off cycle is generated, including: for each oil order in the invoice to be written off, if the actual amount collected in the confirmation receipt information corresponding to the oil order is the same as the amount receivable of the oil order in the invoice to be written off, it is determined that the oil order has been successfully written off and the write-off is marked as successful; if the actual amount collected in the confirmation receipt information corresponding to the oil order is not the same as the amount receivable of the oil order in the invoice to be written off, it is determined that the oil order has failed to be written off and the write-off is marked as failed.

[0014] Optionally, before the target customer successfully pays the purchase price of the oil order and generates the confirmation receipt information of the oil order, it also includes: when the oil purchase transaction is reached, generating the oil order corresponding to the oil purchase transaction; according to the payment method agreed in the customer agreement, obtaining the payment paid by the target customer to generate the confirmation receipt information of the oil order.

[0015] Optionally, before determining the confirmation receipt information corresponding to the oil bill based on the oil bill receipt record of the oil bill, it also includes: if there is no corresponding oil bill receipt record for the oil bill, determining that the oil bill verification has failed.

[0016] In a second aspect, the embodiment of the present application further provides an invoice cancellation device, the device comprising:

[0017] Invoice acquisition module, used to obtain the invoices to be written off corresponding to the target customers within the target write-off cycle;

[0018] A collection record acquisition module is used to determine the oil bill identifier corresponding to each oil bill in the invoice to be written off, and obtain the oil bill collection record corresponding to each oil bill based on the oil bill identifier. The invoice to be written off includes the receivable amount of each oil bill;

[0019] A payment information determination module is used to determine, for each oil bill, the confirmed payment information corresponding to the oil bill based on the oil bill payment record of the oil bill, the oil bill payment record is used to associate the oil bill with the confirmed payment information corresponding to the oil bill, and the confirmed payment information includes the actual payment amount of the oil bill;

[0020] The invoice cancellation module is used to compare the actual amount collected on the oil bill with the receivable amount of the oil bill in the invoice to be cancelled, and generate a cancellation record for the target customer within the target cancellation cycle based on the comparison result.

[0021] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the invoice verification method as described above are performed.

[0022] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the invoice verification method as described above are executed.

[0023] The embodiments of the present application bring the following beneficial effects:

[0024] An invoice cancellation method, device, electronic device and storage medium provided in the embodiments of the present application can determine the oil bill collection record of each oil bill within the target cancellation period based on the invoices to be cancelled within the target cancellation period, use the oil bill collection record to determine the actual collection amount of the oil bill, compare the actual collection amount of each oil bill with the receivable amount of the oil bill in the invoice to be cancelled, and determine the cancellation result of the invoice to be cancelled based on the comparison result. Compared with the invoice cancellation method in the prior art, the problem of low invoice cancellation efficiency is solved.

[0025] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1 A flow chart of the invoice cancellation method provided in an embodiment of the present application is shown;

[0028] Figure 2 A schematic diagram showing the structure of an invoice cancellation device provided in an embodiment of the present application is shown;

[0029] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0030] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0031] It is worth noting that before this application was filed, payment verification was a work of calculating and recording the matching of sales and payments, and was an important way to ensure accurate settlement and clear accounts. The verification of aircraft refueling in aviation fuel companies is the matching of the amount of oil sales and the amount of payments received. In daily work, aviation fuel companies mainly verify invoices manually based on the payment list provided by customers. However, when manually verifying based on the payment list, it is necessary to manually select and match the invoice information, resulting in low efficiency in invoice verification.

[0032] Based on this, an embodiment of the present application provides an invoice cancellation method to improve the efficiency of invoice cancellation.

[0033] See also Figure 1 , Figure 1 This is a flow chart of an invoice cancellation method provided in an embodiment of the present application. Figure 1 As shown, the invoice cancellation method provided in the embodiment of the present application includes:

[0034] Step S101, obtaining the invoices to be written off corresponding to the target customer within the target write-off cycle.

[0035] In this step, the target write-off cycle may refer to a time interval for writing off invoices, and the target write-off cycle is used to determine which dates' invoices are to be written off.

[0036] Exemplarily, the duration of the target write-off period may be one month or one week. For example, the target write-off period may be a time interval of one month before the current date.

[0037] Take the invoice settlement of an aviation fuel company as an example. Different airlines purchase dirty gasoline from the aviation fuel company. These airlines are the customers of the aviation fuel company. When the invoices of airline X within the target settlement period are settled, airline X is the target customer.

[0038] In an optional embodiment, obtaining the invoices to be written off corresponding to the target customer within the target writing-off period includes: generating invoices corresponding to all customers on the day at a preset time point each day; treating all customers' unwritten invoices on different dates as historical invoices to be written off; and selecting the invoices to be written off corresponding to the customer identification of the target customer and the target writing-off period from the historical invoices to be written off as the invoices to be written off for the target customer within the target writing-off period.

[0039] Here, the historical invoices to be written off may refer to the unwritten invoices from different customers on different dates.

[0040] Taking the above example, suppose that Airline Company X reached 1,000 aviation gasoline transactions with the aviation fuel company last month. Each aviation gasoline transaction corresponds to a fuel bill, and there are 1,000 fuel bills in total. This requires the invoices corresponding to each fuel bill to be written off. Among them, the invoice is automatically generated by the system at the preset time point every day. For example, at 24:00 every night, the invoices of all fuel bills of different airlines on that day are automatically generated. These invoices include the invoice of Airline Company X. The invoice of Airline Company X can be selected from all the invoices generated and not written off last month as the invoice to be written off.

[0041] In an optional embodiment, before obtaining the invoices to be written off corresponding to the target customer within the target write-off cycle, it also includes: for each oil bill, generating confirmation receipt information of the oil bill when the target customer successfully pays the payment for the oil bill; associating the oil bill with the corresponding confirmation receipt information to generate an oil bill receipt record for the oil bill.

[0042] Here, the confirmed payment information may refer to the record of actual payment information, and the confirmed payment information is used to determine the actual amount received.

[0043] The payment confirmation information includes but is not limited to: oil receipt identification, payment confirmation information identification, payment amount, customer name, and payment time.

[0044] The fuel receipt payment record is used to establish the association between the fuel receipt and the confirmation receipt information.

[0045] Specifically, the fuel slip records the time of the transaction, the tonnage of aviation gasoline purchased, the amount receivable, the customer name and other information. When the target customer successfully pays the corresponding amount according to the information in the fuel slip, the system will generate confirmation receipt information based on the amount received, customer name, time of receipt and other information, and associate the confirmation receipt information with the corresponding fuel slip to obtain the fuel slip receipt record, so as to trace back the actual receipt amount of the fuel slip based on the fuel slip receipt record.

[0046] In an optional embodiment, the confirmation receipt information includes a fuel bill identification; the fuel bill is associated with the corresponding confirmation receipt information to generate a fuel bill receipt record for the fuel bill, including: extracting the fuel bill identification and the confirmation receipt information identification of the fuel bill from the confirmation receipt information; matching the fuel bill identification with the confirmation receipt information identification to generate a fuel bill receipt record for the fuel bill.

[0047] Here, the oil bill identifier may refer to a unique identifier of the oil bill, and the oil bill identifier is used to distinguish different oil bills.

[0048] Exemplarily, the oil slip identifier may be the oil slip number.

[0049] Specifically, since the confirmation receipt information records the fuel slip identifier and the confirmation receipt information identifier of the confirmation receipt information, the fuel slip identifier and the confirmation receipt information identifier are extracted from the confirmation receipt information, and the two are combined together to generate a fuel slip receipt record to establish the association relationship between the fuel slip and the confirmation receipt information.

[0050] In an optional embodiment, before the target customer successfully pays the purchase price of the oil order and generates the confirmation receipt information of the oil order, it also includes: when the oil purchase transaction is reached, generating the oil order corresponding to the oil purchase transaction; according to the payment method agreed in the customer agreement, obtaining the payment paid by the target customer to generate the confirmation receipt information of the oil order.

[0051] Specifically, each time a purchase transaction is concluded, the system will generate a fuel bill and submit the bill to the customer for confirmation. After the customer confirms, the system will collect the corresponding amount of payment according to the payment method agreed in the customer agreement signed with the customer. After the payment is successfully collected, the corresponding confirmation receipt information of the fuel bill will be generated based on the amount of payment received, the payment time, the name of the customer who paid the payment, and other information.

[0052] In an optional embodiment, the payment made by the target customer is obtained according to the payment method agreed upon in the customer agreement, including: if the payment method specified in the customer agreement is the first payment method, the payment corresponding to the payable amount in the oil bill is automatically deducted from the bank account specified in the customer agreement; if the payment method specified in the customer agreement is the second payment method, the oil bill is sent to the target customer so that the target customer pays the corresponding payment according to the payable amount in the oil bill.

[0053] Here, the first payment method may refer to a payment method in which the system automatically deducts money from a bank account designated by the customer.

[0054] The second payment method may refer to the payment method used by the customer to transfer funds.

[0055] Specifically, in the customer agreement signed between the aviation fuel company and the target customer, a specific payment method is agreed upon. There are two payment methods, namely the first payment method and the second payment method.

[0056] If it is the first payment method, after the oil bill is generated and confirmed by the customer, the system automatically deducts the corresponding amount of payment from the bank account designated by the target customer to complete the real-time settlement payment of the oil bill.

[0057] If it is the second payment method, after the fuel bill is generated and confirmed by the customer, the fuel bill will be sent to the target customer, and the target customer will automatically transfer the payable amount in the fuel bill to the bank account designated by the aviation fuel company to complete the real-time settlement payment of the fuel bill.

[0058] Step S102, determining the oil bill identification corresponding to each oil bill in the invoice to be written off, and obtaining the oil bill collection record corresponding to each oil bill based on the oil bill identification.

[0059] In this step, the invoices to be written off include but are not limited to: the receivable amount of each oil bill, the oil bill identification, the customer name of the target customer, and the invoice date.

[0060] In the implementation example of the present application, the oil bill identification of the oil bill to be settled is recorded in the invoice to be written off. Assuming that there are 5 oil bills for the invoice to be written off, the oil bill identifications of these oil bills are extracted respectively, namely oil bill identification A, oil bill identification B, oil bill identification C, oil bill identification D, and oil bill identification E, and the oil bill collection record a matching the oil bill identification A, the oil bill collection record b matching the oil bill identification B, the oil bill collection record c matching the oil bill identification C, the oil bill collection record d matching the oil bill identification D, and the oil bill collection record e matching the oil bill identification E are found from the historical oil bill collection records.

[0061] Step S103, for each fuel bill, determining the confirmation receipt information corresponding to the fuel bill based on the fuel bill receipt record of the fuel bill.

[0062] In this step, the oil receipt payment record is used to associate the oil receipt with the confirmation payment information corresponding to the oil receipt, and the confirmation payment information includes the actual payment amount of the oil receipt.

[0063] Taking the above example, assuming that the confirmation receipt information in the fuel bill receipt record a is identified as F, the confirmation receipt information in the fuel bill receipt record b is identified as G, the confirmation receipt information in the fuel bill receipt record c is identified as H, the confirmation receipt information in the fuel bill receipt record d is identified as I, and the confirmation receipt information in the fuel bill receipt record e is identified as J, then the corresponding confirmation receipt information F is determined for the fuel bill identification A, the corresponding confirmation receipt information G is determined for the fuel bill identification B, the corresponding confirmation receipt information H is determined for the fuel bill identification C, the corresponding confirmation receipt information I is determined for the fuel bill identification D, and the corresponding confirmation receipt information J is determined for the fuel bill identification E.

[0064] In this way, the confirmation receipt information corresponding to each oil order can be determined. If no corresponding confirmation receipt information is found for a certain oil order, it means that the target customer has not paid the corresponding payment for the oil order.

[0065] In an optional implementation example, before determining the confirmation receipt information corresponding to the oil bill based on the oil bill receipt record of the oil bill, it also includes: if there is no corresponding oil bill receipt record for the oil bill, determining that the oil bill cancellation has failed.

[0066] Specifically, if the fuel receipt record corresponding to a fuel order is not found, it means that the aviation fuel company has not received the payment paid by the target customer for the fuel order, or the payment for the fuel order is 0, so when the invoice is written off for the fuel order, it is determined that the fuel order has failed to be written off.

[0067] Step S104, comparing the actual amount collected on the oil bill with the receivable amount on the oil bill in the invoice to be written off, and generating a write-off record for the target customer within a target write-off cycle based on the comparison result.

[0068] In this step, the actual amount received in the confirmed receipt information is compared with the receivable amount of the oil bill in the invoice to be written off. If the two are the same, it means that the target customer has paid the corresponding amount according to the oil bill. If the two are different, it means that the target customer has not paid the corresponding amount according to the oil bill. The target customer may have overpaid or underpaid.

[0069] In an optional embodiment, a write-off record of a target customer within a target write-off cycle is generated based on the comparison result, including: for each oil slip in the invoice to be written off, if the actual amount collected in the confirmation receipt information corresponding to the oil slip is the same as the amount receivable of the oil slip in the invoice to be written off, it is determined that the oil slip is successfully written off and marked as a successful write-off; if the actual amount collected in the confirmation receipt information corresponding to the oil slip is not the same as the amount receivable of the oil slip in the invoice to be written off, it is determined that the oil slip has failed to be written off and marked as a failed write-off.

[0070] Specifically, if the actual amount collected corresponding to a certain oil order is equal to the receivable amount of the oil order in the invoice to be written off, it means that the target customer has successfully paid the corresponding amount of goods, and it can be determined that the oil order has been successfully written off. Therefore, the oil order and the confirmation receipt information corresponding to the oil order are marked as successfully written off, for example, with the symbol "√".

[0071] If the actual amount collected corresponding to a certain oil order is not equal to the amount receivable of the oil order in the invoice to be written off or the confirmation receipt information of the oil order is not found, it means that the target customer has not successfully paid the corresponding amount of goods. It can be determined that the oil order has failed to be written off. Therefore, the oil order and the confirmation receipt information corresponding to the oil order are marked as failed to be written off, for example, they are marked with the symbol "×".

[0072] Compared with the invoice cancellation method in the prior art, the present application can determine the oil bill collection record of each oil bill within the target cancellation period based on the invoices to be cancelled within the target cancellation period, use the oil bill collection record to determine the actual collected amount of the oil bill, compare the actual collected amount of each oil bill with the receivable amount of the oil bill in the invoice to be cancelled, and determine the cancellation result of the invoice to be cancelled based on the comparison result, thereby solving the problem of low invoice cancellation efficiency.

[0073] Based on the same inventive concept, an invoice cancellation device corresponding to the invoice cancellation method is also provided in the embodiment of the present application. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned invoice cancellation method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0074] See also Figure 2 , Figure 2 This is a schematic diagram of the structure of an invoice cancellation device provided in an embodiment of the present application. Figure 2 As shown in , the invoice cancellation device 200 includes:

[0075] Invoice acquisition module 201, used to acquire the invoices to be written off corresponding to the target customer within the target write-off cycle;

[0076] A payment record acquisition module 202 is used to determine the oil bill identifier corresponding to each oil bill in the invoice to be written off, and acquire the oil bill payment record corresponding to each oil bill based on the oil bill identifier, wherein the invoice to be written off includes the receivable amount of each oil bill;

[0077] A payment information determination module 203 is used to determine, for each oil bill, the confirmed payment information corresponding to the oil bill based on the oil bill payment record of the oil bill, wherein the oil bill payment record is used to associate the oil bill with the confirmed payment information corresponding to the oil bill, and the confirmed payment information includes the actual payment amount of the oil bill;

[0078] The invoice cancellation module 204 is used to compare the actual amount collected on the oil bill with the receivable amount of the oil bill in the invoice to be cancelled, and generate a cancellation record of the target customer within a target cancellation cycle based on the comparison result.

[0079] In an optional embodiment, the invoice verification device 200 also includes a record generation module (not shown in the figure), which is specifically used to: for each oil order, generate confirmation receipt information of the oil order when the target customer successfully pays the payment for the oil order; associate the oil order with the corresponding confirmation receipt information to generate an oil order receipt record for the oil order.

[0080] In an optional embodiment, the invoice acquisition module 201 is also specifically used to: generate invoices corresponding to all customers on that day at a preset time point every day; treat all customers' unreconciled invoices on different dates as historical invoices to be reconciled; and select invoices to be reconciled corresponding to the customer identification of the target customer and the target reconciliation period from the historical invoices to be reconciled as the invoices to be reconciled for the target customer within the target reconciliation period.

[0081] In an optional embodiment, the confirmation receipt information includes a fuel bill identifier; the record generation module is also specifically used to: extract the fuel bill identifier in the confirmation receipt information and the receipt identifier in the confirmation receipt information; match the fuel bill identifier with the receipt identifier to generate the fuel bill receipt record of the fuel bill.

[0082] In an optional embodiment, the invoice cancellation module 204 is also specifically used for: for each oil order in the invoice to be cancelled, if the actual amount collected in the confirmation of receipt information corresponding to the oil order is the same as the amount receivable of the oil order in the invoice to be cancelled, it is determined that the oil order is cancelled successfully and the cancellation is marked as successful; if the actual amount collected in the confirmation of receipt information corresponding to the oil order is different from the amount receivable of the oil order in the invoice to be cancelled, it is determined that the oil order has failed to be cancelled and the cancellation is marked as failed.

[0083] In an optional embodiment, the invoice verification device 200 also includes a payment acquisition module (not shown in the figure), which is specifically used to: generate an oil bill corresponding to the oil purchase transaction when the oil purchase transaction is concluded; obtain the payment paid by the target customer according to the payment method agreed in the customer agreement to generate confirmation receipt information of the oil bill.

[0084] In an optional embodiment, the invoice cancellation module 204 is further specifically used for: if there is no corresponding oil bill payment record for the oil bill, determining that the oil bill cancellation has failed.

[0085] See also Figure 3 , Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 3As shown in , the electronic device 300 includes a processor 310 , a memory 320 and a bus 330 .

[0086] The memory 320 stores machine-readable instructions executable by the processor 310. When the electronic device 300 is running, the processor 310 communicates with the memory 320 via the bus 330. When the machine-readable instructions are executed by the processor 310, the above-mentioned Figure 1 The specific implementation of the steps of the invoice cancellation method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0087] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The specific implementation of the steps of the invoice cancellation method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0088] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0089] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0090] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0091] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0092] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0093] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. An invoice cancellation method, characterized in that: include: Obtain the invoices to be written off corresponding to the target customers within the target write-off cycle; Determine the oil bill identifier corresponding to each oil bill in the invoice to be written off, and obtain the oil bill collection record corresponding to each oil bill based on the oil bill identifier, wherein the invoice to be written off includes the receivable amount of each oil bill; For each oil bill, determining the confirmation receipt information corresponding to the oil bill based on the oil bill receipt record of the oil bill, wherein the oil bill receipt record is used to associate the oil bill with the confirmation receipt information corresponding to the oil bill, and the confirmation receipt information includes the actual receipt amount of the oil bill; Compare the actual amount collected on the oil bill with the receivable amount on the oil bill in the invoice to be written off, and generate a write-off record for the target customer within a target write-off cycle based on the comparison result; Before obtaining the invoices to be written off corresponding to the target customer within the target write-off cycle, the method further includes: For each oil order, when the target customer successfully pays the price of the oil order, the confirmation receipt information of the oil order is generated, and the confirmation receipt information includes the oil order identification; Extracting the fuel receipt identifier and the payment confirmation information identifier of the fuel receipt from the payment confirmation information; The oil bill identification is matched with the confirmation receipt information identification to generate the oil bill receipt record of the oil bill.

2. The method according to claim 1, characterized in that The obtaining of the invoices to be written off corresponding to the target customer within the target write-off cycle includes: Generate invoices for all customers of the day at a preset time each day; Treat all customers' unreconciled invoices on different dates as historical invoices to be reconciled; From the historical invoices to be written off, the invoices to be written off corresponding to the customer identifier of the target customer and the target writing-off period are selected as the invoices to be written off of the target customer within the target writing-off period.

3. The method according to claim 1, characterized in that The generating of the write-off record of the target customer within the target write-off period based on the comparison result includes: For each oil slip in the invoice to be written off, if the actual amount received in the confirmation receipt information corresponding to the oil slip is the same as the receivable amount of the oil slip in the invoice to be written off, it is determined that the oil slip is successfully written off and marked as successfully written off; If the actual amount collected in the confirmation receipt information corresponding to the oil bill is different from the receivable amount of the oil bill in the invoice to be written off, it is determined that the oil bill has failed to be written off and a mark of failure is made.

4. The method according to claim 1, characterized in that: Before generating the confirmation receipt information of the oil bill when the target customer successfully pays the payment for the oil bill, the method further includes: When the oil purchase transaction is completed, an oil bill corresponding to the oil purchase transaction is generated; According to the payment method agreed in the customer agreement, the payment made by the target customer is obtained to generate the confirmation receipt information of the oil bill.

5. The method according to claim 1, characterized in that Before determining the confirmed payment information corresponding to the oil bill based on the oil bill payment record of the oil bill, the method further includes: If there is no corresponding oil bill payment record for the oil bill, it is determined that the oil bill cancellation has failed.

6. An invoice cancellation device, characterized in that: include: Invoice acquisition module, used to obtain the invoices to be written off corresponding to the target customers within the target write-off cycle; A collection record acquisition module, used to determine the oil bill identifier corresponding to each oil bill in the invoice to be written off, and acquire the oil bill collection record corresponding to each oil bill based on the oil bill identifier, wherein the invoice to be written off includes the receivable amount of each oil bill; A payment information determination module, for each oil bill, determining the confirmed payment information corresponding to the oil bill based on the oil bill payment record of the oil bill, wherein the oil bill payment record is used to associate the oil bill with the confirmed payment information corresponding to the oil bill, and the confirmed payment information includes the actual payment amount of the oil bill; An invoice write-off module, used to compare the actual amount collected on the oil bill with the receivable amount of the oil bill in the invoice to be written off, and generate a write-off record for the target customer within a target write-off cycle based on the comparison result; The invoice acquisition module is also used for: For each oil order, when the target customer successfully pays the price of the oil order, payment confirmation information of the oil order is generated, and the payment confirmation information includes an oil order identifier; Extracting the fuel receipt identifier and the payment confirmation information identifier of the fuel receipt from the payment confirmation information; The oil bill identification is matched with the confirmation receipt information identification to generate the oil bill receipt record of the oil bill.

7. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the storage medium communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of the invoice verification method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the invoice verification method according to any one of claims 1 to 5 are executed.

Images