WO2017133570A1

WO2017133570A1 - Invoice title information change method and apparatus and invoice management system

Info

Publication number: WO2017133570A1
Application number: PCT/CN2017/072406
Authority: WO
Inventors: 段亚军; 王均方
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2016-02-05
Filing date: 2017-01-24
Publication date: 2017-08-10
Also published as: TW201802739A; CN107045695A

Abstract

An embodiment of the present invention provides an invoice title information change method and apparatus and an invoice management system. The method comprises: receiving an invoice title information change request submitted by a user; determining, on the basis of a preset rule, whether the change request needs to be reviewed; if a review is required, then generating a corresponding shadow title data table based on the change request, wherein the shadow title data table comprises original title information, new title information and current change record information; if the new title information passes the review, then changing old invoice title information to the new title information; and updating a new title state in the current change record information within the shadow title data table to effective and an old title state in the current change record information to ineffective. An embodiment of the present invention can change the invoice title information more accurately and efficiently, and can improve user experience.

Description

Method, device and invoice management system for changing invoice header information

This application claims the priority of the Chinese Patent Application No. 201610080755.6, entitled "Invoicing Header Information Change Method, Apparatus and Invoice Management System", which is filed on February 5, 2016, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present application relates to the field of information processing technologies, and in particular, to a method and device for changing invoice header information, and an invoice management system.

Background technique

Today, with the widespread use of e-commerce applications, with the rapid development of information technology, information has exploded, and people are increasingly demanding how to process information more efficiently. For example, in the Invoice Management Center, users can manage the invoicing information. For invoice header information that has been in effect in the system, the user may need to change the invoice header information for various reasons. However, because the rigor of the financial review requirements of different invoice types is different, the items that are allowed to change in the process of changing the invoice header information are also different. The situation in which the header information of the change requires financial review is also different. In addition, there are many situations in which the status of the invoice header is in the change process, which makes the mutual transfer relationship between multiple states more complicated. If the user wants to make changes to some type of invoice header information that has already taken effect, and the number of changes may be more than once; then, when the user makes several changes to the invoice header information, if needed due to certain circumstances The process of this change is terminated, and the prior art cannot provide the process of canceling the change operation. Therefore, when the user changes the invoice header information, the defects of the prior art will bring a lot of changes to the user.

Therefore, how to change the invoice header information more accurately and efficiently becomes a technical problem that needs to be solved by those skilled in the art.

Summary of the invention

In view of the above problems, embodiments of the present application have been made in order to provide an invoice header change method and a corresponding invoice header change device, and an invoice management system, which overcome the above problems or at least partially solve the above problems.

The application discloses a method for changing the invoice header information, including:

Receiving an invoice header change request submitted by the user;

Determining whether the change request needs to be audited based on a preset rule;

If the auditing is required, generating a corresponding shadow header data table based on the change request, where the shadow header data table includes original header information, new header information, and current change record information;

If the new header information is approved, the old header information of the invoice is changed to the new header information; and the new header status of the current change record information in the shadow header data table is updated to be valid, and the old header status is invalid.

Correspondingly, the present application discloses an invoice header information changing device, including:

a receiving module, configured to receive an invoice header information change request submitted by a user;

a determining module, configured to determine, according to a preset rule, whether the change request received by the receiving module needs to be audited;

a generating module, configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change record information, if the determining module determines that the audit is required to be performed;

a change module, configured to: if the new header information is approved, change the old header information of the invoice to the new header information; correspondingly, the generating module is further configured to update a new header of the current change record information in the shadow header data table. The status is valid and the old header status is invalid.

The application also discloses a method for changing the invoice header information, including:

Receiving an invoice header change request submitted by the user;

If the preset condition is met, the invoice new header information is restored to the old header information that has been in effect before the change based on the user-submitted revocation change request and the current change record information of the shadow header data table; and The new header state of the current change record information in the shadow header data table is undo, and the old header state is valid.

And a generating module, configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change, if the determining module determines that the audit is required to be performed. record information;

a searching module, configured to search for current change record information of the shadow header data table based on a revocation change request submitted by the user received by the receiving module, if the preset condition is met;

a change module, configured to restore, according to the current change record information found by the lookup module, the invoice new header information to the old header information that has been in effect before the change; correspondingly, the generating module is further configured to update the The new header state of the current change record information in the shadow header data table is undo, and the old header state is valid.

The present application also discloses an invoice management system including the invoice header information changing device as described above.

According to a specific embodiment provided by the present application, the present application discloses the following technical effects:

In the process of changing the invoice header information, the embodiment may generate a corresponding shadow header data table based on the change request, and may search for the original header information, the new header information, and the current change record information included in the shadow header data table. Improve the user experience by accurately and efficiently changing the invoice header information.

Further, when the user needs to perform the undo operation after encountering a certain number of changes to the invoice header information, the new header information is restored to the change by the current change record information in the shadow header data table. The old header information that has been in effect before; the flag information of the current change record information in the shadow header data table can be used to effectively find the current state information and the state transition relationship of the new header and the old header, so that the invoice header can be restored to the change. An intermediate state or original state before, and provides real-time data rollback, which is more effective in troubleshooting errors throughout the change process.

In addition, with the embodiment of the present application, the change of the invoice header information can be performed more accurately and efficiently, and the maintenance and update of the invoice management system is more convenient, and the development difficulty and the maintenance cost are also reduced.

Of course, implementing any of the products of the present application does not necessarily require all of the advantages described above to be achieved at the same time.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some of the present application. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

1 is a flow chart showing the steps of an embodiment of a method for changing invoice header information according to the present application;

2 is a schematic diagram of an embodiment of generating a shadow header data table according to a change request according to the present application;

3 is a flow chart showing the steps of another embodiment of the method for changing invoice header information of the present application;

4 is a schematic diagram of an embodiment of an invoice header information change process state transition of the present application;

5 is a schematic diagram of a business process of an embodiment of a method for changing invoice header information according to the present application;

6 is a structural block diagram of an embodiment of an invoice header information changing apparatus of the present application;

7 is a structural block diagram of another embodiment of an invoice header information changing apparatus of the present application;

8 is an architectural diagram of an embodiment of an invoice management system of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application are within the scope of the present disclosure.

The above described objects, features and advantages of the present application will become more apparent and understood.

The embodiment of the present application can be applied to an invoice management system, and the user can manage the invoice header information online through the invoice management system. Among them, the management of the invoice management system for the invoice header information can be divided into two parts: a new invoice header information management unit and a change invoice header information management unit.

Specifically, after the new invoice header information management unit receives the request for the user to add the invoice header information, the background server performs corresponding processing according to the type of the invoice, and saves it to the database of the invoice management system.

Generally speaking, the types of invoices can be divided into three types: personal VAT ordinary invoice, enterprise VAT ordinary invoice, and corporate VAT special invoice. For invoice header information that has been saved in the database of the invoice management system, the user may need to change the invoice header information for various reasons.

For example, if you fill in the error, you need to change the old header that was filled with the error to a new one. In general, the header items that need to be changed at this time include: personal name or company name.

For example, if an enterprise changes from a small-scale taxpayer to a general taxpayer, the invoice needs to be changed from the enterprise VAT ordinary invoice to the corporate value-added tax special invoice. In general, the heading items that need to be changed at this time include: tax registration certificate number, registration place address, company registration phone number, bank account information, and the like.

For another example, after the name of the company changes, it needs to be updated.

However, because the rigor of the financial review requirements for different invoice types is different, the items that are allowed to change in the process of changing the invoice header information are also different, and the situation in which the header information of the change requires financial review is different.

In practical applications, certain business scenarios do not require financial review in the change process, for example, individuals Or the company's VAT ordinary invoices are filled in with the wrong changes.

Some business scenarios require financial review in the change process. For example, the enterprise VAT ordinary invoice is changed to the enterprise VAT special invoice, the corporate VAT special invoice is changed in the name of the head, and the personal VAT ordinary invoice is changed to the enterprise value added. Tax special invoices, etc.

Through the embodiment of the present application, the change of the invoice header information can be performed more accurately and efficiently, and the maintenance and update of the invoice management system is more convenient, and the development difficulty and the maintenance cost are also reduced.

In the embodiment of the present invention, the process of changing the invoice header information may involve the following states:

A, new heading pending review status

For example, if the user wants to change the personal VAT ordinary invoice that has been saved in the system to the enterprise VAT special invoice, the system needs to perform a corresponding financial review on the change request submitted by the user, so that the new header is in the pending review state;

B, new header revocation status

For example, in the pending review state, if the user wants to terminate the change process, the operation of canceling the change may be performed, that is, entering the new header revocation state.

In the case that the new header is in the revocation state, the old header is set to the valid state by the invoice management system, that is, the invoice header information is restored to the old header information that the invoice has been valid before the user submits the change.

C, new header rejection status

For example, a change request submitted by a user fails the financial review, that is, the new header is in a rejected state.

At this point, the user can modify and submit again according to the prompt of the system, and re-enter the new header to be reviewed; or directly cancel the operation of canceling the change, that is, enter the new header revocation state.

D, the new head is valid

For example, a change request submitted by a user passes a financial review, that is, the new header is in a valid state.

In the case that the new header is in the active state, the old header will be set to the invalid state by the invoice management system, that is, the invoice header information is changed to the new header information.

E, new heading failure status

For example, in the new header valid state or the new header revocation state, if the system directly rejects, it enters the new header failure state, that is, the unavailable state.

F, old head lock status

For example, the old header is neither a valid state nor a failed state, and may be converted to an active state or an intermediate state of the failed state, that is, the old header is in a locked state in the new header pending review state or the new header rejection state.

G, old header failure status

For example, when the new header information is approved, when the new header is in the active state, the status of the old header is set to the invalid state by the invoice management system from the locked state, that is, the unavailable state, that is, the invoice header information is changed to the new header information.

H, the old header is valid

For example, when the new header information fails the audit, the status of the old header is set to the active state by the invoice management system when the new header is in the rejected state, and the invoice header information is restored to the old header information.

Therefore, there are a variety of situations in which the invoice header information is in the process of change, and these states are not fixed, but are transformed as the modifications and financial review progress. Therefore, if the user wants to change the type of invoice header information that has already taken effect, then after the user makes several changes to the invoice header information, if the operation needs to be performed to cancel the change due to some circumstances, The invoice management system provided by the embodiment of the present application can restore the invoice new header information to the old header information that has been in effect before the change by using the current change record information in the shadow header data table; and can also use the current change record in the shadow header data table. The tag information of the information, effectively find the current state information of the new header and the old header and the state transition relationship, so that the invoice header can be restored to an intermediate state or the original state before the change, and real-time data rollback is provided, thereby further Effectively implement error troubleshooting throughout the change process.

Embodiment 1

Referring to FIG. 1 , a flow chart of steps of an embodiment of a method for changing invoice header information of the present application is shown, which may specifically include the following steps:

Step 110: Receive an invoice header information change request submitted by a user;

Step 120: Determine, according to a preset rule, whether the change request needs to be audited;

It can be understood that the audit described in the embodiment of the present application refers to a financial audit. In practical applications, certain business scenarios do not require financial review in the change process. For example, the personal or corporate VAT ordinary invoices are filled in with incorrect changes. Some business scenarios require financial review in the change process. For example, the enterprise VAT ordinary invoice is changed to the enterprise VAT special invoice, and the corporate VAT special invoice is changed. The personal VAT ordinary invoice is changed to the enterprise VAT special invoice. Therefore, the preset rule described in the embodiment of the present application is preset in the system according to a specific financial auditing standard, and when determining whether the change request needs to be subjected to the financial review, the judgment may be performed according to the preset rule.

Step 130, if a financial review is required, generating a corresponding shadow header data table based on the change request, where the shadow header data table includes original header information, new header information, and current change record information;

It should be noted that the current change record information in the shadow header data table includes information related to the change, for example, old header information that has been in effect before the change, current status information of the new header and the old header, and the like.

Preferably, in the embodiment of the present application, as shown in FIG. 2, a corresponding shadow header data table 1 is generated according to the change request 1, and the shadow header data table 1 includes at least: original header information, new header information, and current change record. information. If there is a change request 2 next, a corresponding shadow header data table 2 is generated according to the change request 2, and the shadow header data table 2 includes at least: original header information, new header information, and current change record information. It can be understood that, if there is a change request n, the corresponding shadow header data table n is generated according to the change request n.

Step 140: If the new header information passes the financial review, the old header information of the invoice is changed to the new header information;

Step 150: Update the new header state of the current change record information in the shadow header data table to be valid, and the old header state to be invalid.

It can be understood that, in the embodiment of the present application, as shown in FIG. 2, after the invoice header information change process ends, the new header information and the shadow header data table generated during the change process are saved in the database.

In the process of changing the invoice header information, the embodiment may generate a corresponding shadow header data table based on the change request, and may search for the original header information, the new header information, and the current change record information included in the shadow header data table. Improve the user experience by accurately and efficiently changing the invoice header information. In addition, with the embodiment of the present application, the change of the invoice header information can be performed more accurately and efficiently, and the maintenance and update of the invoice management system is more convenient, and the development difficulty and the maintenance cost are also reduced.

Embodiment 2

Referring to FIG. 3, a flow chart of the steps of the method for changing the invoice header information of the present application is shown. Specifically, the method may include the following steps:

Step 310: Receive an invoice header information change request submitted by a user;

It should be noted that the original invoice of the invoice needs to be in a valid state in order to carry out the subsequent change process, so it is necessary to determine that the original header of the invoice in the database is in a valid state before entering the change process. As for what to use The manner of determining the original header of the invoice is not limited in the embodiment of the present invention.

Step 320: Determine, according to a preset rule, whether the change request needs to perform a financial review;

Understandably, in practical applications, certain business scenarios do not require financial review in the change process, for example, the personal or corporate VAT ordinary invoices are filled in with incorrect changes. Some business scenarios require financial review in the change process. For example, the enterprise VAT ordinary invoice is changed to the enterprise VAT special invoice, the corporate VAT special invoice is changed in the name of the head, and the personal VAT ordinary invoice is changed to the enterprise value added. Tax special invoices, etc. Therefore, the preset rule described in the embodiment of the present application is preset in the system according to a specific financial auditing standard, and when determining whether the change request needs to be subjected to the financial review, the judgment may be performed according to the preset rule.

Step 330, if a financial review is required, generating a corresponding shadow header data table based on the change request, where the shadow header data table includes original header information, new header information, and current change record information;

Preferably, in another preferred embodiment of the present application, the current change record information of the shadow header data table further includes tag information to indicate a state transition relationship between the new header and the old header. For example, in the shadow header data table, a flag of a state transition relationship between the new header and the old header is implemented by setting an identifier or a tag code or the like. It can be understood that the specific implementation manner of recording the current change record information in the shadow header data table is not limited to the implementation manner of the embodiment of the present application, and may be various, as long as it can be used to indicate the new header and the old header. The state transition relationship is sufficient. For this reason, the embodiment of the present application does not limit this.

Step 340, if the new header information passes the financial review, the old header information of the invoice is changed to the new header information;

Step 350: Update a new header state of the current change record information in the shadow header data table to be valid, and the old header state is invalid.

Step 360: If the preset condition is met, the new header information of the invoice is restored to the old header information that has been in effect before the change based on the revocation change request submitted by the user and the current change record information of the shadow header data table;

Preferably, in an embodiment of the present application, the preset condition is: the new header information fails the review; and the method further includes: updating the shadow when the new header information fails the review The new header status of the current change record information in the header data table is rejected, and the old header status is locked.

In another embodiment of the present application, the preset condition is: the new header information is in a pending state; and the method further includes: updating the shadow when the new header information is in a pending state The new header status of the current change record information in the header data table is pending review, and the old header status is locked.

Step 370: Update a new header state of the current change record information in the shadow header data table to be revoked, and the old header state is valid.

Preferably, in the embodiment of the present application, the method may further include:

In step 380, if the financial review is not required, the invoice old header information is changed to the new header information.

Embodiment 3

Referring to Fig. 4, there is shown a schematic diagram of an embodiment of an invoice header information change flow state transition of the present application, which includes the entire change flow before the change, the change process, and the change end. As shown in Figure 4, the entire change process includes: original header is valid; new header is pending review, old header lock; new header rejection, old header lock; new header undo, old header is valid; new header is valid, old header is invalid; The new header fails, with a total of six transitions between states.

1) In the state that the original header of the invoice is valid, if the new header information needs to be financially audited in the change process, the state of the original header is transferred to the state of the new header to be audited and the old header is locked; at this time, the generated The shadow header data table includes original header information, new header information, and current change record information. The current change record information in the shadow header data table includes information related to the change, for example, old header information that has been in effect before the change, current status information of the new header and the old header, and is used to indicate the state transition of the new header and the old header. Tag information of the relationship, etc. In the embodiment of the present application, the current change record information includes indication information used to indicate the state of being transferred from the original header to the state of the new header to be reviewed, and the old header lock; if the new header information does not require financial review in the change process The state in which the original header is valid is directly updated to the state in which the new header is valid and the old header is invalid, and the generation of the shadow header data table is not accompanied.

2) In the state that the new header is pending review and the old header is locked, if the new header information fails the financial review, the status of the new header to be reviewed and the old header lock is transferred to the state of the new header rejection and the old header lock; The generated shadow header data table includes original header information, new header information, old header information that has been in effect before the change, current change record information, current header information, and current status information of the old header. The current change record information includes indication information used to indicate a status of a new header to be reviewed, an old header lock state transition to a new header rejection, and an old header lock;

If the financial review of the new header information is successful, the state of the new header to be reviewed and the old header lock is transferred to the state where the new header is valid and the old header is invalid; at this time, the generated shadow header data table includes the original header information, the new header information, Current change record information. The current change record information includes indication information indicating that the status of the new header to be reviewed, the old header lock is transferred to the new header, and the old header is invalid;

If the user wants to terminate the change process at this time, the operation of the change can be revoked, and the state of the new header to be reviewed and the old header lock is transferred to the state where the new header is revoked and the old header is valid; at this time, the generated The shadow header data table includes original header information, new header information, and current change record information. The current change record information includes indication information indicating that the state of the new header is pending review, the state of the old header lock is transferred to the new header undo, and the old header is valid.

3) In the state of new header rejection and old header lock, if the new header information is modified and then re-finished, the state of the new header rejection and the old header lock will be transferred back to the state of the new header for review and the old header lock. At this time, the generated shadow header data table includes original header information, new header information, and current change record information. The current change record information includes indication information for indicating a state of being rejected by the new head, the state of the old head lock is transferred back to the new head to be audited, and the old head lock is locked;

If the user wants to terminate the change process at this time, the operation of this change can be revoked, so the new lookup The state of rejection or old header lock is transferred to the state where the new header is revoked and the old header is valid; at this time, the generated shadow header data table includes original header information, new header information, and current change record information. The current change record information includes indication information for indicating a state of being rejected by the new head, the state of the old head lock is transferred to the new head undo, and the old head is valid.

4) In the state where the new header is revoked and the old header is valid, if it is directly rejected, the state of the new header is revoked and the old header is valid to the state where the new header is invalid.

5) In the state where the new head is valid and the old head is invalid, if it is directly rejected, the state in which the new head is valid and the old head is invalid is transferred to the state in which the new head is invalid.

6) In the state where the new head is invalid, the system can select a head from the failed head to edit, and then enter the change process again after it takes effect.

It should be noted that if the scene of failure is automatically caused by the system, such as major changes in the system, it may cause the user's previous invoices of all invoices to be invalid. When the user enters the system again, it may need the previous header information. Therefore, in a preferred embodiment, the user may be provided with a way to select a failed head-up from the failed heads for continued operation. For specific applications, all of the user's failed headers can be listed, and then the user selects one for subsequent operations.

The embodiment of the present application has the following advantages:

Embodiment 4

A specific application of the embodiment of the present application is described below in conjunction with an actual service scenario.

For example, if a company changes from a small-scale taxpayer to a general taxpayer, the invoice needs to be changed from the enterprise VAT ordinary invoice to the corporate value-added tax special invoice. In general, the heads that need to be changed at this time include: tax registration number, Registered place address, company registration phone number, bank account information, etc.

The user enters the invoice management interface, and obtains the invoice header information list by calling the interface to retrieve the database information on the server. The user clicks on the invoice header information to be modified to enter the change process, as shown in FIG. 5, which is a schematic diagram of the business process of the embodiment of the invoice header change information method.

First, the user selects the type of change, that is, the enterprise VAT ordinary invoice is changed to the enterprise VAT special invoice; then, since it is changed from the enterprise VAT ordinary invoice to the enterprise VAT special invoice, it is judged that the type of the issuing does not need to be changed; After confirming that the name of the heading needs to be changed, if it is further judged that the name of the head is not filled incorrectly, the user submits the registration change information; if the system judges that it is a special invoice for the company's value-added tax, the user is required to submit the header and other information of the special invoice for the company's value-added tax, and submit the business change. Prove that the system conducts financial audits;

If the financial review fails, the system updates the current change record information in the generated shadow header data table to the new header rejection and the old header lock state. At this time, if the user wants to terminate the change process, the system can click the undo button. The change operation will be revoked. In this way, the system will update the status of the new header and the old header in the current change record information in the shadow header data table, and record the state of the new header rejection and the old header lock to the new header. The status change relationship of the revocation and the old header is valid; at the same time, the system restores the new header information of the invoice to the old header information that has been in effect before the change according to the current change record information in the shadow header data table. Of course, for the case that the financial review fails, the user can re-submit and re-submit the financial review according to the system prompts; if the financial review is passed, the new header submitted is valid; the change process is ended.

The embodiment of the present application has the following advantages:

It should be noted that, for the method embodiment, for the sake of simple description, it is expressed as a series of action groups. It should be understood by those skilled in the art that the embodiments of the present application are not limited by the described order of actions, as some steps may be performed in other sequences or concurrently in accordance with embodiments of the present application. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required in the embodiments of the present application.

Embodiment 5

Referring to FIG. 6, a structural block diagram of an embodiment of an invoice header information changing apparatus of the present application is shown, which may specifically include the following modules:

The receiving module 610 is configured to receive an invoice header information change request submitted by the user;

The determining module 620 is configured to determine, according to the preset rule, whether the change request received by the receiving module needs to perform a financial review; wherein, in another embodiment of the present application, the determining module 620 may further be configured to determine that the original header is in Valid state.

The generating module 630 is configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change record, if the determining module 620 determines that a financial review is required. information;

The change module 640 is configured to change the old header information of the invoice to the new header information if the new header information passes the financial review. Correspondingly, the generating module 630 is further configured to update a new header state of the current change record information in the shadow header data table to be valid, and the old header state to be invalid.

In the process of changing the invoice header information, the embodiment may generate a corresponding shadow header data table based on the change request, and may search for the original header information, the new header information, and the current change record information included in the shadow header data table. Improve the user experience by accurately and efficiently changing the invoice header information. In addition, through Through the embodiment of the present application, the change of the invoice header information can be performed more accurately and efficiently, and the maintenance and update of the invoice management system is more convenient, and the development difficulty and the maintenance cost are also reduced.

Embodiment 6

Referring to FIG. 7, a structural block diagram of another embodiment of an invoice header information changing apparatus of the present application is shown, which may specifically include the following modules:

The receiving module 710 is configured to receive an invoice header information change request submitted by the user;

The determining module 720 is configured to determine, according to the preset rule, whether the change request received by the receiving module needs to perform a financial review; wherein, in another embodiment of the present application, the determining module 720 is further configured to determine that the original header is in Valid state. It can be understood that the invoice original header needs to be in a valid state in order to carry out the subsequent change process, so it is necessary to determine that the original header state is valid before entering the change process. As for the specific manner of determining the original header state of the invoice, the embodiment of the present invention is not limited.

The generating module 730 is configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change record information, if the determining module 720 determines that the audit is required to be performed. ;

It should be noted that the current change record information in the shadow header data table includes information related to the change, for example, old header information that has been in effect before the change, current status information of the new header and the old header, to indicate the new header and Mark information of the old headed state transition relationship, etc.

Preferably, in the embodiment of the present application, as shown in FIG. 2, the generating module 730 may generate a corresponding shadow header data table 1 according to the change request 1, and the shadow header data table 1 includes at least: original header information and new header information. , current change record information. If there is a change request 2, the generating module 730 may further generate a corresponding shadow header data table 2 according to the change request 2, the shadow header data table 2 including at least: original header information, new header information, and current change record information. Understandably, and so on, if there are change requests next n, the generation module 730 can also generate a corresponding shadow header data table n according to the change request n.

The change module 740 is configured to: if the new header information passes the financial review, change the old header information of the invoice to the new header information; correspondingly, the generating module 730 is further configured to update the current change record information in the shadow header data table. The new header status is valid and the old header status is invalid.

It can be understood that the current change record information of the shadow header data table includes tag information to indicate a state transition relationship between the new header and the old header. For example, the generation module 730 implements a flag of a state transition relationship between the new header and the old header by setting an identifier or a tag code or the like in the shadow header data table. It can be understood that the specific implementation manner in which the generating module 730 records the current change record information in the shadow header data table is not limited to the implementation manner of the embodiment of the present application, and may be various, as long as it can be used to indicate a new head. The state transition relationship with the old head is sufficient. For this reason, the embodiment of the present application does not limit this.

The searching module 750 is configured to search for the current change record information of the shadow header data table based on the undo change request submitted by the user received by the receiving module 710, if the preset condition is met;

The change module 740 is further configured to restore, according to the current change record information found by the lookup module 740, the invoice new header information to the old header information that has been in effect before the change; correspondingly,

The generating module 730 is further configured to update a new header state of the current change record information in the shadow header data table to be undoed, and the old header state is valid.

In a preferred embodiment, the preset condition is: the new header information is in a pending state;

The generating module 730 is further configured to: when the new header information is in a state to be audited, update a new header state of the shadow header data table to be audited, and the old header state is locked;

In another preferred embodiment, the preset condition is that the new header information fails the financial review;

The generating module 730 is further configured to: when the new header information fails to pass the review, update the new header state of the shadow header data table to be rejected, and the old header state to be locked.

In addition, the change module 740 is further configured to: if the determining module 720 determines that the financial review is not required, change the invoice old header information to the new header information.

Preferably, the embodiment of the present application may further include a saving module 760, configured to save the new header information and the shadow header data table generated during the change process in the database after the invoice header information change process ends.

Further, when the user makes several changes to the invoice header information, if needed due to certain circumstances When the undo operation is performed, the new header information of the invoice is restored to the old header information that has been in effect before the change by using the current change record information in the shadow header data table; and the mark information of the record information currently changed in the shadow header data table may also be Effectively find the current status information of the new header and the old header and the state transition relationship, so that the invoice header can be restored to an intermediate state or the original state before the change, and real-time data rollback can be provided, thereby implementing the entire change more effectively. Troubleshooting during the process.

Example 7

Referring to Figure 8, there is shown an architectural diagram of an embodiment of an invoice management system of the present application. The invoice management system 800 includes an invoice header information changing device 810 and a database 820. The specific structure of the invoice header information changing device 810 is described. See the above embodiment, and details are not described herein again.

The invoice management information can be managed by the user through the client accessing the invoice management system 800 on the Invoice Management Center server. Specifically, after receiving the change request of the user invoice header information, the invoice header information changing means 810 of the invoice management system 800 gives corresponding processing based on the type of the invoice based on the background server, and saves the related data information to the invoice management system 800. In the database 820.

It should be noted that the invoice management system of the embodiment of the present application can be applied to the invoice management center server or the invoice management platform, which is not limited in this embodiment of the present application.

The embodiments of the present application have the following advantages:

In addition, with the embodiment of the present application, the change of the invoice header information can be performed more accurately and efficiently, and Easy maintenance and update of the invoice management system also reduces development difficulty and maintenance costs.

For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments can be referred to each other.

Those skilled in the art will appreciate that embodiments of the embodiments of the present application can be provided as a method, apparatus, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application 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, etc.) including computer usable program code.

In a typical configuration, the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium. Computer readable media includes both permanent and non-persistent, removable and non-removable media. Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, read-only optical read-only memory (CD@ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-persistent computer readable media, such as modulated data signals and carrier waves.

Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The instruction device implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device such that a series of operational steps are performed on the computer or other programmable terminal device to produce computer-implemented processing, such that the computer or other programmable terminal device The instructions executed above provide steps for implementing the functions specified in one or more blocks of the flowchart or in a block or blocks of the flowchart.

While a preferred embodiment of the embodiments of the present application has been described, those skilled in the art can make further changes and modifications to the embodiments once they are aware of the basic inventive concept. Therefore, the appended claims are intended to be interpreted as including all the modifications and the modifications

Finally, it should also be noted that in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. There is any such actual relationship or order between operations. Furthermore, the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Other elements that are included, or include elements inherent to such a process, method, article, or terminal device. An element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that comprises the element, without further limitation.

The method and device for changing the invoice header information provided by the present application and an invoice management system are described in detail above. The principles and implementation manners of the present application are described in the specific examples, and the description of the above embodiments is described. It is only used to help understand the method of the present application and its core ideas; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there may be changes in specific implementation manners and application scopes. The contents of this specification are not to be construed as limiting the application.

Claims

A method for changing invoice header information, characterized in that it comprises:

Receiving an invoice header change request submitted by the user;

Determining whether the change request needs to be audited based on a preset rule;

If the auditing is required, generating a corresponding shadow header data table based on the change request, where the shadow header data table includes original header information, new header information, and current change record information;

If the new header information is approved, the old header information of the invoice is changed to the new header information; and the new header status of the current change record information in the shadow header data table is updated to be valid, and the old header status is invalid.
The method of claim 1 further comprising:

If the preset condition is met, the invoice new header information is restored to the old header information that has been in effect before the change based on the user-submitted revocation change request and the current change record information of the shadow header data table; and The new header state of the current change record information in the shadow header data table is undo, and the old header state is valid.
The method of claim 2 wherein:

The preset condition is: the new header information has not passed the audit;

The method further includes: when the new header information fails to pass the review, updating a new header status of the current change record information in the shadow header data table to be rejected, and the old header status is locked;

or

The preset condition is: the new header information is in a pending state;

The method further includes: when the new header information is in an auditing state, updating a new header state of the current change record information in the shadow header data table to be audited, and the old header state is locked.
The method according to any one of claims 1-3, wherein the current change record information in the shadow header data table further comprises: tag information indicating a state transition relationship between the new header and the old header.
The method of claim 1 further comprising:

If the review is not required, the invoice old header information is changed to the new header information.
A method for changing invoice header information, characterized in that it comprises:

Receiving an invoice header change request submitted by the user;

Determining whether the change request needs to be audited based on a preset rule;

If the auditing is required, generating a corresponding shadow header data table based on the change request, where the shadow header data table includes original header information, new header information, and current change record information;

Based on the pre-conditions, based on the user-submitted revocation change request and the shadow header data table The current change record information is restored to the old header information that has been in effect before the change; and the new header status of the current change record information in the shadow header data table is updated to be revoked, and the old header status is valid.
The method of claim 6 wherein:

The preset condition is: the new header information has not passed the audit;

The method further includes: when the new header information fails to pass the review, updating a new header status of the current change record information in the shadow header data table to be rejected, and the old header status is locked;

or

The preset condition is: the new header information is in a pending state;

The method further includes: when the new header information is in an auditing state, updating a new header state of the current change record information in the shadow header data table to be audited, and the old header state is locked.
The method according to claim 6 or 7, wherein the current change record information in the shadow header data table further comprises: tag information indicating a state transition relationship between the new header and the old header.
The method of claim 6 wherein the method further comprises:

If the review is not required, the invoice old header information is changed to the new header information.
An invoice header information changing device, comprising:

a receiving module, configured to receive an invoice header information change request submitted by a user;

a determining module, configured to determine, according to a preset rule, whether the change request received by the receiving module needs to be audited;

a generating module, configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change record information, if the determining module determines that the audit is required to be performed;

a change module, configured to: if the new header information is approved, change the old header information of the invoice to the new header information; correspondingly, the generating module is further configured to update a new header of the current change record information in the shadow header data table. The status is valid and the old header status is invalid.
The device according to claim 10, wherein the device further comprises:

a searching module, configured to search for current change record information of the shadow header data table based on a revocation change request submitted by the user received by the receiving module, if the preset condition is met;

The change module is further configured to restore, according to the current change record information found by the lookup module, the new header information of the invoice to the old header information that has been in effect before the change; correspondingly,

The generating module is further configured to update a new heading status of the current change record information in the shadow header data table. For undo, the old header status is valid.
The device of claim 11 wherein:

The preset condition is: the new header information has not passed the audit;

The generating module is further configured to: when the new header information fails to pass the review, update a new header state of the current change record information in the shadow header data table to be rejected, and the old header state is locked;

or

The preset condition is: the new header information is in a pending state;

And the generating module is further configured to: when the new header information is in a state to be audited, update a new header state of the current change record information in the shadow header data table to be audited, and the old header state is locked.
The device according to any one of claims 10 to 12, wherein the current change record information in the shadow header data table further comprises: tag information indicating a state transition relationship between the new header and the old header.
The device according to claim 10, wherein the change module is further configured to: if the determining module determines that the review is not required, change the invoice old header information to the new header information.
An invoice header information changing device, comprising:

a receiving module, configured to receive an invoice header information change request submitted by a user;

a determining module, configured to determine, according to a preset rule, whether the change request received by the receiving module needs to be audited;

a generating module, configured to generate, according to the change request, a corresponding shadow header data table, where the shadow header data table includes original header information, new header information, and current change record information, if the determining module determines that the audit is required to be performed;

a searching module, configured to search for current change record information of the shadow header data table based on a revocation change request submitted by the user received by the receiving module, if the preset condition is met;

a change module, configured to restore, according to the current change record information found by the lookup module, the invoice new header information to the old header information that has been in effect before the change; correspondingly, the generating module is further configured to update the The new header state of the current change record information in the shadow header data table is undo, and the old header state is valid.
The device of claim 15 wherein:

The preset condition is: the new header information has not passed the audit;

The generating module is further configured to: when the new header information fails to pass the review, update a new header state of the current change record information in the shadow header data table to be rejected, and the old header state is locked; or

The preset condition is: the new header information is in a pending state;

And the generating module is further configured to: when the new header information is in a state to be audited, update a new header state of the current change record information in the shadow header data table to be audited, and the old header state is locked.
The device according to claim 15 or 16, wherein the current change record information in the shadow header data table further comprises: tag information indicating a state transition relationship between the new header and the old header.
The apparatus according to claim 15, wherein the change module is further configured to: if the determining module determines that the audit is not required, change the invoice old header information to the new header information.
An invoice management system comprising the invoice header information changing device according to claim 10 or 15.