WO2020006895A1 - 对账方法、装置、计算机设备和存储介质 - Google Patents

对账方法、装置、计算机设备和存储介质 Download PDF

Info

Publication number
WO2020006895A1
WO2020006895A1 PCT/CN2018/108028 CN2018108028W WO2020006895A1 WO 2020006895 A1 WO2020006895 A1 WO 2020006895A1 CN 2018108028 W CN2018108028 W CN 2018108028W WO 2020006895 A1 WO2020006895 A1 WO 2020006895A1
Authority
WO
WIPO (PCT)
Prior art keywords
enterprise
reconciliation
bank
query task
pipeline
Prior art date
Application number
PCT/CN2018/108028
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 WO2020006895A1 publication Critical patent/WO2020006895A1/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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • the present application relates to the field of computers, and in particular, to a method, an apparatus, a computer device, and a storage medium for reconciliation.
  • the traditional enterprise reconciliation is to download the flow statement from the bank to the local, and then compare it with the manual bookkeeping of the enterprise, which is very labor-intensive and time-consuming and prone to errors.
  • the main purpose of this application is to provide an enterprise reconciliation method, device, computer equipment and storage medium for quick reconciliation.
  • the present application proposes a method for reconciliation, which uses an enterprise-end front-end machine set on the enterprise side to exchange financial data with the bank-side.
  • the front-end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with multiple bank-end front-end processors of different types of banks; the method includes:
  • the reconciliation bank account obtained by the enterprise front-end processor from the bank front-end processor, and inserting the current account statement into a preset reconciliation list, where the reconciliation The list includes at least two parts, one of which is used to insert the running bill and the other is used to insert the enterprise journal of the enterprise end;
  • the first record of the running account in the first part of the reconciliation list is matched with the second record in the corporate journal in the second part, and the matched first record and second record are automatically blended.
  • the application also provides a reconciliation device, which uses the enterprise-side front-end machine set on the enterprise side to exchange financial data with the bank.
  • the enterprise-side front-end machine is provided with multiple UKey interfaces, and the enterprise-side front-end machine corresponds to A plurality of the UKey interfaces are configured to complete financial data interaction with a plurality of bank-side front-end processors of different types of banks; the device includes:
  • a sending unit configured to send a pipeline query task corresponding to a reconciling bank account to be reconciled to the enterprise-end front-end processor
  • a forwarding unit configured to use the enterprise-end front-end machine to send a flow query task for the reconciling bank account to a corresponding bank front-end machine, so as to query a corresponding flow-account statement to a bank server of the corresponding bank front-end machine;
  • An inserting unit configured to receive the current account statement of the reconciliation bank account obtained by the enterprise front-end processor from the bank front-end processor, and insert the current account statement into a preset reconciliation list, where ,
  • the reconciliation list includes at least two parts, one of which is used to insert the running bill and the other is used to insert the enterprise journal of the enterprise.
  • a blending unit configured to match the first record of the running statement in the first part of the reconciliation list with the second record in the corporate journal in the second part, and match the matched first record with the second record Automatic blending.
  • the present application further provides a computer device including a memory and a processor, where the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, implements the steps of any of the foregoing methods.
  • the present application also provides a computer non-volatile readable storage medium having computer-readable instructions stored thereon, which are executed by a processor to implement the steps of the method according to any one of the foregoing.
  • the reconciliation method, device, computer equipment and storage medium of the present application because multiple front-end UKey interfaces are set on the enterprise-side front-end machine and corresponding configurations are performed, so the enterprise-side front-end machine can conduct banking with multiple different types of banks.
  • Enterprise direct connection function when the corresponding UKey is inserted, you can use the corresponding bank account to query the flow of bills, and in the case of flow inquiry of multiple different bank accounts, you can directly operate without switching logins, etc.
  • the running bill is obtained, it is inserted into the preset reconciliation list and automatically matched with the corporate journal to achieve the purpose of automatic reconciliation, which greatly saves the workload of the reconciliation staff and improves the reconciliation. effectiveness.
  • FIG. 1 is a schematic flowchart of a reconciliation method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of step S1 of the reconciliation method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of step S3 of the reconciliation method according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a structure of a reconciliation device according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a sending unit according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a structure of a reconciliation device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a structure of an insertion unit according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • an embodiment of the present application provides a reconciliation method, which uses an enterprise-end front-end machine set on an enterprise side to perform financial data interaction with a bank-side.
  • the enterprise-end front-end machine is provided with multiple UKey interfaces.
  • the enterprise The front end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with a plurality of different bank end front processors.
  • the above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise.
  • the foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines.
  • the configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface.
  • the configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number.
  • Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for.
  • each bank-enterprise direct account When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise.
  • the corresponding UKey (a small storage device directly connected to the computer via USB, with password verification function, and reliable and high speed) can be inserted into the front-end machine, which can realize an enterprise-side front-end machine and a number of different types of banks.
  • the front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer.
  • the above major banks refer to different banks.
  • ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.
  • the above method includes steps:
  • the above-mentioned flow query task is a task of obtaining a flow statement of a designated reconciliation bank account.
  • Enterprises that can use the front end of the enterprise will have multiple different bank accounts, and these bank accounts are distributed in different types of banks. Because the above-mentioned enterprise-side front-end machine can insert multiple UKeys, when querying the running bills of different reconciling bank accounts, as long as all UKeys corresponding to each bank account are inserted into the enterprise-side front-end machine, it is not necessary to query each time.
  • the process of sending a pipeline query task includes: after selecting a reconciliation bank account that needs to be reconciled in a list, and receiving a "start query" command to generate a reconciliation bank account for the selected reconciliation bank account.
  • the pipeline query task is then sent to the enterprise-end front-end processor.
  • the pipeline query task is first sent to the application server corresponding to the enterprise-end front-end machine, and then the application server sends the application-side front-end machine.
  • the above application server refers to a third-party application server that provides an enterprise-side front-end processor to the enterprise. It serves as the management background of the enterprise-side front-end processor. The tasks issued by the enterprise will first enter the above application server and then be sent by the application server to the enterprise. Front-end machine.
  • step S2 because the above-mentioned enterprise-side front-end machine is connected to different bank front-end machines, after obtaining the flow query task, it will first analyze the information of the reconciling bank account corresponding to the flow query task, etc. The task is correctly sent to the corresponding bank front-end machine. When the task is sent to the corresponding bank front-end machine to query the task, the corresponding UKey information will also be obtained, so that the bank can normally query the flow account.
  • the above reconciliation list is a form divided into two columns, one of which is to insert the current account statement, and the other one is to insert the enterprise journal to facilitate manual checking by the reconciliation personnel.
  • step S4 it is to match the running bill with the first record and the second record in the corporate journal. If the matching is successful, the matching is performed, leaving the unsuccessful first record and the second record.
  • the above automatic blending is to eliminate the first and second records that match each other in the reconciliation list. In the automatic elimination process, they are eliminated in pairs, that is, eliminating a first record will necessarily eliminate a second record.
  • the above requirements for matching the first record and the second record are that the data corresponding to the specified field is the same.
  • the reconciliation staff will manually perform the blending and the manual blending. After that, if there are still the first record and the second record, it means that there are discrepancies in the corporate diary and current account, which need to be checked specifically.
  • the above-mentioned step S1 of sending a flow query task corresponding to a reconciling bank account to be reconciled to the enterprise-end front end includes:
  • the above-mentioned pipeline query task ID is only an identifier, and the identifier uniquely corresponds to one of the pipeline query tasks.
  • the pipeline query task ID has no task content, so as to prevent the pipeline query task from being directly placed on the front end of the enterprise. It affects the running space of the front end of the enterprise and reduces its running speed. Because the enterprise-end front-end unit of this application can be connected to multiple bank-side front-end units, there will be many different tasks, and directly stacking various tasks into the cache of the front-end unit will greatly reduce the enterprise-side front-end units. Set up the operating efficiency and even crash.
  • the preset cache queue generally includes a transaction cache queue and a query cache queue. Different cache queues store task IDs of corresponding attributes, and correspondingly set a transaction thread pool and a query thread pool.
  • the front end of the enterprise obtains the pipeline query task ID, it first determines the attributes of the pipeline query task ID.
  • the attributes include transaction attributes and query attributes. Because the pipeline query task ID belongs to the query class, it is placed in the query cache queue. in.
  • the tasks in the two cache queues are sorted according to priority. Each task will be set with a type identifier. The type identifier is divided into 1-8 levels. If it is 1, the highest level, which represents emergency tasks.
  • Priority processing can be based on presets. Pre-set rules, according to the specific request attached to the corresponding priority level, for example, the level of payment is higher than the level of query bank flow.
  • the pipeline query task ID fed back by the front-end server of the enterprise refers to that if the query thread pool corresponding to the query cache queue is free, the pipeline query task is obtained from the query cache queue.
  • the cache queue is only the pipeline query task ID, so the front end of the enterprise side will return the pipeline query task ID to the above application server, and the application server will generate or call the corresponding task according to the pipeline query task ID, and then send it to the enterprise side front end machine.
  • step S1 of sending the flow query task corresponding to the reconciling bank account to be reconciled to the enterprise-end front end the method includes:
  • the identifier corresponding to the type of the bank of the UKey device inserted in each UKey interface is collected, and then the identifier is compared with the identifier representing the various types of banks configured when the front-end processor of the enterprise is configured.
  • the collected logos fully cover the logos representing various types of banks configured when the enterprise-end front-end is configured, then it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front-end, and subsequent steps such as step S1 can be performed. If not, extract the type of bank corresponding to the uncovered logo and send it to the relevant personnel of the enterprise to report the alarm.
  • the relevant personnel of the enterprise can perform corresponding processing and forget the inserted UKey device or the insertion place will be loose. Re-insertion of UKey equipment caused by poor contact to ensure the interaction between the enterprise and the banks.
  • the foregoing receives the current account statement of the reconciliation bank account obtained by the enterprise front-end processor from the bank front-end processor, and inserts the current account statement into a preset Step S3 in the reconciliation list includes:
  • the above-mentioned fields include necessary fields such as account information and amount, and then these data are extracted from the running bill and inserted into the reconciliation list.
  • the corporate journal is put into an excel form and then inserted into the reconciliation list. Because the mode and content of the flow statement of different banks are different, in order to facilitate management and accurate reconciliation, this application will extract the data corresponding to the fields required in the flow statement from the flow statement and insert it into the preset standard. Reconciliation list. In the same way, the same will be done for the corporate journal, etc.
  • the reconciliation method further includes:
  • the enterprise-side front-end unit and application server should be online for a long time, but because it is an electronic product, it will inevitably be caused by failure or upgrade. At this time, the enterprise-side front-end unit and application server may lose connection. When the connection between the two fails, an alarm message needs to be issued to prevent the company's financial system from obtaining the corresponding running bill after the reconciliation request is issued.
  • the front end of the enterprise and the application server detect the connection status of the two by using a heartbeat detection method.
  • the alarm information sent includes sending information such as emails to relevant personnel of the enterprise, and / or to relevant personnel of third parties who provide front-end machines of the enterprise side.
  • step S11 of sending a pipeline query task ID corresponding to the pipeline query task of the reconciling bank account to the enterprise-end front end includes:
  • step S111 different query tasks or transaction tasks cannot be performed at the same time, so they need to be performed in accordance with the order of the instructions, and one instruction can be executed before the next instruction can be executed. It cannot be executed asynchronously.
  • the enterprise front end sends a payment task.
  • the reconciliation method further includes:
  • the protocol buffers are used for serialization.
  • Protocol Buffers It is a lightweight and efficient structured data storage format, which can be used for serialization of structured data, or serialization. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of task message encapsulation and transmission.
  • the enterprise-side front-end unit can perform bank-enterprise direct connection functions with multiple different types of banks; when After inserting the corresponding UKey, you can use the corresponding bank account to query the flow of bills, and in the case of flow query of multiple different bank accounts, you can directly operate without switching logins, etc. After obtaining the flow of bills , It is inserted into the preset reconciliation list to automatically match with the corporate journal, thereby achieving the purpose of automatic reconciliation, greatly saving the workload of the reconciliation staff, and improving the efficiency of reconciliation.
  • an embodiment of the present application further provides a reconciliation device that uses an enterprise-side front-end machine set on an enterprise side to perform financial data interaction with a bank-side.
  • the enterprise-side front-end machine is provided with multiple UKey interfaces.
  • the enterprise front end corresponds to a plurality of the UKey interfaces, and is configured to complete financial data interaction with a plurality of different bank end front end types.
  • the above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise.
  • the foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines.
  • the configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface.
  • the configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number.
  • Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for.
  • each bank-enterprise direct account When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise.
  • the corresponding UKey (a small storage device directly connected to the computer via USB, with password verification function, and reliable and high speed) can be inserted into the front-end machine, which can realize an enterprise-side front-end machine and a number of different types of banks.
  • the front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer.
  • the above major banks refer to different banks.
  • ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.
  • the device includes:
  • the sending unit 10 is configured to send a pipeline query task corresponding to a reconciling bank account to be reconciled to the front end of the enterprise.
  • the above-mentioned flow query task is a task of obtaining a flow statement of a designated reconciliation bank account.
  • Enterprises that can use the front end of the enterprise will have multiple different bank accounts, and these bank accounts are distributed in different types of banks.
  • the above-mentioned enterprise-side front-end machine can insert multiple UKeys, when querying the running bills of different reconciling bank accounts, as long as all UKeys corresponding to each bank account are inserted into the enterprise-side front-end machine, no need to query An account has a flow of bills, a corresponding operation to insert a UKey, etc., and because all the UKeys corresponding to each bank are inserted into the enterprise front-end machine at one time, there is no need to worry about the problem of incorrect UKey insertion.
  • the process of sending a pipeline query task includes: after selecting a reconciliation bank account that needs to be reconciled in a list, and receiving a "start query" command to generate a reconciliation bank account for the selected reconciliation bank account
  • the pipeline query task is then sent to the enterprise-end front-end processor.
  • the pipeline query task is first sent to the application server corresponding to the enterprise-end front-end machine, and then the application server sends the application-side front-end machine.
  • the above application server refers to a third-party application server that provides an enterprise-side front-end processor to the enterprise. It serves as the management background of the enterprise-side front-end processor.
  • the tasks issued by the enterprise will first enter the above application server and then be sent by the application server to the enterprise. Front-end machine.
  • the forwarding unit 20 is configured to use the enterprise-end front-end machine to send the flow inquiry task for the reconciled bank account to the corresponding bank front-end machine, so as to query the corresponding flow-through bill to the bank server of the corresponding bank front-end machine. .
  • the foregoing enterprise-side front-end machine is connected to different bank front-end machines, after obtaining the pipeline query task, it will first analyze the information of the reconciliation bank account corresponding to the pipeline query task, etc.
  • the query task is correctly sent to the corresponding bank front-end machine.
  • the corresponding UKey information is also obtained to facilitate the bank's normal query of the flow account.
  • An inserting unit 30 configured to receive the current account statement of the reconciliation bank account obtained by the enterprise front-end processor from the bank front-end processor, and insert the current account statement into a preset reconciliation list,
  • the reconciliation list includes at least two parts, one of which is used to insert the running bill and the other is used to insert the enterprise journal of the enterprise.
  • the above reconciliation list is a form divided into two columns, one of which inserts the current account statement, and the other of which inserts the enterprise journal to facilitate manual checking by the accountant.
  • a blending unit 40 is configured to match the first record of the running account in the first part of the reconciliation list with the second record in the corporate journal in the second part, and match the matched first record and the second record Carry out automatic blending.
  • the current bill is matched with the first record and the second record in the corporate journal. If the matching is successful, the matching blending is performed, leaving the unmatched first record and the second record.
  • the above automatic blending is to eliminate the first and second records that match each other in the reconciliation list. In the automatic elimination process, they are eliminated in pairs, that is, eliminating a first record will necessarily eliminate a second record.
  • the above requirements for matching the first record and the second record are that the data corresponding to the specified field is the same.
  • the reconciliation staff will manually perform the blending and the manual blending. After that, if there are still the first record and the second record, it means that there are discrepancies in the corporate diary and current account, which need to be checked specifically.
  • the sending unit 10 includes:
  • a sending module 11 is configured to send a pipeline query task ID corresponding to the pipeline query task of the reconciling bank account to the enterprise-end front-end machine, wherein the enterprise-end front-end machine stores the pipeline query task ID in To the preset cache queue.
  • the above-mentioned pipeline query task ID is only an identifier, and the identifier uniquely corresponds to one of the pipeline query tasks.
  • the pipeline query task ID has no task content, so as to prevent the pipeline query task from being directly placed in front of the enterprise side. In the machine, it affects the running space of the front end of the enterprise, and reduces its running speed. Because the enterprise-end front-end unit of this application can be connected to multiple bank-side front-end units, there will be many different tasks, and directly stacking various tasks into the cache of the front-end unit will greatly reduce the enterprise-side front-end units. Set up the operating efficiency and even crash.
  • the preset cache queue generally includes a transaction cache queue and a query cache queue. Different cache queues store task IDs of corresponding attributes, and correspondingly set a transaction thread pool and a query thread pool.
  • the front end of the enterprise obtains the pipeline query task ID, it first determines the attributes of the pipeline query task ID.
  • the attributes include transaction attributes and query attributes. Because the pipeline query task ID belongs to the query class, it is placed in the query cache queue. in.
  • the tasks in the two cache queues are sorted according to priority. Each task will be set with a type identifier. The type identifier is divided into 1-8 levels. If it is 1, the highest level, which represents emergency tasks.
  • Priority processing can be based on presets. Pre-set rules, according to the specific request attached to the corresponding priority level, for example, the level of payment is higher than the level of query bank flow.
  • the receiving feedback module 12 is configured to receive a pipeline query task ID fed back by the enterprise-end front-end machine, acquire a corresponding pipeline query task according to the pipeline-query task ID, and send the pipeline query task to the enterprise-side front-end machine.
  • the pipeline query task ID fed back by the front end of the enterprise refers to that the query thread pool corresponding to the query cache queue is free, and the pipeline query task is obtained from the query cache queue.
  • the query cache queue is only the pipeline query task ID, so the enterprise side will return the pipeline query task ID to the above application server, and the application server will generate or call the corresponding task according to the pipeline query task ID, and then send it to the enterprise side. Set up.
  • the account reconciliation device further includes:
  • a judging unit 101 configured to judge whether a UKey device corresponding to various types of banks is inserted into the front end of the enterprise;
  • the first alarm unit 102 is configured to report an alarm if it is determined that UKey devices corresponding to various types of banks are not inserted into the front end of the enterprise.
  • the identifiers corresponding to the types of banks of the UKey devices inserted in each UKey interface are collected, and then the identifiers and the identifiers representing various types of banks configured when the enterprise-side front-end processor is configured are collected.
  • the collected logo fully covers the logos representing various types of banks configured when the enterprise-end front-end is configured, it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front-end, otherwise, The bank types corresponding to the uncovered identification are extracted and sent to the relevant personnel of the enterprise to report the alarm.
  • the relevant personnel of the enterprise can take corresponding measures to forget the inserted UKey device or the insertion place is loose and the UKey device is contacted. Bad reinsertion, etc. to ensure the interaction between the business and the banks.
  • the above-mentioned insertion unit 30 includes:
  • An obtaining module 31 configured to obtain the running bill
  • An extraction module 32 configured to extract data from the running bill according to a preset field
  • the inserting module 33 is configured to insert the extracted data into the reconciliation list.
  • the above fields include necessary fields such as account information and amount, and then these data are extracted from the running bill and inserted into the reconciliation list.
  • the corporate journal is put into an excel form and then inserted into the reconciliation list. Because the mode and content of the flow statement of different banks are different, in order to facilitate management and accurate reconciliation, this application will extract the data corresponding to the fields required in the flow statement from the flow statement and insert it into the preset standard. In the reconciliation list, the same will be done for the corporate journal, etc.
  • the reconciliation device further includes:
  • connection detection unit is used to judge the connection status with the enterprise-end front-end processor; if the connection status is disconnected, an alarm message is issued.
  • connection detection unit in theory, the enterprise-side front-end machine and application server should be online for a long time, but because it is an electronic product, it will inevitably occur failures or upgrades. At this time, the enterprise-side front-end machine and application server may be disconnected. Connection, when the connection between the two fails, you need to send an alarm message to prevent the financial system on the enterprise side from obtaining a corresponding flow of bills in a timely manner after the reconciliation request is issued.
  • the front end of the enterprise and the application server detect the connection status of the two by using a heartbeat detection method.
  • the alarm information sent includes sending information such as emails to relevant personnel of the enterprise, and / or to relevant personnel of third parties who provide front-end machines of the enterprise side.
  • the sending module 11 includes:
  • a sending submodule is configured to send a pipeline query task ID corresponding to the pipeline query task of the reconciled bank account to the enterprise-end front-end processor through the BIO synchronous blocking mode.
  • the reconciliation device further includes:
  • a serialization unit is configured to serialize the pipeline query task sent by the application server to the enterprise-end front-end processor using Protocol Buffers.
  • the above-mentioned Protocol Buffers is a portable and efficient structured data storage format, which can be used to serialize or serialize structured data. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of task message encapsulation and transmission.
  • the enterprise-side front-end machine can perform bank-enterprise direct connection functions with multiple different types of banks; After inserting the corresponding UKey, you can use the corresponding bank account to query the flow of bills, and in the case of flow query of multiple different bank accounts, you can directly operate without switching logins, etc. After obtaining the flow of bills , It is inserted into the preset reconciliation list to automatically match with the corporate journal, thereby achieving the purpose of automatic reconciliation, greatly saving the workload of the reconciliation staff, and improving the efficiency of reconciliation.
  • an embodiment of the present application further provides a computer device.
  • the computer device may be a server, and its internal structure may be as shown in FIG.
  • the computer device includes a processor, a memory, a network interface, and a database connected through a system bus.
  • the computer design processor is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system, computer-readable instructions, and a database.
  • the memory provides an environment for operating systems and computer-readable instructions in a non-volatile storage medium.
  • the database of the computer equipment is used for storing reconciliation method programs and the like.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection.
  • the computer-readable instructions are executed by a processor to implement the reconciliation method of any one of the above embodiments.
  • An embodiment of the present application further provides a computer non-volatile readable storage medium having computer readable instructions stored thereon.
  • the computer readable instructions are executed by a processor, the reconciliation method of any one of the foregoing embodiments is implemented.
  • Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual-speed data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种对账方法、装置、计算机设备和存储介质，企业端前置机设置多个UKey接口，并进行相应的配置，企业端前置机能够与多个不同种类的银行进行银企直联功能；插入对应的UKey，就可以使用对应的银行账户进行流水账单的查询，获取到流水账单，将该流水账单插入到预设的对账列表中与企业日记账进行自动匹配勾兑，提高对账的效率。

Description

对账方法、装置、计算机设备和存储介质
本申请要求于2018年7月2日提交中国专利局、申请号为2018107078700，申请名称为“对账方法、装置、计算机设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及到计算机领域，特别是涉及到一种对账方法、装置、计算机设备和存储介质。
 背景技术
传统的企业对账是从银行下载流水账单到本地，然后与企业的手动记账进行对比，非常消耗人力和时间，并且容易出错。
 技术问题
本申请的主要目的为提供一种企业快速进行对账的对账方法、装置、计算机设备和存储介质。
 技术解决方案
为了实现上述发明目的，本申请提出一种对账方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账；
将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，将匹配的第一记录和第二记录进行自动勾兑。
本申请还提供一种对账装置，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述装置，包括：
发送单元，用于向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
转发单元，用于利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
插入单元，用于接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账。
勾兑单元，用于将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，并将匹配的第一记录和第二记录进行自动勾兑。
本申请还提供一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，所述处理器执行所述计算机可读指令时实现上述任一项所述方法的步骤。
本申请还提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现上述任一项所述的方法的步骤。
 有益效果
本申请的对账方法、装置、计算机设备和存储介质，因为企业端前置机上设置了多个UKey接口，并进行相应的配置，所以企业端前置机能够与多个不同种类的银行进行银企直联功能；当插入对应的UKey之后，既可以使用对应的银行账户进行流水账单的查询，而且在多个不同的银行账户进行流水查询的情况下，无需切换登录等，可以直接进行操作，当获取到流水账单之后，将其插入到预设的对账列表中与企业日记账进行自动匹配勾兑，进而实现自动对账的目的，大大地节约了对账人员的工作量，以及提高对账的效率。
 附图说明
图1 为本申请一实施例的对账方法的流程示意图；
图2 为本申请一实施例的上述对账方法的步骤S1的流程示意图；
图3 为本申请一实施例的上述对账方法的步骤S3的流程示意图；
图4 为本申请一实施例的对账装置的结构示意框图；
图5 为本申请一实施例的发送单元的结构示意框图；
图6 为本申请一实施例的对账装置的结构示意框图；
图7 为本申请一实施例的插入单元的结构示意框图；
图8 为本申请一实施例的计算机设备的结构示意框图。
 本发明的最佳实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
参照图1，本申请实施例提供一种对账方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互。
上述的企业端前置机是指设置在企业端的前置机，是企业端财务系统与银行端进行银企直联时的中间设备。上述企业端前置机被配置为可以与多个不同银行种类的银行端前置机完成数据交互，配置过程为，当企业安装企业端前置机时，企业端前置机有一个管理员界面，在预设的界面内输入指定的配置信息，该配置信息包括企业ID、企业端前置机编号、银行服务器IP、银行端口、银行的银企直联编号、银行端前置机的版本号，银行大类等企业财务系统与银行完成银企直联的必要参数，还会配置线程数大小配置等，以实现多线程任务的处理；然后将配置结果发送给企业端前置机对应的应用服务器。也就是，配置申请通过的银企直联的账号及其相关信息，当企业需要登录各银企直联的账户获取在其对应银行的数据时（交易数据、查询数据等），只需要在企业端前置机上插入对应的UKey（一种通过USB直接与计算机相连、具有密码验证功能、可靠高速的小型存储设备）即可，实现一个企业端前置机与多个不同类银行的银行端前置机连接，企业统一集中管理用户的银行UKey，无需做银行的切换操作。通过企业端前置机可以方便地获取企业的每个银企直联账户的账户信息、交易流水信息、余额信息，并且可以进行相关的支付、归集、调拨等相关操作。上述银行大类是指不同的银行，比如工商银行与建设银行属于两个不同的银行大类等，即使用不同前置机的银行被认为是不同的银行大类。
上述方法，包括步骤：
S1、向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务。
在上述步骤S1中，上述流水查询任务即为获取指定的对账银行账户的流水账单的任务。能用到企业端前置的企业都会设置有多个不同的银行账户，这些银行账户分布于不同的银行大类。因为上述企业端前置机可以插入多个UKey，那么在查询不同的对账银行账户的流水账单时，只要提前将各银行账户对应的UKey全部插入到企业端前置机上即可，无需每查询一个账户流水账单，对应的插入一个UKey的操作等，又因为是一次性将各银行对应的UKey全部插入到企业端前置机上，则无需担心UKey插错的问题。在本实施例中，发送流水查询任务的过程包括：在一个列表中选择需要查询对账的对账银行账户后，接收一个“开始查询”的命令即可生成针对被选择的对账银行账户的流水查询任务，然后将流水查询任务发送给企业端前置机。本申请中，流水查询任务是先发送给企业端前置机对应的应用服务器，然后由应用服务器发送给所述企业端前置机。上述应用服务器是指给企业提供企业端前置机的第三方的应用服务器，其作为企业端前置机的管理后台，企业发布的任务会先进入到上述应用服务器，然后由应用服务器发送给企业端前置机。
S2、利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单。
在上述步骤S2中，因为上述企业端前置机连接有不同的银行前置机，获取到流水查询任务后，会先分析流水查询任务对应的对账银行账户的信息等，以便于将流水查询任务正确地发送给对应的银行前置机，在发送给对应的银行前置机流水查询任务的时候，还会获取对应的UKey信息，以便于银行端正常的查询流水账单。
S3、接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账。
在上述步骤S3中，上述的对账列表是一种表格，分为两大列，一大列内插入流水账单，另一大列内插入企业日记账，方便对账人员进行人工查看。
S4、将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，将匹配的第一记录和第二记录进行自动勾兑。
在上述步骤S4中，即为将流水账单与企业日记账中的第一记录和第二记录进行匹配，如果匹配成功，则将匹配的勾兑，留下未匹配成功的第一记录和第二记录。上述自动勾兑即为将对账列表内的相互匹配的第一记录和第二记录消除，在自动消除过程中均为成对消除，即消除一个第一记录，必然会消除一个第二记录。上述第一记录和第二记录匹配的要求即为指定的字段对应的数据相同。
在一个具体实施例中，当将匹配的第一记录和第二记录进行自动勾兑之后，如果对账列表中还保留有第一记录和第二记录，则由对账人员进行手动勾兑，手动勾兑之后，如果还保留有第一记录和第二记录，则说明企业日记账和流水账单存在出入，需要具体核查。
参照图2，在一个实施例中，上述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤S1，包括：
S11、向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中。
在上述步骤S11中，上述的流水查询任务ID只是一个标识，该标识唯一对应一个所述流水查询任务，流水查询任务ID并没有任务内容，以防止将流水查询任务直接放到企业端前置机中，影响企业端前置机的运行空间，而降低其运行速度。因为本申请的企业端前置机可以连接多个银行端前置机，所以各种不同的任务会较多，直接将各种任务堆积到前置机的缓存中，会大大地降低企业端前置机的运行效率，甚至崩溃。本申请中，只放入流水查询任务ID，则大大地降低了企业端前置机的缓存空间的要求，提高运行环境质量。本实施例中，预设的缓存队列一般包括交易缓存队列和查询缓存队列，不同的缓存队列存放对应属性的任务ID，对应的设置交易线程池和查询线程池。企业端前置机在获取到流水查询任务ID时，先判断所述流水查询任务ID的属性，其中属性包括交易属性、查询属性，因为流水查询任务ID属于查询类，则放入到查询缓存队列中。两个缓存队列中的任务按优先级进行排序，每个任务会设置有一个类型标识，类型标识分为1-8个级别，为1的话等级最高，代表紧急任务，优先处理，可以根据预设预设规则，根据具体请求附加对应的优先级别，比如，支付的级别高于查询银行流水的级别等。
S12、接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
在上述步骤S12中，上述企业端前置机反馈的流水查询任务ID是指，对应上述查询缓存队列的查询线程池中有空闲，则到查询缓存队列中获取流水查询任务，又因为此时查询缓存队列中只是流水查询任务ID，所以企业端前置机会将流水查询任务ID返回给上述应用服务器，应用服务器会根据流水查询任务ID生成或调取对应的任务，然后发送给企业端前置机。
在一个实施例中，上述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤S1之前，包括：
S101、判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
S102、若否，则报警。
在上述步骤S101和S102中，采集各UKey接口插入的UKey设备的对应其银行种类的标识，然后将所述标识与配置企业端前置机时配置的代表各类银行的标识进行比对，如果采集到的各标识全面覆盖配置企业端前置机时配置的代表各类银行的标识时，则判定企业端前置机上插入各对应各种类银行的UKey设备，可以执行后续如步骤S1等步骤，否者，将未被覆盖的标识对应的银行种类提取出来，并发送给企业的相关人员以报警，此时企业的相关人员可以进行相应的处理，将忘记插入的UKey设备或插入处松动而导致UKey设备接触不良的重新插入等，以保证企业与各银行之间的交互。本申请中，还可以判断获取到的UKey设备的标识与配置企业端前置机时配置的代表各类银行的标识（不重复）的数量是否相同，因为一个银行只会发一个UKey给企业，所以当数量相同时候，基本可以判定企业端前置机上插入对应各种类银行的UKey设备，此种判断方法虽然存在缺陷，但是判断速度会更快。
参照图3，在一个实施例中，上述接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中的步骤S3，包括：
S31、获取到所述流水账单；
S32、按照预设的字段从所述流水账单中抽取数据；
S33、将抽取出的数据插入到所述对账列表中。
在上述步骤S31-S33中，上述字段包括账户信息、金额等必须的字段，然后将这些数据从流水账单中抽取出来，插入到对账列表中。同样的，企业日记账是放入到一个excel表格中，然后插入到对账刘表中。因为不同的银行的流水账单的模式和内容存在一定的差别，为了便于管理和对账准确，本申请会对流水账单中需要的字段对应的数据从流水账单中抽取出来，插入到预设的标准的对账列表中。同理，也会对企业日记账进行同样的处理等，
在一个实施例中，上述对账方法还包括：
判断与企业端前置机的连接状态；若连接状态为断开，则发出警报信息。
在本步骤中，理论上，企业端前置机和应用服务器应该长期在线，但是因为是电子产品，难免会出现故障或者升级等处理，此时企业端前置机与应用服务器可能断掉连接，当两者连接失败，则需要发出警报信息，以防止企业端的财务系统发出对账请求后，无法及时获取对应的流水账单等。本申请中，企业端前置机和应用服务器通过心跳检测的方式检测两者的连接状态。发出的警报信息包括，发送邮件等信息给企业的相关人员，和/或发送给提供企业端前置机的第三方的相关人员等。
在一个实施例中，上述向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID的步骤S11，包括：
S111、通过BIO同步阻塞模式向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID。
在上述步骤S111中，针对不同的查询任务或交易任务不能够同时进行，所以需要按照指令顺序进行，一个指令执行完才能执行下一个指令，不能异步执行，所以本申请中采用BIO同步阻塞模式向所述企业端前置机发送支付任务。
在一个实施例中，上述对账方法还包括：
通过应用服务器向所述企业端前置机发送的流水查询任务时，采用Protocol Buffers进行序列化。
Protocol Buffers 是一种轻便高效的结构化数据存储格式，可以用于结构化数据串行化，或者说序列化。它很适合做数据存储或 RPC 数据交换格式。可用于通讯协议、数据存储等领域的语言无关、平台无关、可扩展的序列化结构数据格式，简单说来 Protobuf 的主要优点就是：简单，快。本申请采用GOOGLE的Protocol Buffers进行序列化，可以提高任务报文封装和发送的效率。
本申请实施例的对账方法，因为企业端前置机上设置了多个UKey接口，并进行相应的配置，所以企业端前置机能够与多个不同种类的银行进行银企直联功能；当插入对应的UKey之后，既可以使用对应的银行账户进行流水账单的查询，而且在多个不同的银行账户进行流水查询的情况下，无需切换登录等，可以直接进行操作，当获取到流水账单之后，将其插入到预设的对账列表中与企业日记账进行自动匹配勾兑，进而实现自动对账的目的，大大地节约了对账人员的工作量，以及提高对账的效率。
参照图4，本申请实施例还提供一种对账装置，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互。
上述的企业端前置机是指设置在企业端的前置机，是企业端财务系统与银行端进行银企直联时的中间设备。上述企业端前置机被配置为可以与多个不同银行种类的银行端前置机完成数据交互，配置过程为，当企业安装企业端前置机时，企业端前置机有一个管理员界面，在预设的界面内输入指定的配置信息，该配置信息包括企业ID、企业端前置机编号、银行服务器IP、银行端口、银行的银企直联编号、银行端前置机的版本号，银行大类等企业财务系统与银行完成银企直联的必要参数，还会配置线程数大小配置等，以实现多线程任务的处理；然后将配置结果发送给企业端前置机对应的应用服务器。也就是，配置申请通过的银企直联的账号及其相关信息，当企业需要登录各银企直联的账户获取在其对应银行的数据时（交易数据、查询数据等），只需要在企业端前置机上插入对应的UKey（一种通过USB直接与计算机相连、具有密码验证功能、可靠高速的小型存储设备）即可，实现一个企业端前置机与多个不同类银行的银行端前置机连接，企业统一集中管理用户的银行UKey，无需做银行的切换操作。通过企业端前置机可以方便地获取企业的每个银企直联账户的账户信息、交易流水信息、余额信息，并且可以进行相关的支付、归集、调拨等相关操作。上述银行大类是指不同的银行，比如工商银行与建设银行属于两个不同的银行大类等，即使用不同前置机的银行被认为是不同的银行大类。所述装置，包括：
发送单元10，用于向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务。
在上述发送单元10中，上述流水查询任务即为获取指定的对账银行账户的流水账单的任务。能用到企业端前置的企业都会设置有多个不同的银行账户，这些银行账户分布于不同的银行大类。因为上述企业端前置机可以插入多个UKey，那么在查询不同的对账银行账户的流水账单时，只要提前将各银行账户对应的UKey全部插入到企业端前置机上即可，无需每查询一个账户流水账单，对应的插入一个UKey的操作等，又因为是一次性将各银行对应的UKey全部插入到企业端前置机上，则无需担心UKey插错的问题。在本实施例中，发送流水查询任务的过程包括：在一个列表中选择需要查询对账的对账银行账户后，接收一个“开始查询”的命令即可生成针对被选择的对账银行账户的流水查询任务，然后将流水查询任务发送给企业端前置机。本申请中，流水查询任务是先发送给企业端前置机对应的应用服务器，然后由应用服务器发送给所述企业端前置机。上述应用服务器是指给企业提供企业端前置机的第三方的应用服务器，其作为企业端前置机的管理后台，企业发布的任务会先进入到上述应用服务器，然后由应用服务器发送给企业端前置机。
转发单元20，用于利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单。
在上述转发单元20中，因为上述企业端前置机连接有不同的银行前置机，获取到流水查询任务后，会先分析流水查询任务对应的对账银行账户的信息等，以便于将流水查询任务正确地发送给对应的银行前置机，在发送给对应的银行前置机流水查询任务的时候，还会获取对应的UKey信息，以便于银行端正常的查询流水账单。
插入单元30，用于接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账。
在上述插入单元30中，上述的对账列表是一种表格，分为两大列，一大列内插入流水账单，另一大列内插入企业日记账，方便对账人员进行人工查看。
勾兑单元40，用于将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，并将匹配的第一记录和第二记录进行自动勾兑。
在上述勾兑单元40中，将流水账单与企业日记账中的第一记录和第二记录进行匹配，如果匹配成功，则将匹配的勾兑，留下未匹配成功的第一记录和第二记录。上述自动勾兑即为将对账列表内的相互匹配的第一记录和第二记录消除，在自动消除过程中均为成对消除，即消除一个第一记录，必然会消除一个第二记录。上述第一记录和第二记录匹配的要求即为指定的字段对应的数据相同。
在一个具体实施例中，当将匹配的第一记录和第二记录进行自动勾兑之后，如果对账列表中还保留有第一记录和第二记录，则由对账人员进行手动勾兑，手动勾兑之后，如果还保留有第一记录和第二记录，则说明企业日记账和流水账单存在出入，需要具体核查。
参照图5，在一个实施例中，上述发送单元10，包括：
发送模块11，用于向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中。
在上述发送模块11中，上述的流水查询任务ID只是一个标识，该标识唯一对应一个所述流水查询任务，流水查询任务ID并没有任务内容，以防止将流水查询任务直接放到企业端前置机中，影响企业端前置机的运行空间，而降低其运行速度。因为本申请的企业端前置机可以连接多个银行端前置机，所以各种不同的任务会较多，直接将各种任务堆积到前置机的缓存中，会大大地降低企业端前置机的运行效率，甚至崩溃。本申请中，只放入流水查询任务ID，则大大地降低了企业端前置机的缓存空间的要求，提高运行环境质量。本实施例中，预设的缓存队列一般包括交易缓存队列和查询缓存队列，不同的缓存队列存放对应属性的任务ID，对应的设置交易线程池和查询线程池。企业端前置机在获取到流水查询任务ID时，先判断所述流水查询任务ID的属性，其中属性包括交易属性、查询属性，因为流水查询任务ID属于查询类，则放入到查询缓存队列中。两个缓存队列中的任务按优先级进行排序，每个任务会设置有一个类型标识，类型标识分为1-8个级别，为1的话等级最高，代表紧急任务，优先处理，可以根据预设预设规则，根据具体请求附加对应的优先级别，比如，支付的级别高于查询银行流水的级别等。
接收反馈模块12，用于接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
在上述接收反馈模块12中，上述企业端前置机反馈的流水查询任务ID是指，对应上述查询缓存队列的查询线程池中有空闲，则到查询缓存队列中获取流水查询任务，又因为此时查询缓存队列中只是流水查询任务ID，所以企业端前置机会将流水查询任务ID返回给上述应用服务器，应用服务器会根据流水查询任务ID生成或调取对应的任务，然后发送给企业端前置机。
参照图6，在一个实施例中，上述对账装置还包括：
判断单元101，用于判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
第一报警单元102，用于若判定所述企业端前置机上未插入对应各种类银行的UKey设备，则报警。
在上述判断单元101和第一报警单元102中，采集各UKey接口插入的UKey设备的对应其银行种类的标识，然后将所述标识与配置企业端前置机时配置的代表各类银行的标识进行比对，如果采集到的各标识全面覆盖配置企业端前置机时配置的代表各类银行的标识时，则判定企业端前置机上插入各对应各种类银行的UKey设备，否者，将未被覆盖的标识对应的银行种类提取出来，并发送给企业的相关人员以报警，此时企业的相关人员可以进行相应的处理，将忘记插入的UKey设备或插入处松动而导致UKey设备接触不良的重新插入等，以保证企业与各银行之间的交互。本申请中，还可以判断获取到的UKey设备的标识与配置企业端前置机时配置的代表各类银行的标识（不重复）的数量是否相同，因为一个银行只会发一个UKey给企业，所以当数量相同时候，基本可以判定企业端前置机上插入对应各种类银行的UKey设备，此种判断方法虽然存在缺陷，但是判断速度会更快。
参照图7，在一个实施例中，上述插入单元30，包括：
获取模块31，用于获取到所述流水账单；
抽取模块32，用于按照预设的字段从所述流水账单中抽取数据；
插入模块33，用于将抽取出的数据插入到所述对账列表中。
在上述获取模块31、抽取模块32和插入模块33中，上述字段包括账户信息、金额等必须的字段，然后将这些数据从流水账单中抽取出来，插入到对账列表中。同样的，企业日记账是放入到一个excel表格中，然后插入到对账刘表中。因为不同的银行的流水账单的模式和内容存在一定的差别，为了便于管理和对账准确，本申请会对流水账单中需要的字段对应的数据从流水账单中抽取出来，插入到预设的标准的对账列表中，同理，也会对企业日记账进行同样的处理等，
在一个实施例中，上述对账装置还包括：
连接检测单元，用于判断与企业端前置机的连接状态；若连接状态为断开，则发出警报信息。
在上述连接检测单元中，理论上，企业端前置机和应用服务器应该长期在线，但是因为是电子产品，难免会出现故障或者升级等处理，此时企业端前置机与应用服务器可能断掉连接，当两者连接失败，则需要发出警报信息，以防止企业端的财务系统发出对账请求后，无法及时获取对应的流水账单等。本申请中，企业端前置机和应用服务器通过心跳检测的方式检测两者的连接状态。发出的警报信息包括，发送邮件等信息给企业的相关人员，和/或发送给提供企业端前置机的第三方的相关人员等。
在一个实施例中，上述发送模块11，包括：
发送子模块，用于通过BIO同步阻塞模式向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID。
在上述发送子模块中，针对不同的查询任务或交易任务不能够同时进行，所以需要按照指令顺序进行，一个指令执行完才能执行下一个指令，不能异步执行，所以本申请中采用BIO同步阻塞模式向所述企业端前置机发送支付任务。
在一个实施例中，上述对账装置还包括：
序列化单元，用于将通过应用服务器向所述企业端前置机发送的流水查询任务，采用Protocol Buffers进行序列化。
在上述序列化单元中，上述Protocol Buffers 是一种轻便高效的结构化数据存储格式，可以用于结构化数据串行化，或者说序列化。它很适合做数据存储或 RPC 数据交换格式。可用于通讯协议、数据存储等领域的语言无关、平台无关、可扩展的序列化结构数据格式，简单说来 Protobuf 的主要优点就是：简单，快。本申请采用GOOGLE的Protocol Buffers进行序列化，可以提高任务报文封装和发送的效率。
本申请实施例的对账装置，因为企业端前置机上设置了多个UKey接口，并进行相应的配置，所以企业端前置机能够与多个不同种类的银行进行银企直联功能；当插入对应的UKey之后，既可以使用对应的银行账户进行流水账单的查询，而且在多个不同的银行账户进行流水查询的情况下，无需切换登录等，可以直接进行操作，当获取到流水账单之后，将其插入到预设的对账列表中与企业日记账进行自动匹配勾兑，进而实现自动对账的目的，大大地节约了对账人员的工作量，以及提高对账的效率。
参照图8，本申请实施例中还提供一种计算机设备，该计算机设备可以是服务器，其内部结构可以如图8所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设计的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机可读指令和数据库。该内存器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的数据库用于存储对账方法程序等。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现上述任一实施例的对账方法。
本申请一实施例还提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，计算机可读指令被处理器执行时实现上述任一实施例的对账方法。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的和实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可以包括只读存储器（ROM）、可编程ROM（PROM）、电可编程ROM（EPROM）、电可擦除可编程ROM（EEPROM）或闪存。易失性存储器可包括随机存取存储器（RAM）或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM（SRAM）、动态RAM（DRAM）、同步DRAM（SDRAM）、双速据率SDRAM（SSRSDRAM）、增强型SDRAM（ESDRAM）、同步链路（Synchlink）DRAM（SLDRAM）、存储器总线（Rambus）直接RAM（RDRAM）、直接存储器总线动态RAM（DRDRAM）、以及存储器总线动态RAM（RDRAM）等。
以上所述仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种对账方法，其特征在于，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
    利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
    接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账；
    将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，将匹配的第一记录和第二记录进行自动勾兑。
  2. 根据权利要求1所述的对账方法，其特征在于，所述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤，包括：
    向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中；
    接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
  3. 根据权利要求1所述的对账方法，其特征在于，所述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤之前，包括：
    判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    若否，则报警。
  4. 根据权利要求1所述的对账方法，其特征在于，所述接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中的步骤，包括：
    获取到所述流水账单；
    按照预设的字段从所述流水账单中抽取数据；
    将抽取出的数据插入到所述对账列表中。
  5. 根据权利要求1所述的对账方法，其特征在于，所述方法还包括：
    判断与企业端前置机的连接状态；
    若连接状态为断开，则发出警报信息。
  6. 根据权利要求1所述的对账方法，其特征在于，所述向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID的步骤，包括：
    通过BIO同步阻塞模式向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID。
  7. 根据权利要求1所述的对账方法，其特征在于，所述方法还包括：
    通过应用服务器向所述企业端前置机发送的流水查询任务时，采用Protocol Buffers进行序列化。
  8. 一种对账装置，其特征在于，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述装置，包括：
    发送单元，用于向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
    转发单元，用于利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
    插入单元，用于接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账。
    勾兑单元，用于将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，并将匹配的第一记录和第二记录进行自动勾兑。
  9. 根据权利要求8所述的对账装置，其特征在于，所述发送单元，包括：
    发送模块，用于向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中；
    接收反馈模块，用于接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
  10. 根据权利要求8所述的对账装置，其特征在于，所述对账装置还包括：
    判断单元，用于判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    第一报警单元，用于若判定所述企业端前置机上未插入对应各种类银行的UKey设备，则报警。
  11. 根据权利要求8所述的对账装置，其特征在于，所述插入单元，包括：
    获取模块，用于获取到所述流水账单；
    抽取模块，用于按照预设的字段从所述流水账单中抽取数据；
    插入模块，用于将抽取出的数据插入到所述对账列表中。
  12. 根据权利要求8所述的对账装置，其特征在于，所述对账装置还包括：
    连接检测单元，用于判断与企业端前置机的连接状态，若连接状态为断开，则发出警报信息。
  13. 根据权利要求8所述的对账装置，其特征在于，所述发送模块，包括：
    发送子模块，用于通过BIO同步阻塞模式向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID。
  14. 根据权利要求8所述的对账装置，其特征在于，所述对账装置还包括：
    序列化单元，用于将通过应用服务器向所述企业端前置机发送的流水查询任务，采用Protocol Buffers进行序列化。
  15. 一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现对账方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
    利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
    接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账；
    将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，将匹配的第一记录和第二记录进行自动勾兑。
  16. 根据权利要求15所述的计算机设备，其特征在于，所述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤，包括：
    向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中；
    接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
  17. 根据权利要求15所述的计算机设备，其特征在于，所述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤之前，包括：
    判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    若否，则报警。
  18. 根据权利要求15所述的计算机设备，其特征在于，所述接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中的步骤，包括：
    获取到所述流水账单；
    按照预设的字段从所述流水账单中抽取数据；
    将抽取出的数据插入到所述对账列表中。
  19. 一种计算机非易失性可读存储介质，其上存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现对账方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务；
    利用所述企业端前置机将针对所述对账银行账户的流水查询任务发送给对应的银行前置机，以到对应银行前置机的银行服务器查询对应的流水账单；
    接收所述企业端前置机从所述银行前置机获取到的所述对账银行账户的流水账单，并将所述流水账单插入到预设的对账列表中，其中，所述对账列表至少包括两部分，其中一部分用于插入所述流水账单，另一用于插入企业端的企业日记账；
    将所述对账列表的第一部分内的流水账单的第一记录和第二部分内的企业日记账中的第二记录进行匹配，将匹配的第一记录和第二记录进行自动勾兑。
  20. 根据权利要求19所述的计算机非易失性可读存储介质，其特征在于，所述向所述企业端前置机发送待对账的对账银行账户对应的流水查询任务的步骤，包括：
    向所述企业端前置机发送所述对账银行账户的流水查询任务对应的流水查询任务ID，其中，所述企业端前置机将所述流水查询任务ID存入到预设的缓存队列中；
    接收所述企业端前置机反馈的流水查询任务ID，根据所述流水查询任务ID获取对应的流水查询任务，并发给所述企业端前置机。
PCT/CN2018/108028 2018-07-02 2018-09-27 对账方法、装置、计算机设备和存储介质 WO2020006895A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810707870.0A CN109166026B (zh) 2018-07-02 2018-07-02 对账方法、装置、计算机设备和存储介质
CN201810707870.0 2018-07-02

Publications (1)

Publication Number Publication Date
WO2020006895A1 true WO2020006895A1 (zh) 2020-01-09

Family

ID=64897523

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/108028 WO2020006895A1 (zh) 2018-07-02 2018-09-27 对账方法、装置、计算机设备和存储介质

Country Status (2)

Country Link
CN (1) CN109166026B (zh)
WO (1) WO2020006895A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112581296A (zh) * 2020-12-16 2021-03-30 中国建设银行股份有限公司 银行代理保险系统账务一致性处理方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109978544B (zh) * 2019-04-03 2021-07-23 国网山东省电力公司 基于大数据技术的企业密钥管控及智能化分析方法及系统
CN111178881A (zh) * 2019-12-13 2020-05-19 远光软件股份有限公司 关联财务凭证和银行回单的方法和装置
CN113689271A (zh) * 2020-05-18 2021-11-23 深圳兆日科技股份有限公司 企业与银行间对账方法、装置、设备和存储介质
CN112529697A (zh) * 2020-12-25 2021-03-19 北京来也网络科技有限公司 结合rpa和ai的银行流水处理方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1681260A (zh) * 2004-06-30 2005-10-12 中国银行股份有限公司 用于企业和银行之间业务对接的处理系统
CN201315082Y (zh) * 2008-12-18 2009-09-23 北京华电方胜软件技术有限公司 银企联网收费系统
CN101706934A (zh) * 2009-12-01 2010-05-12 中国建设银行股份有限公司 汽车金融银行业务处理的方法及系统
CN103679960A (zh) * 2012-09-06 2014-03-26 联多科技（北京）有限公司 现金通统一金融平台

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105630614B (zh) * 2015-12-22 2019-01-11 世纪龙信息网络有限责任公司 批处理任务处理系统和方法
CN106127567A (zh) * 2016-06-21 2016-11-16 国家电网公司 企业存款日记账和银行存款对账单的对账方法和系统
CN107516204A (zh) * 2017-08-31 2017-12-26 四川长虹电器股份有限公司 互联网银企对接系统及对接方法
CN107944996A (zh) * 2017-10-17 2018-04-20 九派天下支付有限公司 一种资金对账方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1681260A (zh) * 2004-06-30 2005-10-12 中国银行股份有限公司 用于企业和银行之间业务对接的处理系统
CN201315082Y (zh) * 2008-12-18 2009-09-23 北京华电方胜软件技术有限公司 银企联网收费系统
CN101706934A (zh) * 2009-12-01 2010-05-12 中国建设银行股份有限公司 汽车金融银行业务处理的方法及系统
CN103679960A (zh) * 2012-09-06 2014-03-26 联多科技（北京）有限公司 现金通统一金融平台

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112581296A (zh) * 2020-12-16 2021-03-30 中国建设银行股份有限公司 银行代理保险系统账务一致性处理方法及装置

Also Published As

Publication number Publication date
CN109166026B (zh) 2024-01-02
CN109166026A (zh) 2019-01-08

Similar Documents

Publication Publication Date Title
WO2020006895A1 (zh) 对账方法、装置、计算机设备和存储介质
EP3864817B1 (en) Blockchain timestamp agreement
CN110458559B (zh) 交易数据处理方法、装置、服务器和存储介质
CN107833124A (zh) 基于财务总账数据的财务分析系统及实现方法
WO2020006903A1 (zh) 财务数据交互方法、装置、计算机设备和存储介质
WO2020000720A1 (zh) 服务器、报文处理方法、程序和计算机可读存储介质
CN107133231B (zh) 一种数据获取方法和装置
US20140089156A1 (en) Addresses in financial systems
WO2019019447A1 (zh) 年金数据处理方法、装置、服务器和存储介质
CN110063042B (zh) 一种数据库故障的响应方法及其终端
CN112232818A (zh) 数据对账方法、装置、计算机设备和存储介质
CN109165935A (zh) 批量支付方法、装置、计算机设备和存储介质
WO2020006893A1 (zh) 回单获取方法、装置、计算机设备和存储介质
WO2020006896A1 (zh) 余额监控方法、装置、计算机设备和存储介质
CN107483477B (zh) 账户管理方法及账户管理系统
CN112965986B (zh) 业务一致性处理方法、装置、设备及存储介质
WO2020006901A1 (zh) 资金归集方法、装置、计算机设备和存储介质
US12020246B2 (en) Intelligent distributed ledger consent optimizing apparatus for asset transfer
WO2020006904A1 (zh) 财务调拨方法、装置、计算机设备和存储介质
US10216830B2 (en) Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine
CN115242478B (zh) 一种提升数据安全的方法、装置、电子设备及存储介质
US11625698B2 (en) Intelligent distributed ledger consent optimizing apparatus for asset transfer
CN111582851B (zh) 基于大数据的平台打款方法、装置、电子设备及存储介质
CN111161048B (zh) 一种资金归集自动过账的应用方法及装置
CN114900569B (zh) 一种测试脚本的获取方法及装置

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: 18925181

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: 18925181

Country of ref document: EP

Kind code of ref document: A1