I Method and System for centralised bill management and payment FIELD OF THE INVENTION [0001] The invention relates to a method and a system for direct debit and scheme debit via a third party debit management function that centralises instructions from an array of billers seeking funds from a payer, communicates bill instructions to the payer and enables the payer to manage debit requests. BACKGROUND OF THE INVENTION [0002] Direct debits provide the cheapest form of payments compared to any payment made via a scheme such as debit and credit card payments. As such, billers would prefer individual payers to use direct debit. [0003] Direct debits and scheme debits provide billers with a convenient way to directly charge customers. Sometimes payment occurs on a regular basis and sometimes on an adhoc basis. [0004] In Australia, a de-centralised direct debit and scheme debit system exists that provides a biller with the authority to pull money from an individual payer's account (which may be a bank account or scheme card account). There is no single functionality in this de centralised system, including the payer's bank, which gives a consolidated view of biller identities, amount and timings of bills. [0005] Further there is no link between the biller and the payer's account from where they are pulling money. Direct debits are only visible to the payer after they have occurred. As such, the payer does not have the ability to easily stop a payment before it occurs if they dispute the payment or if they do not have sufficient funds to make the payment. [0006] Further there is possibility that if an individual does not maintain a "buffer" amount in their account and is not aware of the exact date and amount that is being withdrawn, the biller could overdraw their account. In such a scenario the payer's bank may then dishonour the payment and may charge the payer a fee. The biller's bank may also charge the biller a fee too.
[0007] This lack of transparency and control reduces the number of individual payers who are prepared to pay bills and other payments via direct debit. OBJECT OF THE INVENTION [0008] It is an object of the present invention to encourage the use of a direct debit system by both billers and payers. The new system eliminates any uncertainty in a payer's billing schedule, provides the payer with a degree of control over payments and, at the same time, provides the biller with a reliable and secure means to receive payment. SUMMARY OF THE INVENTION [0009] The present invention is a bill management/payment method and system that aggregates payer specific bill information from a plurality of billers with a third party debit management function, the same third party receives a single debit consent form from each user (the payer) that authorises the third party to send payment instructions on behalf of the payer to facilitate payment from the payer's account(s)to the biller, in accordance with the bill information specified by the billers. The method can be implemented via suitable computer network system between the billers and the third party, and the third party and the payer. It is understood that the payer may use an app on a mobile electronic device to communicate with the third party and receive information, communications and messages from the third party via this app. The app also allows the payer to view their debit schedule, for example when the next funds will be pulled from their account. [0010] The system issues a communication from the central module to the payer alerting the payer to impending payment from their account. At this point the system provides the payer with the opportunity to perform an action on the pending payment selected from amending the value, postponing or stopping the payment. If no action is performed by the payer, then the third party will send payment instructions to facilitate payment to be made from the payer's nominated account to the biller. [0011] If the payer decides to amend the value, postpone or stop the payment, then the system communicates this response to the biller and payment is either amended, delayed by a specified period of time or the payment is cancelled. [0012] At any time, the payer may view pending payments and a history of their payments, via an online interface. This may include, but is not limited to: the date that the next payment 2 will be taken; the account; the amount that will be taken; and the account from which the money will be taken. BRIEF DESCRIPTION OF THE DRAWING [0013] FIG. 1 is a representation of a bill management/payment method and system consistent with the present invention. DETAILED DESCRIPTION OF THE INVENTION [0014] In this example the third party that controls the bill management/payment system and possesses authorisation to facilitate direct debit or scheme debits payments from the payer's bank account is named Pay24 for illustrative purposes. [0015] Authority to facilitate direct debit or scheme debit payments from a payer's bank account will sit centrally with Pay24. Pay24 will then use the direct debit system to facilitate payment from the payer's account to the biller. Pay24 will allow complete visibility of the payment to the customer via an online interface. This may include, but is not limited to: the date that the payment will be taken; the account; the amount that will be taken; and the account from which the money will be taken. [0016] This centralised view of direct debits sits outside of an individual's bank account and does not require the individual to log in to their bank account to pause or stop their direct debits. [0017] Pay24 provides the payer with control to pause or stop a direct debit payment before it is made. Pay24 notifies the payer in advance of the payment being taken and will keep them apprised of status (e.g., failure or success of a payment). [0018] If the payer pauses or stops a payment, the payer will be prompted to advise as to why e.g. because they dispute the bill, are no longer a customer, or they propose to pay by alternative payment means. This information is then sent to the biller. [0019] When integrated with other parties, Pay24 can also monitor the payer's bank account balance to offer a level of protection from becoming overdrawn or being left with only a little amount in their account. E.g. If an individual has a bank balance of $200 and a direct debit scheduled imminently for $200 Pay24 can notify the user that they will not be left with any 3 money and recommend they pay via an alternative method or postpone the payment for a period of time. [0020] This method and system provides the payer the following capabilities not seen in prior billing and payment methods and systems: * to see exactly what is coming out of their bank account and when; * to postpone scheduled payment without having to contact the biller; - easily cancel direct debit authorisation without having to contact the biller. DEBIT AUTHORISATION FORM [0021] A key feature of the system is the provision of a single debit authorisation form from the payer to the third party managing the system. This is typically a Direct Debit Request (DDR) form or may be entry of the payer's account details into the system via a web based interface. [0022] There will be some text prior to the DDR explaining to the customer what the next form will be about and what information is required. E.g. "To authorise PowerDebitsTM to pay bills- either on a scheduled or one-off basis, you will need to provide us with your bank account details and personal details" [0023] The payer will be instructed to agree to terms and conditions of the DDR, which includes the following: * Pay24 (the third party in this example managing the system) will never take money from the Payer's account without your express authorisation * Payer has, through a web based interface, provided Pay24 authorisation to facilitate payments directly from the Payer's bank account to billers * Other terms and conditions may be added as determined by the third party, in this case Pay24. THE WEB BASED INTERFACE OF THE SYSTEM [0024] One feature of the interface provides a means for the payer to elect a biller to pay and the payment method. 4 [0025] When adding a biller and selecting a payment method, the payer can select either a credit/debit card or BSB and bank account as their preferred payment account for that biller. The payer can select either manual or auto payment and set other preferences). [0026] The system provides the payer the ability to postpone payment. The web based interface provides automatic response to payers requests to postpone payments, for example: * If the due date is > 5 days away. The web interface provides the payer with the following reply: "No problems. Pay24 can postpone your payment for 24 or 48 hours. Your payment will be processed on <date>". An option will be provided by the interface for the payer to select 24 or 48 hours postponement and to cancel or confirm postponement. Scheduled due date is updated on server and anywhere on client. * If the due date is < 5 days away. The web interface provides the payer with the following reply: "Your payment will be postponed 24 or 48 hours. Payments from bank accounts can take up to 3 days. Pay24 does not take liability for any payments that miss their due dates. Your payment will be processed on <date>." An option will be provided by the interface for the payer to select 24 or 48 hours postponement and to cancel or confirm postponement. Scheduled due date is updated on server and anywhere on client. [0027] The interface will provide the payer the means to stop an auto payment. Selecting this option in the interface will bring up a dialogue: "No problems. Pay24 can stop your auto payment. For our records can you please select the reason. We may share this with your biller". [0028] Suitable reasons may include: * Payer desires to make a one off manual payment * Payer does not believe the bill is correct. The payer is instructed by the interface to contact the biller directly to let them know. Pay24 may also automatically alert the biller via an electronic interface. * Payer states he/she is no longer a customer. The payer is instructed by the interface to contact the biller directly to let them know. Pay24 may also automatically alert the biller via an electronic interface. 5 - Other (if they select this option the payer must type something in) [0029] If the selected due date and time has passed (e.g. 4pm on the due date) and the payer has not performed an action on the bill, then the payment should have "Nothing to Pay" displayed in the interface. If the payment was made via direct bank transfer and not credit card, the words "Payment Pending" are displayed until it is cleared. This must be confirmed with the server. System Server Requirements [0030] The system will store debit authorisation forms and acceptances. It is anticipated that the system server must securely store (and backup) acceptance of these forms for a period of at least 7 years. Web interface functionality for billers [0031] Billers will be able to access a biller portal to see the status of their latest billing and payments sorted by cleared, pending, declined and other categorisations, and also provide details of billing information to the third party controlling the system. [0032] Billing information can be uploaded in a number of formats, for example an excel spreadsheet with a list of all customers for whom they want to set up a scheduled payment. [0033] Billers will be able to remove an existing customer from the billing information. [0034] Billers will have the ability to provide a note when an amendment is made to a bill e.g. a yearly increase. This note will be visible to the payer via the web based interface in the detailed section of their bill for the first bill with that amount only. Running reports by the Third Party [0035] For the third party, in this example Pay24, to effectively control the billing and payment system it is contemplated that a series of reports will be easily available at any time for any period, including: Which customers have which bills and their default payment method (manual or auto). Manual payment option requires a payer to authorise the direct debit payment before it is made; while auto payment notifies the payer of the impending payment, allowing the payer to take action if required (including cancelling or pausing a payment), 6 however if no action is taken the direct debit will proceed. Third party report will advise the biller what the customer's setting for bill payment is set to. [0036] The third party will have the ability to search within the system to show specific customers who have: * specific billers e.g. energy companies * a bill due * a bill overdue and how many days overdue * a payment ageing report - for every bill due, when was it paid compared to it's due date. This can be accessed and filtered by the biller * a customer aging report, for every/any payer when did they pay their bills compared to their due date * for any/every payer show all their bills that have been paid/unpaid * for any given period who has postponed a bill and the current status * for any given period who has stopped an auto payment and the current status * the reason why a bill has been stopped and current status Although the present invention has been described in connection with the preferred form of practicing it and modifications thereto, those of ordinary skill in the art will understand that many other modifications can be made to the present invention within the scope of the claims that follow. Accordingly, it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow. 7