Computer-implemented invoice processing method, device and storage medium

Abstract

A computer-implemented invoice processing method, device and storage medium are provided. The method includes: determining a business category corresponding to a business for which an invoice is to be generated; selecting one or more fields related to the business category from a field set including various fields based at least on the business category, and setting default information for the selected one or more fields based at least on the business category; and generating an invoice template corresponding to the business category based on the selected one or more fields and the default information set for the one or more fields, wherein the invoice template is used to generate an invoice for the business.

Description

Technical Field

[0001] The present disclosure relates to a computer-implemented invoice processing method, device and storage medium. Background Art

[0002] In the course of conducting business activities, invoices need to be processed for various purposes, such as customs declaration. Due to the diversity of business, various different information is required in the process of invoice processing. In addition, due to the huge number of businesses, the number of invoices that need to be processed is also huge. Therefore, invoice processing is a complicated task. How to process invoices efficiently and conveniently has become a challenging issue.

[0003] In view of at least the foregoing, a need exists for improvements in invoice processing. Summary of the invention

[0004] The present disclosure proposes a computer-implemented invoice processing method, device and storage medium.

[0005] According to some embodiments of the present disclosure, a computer-implemented invoice processing method is provided, comprising: determining a business category corresponding to a business for which an invoice is to be generated; selecting one or more fields related to the business category from a field set including various fields based at least on the business category, and setting default information for the selected one or more fields based at least on the business category; generating an invoice template corresponding to the business category based on the selected one or more fields and the default information set for the one or more fields; and generating an invoice for the business using the invoice template.

[0006] According to some embodiments of the present disclosure, the business category includes a service category or a product category.

[0007] According to some embodiments of the present disclosure, in the case where the business category is a product category, selecting one or more fields related to the business category from a field set including various fields at least based on the business category and setting default information for the selected one or more fields at least based on the business category includes: determining a product type corresponding to the product category; and selecting one or more fields related to the product type from a field set including various fields based on the product category and the product type, and setting default information for the selected one or more fields based on the product category and the product type.

[0008] According to some embodiments of the present disclosure, the product categories include one or more of complete vehicles, spare parts, car bodies, and powertrain components.

[0009] According to some embodiments of the present disclosure, the product type includes one or more of a vehicle model, a spare part model, a vehicle body model, and a powertrain component model.

[0010] According to some embodiments of the present disclosure, determining the product type corresponding to the product category includes: when the product category is a complete vehicle, determining the vehicle type corresponding to the complete vehicle; when the product category is spare parts, determining the spare parts model corresponding to the spare parts; when the product category is a vehicle body, determining the vehicle body model corresponding to the vehicle body; and when the product category is a powertrain component, determining the powertrain component model corresponding to the powertrain component.

[0011] According to some embodiments of the present disclosure, each of the various fields has a default information flag, and the default information flag is used to indicate whether to turn on or off the default information of each field.

[0012] According to some embodiments of the present disclosure, each of the various fields has a field number, and the field number is used to uniquely identify each field.

[0013] According to some embodiments of the present disclosure, the invoice template has an invoice template name, and the invoice template name is generated based on the business category.

[0014] According to some embodiments of the present disclosure, when the business category is a product category, a product type corresponding to the product category is determined, and the invoice template name is generated based on both the business category and the product type.

[0015] According to some embodiments of the present disclosure, using the invoice template to generate an invoice for a business includes: automatically calling a corresponding invoice template to generate an invoice for the business based on a business requirement for generating an invoice.

[0016] According to some embodiments of the present disclosure, the business demand includes one or more of the following: an export request, a transportation plan, and a delivery plan.

[0017] According to some embodiments of the present disclosure, automatically calling a corresponding invoice template to generate an invoice for a business based on a business requirement that requires generating an invoice includes: automatically calling an invoice template corresponding to a business category based on a business category corresponding to the business included in the business requirement; obtaining detailed information related to the business included in the business requirement from various data sources using trigger information included in the business requirement; and automatically filling in corresponding fields in the called invoice template using the obtained detailed information related to the business included in the business requirement.

[0018] According to some embodiments of the present disclosure, automatically calling an invoice template corresponding to a business category based on the business category corresponding to the business included in the business requirement includes: comparing the business category corresponding to the business included in the business requirement with the invoice template name of the invoice template; based on the comparison, selecting an invoice template whose invoice template name best matches the business category corresponding to the business included in the business requirement; and automatically calling the selected invoice template.

[0019] According to some embodiments of the present disclosure, in the case where the business category corresponding to the business included in the business requirement is a product category, determining the product type corresponding to the product category, and automatically calling the invoice template corresponding to the business category based on the business category corresponding to the business included in the business requirement includes: comparing the business category and product type corresponding to the business included in the business requirement with the invoice template name of the invoice template; based on the comparison, selecting the invoice template whose invoice template name best matches the business category and product type corresponding to the business included in the business requirement; and automatically calling the selected invoice template.

[0020] According to some embodiments of the present disclosure, the trigger information includes a business identification number included in the business requirement, and the data source includes one or more of the following: an export data source, a logistics data source, a production data source, and a sales data source.

[0021] According to some embodiments of the present disclosure, the invoice processing method also includes: modifying or inputting the values ​​of each field in the automatically filled invoice template; and generating a first invoice including a cover and business items using the values ​​of each field in the modified or input invoice template and according to a predetermined layout style of the invoice.

[0022] According to some embodiments of the present disclosure, when the business requirements include multiple businesses of the same business category, the invoice processing method also includes: generating a common cover for the multiple businesses of the same business category; generating multiple invoice items, each of the multiple invoice items corresponds to each business of the multiple businesses of the same business category and includes an actual invoice number; and generating a second invoice including the common cover and the multiple invoice items, wherein the second invoice includes a virtual invoice number.

[0023] According to some embodiments of the present disclosure, when the business category includes a product category, the invoice processing method further includes: utilizing the generated invoice and automatically generating a packing list of products corresponding to the generated invoice according to a predetermined packing list typesetting style.

[0024] According to some embodiments of the present disclosure, the method of automatically generating a packing list of products corresponding to the generated invoice using the generated invoice and according to a predetermined packing list typeset style includes: obtaining first information of a first field in the packing list that is the same as a field in the invoice from the generated invoice; obtaining second information of a second field in the packing list that is different from the field in the invoice from various data sources using a product identification number included in the generated invoice; and automatically generating a packing list of products corresponding to the generated invoice using the first information and the second information and according to a predetermined packing list typeset style.

[0025] According to some embodiments of the present disclosure, the generated invoice and / or the generated packing list can be stored in a computer system and can be browsed, queried, downloaded or printed by various parties.

[0026] According to some embodiments of the present disclosure, a computer storage medium is provided, on which computer instructions are stored. When the computer instructions are executed by a computer, the computer is caused to execute the invoice processing method as described in any one of the above items.

[0027] According to some embodiments of the present disclosure, a computer-implemented invoice processing is provided, comprising: a memory storing computer instructions; and a processor coupled to the memory, executing the computer instructions to perform the invoice processing method as described in any one of the foregoing items.

[0028] By using the computer-implemented invoice processing method, device and storage medium disclosed in the present invention, invoice processing can be performed quickly and conveniently, thereby improving the efficiency of invoice processing and improving the convenience of use for users.

[0029] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0031] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0032] Figure 1 is a flow chart schematically illustrating a computer-implemented invoice processing method according to an embodiment of the present disclosure.

[0033] Figure 2 is a flow chart schematically illustrating a process for processing an invoice based on a product category and a product type according to an embodiment of the present disclosure.

[0034] Figure 3 is a flowchart schematically illustrating a process for determining a product type according to an embodiment of the present disclosure.

[0035] Figure 4 is an exemplary diagram schematically illustrating various fields in a field set according to an embodiment of the present disclosure.

[0036] Figure 5 is an exemplary diagram schematically illustrating an invoice template according to an embodiment of the present disclosure.

[0037] Figure 6 is a flow chart schematically illustrating a process for generating an invoice according to an embodiment of the present disclosure.

[0038] Figure 7 is a flowchart schematically illustrating a process for calling an invoice template to generate an invoice according to an embodiment of the present disclosure.

[0039] Figure 8 is a flow chart schematically illustrating a computer-implemented process for invoking an invoice template according to an embodiment of the present disclosure.

[0040] Fig. 9 is a flow chart schematically illustrating another process for calling an invoice template according to an embodiment of the present disclosure.

[0041] Fig.10 It is an exemplary schematic diagram schematically showing an invoice basic information editing interface according to an embodiment of the present disclosure.

[0042] Fig.11 is a flow chart schematically illustrating a process for generating an invoice according to an embodiment of the present disclosure.

[0043] Fig.12 is an exemplary diagram schematically illustrating an invoice according to an embodiment of the present disclosure.

[0044] Fig.13 is a flow chart schematically illustrating another process for generating an invoice according to an embodiment of the present disclosure.

[0045] Fig.14 is an exemplary diagram schematically illustrating another invoice according to an embodiment of the present disclosure.

[0046] Fig.15 is a flowchart schematically illustrating a process for generating a packaging list according to an embodiment of the present disclosure.

[0047] Fig.16 is a flowchart schematically illustrating a process for generating a packing list using a generated invoice according to an embodiment of the present disclosure.

[0048] Fig.17 is an exemplary diagram schematically illustrating a package list according to an embodiment of the present disclosure.

[0049] Fig.18 is a schematic block diagram illustrating an information processing device that can be used to implement a computer-implemented invoice processing method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0050] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of modules and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0051] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0052] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0053] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0054] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0055] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0056] Combine the following Figure 1 An exemplary process of a computer-implemented invoice processing method is described below. Figure 1 is a flow chart schematically illustrating a computer-implemented invoice processing method 100 according to an embodiment of the present disclosure.

[0057] like Figure 1 As shown in FIG. 1 , in step S101 , a business category corresponding to the business for which an invoice is to be generated may be determined.

[0058] According to some embodiments of the present disclosure, the business category may include a service category or a product category.

[0059] For example, the service category could be outsourcing services that help other companies with their research and development work. Another example is the product category, which could be physical products that are produced from raw materials.

[0060] Those skilled in the art can understand that the service categories that can be defined are not limited to the above items, but various service categories can be defined according to actual conditions, and the present disclosure does not limit this.

[0061] According to some embodiments of the present disclosure, the product categories may include one or more of complete vehicles, spare parts, car bodies, and powertrain components.

[0062] Those skilled in the art will appreciate that the product categories that can be defined are not limited to the above items, but various product categories can be defined according to actual conditions, and the present disclosure does not limit this.

[0063] After step S101, the computer-implemented invoice processing method 100 may proceed to step S103. In step S103, one or more fields related to the business category may be selected from a field set including various fields based at least on the business category, and default information may be set for the selected one or more fields based at least on the business category.

[0064] Combine the following Figure 4 To describe various fields in a field set according to an embodiment of the present disclosure. Figure 4 4 is an exemplary diagram schematically illustrating various fields in a field set 400 according to an embodiment of the present disclosure.

[0065] like Figure 4 As shown in , each field in the field set 400 may have a field name 401, a business category 402, a field number 403, a product type 404, a default information flag 405, and default information 406, etc.

[0066] According to some embodiments of the present disclosure, field name 401 may be used to represent a descriptive name of a field. Figure 4 As shown in , the field name 401 can be "company name" or "company address" and the like.

[0067] According to some embodiments of the present disclosure, the service category 402 may be used to indicate the service category corresponding to the service to which the field belongs. Figure 4 As shown in , business category 402 may be services, complete vehicles, spare parts, vehicle bodies or powertrain components, etc.

[0068] According to some embodiments of the present disclosure, field number 403 may be used to uniquely identify each field. Figure 4As shown in , the field whose field name 401 is "Company Name" may have a field number 403 value of "4", while the field number 403 of another field whose field name 401 is "Company Address" may have a field number 403 value of "5". Therefore, the field whose field name 401 is "Company Name" may be uniquely identified by the field number 403 value of "4", while the field number 403 of another field whose field name 401 is "Company Address" may be uniquely identified by the field number 403 value of "5".

[0069] According to some embodiments of the present disclosure, product type 404 may be used to indicate the product type corresponding to the product to which the field belongs. Figure 4 As shown in , the product type 404 may be a vehicle model, a spare part model, a vehicle model, or a powertrain component model, etc. Note that if the business category 402 is a service category, the product type 404 is not available (NA).

[0070] According to some embodiments of the present disclosure, the default information flag 405 may be used to indicate whether to turn on or off the default information of each field. For example, the default information flag 405 may be "on" or "off". If the default information flag 405 is "on", the field may adopt its default information. In addition, if the default information flag 405 is "off", the field may not adopt its default information.

[0071] According to some embodiments of the present disclosure, the default information 406 may be used to indicate a default value pre-set for the field. Figure 4 As shown in , the default information 406 of the field name 401 "Company Name" corresponding to the business category 402 "Service" may be "Company A", and the default information 406 of the field name 401 "Company Name" corresponding to the business category 402 "Company Vehicle" may be "Company B". Figure 4 As shown in , the default information 406 of the field name 401 "Company Address" corresponding to the business category 402 "Car Body" may be "City D", while the default information 406 of the field name 401 "Company Address" corresponding to the business category 402 "Powertrain Components" may be "City E". Note that the same field name 401 corresponding to different business categories 402 may have the same default information or different default information, which is not limited in the present disclosure.

[0072] Those skilled in the art can understand that the various fields are not limited to the above items, but may include any fields related to the business category, and the present disclosure does not limit this.

[0073] For example, refer to Figure 4, if the business for which the invoice is to be generated is engine development service, the business category 402 corresponding to the engine development service is "service". Therefore, one or more fields related to the business category 402 "service" may be selected from the field set 400 of various fields based at least on the business category 402 "service", such as a field with a field name 401 of "company name". In addition, default information 406 "Company A" may be set for the selected field with a field name 401 of "company name" based at least on the business category 402 "service".

[0074] According to some embodiments of the present disclosure, in the case where the business category is a product category, selecting one or more fields related to the business category from a field set including various fields at least based on the business category and setting default information for the selected one or more fields at least based on the business category may include: determining a product type corresponding to the product category; and selecting one or more fields related to the product type from a field set including various fields based on the product category and the product type, and setting default information for the selected one or more fields based on the product category and the product type.

[0075] Combine the following Figure 2 An exemplary process for processing invoices based on product category and product type is described below. Figure 2 is a flow chart schematically illustrating a process 200 for processing invoices based on product categories and product types according to an embodiment of the present disclosure.

[0076] like Figure 2 As shown in , in step S201, it can be determined whether the business category is a product category.

[0077] If the judgment result in step S201 is "yes", the process 200 for processing an invoice based on a product category and a product type may proceed to step S203. In step S203, a product type corresponding to the product category may be determined.

[0078] As described above, the product type may include one or more of a vehicle model, a spare part model, a vehicle body model, and a powertrain component model.

[0079] According to some embodiments of the present disclosure, determining the product type corresponding to the product category may include: when the product category is a complete vehicle, determining the vehicle type corresponding to the complete vehicle; when the product category is spare parts, determining the spare parts model corresponding to the spare parts; when the product category is a vehicle body, determining the vehicle body model corresponding to the vehicle body; and when the product category is a powertrain component, determining the powertrain component model corresponding to the powertrain component.

[0080] Combine the following Figure 3 hereinafter describes an exemplary process for determining a product type. Figure 3 is a flow chart schematically illustrating a process 300 for determining a product type according to an embodiment of the present disclosure.

[0081] like Figure 3 As shown in , in step S301 , it can be determined whether the product category is a complete vehicle, spare parts, vehicle body, or powertrain component.

[0082] In the case where it is determined in step S301 that the product category is a complete vehicle, the process 300 for determining the product type may proceed to step S303. In step S303, a vehicle model corresponding to the complete vehicle may be determined.

[0083] In the case that the product category is determined to be a spare part in step S301, the process 300 for determining the product type may proceed to step S305. In step S305, a spare part model corresponding to the spare part may be determined.

[0084] In the case where it is determined in step S301 that the product category is a vehicle body, the process 300 for determining the product type may proceed to step S307. In step S307, a vehicle body model corresponding to the vehicle body may be determined.

[0085] In the case that the product category is determined to be a powertrain component in step S301, the process 300 for determining the product type may proceed to step S309. In step S309, a powertrain component model corresponding to the powertrain component may be determined.

[0086] Return to reference Figure 2 After step S203, the process 200 for processing an invoice based on a product category and a product type may proceed to step S205. In step S205, one or more fields related to the product type may be selected from a field set including various fields based on the product category and the product type, and default information may be set for the selected one or more fields based on the product category and the product type.

[0087] For example, refer to Figure 4, if the business for which the invoice is to be generated is the export of an S-brand Y-type sedan, the business category 402 corresponding to the business is "complete vehicle", and the product type corresponding to the business category 402 "complete vehicle" is "car model" (in this example, "S-brand Y-type sedan"). Therefore, one or more fields related to the product type 404 "car model" can be selected from the field set 400 of various fields based at least on the business category 402 "complete vehicle" and the product type 404 "car model", such as a field with a field name 401 of "company name". In addition, the default information 406 "Company B" can be set for the field with a field name 401 of "company name" selected based at least on the business category 402 "complete vehicle" and the product type 404 "car model".

[0088] Return to reference Figure 1 After step S103, the computer-implemented invoice processing method 100 may proceed to step S105. In step S105, an invoice template corresponding to the business category may be generated based on the selected one or more fields and the default information set for the one or more fields.

[0089] Combine the following Figure 5 To describe an invoice template according to an embodiment of the present disclosure. Figure 5 is an exemplary diagram schematically illustrating an invoice template 500 according to an embodiment of the present disclosure.

[0090] According to some embodiments of the present disclosure, the invoice template 500 may have an invoice template name 501, and the invoice template name 501 may be generated based on the business category 402. For example, Figure 5 As shown in , the invoice template name 501 "F Service" of the first invoice template 508 can be generated based on the business category 402 "Service". Note that, as described above, if the business category 502 is service, the product type 404 is not available (NA). In addition, note that the invoice template name 501 of the invoice template can include other information in addition to the business category 402, such as user-defined information.

[0091] According to some embodiments of the present disclosure, when the business category 402 is a product category, a product type 404 corresponding to the product category may be determined, and the invoice template name 501 may be generated based on both the business category 402 and the product type 404. Figure 5As shown in , the invoice template name 501 "Full vehicle G type" of the second invoice template 509 can be generated based on both the business category 402 "Full vehicle" and the product type 404 "G type". Note that the invoice template name 501 of the invoice template may include other information, such as user-defined information, in addition to the business category 402 and the product type 404.

[0092] In addition, in addition to the fields such as the invoice template name 501, business category 402, and product type 404, the invoice template 500 may also include fields such as departure 504, arrival 505, departure port 506, and arrival port 507. For example, in addition to the invoice template name 501 "Full vehicle G type", the business category 402 "Full vehicle" and the product type 404 "G type", the second invoice template 509 may also include departure 504 "H country", arrival 505 "I country", departure port 506 "J port" and arrival port 507 "K port". Note that the fields that can be included in the invoice template are not limited to the above items, but may include any fields, and the present disclosure does not limit this.

[0093] Return to reference Figure 1 After step S105, the computer-implemented invoice processing method 100 may proceed to step S107. In step S107, the invoice template may be used to generate an invoice for the business.

[0094] According to some embodiments of the present disclosure, using the invoice template to generate an invoice for a business may include: automatically calling a corresponding invoice template to generate an invoice for the business based on a business requirement for generating an invoice.

[0095] Combine the following Figure 6 hereinafter describes an exemplary process for generating an invoice. Figure 6 is a flow chart schematically illustrating a process 600 for generating an invoice according to an embodiment of the present disclosure.

[0096] like Figure 6 As shown in FIG. 5 , in step S601 , a corresponding invoice template may be automatically called based on the business requirement for generating an invoice to generate the invoice for the business.

[0097] According to some embodiments of the present disclosure, the business requirements may include one or more of the following: export request, transportation plan, and delivery plan. For example, if the export department requests to export a batch of complete vehicles, an invoice needs to be generated for the batch of complete vehicles to be exported. For example, if the logistics department arranges a transportation plan for a batch of vehicle bodies, an invoice needs to be generated for the batch of vehicle bodies to be transported. For example, if the sales department plans to deliver a complete vehicle to a customer, an invoice needs to be generated for the complete vehicle.

[0098] According to some embodiments of the present disclosure, automatically calling a corresponding invoice template to generate an invoice for a business based on a business requirement that requires generating an invoice may include: automatically calling an invoice template corresponding to a business category based on a business category corresponding to the business included in the business requirement; obtaining detailed information related to the business included in the business requirement from various data sources using trigger information included in the business requirement; and automatically filling in corresponding fields in the called invoice template using the obtained detailed information related to the business included in the business requirement.

[0099] Combine the following Figure 7 An exemplary process for calling an invoice template to generate an invoice is described below. Figure 7 FIG. 7 is a flow chart schematically illustrating a process 700 for calling an invoice template to generate an invoice according to an embodiment of the present disclosure.

[0100] like Figure 7 As shown in , in step S701, an invoice template corresponding to the business category can be automatically called based on the business category corresponding to the business included in the business requirement.

[0101] According to some embodiments of the present disclosure, automatically calling an invoice template corresponding to a business category based on a business category corresponding to the business included in the business requirement may include: comparing the business category corresponding to the business included in the business requirement with the invoice template name of the invoice template; based on the comparison, selecting an invoice template whose invoice template name best matches the business category corresponding to the business included in the business requirement; and automatically calling the selected invoice template.

[0102] Combine the following Figure 8 An exemplary process for invoicing an invoice template is described below. Figure 8 is a flow chart schematically illustrating a computer-implemented process 800 for invoking an invoice template according to an embodiment of the present disclosure.

[0103] like Figure 8 As shown in , in step S801, the business category corresponding to the business included in the business requirement may be compared with the invoice template name of the invoice template.

[0104] For example, if the business requirement includes engine R&D services, the business category corresponding to this business is "Service". Figure 5 , the business category “service” corresponding to the engine R&D service may be compared with the invoice template name 501 of the invoice template 500 .

[0105] After step S801, the process 800 for calling an invoice template may proceed to step S803. In step S803, an invoice template whose invoice template name best matches the business category corresponding to the business included in the business requirement may be selected based on the comparison.

[0106] Continuing with the above example, it can be seen from the above comparison that because the invoice template name 501 "F Service" of the first invoice template 508 best matches the business category "Service" corresponding to the engine R&D service, the first invoice template 508 can be selected.

[0107] After step S803, the process 800 for calling an invoice template may proceed to step S805. In step S805, the selected invoice template may be automatically called.

[0108] Continuing with the above example, the selected first invoice template 508 may be automatically called to generate an invoice for engine development services.

[0109] According to some embodiments of the present disclosure, when the business category corresponding to the business included in the business requirement is a product category, determining the product type corresponding to the product category, and automatically calling the invoice template corresponding to the business category based on the business category corresponding to the business included in the business requirement may include: comparing the business category and product type corresponding to the business included in the business requirement with the invoice template name of the invoice template; based on the comparison, selecting the invoice template whose invoice template name best matches the business category and product type corresponding to the business included in the business requirement; and automatically calling the selected invoice template.

[0110] Combine the following Fig. 9 Another exemplary process for invoking an invoice template is described below. Fig. 9 is a flow chart schematically illustrating another process 900 for calling an invoice template according to an embodiment of the present disclosure.

[0111] like Fig. 9 As shown in , in step S901, the business category and product type corresponding to the business included in the business requirement may be compared with the invoice template name of the invoice template.

[0112] For example, if the business requirement includes the export of G-type complete vehicles, the business category corresponding to the business is "complete vehicle" and the product type is "G-type". Figure 5 , the business category “complete vehicle” and the product type “G type” corresponding to the export G type complete vehicle can be compared with the invoice template name 501 of the invoice template 500.

[0113] After step S901, another process 900 for calling an invoice template may proceed to step S903. In step S903, an invoice template whose invoice template name best matches the business category and product type corresponding to the business included in the business requirement may be selected based on the comparison.

[0114] Continuing with the above example, through the above comparison, it can be seen that because the invoice template name 501 "Complete Vehicle Type G" of the second invoice template 509 best matches the business category "Complete Vehicle" and product type "Type G" corresponding to the export of Type G complete vehicles, the second invoice template 509 can be selected.

[0115] After step S903, another process 900 for calling an invoice template may proceed to step S905. In step S905, the selected invoice template may be automatically called.

[0116] Continuing with the above example, the selected second invoice template 509 may be automatically called to generate an invoice for export of a Type G vehicle.

[0117] Return to reference Figure 7 After step S701, the process 700 for calling an invoice template to generate an invoice may proceed to step S703. In step S703, detailed information related to the business included in the business requirement may be acquired from various data sources using the trigger information included in the business requirement.

[0118] Combine the following Fig.10 To describe an exemplary invoice basic information editing interface according to an embodiment of the present disclosure. Fig.10 Schematic diagram schematically showing an exemplary invoice basic information editing interface 1000 according to an embodiment of the present disclosure.

[0119] like Fig.10 As shown in, for example, the invoice basic information editing interface 1000 may include one or more of the following fields: invoice number, trigger information, delivery date, business category, invoice status, invoice generation date, vehicle type, mode of transport, departure port, arrival port, shipment, arrival, etc. Among the above fields, fields marked with an "*" (such as invoice number 1001, delivery date, business category, invoice generation date, mode of transport, shipment, arrival, etc.) may be required fields (that is, fields whose values ​​cannot be empty), and fields marked with a "#" (such as shipment 1003, arrival, etc.) may be template fields (that is, fields that can adopt the default information of the fields in the invoice template). Note that some fields can be both required fields and template fields. For example, Fig.10As shown in , the two fields of departure and arrival can be both mandatory fields and template fields. Note that the invoice basic information editing interface 1000 can also include other fields, which are not specifically limited in the present disclosure.

[0120] According to some embodiments of the present disclosure, the trigger information may include a business identification number included in the business requirement, and the data source may include one or more of the following: an export data source, a logistics data source, a production data source, and a sales data source. According to some embodiments of the present disclosure, in the case where the business category corresponding to the business included in the business requirement is a product category, the business identification number may include a product identification number. For example, the product identification number may include a material number, such as a frame number of a complete vehicle, a spare part number of a spare part, etc.

[0121] like Fig.10 As shown in , detailed information related to the business can be obtained from various data sources using trigger information 1005. For example, in the case where the business is to export a G-type vehicle, the frame number of the G-type vehicle can be used as trigger information 1005, and the frame number of the G-type vehicle can be used to obtain the delivery date information, vehicle export business information, etc. of the G-type vehicle from the export data source, the transportation mode information, departure port information, arrival port information, etc. of the G-type vehicle from the logistics data source, and the model information of the G-type vehicle (in this example, G-type) from the production data source.

[0122] Return to reference Figure 7 After step S703, the process 700 for calling an invoice template to generate an invoice may proceed to step S705. In step S705, the corresponding fields in the called invoice template may be automatically filled with the acquired detailed information related to the business included in the business requirement.

[0123] Continuing with the above example, after obtaining detailed information related to the business, the corresponding fields in the called invoice template can be automatically filled with the detailed information. For example, the "delivery date" field in the called invoice template can be automatically filled with the delivery date information of the G-type vehicle, the "business category" field in the called invoice template can be automatically filled with the whole vehicle export business information of the G-type vehicle, the "transportation mode" field in the called invoice template can be automatically filled with the transportation mode information of the G-type vehicle, the "departure port" field in the called invoice template can be automatically filled with the departure port information of the G-type vehicle, the "arrival port" field in the called invoice template can be automatically filled with the arrival port information of the G-type vehicle, the "model" field in the called invoice template can be automatically filled with the model information of the G-type vehicle, and so on.

[0124] According to the above-mentioned embodiments of the present disclosure, since the corresponding invoice template can be automatically called based on the business needs to generate the invoice for the business, and the trigger information included in the business needs can be used to obtain detailed information related to the business from various data sources to automatically fill in the corresponding fields in the called invoice template, the efficiency of generating invoices can be greatly improved, the user's convenience is greatly improved, and various data errors when generating invoices are avoided.

[0125] According to some embodiments of the present disclosure, the values ​​of each field in the automatically filled invoice template can be modified or input; and the first invoice including the cover and business items can be generated using the values ​​of each field in the modified or input invoice template and according to a predetermined layout style of the invoice.

[0126] Combine the following Fig.11 An illustrative process 1100 for generating an invoice is described below. Fig.11 is a flow chart schematically illustrating a process 1100 for generating an invoice according to an embodiment of the present disclosure.

[0127] like Fig.11 As shown in , in step S1101, the values ​​of various fields in the automatically filled invoice template can be modified or input.

[0128] like Fig.10 As shown in , for example, date information can be input into the "invoice generation date" field in the invoice basic information editing interface 1000, or the system can also fill the current time into the "invoice generation date" field. In addition, for example, the "departure port" field in the invoice basic information editing interface 1000 can be modified, for example, the "departure port" can be changed from Port J to Port P, and so on.

[0129] After step S1101, the process 1100 for generating an invoice may proceed to step S1103. In step S1103, the first invoice including a cover and business items may be generated using the values ​​of the fields in the modified or input invoice template and according to a predetermined layout style of the invoice.

[0130] Next reference Fig.12 An exemplary invoice according to an embodiment of the present disclosure is described. Fig.12 is an exemplary diagram schematically illustrating an invoice according to an embodiment of the present disclosure.

[0131] like Fig.12 As shown in , the first invoice 1200 may include a cover page 1201, business items 1203, and other information 1205. The cover page 1201 may include one or more of the following fields: invoice number, invoice generation date, departure, arrival, mode of transport, shipping date, etc. The business items 1203 may include one or more of the following fields: serial number, material number, name of goods, country of origin, quantity, unit price, total price, etc. For example, Fig.12 As shown in FIG. 1 , the business item 1203 may include a business item 1207 about the engine. Other information 1205 may include one or more of the following fields: bank account, tax number, letter of credit number, etc. Note that Fig.12 The layout style of the first invoice 1200 shown in the figure is only an example, and the first invoice may also adopt other layout styles, which are not specifically limited in the present disclosure. In addition, it is noted that the fields included in the cover 1201, business items 1203 and other information 1205 are only examples, and they may also include other fields, which are not specifically limited in the present disclosure.

[0132] According to some embodiments of the present disclosure, when the business requirements include multiple businesses of the same business category, the invoice processing method may further include: generating a common cover for the multiple businesses of the same business category; generating multiple invoice items, each of the multiple invoice items corresponding to each business of the multiple businesses of the same business category and including an actual invoice number; and generating a second invoice including the common cover and the multiple invoice items, wherein the second invoice includes a virtual invoice number.

[0133] Combine the following Fig.13 Another exemplary process for generating an invoice is described below. Fig.13 is a flow chart schematically illustrating another process 1300 for generating an invoice according to an embodiment of the present disclosure.

[0134] like Fig.13As shown in , in step S1301, a common cover can be generated for the multiple services of the same service category.

[0135] After step S1301, another process 1300 for generating an invoice may proceed to step S1303. In step S1303, a plurality of invoice items may be generated, each of which may correspond to each business of the plurality of businesses of the same business category and include an actual invoice number.

[0136] After step S1303, another process 1300 for generating an invoice may proceed to step S1305. In step S1305, a second invoice including the common cover and the plurality of invoice items may be generated, wherein the second invoice includes a virtual invoice number.

[0137] Combine the following Fig.14 Another exemplary invoice according to an embodiment of the present disclosure is described below. Fig.14 is an exemplary diagram schematically illustrating another invoice according to an embodiment of the present disclosure.

[0138] like Fig.14 As shown in , the second invoice 1400 may include a common cover 1401, multiple invoice items 1403, and other information 1405. The common cover 1401 may include one or more of the following fields: invoice number, invoice generation date, departure, arrival, mode of transport, shipping date, etc. Note that the invoice number in the common cover 1401 may be a virtual invoice number of the second invoice 1400. Multiple invoice items 1403 may include one or more of the following fields: serial number, material number, index number, name of goods, country of origin, quantity, unit price, total price, etc. For example, Fig.14 As shown in , multiple invoice items 1403 may include an invoice item 1407 for the engine and an invoice item 1409 for the vehicle body. Note that the index number in each invoice item in the multiple invoice items 1403 may be an actual invoice number. For example, the index number "SYXX1" in invoice item 1407 may be the actual invoice number of the engine, and the index number "SYXX6" in invoice item 1409 may be the actual invoice number of the vehicle body. Other information 1405 may include one or more of the following fields: bank account, tax number, letter of credit number, etc. Note that Fig.14 The layout style of the second invoice 1400 shown in the figure is only an example, and the second invoice may also adopt other layout styles, which are not specifically limited in the present disclosure. In addition, it is noted that the fields included in the common cover 1401, the multiple invoice items 1403 and the other information 1405 are only examples, and other fields may also be included, which are not specifically limited in the present disclosure.

[0139] Fig.14 and Fig.12 The main difference is that Fig.12 The business item 1203 in includes only one business item, and Fig.14 The multiple invoice items 1403 may include multiple invoice items; in addition, Fig.12 The cover 1201 in the example is for a business item in the business item 1203, and Fig.14 The common cover 1401 in the example is for all invoice items in the multiple invoice items 1403, that is, Fig.14 The common cover 1401 is common to all invoice items in the plurality of invoice items 1403 .

[0140] According to the above-mentioned embodiments of the present disclosure, multiple businesses of the same business category can be concentrated in the same second invoice, so as to facilitate subsequent processing, such as subsequent customs declaration processing and logistics processing, etc., further improving the user's convenience.

[0141] According to some embodiments of the present disclosure, when the business category includes a product category, the invoice processing method may further include: utilizing the generated invoice and automatically generating a packing list of products corresponding to the generated invoice according to a predetermined packing list typesetting style.

[0142] Combine the following Fig.15 hereinafter describes an exemplary process for generating a packaging list. Fig.15 is a flow chart schematically illustrating a process 1500 for generating a packaging list according to an embodiment of the present disclosure.

[0143] like Fig.15 As shown in FIG. 1 , in step 1501 , a packing list of products corresponding to the generated invoice can be automatically generated using the generated invoice and according to a predetermined packing list layout style.

[0144] Combine the following Fig.17 An exemplary packaging list according to an embodiment of the present disclosure is described. Fig.17 is an exemplary diagram schematically illustrating a package list according to an embodiment of the present disclosure.

[0145] like Fig.17 As shown, the package list includes a "referenced invoice number" field, which can be used to indicate the invoice number of the invoice corresponding to the package list. That is, the package list and invoice of the same product correspond to each other.

[0146] According to some embodiments of the present disclosure, the method of automatically generating a packing list of products corresponding to the generated invoice using the generated invoice and according to a predetermined packing list typeset style may include: obtaining first information of a first field in the packing list that is the same as the field in the invoice from the generated invoice; obtaining second information of a second field in the packing list that is different from the field in the invoice from various data sources using a product identification number included in the generated invoice; and automatically generating a packing list of products corresponding to the generated invoice using the first information and the second information and according to a predetermined packing list typeset style.

[0147] Combine the following Fig.16 to describe. Fig.16 is a flow chart schematically illustrating a process 1600 for generating a packing list using a generated invoice according to an embodiment of the present disclosure.

[0148] like Fig.16 As shown in , in step S1601, first information of a first field in a packaging list that is the same as a field in the invoice can be obtained from the generated invoice.

[0149] like Fig.17 As shown in , the package list 1700 may also include header information 1701 and package entries 1703. Header information 1701 may include one or more of the following information: buyer, remarks, invoice generation date, shipping address, transportation information, measurement and weight, etc. Note that each of the above information may include one or more fields. For example, "transportation information" may include fields such as "transportation mode", "departure", and "arrival". Package entry 1703 may include one or more of the following fields: serial number, material number, cargo name, quantity, package number, package type, package quantity, length, width, height, volume, net weight, gross weight, etc. For example, Fig.17 An engine-related packaging item is shown in .

[0150] Fig.17 Some of the fields in the package list 1700 shown in Fig.12 Some fields in the first invoice 1200 shown in FIG. 1 are the same. For example, Fig.17 and Fig.12 The fields shown in the table are the same, such as "Material Number", "Goods Name", "Invoice Generation Date", "Transportation Method", "Departure", "Arrival", etc. These same fields can be called the first field. In addition, Fig.17 The package list shown in 1700 and Fig.12 The same first fields in the first invoice 1200 shown in FIG. 1 may have the same first information. For example, Fig.17 and Fig.12The same first field "Material Number" shown in can have the same first information "A1B1", and Fig.17 and Fig.12 The same first field "Goods Name" shown in can have the same first information "Engine".

[0151] After step S1601, the process 1600 for generating a packing list using the generated invoice can proceed to step S1603. In step S1603, the second information of the second field in the packing list that is different from the field in the invoice can be obtained from various data sources using the product identification number included in the generated invoice.

[0152] like Fig.17 As shown in Fig.17 Some fields in the packaging list 1700 shown in FIG. 1700 are unique to the packaging list 1700 and are related to Fig.12 All fields in the first invoice 1200 shown in FIG. 1 are different. For example, Fig.17 The fields such as package number, package type, package quantity, length, width, height, volume, net weight, gross weight, etc. shown in are unique to package list 1700. These fields are Fig.12 The fields not shown in the first invoice 1200 are referred to as second fields. Fig.17 and Fig.12 The same first field "material number" shown in the figure is used as the product identifier to obtain the second information of the second field from each data source. For example, the "material number" can be used as the product identifier to obtain the second information of the second field such as length, width, height, volume, net weight, gross weight, etc. from the production data source, and the second information of the second field such as package number, package type, package quantity, etc. can be obtained from the logistics data source, and so on.

[0153] After step S1603, the process 1600 for generating a packing list using the generated invoice may proceed to step S1605. In step S1605, a packing list of products corresponding to the generated invoice may be automatically generated using the first information and the second information and according to a predetermined packing list layout style.

[0154] Fig.17 The layout style of the package list 1700 shown in the figure is only exemplary, and other layout styles may also be used, which is not specifically limited in the present disclosure.

[0155] According to the above-mentioned embodiments of the present disclosure, since the generated invoice can be used to automatically generate a packing list of products corresponding to the generated invoice, the effect of generating the packing list can be greatly improved, the user's convenience is greatly improved, and various data errors when generating the packing list are avoided.

[0156] According to some embodiments of the present disclosure, the generated invoice and / or the generated packing list can be stored in a computer system and can be browsed, queried, downloaded or printed by various parties.

[0157] According to some embodiments of the present disclosure, a computer storage medium may be provided, on which computer instructions are stored. When the computer instructions are executed by a computer, the computer is caused to execute the invoice processing method as described in any one of the above items.

[0158] According to some embodiments of the present disclosure, a computer-implemented invoice processing device may be provided, comprising: a memory storing computer instructions; and a processor coupled to the memory to execute the computer instructions to perform the invoice processing method as described in any one of the foregoing items.

[0159] By using the computer-implemented invoice processing method, device and storage medium disclosed in the present invention, invoice processing can be performed quickly and conveniently, thereby improving the efficiency of invoice processing and improving the convenience of use for users.

[0160] Note that the above-described effects are not necessarily limited, and any effects shown in the present specification or other effects that can be understood from the present specification may be exhibited together with or instead of the above-described effects.

[0161] Fig.18 is a schematic block diagram illustrating an information processing device that can be used to implement a computer-implemented invoice processing method according to an embodiment of the present disclosure.

[0162] exist Fig.18 In the embodiment of the present invention, a central processing unit (CPU) 2101 performs various processes according to a program stored in a read-only memory (ROM) 2102 or a program loaded from a storage section 2108 to a random access memory (RAM) 2103. In the RAM 2103, data required when the CPU 2101 performs various processes and the like is also stored as needed. The CPU 2101, the ROM 2102, and the RAM 2103 are connected to each other via a bus 2104. An input / output interface 2105 is also connected to the bus 2104.

[0163] The following components are connected to the input / output interface 2105: an input section 2106 (including a keyboard, a mouse, etc.), an output section 2107 (including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.), a storage section 2108 (including a hard disk, etc.), a communication section 2109 (including a network interface card such as a LAN card, a modem, etc.). The communication section 2109 performs communication processing via a network such as the Internet. A drive 2110 may also be connected to the input / output interface 2105 as needed. A removable medium 2111 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is installed on the drive 2110 as needed, so that a computer program read therefrom is installed in the storage section 2108 as needed.

[0164] In the case where the above-described series of processing is implemented by software, a program constituting the software is installed from a network such as the Internet or a storage medium such as the removable medium 2111 .

[0165] It should be understood by those skilled in the art that such storage media is not limited to Fig.18 The removable medium 2111 shown has a program stored therein and is distributed separately from the device to provide the program to the user. Examples of the removable medium 2111 include magnetic disks (including floppy disks (registered trademark)), optical disks (including compact disk read-only memory (CD-ROM) and digital versatile disks (DVD)), magneto-optical disks (including minidiscs (MD) (registered trademark)), and semiconductor memories. Alternatively, the storage medium may be a ROM 2102, a hard disk included in the storage portion 2108, or the like, in which the program is stored and distributed to the user together with the device containing them.

[0166] When the instruction code is read and executed by a machine, the above method according to the embodiment of the present disclosure can be executed.

[0167] Computer program code for performing the operations of various aspects of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0168] It should be understood that each box in the flowchart and / or block diagram and the combination of boxes in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so as to produce a machine, so that when these computer program instructions are executed by the processor of the computer or other programmable data processing device, a device is generated to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0169] These computer program instructions may also be stored in a computer-readable medium, which enables a computer, other programmable data processing apparatus, or other device to operate in a specific manner, so that the instructions stored in the computer-readable medium produce an article of manufacture including instructions for implementing the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0170] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby enabling the instructions executed on the computer or other programmable device to provide a process for implementing the functions / operations specified in the blocks in the flowchart and / or block diagram.

[0171] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0172] Note that in order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed herein.

Claims

1. A computer-implemented invoice processing method comprising: Determine the transaction category corresponding to the transaction for which the invoice is to be generated; selecting one or more fields related to the business category from a field set including various fields based at least on the business category, and setting default information for the selected one or more fields based at least on the business category; generating an invoice template corresponding to the business category based on the one or more selected fields and default information set for the one or more fields; as well as Use the invoice template to generate invoices for your business. Wherein, using the invoice template to generate a business invoice includes: Automatically calling an invoice template corresponding to the business category based on the business category corresponding to the business included in the business requirement; Acquire detailed information related to the business included in the business requirement from various data sources using the trigger information included in the business requirement; and The acquired detailed information related to the business included in the business requirement is used to automatically fill in the corresponding fields in the called invoice template to generate an invoice for the business.

2. The invoice processing method according to claim 1, wherein: The business category includes a service category or a product category.

3. The invoice processing method according to claim 2, wherein: In the case where the business category is a product category, selecting one or more fields related to the business category from a field set including various fields at least based on the business category and setting default information for the selected one or more fields at least based on the business category includes: Identify the product types that correspond to the product categories; and One or more fields related to the product type are selected from a field set including various fields based on the product category and the product type, and default information is set for the selected one or more fields based on the product category and the product type.

4. The invoice processing method according to claim 3, wherein: The product categories include one or more of complete vehicles, spare parts, body and powertrain components.

5. The invoice processing method according to claim 4, wherein: The product type includes one or more of a vehicle model, a spare part model, a vehicle body model, and a powertrain component model.

6. The invoice processing method according to claim 5, wherein: Determining the product type corresponding to the product category includes: In the case where the product category is a complete vehicle, determine the model corresponding to the complete vehicle; In the case where the product category is spare parts, determine the spare parts model corresponding to the spare parts; In the case where the product category is a vehicle body, determining a vehicle body model corresponding to the vehicle body; and When the product category is a powertrain component, a powertrain component model corresponding to the powertrain component is determined.

7. The invoice processing method according to claim 1, wherein: Each of the various fields has a default information flag, and the default information flag is used to indicate whether to turn on or off the default information of each field.

8. The invoice processing method according to claim 1, wherein: Each of the various fields has a field number, and the field number is used to uniquely identify the respective field.

9. The invoice processing method according to claim 1, wherein: The invoice template has an invoice template name, and the invoice template name is generated based on the business category.

10. The invoice processing method according to claim 9, wherein: In the case where the business category is a product category, a product type corresponding to the product category is determined, and the invoice template name is generated based on both the business category and the product type.

11. The invoice processing method according to claim 1, wherein: The business requirements include one or more of the following: export request, transportation plan, and delivery plan.

12. The invoice processing method according to claim 1, wherein: The automatically calling the invoice template corresponding to the business category based on the business category corresponding to the business included in the business requirement includes: Comparing the business category corresponding to the business included in the business requirement with the invoice template name of the invoice template; According to the comparison, selecting an invoice template whose name best matches the business category corresponding to the business included in the business requirement; and Automatically call the selected invoice template.

13. The invoice processing method according to claim 1, wherein: In the case where the business category corresponding to the business included in the business requirement is a product category, determining the product type corresponding to the product category, and automatically calling the invoice template corresponding to the business category based on the business category corresponding to the business included in the business requirement includes: Comparing the business category and product type corresponding to the business included in the business requirement with the invoice template name of the invoice template; According to the comparison, selecting an invoice template whose invoice template name best matches the business category and product type corresponding to the business included in the business requirement; and Automatically call the selected invoice template.

14. The invoice processing method according to any one of claims 1 to 13, wherein: The trigger information includes the business identification number included in the business requirement, and the data source includes one or more of the following: an export data source, a logistics data source, a production data source, and a sales data source.

15. The invoice processing method according to any one of claims 1 to 13, further comprising: Modify or enter the values ​​of each field in the automatically filled invoice template; as well as A first invoice including a cover page and business items is generated by using the values ​​of each field in the modified or input invoice template and according to a predetermined layout style of the invoice.

16. The invoice processing method according to claim 15, wherein: In the case where the business requirements include multiple businesses of the same business category, the invoice processing method further includes: generating a common cover for the multiple businesses of the same business category; generating a plurality of invoice items, each invoice item in the plurality of invoice items corresponding to each business in the plurality of businesses of the same business category and including an actual invoice number; and A second invoice is generated that includes the common cover and the plurality of invoice items, wherein the second invoice includes a virtual invoice number.

17. The invoice processing method according to claim 2, wherein: In the case where the business category includes a product category, the invoice processing method further includes: A packing list of products corresponding to the generated invoice is automatically generated using the generated invoice and according to a predetermined packing list layout style.

18. The invoice processing method according to claim 17, wherein: The method of automatically generating a packaging list of products corresponding to the generated invoice by using the generated invoice and according to a predetermined packaging list layout style comprises: Obtain, from the generated invoice, first information of a first field in the package list that is identical to a field in the invoice; Using the product identification number included in the generated invoice, obtaining second information of a second field in the package list that is different from the field in the invoice from various data sources; and A packing list of products corresponding to the generated invoice is automatically generated using the first information and the second information and according to a predetermined packing list layout style.

19. The invoice processing method according to claim 17, wherein: The generated invoice and / or the generated packing list can be stored in the computer system and can be viewed, queried, downloaded or printed by all parties.

20. A computer storage medium having computer instructions stored thereon, which, when executed by a computer, causes the computer to execute the invoice processing method according to any one of claims 1 to 19.

21. A computer-implemented invoice processing device comprising: a memory storing computer instructions; and A processor, coupled to the memory, executes the computer instructions to perform the invoice processing method according to any one of claims 1-19.

Images