AU2003204059A1 - A payment system - Google Patents

Description

P/00/011 Regulation 3.2

AUSTRALIA

Patents Act 1990 COMPLETE SPECIFICATION STANDARD PATENT

(ORIGINAL)

Name of Applicant: Actual Inventors: Address for Service: Invention Title: MYOB Technology Pty Ltd, ACN 086 760 269, of 4 Solwood Lane, Blackburn, Victoria 3130, Australia Leonid Antanovskii John Trevor Finnin Viktor Vladimirovich Mikho Michael Pardy Andrew Craig Winkler DAVIES COLLISON CAVE, Patent Attorneys, of 1 Little Collins Street, Melbourne, Victoria 3000, Australia A payment system Details of Associated Provisional Application: PS2183/02 The following statement is a full description of this invention, including the best method of performing it known to us:- P:%opd0db.283-02 spe.doc-07/05/03 -1- A PAYMENT SYSTEM The present invention relates to a payment system, and in particular to a system and process for managing payment of an invoice, and an invoice pad for use with the system.

Software packages have been developed for managing the financial affairs of businesses of any size. For small businesses, financial software packages are available for generic personal computer systems, providing financial management systems that allow small businesses to print their own invoices, and to keep track of their customer's payments.

However, these systems are typically feature-laden and quite complex, requiring considerable expertise to configure and use them correctly. In particular, very small businesses comprising few or (as little as one) employees may not have the human or financial resources to use and maintain such systems. It is desired, therefore, to provide a payment process and system that alleviates one or more of the above difficulties, or at least provides a useful alternative.

In accordance with the present invention, there is provided a payment process, including: receiving subscription data including a pad identifier for identifying an invoice pad, and banking data of a user of the pad receiving invoice data submitted by a customer of said user, said invoice data including said pad identifier, an invoice identifier identifying an invoice of said pad, and a payment amount; and notifying said user of a payment of said payment amount against said invoice on the basis of said invoice data.

Advantageously, the process may include receiving said payment amount from said customer, and transferring funds to said user on the basis of said payment amount and said banking data.

P:\oprdbsW2 183-02 sp.d-07/05/03 -2- Advantageously, said notifying may include sending an electronic message for said user, acknowledging receipt of said payment. Preferably, said electronic message includes a short messaging service (SMS) message.

Preferably, said invoice identifier represents an invoice number, and said pad identifier represents a biller code.

Preferably, said subscription data includes a trading name of said user.

Preferably, the pad includes a subscription page for recording said subscription data.

The present invention also provides a payment system for payment of merchant invoices, including: a subscription facility for receiving merchant data, to register a merchant with the system, said merchant data including a pad code unique to an invoice pad and banking details identifying an account of said merchant for receiving payments; and a payment facility for processing payment data submitted by a customer of said user, said payment data including a payment amount, an invoice number of an invoice of said pad and said pad code; wherein said pad code corresponds to a biller code that allows said payment amount to be applied to said account of said merchant.

The present invention also provides an invoice pad for use with a payment system, including a plurality of invoices having a pad identifier that identifies said invoice pad, and invoice identifiers for respectively identifying said invoices, said pad identifier providing a biller code for submitting payments against said invoices using said payment system.

Preferably, the pad includes a subscription page for submitting subscription data including said pad identifier and banking data of a user of the pad. Preferably, said subscription data includes a trading name of said user. Advantageously, said subscription data may include a mobile telephone number of said user.

P:\opadbw\p2183.02 spc.doc-07/05/03 -3- Preferably, said pad includes instructions for sending a facsimile of said subscription page in order to subscribe a user of said pad to a payment system.

Preferably, each invoice includes a barcode for uniquely identifying the invoice.

Preferably, each invoice of said pad includes instructions for paying said invoice.

A preferred embodiment of the present invention is hereinafter described, by way of example only, with reference to the accompanying drawings, wherein: Figure 1 is a schematic diagram of a preferred embodiment of a payment system; Figure 2 is a schematic diagram of a payment process for use with the payment system Figure 3 is a flow diagram of a registration process for use with the payment system Figure 4 is an illustration of a subscription page of an invoice pad used with the payment system; Figure 5 is an illustration of an invoice page of the invoice pad and Figure 6 is a flow diagram of an invoice process for use with the payment system.

A payment system 8, as shown in Figures 1 and 2, includes file transport modules 10, a flat file to XML translator 19, a validation module 21, a database management system (DBMS) 16, a receivables processor 14, a transaction processor 18, a payment advice module 102, a monthly statement module 104, a customer relationship management system (CRM) and administration systems 106. The payment system 8 executes a payment process that receives payment on behalf of a user from a customer of the user. The user may be any goods and/or services supplier, such as a merchant described below. The payment system 8 also includes an interactive voice response (IVR) system 15 that allows users to register and customers to make payments.

The payment system 8 receives payment from a customer of a merchant on the basis of an invoice issued by the merchant to the customer. Before using the payment system 8, the P:Nadbwps2183.02 gp.dc.07/05/03 -4merchant registers with or subscribes to the system 8 using a registration process, as shown in Figure 3. The merchant's invoices are provided as removable pages of a pad of invoices that the merchant purchases from an office supply store or a Post Office, at step 32. The first page of the pad is a subscription page, as shown in Figure 4. The subscription page includes a pad code 48, in this case an 8-digit number that uniquely identifies the merchant's pad. The subscription page also includes blank fields 42 to 46 for entering information used for subscribing the merchant to the payment system 8. For example, the merchant's trading name is written in a trading name field 42, and the merchant's banking details are written in banking details fields 46. The merchant can enter a mobile phone number in a mobile phone number field 44. Following the subscription instructions 49 printed on the subscription page, the merchant enters this information on the subscription page at step 34, tears the page from the pad, and at step 36 faxes it to the number provided.

A facsimile of the subscription page is received by an administrator of the payment system 8, and at step 38 this information is keyed in by the administrator and stored in a customer relationship management (CRM) system 20, as shown in Figure 2. Alternatively, the data 42 to 48 on the subscription page can be submitted using a number of other different processes, such as completing a HTML subscription form submitted to a web server connected to the CRM system 20 or telephoning the payment system 8. The merchant's trading name and banking details are then associated with the pad code 48 of the merchant's pad and stored by the database system 16. At step 39, a subscription is created for the merchant. This includes establishing periodic direct debit details for the merchant, whereby funds are transferred from the merchant's bank account to a bank account of the payment system operator to pay for the merchant's use of the payment system 8.

Alternatively, if the merchant has previously subscribed to the system, then a replacement or additional pad can be registered with the system 8 and associated with the merchant's existing subscription information by calling a toll free telephone number provided by pad registration instructions 45 on the subscription page, and entering the unique pad code 48 for the replacement or additional pad. The steps of registering the new pad code 48 are executed by the CRM 20 of the payment system 8. Table 1 shows a dialog between a P:opdbw.'ps2183.O2 spe.doc.7/O3/O3 merchant and the interactive voice response (IVR) system 15 during the registration of a replacement or additional pad.

Table 1 merchant: Dials 1300 888 3333 IVR: "Welcome to padiWak. Please enter the Pad Code shown on the front of your new pad." merchant: enters pad code from new pad, 73521983 IVR: "Please enter the code on the last pad you had." merchant: enters pad code of most recently registered pad.

IVR: "All payments for your new pad will be credited to the bank account for [Trading Name]. Press 1 is this is correct." merchant: Presses 1 IVR: "Thank-you. Your new pad is now ready to use." After the merchant has subscribed to the payment system 8, the merchant's subscription information is sent from the CRM 20 to the DBMS 16. A pad registered with the system can then be used to issue invoices to the merchant's customers. An invoice page from the invoice pad, as shown in Figure 5, includes an invoice number 52, customer information fields 54, merchant information fields 56, product and/or service fields 58, and payment instructions 59. The invoices of a pad include a payee number 55, which is the number of the pad code 48. Each invoice also includes a barcode 57 that represents both the pad code and the invoice number, uniquely identifying the invoice. The invoices are handled by an invoice process, as shown in Figure 6. The process begins at step 602 when the merchant completes an invoice and presents it to a customer. The customer's information is entered into the customer fields 54, including the customer's name, and business number, if appropriate. The merchant's information, including the merchant's business number, is entered into the merchant information fields 56. The products and/or services provided by the merchant to the customer are entered into the product and service fields 58, including for each item the quantity of items provided, a description, the price per item, and the total cost of the items.

P:'cpqbw p283-02 spe.doc-0705/03 -6- At step 604, the customer pays the invoice using an existing bill payment provider system.

The invoice can be paid in person, or by using a form of electronic funds transfer (EFT).

The latter may include Internet banking or payment by phone, using the interactive voice response (IVR) system 15 and a credit card. The EFT payment systems of a bill provider that can be used include Credit card by Phone, ColesATM, Maxi, the Bpay® system provided by Australian Banks, and POST Bill Pay T M provided by Australia Post. For example, payments in person can be made at any Post Office simply by presenting the invoice together with the appropriate payment. The barcode 57 of the invoice is scanned, providing unique identification of the invoice. The customer can provide payment to the post office in cash, direct debit, or credit. Alternatively, the customer can pay by phone by dialling the telephone number provided on the invoice. The customer is then connected to the IVR 15. A typical dialog between the customer and the IVR 15 is given in Table 2, in which the customer uses the telephone keypad to enter the payee number 55 printed on the invoice, which is identical to the pad code 48 that uniquely identifies the merchant's invoice pad. The customer also provides the invoice number 52, and their credit card details in order to make the payment. The IVR 15 generates XML payment data for inclusion in a daily payment file 17.

Table 2 customer: Dials 1300 111 222 IVR "Welcome to padiWak. Please enter the payee number shown on the invoice you wish to pay." customer: Enters the payee number.

IVR "Please enter the invoice number." customer: Enters invoice number.

IVR "You wish to pay "Joe the Plumber" for invoice 102. Press 1 if this is correct. Press 2 to start again." customer: Presses 1.

IVR "Please enter your credit card number followed by the hash key." customer: Enters credit card number.

IVR "Please enter you expiry date followed by the hash key." customer: Enters expiry date.

P:'op adbwk,2183-02 spdoc-0705103 IVR "Please enter the amount in dollars and cents you wish to pay followed by the hash key." customer: Enters 10840.

IVR "Thank you. You wish to pay 108 dollars and forty cents. If this is correct press 1.

Press 2 if this is incorrect." customer: Presses 1.

IVR "Your payment has been accepted. Thank you. Your receipt number is: N000324.

Press 1 to hear your receipt number again. Press 2 if you wish to pay another invoice. Otherwise hang up. The bill payment provider system uses the pad code, ie the payee number, on the invoice as a biller code identifying the payee. The payee can be either the payment system operator or the merchant. In either case, the bill payment provider system identifies the payee by the biller code at step 606 and transfers funds from the customer's bank account to the payee's bank account at step 608. If the payee is the payment system 8, a range of biller codes is pre-allocated to the payment system 8 by the bill payment provider, and these biller codes are then used as pad numbers applied to invoice pads by or on behalf of the operator of the payment system 8. Each biller code can, if desired, comprise a primary billing code portion identifying the payment system 8 and a sub-billing code portion identifying the merchant.

The association of the sub-billing code portion with the merchant is made by the payment system 8 when the merchant registers a pad, as described above. For payments made direct to merchant accounts, the transaction process 18 communicates with the bill payment provider systems, such as by FTP, to provide necessary merchant account details 46 for association with a biller code, ie registered pad code. Depending on arrangements made with a bill payment system provider, biller codes are either pre-allocated to the payment system, and associated account details adjusted when a pad is registered, or a biller code and account detail record created when a pad is registered.

At the end of each day, each bill payment provider system sends a daily payment file 17 to the payment system 8 at step 610. The daily payment files 17 include payment details for each payment made on that day, including the pad number, invoice number, customer information, and payment amount. The daily payment files 17 are sent using file transport modules 10 that provide a secure communications channel between the bill payment P:'opdbwfs2183-02 spe.doc-07/0103 -8provider and the payment system. The file transport modules 10 are preferably standard computer system modules using encrypted communications based on CONNECT:Direct® middleware, described at http://www.sterlingcommerce.com, but can include any suitable form of secure communications modules. Any daily payment files 17 that are not already in XML format, such as those from Bpay® and POST Bill PayTM systems are translated into XML payment data by a flat file to XML translator 19 at step 612. At step 614, the XML payment data is validated against a set of business rules by a validation module 21.

The rules include validity checks such as ensuring that the pad code numbers correspond to registered pads. At step 64, valid XML payment data is processed by the receivables processor 14 at step 616 to identify the corresponding merchant's trading name and banking details on the basis of the payee number 55 provided by the customer. The payment data is then stored by the receivables database management system (DBMS) 16.

Data stored in the receivables database 16 can be viewed and manipulated by an administrator using administrative computer systems 106.

When payments are credited to the payment system operator as an agent for the merchant, the transaction processor 18 sends, at step 618, payment data to banks 110 using FTP in order to complete the transfer of funds from a clearing account of the payment system operator to the merchant's account. This step is not necessary if the payment made at step 62 was made directly from the customer to the merchant.

The CRM system 20 is updated at step 620 to reflect payment at step 66. If the merchant has provided a mobile telephone number on the subscription page of the pad, then the merchant is notified by mobile phone at step 622 using a short message services (SMS) message 102 generated by the payment advice module 102. At the end of each month, a service fee is debited against the merchant's account for use of the payment system 8 (step 624). A monthly statement 104 is generated by the monthly statement module 104 at step 626 and is sent to the merchant by email or post from the payment system operator, listing customer payments. Customer invoicing data for use of the payment system 8 is also included, and is sent to the CRM 20 via FTP for managing customer accounts. The P:pr'dbwps2183-02 spc.doc-07/05/03 -9merchant's bank statement also independently notifies the merchant of customer payments.

Payments sent to the bank include the invoice number 52 as part of the narrative.

In the described embodiment, the modules of the payment system 8 are implemented as software modules executed by standard computer systems such as Intel®-based personal computer systems running a Windows® operating system. However, it will be apparent to the skilled addressee that at least some processes executed by the modules may be performed by dedicated hardware circuits such as application-specific integrated circuits (ASICs).

Many modifications will be apparent to those skilled in the art without departing from the scope of the present invention as herein described with reference to the accompanying drawings.

The reference to any prior art in this specification is not, and should not be taken as, an acknowledgment or any form of suggestion that that prior art forms part of the common general knowledge in Australia.

Claims (23)

1. A payment process, including: receiving subscription data including a pad identifier for identifying an invoice pad, and banking data of a user of the pad receiving invoice data submitted by a customer of said user, said invoice data including said pad identifier, an invoice identifier identifying an invoice of said pad, and a payment amount and notifying said user of a payment of said payment amount against said invoice on the basis of said invoice data.

2. A payment process as claimed in claim 1, including receiving said payment amount from said customer, and transferring funds to said user on the basis of said payment amount and said banking data.

3. A payment process as claimed in claim 1, wherein said notifying includes sending an electronic message for said user, acknowledging receipt of said payment.

4. A payment process as claimed in claim 3, wherein said subscription data includes a destination address associated with said user for receiving said message. A payment process as claimed in claim 4, wherein said electronic message comprises a short message service (SMS) message and said destination address is a mobile telephone number.

6. A payment process as claimed in any one of the preceding claims, wherein said pad identifier presents a biller code and said invoice identifier represents an invoice number.

7. A payment process as claimed in any one of the preceding claims, wherein said subscription data includes a trading name of said user. P:opcdbWp2183-02 spdoc-07/03/03 -11-

8. A payment process as claimed in any one of the preceding claims, wherein said pad includes a subscription page for recording said subscription data.

9. A payment system for executing a payment process as claimed in any one of the preceding claims. Software for performing the steps of a payment process as claimed in any one of claims 1 to 8.

11. Software as claimed in claim 10, stored on computer readable storage medium of a computer system.

12. A payment system for payment of merchant invoices, including: a subscription facility for receiving merchant data, to register a merchant with the system, said merchant data including a pad code unique to an invoice pad and banking details identifying an account of said merchant for receiving payments; and a payment facility for processing payment data submitted by a customer of said user, said payment data including a payment amount, an invoice number of an invoice of said pad and said pad code; wherein said pad code corresponds to a biller code that allows said payment amount to be applied to said account of said merchant.

13. A payment system as claimed in claim 12, wherein said payment data includes account details for an account of said customer from which said payment amount is obtained.

14. A payment system as claimed in claim 13, including a bill facility for receiving said payment data and transferring said payment amount between the customer account and the account of said merchant and forwarding said payment data to said payment facility. P:'opa'dbwss2I83-0 2 spdoc.07/05/03 12- A payment system as claimed in any one of claims 12 to 14, wherein said payment facility generates and sends a notification for transmission to said merchant advising of payment of said invoice.

16. An invoice pad for use with a payment system, including a plurality of invoices having a pad identifier that identifies said invoice pad, and invoice identifiers for respectively identifying said invoices, said pad identifier providing a biller code for submitting payments against said invoices using said payment system.

17. An invoice pad for use with a payment system as claimed in claim 16, including instructions for subscribing to said payment system by submitting subscription data including said pad identifier and banking data of the user of the pad, said banking data identifying an account for receiving said payments.

18. An invoice pad for use with a payment system as claimed in claim 17, wherein said subscription data includes a destination address associated with said user for receiving an electronic message concerning payment of one of said invoices.

19. An invoice pad for use with a payment system as claimed in claim 18, wherein said electronic message comprises a short message service (SMS) message and said destination address is a mobile telephone number. An invoice pad for use with a payment system as claimed in claim 19, wherein said subscription data includes a trading name of said user.

21. An invoice pad for use with a payment system as claimed in any one of claims 17 to 20, including a subscription page for submitting said subscription data, such that sending said subscription page to said payment system subscribes said user to said system.

22. An invoice pad for use with a payment system as claimed in any one of claims 16 to 21, wherein each invoice includes a barcode for uniquely identifying the invoice. opcr'dbwfs2183-02 spc.doc-07/05/03 13-

23. An invoice pad for use with a payment system as claimed in any one of claims 16 to 22, wherein each invoice of said pad includes instructions for paying said invoice using said payment system.

24. An invoice pad as claimed in any one of claims 16 to 23, wherein said payment system is as claimed in any one of claims 9 and 12 to A payment process substantially as hereinbefore described with reference to the accompanying drawings.

26. A payment system substantially as hereinbefore described with reference to the accompanying drawings.

27. Software substantially as hereinbefore described with reference to the accompanying drawings.

28. An invoice pad for use with a payment system substantially as hereinbefore described with reference to the accompanying drawings. DATED this 7th day of May 2003 MYOB Technology Pty Ltd By its Patent Attorneys DAVIES COLLISON CAVE