Configurable networking collection intra-bank clearing method and device
By implementing configurable channel and cycle management, the problems of rigid logic and difficulty in expansion in traditional clearing methods have been solved, realizing the flexibility and scalability of clearing methods, reducing operational risks, and improving financial processing efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-30
- Publication Date
- 2026-04-07
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Traditional clearing methods involve strong coupling between clearing logic and code, resulting in long development cycles, high system risks, difficulty in adapting to diverse scenarios, poor scalability, and high maintenance costs.
By using a configuration-driven approach and leveraging channel configuration tables, period configuration tables, and account configuration tables, flexible management of clearing rules and periods can be achieved, automatically identifying channel identifiers and completing fund allocation according to account rules.
It achieves flexibility and scalability in the clearing method, reduces operational risks, improves financial processing efficiency, and adapts to the business needs of complex accounting scenarios.
Smart Images
Figure CN121810380A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of internet finance technology, specifically to a configurable online clearing and sorting method and apparatus for in-bank collection. Background Technology
[0002] Currently, traditional clearing methods have tightly coupled clearing logic and code. Adding new channels or adjusting the cycle requires modifying the core program, resulting in long development cycles and potential system risks. Revenue sharing rules rely on hard coding, making it difficult to adapt to diverse scenarios (such as proportional revenue sharing for different channels or tiered fee rates). Changes require full-process testing. The system's scalability is limited. When facing business surges, adding clearing dimensions requires refactoring the architecture, resulting in a response speed that lags behind business needs. At the same time, rule conflicts are prone to occur when multiple channels are running in parallel, and maintenance costs increase exponentially with business growth.
[0003] To effectively address the issues of "fixed rules and difficulty in expansion" in traditional clearing methods, especially suitable for multi-channel and multi-scenario collection and clearing businesses in financial institutions, there is an urgent need for a clearing solution that replaces hard-coded logic with configuration-driven approaches to solve the flexibility issues of clearing methods and cycles, achieving configurable and controllable online clearing and clearing. Summary of the Invention
[0004] To address the aforementioned issues, this application provides a configurable online collection and in-bank clearing method and apparatus.
[0005] The technical solution provided in this application is as follows.
[0006] Firstly, this application provides a configurable online clearing and settlement method for interbank collection, including: Configure the channel-related information for receiving payments through the UnionPay system and write it into the channel configuration table; the channel information includes the channel name, unique identifier, business type, clearing cycle ID, default billing rule group, and enabled status; Configure a cycle configuration table; the cycle configuration table includes the type of collection and settlement cycle of the online collection and settlement system, parameters, and associated settlement rules; Set revenue sharing rules; Transaction triggers matching; Clearing and sorting will be carried out periodically; Results verification and archiving.
[0007] In one possible implementation, the clearing cycle type includes: a first statistical interval: from the second clearing time two days before the benchmark date to the second clearing time one day before the benchmark date; and a second statistical interval: from 0:00 one day before the benchmark date to 24:00 one day before the benchmark date. The parameters include the number of clearing operations, whether or not advance payment is required, and the execution time. The associated clearing rules include binding the corresponding accounting calculation logic ID.
[0008] In one possible implementation, the transaction trigger matching includes: Obtain transaction details, extract channel identifier, amount, reconciliation flag, settlement flag, clearing flag, and batch number; Retrieve the associated cycle and revenue sharing rules from the channel configuration table based on the channel identifier; The channel status, cycle, and revenue sharing rules have all been confirmed to be valid.
[0009] In one possible implementation, the periodic clearing includes: The clearing process is triggered according to the triggering rules of the clearing schedule task; The clearing process is divided into two categories: those that allow advance payment and those that do not. For those that allow advance payment, the clearing period is the day before the benchmark date, and the clearing is summarized on the benchmark date. For those that do not allow advance payment, either one clearing or two clearings are used. Execute fund allocation.
[0010] Furthermore, for projects where advance payment is not permitted, the aforementioned single clearing includes: clearing summary at the second clearing session on the day before the benchmark date, with the clearing period being from the second clearing session two days before the benchmark date to the second clearing session on the day before the benchmark date; For cases where advance payment is not permitted, the two clearing processes include: The first clearing will be conducted from the first clearing session one day prior to the benchmark date of the clearing cycle to the second clearing session one day prior to the benchmark date. The second clearing will be carried out from the second clearing session on the day before the base date of the clearing cycle to the first clearing session on the base date itself.
[0011] In one possible implementation, the result verification and archiving includes: Check whether the daily clearing transaction records have been successfully recorded, and whether the clearing transaction amount in the aggregated channels is consistent with the clearing general ledger; verify whether the number of clearing transaction records per day is consistent with the business requirements. Verify that the daily settlement amount matches the corresponding transaction record; Save the clearing transaction records to the audit report; If the verification fails, an alarm is triggered and a retry mechanism is started, and the reason for the error is recorded.
[0012] Secondly, this application provides a configurable online collection and clearing device for in-bank transactions, comprising: The first configuration module is used to configure the channel-related information for the collection and reception of goods through the UnionPay to be written into the channel configuration table; the channel information includes channel name, unique identifier, business type, clearing cycle ID, default billing rule group and flag enabled status; The second configuration module is used to configure the cycle configuration table; the cycle configuration table includes the network-connected collection and settlement cycle type, parameters and associated settlement rules. The settings module is used to set the revenue sharing rules; The trigger module is used for transaction trigger matching; The clearing module is used to perform clearing on a periodic basis; The verification module is used for result verification and archiving.
[0013] Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the configurable online collection and intra-bank clearing method as described in the first aspect.
[0014] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the configurable online collection and in-bank clearing method as described in the first aspect.
[0015] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the configurable online collection and in-bank clearing method as described in the first aspect.
[0016] The beneficial effects of this application are as follows: The method provided in this application enables flexible management of clearing rules and cycles for different channels through channel configuration tables, cycle configuration tables, and account configuration tables in the database. During transaction processing, the method provided in this application can automatically identify channel identifiers, trigger the clearing process according to preset cycles, and complete fund allocation according to account rules.
[0017] The method provided in this application is particularly suitable for businesses that require complex revenue sharing scenarios, and can significantly improve financial processing efficiency and reduce operational risks. Attached Figure Description
[0018] Figure 1 A flowchart illustrating the configurable online clearing and settlement method for in-bank collection provided in this application embodiment; Figure 2 A flowchart illustrating the framework of the configurable online clearing and settlement method for in-bank collection provided in this application embodiment; Figure 3 A schematic diagram of the structure of the configurable online collection and clearing device provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0019] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0020] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.
[0021] In the description of this application, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid unnecessarily obscuring the description of this application. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.
[0022] The existing clearing methods suffer from insufficient flexibility, rigid rules, difficulty in expansion, and low efficiency, making it difficult to meet the needs of subsequent business growth, and the maintenance costs are high.
[0023] In view of this, this application provides a configurable online clearing and settlement method for in-bank collection.
[0024] See Figure 1 The configurable online clearing and settlement method for interbank collection provided in this application includes the following steps: S101. Configure the channel-related information for receiving payments through the online payment collection service and write it into the channel configuration table; the channel information includes the channel name, unique identifier, business type, clearing cycle ID, default billing rule group, and enabled status.
[0025] In one possible implementation, S101 includes: S101a. Enter basic information: Fill in core fields such as channel name, unique identifier (channel_id), and business type.
[0026] S101b, Associated Configuration Items: Bind the corresponding clearing cycle ID and default accounting rule group, and mark whether it is enabled.
[0027] S101c, Approval and Activation: Submit the configuration to the approval process. Once approved, it will be written into the channel configuration table and activated.
[0028] It should be noted that in the business process of the clearing system, tagging is an operation that adds identification fields or status labels to objects such as transaction data, clearing tasks, and channel status. The purpose is to achieve data classification, process control, and risk identification, ensuring that the clearing logic is traceable and controllable. For example, 0 - no advance payment allowed, 1 - advance payment allowed.
[0029] S102. Configure the cycle configuration table; the cycle configuration table includes the network-connected collection and settlement cycle type, parameters and associated settlement rules.
[0030] In one possible implementation, the clearing cycle type includes: a first statistical interval: from the second clearing time two days before the benchmark date to the second clearing time one day before the benchmark date; and a second statistical interval: from 0:00 on the day before the benchmark date to 24:00 on the day before the benchmark date.
[0031] Understandably, within a clearing period (e.g., from 23:00 on day T to 23:00 on day T+1), not all transactions are settled at the end of the day. To improve capital efficiency, especially to allow merchants to receive partial revenue earlier, the system typically sets up at least two clearing sessions, for example: The first clearing session (daytime session): processes a portion of the transactions made in the morning, enabling early settlement of funds. The second clearing session (night session): processes most of the remaining transactions of the day, as well as transactions after the day cut, and completes the main and final settlement.
[0032] It should be noted that the clearing time is arranged by the NetsUnion Clearing Center. Currently, the first clearing session is at 9:00 AM and the second clearing session is at 3:00 PM.
[0033] In one possible implementation, the parameters include the number of clearing operations, whether or not advance payment is required, and the execution time. In one possible implementation, the associated clearing rules include binding the corresponding accounting calculation logic ID.
[0034] Specifically, S102 includes: S102a, Select the online collection period type: clr_circle clearing cycle: The first statistical interval is: 1 - ((T-2) day H2:00 - (T-1) day H2:00); The second statistical interval: 2 - ((0:00 on day (T - 1)) - (24:00 on day (T - 1))); S102b. Configuration parameter details: clr_cnt Clearing count: 1 - (clearing once a day), 2 - (clearing twice a day); clr_ads Whether to advance funds for clearing: 0 - No advance funds allowed, 1 - Advance funds allowed; clr_time Execution time point: 1 - (1:00), 2 - (H1:00), 3 - (H2:00); H1 < H2; S102c. Associated clearing rules: Bind the corresponding profit sharing calculation logic ID and save it to the cycle configuration table.
[0035] It should be noted that T represents the reference date, (T - 1) day represents the day before the reference date, H1:00 represents the first settlement time, and H2:00 represents the second settlement time.
[0036] In this step, the cycle configuration table (is the core rule center of the clearing system, and its function is to decouple the clearing business logic from the code and uniformly manage the related rules, parameters, and permissions of clearing through a configurable method to support the automated, standardized, and flexible operation of the clearing process.
[0037] S103. Configure the account configuration table and set the profit sharing rules.
[0038] In a possible implementation, S103 includes: S103a. Configure the account configuration table: Enter the profit sharing account number, account type (such as commission account, principal account), and priority.
[0039] S103b. Set the profit sharing rules: Sort and clear by the priority of the channels, and the channel with a higher priority is cleared first; the collected and summarized amount of the channel will be transferred to the profit sharing account number and the commission account according to the preset commission ratio.
[0040] S104. Transaction trigger matching.
[0041] In a possible implementation, S104 includes: S104a. Obtain the transaction flow (epcc_paymsg), extract the channel identifier (channel_id), amount (tran_amt), reconciliation flag (collate_flag), settlement flag (clear_flag), clearing flag (clr_flag), and batch number (batch_id); S104b. Retrieve the associated cycle and profit sharing rules from the channel configuration table according to the channel identifier; S104c: Confirm that the channel status, cycle, and revenue sharing rules are all valid.
[0042] Specifically, the online payment collection is divided into 24 reconciliation batches per day, with each batch associated with one hour of transaction data, thus corresponding to 24 batch numbers per day.
[0043] Reconciliation batches for the day: T-batch1, T-batch2...T-batch24.
[0044] The reconciliation batches from the previous day: (T-1)-batch1, (T-1)-batch2...(T-1)-batch24.
[0045] Tomorrow's reconciliation batches: (T+1)-batch1, (T+1)-batch2...(T+1)-batch24.
[0046] Note: batch1: represents the batch from 0:00 to 1:00 in a day, and so on.
[0047] S105. Perform clearing and sorting according to the cycle.
[0048] In one possible implementation, S105 includes: S105a. Trigger the clearing process according to the triggering rules of the clearing schedule task; S105b. Clearing is carried out for modes that allow and do not allow advance payment; for modes that allow advance payment, the clearing period is the day before the benchmark date, and the clearing is summarized on the benchmark date; for modes that do not allow advance payment, one clearing or two clearing methods are adopted. S105c, Execute fund allocation.
[0049] Furthermore, in S105b, for projects where advance payment is not permitted, the one-time clearing includes: clearing summary at the second clearing time on the day before the benchmark date, and the clearing period is from the second clearing time on the two days before the benchmark date to the second clearing time on the day before the benchmark date.
[0050] Furthermore, in S105b, for cases where advance payment is not permitted and settlement is performed twice, the following applies: The first clearing will be conducted from the first clearing session one day prior to the benchmark date of the clearing cycle to the second clearing session one day prior to the benchmark date. The second clearing will be carried out from the second clearing session on the day before the base date of the clearing cycle to the first clearing session on the base date itself.
[0051] Specifically, S105 includes: (1) Trigger the clearing according to the triggering rules of the clearing timed task.
[0052] (2) Sorting out different modes: (2.1) Clearing up the allowed advance payment model: On day T, all reconciliation batches of day (T-1) are grouped according to payment channels, and the total transaction amount of each payment channel is calculated.
[0053] In this mode, clearing can begin as soon as the transaction batches are reconciled, and the clearing period can be customized. Here, it's temporarily set to 00:00 on (T-1) day - 24:00 on (T-1) day. This clearing method also doesn't need to consider holidays. Clearing summary at 1:00 AM on day T: select sum(tran_amt),channel_id from epcc_paymsg where batch_id in ( (T-1)-batch1,(T-1)-batch2,(T-1)-batch3,(T-1)-batch4, (T-1)-batch5,(T-1)-batch6,(T-1)-batch7,(T-1)-batch8, (T-1)-batch9,(T-1)-batch10,(T-1)-batch10,(T-1)-batch11, (T-1)-batch12,(T-1)-batch13,(T-1)-batch14,(T-1)-batch15, (T-1)-batch16,(T-1)-batch17,(T-1)-batch18,(T-1)-batch19, (T-1)-batch20,(T-1)-batch21,(T-1)-batch22,(T-1)-batch23, (T-1)-batch24); It should be noted that `select sum(tran_amt),channel_id from epcc_paymsg wherebatch_id in` means: from the transaction log (epcc_paymsg), filter out records whose batch number (batch_id) meets the specified condition, group them by channel identifier (channel_id), and then calculate the sum of the amount (tran_amt) of each group.
[0054] (2.2) For the no-advance-funding model: adopt a one-time or two-time clearing method. The clearing flow not only requires reconciliation, but also requires settlement. This method needs to take into account holidays. If a holiday occurs, the clearing needs to be postponed, and the flow of all previous holidays will be added when clearing on the first working day after the holiday.
[0055] The advantage of double clearing over single clearing is that it allows for faster settlement of funds through the distribution channels. Clearing is done as soon as funds are received, accelerating capital turnover. Single clearing combines two clearing sessions into one.
[0056] (2.2.1) First clearing: During the second clearing session on the day before the benchmark date, all reconciliation batches within the clearing period are grouped according to payment channels, and the total transaction amount of each payment channel is calculated; the clearing period is from the second clearing session two days before the benchmark date to the second clearing session on the day before the benchmark date. For example, the clearing and summarizing is completed at H2:00 on day (T-1), and the clearing period is from H2:00 on day (T-2) to H2:00 on day (T-1). The algorithm is as follows: select sum(tran_amt),channel_id from epcc_paymsg where batch_id in ( (T-2)-batch16, (T-2)-batch17, (T-2)-batch18, (T-2)-batch19, (T-2)-batch20, (T-2)-batch21, (T-2)-batch22, (T-2)-batch23, (T-2)-batch24, (T-1)-batch1, (T-1)-batch2, (T-1)-batch3, (T-1)-batch4, (T-1)-batch5 (T-1)-batch6, (T-1)-batch7, (T-1)-batch8, (T-1)-batch9, (T-1)-batch10 (T-1)-batch11, (T-1)-batch12, (T-1)-batch13, (T-1)-batch14, (T-1)-batch15); The clearing and settlement process begins at 01:00 on day (T), with the clearing period from 00:00 on day (T-1) to 24:00 on day (T-1). The algorithm is the same as that for day (T-1).
[0057] (2.2.2) Secondary clearing: Clearing immediately after initial clearing. The first clearing will be carried out during the second clearing session on the day before the benchmark date. All reconciliation batches within the clearing period will be grouped by payment channel, and the total transaction amount for each payment channel will be calculated. The clearing period is from the first clearing session on the day before the benchmark date to the second clearing session on the day before the benchmark date.
[0058] For example, the algorithm for the clearing cycle from H1:00 on day (T-1) to H2:00 on day (T-1) is as follows: select sum(tran_amt),channel_id from epcc_paymsg where batch_id in ( (T-1)-batch9,(T-1)-batch10,(T-1)-batch10,(T-1)-batch11, (T-1)-batch12,(T-1)-batch13,(T-1)-batch14,(T-1)-batch15); The second clearing process will be conducted during the first clearing session on the benchmark date. All reconciliation batches within the clearing period will be grouped by payment channel, and the total transaction amount for each payment channel will be calculated. The clearing period is from the second clearing session on the day before the benchmark date to the first clearing session on the benchmark date.
[0059] The clearing cycle is from (T-1) day (H2):00 to (T) day H1:00, and the algorithm is as follows: select sum(tran_amt),channel_id from epcc_paymsg where batch_id in ( (T-1)-batch16,(T-1)-batch17,(T-1)-batch18,(T-1)-batch19, (T-1)-batch20,(T-1)-batch21,(T-1)-batch22,(T-1)-batch23, (T-1)-batch24, T-batch1,T-batch2,T-batch3,T-batch4,T-batch5,T-batch6,T-batch7,T-batch8, T-batch9); (3) Funds transfer: Generate clearing instructions according to the channel, send them to the core system to execute the actual fund allocation, and register the clearing flow; if the core accounting fails, multiple sending is allowed, with an interval of 30 minutes.
[0060] It should be noted that this step employs different cycle configurations for different funding models to meet the varying clearing requirements of different channels. For funding-permitted models, a single clearing method is used, which ensures that the channel clears its assets before final settlement. For funding-disallowed models, either a single clearing or a double clearing method is used. A single clearing requires two settlements to be completed before clearing is permitted, while a double clearing involves clearing one settlement and then clearing the assets in the next.
[0061] S106. Result verification and archiving.
[0062] In one possible implementation, S106 includes: S106a. Check whether the daily clearing transaction records have been successfully recorded, and whether the clearing transaction amount in the summary channel is consistent with the clearing general ledger; verify whether the number of clearing transaction records per day is consistent with the business requirements. S106b, Verify whether the daily settlement amount is consistent with the corresponding transaction record; S106c, Save the clearing transaction records (including channel, account, amount, and time) to the audit report; S106d. If the verification fails, trigger an alarm and start the retry mechanism, and record the reason for the error.
[0063] Furthermore, S106a can be set to execute after the second clearing session of the day, and S106b can be set to execute after the first clearing session of the day.
[0064] The following describes a configurable online collection and settlement device provided in this application. The configurable online collection and settlement device described below and the configurable online collection and settlement method described above can be referred to in correspondence.
[0065] Figure 3 This is a schematic diagram of a configurable online collection and clearing device provided in an embodiment of this application, as shown below. Figure 3 As shown, it includes: a first configuration module 31, a second configuration module 32, a setting module 33, a triggering module 34, a clearing module 35, and a verification module 36, wherein: The first configuration module 31 is used to configure the channel-related information of the collection and reception of the network to be written into the channel configuration table; the channel information includes channel name, unique identifier, business type, clearing cycle ID, default billing rule group and flag enabled status; The second configuration module 32 is used to configure the cycle configuration table; the cycle configuration table includes the network-connected collection and settlement cycle type, parameters and associated settlement rules; Module 33 is used to set the revenue sharing rules; Trigger module 34 is used for transaction trigger matching; The clearing module 35 is used to perform clearing on a periodic basis; Verification module 36 is used for result verification and archiving.
[0066] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include a processor 410, a communications interface 420, a memory 430, and a communications bus 440. The processor 410, communications interface 420, and memory 430 communicate with each other via the communications bus 440. The processor 410 can call logical instructions from the memory 430 to execute a configurable online collection and clearing method within the bank.
[0067] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0068] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute a configurable online collection and clearing method provided by the above methods.
[0069] In another aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform a configurable online collection and settlement method provided by the methods described above.
[0070] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0071] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0072] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A configurable online collection and settlement method for in-bank transactions, characterized in that, include: Configure the channel-related information for receiving payments through the UnionPay system and write it into the channel configuration table; the channel information includes the channel name, unique identifier, business type, clearing cycle ID, default billing rule group, and enabled status; Configure a cycle configuration table; the cycle configuration table includes the type of collection and settlement cycle of the online collection and settlement system, parameters, and associated settlement rules; Set revenue sharing rules; Transaction triggers matching; Clearing and sorting will be carried out periodically; Results verification and archiving.
2. The sorting method according to claim 1, characterized in that, The clearing cycle types include: the first statistical interval: from the second clearing time two days before the benchmark date to the second clearing time the day before the benchmark date; the second statistical interval: from 0:00 the day before the benchmark date to 24:00 the day before the benchmark date; The parameters include the number of clearing operations, whether or not advance payment is required, and the execution time. The associated clearing rules include binding the corresponding accounting calculation logic ID.
3. The sorting method according to claim 1, characterized in that, The transaction trigger matching includes: Obtain transaction details, extract channel identifier, amount, reconciliation flag, settlement flag, clearing flag, and batch number; Retrieve the associated cycle and revenue sharing rules from the channel configuration table based on the channel identifier; The channel status, cycle, and revenue sharing rules have all been confirmed to be valid.
4. The sorting method according to claim 1, characterized in that, The periodic clearing includes: The clearing process is triggered according to the triggering rules of the clearing schedule task; The clearing process is divided into two categories: those that allow advance payment and those that do not. For those that allow advance payment, the clearing period is the day before the benchmark date, and the clearing is summarized on the benchmark date. For those that do not allow advance payment, either one clearing or two clearings are used. Execute fund allocation.
5. The sorting method according to claim 4, characterized in that, For projects where advance payment is not permitted, the aforementioned "one-time clearing" includes: the clearing summary at the second clearing session on the day before the benchmark date, with the clearing period being from the second clearing session two days before the benchmark date to the second clearing session on the day before the benchmark date; For cases where advance payment is not permitted, the two clearing processes include: The first clearing will be conducted from the first clearing session one day prior to the benchmark date of the clearing cycle to the second clearing session one day prior to the benchmark date. The second clearing will be carried out from the second clearing session on the day before the base date of the clearing cycle to the first clearing session on the base date itself.
6. The sorting method according to claim 1, characterized in that, The result verification and archiving include: Check whether the daily clearing transaction records have been successfully recorded, and whether the clearing transaction amount in the aggregated channels is consistent with the clearing general ledger; verify whether the number of clearing transaction records per day is consistent with the business requirements. Verify that the daily settlement amount matches the corresponding transaction record; Save the clearing transaction records to the audit report; If the verification fails, an alarm is triggered and a retry mechanism is started, and the reason for the error is recorded.
7. A configurable networked collection and settlement device for in-bank transactions, characterized in that, include: The first configuration module is used to configure the channel-related information for the collection and reception of goods through the UnionPay to be written into the channel configuration table; the channel information includes channel name, unique identifier, business type, clearing cycle ID, default billing rule group and flag enabled status; The second configuration module is used to configure the cycle configuration table; the cycle configuration table includes the network-connected collection and settlement cycle type, parameters and associated settlement rules. The settings module is used to set the revenue sharing rules; The trigger module is used for transaction trigger matching; The clearing module is used to perform clearing on a periodic basis; The verification module is used for result verification and archiving.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the configurable online collection and in-bank clearing method as described in any one of claims 1 to 6.
9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the configurable online collection and in-bank clearing method as described in any one of claims 1 to 6.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the configurable online collection and in-bank clearing method as described in any one of claims 1 to 6.