WO2022247964A1 - 票据处理方法、装置、电子设备及存储介质 - Google Patents

票据处理方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2022247964A1
WO2022247964A1 PCT/CN2022/103541 CN2022103541W WO2022247964A1 WO 2022247964 A1 WO2022247964 A1 WO 2022247964A1 CN 2022103541 W CN2022103541 W CN 2022103541W WO 2022247964 A1 WO2022247964 A1 WO 2022247964A1
Authority
WO
WIPO (PCT)
Prior art keywords
bill
account
business
bills
payment
Prior art date
Application number
PCT/CN2022/103541
Other languages
English (en)
French (fr)
Inventor
沈海涛
黄敏
华建辉
陈利剑
王军伟
Original Assignee
支付宝(杭州)信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Publication of WO2022247964A1 publication Critical patent/WO2022247964A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/125—Finance or payroll

Definitions

  • This specification relates to the technical field of data processing, and in particular to a bill processing method and device.
  • Bills usually have certain credential effects. For example, bills are the original basis for accounting in enterprises, and they are also an important basis for law enforcement inspections by audit agencies and taxation agencies. When agency employees make expense reimbursements based on bills, they need to fill in a report and submit the bills, which will be reviewed by the bill manager of the organization. The reimbursement process is cumbersome, and the reimbursement process takes a long time, consuming a lot of time from both the organization members and the bill manager. time and energy.
  • the bill processing method includes: obtaining the business payment bill obtained by the organization member after making the business payment, and storing it in the member account of the organization member; synchronizing the business payment bill from the member account to the co-management of the institution to which the member belongs account to be added to the list of bills in the joint management account; according to the bill addition request submitted by the organization member for the business payment bill, obtain the bill associated with the business payment bill; return the bill based on the account association relationship between the member account and the joint management account To the joint management account to link to the business payment bill in the bill list.
  • the bill processing device includes: a bill acquisition module, configured to obtain the business payment bill obtained by the organization member after the business payment, and store it in the member account of the organization member; a bill synchronization module, configured to transfer the business payment bill from the member The account is synchronized to the co-management account of the institution to which the institutional member associated with the member account is added to the list of bills in the co-management account; the bill adding module is configured to obtain and due Bills associated with public payment bills; the bill return module is configured to return the bills to the joint management account based on the account association relationship between the member account and the joint management account, so as to be associated with the business payment bill in the bill list.
  • One or more embodiments of the present specification provide an electronic device, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:
  • the business payment bill obtained after the business payment is stored in the member account of the organization member;
  • the business payment bill is synchronized from the member account to the co-management account of the organization member's institution associated with the member account, so as to be added to the bill in the co-management account List;
  • One or more embodiments of this specification provide a storage medium for storing computer-executable instructions.
  • the following processes are implemented: obtain the business-related payment bills obtained by the members of the organization after making business-related payments, And store it in the member account of the organization member; Synchronize the business payment bill from the member account to the co-management account of the organization member's institution associated with the member account, so as to add it to the bill list in the co-management account;
  • the submitted note addition request obtains the note associated with the business payment bill; based on the account association relationship between the member account and the joint management account, the note is returned to the joint management account to be associated with the business payment bill in the bill list.
  • Fig. 1 is a processing flowchart of a bill processing method provided by one or more embodiments of this specification
  • Fig. 2 is a schematic diagram of the relationship between an account user, an account and a bill in a bill processing method provided by one or more embodiments of this specification;
  • Fig. 3 is a processing flowchart of creating a co-management account in a bill processing method provided by one or more embodiments of this specification;
  • Fig. 4 is a processing flowchart of a bill processing method applied in a bill reimbursement scenario provided by one or more embodiments of this specification;
  • Fig. 5 is a schematic structural diagram of a bill processing device provided by one or more embodiments of this specification.
  • Fig. 6 is a schematic structural diagram of an electronic device provided by one or more embodiments of this specification.
  • FIG. 1 is a processing flowchart of a bill processing method provided in this embodiment.
  • FIG. 2 is a schematic diagram of the relationship between an account user, an account, and a bill in a bill processing method provided in this embodiment.
  • Fig. 3 is a flow chart of creating a co-management account in a bill processing method provided by this embodiment.
  • the execution subject of the ticket processing method provided in this embodiment may be a server.
  • the bill processing method provided in this embodiment specifically includes the following steps S102 to S108.
  • the bill processing method provided in this embodiment can synchronize the business payment bill to the joint management account when obtaining the business payment bill through the member account, and send it back to the joint management account when obtaining the bill associated with the business payment bill. Simplify the reimbursement bill reimbursement process for organization members, shorten the waiting time required for the reimbursement process, and correspondingly improve the management efficiency of the organization's bill managers.
  • Step S102 obtaining the business payment bill obtained by the organization member after making the business payment, and storing it in the member account of the organization member.
  • Institutions can be enterprises, schools, associations, or other organizations. Taking the organization as an example, the members of the organization can be the employees of the enterprise, and the bill manager in the following can be the manager of the enterprise, or the financial staff designated by the enterprise. Organization members and ticket managers belong to the same organization.
  • Business payment can appear in business trip scenarios, for example, buying round-trip train tickets between the business trip location and the original place; it can also appear in the purchase of items needed for work, for example, purchasing office supplies; it can also appear in the scene of entertaining customers Next, for example, treat a client to dinner.
  • business trip scenarios for example, buying round-trip train tickets between the business trip location and the original place; it can also appear in the purchase of items needed for work, for example, purchasing office supplies; it can also appear in the scene of entertaining customers Next, for example, treat a client to dinner.
  • the above scenarios are just a few examples, and there are other scenarios of business payment, which will not be repeated here.
  • Member accounts of institutional members may be data accounts used by individual institutional members that can perform payment operations, for example, personal platform accounts, social accounts, and platform accounts on shopping platforms of institutional members on third-party payment platforms.
  • the bill processing method provided by this embodiment further includes: establishing Request to create a co-management account; link the institutional account and fund account of the bill manager to the co-management account according to the pre-set institutional role of the co-management account; link the member accounts of each institution member to the co-management account according to the pre-set member roles of the co-management account .
  • the institutional account of the bill manager can be the data account used by the bill manager personally, for example, the personal platform account of the third-party payment platform of the enterprise legal person; it can also be the institutional account of the institution to which the bill manager belongs, for example, the The enterprise account of the three-party payment platform.
  • the note manager who creates the institutional account and jointly-managed account may or may not be the same person as the note manager who uses the institutional account and jointly-managed account to manage notes in the actual scenario.
  • an enterprise manager creates an institutional account and a jointly managed account
  • he or she can grant the designated financial staff some authority over the institutional account, so that the financial staff can use the institutional account and the jointly managed account to manage bills.
  • the account users in Fig. 2 include institutional members 204 and bill managers 202, the accounts include institutional accounts 206, joint management accounts 208, member accounts 210, and capital accounts 212, and bills include bills 214 stored in member accounts 210 and joint management accounts 208. Stored notes 216.
  • step S302 the bill manager creates a co-management account. That is, the note manager 202 in FIG. 2 creates a co-management account 208 .
  • Step S304 binding the co-management account with the member account of the organization member. That is, the member account 210 in FIG. 2 is associated with the co-management account 208 .
  • Step S306 binding the co-management account with the capital account, that is, linking the capital account 212 in FIG. 2 to the co-management account 208 .
  • the fund account 212 in FIG. 2 can be linked to the co-management account 208 by means of mounting.
  • Mounting refers to a process by which the operating system makes computer files and directories on a storage device (such as a hard disk, CD-ROM, or shared resource) accessible to users through the computer's file system.
  • the co-management account 208 is mounted with the fund account 212, which can be understood as, for example, the member account 210 associated with the co-management account 208 can access the fund account 212 through the co-management account 208, specifically, when performing a payment operation through the member account 210, you can select the fund
  • the account 212 serves as a capital contribution account; the institutional account 206 associated with the co-management account 208 can access the capital account 212 through the co-management account 208 , specifically, the institutional account 206 can transfer funds to the capital account 212 .
  • Step S308 the note manager transfers money to the fund account. That is, the note manager 202 in FIG. 2 manages the fund account 212 through the institutional account 206.
  • the management method may be to designate the fund account 212 as the payee of the transfer, and transfer funds in other accounts to the fund account 212.
  • joint management account in this embodiment is different from the joint management account opened by the bank.
  • the joint management account is a different type of account from the member account or institutional account. This account can be regarded as a virtual account that cannot be logged in .
  • Co-management accounts can pre-set organization roles and member roles, and configure different functions and permissions according to organization roles and member roles. Institutional roles include funding roles and managerial roles.
  • the fund account linked to the co-management account according to the role of the fund can be regarded as a public wallet, that is, each member account linked to the co-management account according to the member role can choose the fund account as the payment method when making payment, and use the fund Payment of funds in the account.
  • the employees of the organization make public payments through the employee account, they will choose the fund account as the payment method, that is, directly use the funds of the organization to pay, and there is no need for the employee to advance the funds and reimburse them afterwards.
  • the institutional account linked to the co-management account according to the manager role can be regarded as the manager of the co-management account.
  • the note manager cannot directly log in to the co-management account, but the note manager can manage the notes in the co-management account through the institutional account.
  • the organization account 206 manages a ticket 216 , which is stored in the co-management account 208 , and the note 216 is obtained after synchronizing the note 214 stored in the member account 210 to the co-management account 208 .
  • the member account linked to the joint management account according to the member role can be regarded as the bill provider and the bill provider of the joint management account. And each member account can use the capital account corresponding to the joint management account to make business-related payments.
  • organization members 204 use the funds in the fund account 212 for consumption, and the bills 214 stored in the member account 210 are synchronized to the co-management account 208, and are synchronously sent to the co-management account 208, that is, stored in the co-management account 208 Note 216.
  • the institutional account of the note manager can be associated with one or more joint management accounts; the joint management account can be associated with the capital account, and one joint management account can be associated with multiple member accounts.
  • obtain the business payment bill obtained after the organization member makes the business payment including: obtaining the confirmation request of the organization member to make the business payment; the confirmation request carries the member account ID of the member account of the organization member and the fund account of the organization ID of the capital account; the member account and the capital account are associated with the jointly managed account; obtain the business payment bill obtained after the business payment is made according to the ID of the member account and the ID of the fund account.
  • the member account 210 is associated with the co-management account 208
  • the capital account 212 is associated with the co-management account 208
  • the organization member 204 can use the association relationship between the member account 210 and the co-management account 208 and the association relationship between the co-management account 208 and the capital account 212
  • the funds in the funds account 212 are used to make business payments.
  • a payment method list composed of various payment methods bound to the personal platform account can be obtained, and the organization member can select the fund account of the organization As a payment method, and to confirm the payment, issue a confirmation request for business payment. Then the confirmation request carries the member account ID of the personal platform account and the fund account ID of the fund account.
  • the server After the business payment is made according to the member account ID and the capital account ID, the server obtains the business payment bill.
  • the bills of the fund account whose payment method is an institution are all business-paying bills, and the server can judge whether the newly obtained bills of the member account are business-paying bills according to the fund account identifier.
  • Step S104 synchronizing the business payment bill from the member account to the co-management account of the institution to which the institutional member is associated with the member account, so as to add it to the list of bills in the co-management account.
  • the server can synchronize the business payment bill from the member account to the co-management account of the organization member's institution associated with the member account.
  • the bill 214 is synchronized from the member account 210 to the co-management account 208, Obtain note 216. Synchronization can be understood as copying a piece of data in one account and sending it to another account.
  • a bill list is stored in the joint management account, and the bill list is composed of multiple business payment bills that are synchronized to the joint management account by different member accounts.
  • Step S106 according to the note adding request submitted by the organization member for the business payment bill, obtain the note associated with the business payment bill.
  • the bill processing method provided by this embodiment further includes: according to the bill access request of the organization member, obtaining a member bill list composed of various business-related bills in the member account; 1. Pay bills on business, query the bill status of bills paid on business; if the bill status is unreturned, get the add control configuration data of the bill add control; render and generate member bill list according to member bill list and add control configuration data Display the page.
  • the server can obtain business-related payment bills from the bills of member accounts according to the capital account identifier, and then obtain a list of member bills composed of various business-related payment bills.
  • the server can obtain business-related payment bills from the bills of member accounts according to the capital account identifier, and then obtain a list of member bills composed of various business-related payment bills.
  • add a specified mark to the business-paying bill and then filter according to the specified mark to obtain a list of member bills composed of business-paying bills.
  • the server may store the association between the business payment bill and the receipt. If the invoice associated with the business-paying bill is obtained from the query, the status of the bill is determined to be returned; if it is determined after the query that the bill associated with the business-paying bill does not exist, the status of the bill is determined to be unreceived. At any point in time, the status of a bill for business payment can only be one of "Receipt" and "Not Receipt".
  • Organization members can add the bills associated with the business-paying bills through the bill adding control.
  • the method for processing the invoice provided in this embodiment further includes: obtaining the merchant corresponding to the on-duty payment bill According to the bill issuance information, determine whether the merchant supports the issuance of electronic bills; if so, obtain the first control configuration data of the electronic bill request control; according to the first control configuration data, configure the bill acquisition method for business payment bills.
  • the server acquires the bill issuing information of the merchant corresponding to the business payment bill, and the bill issuing information includes information on whether the merchant supports issuing electronic bills, and/or information on whether the merchant supports issuing paper bills.
  • the bill issuing information of merchant 1 includes not supporting the issuance of electronic bills, but supporting the issuance of paper bills.
  • the server judges whether the merchant supports the issuance of electronic bills according to the bill issuance information, and if the merchant supports the issuance of electronic bills, obtains the configuration data of the first control of the electronic bill request control; configures the bill acquisition method for paying bills on business according to the configuration data of the first control .
  • a button is configured on the right side of the business bill 1, and the organization member can request an electronic bill from the merchant by clicking the button.
  • electronic bills have the same codes issued by tax authorities, so they have the same credential effect as ordinary paper bills, but electronic bills are more convenient than ordinary paper bills in all aspects of billing and reimbursement. Therefore, If the merchant supports the issuance of electronic bills, the electronic bill request control can be configured first, which can improve the efficiency and convenience of all links such as billing and reimbursement.
  • the following operations are performed: according to the bill issuing information, it is judged whether the merchant supports the issuance of paper bills; if so, obtain the paper According to the configuration data of the second control of the bill request control and the configuration data of the third control of the paper bill upload control, according to the configuration data of the second control and the configuration data of the third control, configure the bill acquisition method for paying bills on business; if not, obtain The third control configures the data, according to the configuration data of the third control, configures the ticket acquisition method for business payment bills.
  • the bill issuance information determine whether the merchant supports the issuance of paper bills; if the merchant supports the issuance of paper bills, then obtain the second control configuration data of the paper bill request control and the third control configuration data of the paper bill upload control, according to the first
  • the second control configuration data and the third control configuration data are used to configure the way to obtain bills for business payment bills.
  • an icon control is configured on the right side of business payment bill 1, and organization members can request from the merchant by clicking the icon control paper receipts.
  • there is an arrow control configured on the right side of the business payment bill 1. By clicking the arrow control, organization members can obtain the paper bill image as the bill associated with the business payment bill through image acquisition. The receipt obtained after OCR processing the receipt image is used as the receipt associated with the business payment bill.
  • the organization members can find the same type of invoices as the invoices associated with the business bills as a substitute for the invoices associated with the business bills.
  • the server obtains the configuration data of the third control, and configures the method of obtaining receipts for paying bills on business according to the configuration data of the third control. For example, there is an arrow control configured on the right side of business payment bill 1. By clicking the arrow control, organization members can obtain the paper bill image as the bill associated with the business payment bill through image acquisition. The receipt obtained after performing OCR processing on the receipt image is used as the receipt associated with the business payment bill.
  • the bill associated with the business payment bill including: according to the related bill upload request submitted by the organization member for the business payment bill, obtain the associated bill upload page configuration data to generate the associated bill upload page corresponding to the business payment bill; obtain the bill image of the paper bill uploaded by the organization members on the bill upload page; perform OCR processing on the bill image to obtain the bill associated with the business payment bill .
  • an organization member clicks the paper bill upload control on the right side of a certain business-related bill, and the server obtains and uploads the associated bill submitted by the organization member for the business-related bill.
  • the associated bill upload page can call the OCR scanning function to collect the bill image of the paper bill and perform OCR processing to obtain the bill associated with the business payment bill.
  • the associated bill upload page can also call the image collection function to collect the bill image of the paper bill, and use the bill image as the bill associated with the business payment bill.
  • the bill addition request submitted by the organization member for the business payment bill obtain the bill associated with the business payment bill, including: according to the electronic bill acquisition request submitted by the organization member for the business payment bill, generate a bill request message and Send a bill request message to the merchant corresponding to the business bill payment; the electronic bill acquisition request carries the member account ID and the bill ID of the business bill; obtain the electronic bill sent by the merchant based on the member account ID; Issuing; linking electronic bills to business bills.
  • the organization member clicks the electronic bill request control on the right side of a certain business payment bill, and the server obtains the electronic bill acquisition request submitted by the organization member for the business payment bill , the server generates a bill request message according to the electronic bill acquisition request and sends the bill request message to the merchant corresponding to the business bill payment.
  • the merchant sends the requested electronic bill to the member account according to the member account identifier, and the electronic bill is issued by the merchant according to the bill identifier carried in the bill request message.
  • the server associates the electronic bill with the business payment bill.
  • the bill addition request submitted by the organization member for the business payment bill obtain the bill associated with the business payment bill, including: determine multiple business payment bills selected by the organization member according to the bill selection operation of the organization member ;According to the combined bill addition request, obtain bills associated with multiple business payment bills.
  • organization members can click the multi-choice mode control on the display page of business-related bills.
  • multi-choice mode organization members select multiple business-related bills and click Merge Bills, and the server obtains the bills according to the organization members. Select the operation to determine the multiple business payment bills selected by the organization members; the organization members can click the control to add combined bills, and the server will obtain the request to add combined bills.
  • Step S108 based on the account association relationship between the member account and the joint management account, the bill is returned to the joint management account, so as to be associated with the business payment bill in the bill list.
  • the member account 210 synchronizes the stored note 214 to the joint management account 208 to obtain the note 216 stored in the joint management account 208 .
  • the server when an organization member uploads the bill to the member account, the server immediately synchronizes the bill to the management account, thereby eliminating the need for the organization member to organize the bills to be reimbursed and reducing the workload of the organization member.
  • the server can synchronize the business payment bill from the member account to the co-management account of the organization member’s institution associated with the member account, so the list of bills in the co-management account includes from Each member account synchronizes business payment bills. Therefore, after the bills of the member accounts are synchronized to the joint management account, the returned bills can be associated with the business payment bills in the bill list according to the association between business payment bills and bills. Then the bill manager can intuitively and clearly perceive which bills associated bills have been returned and which bills associated bills have not been returned through the institutional account and joint management account.
  • the bill processing method provided in this embodiment further includes: obtaining the bill access conditions submitted by the bill manager through the institutional account; according to the association relationship between the institutional account and the co-management account, obtaining the target bill from the bill list that meets the bill access conditions list; process 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.
  • the bill manager 202 can manage the bills 216 stored in the joint management account 208 through the institutional account 206 and the joint management account 208 associated with the institutional account 206 .
  • Bill access conditions include, but are not limited to, the time period to which the bill belongs, organization members, bill types, bill tags, and bill groups.
  • the bill manager can use the institutional account to filter the bills from the list of co-managed accounts according to the time period from X, Y, to X, Z. Pay bills on business within the time period to get a list of target bills.
  • the bill manager can process the target bill selected by the bill manager in the target bill list through the institutional account, and the processing methods include but are not limited to viewing processing, download processing, obtaining request prompt processing, rejection processing, and bill parameter statistics processing.
  • process the bill associated with the target bill according to the associated bill processing request submitted by the bill manager for the target bill in the list of target bills including: obtaining the bill associated with the target bill according to the bill viewing request submitted by the bill manager for the target bill
  • the configuration data of the target ticket and the ticket display page to render and generate the ticket display page of the target ticket.
  • the server obtains the bill view request submitted by the bill manager for the target bill through the organization account, and the bill view request carries the bill ID of the target bill, and the server obtains the target bill associated with the target bill and the configuration data of the bill display page according to the bill ID. Render and generate the bill display page of the target bill, and the bill display interface displays the bills associated with the template bill.
  • process the bill 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 including: according to the bill return prompt request submitted by the bill manager for the target bill, send back The member account of the target bill sends a bill return reminder message.
  • the server obtains the bill return prompt request submitted by the bill manager for the target bill through the organization account, and the bill return prompt request carries the bill identifier of the target bill, and the server determines the member account that returns the target bill according to the bill identifier, and sends The member account sends a reminder message for bill return.
  • the prompt information of bill return can be understood as, the business payment bill obtained by the organization member after the business payment is synchronized to the joint management account, but the associated bill is not returned to the joint management account after a long period of time, the bill manager passes this
  • the note return reminder message urges the organization members to return the note as soon as possible.
  • the bill processing method provided by this embodiment, firstly, obtain the business payment bills obtained by the organization members after making business payments, and store them in the member accounts of the organization members; secondly, synchronize the business payment bills from the member accounts to The co-management account of the institution to which the institutional member belongs to the member account is added to the list of bills in the co-management account, and then, according to the note addition request submitted by the organization member for the business payment bill, the bill associated with the business payment bill is obtained; finally . Based on the account association relationship between the member account and the co-management account, the bill is returned to the co-management account, so as to be associated with the business payment bill in the bill list.
  • the bill reimbursement process of organization members can be simplified, the waiting time required for the reimbursement process can be shortened, and the management efficiency of the bill managers of the organization can be improved correspondingly.
  • the bill processing method provided by this embodiment is further described below in combination with bill reimbursement scenarios.
  • FIG. 4 is a processing flowchart of a bill processing method applied in a bill reimbursement scenario provided by this embodiment.
  • step S402 the members of the organization perform business payment processing through the capital account corresponding to the jointly managed account.
  • the server may obtain the business payment bill obtained by the organization member after making the business payment.
  • Step S404 judging whether the merchant supports issuing electronic bills.
  • the server acquires the bill issuing information of the merchant corresponding to the business payment bill, and the bill issuing information includes information on whether the merchant supports issuing electronic bills, and/or information on whether the merchant supports issuing paper bills.
  • the server judges whether the merchant supports issuing electronic bills according to the bill issuing information.
  • step S406 If yes, execute step S406; if not, execute step S408.
  • Step S406 acquiring the electronic receipt sent by the merchant.
  • the first control configuration data of the electronic bill request control is obtained; according to the first control configuration data, the way of obtaining bills for paying bills on business is configured.
  • a button is configured on the right side of the business bill 1, and the organization member can request an electronic bill from the merchant by clicking the button.
  • an organization member clicks the electronic bill request control on the right side of a certain business-related bill, and the server obtains the electronic bill acquisition request submitted by the organization member for the business-related bill.
  • the electronic bill acquisition request generates a bill request message and sends the bill request message to the merchant corresponding to the business bill payment.
  • the electronic bill request control can be configured first, which can improve the efficiency and convenience of all links such as billing and reimbursement.
  • the merchant sends the requested electronic bill to the member account according to the member account identifier, and the electronic bill is issued by the merchant according to the bill identifier carried in the bill request message.
  • the server associates the electronic bill with the business payment bill.
  • obtaining the electronic receipt sent by the merchant may also be obtaining an email sent by the merchant, and the attachment of the email is the requested electronic receipt.
  • Step S408 judging whether the merchant supports issuing paper receipts. If yes, execute step S410; if not, execute step S412.
  • the server executes step S408.
  • the server judges whether the merchant supports issuing paper bills according to the bill issuing information; if the merchant supports issuing paper bills, obtain the second control configuration data of the paper bill request control and upload the paper bills
  • the configuration data of the third control of the control according to the configuration data of the second control and the configuration data of the third control, configure the ticket acquisition method of the business payment bill, for example, an icon control is configured on the right side of the business payment bill 1, and the organization member A paper receipt can be requested from the merchant by clicking the icon control.
  • step S408 performed by the server can be omitted, and it is up to the staff of the organization to decide whether to upload the paper receipt issued by the merchant or upload the paper receipt of the same type as the business payment bill, that is, the server executes step S404 Afterwards, if the merchant does not support the issuance of electronic bills, step S410 is executed.
  • Step S410 acquiring the image of the paper receipt uploaded by the organization member and performing OCR processing.
  • the merchant supports the issuance of paper receipts, then obtain the configuration data of the second control of the paper receipt request control and the configuration data of the third control of the paper receipt upload control.
  • the configuration data of the second control and the third control configure the The method of obtaining bills for paying bills, for example, an icon control is configured on the right side of business bill 1, and organization members can request paper bills from merchants by clicking the icon control.
  • there is an arrow control configured on the right side of the business payment bill 1. By clicking the arrow control, organization members can obtain the paper bill image as the bill associated with the business payment bill through image acquisition. The receipt obtained after OCR processing the receipt image is used as the receipt associated with the business payment bill.
  • the server obtains the configuration data of the third control, and configures the method of obtaining receipts for paying bills on business according to the configuration data of the third control.
  • organization members can obtain the paper bill image as the bill associated with the business payment bill through image acquisition.
  • the receipt obtained after performing OCR processing on the receipt image is used as the receipt associated with the business payment bill.
  • step S412 organization members obtain paper receipts of the same type. It should be noted that step S412 is not executed by the server, but by the personnel of the institution. If the merchant does not support the issuance of paper invoices, in this case, the organization members can find the same type of invoices as the invoices associated with the business bills as a substitute for the invoices associated with the business bills.
  • Step S414 storing the acquired ticket in the member account.
  • the electronic bill sent by the merchant, or the bill obtained by OCR processing the image of the paper bill, is stored in the member account of the organization member.
  • Step S416, return the note to the co-management account. Transfer bills back from member accounts to joint accounts.
  • the bill manager can view or download the bills stored in the joint management account based on the association relationship between the institutional account and the joint management account.
  • the method embodiment shown in FIG. 4 can implement various processes in the foregoing method embodiments, and details are not repeated here.
  • the bill processing method provided by this embodiment, firstly, obtain the business payment bills obtained by the organization members after making business payments, and store them in the member accounts of the organization members; secondly, synchronize the business payment bills from the member accounts to The co-management account of the institution to which the institutional member belongs to the member account is added to the list of bills in the co-management account, and then, according to the note addition request submitted by the organization member for the business payment bill, the bill associated with the business payment bill is obtained; finally . Based on the account association relationship between the member account and the co-management account, the bill is returned to the co-management account, so as to be associated with the business payment bill in the bill list.
  • the bill reimbursement process of organization members can be simplified, the waiting time required for the reimbursement process can be shortened, and the management efficiency of the bill managers of the organization can be improved correspondingly.
  • FIG. 5 is a schematic structural diagram of a first bill processing device provided by one or more embodiments of this specification. As shown in FIG.
  • the bill processing device includes: a bill acquisition module 502 configured to obtain a business payment bill obtained by an organization member after paying for business, and store it in the member account of the organization member; a bill synchronization module 504, It is configured to synchronize the public payment bill from the member account to the co-management account of the institution to which the institution member belongs associated with the member account, so as to add to the bill list in the co-management account; bill adding module 506 , configured to obtain a note associated with the on-duty payment bill according to the note addition request submitted by the institution member for the on-duty payment bill; the note return module 508 is configured to, based on the member account and the According to the account association relationship of the co-management account, the bill is returned to the co-management account, so as to be associated with the business payment bill in the bill list.
  • a bill acquisition module 502 configured to obtain a business payment bill obtained by an organization member after paying for business, and store it in the member account of the organization member
  • a bill synchronization module 504 It is configured to
  • FIG. 5 is a schematic structural diagram of an electronic device provided by one or more embodiments of this specification.
  • electronic devices may have relatively large differences due to different configurations or performances, and may include one or more processors 601 and memories 602, and one or more storage applications or data may be stored in the memories 602 .
  • the storage 602 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 602 may include one or more modules (not shown), and each module may include a series of computer-executable instructions in the electronic device.
  • the processor 601 may be configured to communicate with the memory 602, and execute a series of computer-executable instructions in the memory 602 on the electronic device.
  • the electronic device may also include one or more power sources 603, one or more wired or wireless network interfaces 604, one or more input/output interfaces 605, one or more keyboards 606, and the like.
  • the electronic device includes a memory and one or more programs.
  • One or more programs are stored in memory, and one or more programs may include one or more modules.
  • Each module may include a series of computer-executable instructions in an 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 operations:
  • the business payment bill obtained after the business payment is stored in the member account of the organization member; the business payment bill is synchronized from the member account to the co-management account of the organization member's institution associated with the member account, so as to be added to the bill in the co-management account List;
  • the bill associated with the business payment bill is obtained. Pay bills on business.
  • an embodiment of a storage medium provided in this specification is as follows: corresponding to the above-described bill processing method, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium may be a U disk, an optical disk, a hard disk, and the like.
  • the storage medium provided in this embodiment is used to store computer-executable instructions.
  • the following process is implemented: acquire the business-related payment bills obtained by the members of the organization after making business-related payments, and store them in the members of the organization members Account; Synchronize business payment bills from the member account to the co-management account of the organization member’s institution associated with the member account, so as to add to the bill list in the co-management account; according to the bill addition request submitted by the organization member for the business payment bill, obtain Notes associated with business-related bills; based on the account association relationship between the member account and the joint management account, the bills are returned to the joint-management account to be associated with the business-related bills in the bill list.
  • the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvement in method flow).
  • improvements in many current method flows can be regarded as the direct improvement of the hardware circuit structure.
  • Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules.
  • a Programmable Logic Device such as a Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory.
  • controller in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, the means for implementing various functions can be regarded as both software modules implementing the method and structures within hardware components.
  • a typical implementing device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.
  • one or more embodiments of this specification may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present description 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.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information.
  • Information may be computer readable instructions, data structures, modules of a program, or other data.
  • Examples of storage media for computers 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 technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
  • computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本说明书实施例提供了票据处理方法及装置。其中，所述票据处理方法包括：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。

Description

票据处理方法、装置、电子设备及存储介质 技术领域
本说明书涉及数据处理技术领域，尤其涉及一种票据处理方法及装置。
背景技术
票据通常具有一定的凭据效力，例如票据作为企业中会计核算的原始依据，同时也是审计机构、税务机构执法检查的重要依据。机构员工根据票据进行费用报销时，需要填写报表并提交票据，由机构的票据管理者进行审核，报销流程较为繁琐，报销过程所需的时间较长，需要消耗机构成员和票据管理者双方大量的时间和精力。
发明内容
本说明书一个或多个实施例提供了一种票据处理方法。票据处理方法包括：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
本说明书一个或多个实施例提供了一种票据处理装置。票据处理装置包括：账单获取模块，被配置为获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；账单同步模块，被配置为将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；票据添加模块，被配置为根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；票据回传模块，被配置为基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
本说明书一个或多个实施例提供了一种电子设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，计算机可执行指令在被执行时使处理器：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
本说明书一个或多个实施例提供了一种存储介质，用于存储计算机可执行指令，计算机可执行指令在被执行时实现以下流程：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；基于成员账户与共管账 户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的一种票据处理方法的处理流程图；
图2为本说明书一个或多个实施例提供的一种票据处理方法中账户使用者、账户以及票据的关系示意图；
图3为本说明书一个或多个实施例提供的一种票据处理方法中创建共管账户的处理流程图；
图4为本说明书一个或多个实施例提供的一种应用于票据报销场景下的票据处理方法的处理流程图；
图5为本说明书一个或多个实施例提供的一种票据处理装置的结构示意图；
图6为本说明书一个或多个实施例提供的一种电子设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书提供的一种票据处理方法实施例。图1为本实施例提供的一种票据处理方法的处理流程图。图2为本实施例提供的一种票据处理方法中账户使用者、账户以及票据的关系示意图。图3为本实施例提供的一种票据处理方法中创建共管账户的处理流程图。
本实施例提供的票据处理方法的执行主体可以是服务器。
参照图1所示，本实施例提供的票据处理方法具体包括下述步骤S102至步骤S108。
本实施例提供的票据处理方法，通过在通过成员账户获取因公支付账单时将该因公支付账单同步到共管账户，且在获取与因公支付账单关联的票据时回传到共管账户，能够简化机构成员的报销票据报销流程，缩短报销流程所需的等待时间，对应地也提高了机构的票据管理者的管理效率。
步骤S102，获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户。
机构可以是企业，可以是学校，可以是协会，也可以是其他团体组织。以机构为企业为例，机构成员可以是企业的员工，下文中的票据管理者可以是企业的管理者，也可以是企业指定的财务工作人员。机构成员和票据管理者属于同一机构。
因公支付可以出现在出差场景中，例如，购买出差地点与原地之间往返的火车票；也可以出现在采购工作所需物品时，例如，购买办公用品；还可以出现在招待客户的场景下，例如，请客户吃饭。以上几种场景仅为几种示例，还有其他的因公支付的场景，此处不再一一赘述。
机构成员的成员账户，可以是机构成员个人所使用的能够进行支付操作的数据账户，例如，机构成员的第三方支付平台的个人平台账户、社交账户、在购物平台的平台账户等。
可选的，获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户步骤执行之前，本实施例提供的票据处理方法还包括：根据票据管理者的共管账户建立请求，创建共管账户；按照共管账户预先设置的机构角色，将票据管理者的机构账户和资金账户关联至共管账户；按照共管账户预先设置的成员角色，将各机构成员的成员账户关联至共管账户。
票据管理者的机构账户，可以是票据管理者个人所使用的数据账户，例如，企业法人的第三方支付平台的个人平台账户；也可以是票据管理者所属机构的机构账户，例如，企业在第三方支付平台的企业账户。
需要注意的是，创建机构账户和共管账户的票据管理者与实际场景中利用机构账户和共管账户进行票据管理的票据管理者可能是同一人，也可能不是同一人。例如，企业管理者在创建机构账户和共管账户后，向指定的财务工作人员赋予机构账户的部分权限，使得该财务工作人员能够利用机构账户和共管账户进行票据管理。
图2中的账户使用者包括机构成员204和票据管理者202，账户包括机构账户206、共管账户208、成员账户210以及资金账户212，票据包括成员账户210中存储的票据214和共管账户208中存储的票据216。
参照图2和图3所示，步骤S302，票据管理者创建共管账户。即图2中的票据管理者202创建共管账户208。
步骤S304，将共管账户与机构成员的成员账户绑定。即图2中的成员账户210关联至共管账户208。
步骤S306，将共管账户与资金账户绑定，即图2中的资金账户212关联至共管账户208。
图2中的资金账户212关联至共管账户208可以通过挂载的方式。挂载是指由操作系统使一个存储设备(诸如硬盘、CD-ROM或共享资源)上的计算机文件和目录可供用户通过计算机的文件系统访问的一个过程。共管账户208挂载资金账户212，可以理解为，例如，与共管账户208关联的成员账户210可以通过共管账户208访问资金账户212，具体为，在通过成员账户210进行支付操作时，可以选择资金账户212作为出资账户；与共管账户208关联的机构账户206可以通过共管账户208访问资金账户212，具体为，机构账户206可以向资金账户212转入资金。
步骤S308，票据管理者向资金账户转账。即图2中的票据管理者202通过机构账户206管理资金账户212，管理方式可以是指定资金账户212作为转账的收款方，将其他账户中的资金转入该资金账户212。
需要强调的是，本实施例中的共管账户的定义不同于银行开设的共管账户，该共管账户是与成员账户或机构账户不同类型的账户，该账户可以视为一个无法被登录的虚拟的账户。共管账户可以预先设置机构角色和成员角色，按照机构角色和成员角色分别配置不同的功能和权限。机构角色包括资金角色和管理者角色。
按照资金角色关联至共管账户的资金账户可以被视为一个公用的钱袋，即，各个按照成员角色关联至共管账户的成员账户在进行支付时都可以选择该资金账户作为付款方式，使用该资金账户中的资金付款。
通常情况下，机构员工在通过员工账户进行对公支付时会将付款方式选择为该资金账户，即直接利用机构的资金付款，无需员工垫付资金事后报销。
按照管理者角色关联至共管账户的机构账户可以被视为该共管账户的管理者，票据管理者不能直接登录该共管账户，但票据管理者能够通过机构账户对共管账户中的票据进行管理。如图2所示，机构账户206管理票据216，该票据216存储于共管账户208，且该票据216是将成员账户210存储的票据214同步至共管账户208后得到的。
按照成员角色挂链至共管账户的成员账户可以被视为该共管账户的账单提供者和票据提供者。且各个成员账户可以利用共管账户对应的资金账户进行因公支付。如图2所示，机构成员204利用资金账户212中的资金进行消费，成员账户210存储的票据214被同步至共管账户208中，被同步发送到共管账户208中的票据即共管账户208中存储的票据216。
票据管理者的机构账户可以与一个或多个共管账户关联；共管账户可以与资金账户关联，一个共管账户可以与多个成员账户关联。
可选的，获取机构成员进行因公支付后获得的因公支付账单，包括：获取机构成员进行因公支付的确认请求；确认请求携带有机构成员的成员账户的成员账户标识和机构的资金账户的资金账户标识；成员账户与资金账户关联于共管账户；获取根据成员账户标识和资金账户标识进行因公支付后获得的因公支付账单。
结合图2可知，成员账户210关联于共管账户208，资金账户212关联至共管账户208，则机构成员204可以通过成员账户210与共管账户208的关联关系以及共管账户208与资金账户212的关联关系使用资金账户212中的资金来进行因公支付。
具体实施时，例如，通过机构成员的第三方支付平台的个人平台账户触发支付操作后，可获得该个人平台账户绑定的多种付款方式构成的付款方式列表，机构成员从中选择机构的资金账户作为付款方式，并确认支付，发出进行因公支付的确认请求。则该确认请求中携带有该个人平台账户的成员账户标识和资金账户的资金账户标识。
在根据成员账户标识和资金账户标识进行因公支付后，服务器获取因公支付账单。付款方式为机构的资金账户的账单均为因公支付账单，服务器可以根据资金账户标识判断成员账户新获取的账单是否为因公支付账单。
步骤S104，将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表。
在服务器获取因公支付账单后，服务器可以将因公支付账单从成员账户同步至与成员 账户关联的机构成员所属机构的共管账户，参照图2所示，票据214从成员账户210同步至共管账户208，得到票据216。同步可以理解为，复制一个账户中的一份数据并发送到另一个账户中。共管账户中存储有账单列表，该账单列表由分别由不同的成员账户同步到共管账户的多个因公支付账单构成。
步骤S106，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据。
可选的，获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户步骤执行之后，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据步骤执行之前，本实施例提供的票据处理方法还包括：根据机构成员的账单访问请求，获取成员账户中由各因公支付账单构成的成员账单列表；针对成员账单列表中的任一因公支付账单，查询因公支付账单的票据状态；若票据状态为未回票，则获取票据添加控件的添加控件配置数据；根据成员账单列表和添加控件配置数据，渲染生成成员账单列表的展示页面。
具体实施时，服务器可以根据资金账户标识从成员账户的账单中筛选得到因公支付账单，进而得到由各因公支付账单构成的成员账单列表，也可以在首次获取该因公支付账单并同步至共管账户时，为该因公支付账单添加指定标记，再根据指定标记筛选得到由因公支付账单构成的成员账单列表。
针对任一因公支付账单，服务器可以存储有该因公支付账单与票据的关联关系。若查询得到与该因公支付账单关联的票据，则确定票据状态为已回票；若查询后确定与该因公支付账单关联的票据不存在，则确定票据状态为未回票。在任一时间点，一个因公支付账单的票据状态只能是在“已回票”和“未回票”中的一项。
若票据状态为未回票，则获取票据添加控件的添加控件配置数据；根据成员账单列表和添加控件配置数据，渲染生成成员账单列表的展示页面，使得成员账单列表的展示页面中展示有票据添加控件。机构成员可以通过该票据添加控件添加该因公支付账单关联的票据。
可选的，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据步骤执行之前，本实施例提供的票据处理方法还包括：获取因公支付账单对应的商家的票据开具信息；根据票据开具信息，判断商家是否支持开具电子票据；若是，则获取电子票据请求控件的第一控件配置数据；根据第一控件配置数据，配置因公支付账单的票据获取方式。
服务器获取因公支付账单对应的商家的票据开具信息，该票据开具信息包括商家是否支持开具电子票据的信息，和/或，商家是否支持开具纸质票据的信息。例如，商家1的票据开具信息包括不支持开具电子票据，支持开具纸质票据。
服务器根据票据开具信息，判断商家是否支持开具电子票据，若商家支持开具电子票据，则获取电子票据请求控件的第一控件配置数据；根据第一控件配置数据，配置因公支付账单的票据获取方式。例如，在因公支付账单1的右侧配置有一个按钮，机构成员通过 单击该按钮可以向商家请求电子票据。电子票据与普通纸质票据一样具有税务机构统一发放的编码，因此与普通纸质票据具有同样的凭据效力，但电子票据在开票、报销等各个环节相比普通纸质票据都更加便捷，因此，若商家支持开具电子票据，优先配置电子票据请求控件，能够提高开票报销等各个环节的效率和便利性。
可选的，若根据票据开具信息，判断商家是否支持开具电子票据步骤执行之后的执行结果为否，执行如下操作：根据票据开具信息，判断商家是否支持开具纸质票据；若是，则获取纸质票据请求控件的第二控件配置数据和纸质票据上传控件的第三控件配置数据，根据第二控件配置数据和第三控件配置数据，配置因公支付账单的票据获取方式；若否，则获取第三控件配置数据，根据第三控件配置数据，配置因公支付账单的票据获取方式。
根据票据开具信息，判断商家是否支持开具纸质票据；若商家支持开具纸质票据，则获取纸质票据请求控件的第二控件配置数据和纸质票据上传控件的第三控件配置数据，根据第二控件配置数据和第三控件配置数据，配置因公支付账单的票据获取方式，例如，在因公支付账单1的右侧配置有一个图标控件，机构成员通过单击该图标控件可以向商家请求纸质票据。又例如，在因公支付账单1的右侧配置有一个箭头控件，机构成员通过单击该箭头控件可以通过图像采集的方式获取纸质票据的票据图像作为因公支付账单关联的票据，也可以将对票据图像进行OCR处理后得到的票据作为因公支付账单关联的票据。
若商家不支持开具纸质票据，在这种情况下，机构成员可以通过寻找与因公支付账单相同类型的票据作为因公支付账单关联的票据的替代品。服务器获取第三控件配置数据，根据第三控件配置数据，配置因公支付账单的票据获取方式。例如，在因公支付账单1的右侧配置有一个箭头控件，机构成员通过单击该箭头控件可以通过图像采集的方式获取纸质票据的票据图像作为因公支付账单关联的票据，也可以将对票据图像进行OCR处理后得到的票据作为因公支付账单关联的票据。
可选的，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据，包括：根据机构成员针对因公支付账单提交的关联票据上传请求，获得关联票据上传页面的配置数据，以生成与因公支付账单对应的关联票据上传页面；获取机构成员在票据上传页面上传的纸质票据的票据图像；对票据图像进行OCR处理，获得与因公支付账单关联的票据。
具体实施时，机构成员在因公支付账单的展示页面中，针对某个因公支付账单单击其右侧的纸质票据上传控件，则服务器获取机构成员针对因公支付账单提交的关联票据上传请求，获得关联票据上传页面的配置数据以生成与因公支付账单对应的关联票据上传页面。该关联票据上传页面可以调用OCR扫描功能，采集纸质票据的票据图像并进行OCR处理，获得与因公支付账单关联的票据。
该关联票据上传页面也可以调用图像采集功能，采集纸质票据的票据图像，将该票据图像作为与因公支付账单关联的票据。
可选的，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据，包括：根据机构成员针对因公支付账单提交的电子票据获取请求，生成票据 请求消息并向与因公支付账单对应的商家发送票据请求消息；电子票据获取请求携带有成员账户标识和因公支付账单的账单标识；获取商家基于成员账户标识发送的电子票据；电子票据为商家根据账单标识开具；将电子票据关联至因公支付账单。
具体实施时，机构成员在因公支付账单的展示页面中，针对某个因公支付账单单击其右侧的电子票据请求控件，则服务器获取机构成员针对因公支付账单提交的电子票据获取请求，服务器根据该电子票据获取请求生成票据请求消息并向与因公支付账单对应的商家发送票据请求消息。商家根据成员账户标识向成员账户发送被请求的电子票据，该电子票据是商家根据该票据请求消息中携带的账单标识开具的。服务器将该电子票据关联至因公支付账单。
可选的，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据，包括：根据机构成员的账单选择操作，确定被机构成员选中的多个因公支付账单；根据合并票据添加请求，获取与多个因公支付账单关联的票据。
具体实施时，机构成员可以在因公支付账单的展示页面中点击多选模式控件，机构成员在多选模式下选中多个因公支付账单并单击合并票据，则服务器获取根据机构成员的账单选择操作，确定被机构成员选中的多个因公支付账单；机构成员可以单击合并票据添加控件，则服务器获取合并票据添加请求，通过上传纸制品票据或向商家请求电子票据的方式获取与多个因公支付账单关联的票据。
步骤S108，基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
参照图2所示，成员账户210将存储的票据214同步至共管账户208，得到该共管账户208中存储的票据216。
可以理解为，当机构成员将票据上传至成员账户后，服务器马上将该票据同步到管理账户，从而省去了机构成员整理待报销的票据的过程，减少了机构成员的工作量。
在前述的步骤S104中，在服务器获取因公支付账单后，服务器可以将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，故共管账户中的账单列表包括从各个成员账户同步的因公支付账单，故成员账户的票据被同步至共管账户后，可以根据因公支付账单和票据的关联关系，将回传的票据关联至账单列表中的因公支付账单。则票据管理者可以通过机构账户和共管账户直观明确地感知哪些账单关联的票据已回传，哪些账单关联的票据尚未回传。
可选的，本实施例提供的票据处理方法还包括：获取票据管理者通过机构账户提交的账单访问条件；根据机构账户与共管账户的关联关系，从账单列表中获取满足账单访问条件的目标账单列表；根据票据管理者在目标账单列表中针对目标账单提交的关联票据处理请求，处理目标账单关联的票据。
参照图2所示，票据管理者202可以通过机构账户206、机构账户206关联的共管账户208，实现对共管账户208存储的票据216的管理。
账单访问条件包括且不限于，账单所属的时间段、机构成员、账单种类、账单标签、 账单分组。
例如，账单访问条件为X月Y日到X月Z日，则票据管理者可以通过机构账户从共管账户的账单列表中按照X月Y日到X月Z日的时间段筛选得到账单生成时间在该时间段内的因公支付账单，得到目标账单列表。账单管理者可以通过机构账户对目标账单列表中被账单管理者选中的目标账单进行处理，处理方式包括且不限于查看处理、下载处理、获取请求提示处理、驳回处理、账单参数统计处理。
可选的，根据票据管理者在目标账单列表中针对目标账单提交的关联票据处理请求，处理目标账单关联的票据，包括：根据票据管理者针对目标账单提交的票据查看请求，获取目标账单关联的目标票据以及票据展示页面的配置数据，以渲染并生成目标票据的票据展示页面。
服务器获取票据管理者通过机构账户针对目标账单提交的票据查看请求，该票据查看请求携带有目标账单的账单标识，服务器根据账单标识，获取目标账单关联的目标票据以及票据展示页面的配置数据，以渲染并生成目标票据的票据展示页面，该票据展示界面中展示有模板账单关联的票据。
可选的，根据票据管理者在目标账单列表中针对目标账单提交的关联票据处理请求，处理目标账单关联的票据，包括：根据票据管理者针对目标账单提交的票据回传提示请求，向回传目标账单的成员账户发送票据回传提示信息。
服务器获取票据管理者通过机构账户针对目标账单提交的票据回传提示请求，该票据回传提示请求携带有目标账单的账单标识，服务器根据账单标识，确定回传所述目标账单的成员账户，向该成员账户发送票据回传提示信息。票据回传提示信息可以理解为，机构成员进行因公支付后获得的因公支付账单同步至共管账户，但很长一段时间后都没有向共管账户回传关联的票据，则票据管理者通过该票据回传提示信息催促机构成员尽快回传票据。
综上，本实施例提供的票据处理方法，首先，获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；其次，将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表，接着，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；最后。基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。通过该技术方案，能够简化机构成员的票据报销流程，缩短报销流程所需的等待时间，对应地也提高了机构的票据管理者的管理效率。
下文结合票据报销场景进一步说明本实施例提供的票据处理方法。
图4为本实施例提供的一种应用于票据报销场景下的票据处理方法的处理流程图。
步骤S402，机构成员通过共管账户对应的资金账户进行因公支付处理。
本实施例中出现的各个账户、各个账户使用者以及票据与如图1所示的实施例中对应的概念相似，此处不再赘述。服务器可以获取机构成员进行因公支付后获得的因公支付账单。
步骤S404，判断商家是否支持开电子票据。
服务器获取因公支付账单对应的商家的票据开具信息，该票据开具信息包括商家是否支持开具电子票据的信息，和/或，商家是否支持开具纸质票据的信息。服务器根据票据开具信息判断商家是否支持开电子票据。
若是，则执行步骤S406，若否，则执行步骤S408。
步骤S406，获取商家发送的电子票据。
若商家支持开具电子票据，则获取电子票据请求控件的第一控件配置数据；根据第一控件配置数据，配置因公支付账单的票据获取方式。例如，在因公支付账单1的右侧配置有一个按钮，机构成员通过单击该按钮可以向商家请求电子票据。
机构成员在因公支付账单的展示页面中，针对某个因公支付账单单击其右侧的电子票据请求控件，则服务器获取机构成员针对因公支付账单提交的电子票据获取请求，服务器根据该电子票据获取请求生成票据请求消息并向与因公支付账单对应的商家发送票据请求消息。
电子票据与普通纸质票据一样具有税务机构统一发放的编码，因此与普通纸质票据具有同样的凭据效力，但电子票据在开票、报销等各个环节相比普通纸质票据都更加便捷，因此，若商家支持开具电子票据，优先配置电子票据请求控件，能够提高开票报销等各个环节的效率和便利性。
商家根据成员账户标识向成员账户发送被请求的电子票据，该电子票据是商家根据该票据请求消息中携带的账单标识开具的。服务器将该电子票据关联至因公支付账单。
在另一些实施例中，获取商家发送的电子票据，也可以是获取商家发送的电子邮件，该电子邮件的附件为被请求的电子票据。
步骤S408，判断商家是否支持开纸质票据。若是，则执行步骤S410；若否，则执行步骤S412。
服务器执行步骤S408，具体实施时，服务器根据票据开具信息，判断商家是否支持开具纸质票据；若商家支持开具纸质票据，则获取纸质票据请求控件的第二控件配置数据和纸质票据上传控件的第三控件配置数据，根据第二控件配置数据和第三控件配置数据，配置因公支付账单的票据获取方式，例如，在因公支付账单1的右侧配置有一个图标控件，机构成员通过单击该图标控件可以向商家请求纸质票据。又例如，在因公支付账单1的右侧配置有一个箭头控件，机构成员通过单击该箭头控件可以通过图像采集的方式获取纸质票据的票据图像作为因公支付账单关联的票据，也可以将对票据图像进行OCR处理后得到的票据作为因公支付账单关联的票据。
需要注意的是，在商家不支持开具电子票据的情况下，无论商家是否支持开纸质票据，机构成员都需要通过采集纸质票据的图像的方式将商家开具的纸质票据或机构成员获取的替代纸质票据上传并存储于成员账户。另外，在一些场景中，机构成员在因公支付后马上在商家开具了纸质票据。因此，在一些实施例中，由服务器执行的步骤S408可以被省略，由机构人员自行判断上传商家开具的纸制票据还是上传与因公支付账单同类型的纸质 票据，即在服务器执行步骤S404之后，若商家不支持开电子票据，则执行步骤S410。
步骤S410，获取机构成员上传的纸质票据的图像并进行OCR处理。
若商家支持开具纸质票据，则获取纸质票据请求控件的第二控件配置数据和纸质票据上传控件的第三控件配置数据，根据第二控件配置数据和第三控件配置数据，配置因公支付账单的票据获取方式，例如，在因公支付账单1的右侧配置有一个图标控件，机构成员通过单击该图标控件可以向商家请求纸质票据。又例如，在因公支付账单1的右侧配置有一个箭头控件，机构成员通过单击该箭头控件可以通过图像采集的方式获取纸质票据的票据图像作为因公支付账单关联的票据，也可以将对票据图像进行OCR处理后得到的票据作为因公支付账单关联的票据。
服务器获取第三控件配置数据，根据第三控件配置数据，配置因公支付账单的票据获取方式。例如，在因公支付账单1的右侧配置有一个箭头控件，机构成员通过单击该箭头控件可以通过图像采集的方式获取纸质票据的票据图像作为因公支付账单关联的票据，也可以将对票据图像进行OCR处理后得到的票据作为因公支付账单关联的票据。
步骤S412，机构成员获取同类型的纸质票据。需要注意的是，步骤S412不是由服务器执行的，而是由机构人员执行的。若商家不支持开具纸质票据，在这种情况下，机构成员可以通过寻找与因公支付账单相同类型的票据作为因公支付账单关联的票据的替代品。
步骤S414，将获取的票据存储于成员账户。将商家发送的电子票据，或者，将对纸质票据的图像并进行OCR处理得到的票据，存储于机构成员的成员账户。
步骤S416，将票据回传到共管账户。将票据从成员账户回传到共管账户。
步骤S418，票据管理者查看下载票据。例如，票据管理者可基于机构账户与共管账户之间的关联关系，对共管账户中存储的票据进行查看处理或下载处理。
如图4所示的方法实施例，可以实现前述方法实施例中的各个过程，此处不再赘述。
综上，本实施例提供的票据处理方法，首先，获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；其次，将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表，接着，根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；最后。基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。通过该技术方案，能够简化机构成员的票据报销流程，缩短报销流程所需的等待时间，对应地也提高了机构的票据管理者的管理效率。
对应上述图1描述的票据处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种票据处理装置。图5为本说明书一个或多个实施例提供的第一种票据处理装置的结构示意图。如图5所示，票据处理装置包括：账单获取模块502，被配置为获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户；账单同步模块504，被配置为将所述因公支付账单从所述成员账户同步至与所述成员账户关联的所述机构成员所属机构的共管账户，以添加至所述共管账户中的账单列表；票据添加模块506，被配置为根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所 述因公支付账单关联的票据；票据回传模块508，被配置为基于所述成员账户与所述共管账户的账户关联关系将所述票据回传至所述共管账户，以关联至所述账单列表中的因公支付账单。
需要说明的是，本说明书中关于票据处理装置的实施例与本说明书中关于票据处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的票据处理方法的实施，重复之处不再赘述。
对应上述描述的应用于电子设备的票据处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种电子设备，该电子设备用于执行上述提供的票据处理方法。图5为本说明书一个或多个实施例提供的一种电子设备的结构示意图。
如图6所示，电子设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器601和存储器602，存储器602中可以存储有一个或一个以上存储应用程序或数据。其中，存储器602可以是短暂存储或持久存储。存储在存储器602的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括电子设备中的一系列计算机可执行指令。更进一步地，处理器601可以设置为与存储器602通信，在电子设备上执行存储器602中的一系列计算机可执行指令。电子设备还可以包括一个或一个以上电源603，一个或一个以上有线或无线网络接口604，一个或一个以上输入/输出接口605，一个或一个以上键盘606等。
在一个具体的实施例中，电子设备包括有存储器以及一个或一个以上的程序。其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块。每个模块可以包括对电子设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种的票据处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。一个具体的实施例中，该存储介质可以为U盘、光盘、硬盘等。
本实施例提供的存储介质，用于存储计算机可执行指令，计算机可执行指令在被执行时实现以下流程：获取机构成员进行因公支付后获得的因公支付账单，并存储至机构成员的成员账户；将因公支付账单从成员账户同步至与成员账户关联的机构成员所属机构的共管账户，以添加至共管账户中的账单列表；根据机构成员针对因公支付账单提交的票据添加请求，获取与因公支付账单关联的票据；基于成员账户与共管账户的账户关联关系将票据回传至共管账户，以关联至账单列表中的因公支付账单。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于票据处理方法的 实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如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、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为 既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书是参照根据本说明书实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、 动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (15)

  1. 一种票据处理方法，包括：
    获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户；
    将所述因公支付账单从所述成员账户同步至与所述成员账户关联的所述机构成员所属机构的共管账户，以添加至所述共管账户中的账单列表；
    根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据；
    基于所述成员账户与所述共管账户的账户关联关系将所述票据回传至所述共管账户，以关联至所述账单列表中的因公支付账单。
  2. 根据权利要求1的方法，所述获取机构成员进行因公支付后获得的因公支付账单，包括：
    获取所述机构成员进行因公支付的确认请求；所述确认请求携带有所述机构成员的成员账户的成员账户标识和所述机构的资金账户的资金账户标识；所述成员账户与所述资金账户关联于所述共管账户；
    获取根据所述成员账户标识和所述资金账户标识进行因公支付后获得的所述因公支付账单。
  3. 根据权利要求1的方法，所述根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据，包括：
    根据所述机构成员针对所述因公支付账单提交的关联票据上传请求，获得关联票据上传页面的配置数据，以生成与所述因公支付账单对应的关联票据上传页面；
    获取所述机构成员在所述票据上传页面上传的纸质票据的票据图像；
    对所述票据图像进行OCR处理，获得与所述因公支付账单关联的票据。
  4. 根据权利要求1的方法，所述根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据，包括：
    根据所述机构成员针对所述因公支付账单提交的电子票据获取请求，生成票据请求消息并向与所述因公支付账单对应的商家发送所述票据请求消息；所述电子票据获取请求携带有所述成员账户标识和所述因公支付账单的账单标识；
    获取所述商家基于所述成员账户标识发送的电子票据；所述电子票据为所述商家根据所述账单标识开具；
    将所述电子票据关联至所述因公支付账单。
  5. 根据权利要求1的方法，所述根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据，包括：
    根据所述机构成员的账单选择操作，确定被所述机构成员选中的多个所述因公支付账单；
    根据合并票据添加请求，获取与多个所述因公支付账单关联的票据。
  6. 根据权利要求1的方法，所述根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据步骤执行之前，还包括：
    获取所述因公支付账单对应的商家的票据开具信息；
    根据所述票据开具信息，判断所述商家是否支持开具电子票据；
    若是，则获取电子票据请求控件的第一控件配置数据；
    根据所述第一控件配置数据，配置所述因公支付账单的票据获取方式。
  7. 根据权利要求6的方法，若所述根据所述票据开具信息，判断所述商家是否支持开具电子票据步骤执行之后的执行结果为否，执行如下操作：
    根据所述票据开具信息，判断所述商家是否支持开具纸质票据；
    若是，则获取纸质票据请求控件的第二控件配置数据和纸质票据上传控件的第三控件配置数据，根据所述第二控件配置数据和所述第三控件配置数据，配置所述因公支付账单的票据获取方式；
    若否，则获取所述第三控件配置数据，根据所述第三控件配置数据，配置所述因公支付账单的票据获取方式。
  8. 根据权利要求1所述的方法，所述获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户步骤执行之前，还包括：
    根据票据管理者的共管账户建立请求，创建所述共管账户；
    按照所述共管账户预先设置的机构角色，将所述票据管理者的机构账户和资金账户关联至所述共管账户；
    按照所述共管账户预先设置的成员角色，将各所述机构成员的成员账户关联至所述共管账户。
  9. 根据权利要求1所述的方法，所述获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户步骤执行之后，所述根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据步骤执行之前，还包括：
    根据所述机构成员的账单访问请求，获取所述成员账户中由各所述因公支付账单构成的成员账单列表；
    针对所述成员账单列表中的任一所述因公支付账单，查询所述因公支付账单的票据状态；
    若所述票据状态为未回票，则获取票据添加控件的添加控件配置数据；
    根据所述成员账单列表和所述添加控件配置数据，渲染生成所述成员账单列表的展示页面。
  10. 根据权利要求8所述的方法，还包括：
    获取所述票据管理者通过所述机构账户提交的账单访问条件；
    根据所述机构账户与所述共管账户的关联关系，从所述账单列表中获取满足所述账单访问条件的目标账单列表；
    根据所述票据管理者在所述目标账单列表中针对目标账单提交的关联票据处理请求，处理所述目标账单关联的票据。
  11. 根据权利要求10所述的方法，所述根据所述票据管理者在所述目标账单列表中针对目标账单提交的关联票据处理请求，处理所述目标账单关联的票据，包括：
    根据所述票据管理者针对所述目标账单提交的票据查看请求，获取所述目标账单关联的目标票据以及票据展示页面的配置数据，以渲染并生成所述目标票据的票据展示页面。
  12. 根据权利要求10所述的方法，所述根据所述票据管理者在所述目标账单列表中针对目标账单提交的关联票据处理请求，处理所述目标账单关联的票据，包括：
    根据所述票据管理者针对所述目标账单提交的票据回传提示请求，向回传所述目标账单的成员账户发送票据回传提示信息。
  13. 一种票据处理装置，包括：
    账单获取模块，被配置为获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户；
    账单同步模块，被配置为将所述因公支付账单从所述成员账户同步至与所述成员账户关联的所述机构成员所属机构的共管账户，以添加至所述共管账户中的账单列表；
    票据添加模块，被配置为根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据；
    票据回传模块，被配置为基于所述成员账户与所述共管账户的账户关联关系将所述票据回传至所述共管账户，以关联至所述账单列表中的因公支付账单。
  14. 一种电子设备，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户；
    将所述因公支付账单从所述成员账户同步至与所述成员账户关联的所述机构成员所属机构的共管账户，以添加至所述共管账户中的账单列表；
    根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据；
    基于所述成员账户与所述共管账户的账户关联关系将所述票据回传至所述共管账户，以关联至所述账单列表中的因公支付账单。
  15. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    获取机构成员进行因公支付后获得的因公支付账单，并存储至所述机构成员的成员账户；
    将所述因公支付账单从所述成员账户同步至与所述成员账户关联的所述机构成员所 属机构的共管账户，以添加至所述共管账户中的账单列表；
    根据所述机构成员针对所述因公支付账单提交的票据添加请求，获取与所述因公支付账单关联的票据；
    基于所述成员账户与所述共管账户的账户关联关系将所述票据回传至所述共管账户，以关联至所述账单列表中的因公支付账单。
PCT/CN2022/103541 2021-05-25 2022-07-04 票据处理方法、装置、电子设备及存储介质 WO2022247964A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110572299.8A CN113222724B (zh) 2021-05-25 2021-05-25 票据处理方法及装置
CN202110572299.8 2021-05-25

Publications (1)

Publication Number Publication Date
WO2022247964A1 true WO2022247964A1 (zh) 2022-12-01

Family

ID=77098268

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103541 WO2022247964A1 (zh) 2021-05-25 2022-07-04 票据处理方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (2) CN113222724B (zh)
WO (1) WO2022247964A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113222724B (zh) * 2021-05-25 2022-06-21 支付宝(杭州)信息技术有限公司 票据处理方法及装置
CN113850577A (zh) * 2021-09-24 2021-12-28 支付宝(杭州)信息技术有限公司 资源账户处理方法及装置
CN114548963B (zh) * 2022-02-10 2023-01-17 支付宝(杭州)信息技术有限公司 支付交互处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180189870A1 (en) * 2002-05-14 2018-07-05 Early Warning Services, Llc Multi-database system for storing data from multiple data sources
CN111402026A (zh) * 2020-03-25 2020-07-10 支付宝(杭州)信息技术有限公司 业务处理方法及因公报销处理方法
CN111552954A (zh) * 2020-04-27 2020-08-18 中国银行股份有限公司 账户管理方法及装置
CN112132565A (zh) * 2020-11-24 2020-12-25 支付宝(杭州)信息技术有限公司 一种支付方法及装置、电子设备和存储介质
CN113222724A (zh) * 2021-05-25 2021-08-06 支付宝(杭州)信息技术有限公司 票据处理方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100257066A1 (en) * 2009-04-06 2010-10-07 Bank Of America Corporation Electronic receipts collection and management system
CN107590731A (zh) * 2017-08-31 2018-01-16 深圳市联邦重科电子科技有限公司 一种账单费用的记录方法、装置及设备
CN108537538A (zh) * 2018-03-07 2018-09-14 胡金钱 电子发票的开具方法及系统、计算机存储介质
CN108537608A (zh) * 2018-03-07 2018-09-14 胡金钱 电子发票的管理方法及系统、计算机存储介质
CN108846657B (zh) * 2018-05-28 2023-08-08 广州腾讯科技有限公司 一种电子转账的方法以及相关装置
CN109087155A (zh) * 2018-06-19 2018-12-25 优识云创（北京）科技有限公司 一种发票管理的方法和设备
CN110827014A (zh) * 2018-09-28 2020-02-21 武汉小码联城科技有限公司 基于企业账户的乘车支付方法、系统及一种企业端、用户终端
US20200394638A1 (en) * 2019-06-14 2020-12-17 Martin Thomas Mcleod Method of Managing a Personal Payment Platform
CN112734419B (zh) * 2021-01-18 2023-07-04 北京极智数仓科技有限公司 支持个人实时支付的企业电子钱包管理方法、系统及终端
CN112434114B (zh) * 2021-01-26 2021-07-02 腾讯科技（深圳）有限公司 电子票据处理方法、装置、介质及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180189870A1 (en) * 2002-05-14 2018-07-05 Early Warning Services, Llc Multi-database system for storing data from multiple data sources
CN111402026A (zh) * 2020-03-25 2020-07-10 支付宝(杭州)信息技术有限公司 业务处理方法及因公报销处理方法
CN111552954A (zh) * 2020-04-27 2020-08-18 中国银行股份有限公司 账户管理方法及装置
CN112132565A (zh) * 2020-11-24 2020-12-25 支付宝(杭州)信息技术有限公司 一种支付方法及装置、电子设备和存储介质
CN113222724A (zh) * 2021-05-25 2021-08-06 支付宝(杭州)信息技术有限公司 票据处理方法及装置

Also Published As

Publication number Publication date
CN113222724A (zh) 2021-08-06
CN113222724B (zh) 2022-06-21
CN115205006A (zh) 2022-10-18

Similar Documents

Publication Publication Date Title
WO2022247964A1 (zh) 票据处理方法、装置、电子设备及存储介质
US10318955B2 (en) Attribute based card combinations for digital wallets
US10121208B2 (en) Thematic repositories for transaction management
WO2022247968A1 (zh) 数据处理
US8346664B1 (en) Method and system for modifying financial transaction categorization lists based on input from multiple users
US20150019423A1 (en) Transactional reconciliation system and method
JP2005276195A (ja) プロジェクト時間および経費
US10366457B2 (en) Thematic repositories for transaction management
WO2022247966A1 (zh) 票据处理方法、装置、设备和存储介质
US20190073733A1 (en) Allocating and Tracking Resource Distributions in Computer Networks
CN113222726B (zh) 电子凭证的处理方法、装置及设备
US20230252467A1 (en) Predicting and making payments via preferred payment methods
WO2022247965A1 (zh) 账单处理
WO2023151438A1 (zh) 支付交互处理
US20130173472A1 (en) Transaction Management System
US20230306547A1 (en) Digital credential dependency management
US8868488B2 (en) Techniques for integrating structured accounting data with unstructured data
US20170186092A1 (en) System and method for providing offline framework for business support
JP2021064245A (ja) 給与前払いサーバ、給与前払いプログラム、給与前払いシステム、および給与前払い方法
TW201546731A (zh) 用於網路經紀媒合平台之資訊交換系統及其資訊交換方法
EP3583523A1 (en) Thematic repositories for transaction management
US20220398666A1 (en) Distributed ledger-based decentralized autonomous organizations and collaborations
US20180114276A1 (en) Financial organization system
AU2014203478A1 (en) Transactional Reconciliation System and Method
WO2017103841A1 (en) System and method for payer controlled payment processing system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22810687

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18561579

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22810687

Country of ref document: EP

Kind code of ref document: A1