CN115239448A

CN115239448A - Account checking management method and account checking management device

Info

Publication number: CN115239448A
Application number: CN202210894023.6A
Authority: CN
Inventors: 吴涛昌
Original assignee: Beijing Hesi Information Technology Co Ltd
Current assignee: Beijing Hesi Information Technology Co Ltd
Priority date: 2022-07-27
Filing date: 2022-07-27
Publication date: 2022-10-25

Abstract

The application discloses a reconciliation management method and a reconciliation management device, and belongs to the field of financial management. The account checking management method comprises the steps of receiving a first input at a first client, responding to the first input, creating bill information, and sending the bill information to a second client; receiving a second input at the second client, in response to which the billing information is checked; and generating a settlement list under the condition that the checking result is correct, and settling accounts according to the settlement list. The account checking management method greatly improves convenience and accuracy of account checking, and is beneficial to improving production and management efficiency of enterprises.

Description

Account checking management method and account checking management device

Technical Field

The application belongs to the field of financial management, and particularly relates to a reconciliation management method and a reconciliation management device.

Background

The financial reconciliation work is an important link of the financial management work, and the quality of the reconciliation work is directly related to the operation quality of the production and operation activities. In order to prevent and resolve enterprise capital risks, reduce labor intensity and improve account checking efficiency and timeliness, an efficient account checking management mode is needed.

When the expense generated by the enterprise after the consumption of the supplier needs to be checked, the current processing mode is that the supplier mails the bill to the enterprise manually, and the related responsible person of the enterprise needs to check the bill manually and then settle. Because the risk of bill loss exists in the mailing process and the mailing process is time-consuming, the related responsible persons of the enterprise need to manually sign and receive bills and then manually calculate and settle the bills, the whole process is time-consuming, the efficiency is low, and careless mistakes are easy to occur. Such a reconciliation method is not favorable for the high efficiency of production and operation.

Disclosure of Invention

An object of the embodiments of the present application is to provide an account checking management method and an account checking management apparatus, which can solve the technical problems that at present, the time consumption and the long efficiency of account checking are low, and careless mistakes are easy to occur.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, the present application provides a reconciliation management method, including:

receiving a first input at a first client;

in response to the first input, creating billing information and sending the billing information to a second client;

receiving a second input at the second client;

checking the billing information in response to the second input;

and generating a settlement list under the condition that the checking result is correct, and settling accounts according to the settlement list.

Further, the reconciliation management method further comprises the following steps:

and returning the bill information to the first client side under the condition that the checking result is wrong.

Further, the creating billing information in response to the first input and sending the billing information to the second client specifically includes:

creating billing information in response to the first input;

carrying out data uniqueness check and cost mapping check on the bill information;

and after the bill information passes through the data uniqueness check and the expense mapping check, sending the bill information to a second client.

Further, returning the billing information to the first client when the checking result is incorrect specifically includes:

under the condition that the checking result is wrong, the bill information is adjusted at the second client;

and sending the adjusted bill information to the first client.

Further, the first client is a client on the supplier side, and the second client is a client on the enterprise side.

In a second aspect, the present application provides a reconciliation management apparatus, comprising:

a first input module for receiving a first input at a first client;

the bill creating module is used for responding to the first input, creating bill information and sending the bill information to the second client;

a second input module for receiving a second input at the second client;

a bill checking module for checking the bill information in response to the second input;

and the settlement module is used for generating a settlement list under the condition that the checking result is correct, and settling accounts according to the settlement list.

Further, the reconciliation management device further comprises:

and the returning module is used for returning the bill information to the first client side under the condition that the checking result is wrong.

Further, the bill creation module includes:

a creating sub-module for creating billing information in response to the first input;

the checking submodule is used for carrying out data uniqueness checking and cost mapping checking on the bill information;

and the sending submodule is used for sending the bill information to a second client after the bill information passes through the data uniqueness check and the cost mapping check.

Further, the retraction module comprises:

the adjusting submodule is used for adjusting the bill information at the second client under the condition that the checking result is wrong;

and the return submodule is used for sending the adjusted bill information to the first client.

In an embodiment of the present application, an online reconciliation management method is provided in an embodiment of the present application, where a provider and an enterprise may manage billing information in the same online system, specifically, receive a first input at a first client, create billing information in response to the first input, and send the billing information to a second client; receiving a second input at the second client, in response to which the billing information is checked; and generating a settlement list under the condition that the checking result is correct, and settling accounts according to the settlement list. In the embodiment of the application, the bill generation and the bill accounting are performed on line, and the supplier and the enterprise can follow up the bill information in real time, so that the convenience and the accuracy of account checking are greatly improved, and the production and enterprise management efficiency is favorably improved.

Drawings

Fig. 1 is a schematic flowchart of a reconciliation management method provided in an embodiment of the present application;

fig. 2 is a schematic diagram of an account checking management apparatus according to an embodiment of the present application.

The implementation, functional features and advantages of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

First, the background of the field to which the present application relates is explained. In the enterprise operation, generally, a supplier provides raw materials and other goods to an enterprise for the production and operation of the enterprise, and after the production and operation of the enterprise for a certain period, account settlement is performed. This process involves reconciliation. The account checking is to check the account, and refers to checking and checking related data in the account book in the accounting calculation for ensuring the record of the account book to be correct and reliable.

The conventional account checking management is that a supplier generally provides a bill, the bill is explicitly recorded with information such as the quantity, unit price and accumulated payment of goods, the supplier sends the bill to an enterprise, an enterprise financial management department performs accounting according to the information recorded in the bill, and the bill is paid to an account of the supplier when the accounting determines that the bill information is correct. The process is very complicated, long in time consumption and not beneficial to improving the production and operation efficiency of enterprises. To solve the problem, the application provides a reconciliation management method and a reconciliation management device.

The reconciliation management method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings by specific embodiments and application scenarios thereof.

Example one

Referring to fig. 1, a schematic flow chart of a reconciliation management method provided in the embodiment of the present application is shown.

The application provides a reconciliation management method, which comprises the following steps:

s101: receiving a first input at a first client;

specifically, the first client is a client installed on the provider side. In the application, account checking management is performed on line, so account checking management software can be installed on both the supplier and the enterprise. It can be appreciated that because the supplier and the software have different requirements for the reconciliation management software, for example, the reconciliation management software on the supplier side needs to facilitate the bill information input of the supplier, and the reconciliation management software on the enterprise side needs to facilitate the reconciliation of the bill information of the enterprise, the display interfaces of the client sides on the supplier side and the enterprise side can be different so as to facilitate the respective operations.

In this step, the client installed on the supplier side receives the original bill information provided by the supplier.

It should be noted that before receiving the original billing information provided by the provider, the provider is required to establish an account for the corresponding enterprise, so as to implement one-to-one sharing of the billing information with the enterprise.

S102: in response to the first input, billing information is created and sent to a second client.

Different from the existing account checking mode, the existing account checking mode is carried out through a paper invoice; in the embodiment of the application, the bill is an electronic bill. The supplier inputs the electronic bill into the system after the input is made at the first client, and the system generates bill information according to the first input. The electronic bill can be input into the system in various ways, such as code scanning input or manual input, and the embodiment of the application is not limited. The account information specifically includes the name, type, quantity, unit price, supply date, and the like of the goods, and the recorded content of the account information needs to be detailed and clear so as to be convenient for the financial management personnel at the enterprise side to check.

After the bill information is created, data uniqueness check and cost mapping check need to be performed on the bill information.

The data uniqueness check is to avoid repeated information entry in the bill information, including that the target data cannot exceed a certain limit value and that the target data must be a certain limit value. The fact that the target data cannot exceed a certain limit value means that two pieces of identical shipment information cannot exist in the bill information, for example, the same goods of the same type and the same quantity processed by the same person at the same time cannot appear, which means that the shipment information is duplicated, which may cause errors in the bill information. The fact that the target data is required to be a certain limiting value means that the occurrence of the target data needs to meet a certain sequence, for example, the preposed warehousing needs to be warehoused before warehousing, and then warehousing is carried out on the preposed warehousing.

The data uniqueness check can be performed in various ways, for example, the data uniqueness check can be performed through screening of an excel conditional format, and the data uniqueness check can also be performed through programming, which is not limited herein, and the check mode can be selected according to specific requirements.

The expense mapping check refers to corresponding expense with a specific item. That is, each payment in the billing information should correspond to a specific entry. Through the expense mapping and checking, the excessive items generated in the expense can be avoided, and further the error of the bill information is caused. The cost mapping verification may also be performed in various manners, for example, the cost mapping verification may be performed through an excel mapping function, or the cost mapping verification may be performed through programming, which is not limited herein, and the verification manner may be selected according to specific requirements.

After the billing information passes the data uniqueness check and the cost mapping check, the billing information may be sent to the second client.

The second client is a client installed on the enterprise side, and the supplier sends the verified bill to the client on the enterprise side. Therefore, the time consumed by mailing the bill can be saved, and the bill processing efficiency is improved.

S103, receiving a second input at the second client;

after the supplier sends the verified bill to the client at the enterprise side, the enterprise accepts the bill information. At this time, the account checking management node arrives at the enterprise side, and at this time, the client side at the enterprise side receives user input so as to process account information.

S104: in response to the second input, the billing information is checked.

The bill checking includes account checking, account checking and real account checking. The account certificate checking means that whether the content, the quantity and the amount of each economic business in the original voucher, the bookkeeping voucher and the account book record are consistent or not and whether the accounting subject is correct or not are checked. According to the size of the traffic, the check can be performed one by one or can be performed by spot check. If an error is found, the initial basis should be checked step by step until the cause of the error is found.

The account checking generally includes the following methods: (1) checking the record of the general classification account for errors. A trial balance table can be compiled for checking, if the sum of the borrower and the lender is trial balanced, generally speaking, no error exists, and if the sum of the borrower and the lender is unbalanced, the bookkeeping is wrong, and further checking is needed; (2) Checking whether the record between the general classified account and the belonged detail classified account has errors, specifically, compiling the generation amount of the detail classified account and the balance detail list or the receiving and sending balance list of property materials to check with the general classified account, and if the record does not accord with the balance detail list or the receiving and sending balance list of the property materials, further searching the reason of the errors; or adding the current generation amount or the balance sum in each detail classification account, and directly checking with the corresponding number of the general classification account. This method can omit the above-mentioned list-making work.

The account and real check means that the balance of the account book record is matched with the real-deposit number check of each property and material, cash, bank deposit and various securities. The checking method is property checking. For fixed assets, materials, products, finished products, cash and the like, checking the real objects with the account number and judging whether the real objects are consistent with the account number.

This process may be done at the enterprise-side client. In this process, a plurality of reconciliation sub-bills may be generated. The reconciliation sub-bill is a bill obtained by splitting the reconciliation bill into a plurality of items, for example, splitting according to date, splitting according to goods category, or splitting according to a manager. The split sub-bills can be distributed to a plurality of persons for checking, namely, user input can be received at a plurality of second client sides, so that multi-person parallel bill checking can be realized, and checking efficiency is further improved. Meanwhile, error checking is convenient to carry out in the later period when errors exist in the checking.

And after the plurality of account checking sub-bills are checked, the plurality of account checking sub-bills are collected into a bill.

S105: and generating a settlement list under the condition that the checking result is correct, and settling accounts according to the settlement list.

It is understood that, in the case where the result of the check is correct, it indicates that both parties agree on the billing information, and thus the settlement statement can be generated. Generally, after the statement is generated, the statement may be sent to the financial department within the enterprise, and the financial department may make a payment based on the statement.

Because the whole account checking process is carried out on line, the time required by account checking is greatly shortened. Because the account transfer cycle is short, the fund transfer rate is high, on one hand, the cooperation compactness between a supplier and an enterprise can be improved, and on the other hand, the production and operation efficiency can also be improved.

It can be understood that, in the case that the checking result shows that the bill is wrong, the two parties are confused about the bill information.

In order to eliminate the divergence, one possible way is to return the billing information to the provider side, and the billing information is re-checked by the provider side (i.e. the first client) and then sent to the client (i.e. the second client) on the enterprise side;

another feasible mode is that the bill information is revised and adjusted and returned to the supplier side for secondary check, the bill information is sent to the enterprise side client side again after the supplier check, and the enterprise side client side performs settlement and payment after the bill information is checked to be correct. This approach is more efficient than the previous approach and makes it easier to perform communication processing at the point of divergence to achieve consistency more quickly.

Optionally, settlement software associated with the reconciliation management software can be created between the enterprise and the supplier, and after the reconciliation management is completed, finally determined bill information can be sent to the associated settlement software, so that the efficiency of reconciliation and settlement can be further improved by processing payment on the settlement software.

It can be understood that, in the embodiment of the present application, the provider side is the first client, and the enterprise side is the second client. That is, the supplier uploads and generates bill information, and sends the bill information to the enterprise side for bill checking, and the settlement and the payment are carried out after the check is correct. In the application, the enterprise side can be a first client, and the supplier side can be a second client. The enterprise side uploads the uploaded and generated bill information, the bill information is sent to the supplier side for bill checking, and settlement and payment are carried out after the check is correct. This is not limited by the present application.

In the embodiment of the application, the account checking management software is installed on the enterprise side and the supplier side, so that the supplier and the enterprise can manage the bill information in the same online system. The supplier inputs bill information, a bill is generated at the supplier side and is sent to the enterprise side client side, financial management personnel at the enterprise side can check and adjust the bill information on line, a settlement bill is generated according to the bill information after the bill information at the enterprise side and the supplier side are checked and determined, and the enterprise side performs settlement and payment according to the settlement bill. In the embodiment of the application, the bill generation and the bill accounting are performed on line, and the supplier and the enterprise can follow up the bill information in real time, so that the convenience and the accuracy of account checking are greatly improved, and the production and enterprise management efficiency is favorably improved.

Example two

Referring to fig. 2, a schematic structural diagram of a reconciliation management 20 provided in an embodiment of the present application is shown.

The reconciliation management device 20 includes:

a first input module 201 for receiving a first input at a first client;

the first client may be a client on the provider side.

A bill creation module 202, configured to create bill information in response to the first input, and send the bill information to a second client;

the second client may be a client on the enterprise side.

The bill creating module 202 includes:

a creating sub-module 2021 for creating billing information in response to the first input;

the checking submodule 2022 is configured to perform data uniqueness checking and cost mapping checking on the billing information;

the sending submodule 2023 is configured to send the billing information to the second client after the billing information passes through the data uniqueness check and the cost mapping check.

A second input module 203, configured to receive a second input at the second client;

a bill reconciliation module 204 for reconciling the bill information in response to the second input;

the settlement module 205 is configured to generate a settlement statement and perform account settlement according to the settlement statement if the checking result is correct;

a returning module 206, configured to return the billing information to the first client if the checking result is false.

Wherein, the return module 206 comprises:

an adjusting submodule 2061, configured to, if the checking result is an error, adjust the billing information at the second client;

and a return submodule 2062, configured to send the adjusted billing information to the first client.

The reconciliation management device 20 provided in the embodiment of the present application can implement each process implemented in the foregoing reconciliation method embodiment, and for avoiding repetition, details are not described here.

In the embodiment of the present application, by providing the first input module 201, the bill creation module 202, the second input module 203, the bill verification module 204, the settlement module 205, and the return module 206, the supplier and the enterprise can manage the bill information in the same online system. The supplier inputs bill information, a bill is generated at the supplier side and is sent to the enterprise side client side, financial management personnel at the enterprise side can check and adjust the bill information on line, a settlement bill is generated according to the bill information after the bill information at the enterprise side and the supplier side are checked and determined, and the enterprise side performs settlement and payment according to the settlement bill. Because the bill generation and the bill accounting are carried out on line and the suppliers and enterprises can follow up the bill information in real time, the convenience and the accuracy of account checking are greatly improved, and the production and enterprise management efficiency is improved.

The virtual device in the embodiment of the present application may be a device, and may also be a component, an integrated circuit, or a chip in a terminal.

The present invention may be methods, apparatus, systems and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therein for carrying out aspects of the present invention.

The computer-readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present invention may be assembler instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It is noted that, unless expressly stated otherwise, all features disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. Where used, further, preferably, still further and more preferably is a brief introduction to the description of the other embodiment based on the foregoing embodiment, the combination of the contents of the further, preferably, still further or more preferably back strap with the foregoing embodiment being a complete construction of the other embodiment. Several further, preferred, still further or more preferred arrangements of the belt after the same embodiment may be combined in any combination to form a further embodiment.

It will be appreciated by persons skilled in the art that the embodiments of the invention described above and shown in the drawings are given by way of example only and are not limiting of the invention. The objects of the present invention have been fully and effectively accomplished. The functional and structural principles of the present invention have been shown and described in the examples, and any variations or modifications of the embodiments of the present invention may be made without departing from the principles.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present disclosure, and not for limiting the same; while the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present disclosure.

The above description is only an example of the present invention and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A reconciliation management method is characterized by comprising the following steps:

receiving a first input at a first client;

receiving a second input at the second client;

checking the billing information in response to the second input;

2. The reconciliation management method of claim 1, further comprising:

3. The reconciliation management method of claim 1, wherein the creating billing information in response to the first input and sending the billing information to a second client specifically comprises:

creating billing information in response to the first input;

carrying out data uniqueness verification and cost mapping verification on the bill information;

4. The reconciliation management method of claim 2, wherein the returning the billing information to the first client, if the reconciliation result is an error, specifically comprises:

and sending the adjusted bill information to the first client.

5. A reconciliation management method according to claim 1, wherein the first client is a client on the supplier side, and the second client is a client on the enterprise side.

6. An account reconciliation management apparatus, comprising:

a first input module for receiving a first input at a first client;

a second input module for receiving a second input at the second client;

7. The reconciliation management device of claim 6, further comprising:

8. The reconciliation management device of claim 6, wherein the bill creation module comprises:

9. The reconciliation management device of claim 7, wherein the return module comprises:

the adjusting sub-module is used for adjusting the bill information at the second client under the condition that the checking result is wrong;

10. The reconciliation management device of claim 6, wherein the first client is a supplier-side client and the second client is an enterprise-side client.