Document processing method and apparatus

Abstract

Embodiments of the present specification provide a bill processing method and device, wherein a bill processing method comprises: obtaining a business payment bill obtained after an institution member makes a business payment, and storing the business payment bill to a member account of the institution member; synchronizing the business payment bill from the member account to a co-management account of an institution to which the institution member belongs, which is associated with the member account, to add to a bill list in the co-management account; obtaining a bill associated with the business payment bill according to a bill adding request submitted by the institution member for the business payment bill; and returning the bill to the co-management account based on an account association relationship between the member account and the co-management account, to be associated with the business payment bill in the bill list.

Description

[0001] This invention patent application was filed on May 25, 2021, with application number CN202110572299.8 and title... This is a divisional application of the Chinese invention patent application for "method and apparatus for processing bills". Technical Field

[0002] This specification relates to the field of data processing technology, and in particular to a method and apparatus for processing invoices. Background Technology

[0003] Invoices typically possess certain evidentiary value. For example, they serve as the primary basis for accounting within a company and are also crucial evidence for auditing and tax enforcement inspections. When employees submit expense reports based on invoices, they must complete forms and submit the invoices, which are then reviewed by the organization's invoice manager. This reimbursement process is cumbersome and time-consuming, requiring significant time and effort from both employees and the invoice manager. Summary of the Invention

[0004] This specification provides one or more embodiments of a bill processing method. The bill processing method includes: obtaining an official payment invoice obtained after an institutional member makes an official payment, and storing it in the institutional member's member account; synchronizing the official payment invoice from the member account to a co-managed account of the institutional member's organization associated with the member account, to add it to the invoice list in the co-managed account; obtaining the invoice associated with the official payment invoice based on the invoice addition request submitted by the institutional member for the official payment invoice; and sending the invoice back to the co-managed account based on the account association relationship between the member account and the co-managed account, to associate it with the official payment invoice in the invoice list.

[0005] This specification provides one or more embodiments of a bill processing apparatus. The bill processing apparatus includes: a bill acquisition module configured to acquire official payment bills obtained after an organization member makes official payments and store them in the member's member account; a bill synchronization module configured to synchronize the official payment bills from the member account to a co-managed account of the organization to which the member belongs, associated with the member account, to add them to the bill list in the co-managed account; a bill addition module configured to acquire bills associated with the official payment bills based on bill addition requests submitted by the organization member for the official payment bills; and a bill return module configured to return the bills to the co-managed account based on the account association relationship between the member account and the co-managed account, to associate them with the official payment bills in the bill list.

[0006] This specification provides one or more embodiments of an electronic device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: obtain an official payment invoice obtained after an organizational member makes an official payment, and store it in the organizational member's member account; synchronize the official payment invoice from the member account to a co-managed account of the organizational member's organization associated with the member account, to add it to an invoice list in the co-managed account; obtain a document associated with the official payment invoice based on a document addition request submitted by the organizational member for the official payment invoice; and return the document to the co-managed account based on the account association relationship between the member account and the co-managed account, to associate it with the official payment invoice in the invoice list.

[0007] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions. When executed, these instructions perform the following processes: obtaining an official payment invoice obtained after an organizational member makes an official payment, and storing it in the member's member account; synchronizing the official payment invoice from the member account to a co-managed account of the organization to which the member belongs, associated with the member account, to add it to the invoice list in the co-managed account; obtaining the invoice associated with the official payment invoice based on the invoice addition request submitted by the member; and returning the invoice to the co-managed account based on the account association relationship between the member account and the co-managed account, to associate it with the official payment invoice in the invoice list. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in one or more embodiments of this specification or in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 A flowchart illustrating a bill processing method provided in one or more embodiments of this specification;

[0010] Figure 2 A schematic diagram illustrating the relationship between account users, accounts, and bills in a bill processing method provided in one or more embodiments of this specification;

[0011] Figure 3 A flowchart illustrating the process of creating a co-managed account in a bill processing method provided in one or more embodiments of this specification;

[0012] Figure 4 This document provides a flowchart of a document processing method for a document reimbursement scenario, which is provided for one or more embodiments of this specification.

[0013] Figure 5 This specification provides a schematic diagram of the structure of a ticket processing device according to one or more embodiments.

[0014] Figure 6 This is a schematic diagram of the structure of an electronic device provided for one or more embodiments of this specification. Detailed Implementation

[0015] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0016] This specification provides an example of a bill processing method:

[0017] Figure 1 This is a flowchart illustrating a bill processing method provided in this embodiment. Figure 2 This is a schematic diagram illustrating the relationship between account users, accounts, and bills in a bill processing method provided in this embodiment. Figure 3 This is a flowchart illustrating the process of creating a co-managed account in a bill processing method provided in this embodiment.

[0018] The execution entity of the ticket processing method provided in this embodiment can be a server.

[0019] Reference Figure 1 As shown, the bill processing method provided in this embodiment specifically includes the following steps S102 to S108.

[0020] The invoice processing method provided in this embodiment simplifies the reimbursement process for organizational members by synchronizing the official payment invoice to the co-managed account when the member account obtains the official payment invoice, and sending the invoice associated with the official payment invoice back to the co-managed account when the invoice is obtained. This reduces the waiting time required for the reimbursement process and improves the management efficiency of the organization's invoice managers.

[0021] Step S102: Obtain the official payment bill obtained by the organization member after making official payments, and store it in the organization member's member account.

[0022] An organization can be a company, a school, an association, or other group. Taking a company as an example, its members can be its employees, and the "note manager" mentioned below can be a manager of the company or a financial staff member designated by the company. The members and the note manager belong to the same organization.

[0023] Official business payments can occur during business trips, such as purchasing train tickets between the destination and the origin; they can also occur when purchasing work-related items, such as office supplies; and they can occur when entertaining clients, such as treating them to a meal. These are just a few examples; there are other scenarios for official business payments, which will not be elaborated upon here.

[0024] Member accounts of organizational members can be data accounts used by individual organizational members to perform payment operations, such as personal platform accounts on third-party payment platforms, social media accounts, and platform accounts on shopping platforms.

[0025] Optionally, before the step of obtaining the official payment invoices obtained by the members of the organization after making official payments and storing them in the members' member accounts, the bill processing method provided in this embodiment further includes: creating a co-management account according to the co-management account establishment request of the bill manager; associating the bill manager's institutional account and fund account to the co-management account according to the institutional roles preset in the co-management account; and associating the member accounts of each member of the organization to the co-management account according to the member roles preset in the co-management account.

[0026] The institutional account of the bill manager can be a data account used by the bill manager personally, such as a personal platform account of a corporate entity on a third-party payment platform; or it can be an institutional account of the organization to which the bill manager belongs, such as a corporate account of a company on a third-party payment platform.

[0027] It is important to note that the person who creates the institutional account and co-management account may be the same person as, or may not be the person who actually uses the institutional account and co-management account for bill management in the actual scenario. For example, after creating the institutional account and co-management account, the company manager may grant certain permissions to a designated finance staff member, enabling that staff member to use the institutional account and co-management account for bill management.

[0028] Figure 2 The account users include institutional members 204 and bill managers 202. The accounts include institutional account 206, co-management account 208, member account 210 and fund account 212. The bills include bills 214 stored in member account 210 and bills 216 stored in co-management account 208.

[0029] Reference Figure 2 and Figure 3 As shown, in step S302, the bill manager creates a co-management account. That is... Figure 2 In the bill manager 202, a co-management account 208 is created.

[0030] Step S304 involves linking the co-managed account to the member accounts of the organization's members. That is... Figure 2 Member account 210 is associated with co-managed account 208.

[0031] Step S306 involves linking the co-managed account to the funds account, i.e. Figure 2 Funds account 212 is linked to co-managed account 208.

[0032] Figure 2 The funds account 212 can be associated with the co-managed account 208 via mounting. Mounting refers to the process by which the operating system makes computer files and directories on a storage device (such as a hard drive, CD-ROM, or shared resource) accessible to users through the computer's file system. Mounting the funds account 212 to the co-managed account 208 can be understood as follows: for example, a member account 210 associated with the co-managed account 208 can access the funds account 212 through the co-managed account 208. Specifically, when making a payment operation through the member account 210, the funds account 212 can be selected as the funding account; an institutional account 206 associated with the co-managed account 208 can access the funds account 212 through the co-managed account 208. Specifically, the institutional account 206 can transfer funds to the funds account 212.

[0033] Step S308: The bill manager transfers funds to the funds account. That is... Figure 2 The bill manager 202 manages the funds account 212 through the institutional account 206. The management method can be to designate the funds account 212 as the recipient of the transfer and transfer funds from other accounts into the funds account 212.

[0034] It is important to emphasize that the definition of the co-managed account in this embodiment differs from that of a bank-opened co-managed account. This co-managed account is a different type of account from member accounts or institutional accounts; it can be considered a virtual account that cannot be logged into. The co-managed account can have pre-set institutional and member roles, with different functions and permissions configured according to these roles. Institutional roles include fund roles and manager roles.

[0035] Funds accounts linked to the co-management account according to their roles can be regarded as a shared purse. That is, each member account linked to the co-management account according to its role can choose the funds account as the payment method when making a payment and use the funds in the funds account to make the payment.

[0036] Typically, when employees make corporate payments through their employee accounts, they will select this fund account as the payment method, meaning they can directly use the organization's funds to make the payment without the employee having to pay upfront and then claim reimbursement.

[0037] An institutional account associated with a co-managed account according to its manager role can be considered the manager of that co-managed account. The bill manager cannot directly log in to the co-managed account, but can manage the bills within the co-managed account through the institutional account. For example... Figure 2 As shown, institutional account 206 manages note 216, which is stored in co-management account 208. Note 216 is obtained by synchronizing note 214 stored in member account 210 to co-management account 208.

[0038] Member accounts linked to the co-managed account according to their member roles can be considered as billing and invoice providers for that co-managed account. Furthermore, each member account can use the corresponding funds account of the co-managed account for official payments. For example... Figure 2 As shown, when an institutional member uses funds in fund account 212 for consumption, the bill 214 stored in member account 210 is synchronized to co-managed account 208, and the bill 216 stored in co-managed account 208 is also synchronized to co-managed account 208.

[0039] The institutional account of a bill manager can be associated with one or more co-managed accounts; a co-managed account can be associated with a funds account, and a co-managed account can be associated with multiple member accounts.

[0040] Optionally, obtaining the official payment invoice obtained after an institutional member makes an official payment includes: obtaining a confirmation request for the official payment made by an institutional member; the confirmation request carries the member account identifier of the member's member account and the fund account identifier of the institution's fund account; the member account and the fund account are associated with a co-managed account; and obtaining the official payment invoice obtained after the official payment is made based on the member account identifier and the fund account identifier.

[0041] Combination Figure 2 It is known that member account 210 is associated with co-managed account 208, and fund account 212 is associated with co-managed account 208. Therefore, member 204 can use the funds in fund account 212 to make official payments through the association between member account 210 and co-managed account 208, and the association between co-managed account 208 and fund account 212.

[0042] In practice, for example, after a payment operation is triggered through a member's personal platform account on a third-party payment platform, a list of payment methods linked to that personal platform account is obtained. The member selects the organization's funds account as the payment method, confirms the payment, and sends a confirmation request for official payment. This confirmation request then carries the member account identifier of the personal platform account and the funds account identifier of the funds account.

[0043] After making official payments based on member account identifiers and fund account identifiers, the server retrieves the official payment invoice. Invoices for payments made to institutional fund accounts are all official payment invoices. The server can determine whether a newly acquired invoice for a member account is an official payment invoice based on the fund account identifier.

[0044] Step S104: Synchronize the official payment bills from the member account to the co-management account of the institution to which the member belongs, so as to add them to the bill list in the co-management account.

[0045] After the server retrieves the official payment invoice, it can synchronize the invoice from the member's account to the co-managed account of the institution to which the member's account belongs, as per the following procedure. Figure 2 As shown, bill 214 is synchronized from member account 210 to co-managed account 208, resulting in bill 216. Synchronization can be understood as copying data from one account and sending it to another. The co-managed account stores a list of bills, which consists of multiple official payment bills synchronized from different member accounts to the co-managed account.

[0046] Step S106: Based on the invoice addition request submitted by the organization member for the official payment invoice, obtain the invoice associated with the official payment invoice.

[0047] Optionally, after the step of obtaining the official payment invoices obtained by organizational members after making official payments and storing them in the organizational members' member accounts, and before the step of obtaining the invoices associated with the official payment invoices based on the invoice addition requests submitted by organizational members for the official payment invoices, the invoice processing method provided in this embodiment further includes: obtaining a member invoice list composed of various official payment invoices in the member accounts based on the invoice access requests of organizational members; querying the invoice status of any official payment invoice in the member invoice list; if the invoice status is "not returned", obtaining the addition control configuration data of the invoice addition control; and rendering and generating a display page of the member invoice list based on the member invoice list and the addition control configuration data.

[0048] In practice, the server can filter out official payment bills from the member accounts' bills based on the fund account identifier, and then obtain a member bill list composed of each official payment bill. Alternatively, when the official payment bill is first obtained and synchronized to the co-managed account, a specified tag can be added to the official payment bill, and then the member bill list composed of official payment bills can be obtained by filtering based on the specified tag.

[0049] For any official payment invoice, the server can store the association between that invoice and the corresponding invoice. If a corresponding invoice is found in the query, the invoice status is determined to be "returned"; if the query determines that no corresponding invoice exists, the invoice status is determined to be "unreturned". At any given time, the invoice status of an official payment invoice can only be either "returned" or "unreturned".

[0050] If the invoice status is "not returned," the configuration data for the invoice addition control is retrieved. Based on the member invoice list and the addition control configuration data, a display page for the member invoice list is rendered, displaying the invoice addition control. Organization members can use this invoice addition control to add invoices associated with the official payment invoice.

[0051] Optionally, before the step of obtaining the invoice associated with the official payment bill based on the invoice addition request submitted by the organization member for the official payment bill, the invoice processing method provided in this embodiment further includes: obtaining the invoice issuance information of the merchant corresponding to the official payment bill; determining whether the merchant supports issuing electronic invoices based on the invoice issuance information; if so, obtaining the first control configuration data of the electronic invoice request control; and configuring the invoice acquisition method of the official payment bill based on the first control configuration data.

[0052] The server retrieves the invoice issuance information of the merchant corresponding to the official payment bill. This invoice issuance information includes whether the merchant supports issuing electronic invoices and / or whether the merchant supports issuing paper invoices. For example, the invoice issuance information for Merchant 1 includes that it does not support issuing electronic invoices but supports issuing paper invoices.

[0053] The server determines whether the merchant supports issuing electronic invoices based on the invoice issuance information. If the merchant supports electronic invoices, it retrieves the first control configuration data of the electronic invoice request control. Based on the first control configuration data, it configures the invoice acquisition method for official payment bills. For example, a button is configured on the right side of official payment bill 1, which can be clicked by organizational members to request an electronic invoice from the merchant. Electronic invoices, like ordinary paper invoices, have a unified code issued by the tax authorities, and therefore have the same evidentiary effect. However, electronic invoices are more convenient than ordinary paper invoices in all aspects of invoicing, reimbursement, etc. Therefore, if the merchant supports issuing electronic invoices, prioritizing the configuration of the electronic invoice request control can improve the efficiency and convenience of invoicing, reimbursement, and other processes.

[0054] Optionally, if the execution result after determining whether the merchant supports issuing electronic invoices based on the invoice issuance information is no, the following operations are performed: Determine whether the merchant supports issuing paper invoices based on the invoice issuance information; if yes, obtain the second control configuration data of the paper invoice request control and the third control configuration data of the paper invoice upload control, and configure the invoice acquisition method for official payment bills based on the second control configuration data and the third control configuration data; if no, obtain the third control configuration data, and configure the invoice acquisition method for official payment bills based on the third control configuration data.

[0055] Based on the invoice issuance information, determine whether the merchant supports issuing paper invoices. If the merchant supports issuing paper invoices, obtain the second control configuration data of the paper invoice request control and the third control configuration data of the paper invoice upload control. Based on the second and third control configuration data, configure the invoice acquisition method for official payment bills. For example, an icon control is configured on the right side of official payment bill 1, allowing organizational members to request paper invoices from the merchant by clicking this icon control. Another example is an arrow control on the right side of official payment bill 1, allowing organizational members to obtain a paper invoice image via image capture as the invoice associated with the official payment bill by clicking this arrow control, or to obtain an invoice image obtained through OCR processing as the invoice associated with the official payment bill.

[0056] If the merchant does not support issuing paper invoices, organizational members can find an invoice of the same type as the official payment invoice as a substitute for the invoice associated with the official payment invoice. The server obtains the third-party control configuration data and configures the invoice acquisition method for the official payment invoice based on the third-party control configuration data. For example, an arrow control is configured on the right side of Official Payment Invoice 1. Organizational members can click on this arrow control to obtain an image of a paper invoice as the invoice associated with the official payment invoice through image capture, or they can obtain an invoice obtained by OCR processing of the invoice image as the invoice associated with the official payment invoice.

[0057] Optionally, based on the invoice addition request submitted by an institutional member for an official payment invoice, obtain the invoice associated with the official payment invoice, including: obtaining the configuration data of the associated invoice upload page based on the associated invoice upload request submitted by an institutional member for an official payment invoice, so as to generate an associated invoice upload page corresponding to the official payment invoice; obtaining the invoice image of the paper invoice uploaded by the institutional member on the invoice upload page; and performing OCR processing on the invoice image to obtain the invoice associated with the official payment invoice.

[0058] In practice, when an organization member clicks the paper document upload control on the right side of a specific official payment bill on the bill's display page, the server receives the member's request to upload associated documents for that bill, obtains the configuration data for the associated document upload page, and generates the corresponding associated document upload page for the official payment bill. This page can then utilize OCR scanning to capture and process images of the paper documents, obtaining the documents associated with the official payment bill.

[0059] The linked invoice upload page can also call the image capture function to capture images of paper invoices and use these images as invoices associated with official payment bills.

[0060] Optionally, based on the invoice addition request submitted by an institutional member for an official payment invoice, the invoice associated with the official payment invoice is obtained, including: generating an invoice request message and sending it to the merchant corresponding to the official payment invoice based on the electronic invoice retrieval request submitted by the institutional member for the official payment invoice; the electronic invoice retrieval request carries the member account identifier and the invoice identifier of the official payment invoice; obtaining the electronic invoice sent by the merchant based on the member account identifier; the electronic invoice being issued by the merchant based on the invoice identifier; and associating the electronic invoice with the official payment invoice.

[0061] In practice, when an organization member clicks the electronic invoice request control on the right side of a specific official payment invoice on the display page, the server receives the electronic invoice request submitted by the member. Based on this request, the server generates an invoice request message and sends it to the merchant corresponding to the official payment invoice. The merchant then sends the requested electronic invoice to the member's account based on the member's account identifier. This electronic invoice is issued by the merchant using the invoice identifier carried in the invoice request message. The server then associates this electronic invoice with the official payment invoice.

[0062] Optionally, based on the invoice addition request submitted by the organization member for the official payment invoice, obtain the invoices associated with the official payment invoice, including: determining multiple official payment invoices selected by the organization member based on the invoice selection operation of the organization member; and obtaining the invoices associated with the multiple official payment invoices based on the merged invoice addition request.

[0063] In practice, organizational members can click the multi-select mode control on the display page of official payment bills. In multi-select mode, organizational members can select multiple official payment bills and click "Merge Bills". The server will then obtain the multiple official payment bills selected by the organizational members based on their bill selection operation. Organizational members can click the "Merge Bills Add" control. The server will then obtain the merge bills add request and obtain the bills associated with the multiple official payment bills by uploading paper bills or requesting electronic bills from merchants.

[0064] Step S108: Based on the account association relationship between the member account and the co-managed account, the invoice is returned to the co-managed account to be associated with the official payment invoice in the invoice list.

[0065] Reference Figure 2 As shown, member account 210 synchronizes the stored ticket 214 to co-management account 208, and obtains ticket 216 stored in co-management account 208.

[0066] This can be understood as follows: once an organizational member uploads a receipt to their account, the server immediately synchronizes the receipt to the management account, thus saving organizational members the process of organizing receipts awaiting reimbursement and reducing their workload.

[0067] In step S104 above, after the server obtains the official payment invoices, it can synchronize these invoices from member accounts to the co-managed account of the institution to which the member account belongs. Therefore, the invoice list in the co-managed account includes official payment invoices synchronized from each member account. Thus, after the invoices from member accounts are synchronized to the co-managed account, the returned invoices can be associated with the official payment invoices in the invoice list based on the association between the official payment invoices and the invoices. This allows the invoice manager to clearly and intuitively perceive which invoices have been returned and which have not.

[0068] Optionally, the bill processing method provided in this embodiment further includes: obtaining the bill access conditions submitted by the bill manager through the institutional account; obtaining a target bill list that meets the bill access conditions from the bill list according to the association relationship between the institutional account and the co-managed account; and processing the bills associated with the target bill according to the associated bill processing request submitted by the bill manager for the target bill in the target bill list.

[0069] Reference Figure 2 As shown, the bill manager 202 can manage the bills 216 stored in the co-management account 208 through the institutional account 206 and the co-management account 208 associated with the institutional account 206.

[0070] Bill access criteria include, but are not limited to, the time period to which the bill belongs, the organization or member, the bill type, the bill tag, and the bill group.

[0071] For example, if the bill access criteria are from month X, day Y to month Z, the bill manager can use the institutional account to filter the bill list of the co-managed account according to the time period from month X, day Y to month Z to obtain the official payment bills generated within that time period, thus obtaining the target bill list. The bill manager can then process the target bills selected by the bill manager in the target bill list through the institutional account. Processing methods include, but are not limited to, viewing, downloading, requesting and receiving notifications, rejecting, and processing bill parameter statistics.

[0072] Optionally, based on the related bill processing request submitted by the bill manager for the target bill in the target bill list, the bills associated with the target bill are processed, including: based on the bill viewing request submitted by the bill manager for the target bill, obtaining the configuration data of the target bill associated with the target bill and the bill display page, so as to render and generate the bill display page of the target bill.

[0073] The server receives a bill viewing request submitted by the bill administrator through an institutional account for the target bill. This bill viewing request carries the bill identifier of the target bill. Based on the bill identifier, the server obtains the target bill associated with the target bill and the configuration data of the bill display page, so as to render and generate the bill display page of the target bill. The bill display page displays the bill associated with the template bill.

[0074] Optionally, based on the related bill processing request submitted by the bill manager for the target bill in the target bill list, the bills associated with the target bill are processed, including: based on the bill return prompt request submitted by the bill manager for the target bill, sending bill return prompt information to the member account that returned the target bill.

[0075] The server receives a document return request submitted by the document administrator through the institutional account for a target invoice. This request carries the invoice identifier of the target invoice. Based on the invoice identifier, the server determines the member account that returned the target invoice and sends a document return notification message to that member account. This notification message can be understood as follows: after an institutional member makes an official payment and receives an official payment invoice that is synchronized to the co-managed account, but no related document has been returned to the co-managed account for an extended period, the document administrator uses this notification message to urge the institutional member to return the document as soon as possible.

[0076] In summary, the invoice processing method provided in this embodiment first obtains the official payment invoices obtained after an organization member makes an official payment and stores them in the member's account; second, it synchronizes the official payment invoices from the member's account to the co-managed account of the organization to which the member belongs, adding them to the invoice list in the co-managed account; then, based on the invoice addition request submitted by the organization member for the official payment invoice, it obtains the invoices associated with the official payment invoices; finally, based on the account association relationship between the member's account and the co-managed account, it sends the invoices back to the co-managed account to associate them with the official payment invoices in the invoice list. This technical solution simplifies the invoice reimbursement process for organization members, shortens the waiting time required for the reimbursement process, and correspondingly improves the management efficiency of the organization's invoice managers.

[0077] The following section further illustrates the invoice processing method provided in this embodiment using the invoice reimbursement scenario as an example.

[0078] Figure 4 This embodiment provides a flowchart of a document processing method for document reimbursement scenarios.

[0079] In step S402, members of the organization process official payments through the fund account corresponding to the co-managed account.

[0080] The various accounts, account users, and tickets mentioned in this embodiment are as follows: Figure 1 The concepts in the illustrated embodiments are similar and will not be repeated here. The server can obtain the official payment invoices obtained by organization members after they have made official payments.

[0081] Step S404: Determine whether the merchant supports issuing electronic invoices.

[0082] The server retrieves the invoice issuance information of the merchant corresponding to the official payment bill. This invoice issuance information includes whether the merchant supports issuing electronic invoices and / or whether the merchant supports issuing paper invoices. The server determines whether the merchant supports issuing electronic invoices based on the invoice issuance information.

[0083] If yes, proceed to step S406; otherwise, proceed to step S408.

[0084] Step S406: Obtain the electronic invoice sent by the merchant.

[0085] If the merchant supports issuing electronic invoices, then obtain the first control configuration data of the electronic invoice request control; based on the first control configuration data, configure the invoice acquisition method for official payment bills. For example, a button is configured on the right side of official payment bill 1, which can be clicked by organizational members to request electronic invoices from the merchant.

[0086] When an organization member clicks the electronic invoice request control on the right side of a specific official payment bill on the bill's display page, the server receives the electronic invoice request submitted by the organization member for that bill. Based on this request, the server generates an invoice request message and sends it to the merchant corresponding to the official payment bill.

[0087] Electronic invoices, like ordinary paper invoices, have a unified code issued by the tax authorities and therefore have the same evidentiary effect. However, electronic invoices are more convenient than ordinary paper invoices in all aspects such as invoicing and reimbursement. Therefore, if a merchant supports issuing electronic invoices, prioritizing the configuration of electronic invoice request controls can improve the efficiency and convenience of invoicing and reimbursement.

[0088] The merchant sends a requested electronic invoice to the member account based on the member account identifier. This electronic invoice was issued by the merchant based on the bill identifier carried in the invoice request message. The server then associates this electronic invoice with the official payment invoice.

[0089] In other embodiments, obtaining an electronic ticket sent by a merchant may also involve obtaining an email sent by a merchant with the requested electronic ticket attached to the email.

[0090] Step S408: Determine whether the merchant supports issuing paper invoices.

[0091] If yes, proceed to step S410; otherwise, proceed to step S412.

[0092] The server executes step S408. Specifically, the server determines whether the merchant supports issuing paper invoices based on the invoice issuance information. If the merchant supports paper invoices, it obtains the second control configuration data of the paper invoice request control and the third control configuration data of the paper invoice upload control. Based on the second and third control configuration data, it configures the invoice acquisition method for official payment bills. For example, an icon control is configured on the right side of official payment bill 1, allowing organizational members to request paper invoices from the merchant by clicking this icon control. Alternatively, an arrow control is configured on the right side of official payment bill 1, allowing organizational members to obtain an image of the paper invoice as the invoice associated with the official payment bill by clicking this arrow control, or to obtain an invoice obtained after OCR processing of the invoice image as the invoice associated with the official payment bill.

[0093] It is important to note that if a merchant does not support issuing electronic invoices, regardless of whether the merchant supports issuing paper invoices, organizational members must upload and store the paper invoice issued by the merchant or an alternative paper invoice obtained by the organizational member in their member account by capturing an image of the paper invoice. Additionally, in some scenarios, organizational members immediately obtain paper invoices from the merchant after making official payments. Therefore, in some embodiments, step S408, executed by the server, can be omitted. Organizational personnel can then determine whether to upload the paper invoice issued by the merchant or a paper invoice of the same type as the official payment invoice. That is, after the server executes step S404, if the merchant does not support issuing electronic invoices, then step S410 is executed.

[0094] Step S410: Obtain images of paper tickets uploaded by members of the organization and perform OCR processing.

[0095] If the merchant supports issuing paper invoices, the system retrieves the second control configuration data for the paper invoice request control and the third control configuration data for the paper invoice upload control. Based on these data, it configures the method for obtaining invoices for official payment bills. For example, an icon control can be configured on the right side of "Official Payment Bill 1," allowing organizational members to request paper invoices from the merchant by clicking it. Alternatively, an arrow control can be configured on the right side of "Official Payment Bill 1," allowing organizational members to obtain an image of the paper invoice as the associated invoice for the official payment bill by clicking it, or to obtain an invoice obtained by OCR processing of the invoice image.

[0096] The server retrieves the configuration data of the third-party control and configures the method for obtaining receipts for official payment bills based on this data. For example, an arrow control is configured on the right side of Official Payment Bill 1. Members of the organization can click on this arrow control to obtain an image of a paper receipt as the receipt associated with the official payment bill through image capture, or they can obtain a receipt obtained by OCR processing the receipt image as the receipt associated with the official payment bill.

[0097] Step S412: Members of the organization obtain paper tickets of the same type.

[0098] It should be noted that step S412 is not executed by the server, but by the organization's personnel.

[0099] If a merchant does not support issuing paper invoices, then organizational members can find an invoice of the same type as the one associated with the official payment invoice as a substitute.

[0100] Step S414: Store the obtained tickets in the member account.

[0101] Electronic invoices sent by merchants, or invoices obtained by OCR processing of images of paper invoices, are stored in the member accounts of institutional members.

[0102] Step S416: Return the bill to the escrow account.

[0103] The bills are transferred from the member account to the co-managed account.

[0104] Step S418: The bill manager views and downloads the bill.

[0105] Based on the relationship between the institutional account and the co-managed account, the bill manager can view, process, or download the bills stored in the co-managed account.

[0106] like Figure 4 The method embodiments shown can implement the various processes in the aforementioned method embodiments, and will not be repeated here.

[0107] In summary, the invoice processing method provided in this embodiment first obtains the official payment invoices obtained after an organization member makes an official payment and stores them in the member's account; second, it synchronizes the official payment invoices from the member's account to the co-managed account of the organization to which the member belongs, adding them to the invoice list in the co-managed account; then, based on the invoice addition request submitted by the organization member for the official payment invoice, it obtains the invoices associated with the official payment invoices; finally, based on the account association relationship between the member's account and the co-managed account, it sends the invoices back to the co-managed account to associate them with the official payment invoices in the invoice list. This technical solution simplifies the invoice reimbursement process for organization members, shortens the waiting time required for the reimbursement process, and correspondingly improves the management efficiency of the organization's invoice managers.

[0108] Corresponding to the above Figure 1 Based on the same technical concept, one or more embodiments of this specification also provide a bill processing apparatus for the bill processing method described. Figure 5 A schematic diagram of the structure of a first type of ticket processing device provided in one or more embodiments of this specification, as shown below. Figure 5 As shown, the ticket processing device includes:

[0109] The bill retrieval module 502 is configured to retrieve the official payment bills obtained by the organization members after they make official payments, and store them in the member accounts of the organization members.

[0110] The bill synchronization module 504 is configured to synchronize the official payment bill from the member account to the co-management account of the institution to which the member belongs, which is associated with the member account, so as to add it to the bill list in the co-management account;

[0111] The invoice addition module 506 is configured to obtain invoices associated with the official payment invoice based on the invoice addition request submitted by the organization member for the official payment invoice;

[0112] The invoice return module 508 is configured to return the invoice to the co-managed account based on the account association relationship between the member account and the co-managed account, so as to associate it with the official payment invoice in the invoice list.

[0113] It should be noted that the embodiments of the bill processing device in this specification and the embodiments of the bill processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding bill processing method mentioned above, and the repeated parts will not be described again.

[0114] Corresponding to the above-described method for processing tickets applied to electronic devices, based on the same technical concept, one or more embodiments of this specification also provide an electronic device for executing the above-described method for processing tickets. Figure 5 This is a schematic diagram of the structure of an electronic device provided for one or more embodiments of this specification.

[0115] This embodiment provides an electronic device, including:

[0116] like Figure 6 As shown, electronic devices can vary considerably due to differences in configuration or performance. They may include one or more processors 601 and memories 602, with the memory 602 storing one or more application programs or data. The memory 602 can be temporary or persistent storage. The application programs stored in the memory 602 may include one or more modules (not shown), each module including a series of computer-executable instructions within the electronic device. Furthermore, the processor 601 may be configured to communicate with the memory 602, executing the series of computer-executable instructions stored in the memory 602 on the electronic device. The electronic device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input / output interfaces 605, one or more keyboards 606, etc.

[0117] In one specific embodiment, the electronic device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the electronic device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0118] Obtain the official payment invoices obtained by members of the organization after making official payments, and store them in the member accounts of the organization members;

[0119] Synchronize official payment bills from member accounts to the co-managed account of the institution to which the member accounts belong, so as to add them to the bill list in the co-managed account;

[0120] Based on the invoice addition requests submitted by members of the organization for official payment invoices, obtain the invoices associated with the official payment invoices;

[0121] Based on the account association between member accounts and co-managed accounts, invoices are returned to the co-managed account to be linked to official payment invoices in the invoice list.

[0122] This specification provides an example of a storage medium as follows:

[0123] Corresponding to the ticket processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium. In one specific embodiment, the storage medium can be a USB flash drive, optical disc, hard disk, etc.

[0124] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0125] Obtain the official payment invoices obtained by members of the organization after making official payments, and store them in the member accounts of the organization members;

[0126] Synchronize official payment bills from member accounts to the co-managed account of the institution to which the member accounts belong, so as to add them to the bill list in the co-managed account;

[0127] Based on the invoice addition requests submitted by members of the organization for official payment invoices, obtain the invoices associated with the official payment invoices;

[0128] Based on the account association between member accounts and co-managed accounts, invoices are returned to the co-managed account to be linked to official payment invoices in the invoice list.

[0129] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the ticket processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0130] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0131] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0132] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0133] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0134] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0135] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0136] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of 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, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0137] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0138] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0139] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0140] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0141] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0142] It should also be noted that 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 one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0143] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0144] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0145] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for processing negotiable instruments, comprising: Obtain the bills obtained from the member accounts of the organization after making official payments through the fund accounts corresponding to the co-managed accounts; The funds account was used by members of the organization to make payments for official business. The bill is synchronized from the member account to the co-managed account of the institution to which the member belongs, which is associated with the member account, and added to the bill list in the co-managed account; Determine whether the merchant corresponding to the bill supports issuing electronic invoices; If so, based on the invoice addition request submitted by the member of the organization for the bill, the electronic invoice sent by the merchant is obtained, and based on the account association relationship between the member account and the co-managed account, the electronic invoice is sent back to the co-managed account.

2. The method according to claim 1, wherein obtaining the invoice obtained after the member account of the organization makes an official payment through the fund account corresponding to the co-managed account includes: Obtain a confirmation request from a member of the organization to make official payments; the confirmation request carries the member account identifier of the member's member account and the fund account identifier of the organization's fund account; the member account and the fund account are associated with the co-managed account; Obtain the bill obtained after making official payments based on the member account identifier and the fund account identifier.

3. The method according to claim 1, further comprising: Based on the associated invoice upload request submitted by the organization member for the invoice, obtain the configuration data of the associated invoice upload page to generate the associated invoice upload page corresponding to the invoice; Obtain images of paper receipts uploaded by members of the organization on the receipt upload page; The invoice image is subjected to OCR processing to obtain the invoice associated with the bill.

4. The method according to claim 1, wherein obtaining the electronic invoice sent by the merchant based on the invoice addition request submitted by the institutional member for the bill includes: Based on the electronic invoice retrieval request submitted by the institution member for the bill, an invoice request message is generated and sent to the merchant corresponding to the bill; The electronic ticket retrieval request carries the member account identifier and the bill identifier of the bill; Obtain the electronic invoice sent by the merchant based on the member account identifier; the electronic invoice is issued by the merchant based on the bill identifier; Associate the electronic invoice with the bill.

5. The method according to claim 1, further comprising: Based on the bill selection operation of the organization members, determine the multiple bills selected by the organization members; Based on the consolidated invoice addition request, retrieve the invoices associated with the multiple invoices.

6. The method according to claim 1, wherein determining whether the merchant corresponding to the bill supports issuing electronic invoices includes: Obtain the invoice issuance information of the merchant corresponding to the bill; Based on the invoice issuance information, determine whether the merchant supports issuing electronic invoices; If so, then retrieve the first control configuration data of the electronic invoice request control; Configure the invoice retrieval method for the bill based on the configuration data of the first control.

7. According to the method of claim 6, if the execution result after the step of determining whether the merchant supports issuing electronic invoices based on the invoice issuance information is no, the following operation is performed: Based on the invoice issuance information, determine whether the merchant supports issuing paper invoices; If so, obtain the second control configuration data of the paper ticket request control and the third control configuration data of the paper ticket upload control, and configure the ticket acquisition method of the bill according to the second control configuration data and the third control configuration data; If not, then obtain the configuration data of the third control, and configure the invoice acquisition method of the bill according to the configuration data of the third control.

8. The method according to claim 2, before the step of obtaining the bill obtained after the member account of the organization member makes an official payment through the fund account corresponding to the co-managed account, it further includes: Create the co-management account according to the co-management account establishment request from the bill manager; According to the pre-set institutional roles of the co-managed account, the institutional account of the bill manager and the fund account are associated with the co-managed account; According to the member roles pre-set in the co-management account, the member accounts of each of the institutions are associated with the co-management account.

9. The method according to claim 1, after the step of obtaining the bill obtained by the member account of the organization member through the fund account corresponding to the co-managed account for official payment, and before the step of obtaining the electronic invoice sent by the merchant based on the invoice addition request submitted by the organization member for the bill, further includes: Based on the bill access requests of the organization members, obtain the member bill list consisting of each of the bills in the member account; For any of the bills in the member bill list, query the bill status of the bill; If the bill status is "not returned", then obtain the configuration data of the bill addition control. Based on the member bill list and the added control configuration data, render and generate the display page of the member bill list.

10. The method of claim 8, further comprising: Obtain the bill access conditions submitted by the bill manager through the institutional account; Based on the association between the institutional account and the co-managed account, obtain a target bill list that meets the bill access conditions from the bill list; Based on the related bill processing request submitted by the bill manager for the target bill in the target bill list, process the bills associated with the target bill.

11. The method according to claim 10, wherein processing the bills associated with the target bill based on the associated bill processing request submitted by the bill manager for the target bill in the target bill list includes: Based on the invoice viewing request submitted by the invoice manager for the target invoice, the configuration data of the target invoice associated with the target invoice and the invoice display page are obtained, so as to render and generate the invoice display page of the target invoice.

12. The method according to claim 10, wherein processing the bills associated with the target bill based on the associated bill processing request submitted by the bill manager for the target bill in the target bill list includes: Based on the invoice return request submitted by the invoice manager for the target invoice, invoice return notification information is sent to the member account that returned the target invoice.

13. A method for processing negotiable instruments, comprising: Obtain the bills obtained from the member accounts of the organization after making official payments through the fund accounts corresponding to the co-managed accounts; The funds account was used by members of the organization to make payments for official business. The bill is synchronized from the member account to the co-managed account of the institution to which the member belongs, which is associated with the member account, and added to the bill list in the co-managed account; Determine whether the merchant corresponding to the bill supports issuing electronic invoices; If the merchant does not support issuing electronic invoices, then determine whether the merchant supports issuing paper invoices; If the merchant supports issuing paper invoices, the image of the paper invoice uploaded by the member of the organization is obtained and processed by OCR to obtain the invoice and store it in the member's account; the invoice is then sent back from the member's account to the co-managed account.

14. A ticket processing device, comprising: The bill retrieval module is configured to retrieve bills obtained by the member accounts of organizational members after official payments are made through the fund accounts corresponding to the co-managed accounts. The funds account was used by members of the organization to make payments for official business. The bill synchronization module is configured to synchronize the bill from the member account to a co-management account of the institution to which the member belongs, which is associated with the member account, so as to add the bill to the bill list in the co-management account; The invoice addition module is configured to determine whether the merchant corresponding to the invoice supports issuing electronic invoices; If so, execute the invoice return module; The invoice return module is configured to obtain the electronic invoice sent by the merchant based on the invoice addition request submitted by the member of the organization for the bill, and return the electronic invoice to the co-managed account based on the account association relationship between the member account and the co-managed account.

15. An electronic device comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: The document describes how an organization obtains bills after its members make official payments through a fund account corresponding to a co-managed account; the fund account is used by the organization members to make official payments. The bill is synchronized from the member account to the co-managed account of the institution to which the member belongs, which is associated with the member account, and added to the bill list in the co-managed account; Determine whether the merchant corresponding to the bill supports issuing electronic invoices; If so, based on the invoice addition request submitted by the member of the organization for the bill, the electronic invoice sent by the merchant is obtained, and based on the account association relationship between the member account and the co-managed account, the electronic invoice is sent back to the co-managed account.

16. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: The document describes how an organization obtains bills after its members make official payments through a fund account corresponding to a co-managed account; the fund account is used by the organization members to make official payments. The bill is synchronized from the member account to the co-management account of the institution to which the member belongs and is associated with the member account, and added to the bill list in the co-management account; Determine whether the merchant corresponding to the bill supports issuing electronic invoices; If so, based on the invoice addition request submitted by the member of the organization for the bill, the electronic invoice sent by the merchant is obtained, and based on the account association relationship between the member account and the co-managed account, the electronic invoice is sent back to the co-managed account.

Images