WO2022247963A1 - 票据的生成 - Google Patents

票据的生成 Download PDF

Info

Publication number
WO2022247963A1
WO2022247963A1 PCT/CN2022/103367 CN2022103367W WO2022247963A1 WO 2022247963 A1 WO2022247963 A1 WO 2022247963A1 CN 2022103367 W CN2022103367 W CN 2022103367W WO 2022247963 A1 WO2022247963 A1 WO 2022247963A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
bill
user
transportation
application
Prior art date
Application number
PCT/CN2022/103367
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 WO2022247963A1 publication Critical patent/WO2022247963A1/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
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/90335—Query processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/909—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/26—Government or public services

Definitions

  • This document relates to the field of Internet technology, and in particular to a method and device for generating bills.
  • One or more embodiments of this specification provide a method for generating a bill.
  • the method includes: obtaining the bill information and travel record information obtained after paying the user's transportation fee order based on the institutional account; querying the ticket application keyword of the institution to which the user belongs; applying the keyword according to the ticket, the The bill information and the itinerary record information are assembled into bill application information; the bill application information is passed into the bill application interface of the bill processing platform, and the electronic bill returned by the bill application interface is obtained.
  • the device includes: an acquisition module, which acquires the bill information and travel record information obtained after paying the user's transportation fee order based on the institutional account; the query module, which queries the ticket application keywords of the institution to which the user belongs; the assembly module, Assemble ticket application information according to the ticket application keyword, the bill information and the itinerary record information; the transmission module transmits the ticket application information to the ticket application interface of the ticket processing platform, and obtains the ticket application interface response transmitted electronic receipts.
  • One or more embodiments of the present specification also provide a ticket generation device, which includes a processor and a memory arranged to store computer-executable instructions.
  • the processor when the executable instructions are executed, the processor: obtains the bill information and travel record information obtained after paying the user's transportation fee order based on the institution account; inquires the ticket application key of the institution to which the user belongs word; assemble ticket application information according to the ticket application keyword, the bill information and the itinerary record information; pass the ticket application information into the ticket application interface of the ticket processing platform, and obtain the return of the ticket application interface electronic bills.
  • One or more embodiments of the present specification also provide a storage medium for storing computer-executable instructions.
  • the executable instructions When the executable instructions are executed, the following process is implemented: After the user's transportation fee order is paid based on the institution account, the Obtained bill information and itinerary record information; query the ticket application keywords of the institution to which the user belongs; assemble ticket application information according to the ticket application keywords, the bill information and the itinerary record information; apply the ticket application The information is transmitted to the bill application interface of the bill processing platform, and the electronic bill returned by the bill application interface is obtained.
  • Fig. 1 is a schematic flow chart of the first method for generating a bill provided by one or more embodiments of this specification;
  • Fig. 2 is a second schematic flow chart of the bill generation method provided by one or more embodiments of this specification;
  • Fig. 3 is an interactive flow chart of the bill generation method provided by one or more embodiments of this specification.
  • Fig. 4 is a schematic diagram of the module composition of the bill generation device provided by one or more embodiments of this specification;
  • Fig. 5 is a schematic structural diagram of a bill generation device provided by one or more embodiments of this specification.
  • Figure 1 is a schematic flowchart of the first method for generating a ticket provided by one or more embodiments of this specification. As shown in Figure 1, the The method at least includes the following steps.
  • Step 102 acquiring the billing information and travel record information obtained after paying the user's transportation expense order based on the institution account.
  • Step 104 querying the ticket application keywords of the organization to which the user belongs.
  • Step 106 assemble the ticket application information according to the ticket application keywords, bill information and travel record information.
  • Step 108 transfer the bill application information to the bill application interface of the bill processing platform, and obtain the electronic bill returned by the bill application interface.
  • the ticket generation method provided by one or more embodiments of this specification is executed by the ticket preprocessing platform.
  • the institutional account can be the account corresponding to the institution, and the institution can be any one of an enterprise, a public institution, a group organization, etc.; a specific representation form of the above-mentioned electronic bill can be Of course, the electronic invoice can also be other bills, and the embodiment of this specification does not limit the specific form of the above-mentioned electronic bill.
  • the billing information obtained in the above step 102 is the billing information representing information such as the user's payment amount and the paid order
  • the travel record information is the record information representing the user's getting on and off time information and the geographical location information of getting on and off the car.
  • the itinerary record information corresponding to the traffic expense order is also taken into consideration, so that the issued electronic bill carries the user's It is convenient to verify the authenticity of the expenses corresponding to the electronic bills, and avoid the situation where users use false transportation expenses for reimbursement, thereby bringing financial risks to institutions.
  • the bill information and itinerary information corresponding to the transportation fee order are obtained, and the ticket application of the organization to which the user belongs is inquired.
  • the automatic generation of corresponding electronic bills is realized for transportation orders paid using institutional accounts, which avoids users queuing up at the service desk to obtain electronic bills or using special applications
  • the program additionally performs the issuance and withdrawal of electronic bills, which simplifies the process of issuing and withdrawing electronic bills, and the operation is simple and convenient.
  • the transportation expenses mentioned in one or more embodiments of this specification can be the transportation expenses incurred by the user when taking the subway or bus. Of course, they can also be other transportation expenses.
  • the specific form is limited.
  • the payment of the transportation fee order can be paid through the transportation travel platform, of course, it can also be paid through the bill preprocessing platform.
  • One or more embodiments of this specification do not carry out the payment platform for the transportation fee order limited.
  • the transportation platform and bill preprocessing platform mentioned in the embodiment of this specification can be two independent platforms, or can be two different functional modules or systems integrated on the same platform. , or the above-mentioned traffic processing platform and bill pre-processing platform are the same platform that takes into account the above two functions.
  • the billing information and itinerary record information obtained after paying the user's transportation fee order based on the institutional account may specifically include the following process: obtaining the above-mentioned billing information and itinerary record information from the transportation travel platform; wherein, the bill The information and itinerary record information are sent by the transportation travel platform after paying the transportation fee order based on the institutional account it is bound to.
  • the transportation platform is bound to the institutional account.
  • the transportation platform account corresponding to the user is associated with the institutional account, that is, the institutional account is set as the transportation platform corresponding to the user. payment account.
  • the user's transportation travel platform account can be bound to the institutional account of the organization to which the user belongs.
  • the institutional account pays for the user's transportation expenses.
  • the transportation travel platform can be bound to the institutional account through the following steps: receiving the institutional account binding request sent by the user; the binding request carries the transportation travel platform account information corresponding to the user and Institutional account information; send an authorization request to the institutional financial platform to authorize the binding of the transportation and travel platform account information with the institutional account information; after receiving the authorization instruction returned by the institutional financial platform, link the transportation and travel platform account information with the institutional account information bound.
  • the traffic travel platform account information corresponding to the user can actually be understood as the account information registered by the user on the traffic travel platform.
  • Users can add the institutional account of their organization on the account addition interface corresponding to the transportation travel platform, and send a binding request to bind the institutional account to the transportation travel platform.
  • the transportation and travel platform After receiving the binding request sent by the user, the transportation and travel platform will send the financial information to the institution's financial institution based on the institutional account carried in the binding request and the account information registered by the user on the transportation and travel platform (that is, the account information of the transportation and travel platform).
  • the platform sends an authorization request for authorization to bind the account information of the transportation travel platform with the account information of the institution.
  • the authorization request may carry user information (such as user name, certificate number, etc.) in addition to transportation platform account information and institution account information, so that the institution's financial platform can verify the user's identity, thereby facilitating The institution's financial platform authorizes the user to bind the institution's account to use the institution's account to pay for transportation expenses.
  • the transportation travel platform receives the authorization instruction returned by the institution's financial platform, it binds the institution's account with the user, so that the user can use the institution's account to pay for the transportation fee.
  • the above-mentioned binding request also carries binding validity period information to instruct the transportation travel platform to use the institutional account to pay the user's transportation fee order within the binding validity period.
  • binding validity period information includes binding effective date information and binding expiry date information, so that the transportation travel platform will deduct the user's transportation expenses from the institutional account from the binding effective date, and the self-binding will expire. Stop deducting the user's transportation expenses from the institution's account from this date.
  • the transportation expense order can be paid based on the institutional account through the transportation travel platform.
  • the traffic travel platform pays for the traffic fee order through the following steps: receiving the outbound request sent by the user, the outbound request carrying the user's outbound information and the user's identification information; Identification information, determine the user's inbound information, and based on the user's inbound information and outbound information, create a transportation fee order corresponding to the user; based on the above-mentioned institutional account, execute the payment operation for the transportation fee order.
  • the above-mentioned exit request is generated and sent by the gate device by scanning the boarding code displayed by the user when exiting the station.
  • the specific expression form of the above-mentioned boarding code can be a two-dimensional code, a bar code, etc.; its specific form can be set according to actual needs, and the embodiment of this specification does not limit the specific expression form of the above-mentioned boarding code.
  • the identification information of the above-mentioned user may be the account information of the traffic travel platform corresponding to the user, of course, it may also be other information, such as the ID number information of the user, etc., and the embodiment of this specification does not specify the identification information of the above-mentioned user. To limit.
  • the ride code corresponding to the user can be generated through the transportation travel platform, and the ride code can carry the identification information of the user.
  • the user's boarding code can be scanned through the gate equipment installed at the entrance of the station, and the boarding code information and the entering information are sent to the traffic travel platform.
  • the boarding code can be parsed through the traffic travel platform, and the station entry information corresponding to the user's identification information carried in the boarding code can be recorded.
  • the user exits the station the user's boarding code can be scanned through the gate equipment installed at the exit, and the boarding code information and exit information are sent to the traffic travel platform.
  • the boarding code is analyzed through the traffic travel platform, and the outbound information corresponding to the user's identification information carried in the boarding code is recorded, and the inbound information corresponding to the user is searched based on the user's identification information, based on the user's identification information Inbound information and outbound information, according to the pre-set traffic fee determination rules, determine the traffic fee corresponding to the user, and generate the corresponding traffic fee order. If it is determined that the current time is within the validity period corresponding to the institutional account, the transportation fee corresponding to the transportation fee order will be deducted from the bound institutional account.
  • NFC Near Field Communication
  • the transportation travel platform when the transportation travel platform completes the payment of the transportation fee order, it will verify whether the order is paid based on the bound institution, and if so, send the corresponding payment of the transportation fee order to the bill preprocessing platform. bill information and travel record information to trigger the ticket preprocessing platform to execute the electronic ticket issuance operation corresponding to the transportation expense order.
  • the obtained bill application keywords can be the header information of the invoice, such as organization name, tax ID number, etc. .
  • querying the ticket application keywords of the institution to which the user belongs may specifically include the following process: sending a ticket information query request to the fee control platform corresponding to the institution account; wherein, the above ticket information query request carries the user's user name Identification information, so that the fee control platform can query the bill application keywords of the institution to which the user belongs according to the user identification information; obtain the bill application keywords returned by the fee control platform.
  • the information of the sub-organization to which the user belongs directly can be determined as the ticket application keyword of the organization to which the user belongs.
  • the relevant information of sub-organization A (such as the organization name , tax number, etc.) as the keyword of the bill application corresponding to the user; however, in some cases, although a member of an organization belongs to a certain sub-organization (for example, it is recorded as sub-organization A), the project associated with the current business trip It may belong to another sub-institution (for example, sub-institution B). In this case, the ticket application key of the electronic note issued is the relevant information of sub-institution B. Therefore, in this case, it is necessary to obtain Keyword of bill application corresponding to subsidiary institution B.
  • the relevant information of sub-organization A such as the organization name , tax number, etc.
  • the bill application keywords corresponding to the user can be associated on the fee control platform in advance, so that after receiving the bill information query request sent by the bill preprocessing platform, the query request can be based on the bill information
  • the user identification information carried in query the ticket application keywords corresponding to the user.
  • the above step 106 is executed, that is, the ticket application information is assembled according to the ticket application keyword, bill information and travel record information.
  • the ticket application information is assembled according to the ticket application keywords, bill information, and travel record information. Specifically, it can be realized through the following process: determine the payment information corresponding to the transportation fee order based on the above bill information, and, based on the above The itinerary record information determines the location information of getting on and off the bus and the time information of getting on and off the bus corresponding to the transportation fee order; the above-mentioned payment fee information, getting on and off location information, the getting on and off time information and the ticket application keywords are assembled into the ticket application information according to the preset rules.
  • the above-mentioned payment information , location information for getting on and off, time information for getting on and off, and ticket application keywords are assembled according to preset rules, which can actually be understood as associating the contents of each field with its corresponding field.
  • a possible form of the bill application information obtained after the assembly according to the preset rules is as follows:
  • the bill information corresponding to the transportation expense order may contain information such as the identification information of the transportation expense order, payment information, payment time information, payment method, etc. Therefore, it can be extracted from the bill information
  • the payment information corresponding to the transportation fee order similarly, for the travel record information, it can generally include the user’s boarding time information, boarding location information, alighting time information, and alighting location information, etc. Therefore, based on the travel record information, the user's getting on and off location information and time information on getting on and off the car can be determined.
  • the information used when generating an electronic bill, may include other information, such as a contact number, etc., in addition to the information listed above, according to actual needs.
  • the ticket application information corresponding to the transportation expense order is assembled, the ticket application information is transmitted to the ticket processing platform through the ticket application interface of the ticket processing platform.
  • a specific implementation manner in which the bill preprocessing platform transmits the bill application information to the bill application interface of the bill processing platform may be that the bill preprocessing platform sends a billing request to the bill processing platform, that is, The bill preprocessing platform carries the bill application information in the billing request and transmits it to the bill application interface of the bill processing platform. After the bill processing platform obtains the billing request, it generates the corresponding electronic bill based on the bill application information carried in the billing request. And return the generated electronic bill to the bill preprocessing platform through the bill interface;
  • the above bill application information can be typeset according to the preset template, so as to generate the electronic form corresponding to the bill application information. bill.
  • the bill preprocessing platform When the bill preprocessing platform receives the electronic bill sent back by the bill processing platform through the bill application interface, it sends a notification message of successful issuance of the electronic bill to the user.
  • the method provided by the embodiment of this specification further includes the following steps: associating the above-mentioned electronic bill with the traffic expense order .
  • the user can search for the corresponding electronic bill by searching for the traffic expense order, or use the relevant information of the traffic expense order (such as identification information such as the order number) as the query condition to find the corresponding electronic bill; or, the electronic bill
  • the user can view the corresponding electronic receipt by clicking on a transportation expense order in the transportation expense order list.
  • Fig. 2 is a schematic flowchart of the second method for generating a bill provided by the embodiment of this specification. As shown in Fig. 2 , the method specifically includes the following steps.
  • Step 202 receiving the entry request sent by the gate device, and recording the user's identification information and corresponding entry information based on the entry request; wherein, the above entry request carries the entry information and the user's identification information.
  • Step 204 receiving an outbound request sent by the gate device; wherein, the above outbound request carries outbound information and user identification information.
  • Step 206 based on the identification information of the user, look up the inbound information corresponding to the user, and create a transportation fee order corresponding to the user based on the inbound information and outbound information.
  • Step 208 use the institutional account bound by the user to perform the payment operation for the above-mentioned transportation fee order.
  • step 210 the user's billing information and travel record information are obtained, and the ticket application keyword of the organization to which the user belongs is queried.
  • Step 212 determine the payment information corresponding to the transportation fee order based on the above bill information, and determine the getting on and off location information and getting on and off time information corresponding to the transportation fee order based on the travel record information.
  • Step 214 assemble the above-mentioned payment fee information, getting on and off location information, getting on and off time information and ticket application keywords into ticket application information according to the set rules.
  • Step 216 transfer the bill application information to the bill application interface of the bill processing platform, so as to generate corresponding electronic bills through the bill processing platform.
  • Step 218, obtain the electronic note returned by the note application interface.
  • Step 220 sending notification information of successful issuance of the electronic bill to the user.
  • the generation and payment of the transportation fee order is performed by the transportation travel platform, and the process of assembling the ticket application information is performed by the ticket preprocessing platform.
  • the figure 3 shows an interactive flowchart of the bill generation method provided by the embodiment of this specification, wherein the bill generation method includes an account binding stage and a bill issuing stage; it specifically includes the following process.
  • the user sends an institutional account binding request to the transportation travel platform through the terminal device; wherein, the above binding request carries the transportation platform account information and institutional account information corresponding to the user.
  • the traffic travel platform binds the institutional account with the traffic travel platform corresponding to the user, and sets the institutional account with a payment account.
  • the user When entering the station, the user displays the boarding code through the terminal device.
  • the gate device scans the boarding code displayed on the terminal device, and sends an entry request to the traffic travel platform; wherein, the above entry request carries the entry information and the user's identification information.
  • the traffic travel platform records the user's identification information and corresponding inbound information based on the inbound request.
  • the user When leaving the station, the user displays the boarding code through the terminal device.
  • the gate device scans the boarding code displayed on the terminal device, and sends an outbound request to the traffic travel platform; wherein, the above outbound request carries outbound information and user identification information.
  • the traffic travel platform searches for the inbound information corresponding to the user, and creates a transportation fee order corresponding to the user based on the inbound information and outbound information.
  • the transportation travel platform deducts the transportation fee corresponding to the above transportation fee order from the institutional account bound by the user. 10. The transportation travel platform sends the bill information and travel record information corresponding to the above transportation expense order to the ticket preprocessing platform.
  • the bill preprocessing platform queries the bill application keywords of the institution to which the user belongs.
  • the bill preprocessing platform determines the payment fee information corresponding to the transportation fee order based on the above bill information, and determines the getting on and off location information and the getting on and off time information corresponding to the transportation fee order based on the itinerary record information, and combines the above payment fee information, Get on and off position information, get on and off time information and ticket application keywords are assembled into ticket application information according to the set rules.
  • the bill preprocessing platform transmits the bill application information to the bill application interface of the bill processing platform.
  • the bill processing platform generates corresponding electronic bills based on the bill application information.
  • the bill preprocessing platform obtains the electronic bill returned from the bill application interface.
  • the bill preprocessing platform sends the notification information of the successful issuance of the electronic bill to the user through the terminal device.
  • the embodiment of this specification also provides a ticket generation device, which is used to execute the method described in Figures 1 to 3 of this specification.
  • Figure 4 is a schematic diagram of the module composition of the bill generation device provided by the embodiment of this specification.
  • the bill information and travel record information obtained after the fee order is paid; the query module 404 is used to query the bill application keywords of the institution to which the user belongs; the assembly module 406 is used to apply for keywords according to the bill, the bill information and the itinerary record information to assemble ticket application information; the transmission module 408 is used to transmit the ticket application information to the ticket application interface of the ticket processing platform, and obtain the electronic ticket returned by the ticket application interface.
  • the ticket generation device provided by the embodiment of this specification can realize all the content of the method embodiment shown in Figure 1 to Figure 3, therefore, the specific implementation process of the above-mentioned functional modules will not be repeated here, and the specific content can refer to Figure 1 to Figure The embodiment shown in 3 will not be repeated here.
  • the embodiment of this specification also provides a bill generation device, as shown in FIG. 5 .
  • the ticket generation device may have relatively large differences due to different configurations or performances, and may include one or more processors 501 and memory 502, and one or more storage applications or data may be stored in the memory 502.
  • the storage 502 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 502 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instruction information for the ticket generation device.
  • the processor 501 may be configured to communicate with the memory 502, and execute a series of computer-executable instruction information in the memory 502 on the bill generation device.
  • the bill generation device may also include one or more power sources 503, one or more wired or wireless network interfaces 504, one or more input and output interfaces 505, one or more keyboards 506, and the like.
  • the ticket generation device includes a memory, and one or more programs, wherein 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 instruction information in the ticket generation device, and is configured to be executed by one or more processors.
  • the one or more programs include information for performing the following computer-executable instructions: obtaining The billing information and itinerary information obtained after paying the user's transportation fee order based on the institutional account; querying the bill application keyword of the institution to which the user belongs; applying the keyword, the billing information, and the itinerary according to the bill Record information to assemble bill application information; transfer the bill application information to the bill application interface of the bill processing platform, and obtain the electronic bill returned by the bill application interface.
  • the ticket generation device provided by the embodiment of this specification can realize all the method steps of the embodiments shown in FIG. 1 to FIG. 3 , which will not be repeated here.
  • the bill information and itinerary information corresponding to the transportation fee order are obtained, and the ticket application keyword of the organization to which the user belongs is inquired, and the keyword and bill are applied according to the ticket information and itinerary record information to assemble ticket application information, and transfer the assembled ticket application information to the ticket application interface of the ticket processing platform, thereby generating corresponding electronic tickets based on the ticket processing platform; that is, in one or more embodiments of this specification Among them, the automatic generation of corresponding electronic bills is realized for the transportation fee orders paid by institutional accounts, which avoids users queuing up at the service desk to obtain electronic bills or using special applications to additionally issue electronic bills, simplifying Simple and convenient operation;
  • the itinerary record information corresponding to the transportation expense order is also taken into consideration, so that the issued electronic bill carries the user's itinerary-related information, which is convenient for the The authenticity of the expenses corresponding to the electronic bills is verified, which avoids the situation where users use false transportation expenses for reimbursement, thereby bringing financial risks to institutions.
  • the embodiment of this specification also provides a storage medium for storing computer-executable instruction information.
  • the storage medium can be a USB flash drive, a CD, a hard disk, etc.
  • the following process can be realized: Obtain the information obtained after paying the user's transportation fee order based on the institutional account bill information and itinerary record information; query the ticket application keywords of the institution to which the user belongs; assemble the ticket application information according to the ticket application keywords, the bill information and the itinerary record information; send the ticket application information to Enter the bill application interface of the bill processing platform, and obtain the electronic bill returned by the bill application interface.
  • the bill information and itinerary information corresponding to the transportation fee order are obtained, and the ticket application keyword of the organization to which the user belongs is inquired, and the keyword and bill are applied according to the ticket information and itinerary record information to assemble ticket application information, and transfer the assembled ticket application information to the ticket application interface of the ticket processing platform, thereby generating corresponding electronic tickets based on the ticket processing platform; that is, in one or more embodiments of this specification Among them, the automatic generation of corresponding electronic bills is realized for the transportation fee orders paid by institutional accounts, which avoids users queuing up at the service desk to obtain electronic bills or using special applications to additionally issue electronic bills, simplifying The process of issuing and withdrawing electronic bills is simplified, and the operation is simple and convenient.
  • the itinerary record information corresponding to the transportation expense order is also taken into consideration, so that the issued electronic bill carries the user's itinerary-related information, which is convenient for the The authenticity of the expenses corresponding to the electronic bills is verified, which avoids the situation where users use false transportation expenses for reimbursement, thereby bringing financial risks to institutions.
  • 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 Circuit (ASIC), programmable logic controllers, and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory.
  • ASIC Application Specific Integrated Circuit
  • 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, means for realizing various functions may be regarded as a structure within both a software module realizing a method and a hardware component.
  • 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.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application 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 instruction information 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, so that the instruction information stored in the computer readable memory produces an article of manufacture comprising the instruction information means , the instruction information device realizes the functions specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.
  • These computer program instruction information can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are performed on the computer or other programmable equipment to produce computer-implemented processing, thereby executing on the computer or other programmable equipment
  • the instruction information provides steps for realizing the functions 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.
  • the information may be computer readable instruction information, data structures, modules of a program, 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 technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape 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.
  • the embodiments of the present application may be provided as methods, systems or computer program products. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the application 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

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • General Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Library & Information Science (AREA)
  • Educational Administration (AREA)
  • Computational Linguistics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本说明书实施例提供了一种票据的生成方法及装置。该方法包括：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询用户归属的机构的票据申请关键字；根据上述票据申请关键字、账单信息和行程记录信息组装票据申请信息；将票据申请信息传入票据处理平台的票据申请接口，并获取票据申请接口回传的电子票据。

Description

票据的生成 技术领域
本文件涉及互联网技术领域，尤其涉及一种票据的生成方法及装置。
背景技术
用户在出差时，不可避免的需要乘坐一些交通工具，如地铁、公交等，这些因公产生的交通费用可以进行报销；但是目前的一般是用户在乘坐了交通工具后，去相应的服务台或者特定的应用程序开取电子票据，等出差回去之后，再进行报销；但是目前开取电子票据的方式，操作比较复杂。
发明内容
本说明书一个或多个实施例提供了一种票据的生成方法。其中，该方法包括：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询所述用户归属的机构的票据申请关键字；根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
本说明书一个或多个实施例还提供了一种票据的生成装置。其中，该装置包括：获取模块，获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询模块，查询所述用户归属的机构的票据申请关键字；组装模块，根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；传输模块，将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
本说明书一个或多个实施例还提供了一种票据的生成设备，该设备包括处理器以及被安排成存储计算机可执行指令的存储器。其中，所述可执行指令在被执行时使所述处理器：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询所述用户归属的机构的票据申请关键字；根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
本说明书一个或多个实施例还提供了一种存储介质，用于存储计算机可执行指令，所述可执行指令在被执行时实现以下流程：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询所述用户归属的机构的票据申请关键字；根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；将所述票据 申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本文件中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的票据的生成方法的第一种流程示意图；
图2为本说明书一个或多个实施例提供的票据的生成方法的第二种流程示意图；
图3为本说明书一个或多个实施例提供的票据的生成方法的交互流程图；
图4为本说明书一个或多个实施例提供的票据的生成装置的模块组成示意图；
图5为本说明书一个或多个实施例提供的票据的生成设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本文件中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本文件一部分实施例，而不是全部的实施例。基于本说明书中的一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件保护的范围。
首先，本说明书一个或多个实施例提供了一种票据的生成方法，图1为本说明书一个或多个实施例提供的票据的生成方法的第一种流程示意图，如图1所示，该方法至少包括如下步骤。
步骤102，获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息。
步骤104，查询上述用户归属的机构的票据申请关键字。
步骤106，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息。
步骤108，将票据申请信息传入票据处理平台的票据申请接口，并获取票据申请接口回传的电子票据。
本说明书一个或多个实施例所提供的票据的生成方法的执行主体为票据预处理平台。
在本说明书一个或多个实施例中，机构账户可以为机构所对应的账户，该机构可以为企业、事业单位、团体组织等其中的任意一种；上述电子票据的一种具体表征形式可以为电子发票，当然还可以为其他票据，本说明书实施例并不对上述电子票据的具体形式进行 限定。
其中，上述步骤102中所获取到的账单信息为表征用户支付金额以及所支付的订单等信息的账单信息，行程记录信息为表征用户上下车时间信息以及上下车地理位置信息的记录信息。
在本说明书一个或多个实施例中，在生成交通费用订单所对应的电子票据时，将交通费用订单所对应的行程记录信息也考虑在内，这样，使得所开具的电子票据中携带有用户的行程相关信息，便于对该电子票据所对应的费用的真实性进行核实，避免了用户使用虚假交通费用进行报销、从而给机构带来财务风险的情况的发生。
另外，在本说明书一个或多个实施例中，在用户使用机构账户进行交通费用订单的支付后，则获取该交通费用订单所对应的账单信息和行程信息，以及查询用户归属的机构的票据申请关键字，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息，将所组装的票据申请信息传入票据处理平台的票据申请接口，从而基于票据处理平台生成对应的电子票据；也即，在本说明书一个或多个实施例中，针对使用机构账户进行支付的交通费用订单，实现了其所对应电子票据的自动化生成，避免了用户去服务台排队开取电子票据或者使用专门的应用程序额外进行电子票据的开取，简化了电子票据的开取流程，操作简单方便。
具体的，本说明书一个或多个实施例中所提及到的交通费用可以为用户乘坐地铁或者公交所产生的交通费用，当然，也可以为其他交通费用，本说明书实施例并不对上述交通的具体形式进行限定。
在一种具体实施方式中，交通费用订单的支付可以通过交通出行平台进行支付，当然，也可以通过票据预处理平台进行支付，本说明书一个或多个实施例并不对交通费用订单的支付平台进行限定。其中，需要说明的是，本说明书实施例所提及到的交通出行平台和票据预处理平台可以为两个独立的平台，也可以为集成在同一个平台上的两个不同的功能模块或者系统，或者上述交通处理平台和票据预处理平台为兼顾上述两种功能的同一个平台。为便于理解本说明书一个或多个实施例所提供的方案，下述将以通过交通出行平台进行交通费用的支付、以票据预处理平台进行电子票据相关信息的预处理为例，介绍本说明书一个或多个实施例中的交通费用订单的支付过程。
上述步骤102中，获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息，具体可包括如下过程：从交通出行平台获取上述账单信息和行程记录信息；其中，该账单信息和行程记录信息为交通出行平台基于其所绑定的机构账户对交通费用订单进行支付后发送的。
在本说明书实施例中，交通出行平台与机构账户绑定，实际上可以理解为，将用户所对应的交通出行平台账户与机构账户进行关联，也即将该机构账户设置为用户所对应交通出行平台的支付账户。例如，在一种具体应用场景中，当用户出差时，为了避免用户自己垫付交通费用，可以将用户的交通出行平台账户与其所属机构的机构账户进行绑定，这样，可以直接通过其所属机构的机构账户支付用户的交通费用。
为了使得用户在差旅期间，可以顺利的使用机构账户进行交通费用的支付，需要预先将用户所对应的交通出行平台账户与机构账户进行绑定。在本说明书实施例中，具体可以通过如下步骤将交通出行平台与机构账户进行绑定：接收用户发送的机构账户绑定请求；该绑定请求中携带有用户所对应的交通出行平台账户信息和机构账户信息；向机构财务平台发送授权将交通出行平台账户信息与机构账户信息进行绑定的授权请求；在接收到机构财务平台返回的授权指示后，将交通出行平台账户信息与机构账户信息进行绑定。
其中，用户所对应的交通出行平台账户信息实际上可以理解为，用户在交通出行平台进行注册的账户信息。
用户可以在交通出行平台所对应的账户添加界面添加其所属机构的机构账户，并向交通出行平台发送绑定该机构账户的绑定请求。交通出行平台在接收到用户发送的绑定请求后，基于该绑定请求中所携带的机构账户和用户在交通出行平台的所注册的账户信息(也即交通出行平台账户信息)，向机构财务平台发送授权将交通出行平台账户信息与机构账户信息进行绑定的授权请求。其中，该授权请求中除了携带交通出行平台账户信息和机构账户信息之外，还可以携带有用户信息(如用户姓名、证件号码等信息)，以便于机构财务平台对用户身份进行核验，从而便于机构财务平台授权该用户绑定该机构账户，以使用该机构账户进行交通费用的支付。当交通出行平台接收到机构财务平台返回的授权指示后，将该机构账户与用户进行绑定，从而使得用户可以使用该机构账户进行交通费用的支付。
当然，除了用户在交通出行平台所对应的账户添加界面添加机构账户这种情况之外，还可以通过用户所属机构的相关人员(如财务人员)直接将用户的交通出行平台与机构账户进行绑定，从而使得用户可以基于机构账户进行交通费用的支付。
对于用户而言，其一般在特定时间段内或者特定应用场景下才需要使用机构账户进行交通费用的支付，比如，出差期间等等。因此，还可以对上述绑定设置有效期。例如，用户需要在2021年3月15日至2021年3月20日因公出差，在此期间，用户进行交通出行的交通出行费用可以基于其所绑定的机构账户进行支付，因此，可以将机构账户与用户进行绑定的有效期设置为2021年3月15日至2021年3月20日。当然，此处只是示例性说明，并不构成对本说明书实施例的限定。
因此，本说明书实施例所提供的方案在具体实施时，上述绑定请求中还携带有绑定有效期信息，以指示交通出行平台在绑定有效期内使用机构账户支付用户的交通费用订单。
其中，上述绑定有效期信息的一种具体形式包括绑定生效日期信息和绑定失效日期信息，这样，使得交通出行平台自绑定生效日期开始从机构账户扣除用户的交通费用，自绑定失效日期起停止从机构账户扣除用户的交通费用。
在将用户所对应的交通出行平台账户与机构账户进行绑定后，当通过交通出行平台产生了交通费用订单后，可通过交通出行平台基于该机构账户进行交通费用订单的支付。在一种具体实施方式中，交通出行平台通过如下步骤进行交通费用订单的支付：接收用户发送的出站请求，该出站请求中携带有用户的出站信息和用户的标识信息；基于用户的标识信息，确定用户的进站信息，并基于用户的进站信息和出站信息，创建用户所对应的交通费用订单；基于上述机构账户，执行针对该交通费用订单的付款操作。
在一种具体实施方式中，上述出站请求为闸机设备通过扫描用户在出站时所展示的乘车码生成并发送的。
其中，上述乘车码的具体表现形式可以为二维码、条形码等等；其具体形式可以依据实际需求进行设置，本说明书实施例并不对上述乘车码的具体表现形式进行限定。
可选的，上述用户的标识信息可以为用户所对应的交通出行平台的账户信息，当然，还可以为其他，如用户的身份证号码信息等等，本说明书实施例并不对上述用户的标识信息进行限定。
为便于理解上述过程，下述将结合具体实施例对上述过程进行说明。
例如，可以通过交通出行平台生成用户所对应的乘车码，乘车码中可以携带有用户的标识信息。当用户进站时，可以通过设置于进站入口的闸机设备扫描用户的乘车码，并将乘车码信息和进站信息发送给交通出行平台。这样通过交通出行平台可以解析该乘车码，并记录乘车码中所携带的用户的标识信息所对应的进站信息。当用户出站时，可以通过设置于出站口的闸机设备扫描用户的乘车码，并将乘车码信息和出站信息发送给交通出行平台。这样通过交通出行平台解析该乘车码，并记录乘车码中所携带的用户的标识信息所对应的出站信息，并基于用户的标识信息查找该用户所对应的进站信息，基于用户的进站信息和出站信息，按照预先设置的交通费用确定规则，确定用户所对应的交通费用，并生成其所对应的交通费用订单。若确定当前时间为机构账户所对应的有效期内，则从所绑定的机构账户中扣除该交通费用订单所对应的交通费用。
当然，此处只是示例性列举支付交通费用订单的一种具体实现形式，并不构成对本说明书实施例的限定。例如，用户除了扫码进出站之外，还可以通过其他方式进出站，如使 用近距离无线通信技术(Near Field Communication，NFC)与交通费用平台进行通信以实现交通费用的支付，也即在用户的终端设备上设置有NFC模块，通过NFC模块与闸机设备进行通信。
在具体实施时，当交通出行平台在完成交通费用订单的支付后，会校验该订单是否为基于所绑定的机构进行支付的，若是，则向票据预处理平台发送该交通费用订单所对应的账单信息和行程记录信息，以触发票据预处理平台执行该交通费用订单所对应的电子票据的开取操作。
可选的，在一种具体实施方式中，为了实现生成交通费用订单所对应的电子票据，在获取到账单信息和行程记录信息后，还需要获取电子票据的票据申请关键字，当上述电子票据的具体形式不同时，所需要的票据申请关键字的具体字段信息不同；例如，上述电子票据为电子发票时，所获取的票据申请关键字可以为发票抬头信息，如机构名称、税号等信息。
上述步骤104中，查询用户归属的机构的票据申请关键字，具体可以包括如下过程：向机构账户所对应的费控平台发送票据信息查询请求；其中，上述票据信息查询请求中携带有用户的用户标识信息，以使费控平台根据用户标识信息查询用户所属机构的票据申请关键字；获取费控平台返回的票据申请关键字。
一般情况下，对于某个机构而言，其可能存在归属于该机构的一个或者多个子机构，一般的，对于某个机构成员而言，其只能归属一个子机构，在这种情况下，则直接用户所归属的该子机构的信息确定为该用户所归属机构的票据申请关键字即可，例如，若是用户为子机构A的成员，则直接将子机构A的相关信息(如机构名称、税号等)作为用户所对应的票据申请关键字；但是，在某些情况下，虽然某机构成员归属于某个子机构(如记为子机构A)，但是其当前次出差所关联的项目可能归属为另外一个子机构(如记为子机构B)，在这种情况下，所开取电子票据的票据申请关键字则为子机构B的相关信息,因此，在这种情况下需要获取子机构B所对应的票据申请关键字。
因此，在一种具体实施方式中，可以预先在费控平台关联用户所对应的票据申请关键字，这样，当接收到票据预处理平台发送的票据信息查询请求后，可以基于该票据信息查询请求中所携带的用户标识信息，查询该用户所对应的票据申请关键字。
当接收到费控平台返回的票据申请关键字后，则执行上述步骤106，也即，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息。在本说明书实施例中，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息，具体可以通过如下过程实现：基于上述账单信息确定交通费用订单所对应的支付费用信息，以及，基于上述行程记录信 息确定交通费用订单所对应的上下车位置信息和上下车时间信息；将上述支付费用信息、上下车位置信息、上下车时间信息和票据申请关键字按照预设规则组装成票据申请信息。
一般的，对于各个类型的电子票据而言，其存在自身所对应的固有格式，例如，其需要包含的字段及其对应的字段内容；因此，在一种具体实施方式中，上述将支付费用信息、上下车位置信息、上下车时间信息和票据申请关键字按照预设规则组装实际上可以理解为将各个字段内容与其对应的字段进行关联。
例如，在一种具体实施方式中，假设上述票据申请关键字包括机构名称和机构税号，则上述按照预设规则进行组装后得到的票据申请信息的一种可能形式如下所示：
机构名称：XX公司；
机构税号：XXXXX；
支付费用：X元；
上车地理位置：A站；
上车时间：2021年3月12日15时03分；
下车地理位置：B站；
下车时间：2021年3月12日16时06分。
当然，上述只是示例性列举所得到的票据申请信息的一种可能的具体形式，并不构成对票据申请信息的具体内容以及格式的限定。
一般情况下，对于交通费用订单所对应的账单信息而言，其可以包含有交通费用订单的标识信息、支付费用信息、支付时间信息、支付方式等信息，因此，可以从该账单信息中提取出该交通费用订单所对应的支付费用信息；同样的，对于行程记录信息而言，其一般情况下可以包括用户上车时间信息、上车地理位置信息、下车时间信息以及下车地理位置信息等内容，因此，基于该行程记录信息，可以确定出用户的上下车位置信息和上下车时间信息。
其中，在本说明书一个或多个实施例中，在生成电子票据时，所使用的信息除了上述所列举的信息外，还可以根据实际需求包含其他信息，如联系电话等等。
在本说明书一个或多个实施例中，当组装得到交通费用订单所对应的票据申请信息后，则将该票据申请信息通过票据处理平台的票据申请接口传输至票据处理平台。
其中，在一种具体实施方式中，票据预处理平台将票据申请信息传入票据处理平台的票据申请接口的一种具体实现方式可以是，票据预处理平台向票据处理平台发送开票请求，也即票据预处理平台将票据申请信息携带在开票请求中传入票据处理平台的票据申请接口，当票据处理平台获取到开票请求后，基于该开票请求中所携带的票据申请信息生成对 应的电子票据，并将所生成的电子票据通过票据接口返回给票据预处理平台；
对于票据处理平台而言，当其接收到票据预处理平台通过票据申请接口传入的票据申请信息之后，可将上述票据申请信息按照预设模板进行排版，从而生成该票据申请信息所对应的电子票据。
当票据预处理平台接收到票据处理平台通过票据申请接口回传的电子票据之后，则向用户发送电子票据开具成功的通知信息。
另外，当用户需要使用电子票据时，可以直接从票据预处理平台查找或者下载其所需要的单子票据。因此，为了便于用户查找交通费用订单所对应的电子票据，在获取待票据申请接口回传的电子票据后，本说明书实施例提供的方法还包括如下步骤：将上述电子票据与交通费用订单进行关联。
这样，用户可以通过查找交通费用订单的方式查找到对应的电子票据，或者，以交通费用订单的相关信息(如订单编号等标识信息)作为查询条件查找对应的电子票据；还或者，将电子票据与交通费用订单进行关联后，用户在交通费用订单列表中点击某个交通费用订单即可查看对应的电子票据。
为便于理解本说明书实施例提供的方法，下述将以用户为企业员工、乘坐地铁为例介绍本说明书实施例提供的方法。图2为本说明书实施例提供的票据的生成方法的第二种流程示意图，如图2所示，该方法具体包括如下步骤。
步骤202，接收闸机设备发送的进站请求，并基于该进站请求记录用户的标识信息和对应的进站信息；其中，上述进站请求中携带有进站信息和用户的标识信息。
步骤204，接收闸机设备发送的出站请求；其中，上述出站请求中携带有出站信息和用户的标识信息。
步骤206，基于用户的标识信息，查找用户所对应的进站信息，并基于进站信息和出站信息，创建用户所对应的交通费用订单。
步骤208，使用用户所绑定的机构账户，进行上述交通费用订单的支付操作。
步骤210，获取用户的账单信息和行程记录信息，以及，查询用户归属的机构的票据申请关键字。
步骤212，基于上述账单信息确定交通费用订单所对应的支付费用信息，以及，基于行程记录信息确定交通费用订单所对应的上下车位置信息和上下车时间信息。
步骤214，将上述支付费用信息、上下车位置信息、上下车时间信息和票据申请关键字按照设定规则组装成票据申请信息。
步骤216，将票据申请信息传入票据处理平台的票据申请接口，以通过票据处理平台生 成对应的电子票据。
步骤218，获取票据申请接口回传的电子票据。
步骤220，向用户发送电子票据开具成功的通知信息。
可选的，在一种具体实施方式中，交通费用订单的生成以及支付则是由交通出行平台执行的，组装票据申请信息的过程则是由票据预处理平台执行的，针对该种场景，图3示出了本说明书实施例提供的票据的生成方法的交互流程图，其中，该票据的生成方法包括账户绑定阶段和票据开取阶段；其具体包括如下流程。
账户绑定阶段。
1、用户通过终端设备向交通出行平台发送机构账户绑定请求；其中，上述绑定请求中携带有用户所对应的交通出行平台账户信息和机构账户信息。
2、交通出行平台将机构账户与用户所对应的交通出行平台进行绑定，并将该机构账户设置有支付账户。
票据开取阶段。
3、进站时，用户通过终端设备展示乘车码。
4、闸机设备扫描终端设备展示的乘车码，向交通出行平台发送进站请求；其中，上述进站请求中携带有进站信息和用户的标识信息。
5、交通出行平台基于该进站请求记录用户的标识信息和对应的进站信息。
6、出站时，用户通过终端设备展示乘车码。
7、闸机设备扫描终端设备展示的乘车码，向交通出行平台发送出站请求；其中，上述出站请求中携带有出站信息和用户的标识信息。
8、交通出行平台基于用户的标识信息，查找用户所对应的进站信息，并基于进站信息和出站信息，创建用户所对应的交通费用订单。
9、交通出行平台从用户所绑定的机构账户扣除上述交通费用订单所对应的交通费用。10、交通出行平台将上述交通费用订单所对应的账单信息和行程记录信息发送给票据预处理平台。
11、票据预处理平台查询用户归属的机构的票据申请关键字。
12、票据预处理平台基于上述账单信息确定交通费用订单所对应的支付费用信息，以及，基于行程记录信息确定交通费用订单所对应的上下车位置信息和上下车时间信息，将上述支付费用信息、上下车位置信息、上下车时间信息和票据申请关键字按照设定规则组装成票据申请信息。
13、票据预处理平台将票据申请信息传入票据处理平台的票据申请接口。
14、票据处理平台基于票据申请信息生成对应的电子票据。
15、票据预处理平台获取票据申请接口回传的电子票据。
16、票据预处理平台通过终端设备向用户发送电子票据开具成功的通知信息。
对应于本说明书图1至图3所示实施例提供的票据的生成方法，基于相同的思路，本说明书实施例还提供了一种票据的生成装置，用于执行本说明书图1至图3所示实施例提供的方法，图4为本说明书实施例提供的票据的生成装置的模块组成示意图，如图4所示，该装置具体包括：获取模块402，用于获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询模块404，用于查询所述用户归属的机构的票据申请关键字；组装模块406，用于根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；传输模块408，用于将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
本说明书实施例提供的票据的生成装置可实现图1至图3所示方法实施例的全部内容，因此，此处不再赘述上述各个功能模块的具体实现过程，具体内容可参考图1至图3所示实施例，此处不再赘述。
进一步地，基于上述图1至图3所示的方法，本说明书实施例还提供了一种票据的生成设备，如图5所示。
票据的生成设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器501和存储器502，存储器502中可以存储有一个或一个以上存储应用程序或数据。其中，存储器502可以是短暂存储或持久存储。存储在存储器502的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括对票据的生成设备中的一系列计算机可执行指令信息。更进一步地，处理器501可以设置为与存储器502通信，在票据的生成设备上执行存储器502中的一系列计算机可执行指令信息。票据的生成设备还可以包括一个或一个以上电源503，一个或一个以上有线或无线网络接口504，一个或一个以上输入输出接口505，一个或一个以上键盘506等。
在一个具体的实施例中，票据的生成设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对票据的生成设备中的一系列计算机可执行指令信息，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令信息：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询所述用户归属的机构的票据申请关键字；根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；将所述票据申请信息传入票 据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
其中，本说明书实施例所提供的票据的生成设备可实现图1至图3所示实施例的全部方法步骤，此处不再赘述。
本说明书实施例提供的票据的生成设备，至少具有如下有益效果：
1)、在用户使用机构账户进行交通费用订单的支付后，则获取该交通费用订单所对应的账单信息和行程信息，以及查询用户归属的机构的票据申请关键字，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息，将所组装的票据申请信息传入票据处理平台的票据申请接口，从而基于票据处理平台生成对应的电子票据；也即，在本说明书一个或多个实施例中，针对使用机构账户进行支付的交通费用订单，实现了其所对应电子票据的自动化生成，避免了用户去服务台排队开取电子票据或者使用专门的应用程序额外进行电子票据的开取，简化了电子票据的开取流程，操作简单方便；
2)、在生成交通费用订单所对应的电子票据时，将交通费用订单所对应的行程记录信息也考虑在内，这样，使得所开具的电子票据中携带有用户的行程相关信息，便于对该电子票据所对应的费用的真实性进行核实，避免了用户使用虚假交通费用进行报销、从而给机构带来财务风险的情况的发生。
进一步地，基于上述图1至图3所示的方法，本说明书实施例还提供了一种存储介质，用于存储计算机可执行指令信息。该存储介质可以为U盘、光盘、硬盘等，该存储介质存储的计算机可执行指令信息在被处理器执行时，能实现以下流程：获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；查询所述用户归属的机构的票据申请关键字；根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
其中，本说明书实施例提供的存储介质存储的计算机可执行指令信息在被处理器执行时，可实现图1至图3所示实施例的全部方法步骤，此处不再赘述。
本说明书实施例提供的票据的处理方法、票据的处理设备和相应的存储介质，至少具有如下有益效果：
1)、在用户使用机构账户进行交通费用订单的支付后，则获取该交通费用订单所对应的账单信息和行程信息，以及查询用户归属的机构的票据申请关键字，根据票据申请关键字、账单信息和行程记录信息组装票据申请信息，将所组装的票据申请信息传入票据处理平台的票据申请接口，从而基于票据处理平台生成对应的电子票据；也即，在本说明书一个或多个实施例中，针对使用机构账户进行支付的交通费用订单，实现了其所对应电子 票据的自动化生成，避免了用户去服务台排队开取电子票据或者使用专门的应用程序额外进行电子票据的开取，简化了电子票据的开取流程，操作简单方便。
2)、在生成交通费用订单所对应的电子票据时，将交通费用订单所对应的行程记录信息也考虑在内，这样，使得所开具的电子票据中携带有用户的行程相关信息，便于对该电子票据所对应的费用的真实性进行核实，避免了用户使用虚假交通费用进行报销、从而给机构带来财务风险的情况的发生。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(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)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC625D、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)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请可以在由计算机执行的计算机可执行指令信息的一般上下文中描述，例如程序 模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (13)

  1. 一种票据的生成方法，包括：
    获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；
    查询所述用户归属的机构的票据申请关键字；
    根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；
    将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
  2. 如权利要求1所述的方法，所述获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息，包括：
    从交通出行平台获取所述账单信息和所述行程记录信息；其中，所述账单信息和所述行程记录信息为所述交通出行平台基于其所绑定的所述机构账户对所述交通费用订单进行支付后发送的。
  3. 如权利要求2所述的方法，通过如下步骤将交通出行平台与所述机构账户进行绑定：
    接收所述用户发送的机构账户绑定请求；所述绑定请求中携带有所述用户所对应的交通出行平台账户信息和机构账户信息；
    向机构财务平台发送授权将所述交通出行平台账户信息与所述机构账户信息进行绑定的授权请求；
    在接收到所述机构财务平台返回的授权指示后，将所述交通出行平台账户信息与所述机构账户信息进行绑定。
  4. 如权利要求3所述的方法，所述绑定请求中还携带有绑定有效期信息，以指示所述交通出行平台在所述绑定有效期内使用所述机构账户支付所述用户的交通费用订单。
  5. 如权利要求1所述的方法，所述交通费用订单为通过交通出行平台基于所述机构账户进行支付的；其中，所述交通出行平台通过如下步骤进行所述交通费用订单的支付：
    接收所述用户发送的出站请求，所述出站请求中携带有所述用户的出站信息和所述用户的标识信息；
    基于所述用户的标识信息，确定所述用户的进站信息，并基于所述用户的进站信息和出站信息，创建所述用户所对应的交通费用订单；
    基于所述机构账户，执行针对所述交通费用订单的付款操作。
  6. 如权利要求5所述的方法，所述出站请求为闸机设备通过扫描所述用户在出站时 所展示的乘车码生成并发送的。
  7. 如权利要求1所述的方法，所述查询所述用户归属的机构的票据申请关键字，包括：
    向所述机构账户所对应的费控平台发送票据信息查询请求；其中，所述票据信息查询请求中携带有所述用户的用户标识信息，以使所述费控平台根据所述用户标识信息查询所述用户所属机构的票据申请关键字；
    获取所述费控平台返回的所述票据申请关键字。
  8. 如权利要求1所述的方法，所述根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息，包括：
    基于所述账单信息确定所述交通费用订单所对应的支付费用信息，以及，基于所述行程记录信息确定所述交通费用订单所对应的上下车位置信息和上下车时间信息；
    将所述支付费用信息、所述上下车位置信息、所述上下车时间信息和所述票据申请关键字按照预设规则组装成所述票据申请信息。
  9. 如权利要求1所述的方法，所述获取所述票据申请接口回传的电子票据，包括：
    将所述电子票据与所述交通费用订单进行关联。
  10. 如权利要求1所述的方法，所述获取所述票据申请接口回传的电子票据之后，所述方法还包括：
    向所述用户发送所述电子票据开具成功的通知信息。
  11. 一种票据的生成装置，包括：
    获取模块，获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；
    查询模块，查询所述用户归属的机构的票据申请关键字；
    组装模块，根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；
    传输模块，将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
  12. 一种票据的生成设备，包括：
    处理器；以及
    被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器：
    获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；
    查询所述用户归属的机构的票据申请关键字；
    根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；
    将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
  13. 一种存储介质，用于存储计算机可执行指令，所述可执行指令在被执行时实现以下流程：
    获取基于机构账户对用户的交通费用订单进行支付后获得的账单信息和行程记录信息；
    查询所述用户归属的机构的票据申请关键字；
    根据所述票据申请关键字、所述账单信息和所述行程记录信息组装票据申请信息；
    将所述票据申请信息传入票据处理平台的票据申请接口，并获取所述票据申请接口回传的电子票据。
PCT/CN2022/103367 2021-05-26 2022-07-01 票据的生成 WO2022247963A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110577140.5 2021-05-26
CN202110577140.5A CN113222679A (zh) 2021-05-26 2021-05-26 一种票据的生成方法及装置

Publications (1)

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

Family

ID=77099464

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103367 WO2022247963A1 (zh) 2021-05-26 2022-07-01 票据的生成

Country Status (2)

Country Link
CN (1) CN113222679A (zh)
WO (1) WO2022247963A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113222679A (zh) * 2021-05-26 2021-08-06 支付宝(杭州)信息技术有限公司 一种票据的生成方法及装置
CN113837749A (zh) * 2021-09-16 2021-12-24 武汉虹信技术服务有限责任公司 一种基于nfc的乘车报销方法
CN115392889A (zh) * 2022-09-02 2022-11-25 支付宝(杭州)信息技术有限公司 服务处理方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140337188A1 (en) * 2013-05-09 2014-11-13 Invoice Cloud Incorporated Electronic invoicing and payment
CN108182037A (zh) * 2017-12-04 2018-06-19 西安艾润物联网技术服务有限责任公司 出租车发票获取方法、系统及计算机可读存储介质
CN108230053A (zh) * 2017-12-19 2018-06-29 广州地铁设计研究院有限公司 一种城市轨道交通电子发票的开票系统及方法
CN110874770A (zh) * 2018-09-03 2020-03-10 阿里巴巴集团控股有限公司 发票处理、业务处理方法、装置、服务器及电子设备
CN112288502A (zh) * 2020-11-02 2021-01-29 支付宝(杭州)信息技术有限公司 电子乘车发票处理方法及装置
CN113222679A (zh) * 2021-05-26 2021-08-06 支付宝(杭州)信息技术有限公司 一种票据的生成方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109034922A (zh) * 2018-07-18 2018-12-18 西安艾润物联网技术服务有限责任公司 车辆费用电子发票管理方法、系统及计算机可读存储介质
CN110827014A (zh) * 2018-09-28 2020-02-21 武汉小码联城科技有限公司 基于企业账户的乘车支付方法、系统及一种企业端、用户终端

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140337188A1 (en) * 2013-05-09 2014-11-13 Invoice Cloud Incorporated Electronic invoicing and payment
CN108182037A (zh) * 2017-12-04 2018-06-19 西安艾润物联网技术服务有限责任公司 出租车发票获取方法、系统及计算机可读存储介质
CN108230053A (zh) * 2017-12-19 2018-06-29 广州地铁设计研究院有限公司 一种城市轨道交通电子发票的开票系统及方法
CN110874770A (zh) * 2018-09-03 2020-03-10 阿里巴巴集团控股有限公司 发票处理、业务处理方法、装置、服务器及电子设备
CN112288502A (zh) * 2020-11-02 2021-01-29 支付宝(杭州)信息技术有限公司 电子乘车发票处理方法及装置
CN113222679A (zh) * 2021-05-26 2021-08-06 支付宝(杭州)信息技术有限公司 一种票据的生成方法及装置

Also Published As

Publication number Publication date
CN113222679A (zh) 2021-08-06

Similar Documents

Publication Publication Date Title
WO2022247963A1 (zh) 票据的生成
WO2022222808A1 (zh) 基于报销码的数据处理的方法及装置
US20130268839A1 (en) Method and Apparatus for Inbound Message Summarization
WO2022247966A1 (zh) 票据处理方法、装置、设备和存储介质
WO2022247968A1 (zh) 数据处理
KR20160067975A (ko) 메시지에 기초한 클라이언트 애플리케이션 런칭
CN107563881A (zh) 记账方法和装置、服务器
WO2022247961A1 (zh) 基于报销码的代扣处理
AU2021341692A1 (en) Application integration for contactless payments
US20230074653A1 (en) Federated identifiers for cross-platform interoperability
WO2022247962A1 (zh) 基于区块链的数据处理
CN109800063A (zh) 业务并行处理方法、装置、服务器、存储介质
CN113222726A (zh) 电子凭证的处理方法、装置及设备
TW202001708A (zh) 一種信用退稅方法、裝置、系統及電子設備
WO2024152846A1 (zh) 支付处理方法及装置
US20220005074A1 (en) Information processing device, information processing program, and information processing system
WO2023151438A1 (zh) 支付交互处理
CN113419794B (zh) 支付处理方法及装置
CN115330366A (zh) 交易账单的票据处理方法及装置
CN111985919B (zh) 支付数据处理方法、装置及电子设备
CN112200576B (zh) 一种基于区块链的电子凭证处理方法及装置
CN113835860A (zh) 多程序协同服务方法、装置、电子设备和存储介质
CN113674038A (zh) 凭证权限处理方法及装置
CN109559212B (zh) 一种退税处理方法、装置、设备及系统
CN113159747B (zh) 一种针对电子交通账户的管理方法、装置及设备

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: 22810686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22810686

Country of ref document: EP

Kind code of ref document: A1