WO2020000632A1 - 发票开具方法、装置、设备及计算机可读存储介质 - Google Patents

发票开具方法、装置、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2020000632A1
WO2020000632A1 PCT/CN2018/103331 CN2018103331W WO2020000632A1 WO 2020000632 A1 WO2020000632 A1 WO 2020000632A1 CN 2018103331 W CN2018103331 W CN 2018103331W WO 2020000632 A1 WO2020000632 A1 WO 2020000632A1
Authority
WO
WIPO (PCT)
Prior art keywords
invoice
invoicing
contract
information
characteristic information
Prior art date
Application number
PCT/CN2018/103331
Other languages
English (en)
French (fr)
Inventor
吴昊
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020000632A1 publication Critical patent/WO2020000632A1/zh

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
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07G—REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G5/00—Receipt-giving machines

Definitions

  • the present application relates to the field of computer technology, and in particular, to an invoice issuing method, device, device, and computer-readable storage medium.
  • Invoices are business documents issued or received by enterprises and individuals when they purchase and sell goods, provide or receive services, and engage in other business activities.
  • the traditional method of invoicing is to manually enter the invoice content for invoicing according to the contract content by a special accountant.
  • This manual method of invoicing when the number of contracts is large, takes a lot of time, takes time and effort, and is inefficient.
  • the main purpose of this application is to provide an invoice issuing method, device, device, and computer-readable storage medium, which aims to improve the efficiency of invoice issuing.
  • this application provides an invoice issuing method, which includes the following steps:
  • the step of obtaining contract information corresponding to the billing request includes:
  • a corresponding contract management system is connected according to the billing request, and a management page of the contract management system is displayed;
  • the step of inputting corresponding invoice characteristic information in the invoicing page according to the contract information to send the invoice characteristic information to the invoicing system includes:
  • the invoice characteristic information is input to the characteristic information input area to send the invoice characteristic information to the invoicing system.
  • the invoice characteristic information includes a total invoice denomination
  • the feature information of the invoice is input to the feature information input area according to the number of invoices and the denomination of each invoice to send the feature information of the invoice to the invoicing system.
  • the method further includes:
  • the method further includes:
  • the corresponding failure type is determined according to the invoicing failure prompt, and corresponding alarm processing is performed according to the failure type.
  • the invoice issuing method further includes:
  • a second configuration modification instruction is sent to the billing sub-machine, so that the billing sub-machine performs a billing configuration modification according to the second configuration modification instruction.
  • this application also provides an invoice issuing device, where the invoice issuing device includes:
  • An information acquisition module configured to acquire contract information corresponding to the billing request when the billing request is received
  • a page display module for connecting to the invoicing system and displaying the invoicing page of the invoicing system
  • An information sending module configured to input corresponding invoice characteristic information in the invoicing page according to the contract information, so as to send the invoice characteristic information to the invoicing system;
  • the invoice acquisition module is configured to obtain a corresponding invoice according to the successful billing prompt and save it when receiving a successful billing prompt returned by the billing system.
  • the present application further provides an invoice issuing device, which includes a processor, a memory, and computer-readable instructions stored on the memory and executable by the processor, wherein When the computer-readable instructions are executed by the processor, the steps of the invoice issuing method described above are implemented.
  • the present application further provides a computer-readable storage medium, where the computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the implementation is as described above. Steps of your invoice method.
  • This application uses a robotic process automation method to simulate the behavior of the billing staff by clicking, entering, etc. on the display page of the terminal.
  • the process is independently completed by the computer (robot), which reduces the labor cost, improves the operating efficiency, and reduces the error rate.
  • this embodiment can achieve 24 hours of uninterrupted work, unlimited working hours, and ensure the timely invoicing;
  • invoicing in this application the data is processed and transmitted through the operation in the user interface. There is no need to set up interfaces between different systems for data import and export, etc., to achieve seamless connection across systems and reduce Billing costs.
  • FIG. 1 is a schematic diagram of a hardware structure of an invoice issuing device involved in a solution according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a first embodiment of an invoice issuing method of the present application
  • FIG. 3 is a schematic flowchart of a second embodiment of an invoice issuing method of the present application.
  • FIG. 4 is a functional module diagram of the first embodiment of the invoice issuing device of the present application.
  • the method for issuing an invoice is mainly applied to an invoice issuing device, and the invoice issuing device may be a personal computer. computer (PC), portable computer, mobile terminal and other devices with data processing functions.
  • FIG. 1 is a schematic diagram of a hardware structure of an invoice issuing device involved in a solution according to an embodiment of the present application.
  • the invoice issuing device may include a processor 1001 (for example, a central processor Central Processing Unit (CPU), communication bus 1002, user interface 1003, network interface 1004, and memory 1005.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display and an input unit such as a keyboard.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface.
  • the memory 1005 may be a high-speed random access memory (random access memory (RAM) or non-volatile memory memory), such as a disk memory, the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • RAM random access memory
  • non-volatile memory memory such as a disk memory
  • the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions.
  • the network communication module may be used to connect the invoicing system and perform data communication with the invoicing system; and the processor 1001 may call the computer-readable instructions stored in the memory 1005 and execute the invoice issuing method provided in the embodiment of the present application.
  • the embodiment of the present application provides a method for issuing an invoice.
  • FIG. 2 is a schematic flowchart of a first embodiment of an invoice issuing method of the present application.
  • the invoice issuing method includes the following steps:
  • Step S10 When a billing request is received, obtain contract information corresponding to the billing request.
  • Invoices are business documents issued or received by enterprises and individuals when they purchase and sell goods, provide or receive services, and engage in other business activities.
  • For enterprises after signing a contract to conduct a transaction, they need to issue a corresponding invoice for Follow-up is used for accounting.
  • the traditional method of invoicing is to manually enter the invoice content for invoicing according to the contract content by a special accountant.
  • This manual method of invoicing when the number of contracts is large, takes a lot of time, takes time and effort, and is inefficient.
  • an invoice issuing method is proposed in this embodiment.
  • Process Automation, RPA Process Automation, RPA) method, simulate the behavior of the billing staff, click, enter, etc. on the display page of the computer terminal, complete the entire process of invoice issuance, and automatically store the invoice when the billing is successful.
  • the invoice issuing method in this embodiment may be implemented by an invoice issuing device, which may be a personal computer (personal computer). (computer, PC), portable computer, mobile terminal and other devices with data processing functions.
  • a PC is used as an example for description.
  • the PC can be a PC in the financial system.
  • the PC can be connected to the invoicing system of the billing agency (such as the Inland Revenue Department Baiwang, Airline, etc.) to realize data interaction.
  • the PC also has process automation ( Robotic Process Automation (RPA) robot to perform billing operations to simulate the actions of natural persons.
  • the RPA robot can also be understood as software implemented in a software programming language that simulates user operations in a visual user interface based on certain rules, thereby automating manual activities.
  • RPA Robotic Process Automation
  • the PC when receiving a billing request, the PC first obtains contract information corresponding to the billing request.
  • the invoicing request can be sent by other management devices; of course, the invoicing request can also be triggered manually by the user on the PC; in addition, it can also set the corresponding invoicing conditions, and automatically trigger the corresponding when the invoicing conditions are met. Invoicing request (such as when it is started regularly, when a certain number of new contracts are signed, and the amount of newly signed contracts reaches a certain value, etc.).
  • the invoicing request may include contract characteristics such as contract number, contract time, contract object, and contract type, and the PC may obtain corresponding contract information according to these contract characteristics.
  • the contract information may be stored locally on the PC. Of course, it can also be stored and managed by a special contract management system.
  • the PC when the contract information is stored and managed by a special contract management system, the PC will obtain related contract information from the contract management system. Specifically, when the PC receives the invoicing request, it will connect to the contract management system; in this process, if the contract management system is in the form of a Browser / Server (B / S) architecture, the PC will start up in advance The installed browser is connected to the contract management system; if the contract management system is in the form of a client / server (C / S) architecture, the PC will find the pre-installed contract management client ( Software), and connect to the contract management system through this client. When the connection with the contract management system is successful, the related management page will be displayed on the PC display.
  • B / S Browser / Server
  • the PC will start up in advance
  • the installed browser is connected to the contract management system; if the contract management system is in the form of a client / server (C / S) architecture, the PC will find the pre-installed contract management client ( Software), and connect to the contract management
  • the PC will identify the management page, and determine the contract query area in the management page, and then enter the query characteristics of the target contract in the contract query area to query the target contract that meets the requirements.
  • the recognition script of the RPA robot can be set in advance according to the layout mode of the management page (that is, the identification specification of the RPA robot in the management system is customized according to the contract management system); for example, the management page's It is divided into two areas, the upper area is the contract inquiry area, the input area is included in the contract inquiry area, and the lower area is the system text introduction.
  • this typesetting method you can set the RPA management page element recognition script to identify the input Box to determine the contract query area; you can then enter the contract characteristics of the target contract in this area.
  • OCR Optical Character Recognition
  • the recognition process it can be combined with optical character recognition (Optical Character Recognition (OCR) technology, that is, taking a screenshot when the management page is displayed, and identifying related keywords through OCR technology, so as to determine the corresponding contract query area based on the keywords.
  • OCR Optical Character Recognition
  • the PC can obtain the corresponding contract information; of course, the PC can also download the contract information to the local for storage in the form of a document (can be in excel, word, xml , Json, etc.).
  • this embodiment can obtain related contract information by operating in a user interface, and does not need to set up interfaces between different systems for data export and other tasks, thereby achieving seamless connection across systems.
  • Step S20 Connect the billing system and display the billing page of the billing system
  • the PC when contract information is obtained, the PC will connect to the billing system to perform related billing operations.
  • the process of invoicing is similar to the process of obtaining contract information by the above-mentioned connection contract management system, and information can be transmitted by operating in a user interface.
  • the PC will select an appropriate connection method to connect to the invoicing system according to the architectural form of the invoicing system, and display the invoicing page of the invoicing system.
  • the PC will launch a pre-installed browser to connect to the invoicing system and display the invoicing page; if the invoicing system is in the form of C / S architecture, the PC will The software name finds the pre-installed billing client (software), connects to the billing system through this client, and displays the billing page.
  • Step S30 Enter corresponding invoice characteristic information in the invoicing page according to the contract information to send the invoice characteristic information to the invoicing system;
  • the PC can enter the billing page according to the contract information to send the invoice characteristic information (or billing entry parameter) required for billing to the billing system.
  • the PC will identify the invoicing page, determine the feature input area on the invoicing page, and then enter the invoice feature information in the feature input area.
  • the invoice characteristic information can be obtained according to the contract information.
  • the invoice amount in the invoice characteristic information can be obtained according to the contract amount in the contract information.
  • the bank account number and tax registration number in the invoice characteristic information can be based on the contract object in the contract information. Get the account.
  • the recognition script of the RPA robot can be set in advance according to the layout mode of the invoicing page (that is, the identification specification of the RPA robot in the invoicing system is customized according to the invoicing system). The recognition script identifies relevant page elements, thereby determining a feature input area.
  • OCR Optical Character Recognition
  • the contract information obtained in step S10 is not necessarily all the invoice characteristic information; for this, the PC can filter the contract information according to the characteristic type of the characteristic information input area to obtain the corresponding invoice characteristic information, and then The invoice characteristic information is then input to an input area of the characteristic information to send the invoice characteristic information to an invoicing system.
  • the PC can also identify and determine the corresponding document upload button on the invoicing page, and upload the locally stored invoice characteristic information file through this button.
  • the invoice characteristic information file it can be generated from the contract information file obtained in step S10; that is, the PC will adjust the contract information file according to the invoicing characteristic rules (entry rules) of the invoicing system to obtain the invoice characteristic information file.
  • the adjustment content can include deletion of invalid information, format conversion (such as case conversion, digit adjustment of data values, etc.), ordering of field columns, and so on.
  • the PC can also perform corresponding billing processing according to the requirements of invoicing when entering the invoice characteristic information. Specifically, the PC will first determine the number of invoices and each invoice denomination according to the total denomination of the invoice in the invoice characteristic information and the single denomination limit preset by the billing system; then, enter the invoice characteristic information into the invoice according to the invoice number and each denomination.
  • the feature information input area is used to send the invoice feature information to the invoicing system; in the input process, there may be multiple entries. For example, in the invoicing system, the single denomination limit for each invoice is 1 million yuan, and the total denomination of contract A is 5 million yuan.
  • the PC will determine the number of invoices to be 5 based on the total denomination of the invoice and the single denomination limit. Each invoice has a denomination of 1 million yuan; then the invoice characteristic information is entered according to the invoice quantity and invoice denomination, so that the invoice characteristic information is sent to the invoicing system if the invoicing conditions are met, thereby invoicing contract A Demands are fulfilled in the form of multiple invoices.
  • step S40 upon receiving the prompt of successful invoicing returned by the invoicing system, obtain a corresponding invoice according to the prompt of successful invoicing and save it.
  • the invoicing system when the invoicing system succeeds in invoicing according to the characteristic information of the invoice, the corresponding invoicing success prompt will be returned to the PC.
  • the PC receives the prompt for successful invoicing, it can obtain the corresponding invoice according to the prompt for successful invoicing and store it.
  • the invoice can be included in the billing success prompt, that is, the billing system returns the invoice to the PC; or a download link for the invoice can be added to the billing success prompt, and the PC downloads the invoice to the local for saving according to the download link.
  • the RPA robot of the PC in this embodiment may be in a stand-alone non-interaction form or a network interaction form; when the RPA robot is in a stand-alone non-interaction form, its invoicing configuration (including page identification configuration, input configuration) Etc.) need to be set on the PC body; when the RPA robot is in the form of network interaction, its invoicing configuration can be set in a synchronous manner, thereby facilitating the use of the clustered system of corporate finance and reducing the configuration workload To improve configuration efficiency.
  • its invoicing configuration including page identification configuration, input configuration
  • the RPA robot when it adopts the form of network interaction, it consists of multiple PCs (invoicing devices) provided with the same version of PRA, and each PC can independently complete the above-mentioned invoicing process; the The cluster has at least one invoicing parent machine and at least one invoicing child machine, where the invoicing mother machine can be designated when the cluster is established; when the cluster configuration modification is required, the configuration modification can be performed on the invoicing master machine.
  • the invoicing parent machine will send configuration modification instructions to other invoicing slave machines, so that the invoicing slave machine can perform corresponding configuration modification according to the configuration modification instruction to achieve configuration synchronization.
  • the second configuration modification instruction may be sent to the invoicing slave according to the RPA configuration modification of the local machine, so that the invoicing slave performs the invoicing configuration modification according to the second configuration modification instruction.
  • contract information corresponding to the billing request is obtained; the billing system is connected and the billing page of the billing system is displayed; and the corresponding is entered in the billing page according to the contract information
  • the invoice characteristic information is sent to the invoicing system; when a prompt for successful invoicing returned by the invoicing system is received, a corresponding invoice is obtained and saved according to the prompt for successful invoicing.
  • this embodiment uses a robotic process automation method to simulate the behavior of the invoicing staff to perform operations such as clicking and entering on the display page of the terminal to complete the entire process of invoicing, and automatically obtains and stores the invoice when the invoicing is completed, thereby
  • the entire process of invoicing is completed by a computer (robot) independently, which reduces labor costs, improves operating efficiency, and reduces error rates.
  • this embodiment can achieve 24 hours of uninterrupted work, unlimited working hours, and ensure invoicing
  • the data is processed and transmitted through the operation in the user interface. There is no need to set up interfaces between different systems for data import and export, and to achieve cross-system implementation.
  • the seamless connection reduces the cost of invoicing.
  • FIG. 3 is a schematic flowchart of a second embodiment of an invoice issuing method of the present application.
  • step S40 the method further includes:
  • step S50 the mailbox software is started, and a corresponding billing notification email is sent to a preset contact.
  • the PC when the PC receives the prompt of successful invoicing returned by the invoicing system and obtains the relevant invoice, it may also send a reminder by email to a preset contact. Specifically, the PC starts the pre-installed mailbox software, then clicks the notification template email, and fills in the email address information of the preset contact in the recipient field to obtain the billing notification email.
  • the email address information of the preset contact may be stored in the email account in advance.
  • the PC After the PC starts the email software, the PC will click to open the frequently used contact bar, identify the person name in it, and then click the corresponding preset Set a contact, so that the pre-stored preset contact's email address information is automatically filled in the recipient column of the write window; of course, the preset contact's email address information can also be saved in the contact excel (or other documents) in advance ), After the PC starts the mailbox software, it will open the contact's excel document and fill the recipient field according to the email address information in the document. After receiving the billing notification email, the PC can send the billing notification to the mailbox of the preset contact for notification. Of course, when email notification is performed, you can also log in to the web mailbox through a browser to set it. The specific process and type of notification through software are not described here. It is worth noting that in this embodiment, other notification methods can also be set for notification according to the actual situation, such as through social software, telephone, and the like.
  • a corresponding invoicing failure prompt when the invoicing system fails to invoice, a corresponding invoicing failure prompt will be returned to the PC. And when the PC receives the prompt of the invoicing failure, it can also perform corresponding alarm processing. For example, as described above, an alarm email is sent to a preset contact, or an alarm message is sent to a related contract system.
  • the invoicing failure may be caused by different reasons.
  • the PC can also adopt different alarm processing methods. Specifically, when the invoicing system returns the invoicing failure prompt, it can also add the corresponding failure type identifier; when the PC receives the invoicing failure prompt, it can also determine the corresponding failure type (cause) according to the failure type identification, and then according to the failure The corresponding alarm is handled.
  • the embodiment of the present application also provides an invoice issuing device.
  • FIG. 4 is a schematic diagram of function modules of the first embodiment of the invoice issuing device of the present application.
  • the invoice issuing device includes:
  • An information acquisition module 10 is configured to acquire contract information corresponding to the billing request when the billing request is received;
  • a page display module 20 configured to connect to a billing system and display a billing page of the billing system
  • An information sending module 30, configured to input corresponding invoice characteristic information in the invoicing page according to the contract information, so as to send the invoice characteristic information to the invoicing system;
  • the invoice obtaining module 40 is configured to, upon receiving the prompt for successful invoicing returned by the invoicing system, obtain and save a corresponding invoice according to the prompt for successful invoicing.
  • Each of the virtual function modules of the above-mentioned invoice issuing device is stored in the memory 1005 of the invoice issuing device shown in FIG. 1 and is used to implement all functions of the computer-readable instructions; when each module is executed by the processor 1001, it can realize the process through the robot.
  • the behavior of the billing staff is simulated by clicking, entering, etc. on the display page of the computer terminal to complete the function of the entire process of invoicing.
  • the information acquisition module 10 includes:
  • the system connection unit when receiving a billing request, connects to a corresponding contract management system according to the billing request, and displays a management page of the contract management system;
  • a first determining unit configured to identify the management page and determine a contract query area in the management page
  • a first input unit is configured to input corresponding query characteristics in the contract query area according to the contract characteristics included in the invoicing request to obtain corresponding contract information.
  • the information sending module 30 includes:
  • a second determining unit configured to identify the invoicing page and determine a feature information input area in the invoicing page
  • An information screening unit configured to filter the contract information according to a characteristic type of the characteristic information input area to obtain corresponding characteristic information of an invoice
  • a second input unit is configured to input the invoice characteristic information into the characteristic information input area to send the invoice characteristic information to the invoicing system.
  • the invoice characteristic information includes a total denomination of the invoice
  • the second input unit includes:
  • An invoice determination subunit configured to determine the number of invoices and the denominations of each invoice according to the total denomination of the invoice in the invoice characteristic information and the single denomination limit preset by the invoicing system;
  • An information input subunit is configured to input the invoice characteristic information into the characteristic information input area according to the number of invoices and each invoice denomination, so as to send the invoice characteristic information to the invoicing system.
  • invoice issuing device further includes:
  • the mail sending module is used to start the mailbox software and send a corresponding billing notification email to a preset contact.
  • invoice issuing device further includes:
  • An alarm processing module is configured to determine a corresponding failure type according to the invoicing failure prompt and receive a corresponding alarm processing according to the failure type upon receiving the invoicing failure prompt returned by the invoicing system.
  • invoice issuing device further includes:
  • a configuration modification module configured to, when receiving a first configuration modification instruction sent by the billing master, modify the billing configuration according to the first configuration modification instruction
  • it is configured to send a second configuration modification instruction to the billing sub-machine, so that the billing sub-machine performs billing configuration modification according to the second configuration modification instruction.
  • each module in the above-mentioned invoice issuing device corresponds to each step in the embodiment of the above-mentioned invoice issuing method, and the functions and implementation processes thereof will not be repeated here.
  • an embodiment of the present application further provides a computer-readable storage medium, and the computer-readable storage medium may be a non-volatile readable storage medium.
  • Computer-readable instructions are stored on the computer-readable storage medium of the present application, and when the computer-readable instructions are executed by a processor, the steps of the invoice issuing method described above are implemented.

Landscapes

  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种发票开具方法，包括：在接收到开票请求时，获取与所述开票请求对应的合同信息(S10)；连接开票系统，并显示所述开票系统的开票页面(S20)；根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统(S30)；在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存(S40)。同时还提供一种发票开具装置、设备及计算机可读存储介质。上述方法可实现通过流程自动化的方式，模拟开票人员的行为，在计算机终端的显示页面进行点击、录入等操作，完成发票开具的全流程的功能。

Description

发票开具方法、装置、设备及计算机可读存储介质
本申请要求于2018年6月26日提交中国专利局、申请号为201810673798.4、发明名称为“发票开具方法、装置、设备及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中
技术领域
本申请涉及计算机技术领域，尤其涉及一种发票开具方法、装置、设备及计算机可读存储介质。
背景技术
发票是企业和个人在购销商品、提供或接受服务以及从事其他经营活动时，所开具或收取的业务凭证；对企业而言，在对外签订了合同进行交易后，需要开具对应的发票，以供后续用以进行会计核算。
传统的发票开具方法，是由专门的会计人员根据合同内容人工录入发票内容进行开票。这种人工开票方法，当合同数量较多时，需要花费大量的时间，费时费力，效率较低。
发明内容
本申请的主要目的在于提供一种发票开具方法、装置、设备及计算机可读存储介质，旨在提高发票开具的效率。
为实现上述目的，本申请提供一种发票开具方法，所述发票开具方法包括以下步骤：
在接收到开票请求时，获取与所述开票请求对应的合同信息；
连接开票系统，并显示所述开票系统的开票页面；
根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
可选地，所述在接收到开票请求时，获取与所述开票请求对应的合同信息的步骤包括：
在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
可选地，所述根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤包括：
对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
可选地，所述发票特征信息包括发票总面额，
所述将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统的步骤包括：
根据所述发票特征信息中的发票总面额和所述开票系统预设的单票面额限值确定发票数量和各发票面额；
根据发票数量和各发票面额将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
可选地，所述在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存的步骤之后，还包括：
启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
可选地，所述根据所述合同信息在所述开票页面中录入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤之后，还包括：
在接收到所述开票系统返回的开票失败提示时，根据所述开票失败提示确定对应的失败类型，并根据所述失败类型进行对应的告警处理。
可选地，所述发票开具方法还包括：
在接收到开票母机发送的第一配置修改指令时，根据所述第一配置修改指令进行开票配置修改；
或，向开票子机发送第二配置修改指令，以使所述开票子机根据所述第二配置修改指令进行开票配置修改。
此外，为实现上述目的，本申请还提供一种发票开具装置，所述发票开具装置包括：
信息获取模块，用于在接收到开票请求时，获取与所述开票请求对应的合同信息；
页面显示模块，用于连接开票系统，并显示所述开票系统的开票页面；
信息发送模块，用于根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
发票获取模块，用于在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
此外，为实现上述目的，本申请还提供一种发票开具设备，所述发票开具设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令，其中所述计算机可读指令被所述处理器执行时，实现如上述的发票开具方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机可读指令，其中所述计算机可读指令被处理器执行时，实现如上述的发票开具方法的步骤。
本申请通过机器人流程自动化的方式、模拟开票人员的行为在终端的显示页面进行点击、录入等操作，完成发票开具的全流程，并在开票完成时自动获取和存储发票，从而将发票开具的全流程由计算机（机器人）独立完成，降低了人力成本，提升作业效率，降低出差错率；同时本实施例可以实现24小时不间断工作，工作时间不受限制，保证了开票工作的及时进行；此外，本申请在进行开票时，是通过在用户界面中操作的方式对数据进行处理和传递，不需要在不同的系统之间搭建接口进行数据导入导出等工作，实现跨系统的无缝衔接，降低了开票成本。
附图说明
图1为本申请实施例方案中涉及的发票开具设备的硬件结构示意图；
图2为本申请发票开具方法第一实施例的流程示意图；
图3为本申请发票开具方法第二实施例的流程示意图；
图4为本申请发票开具装置第一实施例的功能模块示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例涉及的发票开具方法主要应用于发票开具设备，该发票开具设备可以是个人计算机（personal computer，PC）、便携计算机、移动终端等具有数据处理功能的设备。
参照图1，图1为本申请实施例方案中涉及的发票开具设备的硬件结构示意图。本申请实施例中，发票开具设备可以包括处理器1001（例如中央处理器Central Processing Unit，CPU），通信总线1002，用户接口1003，网络接口1004，存储器1005。其中，通信总线1002用于实现这些组件之间的连接通信；用户接口1003可以包括显示屏（Display）、输入单元比如键盘（Keyboard）；网络接口1004可选的可以包括标准的有线接口、无线接口（如无线保真WIreless-FIdelity，WI-FI接口）；存储器1005可以是高速随机存取存储器（random access memory，RAM），也可以是稳定的存储器（non-volatile memory），例如磁盘存储器，存储器1005可选的还可以是独立于前述处理器1001的存储装置。本领域技术人员可以理解，图1中示出的硬件结构并不构成对本申请的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
继续参照图1，图1中作为一种计算机可读存储介质的存储器1005可以包括操作系统、网络通信模块以及计算机可读指令。在图1中，网络通信模块可用于连接开票系统，与开票系统进行数据通信；而处理器1001可以调用存储器1005中存储的计算机可读指令，并执行本申请实施例提供的发票开具方法。
本申请实施例提供了一种发票开具方法。
参照图2，图2为本申请发票开具方法第一实施例的流程示意图。
本实施例中，所述发票开具方法包括以下步骤：
步骤S10，在接收到开票请求时，获取与所述开票请求对应的合同信息；
发票是企业和个人在购销商品、提供或接受服务以及从事其他经营活动时，所开具或收取的业务凭证；对企业而言，在对外签订了合同进行交易后，需要开具对应的发票，以供后续用以进行会计核算。传统的发票开具方法，是由专门的会计人员根据合同内容人工录入发票内容进行开票。这种人工开票方法，当合同数量较多时，需要花费大量的时间，费时费力，效率较低。对此，本实施例中提出一种发票开具方法，通过机器人流程自动化（Robotic Process Automation，RPA）的方式、模拟开票人员的行为在计算机终端的显示页面进行点击、录入等操作，完成发票开具的全流程，并在开票成功时自动存储发票。
本实施例中的发票开具方法可以是由发票开具设备实现的，该发票开具设备以可以是个人计算机（personal computer，PC）、便携计算机、移动终端等具有数据处理功能的设备，本实施例中以PC为例进行说明。该PC可以是财务系统中的某台PC端，该PC可与开票机构（如税务局百旺、航信等）的开票系统连接，实现数据交互；同时，该PC中还设置有流程自动化（Robotic Process Automation，RPA）机器人，以模拟自然人的行为进行开票操作。其中，该RPA机器人，也可以理解为通过软件编程语言实现的、基于一定规则在可视的用户界面模拟用户操作的软件，从而将手工活动进行自动化。
本实施例中，PC在接收到开票请求时，首先将会获取与该开票请求对应的合同信息。对于该开票请求，可以是由其它管理设备发送；当然，该开票请求也可以是由用户手动在PC上触发；此外，还可以是设置对应的开票条件，当满足该开票条件时自动触发对应的开票请求（如定时启动、当新签合同达到一定数量、新签合同的金额达到一定数值等）。对于该开票请求中，可以是包括了合同号、合同时间、合同对象、合同类型等合同特征，PC可根据这些合同特征获取到对应的合同信息；其中，这些合同信息可以是存储在PC本地，当然也可以是由专门的合同管理系统进行存储和管理。
进一步的，当合同信息是由专门的合同管理系统进行存储和管理时，PC将要从该合同管理系统获取相关的合同信息。具体的，PC在接收到开票请求时，将连接合同管理系统；在这个过程中，若合同管理系统是浏览器/服务器（Browser/Server，B/S)架构的形式，则PC将会启动预先安装的浏览器连接合同管理系统；若合同管理系统是客户端/服务器（Client/Server，C/S）架构的形式，则PC则会根据客户端软件名查找预先安装好的合同管理客户端（软件），并通过该客户端连接合同管理系统。当与合同管理系统连接成功时，PC的显示屏上将显示相关的管理页面。此时PC将对该管理页面进行识别，并在该管理页面中确定合同查询区域，然后在该合同查询区域中输入目标合同的查询特征，以查询符合要求的目标合同。其中，对于上述页面识别和区域确定的过程，可以是预先根据管理页面的排版模式预先设置RPA机器人的识别脚本（即根据合同管理系统定制RPA机器人在管理系统的识别规范）；例如，管理页面的分为上下两个区域，上区域为合同查询区，合同查询区中包括有输入框，下区域为系统文字介绍，则可根据该排版方式设置对应RPA的管理页面要素识别脚本，通过识别出输入框，从而确定合同查询区域；然后即可在该区域中输入目标合同的合同特征。当然在识别的过程中，可以是结合光学字符识别（Optical Character Recognition，OCR）技术进行，即在显示管理页面时进行截图，并通过OCR技术识别出相关的关键字，从而根据关键字确定对应的合同查询区域。在根据目标合同的合同特征查询到目标合同时，PC接可获取到对应的合同信息；当然，PC还可以将这些合同信息下载到本地进行以文档的形式存储（可以是以excel、word、xml、json等形式）。通过以上方式，本实施例可以通过在用户界面中操作的方式获取相关合同信息，不需要在不同的系统之间搭建接口进行数据导出等工作，实现跨系统的无缝衔接。
步骤S20，连接开票系统，并显示所述开票系统的开票页面；
本实施例中，在获取到合同信息时，PC将连接开票系统，以进行相关的开票操作。对该开票过程，与上述连接合同管理系统获取合同信息的过程类似，可以是通过在用户界面中操作的方式进行信息传递。具体的，PC将根据开票系统的架构形式，选择合适的连接方式连接开票系统，并显示开票系统的开票页面。其中，若开票系统是B/S架构的形式，则PC会启动预先安装的浏览器连接开票系统，并显示开票页面；若开票系统是C/S架构的形式，则PC则会根据开票客户端软件名查找预先安装好的开票客户端（软件），并通过该客户端连接开票系统，然后显示开票页面。
步骤S30，根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
本实施例中，PC在显示开票页面后，即可根据合同信息在该开票页面中进行输入，以向开票系统发送开票所需的发票特征信息（或称为开票入参）。
具体的，PC将对开票页面进行识别，并在开票页面中确定特征输入区域，然后在该特征输入区域输入发票特征信息。其中，该发票特征信息可以根据合同信息中得到，例如发票特征信息中的发票金额可以根据合同信息中的合同金额得到，发票特征信息中的银行账号、税务登记号可以根据合同信息中的合同对象账户得到。而对于特征输入区域的识别过程，也可以是预先根据开票页面的排版模式预先设置RPA机器人的识别脚本（即根据开票系统定制RPA机器人在开票系统的识别规范），从而在显示开票页面时，根据该识别脚本识别出相关的页面要素，从而确定特征输入区域。当然在识别的过程中，可以是结合光学字符识别（Optical Character Recognition，OCR）技术进行，即在显示开票页面时进行截图，并通过OCR技术识别出相关的关键字，从而根据关键字确定对应的特征输入区域。
值得说明的是，对于步骤S10所得到的合同信息，并不一定都是发票特征信息；对此，PC可根据特征信息输入区域的特征类型对合同信息进行筛选，获取对应的发票特征信息，然后再将这些发票特征信息输入至特征信息的输入区域，以将所述发票特征信息发送至开票系统。
当然，在实际中，若开票系统支持文档批量导入的方式入参，则PC也可在开票页面中识别和确定对应的文档上传按键，并通过该按键上传本地存储的发票特征信息文档。而对于该发票特征信息文档，则可以是由步骤S10所得的合同信息文档生成；即PC将根据开票系统的开票特征规则（入参规则）对合同信息文档进行调整后得到发票特征信息文档，该调整内容可以包括无效信息删除、格式转化（如大小写转化、数据值的位数调整等）、字段列的排序等。
再进一步的，对于不同的开票系统，可能会具有不同的开票金额要求；对此，PC还可在进行发票特征信息输入时，根据开票金额要求进行相应的分票处理。具体的，PC首先将根据发票特征信息中的发票总面额、以及开票系统预设的单票面额限值确定发票数量和各发票面额；然后根据发票数量和各发票面额将发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统；在该输入过程中，可能会存在多次输入的情况。例如，开票系统中对于每张发票的单票面额限值为100万元，而合同A的发票总面额为500万元，则PC会根据该发票总面额和单票面额限制确定发票数量为5张，每张发票面额均为100万元；然后根据该发票数量和发票面额进行发票特征信息的输入，以在满足开票条件的情况下将发票特征信息发送至开票系统，从而将合同A的开票需求以多张发票的方式实现。
步骤S40，在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
本实施例中，开票系统在根据发票特征信息开票成功时，将会向PC返回对应的开票成功提示。PC在接收到该开票成功提示时，即可根据该开票成功提示获取对应的发票，并将其进行存储。其中，该发票可以是包括于开票成功提示中，即开票系统将发票返回PC；也可以在开票成功提示中添加发票的下载链接，PC根据该下载链接将发票下载到本地进行保存。
进一步的，本实施例中PC的RPA机器人，可以是单机无交互的形式，也可以是网络交互的形式；当RPA机器人为单机无交互的形式时，其开票配置（包括页面识别配置、输入配置等）需要在该PC本体上进行设置；当RPA机器人为网络交互的形式时，其开票配置可以是以同步的方式进行设置，从而方便企业财务的集群式系统的使用需求，减少了配置工作量，提高配置效率。具体的，当RPA机器人采用网络交互的形式时，是由多台设置有同一版本的PRA的PC（发票开具设备）组成了一个开票PC集群，每台PC均可独立完成上述的开票流程；该集群中至少具有一台开票母机、并至少具有一台开票子机，其中该开票母机可以是在集群建立时进行指定；当需要进行集群配置修改时，可以是在开票母机上进行配置修改，在修改完成时，开票母机将向其它的开票子机发送配置修改指令，以使开票子机根据该配置修改指令进行相应的配置修改，实现配置同步。本实施例中的PC作为开票子机时，若接收到开票母机发送的第一配置修改指令，则将根据该第一配置修改指令进行开票配置修改；而本实施例中的PC作为开票母机时，则可根据本机的RPA配置修改情况向开票子机发送第二配置修改指令，以使开票子机根据该第二配置修改指令进行开票配置修改。
本实施例中，在接收到开票请求时，获取与所述开票请求对应的合同信息；连接开票系统，并显示所述开票系统的开票页面；根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。通过以上方式，本实施例通过机器人流程自动化的方式、模拟开票人员的行为在终端的显示页面进行点击、录入等操作，完成发票开具的全流程，并在开票完成时自动获取和存储发票，从而将发票开具的全流程由计算机（机器人）独立完成，降低了人力成本，提升作业效率，降低出差错率；同时本实施例可以实现24小时不间断工作，工作时间不受限制，保证了开票工作的及时进行；此外，本实施例在进行开票时，是通过在用户界面中操作的方式对数据进行处理和传递，不需要在不同的系统之间搭建接口进行数据导入导出等工作，实现跨系统的无缝衔接，降低了开票成本。
参照图3，图3为本申请发票开具方法第二实施例的流程示意图。
基于上述图2所示实施例，本实施例中，步骤S40之后，还包括：
步骤S50，启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
本实施例中，PC在接收到该开票系统返回的开票成功提示、并获取到相关发票时，还可以向预设的联系人进行邮件提醒。具体的，PC会启动预先安装的邮箱软件，然后点选其中的通知模板邮件，并在收件人栏填写预设联系人的邮箱地址信息，从而获取开票通知邮件。其中，该预设联系人的邮箱地址信息，可以是预先存储在邮箱账户中，PC在启动邮箱软件后，会点击打开常用联系人栏，并对其中的人名进行识别，然后点选对应的预设联系人，从而使得预存的预设联系人的邮箱地址信息自动填充至写信窗口的收件人栏；当然预设联系人的邮箱地址信息也可以是预先保存在联系人excel（或其它文档）中，PC在启动邮箱软件后，会打开该联系人excel文档，并根据文档中的邮箱地址信息填写收件人栏。在得到开票通知邮件后，PC即可将该开票通知发送至预设联系人的邮箱中，以进行通知。当然，在进行邮件通知时，也可以是通过浏览器登录至网页邮箱中进行设置，具体过程与通过软件形式进行通知的方式类型，此处不再赘述。值得说明的是，本实施例中也可以根据实际情况设置其它的通知方式进行通知，例如通过社交软件、电话等。
进一步的，本实施例中，当开票系统开票失败时，将会向PC返回对应的开票失败提示。而当PC接收到该开票失败提示时，还可进行相应的告警处理。例如如上述般向预设联系人发送告警邮件、或是向相关合同系统发送告警信息等。当然，开票失败可能是由不同的原因引起的，对于不同的失败原因，PC还可采用不同的告警处理方式。具体的，开票系统在返回开票失败提示时，还可添加相应的失败类型标识；PC在接收到该开票失败提示时，还可以根据该失败类型标识确定对应的失败类型（原因），然后根据失败原因进行对应的告警处理。
此外，本申请实施例还提供一种发票开具装置。
参照图4，图4为本申请发票开具装置第一实施例的功能模块示意图。
本实施例中，所述发票开具装置包括：
信息获取模块10，用于在接收到开票请求时，获取与所述开票请求对应的合同信息；
页面显示模块20，用于连接开票系统，并显示所述开票系统的开票页面；
信息发送模块30，用于根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
发票获取模块40，用于在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
其中，上述发票开具装置的各虚拟功能模块存储于图1所示发票开具设备的存储器1005中，用于实现计算机可读指令的所有功能；各模块被处理器1001执行时，可实现通过机器人流程自动化的方式、模拟开票人员的行为在计算机终端的显示页面进行点击、录入等操作，完成发票开具的全流程的功能。
进一步的，所述信息获取模块10，包括：
系统连接单元，在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
第一确定单元，用于对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
第一输入单元，用于根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
进一步的，所述信息发送模块30，包括：
第二确定单元，用于对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
信息筛选单元，用于根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
第二输入单元，用于将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
进一步的，所述发票特征信息包括发票总面额，所述第二输入单元，包括：
发票确定子单元，用于根据所述发票特征信息中的发票总面额和所述开票系统预设的单票面额限值确定发票数量和各发票面额；
信息输入子单元，用于根据发票数量和各发票面额将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
进一步的，所述发票开具装置，还包括：
邮件发送模块，用于启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
进一步的，所述发票开具装置，还包括：
告警处理模块，用于在接收到所述开票系统返回的开票失败提示时，根据所述开票失败提示确定对应的失败类型，并根据所述失败类型进行对应的告警处理。
进一步的，所述发票开具装置，还包括：
配置修改模块，用于在接收到开票母机发送的第一配置修改指令时，根据所述第一配置修改指令进行开票配置修改；
或，用于向开票子机发送第二配置修改指令，以使所述开票子机根据所述第二配置修改指令进行开票配置修改。
其中，上述发票开具装置中各个模块的功能实现与上述发票开具方法实施例中各步骤相对应，其功能和实现过程在此处不再一一赘述。
此外，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质可以为非易失性可读存储介质。
本申请计算机可读存储介质上存储有计算机可读指令，其中所述计算机可读指令被处理器执行时，实现如上述的发票开具方法的步骤。
其中，所述计算机可读指令被执行时所实现的方法可参照本申请发票开具方法的各个实施例，此处不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者系统不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者系统所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者系统中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种发票开具方法，其特征在于，所述发票开具方法包括以下步骤：
    在接收到开票请求时，获取与所述开票请求对应的合同信息；
    连接开票系统，并显示所述开票系统的开票页面；
    根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
    在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
  2. 如权利要求1所述的发票开具方法，其特征在于，所述在接收到开票请求时，获取与所述开票请求对应的合同信息的步骤包括：
    在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
    对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
    根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
  3. 如权利要求1所述的发票开具方法，其特征在于，所述根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤包括：
    对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
    根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
    将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  4. 如权利要求3所述的发票开具方法，其特征在于，所述发票特征信息包括发票总面额，
    所述将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统的步骤包括：
    根据所述发票特征信息中的发票总面额和所述开票系统预设的单票面额限值确定发票数量和各发票面额；
    根据发票数量和各发票面额将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  5. 如权利要求1所述的发票开具方法，其特征在于，所述在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存的步骤之后，还包括：
    启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
  6. 如权利要求1所述的发票开具方法，其特征在于，所述根据所述合同信息在所述开票页面中录入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤之后，还包括：
    在接收到所述开票系统返回的开票失败提示时，根据所述开票失败提示确定对应的失败类型，并根据所述失败类型进行对应的告警处理。
  7. 如权利要求1所述的发票开具方法，其特征在于，所述发票开具方法还包括：
    在接收到开票母机发送的第一配置修改指令时，根据所述第一配置修改指令进行开票配置修改；
    或，向开票子机发送第二配置修改指令，以使所述开票子机根据所述第二配置修改指令进行开票配置修改。
  8. 一种发票开具装置，其特征在于，所述发票开具装置包括：
    信息获取模块，用于在接收到开票请求时，获取与所述开票请求对应的合同信息；
    页面显示模块，用于连接开票系统，并显示所述开票系统的开票页面；
    信息发送模块，用于根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
    发票获取模块，用于在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
  9. 如权利要求8所述的发票开具装置，其特征在于，所述信息获取模块包括：
    系统连接单元，在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
    第一确定单元，用于对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
    第一输入单元，用于根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
  10. 如权利要求8所述的发票开具装置，其特征在于，所述信息发送模块包括：
    第二确定单元，用于对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
    信息筛选单元，用于根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
    第二输入单元，用于将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  11. 如权利要求10所述的发票开具装置，其特征在于，所述发票特征信息包括发票总面额，所述第二输入单元，包括：
    发票确定子单元，用于根据所述发票特征信息中的发票总面额和所述开票系统预设的单票面额限值确定发票数量和各发票面额；
    信息输入子单元，用于根据发票数量和各发票面额将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  12. 如权利要求8所述的发票开具装置，其特征在于，所述发票开具装置，还包括：
    邮件发送模块，用于启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
  13. 一种发票开具设备，其特征在于，所述发票开具设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令，其中所述计算机可读指令被所述处理器执行时，实现如下步骤：
    在接收到开票请求时，获取与所述开票请求对应的合同信息；
    连接开票系统，并显示所述开票系统的开票页面；
    根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
    在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
  14. 如权利要求13所述的发票开具设备，其特征在于，所述在接收到开票请求时，获取与所述开票请求对应的合同信息的步骤包括：
    在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
    对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
    根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
  15. 如权利要求13所述的发票开具设备，其特征在于，所述根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤包括：
    对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
    根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
    将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  16. 如权利要求15所述的发票开具设备，其特征在于，所述发票特征信息包括发票总面额，
    所述将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统的步骤包括：
    根据所述发票特征信息中的发票总面额和所述开票系统预设的单票面额限值确定发票数量和各发票面额；
    根据发票数量和各发票面额将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
  17. 如权利要求13所述的发票开具设备，其特征在于，所述在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存的步骤之后，还包括：
    启动邮箱软件，并向预设联系人发送对应的开票通知邮件。
  18. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机可读指令，其中所述计算机可读指令被处理器执行时，实现如下步骤：
    在接收到开票请求时，获取与所述开票请求对应的合同信息；
    连接开票系统，并显示所述开票系统的开票页面；
    根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统；
    在接收到所述开票系统返回的开票成功提示时，根据所述开票成功提示获取对应的发票并进行保存。
  19. 如权利要求18所述的计算机可读存储介质，其特征在于，所述在接收到开票请求时，获取与所述开票请求对应的合同信息的步骤包括：
    在接收到开票请求时，根据所述开票请求连接对应的合同管理系统，并显示所述合同管理系统的管理页面；
    对所述管理页面进行识别，并在所述管理页面中确定合同查询区域；
    根据所述开票请求包括的合同特征在所述合同查询区域输入对应的查询特征，以获取对应的合同信息。
  20. 如权利要求18所述的计算机可读存储介质，其特征在于，所述根据所述合同信息在所述开票页面中输入对应的发票特征信息，以将所述发票特征信息发送至所述开票系统的步骤包括：
    对所述开票页面进行识别，并在所述开票页面中确定特征信息输入区域；
    根据所述特征信息输入区域的特征类型对所述合同信息进行筛选，获取对应的发票特征信息；
    将所述发票特征信息输入至所述特征信息输入区域，以将所述发票特征信息发送至所述开票系统。
PCT/CN2018/103331 2018-06-26 2018-08-30 发票开具方法、装置、设备及计算机可读存储介质 WO2020000632A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810673798.4A CN109741118A (zh) 2018-06-26 2018-06-26 发票开具方法、装置、设备及计算机可读存储介质
CN201810673798.4 2018-06-26

Publications (1)

Publication Number Publication Date
WO2020000632A1 true WO2020000632A1 (zh) 2020-01-02

Family

ID=66354206

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103331 WO2020000632A1 (zh) 2018-06-26 2018-08-30 发票开具方法、装置、设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN109741118A (zh)
WO (1) WO2020000632A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111402522A (zh) * 2020-03-25 2020-07-10 云账户技术(天津)有限公司 一种信息处理方法、装置及系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021076204A1 (en) * 2019-10-14 2021-04-22 UiPath Inc. Providing image and text data for automatic target selection in robotic process automation
CN110806934A (zh) * 2019-11-15 2020-02-18 四川中电启明星信息技术有限公司 基于rpa技术的智能一体机开发及多业务快速处理方法
CN111091428B (zh) * 2019-11-25 2024-05-10 浪潮通用软件有限公司 一种基于物联网的开发票方法与装置
CN111178991B (zh) * 2019-12-12 2024-03-08 远光软件股份有限公司 一种增值税发票模拟开票系统、方法及计算机
CN111091431B (zh) * 2019-12-23 2023-12-19 江苏电力信息技术有限公司 一种基于rpa机器人的自动开具电子发票的方法
CN111144963A (zh) * 2019-12-29 2020-05-12 上海瀚之友信息技术服务有限公司 一种自动化开票方法及系统
CN112008766A (zh) * 2020-09-03 2020-12-01 国网江苏省电力有限公司南通供电分公司 一种基于rpa机器人的数据补召自动化方法
CN112800740A (zh) * 2021-01-27 2021-05-14 北京明略软件系统有限公司 使用rpa机器人实现自动开票的方法、系统、设备及存储介质
CN113741828A (zh) * 2021-07-30 2021-12-03 太逗科技集团有限公司 自动开票打印发票的方法、装置、电子设备及存储介质
CN113610585A (zh) * 2021-08-10 2021-11-05 北京来也网络科技有限公司 基于rpa及ai的税票开具方法、装置、设备及介质
CN115689262A (zh) * 2022-09-05 2023-02-03 国网浙江省电力有限公司桐乡市供电公司 一种变电站倒闸操作票自动生成方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104881804A (zh) * 2015-05-27 2015-09-02 北京京东尚科信息技术有限公司 电子发票开具方法及系统
CN107133831A (zh) * 2017-05-12 2017-09-05 百望电子发票数据服务有限公司 一种自助开具电子发票的方法及系统
CN107301752A (zh) * 2017-01-24 2017-10-27 西安艾润物联网技术服务有限责任公司 打印停车费税控发票的方法及装置
CN107679925A (zh) * 2017-09-25 2018-02-09 深圳市丰巢科技有限公司 一种移动终端在线开发票的方法、移动终端及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104881804A (zh) * 2015-05-27 2015-09-02 北京京东尚科信息技术有限公司 电子发票开具方法及系统
CN107301752A (zh) * 2017-01-24 2017-10-27 西安艾润物联网技术服务有限责任公司 打印停车费税控发票的方法及装置
CN107133831A (zh) * 2017-05-12 2017-09-05 百望电子发票数据服务有限公司 一种自助开具电子发票的方法及系统
CN107679925A (zh) * 2017-09-25 2018-02-09 深圳市丰巢科技有限公司 一种移动终端在线开发票的方法、移动终端及其系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111402522A (zh) * 2020-03-25 2020-07-10 云账户技术(天津)有限公司 一种信息处理方法、装置及系统

Also Published As

Publication number Publication date
CN109741118A (zh) 2019-05-10

Similar Documents

Publication Publication Date Title
WO2020000632A1 (zh) 发票开具方法、装置、设备及计算机可读存储介质
WO2020015067A1 (zh) 数据采集方法、装置、设备及存储介质
WO2020233090A1 (zh) 基于h5页面的应用配置方法、装置、设备及存储介质
WO2020258656A1 (zh) 代码段的生成方法、装置、存储介质及计算机设备
WO2020006852A1 (zh) 差旅费自助核销处理方法、装置、设备和计算机存储介质
WO2020087978A1 (zh) 风控审核模型的生成方法、装置、设备及存储介质
WO2018149083A1 (zh) 业务数据流转方法、装置、存储介质和终端
CN101615177A (zh) 在服务器/浏览器结构上的自定义报表实现方法及装置
WO2020147385A1 (zh) 数据录入方法、装置、终端及计算机可读存储介质
WO2021003956A1 (zh) 产品信息的管理方法、装置、设备及存储介质
EP3584762A1 (en) Sequence management system, sequence management device, and program
WO2020087981A1 (zh) 风控审核模型生成方法、装置、设备及可读存储介质
WO2020062658A1 (zh) 合同生成方法、装置、设备及存储介质
WO2020087704A1 (zh) 信贷信息管理方法、装置、设备和存储介质
WO2020233060A1 (zh) 事件通知方法、事件通知服务器、存储介质及装置
WO2020233089A1 (zh) 测试用例生成方法、装置、终端及计算机可读存储介质
WO2020233078A1 (zh) 用户信息表单的构建方法、装置、设备及存储介质
WO2019179025A1 (zh) 关联交易识别方法、程序、装置及存储介质
WO2013028009A2 (ko) 스마트 오피스 시스템 및 운용을 위한 서버 및 운용 방법
US9639515B2 (en) Transfer of data between applications using intermediate user interface
WO2019000962A1 (zh) 收益计算方法、装置及计算机可读存储介质
WO2020000633A1 (zh) 资金监控方法、资金监控系统、终端及可读存储介质
WO2021261708A1 (ko) 정보시스템을 설계하여 프로그램과 데이터베이스를 자동으로 생성하고 테스트를 자동 수행하는 소프트웨어 공학플랫폼
WO2020143306A9 (zh) 对象互转方法、装置及存储介质、服务器
WO2022220311A1 (ko) 이종 플랫폼 간의 자동 연동 방법, 장치 및 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18924461

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18924461

Country of ref document: EP

Kind code of ref document: A1