CN106408358A - Invoice management method and invoice management apparatus - Google Patents
Invoice management method and invoice management apparatus Download PDFInfo
- Publication number
- CN106408358A CN106408358A CN201611124552.9A CN201611124552A CN106408358A CN 106408358 A CN106408358 A CN 106408358A CN 201611124552 A CN201611124552 A CN 201611124552A CN 106408358 A CN106408358 A CN 106408358A
- Authority
- CN
- China
- Prior art keywords
- invoice
- face data
- ticket face
- ticket
- model
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Character Input (AREA)
Abstract
The invention provides an invoice management method and an invoice management apparatus wherein the invoice management method comprises the following steps: when a signal is received concerning the management of an invoice, determining the attributes of the invoice wherein the attributes decide whether the invoice is a paper one or an electronic one; according to the attributes of the invoice, extracting the nominal value data of the invoice wherein the nominal value data includes the metadata and the corresponding nominal value; and based on the metadata, storing the nominal value corresponding to the metadata to a nominal value data model. For the technical schemes of the invention, it is possible to realize unified management for paper invoice and electronic invoice.
Description
Technical field
The present invention relates to managing bill technical field, in particular to a kind of invoice management method and a kind of invoice pipe
Reason device.
Background technology
According to《The State Tax Administration is with regard to carrying out issuing value-added tax electronics common invoice by value-added tax electronic invoice system
The bulletin of relevant issues》(State Tax Administration announce 2015 No. 84), country determines to carry out passing through value-added tax electronic invoice
The value-added tax electronics common invoice (abbreviation electronic invoice) that system is issued.
Electronic invoice is in purchasing and selling commodities, offer or to accept to service and be engaged in other business activities, with electron number
The bank settlement voucher issue according to mode, collect, storing, have can not distort, with low cost, easy interaction, the easily many-side such as storage
Advantage.Electronic invoice, due to its natural information characteristic, can help tax authority's message tube tax, helps consumer to tie up after sale
Power, helps enterprise to reduce the financial cost of managing bill.
In the invoice type such as value-added tax common invoice, VAT invoice, paper invoice (referred to as " paper ticket ") is still
Play a significant role.In daily productive life, after the completion of invoice issuing, how consumer must be in the face of manages simultaneously effectively
Reason paper invoice, the problem of electronic invoice.Submit an expense account link in invoice, if as the enterprise receiving ticket side it is necessary in the face of efficiently looking into
Test, file the problem of paper invoice.
And the information due to comprising on paper invoice, the propagation medium of electronic invoice is isomery, in prior art simultaneously
Do not enable the unified management to paper invoice and electronic invoice.
Therefore, how to realize the unified management of paper invoice and electronic invoice is become technical problem urgently to be resolved hurrily.
Content of the invention
The present invention is based on the problems referred to above it is proposed that a kind of new technical scheme, it is possible to achieve to paper invoice and electricity
The unified management of sub- invoice.
In view of this, a first aspect of the present invention proposes a kind of invoice management method, including：Receiving, invoice is entered
During the signal of line pipe reason, determine the attribute of described invoice, the attribute of described invoice includes paper invoice or electronic invoice；According to
The attribute of described invoice, extracts the ticket face data in described invoice, and wherein, described ticket face data includes metadata and it is corresponding
Numerical value；According to described metadata, corresponding for described metadata numerical value is stored in ticket face data model.
In this technical scheme, by extracting the ticket face data in invoice, ticket face data is stored ticket face data model
In, wherein, this invoice can be paper invoice, can also be electronic invoice, it is achieved thereby that to paper invoice and electronic invoice
Unified management.And solve invoice and originate various not manageable problem, thus convenient personal or enterprise scien`, efficiently
Ground management invoice, automatization's Business Processing of particularly paper invoice provides data supporting.
It is preferable that the described attribute according to described invoice in technique scheme, extract the nominal value number in described invoice
According to step, specifically include：If described invoice is paper invoice, described invoice is identified by the identification code of described invoice
Summary info, the Table Header information of described invoice, table body information and table tail information are obtained according to described summary info, pluck described
Want information, described Table Header information, described table body information and described table tail information as described ticket face data；If described invoice is electricity
Sub- invoice, then obtain the version file of described invoice, and the content of the version file of described invoice is parsed, with from described
Described ticket face data is parsed in ticket.
In this technical scheme, because paper invoice and electronic invoice are in the qualitative difference of storage medium, therefore, adopt
Different modes is extracting the ticket face data of both invoices, thus providing for the unified management of paper invoice and electronic invoice
Ensure.
It is preferable that described store ticket face data by corresponding for described metadata numerical value in any of the above-described technical scheme
After step in model, also include：Set up described in target index entry and the described ticket face data model in hash index table
Incidence relation between ticket face data；When receiving the signal inquiring about described invoice, obtain described metadata in described Hash
Multiple index entries at index position in concordance list；The corresponding described mesh of described invoice is found out in the plurality of index entry
Mark index entry；The described ticket face data associating with described target index entry is obtained from described ticket face data model.
In this technical scheme, by setting up the target index entry in hash index table and the nominal value in ticket face data model
Incidence relation between data, when inquiring about invoice, first obtains the index position in hash index table according to metadata, due to this
The item number of the multiple index entries at index position is fewer, therefore, can rapidly find out invoice in smaller scope
Corresponding target index entry, next just can obtain the nominal value number of invoice from ticket face data model according to target index entry
According to.Therefore, by above scheme, can rapidly invoice be inquired about.
It is preferable that also including in any of the above-described technical scheme：If described invoice is paper invoice, described extracting
After ticket face data in invoice, the ticket face data in described invoice is stored in the form of string assemble；If described
Invoice is electronic invoice, then after the ticket face data in extracting described invoice, by the ticket face data in described invoice with attribute
The form of table is stored.
In this technical scheme, by way of different, the ticket face data of paper invoice and electronic invoice is stored,
The compatibility and other system between can not only be kept, the also convenient ticket face data obtaining storage.
It is preferable that described ticket face data model is tree shaped model or attribute table model in any of the above-described technical scheme,
In the case that described ticket face data model is tree shaped model, the root node of described ticket face data model is the unique of described invoice
Coding, described root node includes at least one child node, and each child node at least one child node described is included at least
One leaf node.
In this technical scheme, ticket face data model is for tree shaped model it is ensured that the later stage looks into from ticket face data model
Ask the speed of ticket face data, ticket face data model is attribute table model it is ensured that storing the speed of ticket face data.Specifically permissible
Select ticket face data model according to actual demand, thus meeting the demand in varied situations to managing bill for the user.
A second aspect of the present invention proposes a kind of managing bill device, including：Determining unit, for receive to send out
During the signal that ticket is managed, determine the attribute of described invoice, the attribute of described invoice includes paper invoice or electronic invoice；
Extraction unit, for the attribute according to described invoice, extracts the ticket face data in described invoice, wherein, described ticket face data bag
Include metadata and its corresponding numerical value；First memory element, for according to described metadata, by corresponding for described metadata numerical value
Store in ticket face data model.
In this technical scheme, by extracting the ticket face data in invoice, ticket face data is stored ticket face data model
In, wherein, this invoice can be paper invoice, can also be electronic invoice, it is achieved thereby that to paper invoice and electronic invoice
Unified management.And solve invoice and originate various not manageable problem, thus convenient personal or enterprise scien`, efficiently
Ground management invoice, automatization's Business Processing of particularly paper invoice provides data supporting.
It is preferable that described extraction unit includes in technique scheme：Determination subelement, if for described invoice be
Paper invoice, then identify the summary info of described invoice by the identification code of described invoice, obtained according to described summary info
Take the table body information of described invoice, using described summary info and described table body information as described ticket face data；Parsing subelement,
If being electronic invoice for described invoice, obtain the version file of described invoice, the content to the version file of described invoice
Parsed, to parse described ticket face data from described invoice.
In this technical scheme, because paper invoice and electronic invoice are in the qualitative difference of storage medium, therefore, adopt
Different modes is extracting the ticket face data of both invoices, thus providing for the unified management of paper invoice and electronic invoice
Ensure.
It is preferable that also including in any of the above-described technical scheme：Set up unit, for setting up the mesh in hash index table
Incidence relation between ticket face data described in mark index entry and described ticket face data model；Acquiring unit, for receiving
Inquire about described invoice signal when, obtain multiple indexes at the index position in described hash index table for the described metadata
?；Searching unit, for finding out the corresponding described target index entry of described invoice in the plurality of index entry；Described acquisition
Unit is additionally operable to, and obtains the described ticket face data associating with described target index entry from described ticket face data model.
In this technical scheme, by setting up the target index entry in hash index table and the nominal value in ticket face data model
Incidence relation between data, when inquiring about invoice, first obtains the index position in hash index table according to metadata, due to this
The item number of the multiple index entries at index position is fewer, therefore, can rapidly find out invoice in smaller scope
Corresponding target index entry, next just can obtain the nominal value number of invoice from ticket face data model according to target index entry
According to.Therefore, by above scheme, can rapidly invoice be inquired about.
It is preferable that also including in any of the above-described technical scheme：Second memory element, if be papery for described invoice
Invoice, then after the ticket face data in extracting described invoice, by the ticket face data in described invoice with the shape of string assemble
Formula is stored；Described second memory element is additionally operable to, if described invoice is electronic invoice, the ticket in extracting described invoice
After the data of face, the ticket face data in described invoice is stored in the form of attribute list.
In this technical scheme, by way of different, the ticket face data of paper invoice and electronic invoice is stored,
The compatibility and other system between can not only be kept, the also convenient ticket face data obtaining storage.
It is preferable that described ticket face data model is tree shaped model or attribute table model in any of the above-described technical scheme,
In the case that described ticket face data model is tree shaped model, the root node of described ticket face data model is the unique of described invoice
Coding, described root node includes at least one child node, and each child node at least one child node described is included at least
One leaf node.
In this technical scheme, ticket face data model is for tree shaped model it is ensured that the later stage looks into from ticket face data model
Ask the speed of ticket face data, ticket face data model is attribute table model it is ensured that storing the speed of ticket face data.Specifically permissible
Select ticket face data model according to actual demand, thus meeting the demand in varied situations to managing bill for the user.
By technical scheme, it is possible to achieve the unified management to paper invoice and electronic invoice.
Brief description
Fig. 1 shows the schematic flow sheet of invoice management method according to an embodiment of the invention；
Fig. 2 shows the schematic flow sheet of invoice management method according to another embodiment of the invention；
Fig. 3 shows the schematic diagram of the text data of invoice according to an embodiment of the invention；
Fig. 4 shows the schematic diagram of data model according to an embodiment of the invention；
Fig. 5 shows the principle schematic of invoice inquiry according to an embodiment of the invention；
Fig. 6 shows the structural representation of managing bill device according to an embodiment of the invention.
Specific embodiment
In order to the above objects, features and advantages of the present invention can be more clearly understood that, below in conjunction with the accompanying drawings and specifically real
Mode of applying is further described in detail to the present invention.It should be noted that in the case of not conflicting, the enforcement of the application
Feature in example and embodiment can be mutually combined.
Elaborate a lot of details in the following description in order to fully understand the present invention, but, the present invention also may be used
To be implemented different from other modes described here using other, therefore, protection scope of the present invention is not described below
Specific embodiment restriction.
Fig. 1 shows the schematic flow sheet of invoice management method according to an embodiment of the invention.
As shown in figure 1, invoice management method according to an embodiment of the invention, including：
Step 102, when receiving the signal that invoice is managed, determines the attribute of described invoice, described invoice
Attribute includes paper invoice or electronic invoice.
Step 104, according to the attribute of described invoice, extracts the ticket face data in described invoice, wherein, described ticket face data
Including metadata and its corresponding numerical value.
Step 106, according to described metadata, corresponding for described metadata numerical value is stored in ticket face data model.
In this technical scheme, by extracting the ticket face data in invoice, ticket face data is stored ticket face data model
In, wherein, this invoice can be paper invoice, can also be electronic invoice, it is achieved thereby that to paper invoice and electronic invoice
Unified management.And solve invoice and originate various not manageable problem, thus convenient personal or enterprise scien`, efficiently
Ground management invoice, automatization's Business Processing of particularly paper invoice provides data supporting.
It is preferable that described step 104 specifically includes in technique scheme：If described invoice is paper invoice, lead to
Cross the identification code of the described invoice summary info to identify described invoice, obtain the table of described invoice according to described summary info
Header, table body information and table tail information, by described summary info, described Table Header information, described table body information and described table tail
Information is as described ticket face data；If described invoice is electronic invoice, obtain the version file of described invoice, to described invoice
The content of version file parsed, to parse described ticket face data from described invoice.
In this technical scheme, because paper invoice and electronic invoice are in the qualitative difference of storage medium, therefore, adopt
Different modes is extracting the ticket face data of both invoices, thus providing for the unified management of paper invoice and electronic invoice
Ensure.
It is preferable that after step 106, also including in any of the above-described technical scheme：Set up the target in hash index table
Incidence relation between ticket face data described in index entry and described ticket face data model；Receiving the letter inquiring about described invoice
Number when, obtain multiple index entries at the index position in described hash index table for the described metadata；In the plurality of index
The corresponding described target index entry of described invoice is found out in；Obtain from described ticket face data model and described target index
The described ticket face data of item association.
In this technical scheme, by setting up the target index entry in hash index table and the nominal value in ticket face data model
Incidence relation between data, when inquiring about invoice, first obtains the index position in hash index table according to metadata, due to this
The item number of the multiple index entries at index position is fewer, therefore, can rapidly find out invoice in smaller scope
Corresponding target index entry, next just can obtain the nominal value number of invoice from ticket face data model according to target index entry
According to.Therefore, by above scheme, can rapidly invoice be inquired about.
It is preferable that also including in any of the above-described technical scheme：If described invoice is paper invoice, described extracting
After ticket face data in invoice, the ticket face data in described invoice is stored in the form of string assemble；If described
Invoice is electronic invoice, then after the ticket face data in extracting described invoice, by the ticket face data in described invoice with attribute
The form of table is stored.
In this technical scheme, by way of different, the ticket face data of paper invoice and electronic invoice is stored,
The compatibility and other system between can not only be kept, the also convenient ticket face data obtaining storage.
It is preferable that described ticket face data model is tree shaped model or attribute table model in any of the above-described technical scheme,
In the case that described ticket face data model is tree shaped model, the root node of described ticket face data model is the unique of described invoice
Coding, described root node includes at least one child node, and each child node at least one child node described is included at least
One leaf node.
In this technical scheme, ticket face data model is for tree shaped model it is ensured that the later stage looks into from ticket face data model
Ask the speed of ticket face data, ticket face data model is attribute table model it is ensured that storing the speed of ticket face data.Specifically permissible
Select ticket face data model according to actual demand, thus meeting the demand in varied situations to managing bill for the user.
Fig. 2 shows the schematic flow sheet of invoice management method according to another embodiment of the invention.
As shown in Fig. 2 invoice management method according to another embodiment of the invention, including three following steps：
First, extract the ticket face data in invoice, two, isomery ticket face data normalized, three, invoice unification collects.
First, extract the ticket face data in invoice.
If invoice be paper invoice, by scan paper invoice on identification code (for example, identification code be Quick Response Code or
Bar code), to obtain the corresponding text data of identification code, as shown in figure 3, text data include the version of invoice, invoice type,
Invoice codes, invoice number, Amount in Total, date of making out an invoice, invoice check code and CRC check code.Because this article notebook data is one
String text-string, the character feature of analysis this article notebook data, according to preset text feature rule, extracts summary letter therein
Breath.According to summary info, invoice data is checked, to obtain Table Header information, table body information and the table tail information of invoice.Look into
Test the paper invoice completing and will be provided with complete ticket face data and (at least include summary info, Table Header information, table body information and table tail
Information), afterwards complete ticket face data is stored, use for subsequent logic.
If invoice is electronic invoice, automatically extract the board-like literary composition of invoice from the receipts ticket mailbox adnexa of invoice holder
Part it is also possible to obtain user manual on the board-like file of invoice that is conducted into, after the layout files obtaining electronic invoice, directly
The content of parsing layout files, you can obtain complete ticket face data.Wherein, this ticket face data at least includes summary info, table
Header, table body information and table tail information, the file of layout files PDF.
2nd, isomery ticket face data normalized.
By tree shaped model, the ticket face data of electronic invoice and paper invoice can be stored.As shown in figure 4, it is tree-shaped
The root node of model is the unique encodings of invoice, and this unique encodings can be system is a newly-generated coding of invoice, also may be used
Being invoice codes or invoice number, or the combination of invoice codes and invoice number.The unique encodings of invoice have 4 sons
Node, respectively " invoice summary info ", " invoice Table Header information ", " invoice table body information ", " invoice table tail information ".This 4
Child node has respective leaf node respectively, and leaf node stores specific ticket face data.From fig. 4, it can be seen that tree-shaped mould
Type possesses higher hierarchical structure and ability to express.
Attribute list (comprising multiple " key/value to the ") model of tile arrangement except tree shaped model, can also be set up.Attribute list
In " key " be above-mentioned leaf node title, " value " be corresponding ticket face data.
The ticket face data extracted from paper invoice is stored in the form of string assemble.The ticket face data of electronic invoice
Stored in the form of attribute list.
If the string assemble of the ticket face data of paper invoice is L, Li(i=1,2 ..., n) represent that ticket face data is corresponding
Numerical value.The metadata set of invoice is combined into MetaSet={ invoice codes ..., marketing unit }, the genus of the ticket face data of electronic invoice
Property table be M, M (k)=v, (k ∈ MetaSet, v are the corresponding numerical value of ticket face data).If function V (x) represents the corresponding data of x
Value.
Tree shaped model is T, rightRepresent the value of node t, wherein,
T={ Abstract, Header, Body, Footer, Features }
Abstract={ invoice codes, invoice number are made out an invoice the date, check code }
Header={ purchaser's title, Taxpayer Identification Number, address, phone, bank of deposit, account }
Body={ account sales, valency tax adds up to }
Footer=seller title, Taxpayer Identification Number ..., marketing unit }
Features=feature 1 ... }
The step ticket face data of invoice being stored in tree shaped model specifically includes：
And
And
For the ticket face data of paper invoice, take out any value, according to the metadata of this numerical value, this numerical value is put into tree
In the leaf node of shape model.
The metadata concentrated for the ticket face data of electronic invoice, ergodic data, corresponding numerical value is put into tree shaped model
In the leaf node of same metadata in.
3rd, invoice unification collects.
Classification can be executed automatically to the ticket face data of invoice, support manual classification simultaneously.The categorical data storage of invoice
Below the child node of " the invoice feature " of invoice root node.After the completion of classification, automatically extract invoice key word, such as " buy
Item Title in square title, seller title, account sales " etc..Invoice key word is stored under " invoice feature " child node
Face.
Invoice index adopts hash index algorithm, and this algorithm, compared with B+ tree, possesses faster matching speed.Set up index
Step specifically include：Set up associating between the target index entry in hash index table and ticket face data in ticket face data model
Relation.As shown in figure 5, when receiving the signal of inquiry invoice, metadata, through hash algorithm, finds out this metadata and is breathing out
Index position in uncommon concordance list, has multiple index entries, finds out invoice corresponding in multiple index entries at this index position
Target index entry, due to having been set up incidence relation between target index entry and the ticket face data of invoice, therefore, it can from ticket
The ticket face data associating with target index entry is obtained in the data model of face.
Fig. 6 shows the structural representation of managing bill device according to an embodiment of the invention.
As shown in fig. 6, managing bill device 600 according to an embodiment of the invention, including：Determining unit 602, carry
Take unit 604 and the first memory element 606.
Determining unit 602, for when receiving the signal that invoice is managed, determining the attribute of described invoice, institute
The attribute stating invoice includes paper invoice or electronic invoice；Extraction unit 604, for the attribute according to described invoice, extracts
Ticket face data in described invoice, wherein, described ticket face data includes metadata and its corresponding numerical value；First memory element
606, for according to described metadata, corresponding for described metadata numerical value being stored in ticket face data model.
In this technical scheme, by extracting the ticket face data in invoice, ticket face data is stored ticket face data model
In, wherein, this invoice can be paper invoice, can also be electronic invoice, it is achieved thereby that to paper invoice and electronic invoice
Unified management.And solve invoice and originate various not manageable problem, thus convenient personal or enterprise scien`, efficiently
Ground management invoice, automatization's Business Processing of particularly paper invoice provides data supporting.
It is preferable that described extraction unit 604 includes in technique scheme：Determination subelement 6042, if for described
Invoice is paper invoice, then identify the summary info of described invoice by the identification code of described invoice, according to described summary
The table body information of invoice described in acquisition of information, using described summary info and described table body information as described ticket face data；Parsing
Subelement 6044, if being electronic invoice for described invoice, obtains the version file of described invoice, the version to described invoice
The content of file is parsed, to parse described ticket face data from described invoice.
In this technical scheme, because paper invoice and electronic invoice are in the qualitative difference of storage medium, therefore, adopt
Different modes is extracting the ticket face data of both invoices, thus providing for the unified management of paper invoice and electronic invoice
Ensure.
It is preferable that managing bill device 600 also includes in any of the above-described technical scheme：Set up unit 608, be used for building
Incidence relation between ticket face data described in target index entry in vertical hash index table and described ticket face data model；Obtain
Unit 610, for when receiving the signal inquiring about described invoice, obtaining rope in described hash index table for the described metadata
Draw the multiple index entries at position；Searching unit 612, for finding out the corresponding institute of described invoice in the plurality of index entry
State target index entry；Described acquiring unit 610 is additionally operable to, and obtains and close with described target index entry from described ticket face data model
The described ticket face data of connection.
In this technical scheme, by setting up the target index entry in hash index table and the nominal value in ticket face data model
Incidence relation between data, when inquiring about invoice, first obtains the index position in hash index table according to metadata, due to this
The item number of the multiple index entries at index position is fewer, therefore, can rapidly find out invoice in smaller scope
Corresponding target index entry, next just can obtain the nominal value number of invoice from ticket face data model according to target index entry
According to.Therefore, by above scheme, can rapidly invoice be inquired about.
It is preferable that managing bill device 600 also includes in any of the above-described technical scheme：Second memory element 614, uses
If being paper invoice in described invoice, after the ticket face data in extracting described invoice, by the nominal value number in described invoice
The form of string assemble is stored according to this；Described second memory element 614 is additionally operable to, if described invoice is electronic invoice,
Then after the ticket face data in extracting described invoice, the ticket face data in described invoice is deposited in the form of attribute list
Storage.
In this technical scheme, by way of different, the ticket face data of paper invoice and electronic invoice is stored,
The compatibility and other system between can not only be kept, the also convenient ticket face data obtaining storage.
It is preferable that described ticket face data model is tree shaped model or attribute table model in any of the above-described technical scheme,
In the case that described ticket face data model is tree shaped model, the root node of described ticket face data model is the unique of described invoice
Coding, described root node includes at least one child node, and each child node at least one child node described is included at least
One leaf node.
In this technical scheme, ticket face data model is for tree shaped model it is ensured that the later stage looks into from ticket face data model
Ask the speed of ticket face data, ticket face data model is attribute table model it is ensured that storing the speed of ticket face data.Specifically permissible
Select ticket face data model according to actual demand, thus meeting the demand in varied situations to managing bill for the user.
Technical scheme is described in detail above in association with accompanying drawing, by technical scheme, it is possible to achieve
Unified management to paper invoice and electronic invoice.
In the present invention, term " first ", " second " are only used for the purpose describing, and it is not intended that instruction or hint phase
To importance；Term " multiple " represents two or more.For the ordinary skill in the art, can be according to tool
Body situation understands above-mentioned term concrete meaning in the present invention.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for the skill of this area
For art personnel, the present invention can have various modifications and variations.All within the spirit and principles in the present invention, made any repair
Change, equivalent, improvement etc., should be included within the scope of the present invention.
Claims (10)
1. a kind of invoice management method is it is characterised in that include：
When receiving the signal that invoice is managed, determine the attribute of described invoice, the attribute of described invoice includes papery
Invoice or electronic invoice；
According to the attribute of described invoice, extract the ticket face data in described invoice, wherein, described ticket face data include metadata and
Its corresponding numerical value；
According to described metadata, corresponding for described metadata numerical value is stored in ticket face data model.
2. invoice management method according to claim 1, it is characterised in that the described attribute according to described invoice, is extracted
The step of the ticket face data in described invoice, specifically includes：
If described invoice is paper invoice, identify the summary info of described invoice, root by the identification code of described invoice
Obtain Table Header information, table body information and the table tail information of described invoice according to described summary info, by described summary info, described table
Header, described table body information and described table tail information are as described ticket face data；
If described invoice is electronic invoice, obtain the version file of described invoice, the content to the version file of described invoice
Parsed, to parse described ticket face data from described invoice.
3. invoice management method according to claim 1 is it is characterised in that described deposit corresponding for described metadata numerical value
After storing up the step in ticket face data model, also include：
Set up the target index entry in hash index table and associating between ticket face data described in described ticket face data model
System；
When receiving the signal inquiring about described invoice, obtain described metadata at the index position in described hash index table
Multiple index entries；
The corresponding described target index entry of described invoice is found out in the plurality of index entry；
The described ticket face data associating with described target index entry is obtained from described ticket face data model.
4. invoice management method according to any one of claim 1 to 3 is it is characterised in that also include：
If described invoice is paper invoice, after the ticket face data in extracting described invoice, by the nominal value in described invoice
Data is stored in the form of string assemble；
If described invoice is electronic invoice, after the ticket face data in extracting described invoice, by the nominal value in described invoice
Data is stored in the form of attribute list.
5. invoice management method according to any one of claim 1 to 3 is it is characterised in that described ticket face data model
For tree shaped model or attribute table model, in the case that described ticket face data model is tree shaped model, described ticket face data mould
The root node of type is the unique encodings of described invoice, and described root node includes at least one child node, at least one son described
Each child node in node includes at least one leaf node.
6. a kind of managing bill device is it is characterised in that include：
Determining unit, for when receiving the signal that invoice is managed, determining the attribute of described invoice, described invoice
Attribute includes paper invoice or electronic invoice；
Extraction unit, for the attribute according to described invoice, extracts the ticket face data in described invoice, wherein, described nominal value number
According to inclusion metadata and its corresponding numerical value；
First memory element, for according to described metadata, corresponding for described metadata numerical value being stored ticket face data model
In.
7. managing bill device according to claim 6 is it is characterised in that described extraction unit includes：
Determination subelement, if being paper invoice for described invoice, identifies described sending out by the identification code of described invoice
The summary info of ticket, obtains the table body information of described invoice, by described summary info and described table body according to described summary info
Information is as described ticket face data；
Parsing subelement, if being electronic invoice for described invoice, obtains the version file of described invoice, to described invoice
The content of version file is parsed, to parse described ticket face data from described invoice.
8. managing bill device according to claim 6 is it is characterised in that also include：
Set up unit, for setting up the target index entry in hash index table and ticket face data described in described ticket face data model
Between incidence relation；
Acquiring unit, for when receiving the signal inquiring about described invoice, obtaining described metadata in described hash index table
In index position at multiple index entries；
Searching unit, for finding out the corresponding described target index entry of described invoice in the plurality of index entry；
Described acquiring unit is additionally operable to, and obtains the described nominal value associating with described target index entry from described ticket face data model
Data.
9. the managing bill device according to any one of claim 6 to 8 is it is characterised in that also include：
Second memory element, if being paper invoice for described invoice, after the ticket face data in extracting described invoice, will
Ticket face data in described invoice is stored in the form of string assemble；
Described second memory element is additionally operable to, if described invoice is electronic invoice, the ticket face data in extracting described invoice
Afterwards, the ticket face data in described invoice is stored in the form of attribute list.
10. the managing bill device according to any one of claim 6 to 8 is it is characterised in that described ticket face data model
For tree shaped model or attribute table model, in the case that described ticket face data model is tree shaped model, described ticket face data mould
The root node of type is the unique encodings of described invoice, and described root node includes at least one child node, at least one son described
Each child node in node includes at least one leaf node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611124552.9A CN106408358A (en) | 2016-12-08 | 2016-12-08 | Invoice management method and invoice management apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611124552.9A CN106408358A (en) | 2016-12-08 | 2016-12-08 | Invoice management method and invoice management apparatus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106408358A true CN106408358A (en) | 2017-02-15 |
Family
ID=58083844
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611124552.9A Pending CN106408358A (en) | 2016-12-08 | 2016-12-08 | Invoice management method and invoice management apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106408358A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777397A (en) * | 2017-03-02 | 2017-05-31 | 百望电子发票数据服务有限公司 | A kind of electronic invoice data hoc queries method and system |
| CN107424065A (en) * | 2017-05-15 | 2017-12-01 | 贾琨 | The method and system of electronic invoice in a kind of processing Email |
| CN108364042A (en) * | 2018-01-02 | 2018-08-03 | 山东浪潮通软信息科技有限公司 | A kind of invoice management method, device and business platform |
| CN108921240A (en) * | 2018-06-12 | 2018-11-30 | 新乡学院 | A kind of invoice code identification sorting system |
| CN109146584A (en) * | 2018-08-10 | 2019-01-04 | 海南高灯科技有限公司 | A kind of electronic invoice collects system and collecting method |
| CN109359127A (en) * | 2018-09-07 | 2019-02-19 | 彩讯科技股份有限公司 | A kind of querying method of electronic invoice, device, equipment and storage medium |
| CN110348441A (en) * | 2019-07-10 | 2019-10-18 | 深圳市华云中盛科技有限公司 | VAT invoice recognition methods, device, computer equipment and storage medium |
| CN111178993A (en) * | 2019-12-26 | 2020-05-19 | 航天信息股份有限公司企业服务分公司 | Method and system for automatically calling invoice electronic file based on invoice container |
| CN111190999A (en) * | 2019-12-18 | 2020-05-22 | 航天信息股份有限公司 | Correlation query method and system for red and blue electronic invoices |
| CN111899080A (en) * | 2019-05-05 | 2020-11-06 | 广州磐信计算机科技有限公司 | Intelligent invoice collection system |
| CN112131470A (en) * | 2020-09-23 | 2020-12-25 | 欧冶云商股份有限公司 | Invoice three-bill matching method based on linear optimization |
| CN112395465A (en) * | 2020-11-24 | 2021-02-23 | 维沃移动通信有限公司 | Invoice data processing method and device, electronic equipment and readable storage medium |
| CN113469759A (en) * | 2021-06-29 | 2021-10-01 | 平安养老保险股份有限公司 | Method, device and equipment for intelligently generating invoice and storage medium |
| CN116824604A (en) * | 2023-08-30 | 2023-09-29 | 江苏苏宁银行股份有限公司 | Financial data management method and system based on image processing |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609775A (en) * | 2011-04-28 | 2012-07-25 | 许晓飞 | Personal consumption record invoice collecting system |
| CN103164810A (en) * | 2013-04-12 | 2013-06-19 | 重庆市远大印务有限公司 | Electronic invoice service system based on cloud computing technology and big data technology |
| CN104463649A (en) * | 2015-01-07 | 2015-03-25 | 税友软件集团股份有限公司 | Invoice recording method and system |
| CN105023340A (en) * | 2015-07-09 | 2015-11-04 | 胡昭 | Cloud intelligent invoice identification and examination system and method based on scanner |
-
2016
- 2016-12-08 CN CN201611124552.9A patent/CN106408358A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609775A (en) * | 2011-04-28 | 2012-07-25 | 许晓飞 | Personal consumption record invoice collecting system |
| CN103164810A (en) * | 2013-04-12 | 2013-06-19 | 重庆市远大印务有限公司 | Electronic invoice service system based on cloud computing technology and big data technology |
| CN104463649A (en) * | 2015-01-07 | 2015-03-25 | 税友软件集团股份有限公司 | Invoice recording method and system |
| CN105023340A (en) * | 2015-07-09 | 2015-11-04 | 胡昭 | Cloud intelligent invoice identification and examination system and method based on scanner |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777397A (en) * | 2017-03-02 | 2017-05-31 | 百望电子发票数据服务有限公司 | A kind of electronic invoice data hoc queries method and system |
| CN107424065A (en) * | 2017-05-15 | 2017-12-01 | 贾琨 | The method and system of electronic invoice in a kind of processing Email |
| CN108364042A (en) * | 2018-01-02 | 2018-08-03 | 山东浪潮通软信息科技有限公司 | A kind of invoice management method, device and business platform |
| CN108921240A (en) * | 2018-06-12 | 2018-11-30 | 新乡学院 | A kind of invoice code identification sorting system |
| CN109146584B (en) * | 2018-08-10 | 2021-06-08 | 深圳高灯计算机科技有限公司 | Electronic invoice collecting system and collecting method |
| CN109146584A (en) * | 2018-08-10 | 2019-01-04 | 海南高灯科技有限公司 | A kind of electronic invoice collects system and collecting method |
| CN109359127A (en) * | 2018-09-07 | 2019-02-19 | 彩讯科技股份有限公司 | A kind of querying method of electronic invoice, device, equipment and storage medium |
| CN111899080A (en) * | 2019-05-05 | 2020-11-06 | 广州磐信计算机科技有限公司 | Intelligent invoice collection system |
| CN110348441A (en) * | 2019-07-10 | 2019-10-18 | 深圳市华云中盛科技有限公司 | VAT invoice recognition methods, device, computer equipment and storage medium |
| CN110348441B (en) * | 2019-07-10 | 2021-08-17 | 深圳市华云中盛科技股份有限公司 | Value-added tax invoice identification method and device, computer equipment and storage medium |
| CN111190999A (en) * | 2019-12-18 | 2020-05-22 | 航天信息股份有限公司 | Correlation query method and system for red and blue electronic invoices |
| CN111178993A (en) * | 2019-12-26 | 2020-05-19 | 航天信息股份有限公司企业服务分公司 | Method and system for automatically calling invoice electronic file based on invoice container |
| CN112131470B (en) * | 2020-09-23 | 2024-03-12 | 欧冶云商股份有限公司 | Invoice three-order matching method based on linear optimization |
| CN112131470A (en) * | 2020-09-23 | 2020-12-25 | 欧冶云商股份有限公司 | Invoice three-bill matching method based on linear optimization |
| CN112395465A (en) * | 2020-11-24 | 2021-02-23 | 维沃移动通信有限公司 | Invoice data processing method and device, electronic equipment and readable storage medium |
| CN112395465B (en) * | 2020-11-24 | 2022-07-12 | 维沃移动通信有限公司 | Invoice data processing method and device, electronic equipment and readable storage medium |
| CN113469759A (en) * | 2021-06-29 | 2021-10-01 | 平安养老保险股份有限公司 | Method, device and equipment for intelligently generating invoice and storage medium |
| CN116824604A (en) * | 2023-08-30 | 2023-09-29 | 江苏苏宁银行股份有限公司 | Financial data management method and system based on image processing |
| CN116824604B (en) * | 2023-08-30 | 2023-11-21 | 江苏苏宁银行股份有限公司 | Financial data management method and system based on image processing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106408358A (en) | Invoice management method and invoice management apparatus | |
| CN107608958B (en) | Contract text risk information mining method and system based on unified modeling of clauses | |
| CN106372798B (en) | A kind of customized contract generation method of user based on risk and system | |
| CN108960223A (en) | The method for automatically generating voucher based on bill intelligent recognition | |
| CN102622443A (en) | Customized screening system and method for microblog | |
| CN104915334A (en) | Automatic extraction method of key information of bidding project based on semantic analysis | |
| JP2008515061A (en) | A method for searching data elements on the web using conceptual and contextual metadata search engines | |
| CN106296385A (en) | A kind of book keeping operation section purpose arranges and recommends method | |
| US20130275451A1 (en) | Systems And Methods For Contract Assurance | |
| CN106095964A (en) | A kind of method that data are carried out visualization filing and search | |
| CN103903082A (en) | Method for generating accounting documents by means of receipt data in ERP system | |
| CN107679977A (en) | A kind of tax administration platform and implementation method based on semantic analysis | |
| CN107430504A (en) | Data-translating system and method | |
| US11748368B1 (en) | Data field transaction repair interface | |
| CN107609151A (en) | The method that XBRL instance documents caching is realized based on Redis | |
| CN105589897B (en) | Report methods of exhibiting and system based on XBRL | |
| CN110222180A (en) | A kind of classification of text data and information mining method | |
| CN105718457B (en) | Information pushing method and system based on electronic bill | |
| CN109902215A (en) | A kind of method and system of deals match | |
| US8719007B2 (en) | Determining offer terms from text | |
| JP2020030517A (en) | Accounting processor, accounting method, accounting program | |
| CN107357930A (en) | Cloud account mill platform tenant data table structure | |
| CN105260411B (en) | Based on XBRL realize financial report detailed data collect and lower brill system and method | |
| CN112183037A (en) | Data classification and summarization method and system in parallel enterprise finance and tax SaaS system | |
| KR102205637B1 (en) | Address abbreviated waybill |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170215 |
|
| RJ01 | Rejection of invention patent application after publication |