CN114155075A - Team service charge confirmation method and device - Google Patents
Team service charge confirmation method and device Download PDFInfo
- Publication number
- CN114155075A CN114155075A CN202111422977.9A CN202111422977A CN114155075A CN 114155075 A CN114155075 A CN 114155075A CN 202111422977 A CN202111422977 A CN 202111422977A CN 114155075 A CN114155075 A CN 114155075A
- Authority
- CN
- China
- Prior art keywords
- information
- service
- confirmed
- payment
- charged
- 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.)
- Pending
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
- G06Q40/125—Finance or payroll
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/22—Matching criteria, e.g. proximity measures
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Bioinformatics & Computational Biology (AREA)
- General Engineering & Computer Science (AREA)
- Evolutionary Computation (AREA)
- Evolutionary Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Artificial Intelligence (AREA)
- Technology Law (AREA)
- Life Sciences & Earth Sciences (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The document relates to the financial field, in particular to a team business charge confirmation method and a device, wherein the method comprises the following steps: according to a preset plan, acquiring service information to be charged from a service system and acquiring a payment record to be confirmed from a financial system; the service information to be charged and the payment record to be confirmed both comprise money amount information, payer information and payment time information; matching the service information to be charged with the payment record to be confirmed; generating acknowledgement information according to the successfully matched service information to be paid and the payment record to be acknowledged; and sending the acknowledgement information to the business system and the financial system so that the business system changes the state of the related business information to be charged according to the acknowledgement information and the financial system changes the state of the charge record to be confirmed according to the acknowledgement information. The system and the method can realize automatic acknowledgement of team business charge without participation of business personnel.
Description
Technical Field
The present disclosure relates to the field of finance, and in particular, to a method and an apparatus for confirming a charging fee of a team service, a computer device, and a storage medium.
Background
Team business charging requires that business charging funds be driven by a business requesting enterprise into an account with a business providing enterprise. For the record of charging, the financial staff of the business providing enterprise can only know the financial related information such as the account time, the amount, the name of the payer and the like, and can not be matched with the corresponding specific business contract.
In the prior art, the matching process of payment and service contract is as follows: confirming whether the account is marked by a salesman of the business providing enterprise and the business requesting enterprise, and filling a paper confirmation collection document of a related business contract according to a confirmation result; and delivering the paper confirmation collection documents of the related business contracts to the company finance, and operating the collection action of the business contracts one by one in the system by the financial staff according to the paper confirmation collection documents of the related business contracts.
As can be seen from the above paragraphs, the form of team service charge handover in the prior art is very complicated, and the clerk often needs to communicate with the company financial staff many times to complete the collection confirmation operation of the service contract. In addition, the handing over of the paper document is very inconvenient, the financial affairs of the company are often because the waiter's handwriting is illegible and can't be distinguished and increase the communication cost, and the retention of paper document is bound and also needs to consume certain manpower and time.
Aiming at the problems that the charging of team services is complicated and the communication cost is increased by offline cooperation, a team service charging confirmation method is urgently needed.
Disclosure of Invention
In order to solve the above problems in the prior art, embodiments herein provide a method, an apparatus, a computer device, and a storage medium for determining team business charging, which solve the problems in the prior art that team business charging is tedious and communication cost is increased by offline collaboration.
The embodiment of the invention provides a team business charge confirmation method, which is applied to a team business charge confirmation system, wherein the team business charge confirmation system is connected with a business system and a financial system, and the method comprises the following steps: according to a preset plan, acquiring service information to be charged from a service system and acquiring a payment record to be confirmed from a financial system; the service information to be charged and the charging record to be confirmed both comprise the following parameters: all comprise money information, payer information and payment time information; matching the service information to be charged with the payment record to be confirmed; generating acknowledgement information according to the successfully matched service information to be paid and the payment record to be acknowledged; and sending the acknowledgement information to the business system and the financial system so that the business system changes the state of the related business information to be charged according to the acknowledgement information and the financial system changes the state of the charge record to be confirmed according to the acknowledgement information.
According to an aspect of embodiments herein, matching the to-be-charged service information with the to-be-confirmed payment record includes: matching the service information to be charged and the parameter information in the payment record to be confirmed one by one; calculating the matching degree of the service information to be charged and the payment record to be confirmed according to the matching result of the service information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameters; if the matching degree of the service information to be charged and the charging record to be confirmed is greater than a preset value, the matching is successful; and if the matching degree of the service information to be charged and the charging record to be confirmed is less than a preset value, the matching is failed.
According to an aspect of the embodiments herein, the matching the service information to be charged and the parameter information in the payment record to be confirmed one by one includes: and executing the following calculation on each service information to be charged and each payment record to be confirmed:
a. calculating the similarity between the information of the payer in the service information to be paid and the information of the payer in the payment record to be confirmed, and if the similarity is greater than the preset similarity, determining that the information of the payer is successfully matched;
b. confirming whether the payment time information in the payment record to be confirmed is in the payment time information in the service information to be paid, if so, confirming that the payment time information is successfully matched;
c. and confirming whether the payment amount information in the payment record to be confirmed is equal to the payment amount information in the service information to be collected, if so, confirming that the payment amount information is successfully matched.
According to one aspect of embodiments herein, the payer information includes: before calculating the similarity between the information of the payer in the service information to be charged and the information of the payer in the charge record to be confirmed, the method further comprises the following steps: judging whether the information of the payer in the payment record to be confirmed is an organization abbreviation, if so, acquiring a legal organization name corresponding to the organization abbreviation;
calculating the similarity between the information of the payer in the service information to be charged and the information of the payer in the charge record to be confirmed further comprises the following steps: and calculating the similarity between the payer information in the service information to be charged and the name of the corresponding legal institution.
According to an aspect of the embodiments herein, when the matching of the information of the service to be charged and the information of the payer in the payment record to be confirmed is successful and the matching of the information of the payment time or the information of the payment amount is failed, the information of the service to be charged and the payment record to be confirmed are sent to the intelligent terminal of the attendant.
According to an aspect of embodiments herein, further comprising: receiving an inquiry request sent by a salesperson through a client of a team service charge confirmation system, wherein the inquiry request comprises: the service personnel identification or the service type to be confirmed, and start and stop date information; acquiring service information to be charged from a service system according to the service operator identification or the service type to be confirmed; acquiring a payment record to be confirmed from a financial system according to the start-stop date information; and executing the team service charge confirmation process.
According to an aspect of the embodiments herein, calculating the matching degree between the service information to be charged and the payment record to be confirmed according to the matching result between the service information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameter, includes calculating the matching degree using the following formula:
W＝a·α+b·β+c·γ
wherein a represents a matching result of the payer information; b represents the matching result of the payment time information; c represents the matching result of the payment information; α represents the weight of the payer information; β represents the weight of the payment time information; gamma represents the weight of the payment amount information, and W represents the matching degree of the service information to be charged and the payment record to be confirmed.
The embodiment herein further provides a team business charge confirmation apparatus, applied to a team business charge confirmation system, where the team business charge confirmation system connects a business system and a financial system, and includes:
the system comprises an acquisition unit, a payment processing unit and a payment processing unit, wherein the acquisition unit is used for acquiring service information to be charged from a service system and acquiring payment records to be confirmed from a financial system according to a preset plan; the service information to be charged and the charging record to be confirmed both comprise the following parameters: amount information, payer information and payment time information;
the matching unit is used for matching the service information to be charged with the charging record to be confirmed;
the confirmation information generating unit is used for generating confirmation information according to the successfully matched service information to be paid and the payment record to be confirmed;
and the sending unit is used for sending the acknowledgement information to the business system and the financial system so as to enable the business system to change the state of the related business information to be charged according to the acknowledgement information and enable the financial system to change the state of the charge record to be confirmed according to the acknowledgement information.
Embodiments herein also provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above mentioned team service charge validation method when executing the computer program.
Embodiments herein also provide a computer readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the above-described team service charge validation method.
By utilizing the embodiment, the team service charge confirmation system can automatically confirm the action of group charge to account, avoid consuming a large amount of labor cost, reduce the working pressure of business personnel and financial staff and further save the time cost. In addition, the system on the whole flow line can clearly record the operation track of each service step, is convenient for checking and retrieving, and further improves the standardized management level.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic network structure diagram of a team service charge validation system according to an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a method for team business charge validation according to an embodiment of the present disclosure;
fig. 3 is a flowchart illustrating a method for matching the service information to be charged with the payment record to be confirmed according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a method for matching the information of the service to be charged with the information of each parameter in the payment record to be confirmed according to an embodiment of the present disclosure;
FIG. 5 is a flowchart illustrating a method for matching information of a service to be charged with information of a payer in a payment record to be confirmed according to an embodiment of the present disclosure;
FIG. 6 is a flow chart illustrating a method for team business charge validation according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram illustrating a team service charge confirmation apparatus according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram illustrating a specific configuration of a device of a team service charge confirmation method according to this embodiment;
fig. 9 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
Description of the symbols of the drawings:
101. a team service charge validation server;
102. a network;
103. an intelligent terminal for the salesman;
701. an acquisition unit;
7011. a storage module;
702. a matching unit;
7021. a payer information calculation module;
7022. a payment time information confirmation module;
7023. a payment amount information confirmation module;
703. an acknowledgement information generating unit;
704. a transmitting unit;
902. a computer device;
904. a processor;
906. a memory;
908. a drive mechanism;
910. an input/output module;
912. an input device;
914. an output device;
916. a presentation device;
918. a graphical user interface;
920. a network interface;
922. a communication link;
924. a communication bus.
Detailed Description
In order to make the technical solutions in the present specification better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments, but not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.
It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.
The present specification provides method steps as described in the examples or flowcharts, but may include more or fewer steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures.
It should be noted that the team business charge validation method and apparatus herein can be used in the financial field, and can also be used in any field other than the financial field.
Fig. 1 is a schematic network structure diagram of a team service charge validation system according to an embodiment of the present disclosure, in which a team service charge validation method is described by combining a team service charge validation server 101, a network 102, and an intelligent attendant terminal 103. The team service charge confirmation server, the network and the intelligent salesman terminal can perform data interaction.
In some embodiments of the present description, the team service charge confirmation server 101 may be an electronic device with network interaction function, or may be software running in the electronic device to provide service logic for data processing and network interaction. The team service charge confirmation server 101 may obtain the service information to be charged and the charge record to be confirmed from the service system and the financial system according to a preset plan; the team service charge confirmation server 101 may also receive an inquiry request sent by the intelligent attendant terminal to inquire the information of the service to be charged and the charge record to be confirmed. In addition, the team service charge confirmation server 101 further includes a storage device, which is used for storing the service information to be charged and the charge record to be confirmed, which are acquired from the service system and the financial system; storing rules matching the information of the service to be charged and the charging record to be confirmed; and storing information such as legal agency names corresponding to the payer information in the payment record to be confirmed. In some embodiments of the present description, the team business charge validation server 101 includes, but is not limited to, personal computers, laptops, desktops, tablets, laptops, smartphones, and other electronic devices, and also includes browsers, applications, clients, and other software.
In some embodiments of the present description, network 102 may facilitate the exchange of information and/or data. In some embodiments of the present description, information and/or data may be sent in the clerk intelligent terminal 103 to the team business charge validation server 101 via the network 102. In other embodiments of the present description, the team service charge confirmation server 101 may send the result of the success or failure of matching the information of the service to be charged with the information in the charge record to be confirmed to the intelligent terminal 103 of the attendant through the network 102.
In some embodiments, the network 102 may be any form of wired or wireless network, or any combination thereof. Merely by way of example, network 102 may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Public Switched Telephone Network (PSTN), a bluetooth network, a ZigBee network, a Near Field Communication (NFC) network, or the like, or any combination thereof. In some embodiments, network 102 may include at least one network access point. For example, network 102 may include wired or wireless network access points, such as base stations and/or internet switching points, through which the attendant intelligent terminals 103 may connect to network 102 to exchange data and/or information.
In some embodiments of the present description, the intelligent terminal 103 may be an electronic device with network interaction function. The attendant smart terminal 103 includes, but is not limited to, one or any combination of a personal computer, a laptop computer, a desktop computer, a tablet computer, a laptop computer, a smartphone, a digital assistant, a smart wearable device, and the like. The attendant intelligent terminal 103 is connected to the team service charge confirmation server 101 via a network. The intelligent terminal 103 of the salesman is not limited to the above electronic device with certain entity, and may also be software running in the above electronic device.
Fig. 2 is a flowchart of a team service charge confirmation method applied to a team service charge confirmation system according to an embodiment of the present disclosure, where the team service charge confirmation system connects a service system and a financial system, and specifically includes the following steps:
Team businesses described herein include, but are not limited to, team insurance businesses, team health businesses, team travel businesses, and the like.
In some embodiments of the present description, the transaction system stores the information of the transaction to be charged and the financial system stores the record of the payment to be confirmed. The payment records of the payment arrived in the financial system need to be confirmed through the business information in the business system. The service information to be paid in the service system is extracted from team service contract information, the service information to be paid reflects the parameter condition of the due payment, and the team service contract information records contract number, service information, amount information, information of a payer and payment time information. The parameter information in the payment record to be confirmed in the financial system reflects the paid parameter condition. The information of the payer in the information of the service to be paid may include the name of the institution to be paid, the account number to be paid, the bank information to be paid and opened. The payment time information in the information of the services to be charged may include: the latest time due for payment, the time period due for payment, etc.
And step 203, generating the confirmation information according to the successfully matched service information to be paid and the payment record to be confirmed. In this step, if the matching of the service information to be charged and the payment record to be confirmed is successful, which indicates that the team service charging is completed, the team service charging confirmation server will generate the confirmation information, which indicates that the system has confirmed that the correct service payment has been received.
In detail, the confirmation information includes information (such as the service information to be charged and the identification of the payment record to be confirmed, such as a number, an ID, etc.) that the record matching is successful and the service information to be charged and the payment record to be confirmed can be uniquely located.
In detail, the service system changes the state of the corresponding service information to be charged in the system into the charged state according to the identification of the service information to be charged in the acknowledgement information. And the financial system changes the state of the corresponding payment record to be confirmed in the system into confirmed state according to the mark of the payment record to be confirmed in the confirmation information.
Fig. 3 is a flowchart illustrating a method for matching service information to be charged with payment records to be confirmed according to an embodiment of the present disclosure.
And 310, matching the service information to be charged and the parameter information in the payment record to be confirmed one by one. According to the description in fig. 2, the information of the service to be charged includes the parameter information of the due payment (e.g., the information of the amount to be paid, the information of the payer to be paid, the information of the payment time to be paid, etc.), and the record of the payment to be confirmed includes the parameter information of the paid payment (e.g., the information of the amount paid, the information of the payer to be paid, the information of the payment time to be paid, etc.). In order to match the service to be charged and each parameter information in the charging record to be confirmed, the parameter information in the two systems needs to be matched one by one. Specifically, matching the information of the amount to be paid in the service information to be paid with the information of the amount to be paid in the payment record to be confirmed; matching the payor detail information which is payable in the service information to be paid with the payor information which is paid in the payment record to be confirmed; and matching the payment time information of the due payment in the service information to be paid with the payment time information of the paid payment in the payment record to be confirmed.
And step 320, calculating the matching degree of the service information to be charged and the payment record to be confirmed according to the matching result of the service information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameters.
In some embodiments of the present description, there are two cases as a result of matching the service information to be charged with the parameter information in the payment record to be confirmed: matching success and matching failure. Specifically, the matching result may be represented by a numeral 1 or 0. Wherein, the matching success or the matching failure can be determined by a certain rule. This is described in detail with reference to FIG. 4.
In addition, the parameters in the service information to be charged and the payment record to be confirmed have respective weights according to the direction extent of the service information to be charged and the payment record to be confirmed. For example, the payment amount information is weighted 30%, the payer information is weighted 50%, and the payment time is weighted 20%. The payment time is weighted 20%.
In this step, the matching degree of the service information to be charged and the payment record to be confirmed is calculated according to the matching result of the service information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameter, and the matching degree is calculated by using the following formula: w is α · α + b · β + c · γ. Wherein a represents a matching result of the payer information; b represents the matching result of the payment time information; c represents a matching result of the payment amount information; α represents the weight of the payer information; β represents the weight of the payment time information; gamma represents the weight of the payment amount information, and W represents the matching degree of the service information to be charged and the payment record to be confirmed. In this step, the symbol "·" is a dot-by-dot symbol, which means that the multiplication operation is performed on the parameters before and after the symbol.
For example, the matching result a of the service information to be paid and the payer information in the payment record to be confirmed is 1; the matching result b of the service information to be charged and the time information in the payment record to be confirmed is 0; the matching result c of the service information to be charged and the payment amount information in the payment record to be confirmed is 1; the payer information has a weight α of 50% and a payment time weight β of 20%; and the payment amount information is weighted by 30%. According to the formula, the matching degree of the service information to be charged and the charging record to be confirmed can be determined as follows: 1, 30% +0, 20% +1, 50% + 80%. In this application, the weight of the service information to be charged and the parameter in the payment record to be confirmed may be preset by the system, or may be adjusted according to the actual service condition, and this application is not limited herein. In this step, the symbol "·" is a dot-by-dot symbol, which means that the multiplication operation is performed on the parameters before and after the symbol.
And step 330, if the matching degree of the service information to be charged and the payment record to be confirmed is greater than a preset value, the matching is successful. In this step, a specific calculation manner of the matching degree between the service information to be paid and the payment record to be confirmed may be described with reference to fig. 4. In some embodiments of the present description, the predetermined value may be a value of 90%, 95%, 98%, etc. For example, the predetermined value is set to 95%, when the matching degree between the service information to be charged and each parameter information in the payment record to be confirmed is greater than 95%, the service information to be charged and the payment record to be confirmed are considered to be successfully matched, and when the matching degree is less than 95%, the service information to be charged and the payment record to be confirmed are considered to be unsuccessfully matched.
Taking step 320 as an example, if the matching degree of the service information to be collected and the payment record to be confirmed is 80%, the predetermined value is set to be 70%, and the matching degree of the service information to be collected and the payment record to be confirmed is greater than 70%, the matching is successful.
And 340, if the matching degree of the service information to be charged and the payment record to be confirmed is smaller than a preset value, the matching is failed.
The predetermined value may be 90%, 95%, 98%, etc. as depicted in step 330. For example, when the predetermined value is set to 90%, and the matching degree between the service information to be charged and each parameter information in the payment record to be confirmed is lower than 90%, it may be considered that the matching between the service information to be charged and the payment record to be confirmed fails. Taking step 320 as an example, if the matching degree of the service information to be collected and the payment record to be confirmed is 80%, the predetermined value is set to be 90%, and the matching degree of the service information to be collected and the payment record to be confirmed is less than 70%, the matching fails. The predetermined value may be preset by the system, or may be adjusted according to the actual service condition. The method of setting the predetermined value is not limited herein.
Fig. 4 is a flowchart illustrating a method for matching service information to be charged with parameter information in a payment record to be confirmed according to an embodiment of the present disclosure. And specifically calculating the similarity or other related relations between each parameter information in the service information to be charged and each parameter information in the charging record to be confirmed through a certain rule, and further determining the matching result of each parameter.
In this step, after the team service charge confirmation server 101 obtains the information of the payer in the service information to be charged and the information of the payer in the payment record to be confirmed, the information of the payer may be presented on the client of the team service charge system in the form of image or text. The team service charge confirmation server 101 may further perform Character Recognition (OCR) or Natural Language Processing (NLP) on the information of the payer in the charge service information and the information of the payer in the charge record to be confirmed, and further calculate the text similarity of the two types of payment information. When the similarity between the two payment information is greater than a predetermined similarity; it is determined that the payer information matches successfully. In some embodiments of the present description, the predetermined similarity may be an 80%, 90%, 95%, etc. value when the similarity between two payment information is less than the predetermined similarity, it is determined that the payer information fails to match. The predetermined similarity may be preset by the system, or may be adjusted according to the actual service condition. The present application does not limit the setting method of the predetermined similarity.
Fig. 5 is a flowchart illustrating a method for matching information of a service to be charged with information of a payer in a payment record to be confirmed according to an embodiment of the present disclosure. Before calculating the similarity between the payer information in the information about the service to be charged and the payer information in the payment record to be confirmed in fig. 4, the method further includes:
As described above, the payer information includes the name of the payment authority and/or the payment account number. In some embodiments of the present specification, the service information to be collected is service information confirmed when a service contract is made, and generally corresponds to the service contract, and therefore, the name of the payment institution in the service information to be collected is generally formal, and is generally a name of a legal institution of an enterprise. Correspondingly, in an actual application scenario, the information of the payer in the payment record to be confirmed may not be complete, and the information of the payer in the payment record to be confirmed may be referred to as an organization abbreviation. Specifically, for example, the legal agency name of a certain payment agency is: beijing ABC Enforcement Limited liability company. The name of the payment mechanism in the information of the payer in the payment record to be confirmed is called the mechanism for short: and (5) ABC. In this case, when there is a name of a payment institution with the same duplicate name or abbreviated name in the team service charging system, the similarity between the information of the payer in the to-be-confirmed payment record and the information of the payer in the to-be-charged service information cannot be directly calculated.
Thus, the team business charging system may obtain from the memory, database, at least one legal institution name corresponding to the payer information in the payment record to be determined.
When the unique legal institution name corresponding to the payer information in the payment record to be confirmed is obtained, the legal institution name corresponding to the payer information in the payment record to be confirmed determined in step 501 is compared with the similarity of the payer information in the service information to be collected. For example, the name of the payment institution in the payer information in the payment record to be confirmed is "ABC". The team business charging system acquires the only legal institution name corresponding to the ABC institution name from the database according to the ABC institution name, and the only legal institution name is Beijing ABC actual industry LLC company. If the similarity between the information of the payer in the service information to be charged and the name of the corresponding legal organization is higher, the similarity between the information of the payer in the service information to be charged and the information of the payer in the payment record to be determined can be determined to be higher.
When a plurality of legal institution names are obtained from the storage device, further obtaining the payment account number of the paid payer information from the to-be-confirmed payment record and the payment account number of the payer information in the to-be-confirmed payment record from the to-be-confirmed payment record, and comparing whether the payment account number of the paid payer information and the payment account number of the payer information in the to-be-confirmed payment record are consistent, for example, the name of the payment institution in the payer information in the to-be-confirmed payment record is ABC. The team business charging system acquires a plurality of corresponding legal institution names from the database according to the ABC institution names, and the legal institution names are respectively: beijing ABC practice company, Guangdong ABC education and training company, and ABC Mimez company. And further acquiring the ABC payment account number from the payment record to be confirmed, matching the ABC payment account number with the payment account number in the payer information in the service information to be charged, and determining whether the payer information in the service information to be charged is matched with the payer information in the payment record to be confirmed.
As an embodiment herein, when matching of a to-be-charged service information and information of a payer in a to-be-confirmed payment record is successful and matching of payment time information or payment amount information is failed, the to-be-charged service information and the to-be-confirmed payment record are sent to an intelligent terminal of an operator.
When the team service charging confirmation server 101 obtains each parameter from the service information to be charged and the charging record to be confirmed, it is determined that the matching of the information of the payer is successful, and the matching of the information of the payment time or the information of the payment amount is failed. It can be understood that the information matching of the name of the payment institution of the payer, the account number to be paid, the bank information to be paid and opened, and the like fails. The team service charge confirmation server 101 sends the acquired information of the service to be charged and the charge record to be confirmed to the intelligent terminal of the service staff for the service staff to manually confirm or verify.
In addition, when the information of a service to be charged is successfully matched with the information of the payer and the information of the payment amount in the payment record to be confirmed, and the information of the payment time is not successfully matched; or when the matching of the information of the service to be charged and the information of the payer and the information of the payment time in the payment record to be confirmed is successful and the matching of the information of the payment amount is unsuccessful, the team service charging confirmation server 101 can send the information of the service to be charged and the payment record to be confirmed to the intelligent terminal of the waiter, and the information of the service to be charged and the payment record to be confirmed can be further checked manually.
Fig. 6 is a flowchart of a team service charge validation method according to an embodiment of the present disclosure. In some embodiments of the present description, the steps of obtaining the information of the service to be charged from the service system and obtaining the record of the payment to be confirmed from the financial system may be implemented by receiving an inquiry request initiated by a service operator, and the steps are as follows:
And step 603, acquiring the payment record to be confirmed from the financial system according to the start-stop date information. Specifically, the team service charging system may receive the start and end dates sent by the staff through the client of the team service charging confirmation system to obtain the payment records to be confirmed. For example, the team business charging system receives "inquire business charging record with charging date of 9 months in 2021" sent by the business, and the team business charging system can inquire corresponding charging record to be confirmed from the financial system.
Fig. 7 is a schematic structural diagram of a team service charge confirmation apparatus according to an embodiment of the present disclosure, in which a basic structure of the team service charge confirmation apparatus is described, where functional units and modules may be implemented in a software manner, or may also be implemented in a general chip or a specific chip, and a part or all of the functional units and modules may be on a server, or a part of the functional units and modules may also be on a node, and the team service charge confirmation is implemented through cooperation with the server, where the apparatus specifically includes:
an obtaining unit 701, configured to obtain, according to a preset plan, to-be-charged service information from a service system and obtain to-be-confirmed payment records from a financial system; the service information to be charged and the charging record to be confirmed both comprise the following parameters: amount information, payer information and payment time information;
a matching unit 702, configured to match the service information to be charged with the payment record to be confirmed;
the confirmation information generating unit 703 is configured to generate confirmation information according to the successfully matched service information to be paid and the payment record to be confirmed;
a sending unit 704, configured to send the acknowledgement information to the business system and the financial system, so that the business system changes a state of the related to-be-confirmed business information according to the acknowledgement information, and so that the financial system changes a state of the to-be-confirmed payment record according to the acknowledgement information.
In specific implementation, in order to facilitate the salesperson to know the matching condition of the service information to be charged and the charging record to be confirmed, a display interface is generated according to the matching result, so that the salesperson can inquire the matching result.
Through the setting of this paper embodiment, team's business charge confirmation device can confirm the action of group's charge to account through online system interactive cooperation by salesman and financial staff. The consumption of a large amount of labor cost is avoided, the working pressure of business personnel and financial staff is reduced, and the time cost is further saved. In addition, the system on the whole flow line can clearly record the operation track of each service step, is convenient for checking and retrieving, and further improves the standardized management level.
As an embodiment herein, reference may also be made to a schematic structural diagram of the team service charge confirmation device in this embodiment as shown in fig. 8.
The acquiring unit 701 further includes storing the service information to be collected acquired from the service system and the payment record to be confirmed acquired from the financial system in a memory.
As an embodiment herein, the obtaining unit 701 further includes:
the storage module 7011 is configured to store the to-be-charged service information and the to-be-confirmed charging record.
The matching unit 702 further determines whether the information of the payer, the payment time information, and the payment amount in the service information to be charged are successfully matched with the information of the payer, the payment time information, and the payment amount in the payment record to be determined, respectively. As an embodiment herein, the matching unit 702 further includes:
the payer information calculating module 7021 is configured to calculate similarity between the payer information in the to-be-paid service information and the payer information in the to-be-confirmed payment record;
the payment time information confirming module 7022 is configured to confirm whether the payment time information in the payment record to be confirmed is within the payment time information in the service information to be collected;
the payment amount information confirming module 7023 is configured to confirm whether the payment amount information in the payment record to be confirmed is equal to the payment amount information in the service information to be charged.
As shown in fig. 9, for a computer device provided for embodiments herein, the computer device 902 may include one or more processors 904, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 902 may also include any memory 906 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 906 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 902. In one case, when the processor 904 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 902 can perform any of the operations of the associated instructions. The computer device 902 also includes one or more drive mechanisms 908, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.
Corresponding to the contents in fig. 1-6, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, performs the steps of the above-described method.
Embodiments herein also provide computer readable instructions, wherein when executed by a processor, a program thereof causes the processor to perform the operations shown in fig. 1-6.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.
Claims (10)
1. A team service charge confirmation method applied to a team service charge confirmation system, wherein the team service charge confirmation system connects a business system and a financial system, the method comprising:
according to a preset plan, acquiring service information to be charged from the service system and acquiring payment records to be confirmed from the financial system; the service information to be charged and the charging record to be confirmed both comprise the following parameters: amount information, payer information and payment time information;
matching the service information to be charged with the payment record to be confirmed;
generating acknowledgement information according to the successfully matched service information to be paid and the payment record to be acknowledged;
and sending the acknowledgement information to the business system and the financial system so that the business system changes the state of the related business information to be charged according to the acknowledgement information and the financial system changes the state of the charge record to be confirmed according to the acknowledgement information.
2. The team business charge validation method of claim 1, wherein matching the to-be-charged business information with the to-be-validated fee record comprises:
matching the service information to be charged and the parameter information in the payment record to be confirmed one by one;
calculating the matching degree of the service information to be charged and the payment record to be confirmed according to the matching result of the service information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameters;
if the matching degree of the service information to be charged and the charging record to be confirmed is greater than a preset value, the matching is successful;
and if the matching degree of the service information to be charged and the payment record to be confirmed is smaller than the preset value, the matching is failed.
3. The team business charge confirmation method of claim 2, wherein the matching of the business information to be charged and the parameter information in the charge record to be confirmed one by one comprises:
and executing the following calculation on each service information to be charged and each payment record to be confirmed:
a. calculating the similarity between the information of the payer in the service information to be paid and the information of the payer in the payment record to be confirmed, and if the similarity is greater than the preset similarity, determining that the information of the payer is successfully matched;
b. confirming whether the payment time information in the payment record to be confirmed is in the payment time information in the service information to be paid, if so, confirming that the payment time information is successfully matched;
c. and confirming whether the payment amount information in the payment record to be confirmed is equal to the payment amount information in the service information to be collected, if so, confirming that the payment amount information is successfully matched.
4. The team business charge validation method of claim 3, wherein before calculating the similarity between the payer information in the business information to be charged and the payer information in the payment record to be validated, further comprising:
judging whether the information of the payer in the payment record to be confirmed is an organization abbreviation, if so, acquiring a legal organization name corresponding to the organization abbreviation;
calculating the similarity between the information of the payer in the service information to be charged and the information of the payer in the charge record to be confirmed further comprises the following steps: and calculating the similarity between the payer information in the service information to be charged and the corresponding legal institution name.
5. The team service charge confirmation method of claim 3, wherein when a matching of a to-be-charged service information and a payer information in a to-be-confirmed charge record is successful and a matching of a payment time information or a payment amount information is failed, the to-be-charged service information and the to-be-confirmed charge record are transmitted to the intelligent terminal of the waiter.
6. The team business charge validation method of claim 1, further comprising:
receiving an inquiry request sent by a salesperson through a client of the team service charge confirmation system, wherein the inquiry request comprises: the service personnel identification or the service type to be confirmed, and start and stop date information;
acquiring the service information to be charged from the service system according to the operator identification or the service type to be confirmed;
acquiring the payment record to be confirmed from the financial system according to the start-stop date information;
and executing the team service charge confirmation process.
7. The team business charge confirmation method of claim 2, wherein calculating the matching degree of the business information to be charged and the payment record to be confirmed according to the matching result of the business information to be charged and the parameter information in the payment record to be confirmed and the weight information of the parameters comprises calculating the matching degree by using the following formula:
W＝a·α+b·β+c·γ
wherein a represents a matching result of the payer information; b represents the matching result of the payment time information; c represents the matching result of the payment information; α represents the weight of the payer information; β represents the weight of the payment time information; gamma represents the weight of the payment amount information, and W represents the matching degree of the service information to be charged and the payment record to be confirmed.
8. A team service charge confirmation apparatus applied to a team service charge confirmation system connecting a business system and a financial system, the apparatus comprising:
the system comprises an acquisition unit, a payment processing unit and a payment processing unit, wherein the acquisition unit is used for acquiring service information to be charged from a service system and acquiring payment records to be confirmed from a financial system according to a preset plan; the service information to be charged and the charging record to be confirmed both comprise the following parameters: amount information, payer information and payment time information;
the matching unit is used for matching the service information to be charged with the charging record to be confirmed;
the confirmation information generating unit is used for generating confirmation information according to the successfully matched service information to be paid and the payment record to be confirmed;
and the sending unit is used for sending the acknowledgement information to the business system and the financial system so as to enable the business system to change the state of the related business information to be charged according to the acknowledgement information and enable the financial system to change the state of the charge record to be confirmed according to the acknowledgement information.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111422977.9A CN114155075A (en) | 2021-11-26 | 2021-11-26 | Team service charge confirmation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111422977.9A CN114155075A (en) | 2021-11-26 | 2021-11-26 | Team service charge confirmation method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114155075A true CN114155075A (en) | 2022-03-08 |
Family
ID=80458146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111422977.9A Pending CN114155075A (en) | 2021-11-26 | 2021-11-26 | Team service charge confirmation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114155075A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115239338A (en) * | 2022-08-01 | 2022-10-25 | 中科泰岳(北京)科技有限公司 | Industry and finance integrated charging system with automatic data uploading function |
-
2021
- 2021-11-26 CN CN202111422977.9A patent/CN114155075A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115239338A (en) * | 2022-08-01 | 2022-10-25 | 中科泰岳(北京)科技有限公司 | Industry and finance integrated charging system with automatic data uploading function |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11403696B2 (en) | Client centric viewer | |
| CN111316310B (en) | Unified electronic transaction management system | |
| US6598087B1 (en) | Methods and apparatus for network-enabled virtual printing | |
| US6850643B1 (en) | Methods and apparatus for collateral risk monitoring | |
| US7035821B1 (en) | Methods and apparatus for processing cash advance requests | |
| US12008315B2 (en) | Automatic generation and population of digital interfaces based on adaptively processed image data | |
| US6546133B1 (en) | Methods and apparatus for print scraping | |
| EP2740094A1 (en) | Apparatus, method, and computer program product for data cleansing and/or biller scrubbing | |
| US11393045B2 (en) | Methods and systems for efficient delivery of accounting and corporate planning services | |
| US6850908B1 (en) | Methods and apparatus for monitoring collateral for lending | |
| CN112381645A (en) | Information processing method and device for bill transaction | |
| CN114155075A (en) | Team service charge confirmation method and device | |
| JP3654801B2 (en) | Electronic trading method and electronic trading system | |
| JP6055050B1 (en) | Bank system, method and program executed by bank system | |
| US7003489B1 (en) | Methods and apparatus for submitting information to an automated lending system | |
| JP5864636B2 (en) | Electronic record receivable counterparty name display system | |
| CN111178993A (en) | Method and system for automatically calling invoice electronic file based on invoice container | |
| KR101809362B1 (en) | Transaction Information Managing System using Optical Character Reader System and Computerized Transaction Information Managing Method using It | |
| JP2006209302A (en) | Centralized transfer work processing system | |
| JP2016042292A (en) | National government bond principal and interest distributing system, and method for the same | |
| US20100131288A1 (en) | Identification and reconciliation of missed or erroneous provider charges | |
| JP2019219738A (en) | Debt customer management system, debt customer management method, and debt customer management program | |
| KR102677178B1 (en) | System for providing invoice managment agency service | |
| CN115456747B (en) | Automatic intelligent account settling method and device for ERP system and storage medium | |
| JP2002312597A (en) | Electronic transaction method, its center, its terminal and its system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |