CN105719182B - Automatic account checking method and automatic account checking system - Google Patents
Automatic account checking method and automatic account checking system Download PDFInfo
- Publication number
- CN105719182B CN105719182B CN201610031464.8A CN201610031464A CN105719182B CN 105719182 B CN105719182 B CN 105719182B CN 201610031464 A CN201610031464 A CN 201610031464A CN 105719182 B CN105719182 B CN 105719182B
- Authority
- CN
- China
- Prior art keywords
- site
- account checking
- reconciliation
- unit
- amount
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
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/12—Accounting
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
The invention provides an automatic account checking method, which comprises the following steps: acquiring a site list needing account checking at present; calculating the amount of accounts receivable of the site needing account checking according to the acquired site list needing account checking at present; inquiring an order corresponding to a site needing account checking; summarizing the actual received amount according to the inquired corresponding order; the amount due and the actual amount received at the site requiring reconciliation are compared.
Description
Technical Field
The invention relates to an automatic account checking method and an automatic account checking system, in particular to a real-time automatic account checking method and an automatic account checking system.
Background
In recent years, with the development of electronic commerce enterprises, the order quantity of the enterprises is gradually increased, the amount of money of card swiping of users is increased sharply, and particularly the number of pos card swiping is increased sharply. Manual card-swiping reconciliation, which has been commonly used, requires a single manual review by the captain of each site and then submission to the pos system. In this case, the following problems arise: the participation degree of people is too high, and errors are easy to occur; the system does not support dynamic blocking processing, and a server may be down when a large number of pos orders need to be processed, which may affect the operation of the whole company. Thus, the manual card swiping for account checking cannot meet the current business requirements.
Disclosure of Invention
The invention is provided to solve the above problems, and an object of the invention is to provide an automatic reconciliation method which can quickly and accurately complete pos reconciliation, can support horizontal dynamic machine expansion, automatically perform block processing on orders to be reconciled, meet the requirements of quick calculation and continuously increased amount of orders in later stage of reconciliation, and send out an alarm for problematic pos orders.
The invention discloses an automatic reconciliation method, wherein the reconciliation system comprises a preposing unit, a reconciliation unit, a fund collecting unit, a distributed application unit, a cache unit and a downstream unit, and the automatic reconciliation method comprises the following steps: starting automatic account checking; a step of obtaining a site list, in which an account checking unit obtains the site list needing account checking currently from a distributed application unit; calculating the accounts receivable amount of the sites needing account checking according to the acquired site list needing account checking at present by the account checking unit; inquiring a corresponding order, and inquiring the corresponding order by the account checking unit according to a site needing account checking; summarizing the actual received amount, and summarizing the actual received amount according to the inquired corresponding order by the account checking unit; and comparing, namely comparing the account receivable amount and the actual received amount of the site needing account checking by the account checking unit.
The automatic account checking method of the invention also comprises the following steps: sending alarm information, namely sending the alarm information under the condition that the amount of money to be received of the site needing account checking is inconsistent with the actually received amount of money; and a step of pushing to a downstream unit, and entering the processing of the downstream unit under the condition that the receivable amount of the site needing account checking is consistent with the actual received amount.
The automatic reconciliation method comprises the following steps between the step of obtaining the site list and the step of calculating the accumulated amount of the site collection: acquiring a site set, namely acquiring the site set needing account checking according to the site ID needing account checking; and a step of class object deserialization processing, which is to perform class object deserialization processing on the acquired site set.
The automatic reconciliation method comprises the following steps between the step of inquiring the corresponding order and the step of summarizing the actually received amount: inquiring the actual received amount, and inquiring the actual received amount of the order according to the inquired corresponding order; and a step of finding the sub-order by merging orders.
The automatic account checking method of the invention also comprises the following steps: a blocking step, namely blocking the station needing account checking by adopting an automatic balancing average blocking method; and a priority calculation step of calculating a priority of each station by using a priority calculation method and selecting a station having a high priority.
The automatic account checking method of the invention also comprises the following steps: and binding the selected site with the reconciliation unit for performing reconciliation, not allowing other reconciliation servers to perform parallel processing, and storing the corresponding relation between the selected site and the executed server in the cache server.
The automatic account checking method of the invention also comprises the following steps: the priority calculation method is a greedy algorithm.
In the step of calculating the priority, the priority of each site is calculated according to the order quantity of a certain previous time period, the current backlog order, the processed order quantity and the total number of the reconciliation servers.
In the automatic reconciliation method, in the step of calculating the priority, the current latest priority number is updated at fixed time intervals.
The automatic reconciliation method adopts the comprehensive consideration of the actual time cost of the current reconciliation and the estimated future time in the step of calculating the priority.
The automatic account checking method of the invention further comprises the following steps: the step of dynamically adding the reconciliation unit comprises the following steps: remotely increasing the block number in the distributed application unit, and selecting to start a new account checking unit; synchronizing a latest version number to all other reconciliation units; comparing the received latest version number with the version number of the local cache; if the latest version number is large, quitting the account checking processing in the process, and reallocating the sites; if the latest version number is small, this calling process is ignored.
The automatic account checking method of the invention further comprises the following steps: the step of dynamically reducing the account checking unit comprises the following steps: remotely reducing the block number in the distributed application unit; synchronizing a latest version number to all other reconciliation units; comparing the received latest version number with the version number of the local cache; if the latest version number is large, the account checking processing is continued; and if the latest version number is small, exiting the account checking processing in the process and stopping the account checking.
In the automatic reconciliation method of the present invention, the step of acquiring the site set and the step of deserializing the class object are executed in the cache unit.
The automatic reconciliation method of the invention is characterized in that the step of inquiring the actual received amount and the step of searching the sub-order by combining the orders are executed in the preposed unit.
The automatic reconciliation method of the invention is characterized in that the step of partitioning and the step of calculating the priority are executed in the distributed application unit.
The automatic reconciliation method is characterized in that the reconciliation system is a POS-based reconciliation system.
The automatic account checking method stores the corresponding relation between the selected website and the executed server in an Lhash mode.
An automatic reconciliation system comprising: the acquisition unit is used for acquiring a site list needing account checking at present; the calculation unit is used for calculating the amount of accounts receivable of the site needing account checking according to the acquired site list needing account checking currently; the inquiry unit is used for inquiring the order corresponding to the site needing account checking; a collecting unit for collecting the actual received money according to the inquired corresponding order; and the comparison unit is used for comparing the amount of money which is receivable and the actual amount of money which is received at the site needing account checking.
Effects of the invention
By the automatic account checking method, after pos is used for card swiping payment, account checking can be automatically carried out, and early warning can be carried out on problematic collection; by carrying out block processing on the station, the dynamic transverse expansion of the server can be supported, and the account checking bottleneck which possibly appears in the future is solved; and moreover, automatic priority processing is supported, so that the station with high priority can be guaranteed to process priority forever. Therefore, by the technical scheme, the efficiency and the accuracy of account checking can be improved, errors and risks caused by human participation are reduced, account checking results can be calculated and fed back quickly and in real time, and dynamic horizontal expansion is supported to meet the problem that a large number of orders are crowded, wherein the problem may occur in the future.
Drawings
Fig. 1 is a schematic diagram showing the relationship of the overall configuration of the reconciliation system of the present invention.
Fig. 2 is a general diagram illustrating server chunking invocation according to the present invention.
Figure 3 is a flow diagram illustrating a method for dynamically adding reconciliation servers.
Figure 4 is a flow chart illustrating a method for dynamically reducing reconciliation servers.
Fig. 5 is a flowchart showing details of the reconciliation service according to the present invention.
Fig. 6 is an exemplary diagram showing a site list.
Fig. 7 is a flow chart showing the partitioning and priority calculation in the distributed application server.
Fig. 8 is a block diagram showing a reconciliation system in accordance with the present invention.
Detailed Description
In order that the objects, technical solutions and advantages of the present invention will be more clearly understood, the present invention will be described in detail below with reference to specific embodiments and with reference to the accompanying drawings.
Fig. 1 is a schematic diagram showing the relationship of the overall configuration of the reconciliation system of the present invention.
As shown in fig. 1, the reconciliation system 1 of the present invention has a front-end unit (e.g., front-end server) 11, a reconciliation unit (e.g., reconciliation server) 12, a fund collection unit (e.g., fund collection server) 13, a caching unit (e.g., caching server) 14, a distributed application unit (e.g., distributed application server) 15, and a downstream unit (e.g., downstream system) 16.
Specifically, the front-end server 11 is a professional server of the cash register device to the bank, and here, a pos machine is taken as an example, that is, the front-end server 11 is a professional server of the pos to the bank, and the server has pos receivable amount and real receivable amount corresponding to the swipe card reader and the all-in-one machine. The server provides a service for the normal use of pos. Wherein the order receivable amount is pushed by means of a Message Queue (MQ), and the pushed order receivable amount is stored in a database (e.g., sqlserver server). The payment order number is used as a main key.
The fund collection server 13 is configured to account the total of the orders of each site, generate a check bit for starting reconciliation of the orders of each site according to the total of the orders of each site obtained through the accounting, and provide the check bit to the reconciliation server.
The cache server 14 (e.g., a Redis cache server) stores therein site information of the current reconciliation server. The distribution relationship between the site information and the reconciliation server is stored, for example, in an Lhash (Log Hash interleaving, Log type Hash integrity detection, where L is left-side permutation, and Hash is key _ value storage for a Hash field). And directly acquiring the site set needing to be processed by the current account checking server through the site ID.
The distributed application server 16 (for example, a zookeeper server) is mainly used for configuring a clone expression started by a current account checking custom timing task (worker) and configuration of corresponding custom timing task (worker) blocking information. The blocking will be described in detail later.
Specific expressions regarding the expression of cloning are as follows. The clone expression may include 7 fields: seconds, minutes, hours, date within month, day within week, year (optional fields). Primarily to indicate the time and frequency of execution. For example, expression "00/512? "indicates 12 o' clock start, performed every 5 minutes.
When each account checking server is started, the remote long-distance connection distributed application server 16 obtains a user-defined timing task (worker) block number of a current machine, obtains a station number through a user-defined priority blocking algorithm, and obtains a station list of the current account checking server needing account checking.
The downstream system 16, for example, after the pos reconciliation is completed, pushes the process to a different downstream system according to the reconciliation result. Including pushing the bank funds account when the order is finished and there is no problem.
Fig. 2 is a general diagram illustrating server chunking invocation according to the present invention.
As shown in fig. 2, Pos reconciliation uses an automatic balancing (balance) average blocking method, by which each machine is sorted one by one according to the current latest site priority, so that all site priorities can be equally divided. Firstly, estimating the number of sites to be processed by each server according to the number of sites/the number of reconciliation servers, and partitioning. The requirement that the processed orders are uniform in number by blocking accounts for each execution prevents the problem that individual servers have large and centralized accounts. The priorities are calculated by, for example, a greedy algorithm by which the station with the highest current priority is acquired each time, and the stations are selected according to the priorities. Thereby ensuring that the station with high priority is selected and the account checking is carried out on the selected station. By greedy algorithm is meant that when solving a problem, the choice that seems best at the present time is always made. The calculation of the site priorities in the invention is ordered by depending on the current priority of the current calculation.
The selected site will bind with the executing server and will not allow the other servers to process in parallel. Meanwhile, the corresponding relation between the selected site and the executed server is stored in the cache server.
Specifically, the reconciliation servers 121 to 12n send the number of received sites that need to be reconciled to the distributed application server 15, the distributed application server generates site data to be reconciled by using an automatic balancing average blocking method and a priority calculation method, and allocates site queues to be processed to each reconciliation server, that is, a site queue 1 and a site queue 2 … site queue n are generated for each reconciliation server, and the generated site queues 1 and 2 … site queues n are sent to corresponding reconciliation servers respectively.
Hereinafter, a greedy algorithm, which is a priority calculation method, will be described in detail.
The calculation of the priority of each site depends mainly on four factors, respectively the amount of orders from a previous period of time, e.g. yesterday's amount of orders, the current backlog order, the amount of orders already processed and the total number of reconciliation servers.
In this priority calculation method, a special timing task is defined to update the current latest priority number at regular intervals (e.g., 10 minutes). The calculation of the site priority adopts the comprehensive consideration of the current account checking actual time cost and the future time prediction.
F(n)＝0.6×g(n)+0.4×h(n)
Where f (n) represents the priority of the current site, g (n) (current backlog order quantity × t)/current reconciliation server total, g (n) represents the time cost required for each site to process the current backlog order, and t represents the time required for processing each order.
h (n) [ (total order amount of yesterday-processed order) × t/total order amount of yesterday ]/number of idle servers, and h (n) represents the time required for the current site to process the remaining order amount of yesterday from the remaining order amount of yesterday, and t represents the time required for processing each order.
A method of dynamically adding or subtracting reconciliation servers is described below with reference to fig. 3 and 4.
The reconciliation server can be dynamically added or reduced according to the amount of the orders. Figure 3 is a flow diagram illustrating a method for dynamically adding reconciliation servers. Figure 4 is a flow chart illustrating a method for dynamically reducing reconciliation servers.
Referring to fig. 3, after the block number is incremented remotely on the distributed application server 16, the start of a new tie-out server is selected (step S11). At the same time, the distributed application server 16 will synchronize a latest version number to all other reconciliation servers (step S12). The reconciliation server compares the latest version number received with the version number of the local cache (step S13). If the received latest version number is large, the account checking task in process is immediately exited, the site is redistributed, and then account checking is started (step S14). If the latest version number received is small, and possibly an instruction is expired, the custom timing task is ignored and restarted (step S15).
The same is true for decreasing servers. The block numbers are remotely reduced on the distributed application servers 16 while the corresponding number of reconciliation servers are stopped. The process flow is similar to the server addition flow described above. Referring to fig. 4, in particular, the block number is reduced remotely at the distributed application server 16 (step S21). At the same time, the distributed application server 16 will synchronize a latest version number to all other reconciliation servers (step S22). The reconciliation server compares the received latest version number with the version number of the local cache (step S23). If the received latest version number is large, the account checking task in process is immediately exited, the operation of account checking is stopped, and the state is in a standby state (step S25). If the latest version number received is small, the reconciliation task in process continues to be processed (step S24).
The specific process of the reconciliation service of the present invention is described in detail below with reference to fig. 5.
Fig. 5 is a flowchart showing details of the reconciliation service according to the present invention. POS-based reconciliation is used herein as an example, but is not limited thereto.
First, the reconciliation system starts to start the automatic reconciliation service (step S31).
The site list is generated in the distributed application server (S32), and how to generate the site list will be described later. An exemplary diagram of a site list is shown in fig. 6. The site list shown in fig. 6 is only an example, and the site list of the invention of the present application is not limited thereto.
The reconciliation server obtains the site list from the distributed application server (S33). The site set to be processed by the current reconciliation server is directly acquired from the cache server based on the site ID (step S34), class object deserialization is performed on the acquired site set (step S35), and the receivable amount of the site set is calculated (step S36).
The reconciliation server queries the corresponding order according to the site (step S37).
The reconciliation server inquires about the actual received amount of the order (step S38), and finds the sub-order by the consolidated order (step S39). Specifically, some users may pay for two orders at the same time, and at this time, the pos system automatically generates a parent order and then contains two child orders. When paying, pay with the father sheet, then when checking account, also need to consider two son sheets.
The amounts actually received by the orders are aggregated (step S40).
It is judged whether the actually received amount is identical to the receivable amount, that is, the full amount (step S41), and if it is judged that the actually received amount is identical to the receivable amount, that is, the full amount, it is judged that the amount is not erroneous, and the process proceeds to the next step, that is, the process is pushed to the corresponding downstream system (step S42). Wherein the condition that the account checking of each order is successful is
And (4) cash reconciliation: the order accumulation real receiving is equal to the receiving of the pos front-end processor,
checking account of the order: the order real-time collection and accumulation are the amount of the bank receipt.
If the actually received amount is determined to be inconsistent with the amount to be received, it is determined that the amount is wrong, the status bit is immediately marked for the order with failed reconciliation, and an alert mail is sent to the corresponding site owner every 1 hour, for example (step S43).
The processing performed in step S32 will be specifically described below with reference to fig. 7. Fig. 7 is a flow chart showing the partitioning and priority calculation in the distributed application server.
First, the distributed application server 15 receives the number of sites requiring reconciliation (step S321), and the distributed application server blocks the received sites by an auto-balancing average blocking method (step S322), selects sites requiring reconciliation by a priority calculation method (step S323), generates a list of sites requiring reconciliation (step S324), transmits the generated site queues to the corresponding reconciliation servers, respectively (step S33), binds the selected sites with the reconciliation server performing the reconciliation, does not allow the other reconciliation servers to perform parallel processing, and stores the correspondence between the selected sites and the reconciliation server performing the reconciliation in the cache server (step S325). The requirement that the processed orders are uniform in number by blocking accounts for each execution prevents the problem that individual servers have large and centralized accounts. In addition, the station with the highest current priority is acquired every time, so that the station with the high priority is guaranteed to be selected preferentially, and account checking is performed on the station selected preferentially.
The automatic reconciliation system of the present invention will be described below with reference to fig. 8. As shown in fig. 7, the automatic reconciliation system comprises: the acquisition unit is used for acquiring a site list needing account checking at present; the calculation unit is used for calculating the amount of accounts receivable of the site needing account checking according to the acquired site list needing account checking currently; the inquiry unit is used for inquiring the order corresponding to the site needing account checking; a collecting unit for collecting the actual received money according to the inquired corresponding order; and the comparison unit is used for comparing the account receivable amount and the actual account receivable amount of the site needing account checking.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the present invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Although the above-described embodiments of the present invention have been described in terms of software flow, it is obvious to those skilled in the art that some or all of the embodiments can be implemented by hardware, software, or a combination of hardware and software.
Claims (17)
1. An automatic reconciliation method comprising:
determining a plurality of sites needing account checking;
blocking the sites needing account checking by adopting an automatic balancing average blocking method to obtain a plurality of site lists, wherein each site list comprises site information of at least one site needing account checking;
for each site list in the plurality of site lists, calculating the priority of each site in each site list based on the site information, and binding the site with the highest priority in the site list with a designated reconciliation unit so that the site with the highest priority cannot be processed by other reconciliation units in parallel;
calculating the amount of accounts receivable of the sites needing account checking according to the site list;
inquiring an order corresponding to a site needing account checking;
summarizing the actual received amount according to the inquired corresponding order; and
the amount due and the actual amount received at the site requiring reconciliation are compared.
2. The automatic reconciliation method of claim 1 further comprising:
sending alarm information under the condition that the amount of money to be received of the site needing account checking is inconsistent with the actual amount of money to be received;
and in the case that the amount of the receivable amount of the site needing account checking is consistent with the actual received amount, entering the processing of a downstream unit.
3. The automatic reconciliation method of claim 1,
the method comprises the following steps of obtaining a site list needing account checking currently and calculating the receivable amount of the site needing account checking:
acquiring a site set needing account checking according to the site ID needing account checking;
and performing class object deserialization processing on the acquired site set.
4. The automatic reconciliation method of claim 1,
the method comprises the following steps of inquiring the order corresponding to the site needing account checking and summarizing the actual received amount:
inquiring the actual received amount of the order according to the inquired corresponding order;
the sub-orders are found by merging the orders.
5. The automatic reconciliation method of claim 1 further comprising:
and storing the corresponding relation between the station with the highest priority and the designated reconciliation unit in a cache server.
6. The automatic reconciliation method of claim 1 further comprising:
the priority calculation method is a greedy algorithm.
7. The automatic reconciliation method of claim 1,
in the step of calculating the priority, the priority of each site is calculated from the order amount of a previous certain time period, the current backlog order, the amount of orders already processed, and the total number of reconciliation units.
8. The automatic reconciliation method of claim 1,
in the step of calculating the priority, the current latest number of priorities is updated every fixed time.
9. The automatic reconciliation method of claim 1,
in the step of calculating the priority, the comprehensive consideration of the current account checking actual time cost and the future time prediction is adopted.
10. The automatic reconciliation method according to any one of claims 1 to 4 further comprising:
the dynamic addition reconciliation unit comprises:
remotely increasing the block number in the distributed application unit, and selecting to start a new account checking unit;
synchronizing a latest version number to all other reconciliation units;
comparing the received latest version number with the version number of the local cache;
if the latest version number is large, quitting the account checking processing in the process, and reallocating the sites;
if the latest version number is small, this calling process is ignored.
11. The automatic reconciliation method according to any one of claims 1 to 4 further comprising:
dynamic reduction reconciliation unit comprising:
remotely reducing the block number in the distributed application unit;
synchronizing a latest version number to all other reconciliation units;
comparing the received latest version number with the version number of the local cache;
if the latest version number is large, the account checking processing is continued;
and if the latest version number is small, exiting the account checking processing in the process and stopping the account checking.
12. The automatic reconciliation method of claim 3,
and executing the step of acquiring the site set and the step of deserializing the class object in a cache unit.
13. The automatic reconciliation method of claim 4,
the step of inquiring the actual received amount and the step of searching the sub-orders by merging the orders are performed in the front-end unit.
14. The automatic reconciliation method of claim 1,
the steps of blocking and calculating the priority are performed in a distributed application unit.
15. The automatic reconciliation method according to any one of claims 1 to 4,
the account checking unit is based on POS.
16. The automatic reconciliation method of claim 5,
and storing the corresponding relation between the station with the highest priority and the executed reconciliation unit in an Lhash manner.
17. An automatic reconciliation system comprising:
the system comprises a determining unit, a checking unit and a judging unit, wherein the determining unit is used for determining a plurality of sites needing account checking;
the blocking unit is used for blocking the sites needing account checking by adopting an automatic balancing average blocking method to obtain a plurality of site lists, and each site list comprises at least one site information of the site needing account checking;
a calculating unit, configured to calculate, for each of the plurality of site lists, a priority of each site in each of the site lists based on the site information, and bind a site with a highest priority in the site list with a designated reconciliation unit, so that the site with the highest priority cannot be processed by other reconciliation units in parallel;
a calculating unit for calculating the amount of accounts receivable of the sites needing account checking according to the site list;
the inquiry unit is used for inquiring the order corresponding to the site needing account checking;
a collecting unit for collecting the actual received money according to the inquired corresponding order; and
and the comparison unit is used for comparing the amount of money which is receivable and the actual amount of money which is received at the site needing account checking.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610031464.8A CN105719182B (en) | 2016-01-18 | 2016-01-18 | Automatic account checking method and automatic account checking system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610031464.8A CN105719182B (en) | 2016-01-18 | 2016-01-18 | Automatic account checking method and automatic account checking system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105719182A CN105719182A (en) | 2016-06-29 |
| CN105719182B true CN105719182B (en) | 2020-03-03 |
Family
ID=56147172
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610031464.8A Active CN105719182B (en) | 2016-01-18 | 2016-01-18 | Automatic account checking method and automatic account checking system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105719182B (en) |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106875275A (en) * | 2016-12-14 | 2017-06-20 | 武汉默联股份有限公司 | The on-line automatic reconciliation system and method for commercial health insurance |
| CN107067317A (en) * | 2017-04-18 | 2017-08-18 | 北京思特奇信息技术股份有限公司 | A kind of business revenue fund audit system and method |
| CN108874513A (en) * | 2017-05-11 | 2018-11-23 | 北京京东尚科信息技术有限公司 | Handle method, system, electronic equipment and the computer-readable medium of timed task |
| CN107292493B (en) * | 2017-05-26 | 2020-10-30 | 国网山东省电力公司德州供电公司 | Account checking system and method between power enterprise and bank |
| CN109102379B (en) * | 2017-06-21 | 2021-02-09 | 米思米（中国）精密机械贸易有限公司 | Account checking device, account checking server and account checking system |
| CN107392745B (en) * | 2017-07-14 | 2021-11-30 | 上海瀚之友信息技术服务有限公司 | Reconciliation data fragmentation processing method |
| CN107870980B (en) * | 2017-09-30 | 2019-05-10 | 平安科技（深圳）有限公司 | Electronic device, billing data processing method and computer storage medium |
| CN107729553A (en) * | 2017-11-07 | 2018-02-23 | 北京京东金融科技控股有限公司 | System data account checking method and device, storage medium, electronic equipment |
| CN108090824B (en) * | 2017-12-30 | 2019-12-27 | 平安科技（深圳）有限公司 | Data checking method and device, computer equipment and readable storage medium |
| CN108346185A (en) * | 2018-01-23 | 2018-07-31 | 北京悦畅科技有限公司 | A kind of method and apparatus of detection parking lot payment machine failure |
| CN108280754B (en) * | 2018-02-13 | 2021-08-06 | 平安科技（深圳）有限公司 | Routing sub-control account checking method and system |
| CN109117275B (en) * | 2018-08-31 | 2024-05-28 | 平安科技（深圳）有限公司 | Account checking method and device based on data slicing, computer equipment and storage medium |
| CN109359964A (en) * | 2018-09-22 | 2019-02-19 | 深圳优讯科技有限公司 | The real-time account checking method of multi-party payment channel |
| CN109615495B (en) * | 2018-10-11 | 2023-08-18 | 创新先进技术有限公司 | Data reconciliation method, device, equipment and system |
| CN110060142A (en) * | 2019-04-25 | 2019-07-26 | 湖南餐效信息科技有限公司 | Cash register management method and system, terminal and storage medium |
| CN113554376A (en) * | 2020-04-24 | 2021-10-26 | 四川物软网联科技有限公司 | Transportation order auditing method and system |
| CN113421163A (en) * | 2021-07-13 | 2021-09-21 | 北京沃东天骏信息技术有限公司 | Account checking method, account checking application cluster and related client |
| CN115577070B (en) * | 2022-09-09 | 2023-07-18 | 湖南环境生物职业技术学院 | Financial data inquiry management system |
| CN117391876B (en) * | 2023-12-05 | 2024-03-26 | 杭州瀚斯科技有限公司 | Intelligent processing method and related device for account checking information |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101315695A (en) * | 2008-07-09 | 2008-12-03 | 北京九恒星科技股份有限公司 | Bank information processing method and data extraction component |
| CN101872465A (en) * | 2009-04-27 | 2010-10-27 | 美国银行公司 | Be used for the improved account management rule that links financial institution's account management |
| CN102110276A (en) * | 2011-03-28 | 2011-06-29 | 中国建设银行股份有限公司 | Credit card credit investigation method and system |
| CN104809553A (en) * | 2015-04-20 | 2015-07-29 | 广东工业大学 | Multi-source electronic commerce data processing platform and method for heterogeneous data |
-
2016
- 2016-01-18 CN CN201610031464.8A patent/CN105719182B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101315695A (en) * | 2008-07-09 | 2008-12-03 | 北京九恒星科技股份有限公司 | Bank information processing method and data extraction component |
| CN101872465A (en) * | 2009-04-27 | 2010-10-27 | 美国银行公司 | Be used for the improved account management rule that links financial institution's account management |
| CN102110276A (en) * | 2011-03-28 | 2011-06-29 | 中国建设银行股份有限公司 | Credit card credit investigation method and system |
| CN104809553A (en) * | 2015-04-20 | 2015-07-29 | 广东工业大学 | Multi-source electronic commerce data processing platform and method for heterogeneous data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105719182A (en) | 2016-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105719182B (en) | Automatic account checking method and automatic account checking system | |
| CN109347669B (en) | Fault processing method and device for batch operation between bank systems | |
| AU2017251862A1 (en) | Marketplace for timely event data distribution | |
| CN113424171A (en) | Block chain transaction manager | |
| CN104636878B (en) | A kind of bank automatically processes the dispatching method and device of task | |
| US9146952B1 (en) | System and method for distributed back-off in a database-oriented environment | |
| CN102254238A (en) | Scalable billing with de-duplication in aggregator | |
| CN112200595A (en) | Coupon checking method, payment method, device, equipment and medium | |
| US8583754B2 (en) | Business flow distributed processing system and method | |
| CN108242021B (en) | Accounting data processing system, method and device | |
| US20090198543A1 (en) | License Compliance Management | |
| CN114168682A (en) | Data auditing method, device, equipment and storage medium | |
| CN111444003A (en) | Multi-system daily-cutting preparation method and device based on credit bill and financial settlement | |
| CN111274255A (en) | Service data monitoring method and system, monitoring architecture, equipment and storage medium | |
| CN115174686A (en) | Method and device for dynamically adjusting weights of multiple service channels based on service efficiency | |
| CN111062689B (en) | Method and device for processing cross-border service of RMB | |
| CN115271835A (en) | Invoice generation method and device, electronic equipment and storage medium | |
| CN110503477B (en) | Zxfoom zxfoom Muli (Maoli) abnormality of a system(s) apparatus and storage medium | |
| CN113706107A (en) | Accumulation fund payment method and device, electronic equipment and computer readable medium | |
| CN111415263A (en) | Data matching method and device | |
| EP1791056A1 (en) | Data processing method and system | |
| JP2014203227A (en) | Terminal management operation system and method | |
| KR100802092B1 (en) | Method and system for billing based on the client-server | |
| CN117132416B (en) | Data processing system and method | |
| CN109584029B (en) | Method, device, medium and electronic equipment for auditing electronic invoices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |