Invoice issuing method and system

Abstract

The invention discloses an invoice issuing method. The method comprises the steps: an order subsystem synchronizes order information to an invoice subsystem through a message queue (MQ); the invoice subsystem determines the number of invoices corresponding to an order and the content of each invoice according to the order information and the invoice information corresponding to a pre-input warehouse name and transmits the content of each invoice to a warehouse subsystem through the MQ; and the warehouse subsystem sequentially prints each invoice corresponding to the order according to the transmitted content of each invoice and warehouse drawer corresponding to a minimum invoice number of the own subsystem to complete issuing of the invoice. The invention also discloses an invoice issuingsystem. By use of the invoice issuing method and the invoice issuing system, the influence of system abnormality on issuing of the invoice can be reduced.

Description

technical field [0001] The invention relates to the technical field of taxation services, in particular to a method and system for issuing invoices. Background technique [0002] VAT general invoices play a very important role in e-commerce: [0003] 1. The invoice is the receipt certificate issued to the payer by the enterprises, institutions and individuals engaged in production and operation, with regard to the taxable income obtained when they sell goods or provide taxable labor services and engage in other business activities. A shopping voucher that users can use for after-sales and refunds. [0004] 2. The invoice is the carrier for recording the content of economic activities and an important tool for financial management; [0005] 3. Invoices are an important basis for tax authorities to control tax sources and collect taxes; invoices are an important means for the state to supervise economic activities, maintain economic order, and protect national property secur...

AI Technical Summary

Problems solved by technology

[0017] 1. There are too many interactions between subsystems, and they rely heavily on WS interface calls. After the invoice subsystem is entered and assigned successfully, the warehouse subsystem can perform the invoice initialization operation. If the initialization fails, the invoice cannot be issued; the order subsystem will store the order information After the invoice subsystem is synchronized, the invoice subsystem can download the invoice content to the warehouse subsystem. If the synchronization fails, the invoice cannot be downloaded; the invoice can only be issued after the warehouse subsystem initialization operation and the invoice subsystem download the invoice content successfully. After the warehouse subsystem sends back to the invoice subsystem successfully, the invoice subsystem can update the latest invoice status of its own subsystem, and the initialization of the next volume of invoices can be successful. If the invoice fails to be sent back, the next volume cannot be processed. initialization operations, etc.

[0018] 2. The amount of information sent each time the WS interface call is small

In order to prevent the processing timeout due to the large amount of data, it is necessary to artificially split and transmit data multiple times, which seriously affects work efficiency

[0019] 3. Once the WS interface call fails, you must wait until the invoice information is processed manually before you can continue to issue invoices, which greatly affects the efficiency of invoicing and order production

The WS interface call is a single call. Once it fails, manual intervention is required, which is time-consuming and laborious

Images