CN115168502A

CN115168502A - Invoice information updating method and device based on knowledge graph

Info

Publication number: CN115168502A
Application number: CN202210581330.9A
Authority: CN
Inventors: 何艳波
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-05-26
Filing date: 2022-05-26
Publication date: 2022-10-11

Abstract

The invention discloses an invoice information updating method and device based on a knowledge graph, and relates to the technical field of artificial intelligence and the financial field. The method comprises the following steps: receiving an invoice information change instruction; updating a pre-established invoice information knowledge graph according to the change information in the invoice information change instruction, wherein the invoice information knowledge graph is pre-established by taking a plurality of organizations and tax numbers as nodes and taking the hierarchical relationship among the organizations and the corresponding relationship among the organizations and the tax numbers as sides; and acquiring the mechanisms required for making out invoices and the corresponding tax numbers from the updated invoice information knowledge graph. According to the invention, the invoice information is updated, maintained and inquired through the complete mechanism and tax administration map, so that manual intervention and database change operation are reduced, the pressure of development and maintenance personnel is further reduced, and the stable operation of the database is better maintained; meanwhile, the billing efficiency and the service handling experience of the user are improved.

Description

Invoice information updating method and device based on knowledge graph

Technical Field

The invention relates to the technical field of artificial intelligence and the financial field, in particular to an invoice information updating method and device based on a knowledge graph.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

The bank system has more institutions, complex hierarchical relationships exist among institutions such as provinces, cities and counties, and the like, and the new institutions and the withdrawal of institutions occur every year. For a tax invoice correlation system, each institution corresponds to its own tax number. For an invoice system, each upstream business system can provide invoicing transactions for the invoice system based on institution numbers, the invoice system can obtain tax numbers corresponding to invoicing transaction institutions according to institution hierarchical relations and tax numbers of independent tax payment institutions, but institution changes or the tax numbers are changed once, information such as the institution tax numbers, the invoicing transactions, invoicing and the like cannot be normally operated for new tax numbers, a work order needs to be submitted to development and maintenance personnel for processing, the processing time is long, customers need to spend more time waiting for invoicing, the customer experience is poor, the workload of each party is increased by colleagues, the institution tax numbers are changed more frequently, errors occur in the changing process, some functions cannot be normally used, and once problems occur, problem tracking and analysis are not facilitated.

Disclosure of Invention

In order to improve the update efficiency of the invoice information and improve the customer experience, in a first aspect, the application provides a method for updating invoice information based on a knowledge graph, which includes:

receiving an invoice information change instruction;

updating a pre-established invoice information knowledge graph according to change information in the invoice information change instruction, wherein the invoice information knowledge graph is pre-established by taking a plurality of mechanisms and tax numbers as nodes and taking the hierarchical relationship among the mechanisms and the corresponding relationship among the mechanisms and the tax numbers as sides;

and acquiring the mechanisms required for making out invoices and the corresponding tax numbers from the updated invoice information knowledge graph.

In one embodiment, the invoice information change instruction comprises a new mechanism, and the change information comprises new mechanism information, a new mechanism hierarchical relationship and a new mechanism tax number;

the updating of the pre-created invoice information knowledge graph according to the change information in the invoice information change instruction comprises the following steps:

establishing a new mechanism node according to the new mechanism information;

establishing a connection relation between the newly added mechanism node and an existing mechanism node in the invoice information knowledge graph according to the newly added mechanism hierarchical relation;

and determining tax number nodes according to the newly added agency tax number, and establishing a connection relation between the newly added agency tax number nodes and the tax number nodes.

In an embodiment, the invoice information change instruction includes a withdrawal mechanism, and the change information includes information of a mechanism to be withdrawn and information of a merging mechanism;

the updating of the pre-established invoice information knowledge graph according to the change information in the invoice information change instruction comprises the following steps:

searching the mechanism nodes to be withdrawn and the corresponding connection relation thereof according to the information of the mechanism to be withdrawn;

determining a merging mechanism node according to the merging mechanism information;

deleting the connection relation corresponding to the mechanism node to be withdrawn, and establishing the connection relation between the mechanism node to be withdrawn and the merging mechanism node.

In one embodiment, the invoice information change instruction comprises a change tax number, and the change information comprises change mechanism information and change tax number information;

determining a corresponding change mechanism node according to the change mechanism information;

deleting the connection relation between the change mechanism node and the existing tax node;

determining a corresponding tax change node according to the tax change information;

and establishing a connection relation between the change mechanism node and the change tax number node.

In an embodiment, the method for updating invoice information based on a knowledge graph further includes establishing the invoice information knowledge graph, and includes the specific steps of:

acquiring information of a plurality of institutions, hierarchical relationships among the institutions and tax information of the institutions;

establishing a plurality of mechanism nodes and a connection relation among the mechanism nodes according to the hierarchical relation between the mechanism information and each mechanism, wherein the mechanism nodes comprise mechanism numbers, mechanism names and superior mechanism numbers;

and establishing tax nodes according to the tax information of each organization, and establishing a connection relationship between the organization nodes and the tax nodes according to the corresponding relationship between the organizations and the tax.

In a second aspect, the present application provides a knowledge-graph-based invoice information updating apparatus, including:

the change instruction receiving module is used for receiving an invoice information change instruction;

the system comprises a knowledge graph updating module, a tax number calculating module and a tax number calculating module, wherein the knowledge graph updating module is used for updating a pre-established invoice information knowledge graph according to change information of an invoice information change instruction, and the invoice information knowledge graph is pre-established by taking a plurality of mechanisms and the tax number as nodes and taking a hierarchical relationship among the mechanisms and a corresponding relationship among the mechanisms and the tax number as edges;

and the information acquisition module is used for acquiring mechanisms required by invoicing and corresponding tax numbers from the updated invoice information knowledge graph.

In one embodiment, the invoice information change instruction comprises a newly added mechanism, and the change information comprises newly added mechanism information, a newly added mechanism hierarchical relationship and a newly added mechanism tax number;

the knowledge map updating module comprises a mechanism adding unit used for:

establishing a new mechanism node according to the new mechanism information;

establishing a connection relation between the newly added mechanism nodes and the existing mechanism nodes in the invoice information knowledge graph according to the newly added mechanism hierarchical relation;

In an embodiment, the invoice information change instruction includes a merging mechanism, and the change information includes information of a mechanism to be merged and information of a merging mechanism;

the knowledge-graph updating module comprises a mechanism merging unit used for:

searching the mechanism nodes to be withdrawn and the corresponding connection relation thereof according to the mechanism information to be withdrawn;

the knowledge graph updating module comprises a tax number changing unit and is used for:

In one embodiment, the apparatus for updating invoice information based on a knowledge-graph further includes a knowledge-graph establishing module, configured to:

establishing a plurality of mechanism nodes and a connection relation among the mechanism nodes according to the mechanism information and the hierarchical relation among the mechanisms, wherein the mechanism nodes comprise mechanism numbers, mechanism names and superior mechanism numbers;

In a third aspect, the present application provides a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements any one of the methods for updating knowledge-graph based invoice information provided herein when executing the computer program.

In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements any of the methods for knowledge-graph based invoice information update provided herein.

In a fifth aspect, the present application provides a computer program product comprising a computer program that when executed by a processor implements any of the methods for knowledge-graph based invoice information update provided herein.

By constructing a complete organization and tax number management map, the method and the system do not need to provide work orders for development and maintenance personnel to process, do not need to frequently find the free time of the system to change and process the organization and the transaction tax number, reduce the pressure of the database, timely bill customers and do not need customers to wait. When invoicing is carried out by inquiring transaction, the latest tax information of the organization is searched by matching the original organization and the tax number in transaction data with the established organization and tax number map relation, so that manual intervention and database change operation are reduced, stable operation of the database is maintained better, and service experience is also improved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:

fig. 1 is a schematic diagram of an invoice information updating method based on a knowledge graph provided in the present application.

FIG. 2 is a schematic diagram of the steps provided in the present application for building an invoice information knowledge-graph.

Fig. 3 is an intermediate schematic diagram of an invoice information knowledge-graph provided in the present application.

FIG. 4 is a complete schematic diagram of an invoice information knowledge-graph as provided herein.

FIG. 5 is a schematic diagram of one step of altering an invoice information knowledge-graph as provided herein.

FIG. 6 is a schematic diagram of an updated invoice information knowledge-graph as provided herein.

FIG. 7 is a schematic representation of another step of altering an invoice information knowledge-graph as provided herein.

FIG. 8 is a schematic illustration of another step of altering an invoice information knowledge-graph as provided herein.

FIG. 9 is a schematic illustration of another step of altering an invoice information knowledge-graph as provided herein.

FIG. 10 is a schematic illustration of another step of altering an invoice information knowledge-graph as provided herein.

FIG. 11 is a schematic diagram of a knowledge-graph based invoice information update apparatus provided in the present application.

FIG. 12 is another schematic diagram of a knowledge-graph based invoice information update apparatus provided herein.

Fig. 13 is another schematic diagram of the apparatus for updating invoice information based on knowledge-graph provided in the present application.

Fig. 14 is a schematic diagram of a computer device provided in the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.

It should be noted that the method and the device for invoicing based on the knowledge graph can be used in the technical field of artificial intelligence and the financial field, and can also be used in any field except the technical field of artificial intelligence and the financial field.

According to the technical scheme, the data acquisition, storage, use, processing and the like meet relevant regulations of national laws and regulations. The user information in the embodiment of the application is obtained through legal compliance, and the acquisition, storage, use, processing and the like of the user information are all executed on the premise of authorized agreement of a client.

For the public understanding, before the technical solution of the present application is explained in detail, an application scenario of the present application will be explained first.

Banking institutions often have multiple upstream business systems in their systems, many of which are systems that transact with customers. Taking the precious metal transaction system as an example, a customer purchases a precious metal article from a bank as a purchaser, thereby generating a transaction, and when the customer has a demand for invoicing for the transaction within an allowable time range (for example, within five years from the date of generation of the transaction), the customer generates an invoicing request based on transaction information, a purchaser name, a taxpayer identification number, and the like, and transmits the invoicing request to a value-added tax invoice system of the bank. The value-added tax invoice system checks whether the transaction is in compliance and whether the transaction belongs to invokable transactions against the transaction information in the invoicing request. And after the verification is passed, the value-added tax invoice system acquires the related information of the seller from the transaction information, further acquires the name, taxpayer identification number, address, telephone, issuer, account number and other information of the seller, and generates an invoice based on the information and the information in the invoicing request of the client.

For a banking system, it usually includes a main organization and a plurality of subordinate branch organizations, and complex hierarchical relationships exist among organizations such as province, city, county, etc., and different organizations correspond to their respective tax numbers. Since these institutions share the same value added tax invoice system. Therefore, no matter which mechanism the client transacts with, the invoicing request is sent to the value-added tax invoice system, and the value-added tax invoice system determines the seller of the transaction and the tax number of the seller, so as to complete invoicing.

Because the bank system has the conditions of mechanism addition, mechanism withdrawal and the like every year, if a transaction is generated between a client and a certain mechanism and the mechanism is withdrawn when the client wants to make an invoice for the transaction, at the moment, because the mechanism does not exist in the bank system, the value-added tax invoice system cannot continuously use the information of the name, tax number and the like of the mechanism (a seller in the transaction) to execute the operation of making an invoice. When the situation occurs, a work order needs to be submitted to development and maintenance personnel for processing at present, the processing time is long, the seller information can be changed only by maintaining a special window, and invoicing can be performed only after the seller information is changed and maintained. The processing mode not only increases the workload of each party, but also can not bill the client in time, which easily causes poor experience of the client.

The present application has formally been made in this context. When it needs to be explained, in order to describe the application background of the present application more clearly, the applicant takes the bank system as an example for explanation. In fact, the technical scheme of the application is also applicable to enterprises/companies with similar bank system structures (headquarters + a plurality of branch companies), and the application scene of the application is not limited to the bank system. The following is a detailed description of the technical solution of the present application.

In a first aspect, the application provides a method for updating invoice information based on a knowledge graph, and an execution subject of the method can be a value-added tax invoice system or other systems independent of the value-added tax invoice system. As shown in fig. 1, the method includes:

and step S101, receiving an invoice information change instruction.

Specifically, the invoice information change instruction is acquired from a daily batch file downloaded by the core system. The invoice information change instruction comprises change information of an organization and a tax number.

And step S102, updating a pre-established invoice information knowledge graph according to the change information in the invoice information change instruction, wherein the invoice information knowledge graph is pre-established by taking a plurality of mechanisms and tax numbers as nodes and taking the hierarchical relationship among the mechanisms and the corresponding relationship among the mechanisms and the tax numbers as edges.

Specifically, the invoice information knowledge graph comprises a plurality of organization nodes and tax nodes, the connection relationship between the organization nodes represents the hierarchical relationship between the organizations, and the connection relationship between the organization nodes and the tax nodes represents the corresponding relationship between the organizations and the tax. It should be noted that the tax number corresponding to each institution may be an independent tax number, or may be a tax number of a reused superior institution.

And after receiving the invoice information change instruction, acquiring agency and tax number change information in the invoice information change instruction, updating the invoice information knowledge graph in real time based on the change information, and updating the buyer information in the transaction information within a preset time range (for example, within five years before the current day) as required. The schematic diagram and construction process of the invoice information knowledge graph will be described in detail in the next embodiment.

And step S103, acquiring mechanisms required for invoicing and corresponding tax numbers from the updated invoice information knowledge graph.

Since the invoice information knowledge graph is updated in step S102 in real time/daily, when a customer needs to make an invoice for a certain transaction, the value-added tax invoice system can quickly find information such as the name and tax number of the seller of the transaction from the invoice information knowledge graph, thereby realizing quick invoicing.

The method carries out map management on the complex relation change of multiple tax numbers of a bank and the related data change process, can clearly show all related data records of the change of all organizations and the change of the tax numbers through map relations, once the tax numbers are changed, an original organization is not needed, the tax number relation corresponding to transaction data is not needed, when a business system inquires, trades and invoices customers, the original organization, the tax numbers and the constructed organizations are matched with the tax number map relations, the latest tax number information of the organizations is searched, and thus, the map relations and the search are quickly constructed, manual intervention and change operation on a database are reduced, stable operation of the database is better maintained, invoicing can be carried out on the customers at any time, and customer experience is improved.

In one embodiment, the method for updating invoice information based on the knowledge-graph further comprises establishing the invoice information knowledge-graph. As shown in fig. 2, the step of constructing the invoice information knowledge-graph includes steps S201 to S203:

in step S201, information of a plurality of institutions, hierarchical relationships among the institutions, and tax information of the institutions are acquired.

The mechanism information includes information such as a mechanism number, a mechanism name, a superior mechanism number, a provincial mechanism number, a mechanism type, a mechanism state, mechanism effective time and the like.

Taking a bank system as an example, the hierarchical relationship of a bank organization can be expressed as a head office, a first-level branch and a second-level branch \8230, 8230, and the relationship between the organization hierarchical relationship and the tax number of the bank system is shown by a relationship tree in the application as follows:

- -general line (organization number 0- -tax number 0)

- - -first degree branch 1 (organization number 1- -tax number 1)

Two-level branch 11 (organization number 11-tax number 1)

Two-level branch 12 (organization number 12-tax number 1)

- - -first degree branch 2 (organization number 2- -tax number 2)

Two-level branch 21 (organization number 21-tax number 2)

- -first class branch 3 (organization number 3- -tax number 3)

- - -two level branch 31 (organization number 31- -tax number 5)

- -first class branch 4 (organization number 4-tax number 4)

Two-level branch 41 (organization number 41-tax number 4)

- - -second level branch 42 (organization number 42- -tax number 6)

It can also be seen from the above relation tree that the bank system includes a head office, which includes a plurality of first-level branch lines, each of which includes a plurality of second-level branch lines \8230and \8230, and it can also be seen that the institution numbers of different institutions are unique, but the tax numbers of the institutions may be the same or different. For example, the tax number of the first-level branch 1 is tax number 1, and a plurality of second-level branches which belong to the first-level branch 1 are all tax numbers 1, namely the tax number of the upper-level organization is reused; the tax number of the first-level branch 4 is tax number 4, the second-level branch 41 subordinate to the first-level branch n reuses the tax number 4, but the second-level branch 42 subordinate to the first-level branch 4 has its own independent tax number, i.e. tax number 6.

Step S202, establishing a plurality of mechanism nodes and connection relations among the mechanism nodes according to the mechanism information and the hierarchical relations among the mechanisms. The information of organization number, organization name, superior organization number, provincial organization number, organization type, organization state, organization effective time and the like in the organization information can be used as the attribute value of the organization node.

Specifically, as shown in fig. 3, a plurality of organization nodes, i.e., the head line, the first-level branches 1 to 4, the second-level branches 11 to 12, the second-level branches 21, the second-level branches 31, and the second-level branches 41 to 42 in fig. 3, are established according to each organization in the relationship tree. Meanwhile, the hierarchical relationship among the mechanisms is used for establishing the connection relationship among the mechanism nodes, for example, the head office has a connection relationship with each subordinate primary branch, and each primary branch has a connection relationship with each subordinate secondary branch.

Step S203, establishing tax nodes according to the tax information of each organization, and establishing the connection relationship between the organization nodes and the tax nodes according to the corresponding relationship between the organizations and the tax.

Specifically, as shown in fig. 4, on the basis of the graph shown in fig. 3, a plurality of tax nodes are established according to the tax information of each organization, that is, the general tax (tax 0), the first tax (1), the second tax (2), the first tax (3), the second tax (4), the second tax (5), and the second tax (6) in fig. 4.

The first-level branch 1, the subordinate second-level branch 11 and the subordinate second-level branch 12 share the tax number 1, so that three mechanism nodes of the first-level branch 1, the second-level branch 11 and the second-level branch 12 respectively have a connection relation with a tax number node of the first-level branch 1, namely the tax number (tax number 1).

Fig. 4 is a schematic diagram of an invoice information knowledge graph constructed by the present application. It will be understood by those skilled in the art that the number and the hierarchical relationship of the first-level branch and the second-level branch shown in fig. 4 are examples provided in the present application, and are only for illustration and not for limiting the present application.

The step S102 is further described below by using a specific embodiment to update the invoice information knowledge graph created in advance according to the change information in the invoice information change instruction.

First, it should be clear that the invoice information change instruction related to the present application includes the following five types:

(1) And adding a new mechanism and adding a tax number.

At this time, the change information in the invoice information change instruction includes new organization information (e.g., information such as organization number, organization name, organization type, organization status, and organization effective time), new organization hierarchy (e.g., information such as higher-level organization number and provincial organization number), and new organization tax number. The new tax number is a new tax number different from the existing tax number in the invoice information knowledge graph.

As shown in fig. 5, when the invoice information change instruction is received, step S102 specifically includes:

step S10201, establishing a new mechanism node according to the new mechanism information;

step S10202, establishing a connection relation between the newly added mechanism node and an existing mechanism node in the invoice information knowledge graph according to the newly added mechanism hierarchical relation, in particular to a connection relation between the newly added mechanism node and a superior mechanism node thereof;

step S10203, establishing a new tax number node according to the new agency tax number, and establishing a connection relationship between the new agency tax number node and the new tax number node. The changed invoice information knowledge graph is shown in fig. 6, where the secondary sub-row 22 is the newly added organization node and the tax number 7 is the newly added tax number node.

(2) And newly adding an organization and reusing tax numbers of an upper organization.

At this time, the change information in the invoice information change instruction includes added organization information (e.g., information such as organization number, organization name, organization type, organization status, and organization effective time), a hierarchy of the added organization (e.g., information such as higher organization number and provincial organization number), and a higher organization tax number. The upper-level agency tax number refers to the tax number already existing in the invoice information knowledge graph. When the tax number of the upper-level organization is clearly specified and reused, the tax number of the newly added organization is defaulted to reuse the tax number of the upper-level organization.

As shown in fig. 7, when receiving the invoice information change instruction, step S102 specifically includes:

step S10204, establishing a new mechanism node according to the new mechanism information;

step S10205, establishing a connection relationship between the newly added mechanism node and an existing mechanism node in the invoice information knowledge graph, especially a connection relationship between the newly added mechanism node and a superior mechanism node thereof according to the newly added mechanism hierarchical relationship;

and step S10206, establishing a connection relationship between the newly added agency node and the higher agency tax number node.

Fig. 6 shows the changed invoice information knowledge graph, where the secondary branch 32 is the newly added organization node, and the primary branch 3 (tax 3) is the superior organization tax node corresponding to the newly added organization node.

(3) And (4) a merging mechanism.

At this time, the change information in the invoice information change instruction includes organization information to be withdrawn (e.g., information such as organization number and organization name) and consolidation organization information (e.g., information such as organization number and organization name). The mechanism to be removed is referred to as the mechanism to be removed, and the transaction information of the removed mechanism is merged into the merging mechanism. After the mechanism to be cancelled is cancelled, if the invoicing information corresponding to the transaction between the client and the cancelled mechanism is received, the transaction of the cancelled mechanism can be inquired and merged in the merging mechanism through the invoice information knowledge graph, and the invoicing is completed according to the name and the tax number of the merging mechanism.

As shown in fig. 8, when receiving the invoice information change instruction, step S102 specifically includes:

step S10207, searching the mechanism node to be withdrawn and the corresponding connection relation thereof according to the mechanism information to be withdrawn, and determining a merging mechanism node according to the merging mechanism information;

step S10208, deleting the connection relationship corresponding to the mechanism node to be withdrawn, and establishing the connection relationship between the mechanism node to be withdrawn and the merging mechanism node.

Fig. 6 shows a changed invoice information knowledge graph, where the secondary branch 42 is a mechanism node to be removed, the primary branch 4 is a merging mechanism node, a connecting line between the secondary branch 42 and the tax numbers (tax numbers 6) of the primary branch 4 and the secondary branch 42 is changed into a dotted line to indicate that the connection relationship corresponding to the mechanism node to be removed fails, a newly added connecting line between the secondary branch 42 and the tax number (tax number 4) of the primary branch 4 indicates that the transaction of the secondary branch 42 is merged under the primary branch 4, and when the subsequent transaction related to the secondary branch 42 needs to be invoiced, the invoice invoicing operation is performed according to the tax number of the primary branch 4.

(4) The organization is not changed, and the tax number is changed.

At this time, the change information in the invoice information change instruction includes change agency information (e.g., information such as agency number, agency name, agency type, agency status, agency effective time) and change tax number information. The change mechanism herein refers to a mechanism for changing the tax number, and the tax number of the change mechanism is changed from the original tax number to the changed tax number.

As shown in fig. 9, when receiving the invoice information change instruction, step S102 specifically includes:

step S10209, determining a corresponding change mechanism node and a tax node having a connection relation with the change mechanism node according to the change mechanism information;

step S10210, applying the tax number in the changed tax number information to update the tax number node.

The changed invoice information knowledge graph is shown in fig. 6, where the secondary branch 31 is a change mechanism node, and the secondary branch 31 tax number (tax number new) is a change tax number.

(5) The mechanism is not changed, and the tax number is newly added and changed.

At this time, the change information in the invoice information change instruction includes change agency information (e.g., information such as agency number, agency name, agency type, agency status, agency effective time) and change tax number information. Wherein, the changing mechanism refers to a mechanism that changes the tax number, and the changing tax number refers to a new tax number different from the existing tax number in the invoice information knowledge map.

As shown in fig. 10, when receiving the invoice information change instruction, step S102 specifically includes:

step S10211, determining a corresponding change mechanism node and a tax node having a connection relation with the change mechanism node according to the change mechanism information;

step S10212, deleting the connection relationship between the change agency node and the tax number node;

step S10213, determining a newly added tax change node according to the tax change information;

step S10214, establishing a connection relationship between the change mechanism node and the tax change node.

The changed invoice information knowledge graph is shown in fig. 6, wherein the second-level branch 12 is a change mechanism node, the second-level branch 12 tax number (tax number 8) is a newly-added change tax number node, the connection line between the second-level branch 12 and the first-level branch 1 tax number (tax number 1) is changed into a broken line to indicate that the connection relationship between the second-level branch 12 and the first-level branch 1 tax number (tax number 1) is failed, and the newly-added connection line between the second-level branch 12 and the first-level branch 12 tax number (tax number 8) indicates that the tax number of the second-level branch 12 is changed into the tax number 8.

The method constructs a complete institution and tax number management map, when the client is used for invoicing, invoicing transaction inquiry is carried out through transaction information provided by the client, while transaction inquiry is carried out, the institution, the tax number and the change relation management map are constructed, so that real-time matching search of institution and tax number information is carried out, and invoicing is carried out according to the latest institution and tax information during invoicing. The speed of constructing the agency tax map and searching the matching map is much faster than the speed of updating the agency tax and transaction data through a traditional mode and operating the database, so that manual intervention and database operation are greatly reduced, and the performance and stable operation of the system database are better maintained.

Based on the same inventive concept, the embodiment of the present application further provides an invoice information updating apparatus based on a knowledge graph, which can be used to implement the method described in the above embodiment, as described in the following embodiment. Because the principle of solving the problems of the invoice information updating device based on the knowledge graph is similar to that of the invoice information updating method based on the knowledge graph, the implementation of the invoice information updating device based on the knowledge graph can refer to the implementation of the invoice information updating method based on the knowledge graph, and repeated parts are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

In a second aspect, the present application provides a knowledge-graph-based invoice information updating apparatus, as shown in fig. 11, the apparatus including:

a change instruction receiving module 301, configured to receive an invoice information change instruction;

a knowledge graph updating module 302, configured to update a pre-created invoice information knowledge graph according to change information of the invoice information change instruction, where the invoice information knowledge graph is pre-created by taking multiple organizations and tax numbers as nodes and taking a hierarchical relationship between the organizations and a corresponding relationship between the organizations and the tax numbers as edges;

and the information acquisition module 303 is configured to acquire an organization required for making an invoice and a corresponding tax number from the updated invoice information knowledge graph.

In one embodiment, as shown in fig. 12, the invoice information change instruction includes a new organization, and the change information includes information of the new organization, a hierarchical relationship of the new organization, and a tax number of the new organization;

the knowledge-graph update module 302 includes a mechanism addition unit 3021 configured to:

establishing a new mechanism node according to the new mechanism information;

In an embodiment, please continue to refer to fig. 12, the invoice information change instruction includes a merging mechanism, and the change information includes information of a mechanism to be merged and information of a merging mechanism;

the knowledge-graph update module 302 includes an institution-revocation unit 3022 to:

deleting the connection relation corresponding to the mechanism node to be removed, and establishing the connection relation between the mechanism node to be removed and the merging mechanism node.

In an embodiment, please continue to refer to fig. 12, the invoice information change instruction includes a change tax number, and the change information includes change agency information and change tax number information;

the knowledge-graph updating module 302 includes a tax number change unit 3023, configured to:

In one embodiment, as shown in fig. 13, the apparatus for updating invoice information based on a knowledge-graph further includes a knowledge-graph establishing module 304, configured to:

acquiring a plurality of organization information, hierarchical relations among the organizations and tax information of the organizations;

and establishing tax nodes according to the tax information of each organization, and establishing a connection relation between the organization nodes and the tax nodes according to the corresponding relation between the organizations and the tax.

In a third aspect, the present application further provides a computer device, and referring to fig. 14, the electronic device 100 specifically includes:

a central processing unit (processor) 110, a memory (memory) 120, a communication module (Communications) 130, an input unit 140, an output unit 150, and a power supply 160.

The memory (memory) 120, the communication module (Communications) 130, the input unit 140, the output unit 150, and the power supply 160 are respectively connected to the central processing unit (processor) 110. The memory 120 stores a computer program that can be called by the central processing unit 110, and the central processing unit 110 implements any one of the above-mentioned methods for updating the knowledge-graph-based invoice information when executing the computer program.

In a fifth aspect, the present application provides a computer program product comprising a computer program that, when executed by a processor, implements any of the methods for knowledge-graph based invoice information update provided herein.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A knowledge graph-based invoice information updating method is characterized by comprising the following steps:

receiving an invoice information change instruction;

updating a pre-established invoice information knowledge graph according to the change information in the invoice information change instruction, wherein the invoice information knowledge graph is pre-established by taking a plurality of organizations and tax numbers as nodes and taking the hierarchical relationship among the organizations and the corresponding relationship among the organizations and the tax numbers as sides;

2. The knowledge-graph-based invoice information updating method according to claim 1, wherein the invoice information change instruction includes a new organization, and the change information includes new organization information, new organization hierarchical relationship and new organization tax number;

establishing a new mechanism node according to the new mechanism information;

and determining tax number nodes according to the newly added agency tax number, and establishing a connection relation between the newly added agency node and the tax number nodes.

3. The knowledge-graph-based invoice information updating method according to claim 1, wherein the invoice information change instruction comprises a withdrawal mechanism, and the change information comprises information of a mechanism to be withdrawn and information of a merging mechanism;

4. The knowledge-graph-based invoice information updating method according to claim 1, wherein the invoice information change instruction comprises a change tax number, and the change information comprises change institution information and change tax number information;

5. The knowledge-graph-based invoice information updating method according to any one of claims 1 to 4, wherein the step of establishing the invoice information knowledge-graph comprises:

6. An invoice information updating device based on a knowledge graph is characterized by comprising:

the system comprises a knowledge graph updating module, a tax number updating module and a tax number updating module, wherein the knowledge graph updating module is used for updating a pre-established invoice information knowledge graph according to the change information of an invoice information change instruction, and the invoice information knowledge graph is pre-established by taking a plurality of organizations and tax numbers as nodes and taking the hierarchical relationship among the organizations and the corresponding relationship among the tax numbers as edges;

7. The knowledge-graph-based invoice information updating apparatus according to claim 6, wherein the invoice information change instruction comprises a new organization, and the change information comprises new organization information, new organization hierarchy relationship, and new organization tax number;

the knowledge graph updating module comprises a mechanism adding unit and is used for:

establishing a new mechanism node according to the new mechanism information;

8. The knowledge-graph-based invoice information updating apparatus according to claim 6, wherein the invoice information change instruction comprises a withdrawal mechanism, and the change information comprises information of a mechanism to be withdrawn and information of a merging mechanism;

9. The knowledge-graph-based invoice information updating apparatus of claim 6 wherein the invoice information change instructions include change tax numbers, the change information including change agency information and change tax number information;

10. The knowledge-graph-based invoice information updating apparatus according to any one of claims 6 to 9, further comprising a knowledge-graph establishing module for:

11. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of knowledge-graph based invoice information update of any of claims 1 to 5 when executing the computer program.

12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method for knowledge-graph-based invoice information update of any one of claims 1 to 5.

13. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the method of knowledge-graph based invoice information updating of any of claims 1 to 5.