CN114092203A - Method, device, storage medium and computer program product for checking and debiting - Google Patents
Method, device, storage medium and computer program product for checking and debitingDownload PDFInfo
- Publication number
- CN114092203A CN114092203ACN202111136598.3ACN202111136598ACN114092203ACN 114092203 ACN114092203 ACN 114092203ACN 202111136598 ACN202111136598 ACN 202111136598ACN 114092203 ACN114092203 ACN 114092203A
- Authority
- CN
- China
- Prior art keywords
- refund
- account
- data
- time
- type
- 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 OR CALCULATING; 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
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
Translated fromChinese
Description
Technical Field
The present application relates to the field of financial refund and entry, and in particular, to a method, an apparatus, a storage medium, and a computer program product for refund and entry.
Background
At present, in a typical financial processing system, data update at a business level is generally consistent with data update at an accounting level of the financial system, that is, after a cash-back operation at the business level is successful, the data at the business level and the data at the accounting level are updated no matter whether cash flow of the cash-back operation is successfully credited or not.
However, in the actual money-returning process, the completion of the money-returning operation at the business level cannot represent the return of the fund to be paid out, or the deposit is successful according to the business rules, which may cause inconsistency between the fund flow and the data flow at the system accounting level, thereby causing various problems.
Disclosure of Invention
The application aims to provide a refund posting method, a device, a storage medium and a computer program product, which are used for solving the problem of inconsistency between financial affair level fund flow and data flow possibly caused during the operation of the refund posting.
The application provides a refund posting method, which comprises the following steps:
receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
Optionally, the money return operation request further includes: the amount of money to be collected; before the receiving of the refund operation request, the method further comprises: and calculating the amount of the refund which is to be collected according to the refund type and/or the expected arrival time of the refund.
Optionally, the calculating the refund receivable amount according to the refund type and/or the refund estimated due time comprises: under the condition that the refund type is real-time account-finding refund, calculating the refund receivable amount according to the current date; or under the condition that the type of the refund is non-real-time account-arriving refund, calculating the refund receivable amount according to the expected account-arriving time of the refund; wherein the return receivable amount includes at least one of: the fund, interest and overdue fee are charged for the refund.
Optionally, the updating the business data and the accounting data according to the type of the refund and/or the expected arrival time of the refund includes: and updating the business data under the condition that the type of the refund is the real-time account-returning refund, and updating the accounting data after the refund is received.
Optionally, the updating the business data and the accounting data according to the type of the refund and/or the expected arrival time of the refund includes: if the type of the refund is a non-real-time account-in refund and an in-transit refund exists, if the expected account-in time of the refund is earlier than the expected account-in time of the in-transit refund, the in-transit refund is cancelled, and the in-transit refund is resubmitted based on the refund operation request; updating the in-transit cash back information of the business layer, and updating the accounting data after the resubmitted in-transit cash back is sent to an account; or, if the type of the refund is a non-real-time account-returning refund and there is an in-transit refund, if the expected account-arriving time of the refund is not earlier than the expected account-arriving time of the in-transit refund, the refund operation indicated by the refund operation request is cancelled, and the business data is updated based on the result of the refund operation; updating the accounting data after the in-transit return is posted.
Optionally, the updating the business data and the accounting data according to the type of the refund and/or the expected arrival time of the refund includes: and updating the business data under the condition that the type of the return is non-real-time account-arriving return and no in-transit return exists, and updating the accounting data after the non-real-time account-arriving return is received.
The application also provides a device for refund and posting, including:
the receiving module is used for receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; the data updating module is used for updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
Optionally, the money return operation request further includes: the amount of money to be collected; the device further comprises: and the calculating module is used for calculating the amount of the refund which is to be received according to the refund type and/or the expected arrival time of the refund.
Optionally, the calculating module is specifically configured to calculate the amount to be collected for the refund according to a current date when the refund type is a real-time billed refund; or, the calculating module is specifically configured to calculate the amount to be collected for the refund according to the expected arrival time of the refund when the refund type is the non-real-time arrival refund; wherein the return receivable amount includes at least one of: the fund, interest and overdue fee are charged for the refund.
Optionally, the data updating module is specifically configured to update the business data when the type of the return is a real-time account-receiving return, and update the accounting data after the return is received.
Optionally, the data updating module is specifically configured to, when the type of the cash back is a non-real-time reimbursement type and there is an in-transit cash back, revoke the in-transit cash back if the expected due time of the cash back is earlier than the expected due time of the in-transit cash back, and resubmit the in-transit cash back based on the cash back operation request; updating the in-transit cash back information of the business layer, and updating the accounting data after the resubmitted in-transit cash back is sent to an account; or, the data updating module is specifically configured to, when the type of the refund is a non-real-time reimbursement type and there is an in-transit refund, if the expected reimbursement due time is not earlier than the expected due time of the in-transit refund, cancel the refund operation indicated by the refund operation request, and update the service data based on the result of the refund operation; updating the accounting data after the in-transit return is posted.
Optionally, the data updating module is specifically configured to update the business data when the type of the return is a non-real-time account return and no in-transit return exists, and update the accounting data after the non-real-time account return is received.
The present application also provides a computer program product comprising computer program/instructions which, when executed by a processor, implement the steps of a method of check-back posting as described in any of the above.
The application also provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the steps of the cash-back posting method.
The present application also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of check-back posting as described in any of the above.
According to the refund posting method and device, when a refund operation request is received, according to the refund type included in the refund operation request and/or the expected posting time of the refund, after the data of a business layer generated by a fund flow payment result and the data of the fund flow are updated and posted, the account book data of the posting rule of the business is met, so that after the refund operation of business personnel is successful, the data of the business layer and the data of the account layer can be updated according to actual conditions.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a method for depositing a refund according to the present application;
FIG. 2 is a second schematic flow chart of a method for depositing a refund according to the present application;
FIG. 3 is a schematic structural diagram of a cash back posting device provided by the present application;
fig. 4 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
At present, in a typical financial processing system, data update at a business level is generally consistent with data update at an accounting level of the financial system, that is, after a cash-back operation at the business level is successful, the data at the business level and the data at the accounting level are updated no matter whether cash flow of the cash-back operation is successfully credited or not. However, in the actual money-returning process, the completion of the money-returning operation at the business level cannot represent the return of the fund to be paid out, or the deposit is successful according to the business rules, which may cause inconsistency between the fund flow and the data flow at the system accounting level, thereby causing various problems. For example, when the business personnel performs a payment operation, after the client payment operation is successful, the business personnel sees a result returned by the system after the payment is successful, and the financial system also updates the financial data according to the result of the payment being successful. But the repayment is not in real time, so that the fund flow is inconsistent with the accounting data. If the fund of the repayment cannot be paid, fails to be paid or fails to be paid, rollback of the accounting data and rollback of the business data are forced, and system stability and data correctness are seriously affected.
In the related art, a fund flow-based refund entry method for updating business data and financial data exists, although complete consistency of the financial data and the fund flow is ensured, business data hysteresis inevitably occurs for non-real-time fund return operation of the fund in the account type, and the embarrassment that an operator cannot sense timely update of the data after the operation is finished is caused, so that the confusion of the business aspect is brought. In addition, if the client has a refund appeal again when the refund fund is in transit, the condition that the residual fund which should be collected and not received cannot be calculated by trial, the service function is seriously influenced, and potential risk of the customer complaint is brought
In order to solve the above problems, in the technical solution provided in this embodiment of the present application, for the dilemma of the service appeal and the system design, the service layer data and the accounting layer data are segmented from a system architecture level, and on the premise of ensuring the independence of service operation and the timely availability of operation result data, an actual payment view, an actual receipt view, a payable view and a receivable view are split in a daily accumulation increase and repayment counting and submitting manner for the system accounting layer, and a service-free attribute optimization design for real-time repayment management and control and accounting of the whole repayment process is implemented, and a standardized repayment entry processing model with mutually independent service and system accounting is finally implemented by embedding a mode of repayment audit and withdrawal and reimbursement in transit.
The method for depositing a refund according to the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
As shown in fig. 1, a method for refund posting provided in an embodiment of the present application may include thefollowing steps 101 and 102:
Wherein the refund operation request comprises at least one of: type of return, expected time to return
Illustratively, the money withdrawing operation is performed by a service operator on a service operation interface, and the service operator can select a money withdrawing mode on the service operation interface. According to the refund mode, the type of the refund can be determined, and in the case that the type of the refund is the non-real-time account-arriving refund, the system can also calculate the expected account-arriving time of the refund.
It should be noted that the service operator specifically needs to be determined based on a service scenario, for example, if a payment operation interface facing a customer is provided, the payment operation interface is handled by an ordinary user; if the operator is a related financial business operator, the operator is a financial operator; and if the background financial auditor is manually input, the background financial auditor is the background financial auditor and the like. The business roles may be different, depending on the scenario.
For example, after the business operator completes the operation on the business operation interface, the back-end finance system may receive a money return operation request of the money return operation. The refund operation request comprises a refund type of the current refund operation, and under the condition that the refund type is non-real-time account-arriving refund, the refund operation request also comprises expected account-arriving time of the refund of the non-real-time account-arriving refund.
It should be noted that the non-real-time account-finding fund can be a T +1 type fund. Namely, the money-returning operation is carried out on the same day, and the account can be found only after waiting for the next working day (T + 1).
Andstep 102, updating business data and accounting data according to the type of the refund and/or the predicted arrival time of the refund.
Wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
Illustratively, after the business operator completes the operation at the business level, the financial system updates the business data and the financial data according to the type of the refund included in the refund operation request and/or the expected arrival time of the refund.
Illustratively, for the refund operation with the refund type of real-time account arrival, the financial system can directly update the business data after the refund operation of the business operator is completed, namely directly update the data of the business operation interface, so that the business operator can conveniently check the result of the refund operation, and update the financial data after the refund is account arrival.
For the non-real-time account-returning operation, the financial system needs to further judge the effectiveness of the operation after the operation of the service operator finishes the operation of the return, update the service data after the operation of the return is executed, and update the accounting data after the return is received.
For example, the validity of the money return operation may be determined based on whether the money return operation is performed this time. When the money returning operation is executed, the money returning operation is determined to be effective. When the money withdrawing operation is invalid, the money withdrawing operation result is returned to the service operation interface, so that service operators can conveniently know the reason of the failure of the money withdrawing operation.
It can be understood that the refund posting method provided by the embodiment of the application updates the business data based on the payment result of the refund operation, and updates the accounting data only after the refund is billed.
Therefore, when a money return operation request is received, according to the money return type included in the money return operation request and/or the expected arrival time of the money return, the data of the business layer generated by the fund flow payment result and the ledger data of the fund flow payment arrival rule of the business are updated, and the ledger data of the business entry rule are met, so that after the money return operation of business personnel is successful, the data of the business layer and the data of the ledger layer can be updated according to actual conditions.
Optionally, in the embodiment of the present application, the calculated refund amount is different for refund operations with different refund types.
Illustratively, the fund withdrawal operation request further includes: the amount of money to be collected is collected. Before thestep 101, the method for depositing a refund provided by the embodiment of the present application may further include the following step 103:
and 103, calculating the amount to be collected of the refund according to the refund type and/or the expected arrival time of the refund.
In a possible implementation manner, the step 103 may specifically include the following step 103a or step 103 b:
and 103a, under the condition that the refund type is real-time account-finding refund, calculating the refund receivable amount according to the current date.
And 103b, under the condition that the type of the refund is non-real-time account-arriving refund, calculating the refund receivable amount according to the expected account-arriving time of the refund.
Wherein the return receivable amount includes at least one of: the fund, interest and overdue fee are charged for the refund.
For example, when the system calculates the amount of the receivable of the refund, the self and the overdue fees need to be calculated, and for the refund operation of the real-time account, the payment can be settled according to the current settlement date, namely, the self and the overdue fees can be settled according to the date of the current refund operation. For the non-real-time account-arriving refund operation, the interest and overdue cost also need to be calculated according to the expected account-arriving time.
It should be noted that non-real-time billing affects not only interest and overdue fees, but also all fees calculated based on billing results. For example, if a non-real-time reimbursement is made during the overdue period and a compensation operation is performed, and the default money is calculated based on the overdue fine of the interest, interest and the grace period, and the rules of counting head and counting tail are considered, the generation of the default money expense items and the calculation of the amount of the default money are influenced.
For example, when the non-real-time payment return operation date is 9 months and 30 days, due to holidays and other factors, the payment date is expected to be 10 months and 8 days, and interest and overdue fees need to be calculated to 10 months and 8 days instead of 9 months and 30 days.
Therefore, interest and overdue expenses can be calculated according to the actual arrival time of the refund, and the condition that the refund and the actual refund are inconsistent due to the delay of the refund arrival is avoided.
Optionally, in this embodiment of the application, for the real-time account-receiving refund and the non-real-time account-receiving refund, the business data and the accounting data may be updated in different updating manners.
For example, for a refund operation in which the refund mode is a real-time account, thestep 102 may include the following steps 102 a:
and 102a, updating the business data under the condition that the type of the refund is real-time account-returning refund, and updating the accounting data after the refund is received.
For example, in the case that the type of the return is a real-time account-finding return, the financial system may directly update the business data after receiving the return operation request, and update the accounting data after the return is found.
It can be understood that, because the account arrival time of the real-time account arrival refund is short, generally within 2 hours, the refund date of the current refund operation can be considered as the current date of the refund operation. Therefore, the calculation of interest and overdue fees is also settled according to the operation date of the money return.
For example, as shown in fig. 2, as a schematic flow chart of the processing of the money return operation by the financial system, after the financial system receives the request of the money return operation (S01), it is determined whether the money return type of the money return operation is the real-time billed money return operation (S02), when the money return type of the current money return operation is the real-time billed money return operation, the business data is directly updated (S06), and after the money return of the current money return operation is billed (S07), the business data is updated (S12), and then the current money return operation is ended (S13).
For example, for a refund operation with a refund mode of non-real-time account, it is further required to consider whether another refund operation is performed before the refund operation, that is, whether there is an in-transit refund, and thestep 102 may include the following step 102b1 or step 102b 2:
step 102b1, if the type of the refund is non-real-time account-receiving refund and there is an in-transit refund, if the expected account-receiving time of the refund is earlier than the expected account-receiving time of the in-transit refund, canceling the in-transit refund and resubmitting the in-transit refund based on the refund operation request; and updating the in-transit cash back information of the business layer, and updating the accounting data after the resubmitted in-transit cash back is sent to an account.
Step 102b2, if the refund type is non-real-time account-returning refund and there is an in-transit refund, if the expected account-returning time of the refund is not earlier than the expected account-returning time of the in-transit refund, canceling the refund operation indicated by the refund operation request, and updating the business data based on the result of the refund operation; updating the accounting data after the in-transit return is posted.
For example, in the embodiment of the present application, processing is mainly performed on a non-real-time account-arriving refund operation, and for the non-real-time account-arriving refund operation, it needs to be determined whether another refund operation has been performed before the current refund operation. If the in-transit money return exists, if the predicted account arrival time of the money return operation is not earlier than the predicted account arrival time of the in-transit money return, the money return operation is not necessarily executed, otherwise, the money return operation is executed, and the in-transit money return is cancelled.
It will be appreciated that for the expected due time of the present refund operation to be earlier than the expected due time of the in-transit refund operation, the financial system will be charged based on the refund due amount of the present refund operation since the refund due amount has been previously calculated from the expected due time and return the previously paid fee to the user.
For example, as shown in fig. 2, a schematic flow chart of processing a money return operation for the finance system is shown, when the finance system receives a money return operation request (S01), it is determined whether the money return type of the money return operation is a real-time account-finding money return operation (S02), and when the money return type of the money return operation is a non-real-time account-finding money return operation, it is determined whether another money return operation has been performed before the money return operation, that is, whether there is an in-transit money return (S03). If there is an in-transit return, it is determined whether the estimated due date of the present return operation is earlier than the estimated due date of the in-transit return (S04), and if the estimated due date of the present return operation is not earlier than the estimated due date of the in-transit return, the present return operation is cancelled (S05), and the transaction data is updated (S06). Moreover, because the operation is invalid, the financial system can update the accounting data after returning the account in the way.
If the expected due date of the present money return operation is earlier than the expected due date of the in-transit money return, the in-transit money return is cancelled, the present money return is executed (S08), and then the business data is updated based on the present money return operation (S09). Because the previous in-transit cash back has been revoked, the financial system needs to resubmit the in-transit cash back based on this time of the cash back operation (S10), and the in-transit cash back is sequentially posted based on the arrival time (S11). And the financial system updates the accounting data in sequence according to the time of returning money to account.
It should be noted that the difference between the real-time and non-real-time return payment processes is that after the financial system initiates payment, the financial system will directly and asynchronously notify the payment result for the real-time return payment process, and for the non-real-time return payment process, the financial system will asynchronously notify the payment result after the fund flow is confirmed.
For example, in the embodiment of the present application, for the non-real-time account-arriving and account-returning, the business data may be directly updated, and after the non-real-time account-arriving and account-returning are reached, the accounting data may be updated.
Exemplarily, thestep 102 may further include the following step 102b 3:
and step 102b3, updating the business data when the type of the return is non-real-time account-arriving return and no in-transit return exists, and updating the accounting data after the non-real-time account-arriving return is acknowledged.
Therefore, for the non-real-time account-arriving money-returning operation of the current money-returning operation, the consideration based on the reasonability of the expected account-arriving time is adopted, when the money-returning operation is in transit, the late account-arriving money-returning operation is cancelled, the first account-arriving money-returning operation is preferentially submitted, and the real-time property and the non-real-time property of the fund-arriving account are comprehensively considered, so that the fund cost of a client is reduced, and the powerful support of the system on the parallel money-returning operation is ensured.
The refund posting method provided by the application updates the business data based on the effectiveness of the refund operation, and updates the accounting data after the refund is posted, so that the consistency of the fund flow and the data flow is ensured. The problem that financial data is inconsistent with fund flow is thoroughly solved, and meanwhile, the business appeal that business financial visual angle data is obtained when seen and obtained when made is completely met.
It should be noted that, in the refund posting method provided in the embodiment of the present application, the execution main body may be a refund posting apparatus, or a control module in the refund posting apparatus for executing the refund posting method. The embodiment of the present application takes the refund posting apparatus as an example to execute the refund posting method, and the refund posting apparatus provided in the embodiment of the present application is described.
In the embodiments of the present application, the above-described methods are illustrated in the drawings. The method for depositing the refund is described by taking one drawing in the embodiment of the application as an example. In specific implementation, the refund posting method shown in each method drawing can also be implemented by combining any other drawing which can be combined and is illustrated in the above embodiments, and details are not repeated here.
The following description is provided for the present application, and the following description and the above-described refund posting method may be referred to correspondingly.
Fig. 3 is a schematic structural diagram of a refund posting apparatus provided in an embodiment of the present application, and as shown in fig. 3, the refund posting apparatus specifically includes:
areceiving module 301, configured to receive a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; adata updating module 302, configured to update business data and accounting data according to the type of the refund and/or the expected arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
Therefore, when a money return operation request is received, according to the money return type included in the money return operation request and/or the expected arrival time of the money return, the data of the business layer generated by the fund flow payment result and the ledger data of the fund flow payment arrival rule of the business are updated, and the ledger data of the business entry rule are met, so that after the money return operation of business personnel is successful, the data of the business layer and the data of the ledger layer can be updated according to actual conditions.
Optionally, the money return operation request further includes: the amount of money to be collected; the device further comprises: and the calculating module 303 is configured to calculate the amount to be collected for the refund according to the type of the refund and/or the expected arrival time of the refund.
Optionally, the calculating module 303 is specifically configured to calculate the amount receivable for the refund according to the current date when the refund type is a real-time billed refund; or, the calculating module 303 is specifically configured to calculate the amount to be received for the refund according to the estimated arrival time of the refund when the type of the refund is the non-real-time arrival refund; wherein the return receivable amount includes at least one of: the fund, interest and overdue fee are charged for the refund.
Therefore, interest and overdue expenses can be calculated according to the actual arrival time of the refund, and the condition that the refund and the actual refund are inconsistent due to the delay of the refund arrival is avoided.
Optionally, thedata updating module 302 is specifically configured to update the business data when the type of the return is a real-time account-receiving return, and update the accounting data after the return is received.
Optionally, thedata updating module 302 is specifically configured to, if the type of the fund return is a non-real-time account return and there is an in-transit fund return, revoke the in-transit fund return if the expected account time of the fund return is earlier than the expected account time of the in-transit fund return, and resubmit the in-transit fund return based on the fund return operation request; updating the in-transit cash back information of the business layer, and updating the accounting data after the resubmitted in-transit cash back is sent to an account; or, thedata updating module 302 is specifically configured to, when the type of the fund return is a non-real-time income fund return and there is an in-transit fund return, if the expected arrival time of the fund return is not earlier than the expected arrival time of the in-transit fund return, cancel the fund return operation indicated by the fund return operation request, and update the business data based on the fund return operation result; updating the accounting data after the in-transit return is posted.
Optionally, thedata updating module 302 is specifically configured to update the business data when the type of the return is a non-real-time posted return and there is no in-transit return, and update the accounting data after the non-real-time posted return is posted.
Therefore, for the non-real-time account-arriving money-returning operation of the current money-returning operation, the consideration based on the reasonability of the expected account-arriving time is adopted, when the money-returning operation is in transit, the late account-arriving money-returning operation is cancelled, the first account-arriving money-returning operation is preferentially submitted, and the real-time property and the non-real-time property of the fund-arriving account are comprehensively considered, so that the fund cost of a client is reduced, and the powerful support of the system on the parallel money-returning operation is ensured.
The refund posting device provided by the application updates the business data based on the effectiveness of the refund operation, and updates the accounting data after the refund is posted, thereby ensuring the consistency of the fund flow and the data flow. The problem that financial data is inconsistent with fund flow is thoroughly solved, and meanwhile, the business appeal that business financial visual angle data is obtained when seen and obtained when made is completely met.
Fig. 4 illustrates a physical structure diagram of an electronic device, which may include, as shown in fig. 4: a processor (processor)410, acommunication Interface 420, a memory (memory)430 and acommunication bus 440, wherein theprocessor 410, thecommunication Interface 420 and thememory 430 are communicated with each other via thecommunication bus 440.Processor 410 may invoke logic instructions inmemory 430 to perform a method of check-back posting, the method comprising: receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
In addition, the logic instructions in thememory 430 may be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 method according to the embodiments of the present application. 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.
In another aspect, the present application also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the method of check-back posting provided by the above methods, the method comprising: receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
In yet another aspect, the present application further provides a non-transitory computer readable storage medium having stored thereon a computer program that when executed by a processor is implemented to perform the method of providing a refund entry, the method comprising: receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund; updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund; wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
The above-described embodiments of the apparatus are merely illustrative, and 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 modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A method for depositing a refund, comprising:
receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund;
updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund;
wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
2. The method of claim 1, wherein the refund operation request further comprises: the amount of money to be collected;
before the receiving of the refund operation request, the method further comprises:
and calculating the amount of the refund which is to be collected according to the refund type and/or the expected arrival time of the refund.
3. The method of claim 2, wherein calculating the refund receivable amount based on the refund type and/or the refund expected to be due comprises:
under the condition that the refund type is real-time account-finding refund, calculating the refund receivable amount according to the current date;
or,
under the condition that the type of the refund is non-real-time account-arriving refund, calculating the amount which should be received by the refund according to the expected account-arriving time of the refund;
wherein the return receivable amount includes at least one of: the fund, interest and overdue fee are charged for the refund.
4. The method according to any one of claims 1 to 3, wherein the updating of the business data and the accounting data according to the type of the return and/or the expected arrival time of the return comprises:
and updating the business data under the condition that the type of the refund is the real-time account-returning refund, and updating the accounting data after the refund is received.
5. The method according to any one of claims 1 to 3, wherein the updating of the business data and the accounting data according to the type of the return and/or the expected arrival time of the return comprises:
if the type of the refund is a non-real-time account-in refund and an in-transit refund exists, if the expected account-in time of the refund is earlier than the expected account-in time of the in-transit refund, the in-transit refund is cancelled, and the in-transit refund is resubmitted based on the refund operation request; updating the in-transit cash back information of the business layer, and updating the accounting data after the resubmitted in-transit cash back is sent to an account;
or,
under the condition that the refund type is non-real-time account-returning refund and in-transit refund exists, if the expected account-returning time of the refund is not earlier than the expected account-returning time of the in-transit refund, the refund operation indicated by the refund operation request is cancelled, and the business data is updated based on the refund operation result; updating the accounting data after the in-transit return is posted.
6. The method according to any one of claims 1 to 3, wherein the updating of the business data and the accounting data according to the type of the return and/or the expected arrival time of the return comprises:
and updating the business data under the condition that the type of the return is non-real-time account-arriving return and no in-transit return exists, and updating the accounting data after the non-real-time account-arriving return is received.
7. A cash back posting apparatus, characterized in that the apparatus comprises:
the receiving module is used for receiving a money return operation request; the cash back operation request comprises at least one of the following items: the type of the refund, and the expected arrival time of the refund;
the data updating module is used for updating business data and financial data according to the type of the refund and/or the predicted arrival time of the refund;
wherein the type of refund comprises: real-time account-based and non-real-time account-based refunds; the service data comprises: generating service level data based on the fund flow payment result; the accounting data includes: and the fund flow meets the account book data of the entry rule of the business after being paid to the account.
8. The apparatus of claim 7, wherein the refund operation request further comprises: the amount of money to be collected; the device further comprises:
and the calculating module is used for calculating the amount of the refund which is to be received according to the refund type and/or the expected arrival time of the refund.
9. A non-transitory computer readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps of the method of refund posting according to any one of claims 1 to 6.
10. A computer program product comprising computer program/instructions, characterized in that the computer program/instructions, when executed by a processor, implement the steps of the method for refund entry of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111136598.3ACN114092203A (en) | 2021-09-27 | 2021-09-27 | Method, device, storage medium and computer program product for checking and debiting |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111136598.3ACN114092203A (en) | 2021-09-27 | 2021-09-27 | Method, device, storage medium and computer program product for checking and debiting |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114092203Atrue CN114092203A (en) | 2022-02-25 |
Family
ID=80296260
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111136598.3APendingCN114092203A (en) | 2021-09-27 | 2021-09-27 | Method, device, storage medium and computer program product for checking and debiting |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114092203A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114819937A (en)* | 2022-04-11 | 2022-07-29 | 北京理房通支付科技有限公司 | Repayment cancellation method, apparatus, computer program product and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109544151A (en)* | 2018-10-11 | 2019-03-29 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of gathering confirmation |
| CN109949144A (en)* | 2019-03-22 | 2019-06-28 | 深圳前海微众银行股份有限公司 | Entry processing method, apparatus, device and computer-readable storage medium |
| CN110189217A (en)* | 2019-06-04 | 2019-08-30 | 合肥博耀信息技术有限公司 | A kind of client's returned money processing method |
- 2021
- 2021-09-27CNCN202111136598.3Apatent/CN114092203A/enactivePending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109544151A (en)* | 2018-10-11 | 2019-03-29 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of gathering confirmation |
| CN109949144A (en)* | 2019-03-22 | 2019-06-28 | 深圳前海微众银行股份有限公司 | Entry processing method, apparatus, device and computer-readable storage medium |
| CN110189217A (en)* | 2019-06-04 | 2019-08-30 | 合肥博耀信息技术有限公司 | A kind of client's returned money processing method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114819937A (en)* | 2022-04-11 | 2022-07-29 | 北京理房通支付科技有限公司 | Repayment cancellation method, apparatus, computer program product and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20110125616A1 (en) | Buffered Bookkeeping | |
| CN110458691B (en) | Pre-loan risk monitoring method and device | |
| CN113128991B (en) | Public settlement account fund accounting system and working method thereof | |
| KR20210119263A (en) | Method of managing card sales data of affiliate store using electronic device and electronic device thereof | |
| CN111444213B (en) | Ledger clearing system and method based on credit business | |
| JP2009110125A (en) | Inter-account settlement processing apparatus using electronic record receivable and inter-account settlement processing method | |
| CN114092203A (en) | Method, device, storage medium and computer program product for checking and debiting | |
| CN119130685A (en) | Financial shared center receivables and payables integration method, system and storage medium thereof | |
| US20150161690A1 (en) | Automated refund of travel document subsequent to involuntary exchange | |
| CN113657846A (en) | A method and system for enterprise fund management under a financial sharing model | |
| JP2004133514A (en) | Credit erasure processor, credit erasure processing method, computer program and record medium | |
| JP5008820B2 (en) | Credit card company system | |
| JP5889379B1 (en) | Electronic record receivable collateral management service system and method | |
| CN115456747B (en) | Automatic intelligent account settling method and device for ERP system and storage medium | |
| KR101500832B1 (en) | Withholding agency method and system performing the same | |
| EP2881901A1 (en) | Automated refund of travel document subsequent to involuntary exchange | |
| JP6760874B2 (en) | Information processing equipment and programs | |
| CN116167770A (en) | A transaction concurrent processing method and device for a bank's high-frequency hotspot pool account | |
| JP6183867B1 (en) | Notional pooling system and notional pooling method | |
| JP2002329155A (en) | Off-setting settlement processing system | |
| CN115310981A (en) | Transaction data processing method, device, electronic device and storage medium | |
| CN114819937B (en) | Repayment cancellation method, device, computer program product and storage medium | |
| JP6704973B2 (en) | Information processing device and program | |
| CN109255695A (en) | The loan repayment treating method and apparatus of online trade platform | |
| JP2001331759A (en) | Obligation management 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 |