Bill sending method and device, electronic equipment, storage medium and program product

Abstract

The application discloses a kind of bill sending method, device, electronic equipment, storage medium and program product, belong to computer field.The method comprises: in response to received first download request, query the first data generated in the first time period of first customer system, and the first bill configuration corresponding to first customer system, wherein the first download request is used to request downloading the bill of first customer system, and the first download request includes bill configuration demand;First bill configuration is determined based on the business type of first customer system;According to bill configuration demand, first bill configuration is adjusted, and second bill configuration is obtained;According to first data and second bill configuration, the first bill of first customer system is generated;First bill is sent to first customer system.The application can realize the individualization of bill push.

Description

Technical Field

[0001] This disclosure relates to the field of data storage technology, specifically to a method, apparatus, electronic device, storage medium, and program product for sending account statements. Background Technology

[0002] As the integrated financial services system gradually develops, the number of enterprise clients connected to the platform is increasing. When it comes to accounting, it is necessary to provide account statements for clients to use for reconciliation.

[0003] Existing technology provides fixed-configuration account statements, which are not flexible enough to meet customers' personalized needs. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, storage medium, and program product for sending account statements, which can solve the problem of fixed account statement configuration in the prior art.

[0005] In a first aspect, embodiments of this application provide a method for sending account statements, the method comprising:

[0006] In response to the received first download request, the system queries the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system. The first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements. The first statement configuration is determined based on the business type of the first customer system.

[0007] The first statement configuration is adjusted according to the statement configuration requirements to obtain the second statement configuration;

[0008] Based on the first data and the second statement configuration, generate the first statement for the first customer system;

[0009] Send the first statement of account to the first customer system.

[0010] In one possible implementation,

[0011] The second statement configuration includes a second statement type and a second statement field;

[0012] The step of generating the first statement for the first customer based on the first data and the second statement configuration includes:

[0013] Obtain the first statement template corresponding to the second statement type;

[0014] Delete all statement fields in the first statement template except for the second statement field to obtain the second statement template;

[0015] Retrieve the second data from the first data that corresponds to the second statement field;

[0016] Write the second data into the second statement template to generate the first statement.

[0017] In one possible implementation, before sending the first statement to the first customer system, the statement sending method further includes:

[0018] In response to the first download request, send the first batch number;

[0019] Store the first statement to the target path;

[0020] Send the first statement to the first customer's system, including:

[0021] In response to the received second download request, which includes the first batch number, the target path is sent;

[0022] In response to the received access request for the target path, the first statement of account is sent to the first customer system.

[0023] In one possible implementation,

[0024] The first statement configuration includes a first statement type and a first statement field;

[0025] Before responding to the received first download request and querying the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system, the method further includes:

[0026] The registration page is displayed, which includes identifiers corresponding to at least two statement types and identifiers corresponding to at least two statement fields for each statement type. The at least two statement types include a first statement type, and the at least two statement fields of the first statement type include the first statement field.

[0027] In response to the customer's selection input for a first identifier and a second identifier received from the first customer system, the statement type corresponding to the first identifier is determined to be the first statement type corresponding to the first customer system, and the statement field corresponding to the second identifier is determined to be the first statement field corresponding to the first customer system, wherein the first identifier is an identifier among at least two identifiers corresponding to statement types, and the second identifier is an identifier among at least two identifiers corresponding to the first statement type.

[0028] In one possible implementation, after determining the statement type corresponding to the first identifier as the first statement type corresponding to the first customer system, and determining the statement field corresponding to the second identifier as the first statement field corresponding to the first customer system, the method further includes:

[0029] In response to a received query request, output at least two identifiers corresponding to the statement types, and at least two identifiers corresponding to the statement fields of each statement type. The query request is used to request a query of the statement configuration corresponding to the first customer system. The statement configuration includes statement types and statement fields. The identifiers corresponding to the statement configurations are in the first display state, and the other identifiers are in the second display state.

[0030] In one possible implementation, after responding to a received query request and outputting identifiers corresponding to at least two statement types, and identifiers corresponding to at least two statement fields for each statement type, the method further includes:

[0031] When a customer in the first customer system modifies the statement configuration of the first customer system, obtain the third identifier and the fourth identifier in the first display state, wherein the third identifier is the identifier among the identifiers corresponding to at least two statement types, and the fourth identifier is the identifier among the identifiers corresponding to at least two statement fields of the first statement type.

[0032] The statement type corresponding to the third identifier is determined as the first statement type corresponding to the first customer system, and the statement field corresponding to the fourth identifier is determined as the first statement field corresponding to the first customer system.

[0033] Secondly, embodiments of this application provide a statement sending device, the device comprising:

[0034] The query module is used to respond to a received first download request to query the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system. The first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements. The first statement configuration is determined based on the business type of the first customer system.

[0035] The adjustment module is used to adjust the first statement configuration according to the statement configuration requirements to obtain the second statement configuration;

[0036] The generation module is used to generate the first statement of the first customer system based on the first data and the second statement configuration;

[0037] The sending module is used to send the first statement of account to the first customer system.

[0038] Thirdly, this application provides a platform enterprise whose equipment includes:

[0039] Processor and memory storing computer program instructions;

[0040] When the processor executes computer program instructions, it implements the statement sending method as described in the first aspect.

[0041] Fourthly, embodiments of this application provide a computer storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, they implement the statement sending method as described in the first aspect.

[0042] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the statement sending method as described in the first aspect.

[0043] In this embodiment, a statement can be pushed to a first customer system in response to a received first download request for a statement. When pushing a statement to the first customer system, a first statement configuration corresponding to the first customer system can be queried first. This first statement configuration is determined based on the business type of the first customer system. Then, the first statement configuration can be adjusted using the statement configuration carried in the first download request to obtain a second statement configuration. Using the second statement configuration and the first data generated by the first customer system within a first time period, a statement for the first customer system is generated, and then the generated statement is pushed. It is evident that the statement pushed to the customer system in this embodiment is determined based on the statement configuration corresponding to the customer system. Thus, the statements pushed to different customer systems can be different, enabling personalized customization of the statements. Furthermore, when pushing a statement in response to a download request, the statement configuration of the statement pushed to the customer system can be adaptively adjusted based on the statement configuration requirements in the download request, ensuring that the pushed statement meets the statement configuration requirements. This improves the reliability and flexibility of the statement push. Attached Figure Description

[0044] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating the statement sending method provided in an embodiment of this application;

[0046] Figure 2This is one of the structural schematic diagrams of the statement sending device provided in the embodiments of this application;

[0047] Figure 3 This is a schematic diagram of the structure of the statement sending device provided in the embodiments of this application;

[0048] Figure 4 This is the second structural schematic diagram of the statement sending device provided in the embodiments of this application. Detailed Implementation

[0049] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0050] In this document, relational terms such as "first," "second," etc., are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0051] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of national laws and regulations.

[0052] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0053] Platform companies: Platform companies refer to those that have built a platform for the generation, browsing, and interaction of information, providing services to customers on the platform. Platform companies can include: integrated financial service systems and front-end systems.

[0054] Integrated Financial Services System: A system that provides integrated financial services such as settlement and clearing to platform enterprise clients.

[0055] Front end: The interaction device between platform enterprise customers and the integrated financial service system.

[0056] Statement of Reconciliation: After the platform enterprise customers interact with the integrated financial service system, different data will be generated under different business scenarios. In order to ensure data consistency, the integrated financial service system generates a statement of reconciliation for the platform enterprise customers to use for reconciliation.

[0057] The method for sending account statements provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0058] See Figure 1 , Figure 1 This is a flowchart of the statement sending method provided in this application embodiment. The statement sending method of this application embodiment can be applied to platform enterprises, and further, to the integrated financial service system of platform enterprises. Figure 1 As shown, the method for sending a statement may include the following steps:

[0059] S101: In response to the received first download request, query the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system, wherein the first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements; the first statement configuration is determined based on the business type of the first customer system.

[0060] The first customer system is any one of the customer systems that has a cooperative relationship with the platform enterprise.

[0061] In this embodiment of the application, if the platform enterprise determines that it needs to push the statement to the first customer system, it can execute S101 to S103 to generate the statement for the first customer system.

[0062] Platform companies can determine whether to push account statements to the first customer's system if the first condition is met. The first condition can include any of the following:

[0063] 1) Received a statement inquiry request or download request from the first customer's system;

[0064] 2) The end-of-day push time to the first customer system.

[0065] For ease of description, the scenario in case 1) where the statement is pushed will be referred to as the first scenario, or real-time push scenario; and the scenario in case 2) where the statement is pushed will be referred to as the second scenario, or end-of-day push scenario.

[0066] In some embodiments, a statement query request or download request from the first customer system may be generated by the user of the first customer system through interaction with the front end. In other embodiments, a statement query request or download request from the first customer system may be triggered by the user of the first customer system interacting with the first customer system, causing the first customer system to send the request to the platform enterprise.

[0067] In some embodiments, users of the customer system can configure, query, and modify statements on the front-end display interface of the platform enterprise. The integrated financial services system generates corresponding statements after reviewing and approving the statements performed by users of the customer system, and then pushes the statements of the users of the customer system to the customer system.

[0068] In other embodiments, users of the customer system can also send statement sending requests to the integrated financial services system from the customer system. The integrated financial services system generates corresponding statements based on the statement sending request configuration information about statements sent by the user of the customer system and sends them to the customer system.

[0069] The end time of the first time period can be the time when the first condition is met, and the duration of the first time period can be a preset duration.

[0070] In the end-of-day push scenario, users of the customer system can wait for the integrated financial services system to automatically generate the corresponding account statements at the end of the day.

[0071] In step 101, the first condition is specifically manifested as 1).

[0072] It should be noted that the embodiments of this application do not limit the query sequence of the first data and the first statement configuration.

[0073] The first data refers to the data generated by the interaction between the first customer system and the integrated financial services system. The integrated financial services system receives this first data and generates corresponding account statements. Because data generated in different business scenarios is inconsistent, to ensure data consistency and reliability, the integrated financial services system needs to generate account statements based on this first data for users of the customer system to reconcile accounts, thereby improving the reliability of internal data within the platform enterprise.

[0074] In this embodiment of the application, the platform enterprise pre-stores the statement configuration corresponding to each customer system. The statement configuration includes statement type and statement field. Therefore, the platform enterprise can query the statement type (i.e., the first statement type) and statement field (the first statement field) corresponding to the first customer system.

[0075] The reconciliation statement configuration for each customer system can be determined based on the business type of each customer system.

[0076] In some embodiments, the statement configuration for each customer system can be configured by the users of each customer system based on their own business type. For example, the first statement type and the first statement fields can be selected by the users of the first customer system on the front-end device based on the business type of the first customer system.

[0077] In other embodiments, the statement configuration for each customer system can be configured independently by the platform enterprise based on the pre-obtained business types corresponding to each customer system. Optionally, before querying the first statement type and first statement fields corresponding to the first customer system, the method further includes:

[0078] Query the business type of the first customer system;

[0079] Using the first correspondence and the business type of the first customer system, determine the first statement type and the first statement field corresponding to the first customer system;

[0080] Wherein, the first correspondence is the correspondence between business type, statement type and statement field; the first statement type is the statement type in the first correspondence that corresponds to the business type of the first customer system, and the first statement field is the statement field in the first correspondence that corresponds to the business type of the first customer system.

[0081] In this embodiment, a first correspondence can be pre-stored. Thus, after obtaining the business type of a customer system, the corresponding statement configuration for that customer system can be obtained by searching the first correspondence. In other words, the statement configuration for each customer system can be configured independently by the platform enterprise based on the pre-obtained business type of each customer system.

[0082] In this way, the reconciliation statement configuration for the customer's system can be determined without manual operation, and the reconciliation statement configuration of the customer's system can be made to meet business needs, thereby improving the efficiency of the reconciliation statement configuration for the customer's system.

[0083] S102: Adjust the first reconciliation statement configuration according to the reconciliation statement configuration requirements to obtain the second reconciliation statement configuration.

[0084] In this embodiment of the application, the first download request may carry a statement configuration requirement, which can represent the user's latest requirements for the statement configuration of the first customer system. The statement configuration requirement may include at least one of the following: statement type requirement and statement field requirement.

[0085] After obtaining the statement configuration requirements from the first download request, the first statement configuration can be adjusted using these requirements to obtain the second statement configuration.

[0086] The first statement configuration includes a first statement type and a first statement field. The second statement configuration includes a second statement type and a second statement field. It is understood that the second statement type and the first statement type can be the same or different statement types. The first statement field and the second statement field can be completely different, or they can include at least one identical statement field; the specific details can be flexibly determined based on the statement configuration requirements carried in the first download request.

[0087] In a specific implementation, when the statement type requirement is used to indicate that the statement type corresponding to the first customer system is changed to the second statement type, step S102 may include: changing the statement type corresponding to the first customer system from the first statement type to the second statement type, where the first statement type and the second statement type are different.

[0088] When the statement field requirement is used to indicate the statement field corresponding to the second statement type, or to change the statement field corresponding to the first statement type, such as by adding or removing statement fields, step S102 may include: changing the statement field corresponding to the first customer system to the second statement field. In this case, at least one of the first statement field and the second statement field is different.

[0089] In this way, the statement pushed to the first customer system can meet the user's latest requirements for the statement configuration of the first customer system, thereby improving the reliability and flexibility of statement push.

[0090] S103: Generate the first statement of the first customer system based on the first data and the second statement configuration.

[0091] The first statement must meet the following requirements: the type of the first statement is the same as the second statement type; the fields of the first statement include the fields of the second statement; and the data of the first statement includes the data corresponding to the fields of the second statement.

[0092] Based on the business scenarios used by platform enterprise customers, the business type of the business scenario is determined, and the corresponding second statement type and second statement field are configured according to the business type. Based on the first data, the data corresponding to the second statement field is written into the statement, which can generate the first statement of the first customer system, so as to meet the customized needs of customers for statements of different business types in different business scenarios.

[0093] S104: Send the first statement to the first customer's system.

[0094] The first statement can be an electronic document in any readable format. The first statement generated by the first customer system is sent to the first customer system. The first customer system receives the first statement for customer reconciliation. The first statement generated through the integrated financial services system is sent to the first customer system, realizing information exchange between the platform enterprise's internal systems.

[0095] This application provides a method for sending account statements, which can push account statements to a first customer system in response to a received first download request for an account statement. When pushing an account statement to the first customer system, a first account statement configuration corresponding to the first customer system can be queried first. This first account statement configuration is determined based on the business type of the first customer system. Then, the first account statement configuration can be adjusted using the account statement configuration carried in the first download request to obtain a second account statement configuration. Using the second account statement configuration and first data generated by the first customer system within a first time period, an account statement for the first customer system is generated, and then the generated account statement is pushed. It is evident that the account statements pushed to the customer system in this application embodiment are determined based on the account statement configuration corresponding to the customer system. Thus, the account statements pushed to different customer systems can be different, enabling personalized customization of account statements. Furthermore, when pushing an account statement in response to a download request, the account statement configuration of the account statement pushed to the customer system can be adaptively adjusted based on the account statement configuration requirements in the download request, ensuring that the pushed account statement meets the account statement configuration requirements. This improves the reliability and flexibility of account statement pushing.

[0096] In some embodiments, the second statement configuration includes a second statement type and a second statement field;

[0097] The step of generating the first statement for the first customer based on the first data and the second statement configuration includes:

[0098] Obtain the first statement template corresponding to the second statement type;

[0099] Delete all statement fields in the first statement template except for the second statement field to obtain the second statement template;

[0100] Retrieve the second data from the first data that corresponds to the second statement field;

[0101] Write the second data into the second statement template to generate the first statement.

[0102] The first data may include the second data, and the first data may also include data corresponding to the statement fields that the customer has not selected.

[0103] In some embodiments, a first statement template corresponding to the second statement type can be obtained based on the second statement type. The second statement template is obtained by deleting statement fields that the customer has not selected from the first statement template. First, the first statement template corresponding to the second statement type can be obtained, and statement fields other than the second statement fields can be deleted to obtain the second statement template. Then, the first data corresponding to the first statement can be written into the second statement template to generate the first statement.

[0104] In other embodiments, a first reconciliation statement template corresponding to the second reconciliation statement type can be obtained based on the first statement type. First data can be obtained and filled into the reconciliation statement fields in the first reconciliation statement template to obtain alternative reconciliation statements. Then, the fields in the alternative reconciliation statements other than the second reconciliation statement fields and their corresponding data are deleted, and finally the first reconciliation statement is obtained.

[0105] For the data writing process, we can obtain the second data corresponding to the second statement field selected by the customer, determine the target data to be written in the second data, find the row number corresponding to the second statement field of the target data in the second statement template, find the column number corresponding to the target data to be written, and write the target data according to the position corresponding to the found row number and column number. All the second data is written into the second statement template. At this point, the field and data configuration in the second statement template is completed, and the first statement can be generated.

[0106] A second statement template is generated by analyzing the second statement fields selected by the customer system's users. These fields can be customized by the customer system's users, meeting their needs and improving their user experience. Furthermore, by locating the corresponding fields of the target data within the second statement template, all the second data can be sequentially written to the corresponding positions in the second statement fields, improving data writing efficiency.

[0107] In some embodiments, before sending the first statement of account to the first customer system, the method may further include:

[0108] In response to the query request, send the first batch number;

[0109] Store the first statement to the target path;

[0110] Sending the first statement to the first customer's system may include:

[0111] In response to the received second download request, which includes the first batch number, the target path is sent;

[0112] In response to the received access request for the target path, the first statement of account is sent to the first customer system.

[0113] This embodiment corresponds to the first scenario described above.

[0114] The query requests received by the integrated financial services system can be sent from the front-end devices or from the primary customer system. Specifically, users of the customer system can send query requests to the integrated financial services system through the front-end devices. Users of the customer system can also send query requests to the integrated financial services system through their own systems. These query requests can include information such as the name of the primary statement and the query time.

[0115] In some embodiments, a user in the customer system proactively sends a query request. Upon receiving the query request, the platform enterprise's integrated financial services respond by integrating information such as the first data, the first statement type, and the first statement fields in the system to determine the target path of the first statement and generate a task to generate the first statement. The target path of the first statement is located within the integrated financial services system. After generating the task, the platform enterprise sends the first batch number corresponding to the first statement to the front-end device. The front-end device can query the generation status of the first statement file based on a second download request using the first batch number. If the first statement has been generated (i.e., saved to the target path), the integrated financial services system sends the target path to the front-end device. The front-end device then sends a target path access request to the integrated financial services system based on the target path to retrieve the corresponding first statement and send it to the first customer system. If the front-end device queries the generation status of the first statement based on a second download request using the first batch number, but the first statement has not yet been generated, the front-end device will periodically query the generation status of the first statement based on the batch number until the statement is sent to the first customer system. Therefore, users in the customer system can proactively send query requests via the front-end device or the first customer system to obtain the first statement in real time.

[0116] In other embodiments, users of the customer system can also wait for the platform enterprise's integrated financial services to generate a corresponding first statement at the end of the day based on the statement configuration information within the system, and send the first statement to the first customer system, with the customer receiving the first statement periodically. This embodiment corresponds to the second scenario described above.

[0117] This application embodiment can send query requests through the front-end device of the platform enterprise's integrated financial services or the platform enterprise's customer system to generate the first statement, and has multiple channels for statement request query; users in the customer system can actively send query requests, so that the platform enterprise's integrated financial services can respond to the query requests and push the first statement to the first customer system in real time; users in the customer system can also passively wait for the generation of the first statement; the platform enterprise's integrated financial services can automatically generate the first statement generation task for users in the customer system at the end of the day and push the first statement to the first customer system on a regular basis.

[0118] The integrated financial services system receives the first download request from a user in the customer system, generates a query request in response to the first download request, sends a first batch number in response to the query request, and stores the first statement in the target path. The user in the customer system queries the generation status of the first statement in the first batch number. Since the first statement stores a large amount of data, the target path can be sent to the user in the customer system, allowing them to view the generation status of the first statement in the first batch by accessing the target path. The generated first statement in the first customer system is then sent back to the first customer system.

[0119] By sending the first download request for the first statement, the configuration of the first statement can be viewed. After confirming the configuration, the first statement is stored in the target path. The download status of the statement in the target path can be viewed by the batch number, which makes it convenient for users of the customer's system to view the download status of the statement in real time.

[0120] In some embodiments, before querying the first statement type and the first statement fields corresponding to the first customer system, the method further includes:

[0121] The registration page is displayed, which includes identifiers corresponding to at least two statement types and identifiers corresponding to at least two statement fields for each statement type. The at least two statement types include a first statement type, and the at least two statement fields of the first statement type include the first statement field.

[0122] In response to the customer's selection input for a first identifier and a second identifier received from the first customer system, the statement type corresponding to the first identifier is determined to be the first statement type corresponding to the first customer system, and the statement field corresponding to the second identifier is determined to be the first statement field corresponding to the first customer system, wherein the first identifier is an identifier among at least two identifiers corresponding to statement types, and the second identifier is an identifier among at least two identifiers corresponding to the first statement type.

[0123] On the registration interface, both the identifier for the statement type and the identifier for the statement field can be displayed simultaneously on the same screen. Alternatively, the identifier for the statement type can be displayed on the first screen. When the cursor is moved to the target identifier for a target statement type, the screen can display some statement fields corresponding to that type. Clicking the target identifier for that statement type triggers a second screen, which may include the identifiers for the statement fields corresponding to the target statement type. There can be one or more of these first and second identifiers.

[0124] In one example, on the front-end device of the integrated financial services system, multiple identifiers corresponding to statement types can be displayed. Users of the customer system can independently select one or more identifiers corresponding to the desired statement type. The one or more identifiers are the first identifiers, and the statement type corresponding to the first identifier is the first statement type. In response to the customer's click operation, the front-end device displays the identifiers corresponding to multiple statement fields of the first statement type. Users of the customer system select one or more identifiers of the desired statement field as the second identifiers, and the statement field corresponding to the second identifier is the identifier of the first statement field.

[0125] By displaying the registration page, users of the customer system can be presented with selected and unselected statement type identifiers and statement field identifiers, providing them with a variety of statement types and statement fields to choose from, reflecting the diversity of statement configuration.

[0126] In one embodiment, after determining the statement type corresponding to the first identifier as the first statement type corresponding to the first customer system, and determining the statement field corresponding to the second identifier as the first statement field corresponding to the first customer system, the method may further include:

[0127] In response to a received query request, output at least two identifiers corresponding to the statement types, and at least two identifiers corresponding to the statement fields of each statement type. The query request is used to request a query of the statement configuration corresponding to the first customer system. The statement configuration includes statement types and statement fields. The identifiers corresponding to the statement configurations are in the first display state, and the other identifiers are in the second display state.

[0128] On the front-end interface of the platform enterprise financial integrated service system, after a user in the customer system selects the first statement type and the first statement field, the user actively sends a query request to the front-end device. Upon receiving the query request, the front-end device responds by displaying the corresponding identifier for the statement type. The identifier for the statement type in the statement configuration corresponding to the first customer system is in the first display state, indicating that the statement type has been selected by the user in the customer system. Some statement types also have identifiers in a second display state, indicating that the statement type has not been selected by the user in the customer system. When a user clicks on the identifier of a target statement type in the first display state, the front-end responds by displaying the identifiers corresponding to the statement fields within that target statement type. The identifiers for the statement fields also have two display states: the first display state indicates that the statement field has been selected by the customer, and the second display state indicates that the statement field has not been selected by the user in the customer system. The first display state can be characterized by bold text or a prominent display, while the second display state can be characterized by reduced clarity or an unclickable state.

[0129] A user in the customer system sends an inquiry request to the integrated financial services system, which receives and responds to the inquiry request, and sends the generated first statement to the first customer system.

[0130] In one example, after a user in the customer system selects the corresponding statement configuration on the front-end device (which may include statement type and statement fields), clicking the "Query Virtual or Real" button sends a query request to the integrated financial services system. The system receives and responds to the query request by displaying one or more statement type identifiers on the first interface of the front-end device. These identifiers can have two display states: the identifier for the statement type selected by the customer system user is in the first display state, and the identifier for the statement type not selected by the customer system user is in the second display state. When a customer system user clicks on the statement type identifier in the first display state, the front-end device responds by displaying one or more statement field identifiers on the second interface of the front-end device. Again, the statement field identifiers can have two display states: the identifier for the statement field selected by the customer system user is in the first display state, and the identifier for the statement field not selected by the customer system user is in the second display state.

[0131] Users of the first customer system can check the selected statement configuration by querying it. This allows them to determine whether the statement configuration matches the user's application scenario and ensures that there are no omissions or multiple selections. They can also promptly edit any problematic statement configurations to improve the accuracy of statement delivery.

[0132] In one embodiment, after responding to a received query request and outputting identifiers corresponding to at least two statement types, and identifiers corresponding to at least two statement fields for each statement type, the method further includes:

[0133] When a customer in the first customer system modifies the statement configuration of the first customer system, obtain the third identifier and the fourth identifier in the first display state, wherein the third identifier is the identifier among the identifiers corresponding to at least two statement types, and the fourth identifier is the identifier among the identifiers corresponding to at least two statement fields of the first statement type.

[0134] The statement type corresponding to the third identifier is determined as the first statement type corresponding to the first customer system, and the statement field corresponding to the fourth identifier is determined as the first statement field corresponding to the first customer system.

[0135] The integrated financial services system can obtain the third and fourth identifiers of the modified statement configuration in the first display state by receiving modification commands from users of the first customer system on the front-end device regarding the identifiers of the statement configuration; the integrated financial services system can also receive modification commands sent by users of the first customer system on the first customer system.

[0136] Before the customer made the modification, the statement configuration was as follows: the statement type corresponding to the first identifier was determined to be the first statement type corresponding to the first customer system, and the statement field corresponding to the second identifier was determined to be the first statement field corresponding to the first customer system. After the customer made the modification, the statement configuration was as follows: the statement type corresponding to the third identifier was determined to be the first statement type corresponding to the first customer system, and the statement field corresponding to the fourth identifier was determined to be the first statement field corresponding to the first customer system. Specifically, before the customer made the modification, the statement configuration had the first statement type and the first statement field identified by the first identifier and the second identifier, respectively. After the user in the first customer system modified the corresponding statement configuration, the statement configuration could be changed so that the first statement type and the first statement field were identified by the third identifier and the fourth identifier, respectively.

[0137] If the statement type and statement fields are not displayed on the same screen, the front-end device displays multiple labels for the statement type on the first screen. Customers can click the virtual or physical "Edit" button to put the multiple labels for the statement type on the first screen into an editable state. Customer system users can uncheck a statement type according to their current needs, that is, move the label of the statement type that is in the first display state to the second display state; customer system users can also check a statement type according to their current needs, which will move the label of the statement type that is in the second display state to the first display state.

[0138] Similarly, the front-end device displays multiple labels for the statement fields on the second interface. Users of the customer system can click the virtual or physical "Edit" button to put the multiple labels for the statement fields on the second interface into an editable state. Users of the customer system can uncheck a statement field according to their current needs, that is, move the label in the statement field that is in the first display state to the second display state; users of the customer system can also check a statement field according to their current needs, which will move the label in the statement field that is in the second display state to the first display state.

[0139] If the statement type and statement field are displayed on the same screen, you need to uncheck or add the statement type and statement field separately on one screen, and move the marker of the statement type and statement field that is in the first display state to the second display state. Customers can also check one or more statement types and statement fields according to their current needs, which will change the marker of the statement type that is in the second display state to the first display state.

[0140] In one example, after a user in the customer system modifies the first statement type in the statement configuration, clicking the third identifier corresponding to the modified first statement type displays the statement field corresponding to the first statement type on the second interface of the front-end device. The customer system user can then reselect this statement field, and the reselected statement becomes the first statement field, with its corresponding identifier set as the fourth identifier. The modified statement configuration requires system approval to take effect. This approval process prevents formatting errors in the statement or ensures that the statement configuration meets the business type of the customer system user. The modified statement configuration can override the previous configuration. After the front-end device sends a query request to the integrated financial services system, the system responds with the modified statement configuration displayed in response to the query request.

[0141] By querying the business type based on the first customer system, the configuration of the first statement type and fields can be determined. The configured first statement type and fields can be checked and confirmed. Once confirmed, a statement is generated. If configuration issues are found during the confirmation process, the statement type and fields can be reselected, allowing for more flexible configuration of the statement type and fields. Configuration issues may include incorrect statement type configurations and incomplete, excessive, or incorrect selection of statement fields.

[0142] Users of the first customer system can modify the statement configuration to adapt to changes in business scenarios, reflecting the versatility of statement configuration. This configurable approach significantly reduces development costs and improves the responsiveness to customer application needs.

[0143] It should be noted that the various optional implementation methods described in the embodiments of this application can be combined with each other or implemented individually without conflict, and the embodiments of this application do not limit this.

[0144] The following example illustrates the bill sending method provided in this application.

[0145] This application proposes a statement sending method, apparatus, electronic device, storage medium, and program product. The basic idea of ​​this application is: by querying the first statement type configured by the customer in the first customer system and the first statement field corresponding to the first statement type, and after querying the first data, a first statement can be generated and sent to the first customer system. In order to meet the application needs of the users in the first customer system through a configuration method and improve the user experience of the users in the first customer system.

[0146] Its specific implementation method is as follows Figure 2 As shown:

[0147] Platform companies can include: integrated financial service systems and front-end systems.

[0148] Integrated Financial Services System: A system that provides integrated financial services such as settlement and clearing to platform enterprise clients.

[0149] Front end: The interaction device between platform enterprise customers and the integrated financial service system.

[0150] The first customer system refers to any one of at least one customer system that has a cooperative relationship with the platform enterprise. In one example...

[0151] The front-end devices of the integrated financial services system can display a "Platform Enterprise Customer Registration" page, allowing customers to add platform configuration information. The "Information Services" page offers various statement types for customers to choose from. After signing up for the platform enterprise's integrated financial services, customers can select their desired statement type on the "Information Services" page. Customer system users can query, modify, and delete their selected statement configurations on the "Information Services" page. Additions, modifications, and deletions require approval to take effect. The platform enterprise's integrated financial services system pushes daily statements to customers based on their selected effective statements. Statement configurations can include statement type and statement fields.

[0152] The "Information Service" page can display various statements, but account managers can only download the statement types and fields selected by the users in the customer system. New statement configurations can be generated by pushing statements at the end of the day.

[0153] Platform companies can provide users with a variety of statement sending services, such as: platform statement configuration and maintenance, platform statement configuration query, and statement query and download.

[0154] Platform statement configuration and maintenance: Customer system users could access the "Information Service" page on the front-end device of the integrated financial services system. After selecting information and saving on the "Information Service" page, the platform's statement configuration and maintenance service would be invoked, and the system would save the user-configured statement. This interface is now obsolete; the platform's enterprise registration statement request interface is responsible for implementing this part.

[0155] Platform statement configuration query: When employees of platform companies view or review statement configurations through employee channels, they will call the platform statement configuration query service, and the system will return the statement configured by the platform customer. This interface is reserved, but is only used as an internal interface.

[0156] Statement Query and Download: The statement query and download service can download various statements. Upon receiving the download request for the first time, the system initiates an asynchronous automatic task to generate the corresponding statement, places it in the specified path, and matches it with the batch number of the statement on the front end. The front end can check whether the file has been generated completely based on the batch number. If it has, the page redirects to the corresponding path where the statement was generated. If the statement has not yet been generated, the front end needs to periodically poll based on the batch number.

[0157] When setting platform parameters on their devices, users of the customer system can select the necessary statements and fields for the platform and save them to the platform statement settings table in the database.

[0158] When users of the daily automated tasks and customer system trigger the generation of reconciliation statements on the front end, they can first query the data of the corresponding reconciliation statement, then query which reconciliation statement fields have been selected on the platform, and then retrieve the data of the selected reconciliation statement fields and write them to the file.

[0159] If users of the customer system later find that certain fields are no longer needed, they can modify the configured statement through the front-end device.

[0160] When a user in the customer system modifies the statement configuration on the front-end device, they can first query which fields have been selected in the configured statement, then match it with all fields, mark the selected fields as selected, and mark the unselected fields as unselected, and then display the statement configuration on the front-end page.

[0161] Customer system users can reselect saved statements on their front-end devices and save the reselected statement configuration to the database, which can overwrite the old statement configuration. The platform company's end-of-day automatic task will generate the corresponding statement based on the new statement configuration the next time it generates a statement.

[0162] Based on the statement sending method provided in the above embodiments, this application also provides specific implementations of the statement sending device. Please refer to the following embodiments.

[0163] See Figure 3 The statement sending device 300 provided in this application embodiment may include:

[0164] The query module 301 is used to respond to the received first download request to query the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system. The first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements. The first statement configuration is determined based on the business type of the first customer system.

[0165] The adjustment module 302 is used to adjust the first statement configuration according to the statement configuration requirements to obtain the second statement configuration;

[0166] The generation module 303 is used to generate a first statement of account for the first customer system based on the first data and the second statement of account configuration.

[0167] The sending module 304 is used to send the first statement of account to the first customer system.

[0168] In some embodiments, the second statement configuration includes a second statement type and a second statement field; the statement sending device 300 further includes a first acquisition module, a deletion module, and a second acquisition module.

[0169] The first acquisition module is used to acquire the first statement template corresponding to the second statement type;

[0170] The delete module is used to delete all statement fields in the first statement template except for the second statement fields, to obtain the second statement template.

[0171] The second acquisition module is used to acquire the second data in the first data that corresponds to the second statement field;

[0172] The generation module is also used to write the second data into the second statement template to generate the first statement.

[0173] In some embodiments, the first statement configuration includes a first statement type and a first statement field; the statement sending device 300 further includes a storage module.

[0174] The sending module is also used to send the first batch number in response to the first download request;

[0175] The storage module is used to store the first statement to the target path;

[0176] The sending module is also used to send the target path in response to a received second download request including the first batch number;

[0177] The sending module is also used to send a first statement to the first customer system in response to a received access request for the target path.

[0178] In some embodiments, the statement sending device 300 further includes a display module and a determination module.

[0179] The display module is used to display the registration page, wherein the registration page includes identifiers corresponding to at least two statement types, and identifiers corresponding to at least two statement fields of each statement type, wherein the at least two statement types include a first statement type, and the at least two statement fields of the first statement type include the first statement field;

[0180] The determining module is configured to, in response to a received selection input from a customer in the first customer system for a first identifier and a second identifier, determine the statement type corresponding to the first identifier as the first statement type corresponding to the first customer system, and determine the statement field corresponding to the second identifier as the first statement field corresponding to the first customer system, wherein the first identifier is an identifier among at least two identifiers corresponding to statement types, and the second identifier is an identifier among at least two identifiers corresponding to the first statement type.

[0181] In some embodiments, the statement sending device 300 further includes an output module.

[0182] The output module is used to respond to the received query request by outputting the identifiers corresponding to at least two statement types, and the identifiers corresponding to at least two statement fields for each statement type. The query request is used to request the query of the statement configuration corresponding to the first customer system. The statement configuration includes statement type and statement fields. The identifiers corresponding to the statement configuration are in the first display state, and the other identifiers are in the second display state.

[0183] In some embodiments, the statement sending device 300 includes:

[0184] The acquisition module is also used to acquire the third identifier and the fourth identifier in the first display state when the customer of the first customer system modifies the statement configuration of the first customer system. The third identifier is the identifier among the identifiers corresponding to at least two statement types, and the fourth identifier is the identifier among the identifiers corresponding to at least two statement fields of the first statement type.

[0185] The determination module is also used to determine the statement type corresponding to the third identifier as the first statement type corresponding to the first customer system, and to determine the statement field corresponding to the fourth identifier as the first statement field corresponding to the first customer system.

[0186] The statement sending device provided in this application embodiment can achieve... Figure 1 The various processes implemented by the bill sending device in the method embodiment will not be described again here to avoid repetition.

[0187] Figure 4 A schematic diagram of the hardware structure for sending account statements provided in an embodiment of this application is shown.

[0188] The platform enterprise may include a processor 401 and a memory 402 storing computer program instructions.

[0189] Specifically, the processor 401 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0190] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 402 is non-volatile solid-state memory.

[0191] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0192] The processor 401 implements any of the bill sending methods in the above embodiments by reading and executing computer program instructions stored in the memory 402.

[0193] In one example, the platform enterprise may also include a communication interface 403 and a bus 410. For example, Figure 3 As shown, the processor 401, memory 402, and communication interface 403 are connected through bus 410 and complete communication with each other.

[0194] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0195] Bus 410 includes hardware, software, or both, that couples components of a billing sending device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 410 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0196] In addition, in conjunction with the statement sending method in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the statement sending methods in the above embodiments.

[0197] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0198] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0199] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0200] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0201] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for sending account statements, characterized in that, A financial services system applied to a platform enterprise, wherein the platform enterprise's financial services system pre-stores at least one customer system's corresponding statement configuration, the method comprising: The registration page is displayed on the front-end device of the financial integrated service system of the platform enterprise. The registration page includes identifiers corresponding to at least two statement types and identifiers corresponding to at least two statement fields of each statement type. The at least two statement types include a first statement type, and the at least two statement fields of the first statement type include a first statement field. In response to the received selection input from the customer in the first customer system for the first identifier and the second identifier, the statement type corresponding to the first identifier is determined as the first statement type corresponding to the first customer system, and the statement field corresponding to the second identifier is determined as the first statement field corresponding to the first customer system, wherein the first identifier is the identifier among the identifiers corresponding to the at least two statement types, and the second identifier is the identifier among the identifiers corresponding to the at least two statement fields of the first statement type; In response to a first download request received from a first customer system or a first download request generated by a customer of the first customer system through interaction with the front end, the system queries the first data generated by the first customer system within a first time period, and the first statement configuration corresponding to the first customer system. The first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements. The first statement configuration is determined based on the business type of the first customer system. The first customer system is any one of at least one customer system that has a cooperative relationship with the platform enterprise. The statement configuration requirements represent the latest requirements for the statement configuration of the first customer system, and the statement configuration requirements include statement field requirements, which are used to indicate the addition or removal of statement fields. The first statement configuration is adjusted according to the statement configuration requirements to obtain the second statement configuration. The first statement configuration includes a first statement type and a first statement field, and the second statement configuration includes a second statement type and a second statement field. Obtain the first statement template corresponding to the second statement type; Delete all statement fields in the first statement template except for the second statement field to obtain the second statement template; Retrieve the second data from the first data that corresponds to the second statement field; Write the second data into the second statement template to generate the first statement; send the first statement to the first customer system; Alternatively, upon reaching the end-of-day push time of the first customer system, a first statement is generated according to the statement configuration within the financial integrated service system; and the first statement is sent to the first customer system.

2. The method according to claim 1, characterized in that, Before sending the first statement to the first customer system, the method further includes: In response to the first download request, send the first batch number; Store the first statement of account to the target path; Sending the first statement to the first customer system includes: In response to a received second download request including the first batch number, the target path is sent; In response to the received access request for the target path, the first statement of account is sent to the first customer system.

3. The method according to claim 1, characterized in that, After determining the statement type corresponding to the first identifier as the first statement type corresponding to the first customer system, and determining the statement field corresponding to the second identifier as the first statement field corresponding to the first customer system, the method further includes: In response to a received query request, the system outputs the identifiers corresponding to the at least two statement types, as well as the identifiers corresponding to the at least two statement fields of each statement type. The query request is used to request a query of the statement configuration corresponding to the first customer system. The statement configuration includes statement types and statement fields. The identifiers corresponding to the statement configurations are in a first display state, and the other identifiers are in a second display state.

4. The method according to claim 3, characterized in that, After responding to the received query request and outputting the identifiers corresponding to the at least two statement types, and the identifiers corresponding to at least two statement fields for each statement type, the method further includes: When a customer in the first customer system modifies the statement configuration of the first customer system, the third identifier and the fourth identifier in the first display state are obtained, wherein the third identifier is the identifier among the identifiers corresponding to the at least two statement types, and the fourth identifier is the identifier among the identifiers corresponding to the at least two statement fields of the first statement type; The statement type corresponding to the third identifier is determined as the first statement type corresponding to the first customer system, and the statement field corresponding to the fourth identifier is determined as the first statement field corresponding to the first customer system.

5. A statement sending device, characterized in that, A financial services system for platform enterprises, wherein the platform enterprise's financial services system pre-stores at least one customer system's corresponding statement configuration, the device comprising: The query module is used to respond to a first download request received from a first customer system or a first download request generated by a customer of the first customer system through interaction with the front end, and to query the first data generated by the first customer system within a first time period, as well as the first statement configuration corresponding to the first customer system. The first download request is used to request the download of the statement of the first customer system, and the first download request includes statement configuration requirements. The first statement configuration is determined based on the business type of the first customer system. The first customer system is any one of at least one customer system that has a cooperative relationship with the platform enterprise. The statement configuration requirements represent the latest requirements for the statement configuration of the first customer system, and the statement configuration requirements include statement field requirements, which are used to indicate the addition or removal of statement fields. The adjustment module is used to adjust the first statement configuration according to the statement configuration requirements to obtain the second statement configuration. The first statement configuration includes a first statement type and a first statement field, and the second statement configuration includes a second statement type and a second statement field. The generation module is used to obtain a first statement template corresponding to the second statement type; delete statement fields in the first statement template except for the second statement field to obtain a second statement template; obtain second data in the first data corresponding to the second statement field; write the second data into the second statement template to generate a first statement; The sending module is used to send the first statement of account to the first customer system; The device is also used to generate a first statement according to the statement configuration in the financial integrated service system when the end-of-day push time of the first customer system is reached; and to send the first statement to the first customer system. The display module is used to display a registration page using the front-end device of the financial integrated service system of the platform enterprise before querying the first data generated by the first customer system within a first time period and the first statement configuration corresponding to the first customer system in response to the received first download request. The registration page includes identifiers corresponding to at least two statement types and identifiers corresponding to at least two statement fields of each statement type. The at least two statement types include the first statement type, and the at least two statement fields of the first statement type include the first statement field. The determining module is configured to, in response to the received selection input from the customer in the first customer system for a first identifier and a second identifier, determine the statement type corresponding to the first identifier as the first statement type corresponding to the first customer system, and determine the statement field corresponding to the second identifier as the first statement field corresponding to the first customer system, wherein the first identifier is an identifier among the identifiers corresponding to the at least two statement types, and the second identifier is an identifier among the identifiers corresponding to the at least two statement fields of the first statement type.

6. A statement sending device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the statement sending method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the statement sending method as described in any one of claims 1-4.

8. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device causes the electronic device to perform the statement sending method as described in any one of claims 1-4.

Images