US20120317005A1 - System and Method for Prepay Account Management System - Google Patents
System and Method for Prepay Account Management System Download PDFInfo
- Publication number
- US20120317005A1 US20120317005A1 US13/315,085 US201113315085A US2012317005A1 US 20120317005 A1 US20120317005 A1 US 20120317005A1 US 201113315085 A US201113315085 A US 201113315085A US 2012317005 A1 US2012317005 A1 US 2012317005A1
- Authority
- US
- United States
- Prior art keywords
- prepay
- customer
- account
- prepay customer
- balance
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/06—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity with means for prepaying basic charges, e.g. rent for meters
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/28—Pre-payment schemes, e.g. "pay before"
-
- 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—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/06—Electricity, gas or water supply
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/001—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for gas
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/003—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/10—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity with alarm or warning devices, e.g. indicating the interrupting of the supply
Definitions
- FIG. 1 is a simplified block diagram of an embodiment of a system and method of prepay account management system
- FIG. 2 is a flowchart of an embodiment of a method of new customer sign-up for prepay utility service
- FIG. 3 is a flowchart of an embodiment of a method of creating a new prepay customer account
- FIG. 4 is a flowchart of an embodiment of a method of receiving a payment
- FIG. 5 is a flowchart of an embodiment of a method account activation
- FIG. 6 is a flowchart of an embodiment of a method of updating customer usage
- FIG. 7 is a flowchart of an embodiment of a method of providing customer notification
- FIG. 8 is a flowchart of an embodiment of a method of reconciling a customer's account with a legacy billing system
- FIG. 9 is a flowchart of an embodiment of a method for nightly processing
- FIG. 10 is a flowchart of an embodiment of a method for prepaid card management.
- FIG. 11 is a flowchart of an embodiment of a method for prepaid card validation.
- FIG. 1 is a simplified block diagram of an embodiment of a prepay account management system 10 .
- System 10 may be integrated and operate in cooperation with a legacy hardware and/or software utility subsystem 12 that manages existing utility customer accounts.
- System 10 comprises a hardware and/or software subsystem 14 that is operable to manage prepay utility customer accounts and a customer interface subsystem 15 that is operable to provide a multi-media interface with prepay account customers.
- Subsystems 12 , 14 and 15 may be co-located or located remotely from one another.
- Subsystem 12 includes a legacy billing system 18 that includes or has access to customer billing data and a usage database 28 that is operable to store customers' utility usage data.
- a customer or potential customer 17 may call a designated telephone number to speak to a customer service representative, who may use a client portal 16 to access and enter information about the customers.
- the customer service representative can provide information about the prepay service and sign-up the caller as a new prepay account customer.
- the customer service representative can set-up a new prepay account for the new customer and enter all relevant customer data. A new prepay account is thus created in legacy billing system 18 .
- a web-based customer service system 19 may be used.
- a prospective customer that has already established an account in the legacy billing system may obtain information about the prepay utility service and sign-up online.
- the customer service system then passes the new customer account information to prepay server 20 , in which a new prepay account is created.
- Customer interface subsystem 15 may also include an interactive voice response (IVR) system 21 that is operable to provide general information and basic account information to prepay utility customers. When necessary, a customer may ask to be routed to a customer service representative via IVR system 21 .
- IVR interactive voice response
- the utility company using system 10 is a utility cooperative having a plurality of existing members.
- the prepay service may be an additional program offered to the cooperative members.
- the prepay service may be advantageously used by the members as a budgeting device that enables a higher priority be placed on uninterrupted utility service.
- the pay-as-you-go model of the prepay service is easy to comprehend and follow for members living a certain lifestyle.
- the members are also able to monitor their daily utility usage at any time.
- Legacy billing system 18 is operable to relay the new customer account and associated data to a prepay server 20 via a secure communication link 22 .
- Secure communication link 22 provides secure data transfer between two secure communication servers 24 and 25 .
- Secure communication link 22 may span a variety of computer networks such as local area network (LAN), wide area network (WAN), virtual private network (VPN), the Internet, etc. and employ security features now known, such as encryption, or later developed to safeguard the content of the data transmissions.
- the customer account data may be stored in a database 26 .
- Usage system 28 is operable to receive daily utility usage data from an automatic meter reading (AMR) database 30 .
- An automatic meter reading device typically includes a meter that determines the amount of usage, and a meter interface unit (MIU) that is operable to relay the usage data to a remote database via a communications network.
- the utility usage data are collected by the meter and sent to the meter interface unit (not shown), which delivers the data to a database accessed by usage system 28 .
- the daily usage data that are associated with a prepay customer are then transmitted, via secure communication servers 24 and 25 , to prepay server 20 .
- Prepay server 20 is then operable to process the daily usage data and update the prepay customer account balance.
- the prepay customers' utility usage may be monitored in real-time, and usage system 28 is operable to receive the customers' real-time utility usage data from real-time AMR devices. Operating in this manner, system 10 may process the real-time usage data and provide more current prepay customer account balance and even more timely notification than the daily usage processing as described above.
- usage system 28 may accumulate daily usage data and transmit the data to prepay server 20 at an interval other than daily.
- prepay server 20 may receive and process weekly usage data.
- system 10 may require a higher low balance threshold in each prepay account.
- Some automatic meter reading devices are operable to collect and accumulate usage data for transmission on an interval other than daily.
- Subsystem 14 further includes a notification system 32 .
- Notification system 32 is operable to notify prepay customers about certain pre-designated events related to the prepay accounts. For example, a prepay customer may be notified when his/her account balance drops below a certain level. Another prepay customer may desire a daily notification of the account balance.
- Notification system 32 may use a number of notification methods pre-selected by the customer. Notification system 32 is preferably coupled to a number of communication pathways such as an IVR system 34 , the public switched telephone network, the Internet, etc. to enable a variety of notification delivery methods. For example, the customer may select email or instant messaging for low account balance notifications, and interactive voice response (IVR) messaging for daily usage notifications.
- IVR interactive voice response
- Notification system 32 may further specify or permit the customer to specify the timing for delivering the notification to ensure optimal reception of the messages.
- Notification system 32 is operable to access database 26 for information associated with a prepay customer or his/her account, such as account balance, daily usage amounts, notification preferences, etc.
- a subsystem 38 provides support for prepaid card management.
- Prepaid cards 39 are provided to agents and/or retail locations 36 for sale to prepay account customers. Recorded on each prepaid card 39 is a unique serial number, personal identification number (PIN), and a predetermined denomination.
- PIN personal identification number
- Prepay account customers may activate the cards via telephone or the Internet. Upon activation, a credit is posted to the customer's account in prepay server 20 and the card management system 38 is updated to reflect that the card has been used. Agents 36 are invoiced by the card management subsystem based on card usage.
- each system and server described above may be implemented in hardware, software and/or a combination thereof.
- each system, server or node in system 10 may be implemented by a plurality of computers (personal computers, workstations, servers, etc.) or by a single computer.
- the functionalities of subsystems 12 and/or 14 may also be performed by a plurality of computers or a single computer.
- the entities identified in FIG. 1 may be logical functional blocks in system 10 providing specific functionality therefore such as billing, daily usage monitoring, notification, secure communication, etc.
- FIG. 2 is a flowchart of an embodiment of a method 40 of new customer sign-up for prepay utility services.
- a customer service representative receives a telephone call from a prospective customer in step 42 .
- the customer service representative provides information about the prepay utility service and answers any questions the prospective customer may have about the services in step 44 .
- the customer service representative receives instructions from the customer to sign-up for the prepay services.
- the customer service representative determines if the customer is a new or existing customer in step 48 . If the customer is a new account, the customer service representative establishes a new account by entering information related to the new customer in legacy billing system 18 and create a new customer account therein in step 50 .
- the customer information may include the customer name, customer address, telephone number, and email address. Alternatively, if the customer has an existing account in the legacy billing system, no other action is required.
- the process ends in step 52 .
- FIG. 3 is a flowchart of an embodiment of a method 60 of creating a new prepay customer account.
- the utility account number is entered by the customer service representative and is used to retrieve account information from the billing server 18 . This information may include customer name, customer address, customer telephone number(s), email addresses, meter and billing information, and other data.
- secure communication server 24 transmits or otherwise provides the new account information to prepay server 20 in step 66 .
- the customer service representative then manually enters the required information in step 65 .
- a new prepay account is then created in prepay server 20 in step 67 . Notification preferences are set up in steps 68 through 72 .
- one or more types and methods of notification is selected.
- the customer may indicate that email is preferred for notifying him/her that the account requires a recharge payment to avoid disconnection, and a usage message delivered to his/her mobile telephone number is the preferred method.
- the account setup may also include a customer-selected frequency of notification.
- the customer may indicate that he/she prefers a daily usage notification. Another customer may prefer a bi-monthly usage notification.
- the new prepay account setup may also enable the customer to indicate the preferred time of notification.
- the customer may also indicate at which account balance amount he/she is to be notified. For example, the customer may want to be notified when his account balance drops below $10.
- Prepay server 20 may maintain certain minimum thresholds for low balance notifications to ensure that the customer will always receive timely notification. If the customer has an existing account as determined in step 74 , unbilled usage is calculated in step 76 . In step 77 , it is determined whether the customer's previously paid deposit should be applied to the minimum account balance. If the deposit is not to be applied, then the account status is set to “pending payment” in step 75 . If the deposit is to be applied to the minimum account balance, then the account status is set to “paid” in step 78 . The process ends in step 79 . As a result, a customer's account notification preferences may be summarized as in Table A:
- FIG. 4 is a flowchart of an embodiment of a method 80 of receiving payment.
- Payments may be received at the time of account set-up as well as at any time the customer desires to replenish his/her prepay account balance.
- the customer may make payments in a variety of ways. For example, the customer may use established money transfer or bill payment services (such as WESTERN UNION, MONEYGRAM, and ACE CASH EXPRESS), use a credit card or debit card online or over the telephone with the customer service representative, use automated clearing house (ACH) fund transfer networks, or use authorized agents.
- ACH automated clearing house
- an electronic notification that a payment has been made on a prepay account is received.
- the notification may include the customer prepay account number, customer name, and the payment amount.
- the prepay account balance is then updated to reflect the addition of the payment amount in step 84 .
- a check is then made in step 86 to determine if the current account status is Pending, Active, or Suspended. If the account status is Pending, the current balance is compared to the minimum amount due in step 88 . The Minimum amount due may include installation/setup charges, unbilled usage that has accumulated since the last billing cycle, and any past due balance. If the balance is greater than or equal to the minimum amount due, the charges are applied to the account in step 89 and an activation order is generated in step 90 . If the account status is Active in step 86 , then a check is made to determine whether there is a pending service suspend order in step 92 .
- step 92 If there is a pending suspend service order, and if the current balance is also greater than the suspend threshold as determined in step 91 , then the suspend service order is cancelled in step 93 . If the current account status is determined to be Suspended in step 86 , then a check is made to determine if the current balance is greater than the suspend threshold as determined in step 94 . If so, a reconnect order is generated in step 95 . A recharge notification is then created in step 96 so that the customer receives confirmation of his/her payment. The process ends in step 98 .
- FIG. 5 is a flowchart of an embodiment of a method 100 of an account activation process.
- specific meter information such as the meter number, beginning meter reading, meter install date and last meter read date are stored in the system. This meter information is checked and verified in step 102 . If the meter information is not available at the time the account is created, it is entered in step 104 . Once the required information is entered, the activation order status is set to “pending usage” in step 106 upon installation confirmation. An account cannot be activated until the first daily usage data is posted in step 108 . The activation order status is set to “completed” and the order is logged in step 110 . This causes the meter status to be set to “active” in step 112 and the account status is also set to “active” in step 114 . The process ends in step 116 .
- FIG. 6 is a flowchart of an embodiment of a method 120 of updating customer usage.
- the daily usage data is collected from the remote automated meter reading devices. This collected data is then transmitted to prepay server 20 in subsystem 14 in step 124 .
- the usage cost for that day is then calculated in step 126 .
- the daily usage charge is computed based on the number of kilowatts used, a base rate, estimated or actual Power Charge Adjustment (PCA) (also called Power Cost Recovery Factor or PCRF), local sales taxes, option usage, etc.
- PCA Power Charge Adjustment
- the customer's account balance is then updated by subtracting the daily usage charge from the current account balance in step 128 .
- a daily usage notification order is then generated so that the customer will be notified of the usage charge for that day as well as the remaining account balance in step 130 . If the balance is now less than or equal to zero, as determined in step 132 , then a service suspend order is created in step 134 and a suspend notification order is created in step 136 . Unless the customer makes a payment prior to the suspend order being processed, the utility service will be suspended. If the account balance is greater than zero but less than or equal to a grace amount, as determined in step 138 , then a service suspend notification order is created in step 136 . The user will be notified that suspension of services is imminent if payment is not made.
- step 140 If the account balance is not less than or equal to the suspend threshold but is less than or equal to a low balance threshold amount, as determined in step 140 , then a low balance notification order is created in step 142 . The user will be notified that the account balance has reached a certain low threshold amount and that payment should be made in a timely manner. The process ends in step 144 .
- FIG. 7 is a flowchart of an embodiment of a method 150 of providing customer notification in response to specific triggers associated with the prepay customer accounts.
- a notification order is received by notification system 32 .
- the notification order may include the customer account number, customer name, and the type of notification (e.g. daily usage, recharge, low balance, suspend).
- Notification system 32 is operable to access database 26 to obtain additional data such as current account balance and notification preferences, if necessary.
- Notification system 32 then schedules the notification according to the customer preferences in terms of the notification method and preferred time in step 154 . If the preferred method selected by the customer is interactive voice response, as determined in step 156 , then an interactive voice response message is delivered to the customer-specified telephone number at the scheduled time in steps 158 and 160 .
- notification delivery method is email
- an appropriate email message is transmitted to the customer's email address at the scheduled time in step 162 .
- notification charges are applied to the account in step 170 and all subsequent notifications of the same type are cancelled in step 172 .
- the process ends in step 174 .
- system 10 may use other notification methods such as text messaging, pager, and customer service representative call, etc.
- FIG. 8 is a flowchart of an embodiment of a method 180 of reconciling the prepay account with the legacy billing system account.
- This process provides a true-up of the prepay balance based on estimated charges applied daily throughout the billing cycle with actual charges applied in the same billing cycle.
- the process begins with step 182 by collecting, from a service representative or a billing personnel, certain data which includes the base rate, desired cycle date and the actual power charge adjustment to be used. Accounts to be reconciled are selected based on the billing cycle date entered by the user.
- billing information for each account to be reconciled is extracted from the legacy billing system 18 .
- the data elements include: total kilowatt hours used, beginning meter reading, ending meter reading, additional charges, taxes, and the number of days in the billing cycle.
- the data is sent to the prepay server 20 via the secure communication servers 24 and 25 .
- the PCA adjustment is calculated in step 188 by subtracting the estimated PCA charge in the prepay database from the actual PCA charge from the legacy billing system.
- the customer's balance is then updated to include the PCA adjustment in step 190 . All debits and credits are pulled from the prepay system for the same date range for the accounts being reconciled in step 192 .
- step 194 a comparison is made between the data received from the legacy billing system and the data from the prepay system pulled in step 192 .
- the results are then reported to the user for acceptance and verification. Adjustments are calculated and applied to the accounts in step 196 and the balance is update in step 198 .
- Step 199 is the end of the process.
- FIG. 9 is a flowchart of an embodiment of a method 200 of nightly processing prepay accounts.
- Processes included in the nightly process are those which may require unrestricted access to the database or require the existence of external data which can only be obtained once per day.
- Extracting the previous day's meter readings from the AMR database is accomplished by the prepay system initiating a request via the secure communication server 24 in step 202 .
- the request contains a list of the meter numbers that are prepay accounts.
- the extracted data is transmitted to the prepay system in step 204 .
- All orders that have been previously been completed are processed in step 206 and include: suspend, recharge, reconnect and change orders.
- Account cycle dates are advanced for all accounts whose cycle date is less than or equal to the current date in step 208 .
- step 212 In conjunction with advancing the cycle date, all transactions (debits, credits and payments) are logged which is necessary for account reconciliation. Daily option charges are calculated and applied to the account in step 212 . Accounts with a balance less than the suspend threshold are then updated to Past Due in step 214 . This is a prerequisite to step 216 in which suspend orders are generated. Notification orders are also created in this step based on the specific criteria. Applicable taxes are calculated in step 218 for all transactions that are considered taxable. Charges that are generated by the prepay system that would not normally be included in the legacy billing system are identified and exported in step 220 . The process ends in step 222 .
- FIG. 10 is a flowchart of an embodiment of a method 230 of a prepaid card management subsystem.
- the capability to use a prepaid card to pay for electric service is supported in the prepaid account management system.
- Prepaid cards are required to contain a unique serial number and PIN as well as a predetermined denomination. These are generated and stored in step 232 .
- the cards are printed in step 234 and upon receipt, they are added to the inventory in step 236 . Cards are packaged into batches and sent to agents or retail locations in step 240 . Upon confirmation of receipt by the agent, the cards activated in step 240 . Once the cards are activated, they are sold to the customer who in turn calls an automated voice response system or the utility company to process the card in step 242 .
- the card Before a payment can be posted to the customer's account, the card must be validated in step 244 (see FIG. 11 for details). If the card is determined to be valid, a payment is posted to the customer's account and the card is marked as used within the system in step 246 . If the card is invalid, no further action is required. Agents are invoiced for all processed cards on a weekly or monthly basis as determined by the utility in step 248 . The process ends in step 250 .
- FIG. 11 is a flowchart of an embodiment of a method 260 of the prepaid card validation process.
- step 262 the serial number is checked to ensure it is valid by performing a look up in the inventory. If the serial number is valid, the card is then checked to ensure that it has been activated by the agent in step 264 . If the card is determined to be active, the PIN number is verified in step 266 . The last check is to ensure that the card has not been used in step 268 . If it has not, the validation is passed and the payment may be posted in step 270 . If any of the validation steps fail, the card is rejected and no payment is processed in step 272 . The process ends in step 274
- the prepay service may be advantageously used by the customers as a budgeting device that enables a higher priority be placed on uninterrupted utility service.
- the pay-as-you-go model of the prepay service is easy to comprehend and follow for some segments of the society living a certain lifestyle.
- the customers are also able to monitor their daily utility usage or at any time and to specify the notification methods that best suit their lifestyle.
- the customer may make payments at any time and for any amount using a number of methods and outlets.
- System 10 as described herein may be easily integrated with existing systems of a utility company.
- a secure communication server 24 may be provided onsite at a utility company to transmit prepay account and usage information to subsystem 14 to process and administer the prepay accounts.
- existing accounts receivable amounts are significantly reduced and the number of delinquent accounts is also minimized or eliminated.
- the utility company is able to keep the prepay customer apprised of his/her account balance and provide advanced warning of depleting funds in the prepay account by interactive voice response, email and other electronic means. The utility company no longer needs to attend to the burdensome and costly task of generating and sending monthly billing statements and collections on late payments.
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 11/387,611 filed on Mar. 23, 2006, the disclosure of which is incorporated herein by reference in its entirety.
- Utility companies today face the challenges of providing services to low income customers or customers who may have questionable or no credit history. These companies often have to manage customer accounts that are behind on payments for electricity, gas, water and other utilities. The utility companies have the option of discontinuing future delivery of utilities to those customers but are often left with the difficult task of collecting payment for utilities that have already been consumed. In most instances, these debts are not collectible.
- Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with the standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.
-
FIG. 1 is a simplified block diagram of an embodiment of a system and method of prepay account management system; -
FIG. 2 is a flowchart of an embodiment of a method of new customer sign-up for prepay utility service; -
FIG. 3 is a flowchart of an embodiment of a method of creating a new prepay customer account; -
FIG. 4 is a flowchart of an embodiment of a method of receiving a payment; -
FIG. 5 is a flowchart of an embodiment of a method account activation; -
FIG. 6 is a flowchart of an embodiment of a method of updating customer usage; -
FIG. 7 is a flowchart of an embodiment of a method of providing customer notification; -
FIG. 8 is a flowchart of an embodiment of a method of reconciling a customer's account with a legacy billing system; -
FIG. 9 is a flowchart of an embodiment of a method for nightly processing; -
FIG. 10 is a flowchart of an embodiment of a method for prepaid card management; and -
FIG. 11 is a flowchart of an embodiment of a method for prepaid card validation. -
FIG. 1 is a simplified block diagram of an embodiment of a prepayaccount management system 10.System 10 may be integrated and operate in cooperation with a legacy hardware and/orsoftware utility subsystem 12 that manages existing utility customer accounts.System 10 comprises a hardware and/orsoftware subsystem 14 that is operable to manage prepay utility customer accounts and acustomer interface subsystem 15 that is operable to provide a multi-media interface with prepay account customers.Subsystems Subsystem 12 includes alegacy billing system 18 that includes or has access to customer billing data and ausage database 28 that is operable to store customers' utility usage data. - Typically, a customer or
potential customer 17 may call a designated telephone number to speak to a customer service representative, who may use aclient portal 16 to access and enter information about the customers. The customer service representative can provide information about the prepay service and sign-up the caller as a new prepay account customer. The customer service representative can set-up a new prepay account for the new customer and enter all relevant customer data. A new prepay account is thus created inlegacy billing system 18. - As an alternative to using a customer service representative, a web-based
customer service system 19 may be used. A prospective customer that has already established an account in the legacy billing system may obtain information about the prepay utility service and sign-up online. The customer service system then passes the new customer account information to prepayserver 20, in which a new prepay account is created. -
Customer interface subsystem 15 may also include an interactive voice response (IVR)system 21 that is operable to provide general information and basic account information to prepay utility customers. When necessary, a customer may ask to be routed to a customer service representative viaIVR system 21. - In one scenario, the utility
company using system 10 is a utility cooperative having a plurality of existing members. The prepay service may be an additional program offered to the cooperative members. By taking advantage of the prepay utility service, the members do not have to provide a deposit for the utility service. The prepay service may be advantageously used by the members as a budgeting device that enables a higher priority be placed on uninterrupted utility service. The pay-as-you-go model of the prepay service is easy to comprehend and follow for members living a certain lifestyle. The members are also able to monitor their daily utility usage at any time. -
Legacy billing system 18 is operable to relay the new customer account and associated data to aprepay server 20 via a secure communication link 22. Secure communication link 22 provides secure data transfer between twosecure communication servers database 26. -
Usage system 28 is operable to receive daily utility usage data from an automatic meter reading (AMR)database 30. An automatic meter reading device typically includes a meter that determines the amount of usage, and a meter interface unit (MIU) that is operable to relay the usage data to a remote database via a communications network. The utility usage data are collected by the meter and sent to the meter interface unit (not shown), which delivers the data to a database accessed byusage system 28. The daily usage data that are associated with a prepay customer are then transmitted, viasecure communication servers server 20.Prepay server 20 is then operable to process the daily usage data and update the prepay customer account balance. - Alternatively, the prepay customers' utility usage may be monitored in real-time, and
usage system 28 is operable to receive the customers' real-time utility usage data from real-time AMR devices. Operating in this manner,system 10 may process the real-time usage data and provide more current prepay customer account balance and even more timely notification than the daily usage processing as described above. - As an alternative,
usage system 28 may accumulate daily usage data and transmit the data to prepayserver 20 at an interval other than daily. For example,prepay server 20 may receive and process weekly usage data. In order to compensate for more infrequent account balance updates,system 10 may require a higher low balance threshold in each prepay account. Some automatic meter reading devices are operable to collect and accumulate usage data for transmission on an interval other than daily. -
Subsystem 14 further includes anotification system 32.Notification system 32 is operable to notify prepay customers about certain pre-designated events related to the prepay accounts. For example, a prepay customer may be notified when his/her account balance drops below a certain level. Another prepay customer may desire a daily notification of the account balance.Notification system 32 may use a number of notification methods pre-selected by the customer.Notification system 32 is preferably coupled to a number of communication pathways such as anIVR system 34, the public switched telephone network, the Internet, etc. to enable a variety of notification delivery methods. For example, the customer may select email or instant messaging for low account balance notifications, and interactive voice response (IVR) messaging for daily usage notifications.Notification system 32 may further specify or permit the customer to specify the timing for delivering the notification to ensure optimal reception of the messages.Notification system 32 is operable to accessdatabase 26 for information associated with a prepay customer or his/her account, such as account balance, daily usage amounts, notification preferences, etc. - A
subsystem 38 provides support for prepaid card management.Prepaid cards 39 are provided to agents and/orretail locations 36 for sale to prepay account customers. Recorded on eachprepaid card 39 is a unique serial number, personal identification number (PIN), and a predetermined denomination. Prepay account customers may activate the cards via telephone or the Internet. Upon activation, a credit is posted to the customer's account inprepay server 20 and thecard management system 38 is updated to reflect that the card has been used.Agents 36 are invoiced by the card management subsystem based on card usage. - It should be noted that each system and server described above may be implemented in hardware, software and/or a combination thereof. Further, each system, server or node in
system 10 may be implemented by a plurality of computers (personal computers, workstations, servers, etc.) or by a single computer. The functionalities ofsubsystems 12 and/or 14 may also be performed by a plurality of computers or a single computer. The entities identified inFIG. 1 may be logical functional blocks insystem 10 providing specific functionality therefore such as billing, daily usage monitoring, notification, secure communication, etc. -
FIG. 2 is a flowchart of an embodiment of amethod 40 of new customer sign-up for prepay utility services. A customer service representative receives a telephone call from a prospective customer instep 42. The customer service representative provides information about the prepay utility service and answers any questions the prospective customer may have about the services instep 44. Instep 46, the customer service representative receives instructions from the customer to sign-up for the prepay services. The customer service representative determines if the customer is a new or existing customer instep 48. If the customer is a new account, the customer service representative establishes a new account by entering information related to the new customer inlegacy billing system 18 and create a new customer account therein instep 50. The customer information may include the customer name, customer address, telephone number, and email address. Alternatively, if the customer has an existing account in the legacy billing system, no other action is required. The process ends instep 52. -
FIG. 3 is a flowchart of an embodiment of amethod 60 of creating a new prepay customer account. Instep 62, the utility account number is entered by the customer service representative and is used to retrieve account information from thebilling server 18. This information may include customer name, customer address, customer telephone number(s), email addresses, meter and billing information, and other data. If the lookup is successful,secure communication server 24 transmits or otherwise provides the new account information to prepayserver 20 instep 66. If the account number lookup fails to return the requested data, the customer service representative then manually enters the required information instep 65. A new prepay account is then created inprepay server 20 instep 67. Notification preferences are set up insteps 68 through 72. - In
steps step 72, the account setup may also include a customer-selected frequency of notification. For example, the customer may indicate that he/she prefers a daily usage notification. Another customer may prefer a bi-monthly usage notification. Instep 72, the new prepay account setup may also enable the customer to indicate the preferred time of notification. The customer may also indicate at which account balance amount he/she is to be notified. For example, the customer may want to be notified when his account balance drops below $10. Prepayserver 20 may maintain certain minimum thresholds for low balance notifications to ensure that the customer will always receive timely notification. If the customer has an existing account as determined instep 74, unbilled usage is calculated instep 76. Instep 77, it is determined whether the customer's previously paid deposit should be applied to the minimum account balance. If the deposit is not to be applied, then the account status is set to “pending payment” instep 75. If the deposit is to be applied to the minimum account balance, then the account status is set to “paid” instep 78. The process ends instep 79. As a result, a customer's account notification preferences may be summarized as in Table A: -
FIG. 4 is a flowchart of an embodiment of amethod 80 of receiving payment. Payments may be received at the time of account set-up as well as at any time the customer desires to replenish his/her prepay account balance. The customer may make payments in a variety of ways. For example, the customer may use established money transfer or bill payment services (such as WESTERN UNION, MONEYGRAM, and ACE CASH EXPRESS), use a credit card or debit card online or over the telephone with the customer service representative, use automated clearing house (ACH) fund transfer networks, or use authorized agents. Instep 82, an electronic notification that a payment has been made on a prepay account is received. The notification may include the customer prepay account number, customer name, and the payment amount. The prepay account balance is then updated to reflect the addition of the payment amount instep 84. A check is then made instep 86 to determine if the current account status is Pending, Active, or Suspended. If the account status is Pending, the current balance is compared to the minimum amount due instep 88. The Minimum amount due may include installation/setup charges, unbilled usage that has accumulated since the last billing cycle, and any past due balance. If the balance is greater than or equal to the minimum amount due, the charges are applied to the account instep 89 and an activation order is generated instep 90. If the account status is Active instep 86, then a check is made to determine whether there is a pending service suspend order instep 92. If there is a pending suspend service order, and if the current balance is also greater than the suspend threshold as determined instep 91, then the suspend service order is cancelled instep 93. If the current account status is determined to be Suspended instep 86, then a check is made to determine if the current balance is greater than the suspend threshold as determined instep 94. If so, a reconnect order is generated instep 95. A recharge notification is then created instep 96 so that the customer receives confirmation of his/her payment. The process ends instep 98. -
FIG. 5 is a flowchart of an embodiment of amethod 100 of an account activation process. Prior to activating a prepay account, specific meter information such as the meter number, beginning meter reading, meter install date and last meter read date are stored in the system. This meter information is checked and verified instep 102. If the meter information is not available at the time the account is created, it is entered instep 104. Once the required information is entered, the activation order status is set to “pending usage” instep 106 upon installation confirmation. An account cannot be activated until the first daily usage data is posted instep 108. The activation order status is set to “completed” and the order is logged instep 110. This causes the meter status to be set to “active” instep 112 and the account status is also set to “active” instep 114. The process ends instep 116. -
FIG. 6 is a flowchart of an embodiment of amethod 120 of updating customer usage. Instep 122, the daily usage data is collected from the remote automated meter reading devices. This collected data is then transmitted to prepayserver 20 insubsystem 14 instep 124. The usage cost for that day is then calculated instep 126. The daily usage charge is computed based on the number of kilowatts used, a base rate, estimated or actual Power Charge Adjustment (PCA) (also called Power Cost Recovery Factor or PCRF), local sales taxes, option usage, etc. The customer's account balance is then updated by subtracting the daily usage charge from the current account balance instep 128. A daily usage notification order is then generated so that the customer will be notified of the usage charge for that day as well as the remaining account balance instep 130. If the balance is now less than or equal to zero, as determined instep 132, then a service suspend order is created instep 134 and a suspend notification order is created instep 136. Unless the customer makes a payment prior to the suspend order being processed, the utility service will be suspended. If the account balance is greater than zero but less than or equal to a grace amount, as determined instep 138, then a service suspend notification order is created instep 136. The user will be notified that suspension of services is imminent if payment is not made. If the account balance is not less than or equal to the suspend threshold but is less than or equal to a low balance threshold amount, as determined instep 140, then a low balance notification order is created instep 142. The user will be notified that the account balance has reached a certain low threshold amount and that payment should be made in a timely manner. The process ends instep 144. -
FIG. 7 is a flowchart of an embodiment of amethod 150 of providing customer notification in response to specific triggers associated with the prepay customer accounts. Instep 152, a notification order is received bynotification system 32. The notification order may include the customer account number, customer name, and the type of notification (e.g. daily usage, recharge, low balance, suspend).Notification system 32 is operable to accessdatabase 26 to obtain additional data such as current account balance and notification preferences, if necessary.Notification system 32 then schedules the notification according to the customer preferences in terms of the notification method and preferred time instep 154. If the preferred method selected by the customer is interactive voice response, as determined instep 156, then an interactive voice response message is delivered to the customer-specified telephone number at the scheduled time insteps step 162. Upon successful completion, notification charges are applied to the account instep 170 and all subsequent notifications of the same type are cancelled instep 172. The process ends instep 174. Although not specifically shown,system 10 may use other notification methods such as text messaging, pager, and customer service representative call, etc. -
FIG. 8 is a flowchart of an embodiment of amethod 180 of reconciling the prepay account with the legacy billing system account. This process provides a true-up of the prepay balance based on estimated charges applied daily throughout the billing cycle with actual charges applied in the same billing cycle. The process begins withstep 182 by collecting, from a service representative or a billing personnel, certain data which includes the base rate, desired cycle date and the actual power charge adjustment to be used. Accounts to be reconciled are selected based on the billing cycle date entered by the user. Instep 184, billing information for each account to be reconciled is extracted from thelegacy billing system 18. The data elements include: total kilowatt hours used, beginning meter reading, ending meter reading, additional charges, taxes, and the number of days in the billing cycle. Instep 184 the data is sent to the prepayserver 20 via thesecure communication servers step 188 by subtracting the estimated PCA charge in the prepay database from the actual PCA charge from the legacy billing system. The customer's balance is then updated to include the PCA adjustment instep 190. All debits and credits are pulled from the prepay system for the same date range for the accounts being reconciled instep 192. Instep 194, a comparison is made between the data received from the legacy billing system and the data from the prepay system pulled instep 192. The results are then reported to the user for acceptance and verification. Adjustments are calculated and applied to the accounts instep 196 and the balance is update instep 198. Step 199 is the end of the process. -
FIG. 9 is a flowchart of an embodiment of amethod 200 of nightly processing prepay accounts. Processes included in the nightly process are those which may require unrestricted access to the database or require the existence of external data which can only be obtained once per day. Extracting the previous day's meter readings from the AMR database is accomplished by the prepay system initiating a request via thesecure communication server 24 instep 202. The request contains a list of the meter numbers that are prepay accounts. The extracted data is transmitted to the prepay system instep 204. All orders that have been previously been completed are processed instep 206 and include: suspend, recharge, reconnect and change orders. Account cycle dates are advanced for all accounts whose cycle date is less than or equal to the current date instep 208. In conjunction with advancing the cycle date, all transactions (debits, credits and payments) are logged which is necessary for account reconciliation. Daily option charges are calculated and applied to the account instep 212. Accounts with a balance less than the suspend threshold are then updated to Past Due instep 214. This is a prerequisite to step 216 in which suspend orders are generated. Notification orders are also created in this step based on the specific criteria. Applicable taxes are calculated instep 218 for all transactions that are considered taxable. Charges that are generated by the prepay system that would not normally be included in the legacy billing system are identified and exported instep 220. The process ends instep 222. -
FIG. 10 is a flowchart of an embodiment of amethod 230 of a prepaid card management subsystem. The capability to use a prepaid card to pay for electric service is supported in the prepaid account management system. Prepaid cards are required to contain a unique serial number and PIN as well as a predetermined denomination. These are generated and stored instep 232. The cards are printed instep 234 and upon receipt, they are added to the inventory instep 236. Cards are packaged into batches and sent to agents or retail locations instep 240. Upon confirmation of receipt by the agent, the cards activated instep 240. Once the cards are activated, they are sold to the customer who in turn calls an automated voice response system or the utility company to process the card instep 242. Before a payment can be posted to the customer's account, the card must be validated in step 244 (seeFIG. 11 for details). If the card is determined to be valid, a payment is posted to the customer's account and the card is marked as used within the system instep 246. If the card is invalid, no further action is required. Agents are invoiced for all processed cards on a weekly or monthly basis as determined by the utility instep 248. The process ends instep 250. -
FIG. 11 is a flowchart of an embodiment of amethod 260 of the prepaid card validation process. Before a prepaid card payment can be posted, there are several validation points that must be passed. Instep 262 the serial number is checked to ensure it is valid by performing a look up in the inventory. If the serial number is valid, the card is then checked to ensure that it has been activated by the agent instep 264. If the card is determined to be active, the PIN number is verified instep 266. The last check is to ensure that the card has not been used instep 268. If it has not, the validation is passed and the payment may be posted instep 270. If any of the validation steps fail, the card is rejected and no payment is processed instep 272. The process ends instep 274 - By taking advantage of the prepay utility service, the customers do not have to pay a deposit or go through a credit check to get utility service. Instead, the customer pays a small installation fee and an initial amount determined by the utility company. The prepay service may be advantageously used by the customers as a budgeting device that enables a higher priority be placed on uninterrupted utility service. The pay-as-you-go model of the prepay service is easy to comprehend and follow for some segments of the society living a certain lifestyle. The customers are also able to monitor their daily utility usage or at any time and to specify the notification methods that best suit their lifestyle. The customer may make payments at any time and for any amount using a number of methods and outlets.
-
System 10 as described herein may be easily integrated with existing systems of a utility company. For example, asecure communication server 24 may be provided onsite at a utility company to transmit prepay account and usage information to subsystem 14 to process and administer the prepay accounts. By providing the prepay utility service as described herein, existing accounts receivable amounts are significantly reduced and the number of delinquent accounts is also minimized or eliminated. By taking advantage of modern communication channels, the utility company is able to keep the prepay customer apprised of his/her account balance and provide advanced warning of depleting funds in the prepay account by interactive voice response, email and other electronic means. The utility company no longer needs to attend to the burdensome and costly task of generating and sending monthly billing statements and collections on late payments. - Although embodiments of the present disclosure have been described in detail, those skilled in the art should understand that they may make various changes, substitutions and alterations herein without departing from the spirit and scope of the present disclosure. Accordingly, all such changes, substitutions and alterations are intended to be included within the scope of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.
Claims (14)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/315,085 US20120317005A1 (en) | 2006-03-23 | 2011-12-08 | System and Method for Prepay Account Management System |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/387,611 US8095475B2 (en) | 2006-03-23 | 2006-03-23 | System and method for prepay account management system |
US13/315,085 US20120317005A1 (en) | 2006-03-23 | 2011-12-08 | System and Method for Prepay Account Management System |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/387,611 Continuation US8095475B2 (en) | 2006-03-23 | 2006-03-23 | System and method for prepay account management system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120317005A1 true US20120317005A1 (en) | 2012-12-13 |
Family
ID=38581727
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/387,611 Expired - Fee Related US8095475B2 (en) | 2006-03-23 | 2006-03-23 | System and method for prepay account management system |
US13/315,085 Abandoned US20120317005A1 (en) | 2006-03-23 | 2011-12-08 | System and Method for Prepay Account Management System |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/387,611 Expired - Fee Related US8095475B2 (en) | 2006-03-23 | 2006-03-23 | System and method for prepay account management system |
Country Status (6)
Country | Link |
---|---|
US (2) | US8095475B2 (en) |
EP (2) | EP2005399A2 (en) |
CN (1) | CN101438325A (en) |
AU (1) | AU2007235093A1 (en) |
NZ (2) | NZ608189A (en) |
WO (1) | WO2007117831A2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
WO2016145505A1 (en) * | 2015-03-13 | 2016-09-22 | Redknee Inc. | Method, system and apparatus for controlling prepaid delivery of utilities |
US9786003B2 (en) | 2012-12-11 | 2017-10-10 | Visa International Service Association | Prepaid load with account linking |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US10671749B2 (en) | 2018-09-05 | 2020-06-02 | Consumerinfo.Com, Inc. | Authenticated access and aggregation database platform |
Families Citing this family (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7389275B2 (en) | 2002-03-05 | 2008-06-17 | Visa U.S.A. Inc. | System for personal authorization control for card transactions |
US20070250321A1 (en) * | 2006-04-24 | 2007-10-25 | E3 Infosystems, Inc. | Personal and remote article-on-demand system |
US7991131B2 (en) * | 2007-01-16 | 2011-08-02 | Alcatel-Lucent Usa Inc. | Control of prepaid balance status notification |
US11610275B1 (en) | 2007-09-04 | 2023-03-21 | Bluenet Holdings, Llc | System and methods for customer relationship management for an energy provider |
US8442917B1 (en) * | 2007-09-04 | 2013-05-14 | Ambit Holdings, L.L.C. | Energy distribution and marketing backoffice system and method |
US10650359B2 (en) | 2007-09-04 | 2020-05-12 | Bluenet Holdings, Llc | Energy distribution and marketing backoffice system and method |
US10108976B2 (en) | 2007-09-04 | 2018-10-23 | Bluenet Holdings, Llc | System and method for marketing sponsored energy services |
US8401965B2 (en) * | 2007-10-31 | 2013-03-19 | Bank Of America Corporation | Payment handling |
US8320539B2 (en) * | 2008-02-26 | 2012-11-27 | Idi Billing Solutions | Advanced payment for telephone services |
US20090307117A1 (en) * | 2008-06-09 | 2009-12-10 | Greiner Kevin A | Utility services payment system, methods and apparatus |
US20100042522A1 (en) * | 2008-08-15 | 2010-02-18 | Credit Message Inc. | Automatic electronic reminder delivery |
US8112062B2 (en) * | 2009-12-22 | 2012-02-07 | Cellco Partnership | System and method for sending threshold notification in real time |
EP2523388A4 (en) * | 2010-01-08 | 2014-01-29 | Alcatel Lucent | Method and device for notifying account information oriented to data-type terminal |
US20110225072A1 (en) * | 2010-03-09 | 2011-09-15 | Sewell Ronald R | Automated utility metering systems and methods |
US8683042B1 (en) * | 2010-11-24 | 2014-03-25 | Sprint Communications Company L.P. | Maintaining policy traffic statistics over multiple sessions |
KR101239217B1 (en) * | 2011-12-09 | 2013-03-06 | 시큐아이닷컴 주식회사 | High availability system, method for synchronizing devices in the same, and method for managing devices in the same |
JP5553821B2 (en) * | 2011-12-28 | 2014-07-16 | 楽天株式会社 | Information processing server, information processing method, information processing program, recording medium recorded with information processing program, portable terminal, portable terminal program, and recording medium recorded with portable terminal program |
WO2014001995A2 (en) * | 2012-06-28 | 2014-01-03 | Contour Technology (Pty) Ltd. | Automated transaction system |
US10366403B2 (en) * | 2012-10-15 | 2019-07-30 | International Business Machines Corporation | Distributed forecasting and pricing system |
US20150193872A1 (en) | 2014-01-06 | 2015-07-09 | iVinci Partners, LLC | Systems and methods of managing payments that enable configurable financing and payment terms |
CN104199470B (en) * | 2014-08-08 | 2017-02-15 | 潍坊奥博仪表科技发展有限公司 | Steam/hot water IC card prepaid intelligent controller |
CN104899978B (en) * | 2015-06-02 | 2018-03-20 | 中国南方电网有限责任公司 | Based on the resident's day electricity charge charging method and system for taking control technology |
US11030595B1 (en) * | 2015-11-16 | 2021-06-08 | Wells Fargo Bank, N.A. | Integrated utility distribution and automated billing |
CN111028429A (en) * | 2019-12-27 | 2020-04-17 | 深圳华越诚电子科技有限公司 | Water, electricity and gas remote prepayment method and system |
US11941606B2 (en) * | 2020-01-24 | 2024-03-26 | The APocket Company LLC | Mobile platform and associated methods for digital gifts and business networking |
US11875320B1 (en) | 2020-02-28 | 2024-01-16 | The Pnc Financial Services Group, Inc. | Systems and methods for managing a financial account in a low-cash mode |
CN113643477A (en) * | 2021-08-10 | 2021-11-12 | 国网江苏省电力有限公司营销服务中心 | Intelligent electric meter internet of things payment interactive terminal and method based on DCEP |
CN113689208A (en) * | 2021-08-29 | 2021-11-23 | 上海舵衔数字科技中心 | Method for filling up prepaid account of medical institution |
CN115471949A (en) * | 2022-08-24 | 2022-12-13 | 华能苏州热电有限责任公司 | Steam heating network prepayment system |
CN115941687A (en) * | 2022-11-15 | 2023-04-07 | 浪潮云信息技术股份公司 | Cloud platform service bill processing method and system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5146067A (en) * | 1990-01-12 | 1992-09-08 | Cic Systems, Inc. | Prepayment metering system using encoded purchase cards from multiple locations |
Family Cites Families (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2042777B (en) | 1979-02-21 | 1983-05-11 | South Eastern Elec Board | Electrical energy consumption meter |
US4795892A (en) * | 1987-12-09 | 1989-01-03 | Cic Systems, Inc. | Pre-paid commodity system |
BR9405758A (en) | 1993-02-12 | 1995-11-28 | Ekstroem Ind Inc | Apparatus for measuring electricity consumption Apparatus for remote electricity reading Process for measuring electricity supply Process for calculating consumed electricity and Apparatus for remote measuring |
US5677945A (en) | 1995-06-06 | 1997-10-14 | Mci Corporation | Account balancing and monitoring system for a telecommunications network |
US6188689B1 (en) | 1996-10-04 | 2001-02-13 | Kabushiki Kaisha Toshiba | Network node and method of frame transfer |
US6058300A (en) * | 1997-02-04 | 2000-05-02 | National Telemanagement Corporation | Prepay telecommunications system |
IT1295471B1 (en) | 1997-10-03 | 1999-05-12 | Taglioni Communications S A S | SYSTEM FOR DETECTION OF DOMESTIC CONSUMPTION OF ELECTRICITY, THERMAL ENERGY, WATER AND GAS. |
US20020120569A1 (en) | 1997-10-16 | 2002-08-29 | Day Mark E. | System and method for communication between remote locations |
US6452915B1 (en) | 1998-07-10 | 2002-09-17 | Malibu Networks, Inc. | IP-flow classification in a wireless point to multi-point (PTMP) transmission system |
US6667967B1 (en) | 1999-05-14 | 2003-12-23 | Omninet Capital, Llc | High-speed network of independently linked nodes |
DE19927296A1 (en) | 1999-06-15 | 2000-12-28 | Siemens Ag | Arrangement for charging in a telephone network and method for operating such |
KR20010000053A (en) | 1999-11-30 | 2001-01-05 | 류창완 | Payment system for using multi prepaid cards and method of selling the cards |
US20040024483A1 (en) * | 1999-12-23 | 2004-02-05 | Holcombe Bradford L. | Controlling utility consumption |
US20010027490A1 (en) | 2000-01-25 | 2001-10-04 | Gabor Fodor | RSVP handling in 3G networks |
US6947854B2 (en) * | 2000-02-29 | 2005-09-20 | Quadlogic Controls Corporation | System and method for on-line monitoring and billing of power consumption |
US6574195B2 (en) | 2000-04-19 | 2003-06-03 | Caspian Networks, Inc. | Micro-flow management |
US8725657B2 (en) | 2000-05-22 | 2014-05-13 | Secure Electrans Limited | Utility metering system incorporating a transaction authorisation system |
US6707894B1 (en) * | 2000-05-24 | 2004-03-16 | At&T Wireless | Prepaid calling time processing: a method and apparatus for processing pre-paid calling time in a telephone communication system |
US20010051933A1 (en) * | 2000-06-08 | 2001-12-13 | Rowley Robert H. | Prepaid utility service system |
US6900738B2 (en) | 2000-06-21 | 2005-05-31 | Henry Crichlow | Method and apparatus for reading a meter and providing customer service via the internet |
US20020040355A1 (en) * | 2000-10-02 | 2002-04-04 | Weiner Steven D. | System and method for utility meter swipecard |
US20020065761A1 (en) * | 2000-11-29 | 2002-05-30 | Fischer David Howard | Subscriber notification criteria for electronic auctions |
EP1249995A2 (en) | 2001-04-12 | 2002-10-16 | Siemens Aktiengesellschaft | Optimised recharging of prepaid accounts |
US20020178063A1 (en) * | 2001-05-25 | 2002-11-28 | Kelly Gravelle | Community concept for payment using RF ID transponders |
US20030055677A1 (en) * | 2001-09-14 | 2003-03-20 | Automated Energy, Inc. | Utility monitoring and management system |
US7161942B2 (en) | 2002-01-31 | 2007-01-09 | Telcordia Technologies, Inc. | Method for distributing and conditioning traffic for mobile networks based on differentiated services |
US20030225713A1 (en) * | 2002-03-08 | 2003-12-04 | Atkinson Roger F. | Prepayment system for power distribution using RFID technology |
CN1656661A (en) | 2002-03-28 | 2005-08-17 | 罗伯绍控制器公司 | Energy management system and method |
US20040198316A1 (en) * | 2002-06-21 | 2004-10-07 | Compaq Information Technologies Group, L.P. | Visual display of prepay balance on a mobile station upon registration and post-call |
US6995666B1 (en) * | 2002-10-16 | 2006-02-07 | Luttrell Clyde K | Cellemetry-operated railroad switch heater |
US20040093298A1 (en) * | 2002-11-07 | 2004-05-13 | Mcclure Robert E. | Method for providing energy commodities trade outsourcing services within the energy markets |
US7400264B2 (en) * | 2003-02-14 | 2008-07-15 | Energy Technology Group, Inc. | Automated meter reading system, communication and control network for automated meter reading, meter data collector, and associated methods |
WO2004088641A2 (en) * | 2003-03-26 | 2004-10-14 | Way Systems, Inc. | System and method for securely storing, generating, transferring and printing electronic prepaid vouchers |
US20040243525A1 (en) | 2003-05-07 | 2004-12-02 | Brian Forrester | System and method for disconnecting utility services |
WO2005050586A2 (en) * | 2003-11-18 | 2005-06-02 | Amron Technologies, Inc. | Host-client utility meter systems and methods for communicating with the same |
US20050187888A1 (en) | 2004-02-19 | 2005-08-25 | William Sherman | Method for associating information pertaining to a meter data acquisition system |
US7379791B2 (en) * | 2004-08-03 | 2008-05-27 | Uscl Corporation | Integrated metrology systems and information and control apparatus for interaction with integrated metrology systems |
US20070083479A1 (en) * | 2005-09-14 | 2007-04-12 | Swartz Stephen B | Method, apparatus and program storage device for providing a prepaid metering system |
-
2006
- 2006-03-23 US US11/387,611 patent/US8095475B2/en not_active Expired - Fee Related
-
2007
- 2007-03-12 NZ NZ608189A patent/NZ608189A/en not_active IP Right Cessation
- 2007-03-12 AU AU2007235093A patent/AU2007235093A1/en not_active Abandoned
- 2007-03-12 EP EP07779555A patent/EP2005399A2/en not_active Withdrawn
- 2007-03-12 EP EP13161460.4A patent/EP2610828A1/en not_active Withdrawn
- 2007-03-12 NZ NZ595261A patent/NZ595261A/en not_active IP Right Cessation
- 2007-03-12 CN CNA2007800160916A patent/CN101438325A/en active Pending
- 2007-03-12 WO PCT/US2007/063827 patent/WO2007117831A2/en active Application Filing
-
2011
- 2011-12-08 US US13/315,085 patent/US20120317005A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5146067A (en) * | 1990-01-12 | 1992-09-08 | Cic Systems, Inc. | Prepayment metering system using encoded purchase cards from multiple locations |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9786003B2 (en) | 2012-12-11 | 2017-10-10 | Visa International Service Association | Prepaid load with account linking |
US10846790B2 (en) | 2012-12-11 | 2020-11-24 | Visa International Service Association | Prepaid load with account linking |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US10269065B1 (en) | 2013-11-15 | 2019-04-23 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
WO2016145505A1 (en) * | 2015-03-13 | 2016-09-22 | Redknee Inc. | Method, system and apparatus for controlling prepaid delivery of utilities |
US20180068397A1 (en) * | 2015-03-13 | 2018-03-08 | Redknee Inc. | Method, system and apparatus for controlling prepaid delivery of utilities |
US11544802B2 (en) * | 2015-03-13 | 2023-01-03 | Ortiva Canada Inc. | Method, system and apparatus for controlling prepaid delivery of utilities |
US10671749B2 (en) | 2018-09-05 | 2020-06-02 | Consumerinfo.Com, Inc. | Authenticated access and aggregation database platform |
US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US11265324B2 (en) | 2018-09-05 | 2022-03-01 | Consumerinfo.Com, Inc. | User permissions for access to secure data at third-party |
US11399029B2 (en) | 2018-09-05 | 2022-07-26 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
Also Published As
Publication number | Publication date |
---|---|
US8095475B2 (en) | 2012-01-10 |
WO2007117831A2 (en) | 2007-10-18 |
US20070260562A1 (en) | 2007-11-08 |
NZ595261A (en) | 2013-05-31 |
EP2610828A1 (en) | 2013-07-03 |
WO2007117831A3 (en) | 2008-01-03 |
EP2005399A2 (en) | 2008-12-24 |
CN101438325A (en) | 2009-05-20 |
AU2007235093A1 (en) | 2007-10-18 |
NZ608189A (en) | 2014-10-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8095475B2 (en) | System and method for prepay account management system | |
US7627524B2 (en) | System, method, and computer program product for receiving and processing payments | |
US20050125347A1 (en) | Bill payment authorization system and method | |
US20130013497A1 (en) | Global remittance platform | |
RU2520372C2 (en) | Management of shared service | |
US7013127B2 (en) | Systems and methods for employing “pay-as-you-go” telecommunication services | |
CN101370060B (en) | A kind of multiple channel automated refill system, method and apparatus | |
CN110348784A (en) | One kind posting part method, apparatus, equipment and storage medium | |
KR100704334B1 (en) | Access contract changing method and server of a communication service provider | |
US20070271193A1 (en) | Billing and account management system | |
KR100848363B1 (en) | System and method for managing funeral parlor | |
CN114418156A (en) | Business booking and settlement management system | |
CN111429261A (en) | Credit card information accounting method, system, terminal equipment and storage medium based on transaction | |
KR20140015171A (en) | Method for providing deferred type payment using prepaid type moile card | |
KR20010095938A (en) | Prepayment system using mileage | |
KR20100107366A (en) | System and method for managing medical expenses settlement by installments using phone bill and recording medium | |
KR20020034001A (en) | Payment for Proxy Service providing System by Network and Method thereof | |
KR20170080554A (en) | Server and method for electronic transfer based on user approval | |
KR20000058912A (en) | The consolidated receipt management system by internet | |
JP2002207952A (en) | System and method for suspense receipt management | |
KR20020029478A (en) | Bill unify management and handling system and method using communication network | |
KR100895403B1 (en) | Method and system for reflecting subscribers' changed charge information that happen during subscribers' a charging cycle | |
JP2002073999A (en) | Automatic paying/transferring service system to credit payment account | |
WO2003065277A1 (en) | Method of creating a transaction related record | |
JPH1185886A (en) | Financial institution system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EXCELERON SOFTWARE, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HUTSON, CRAIG D.;GAINES, CHRIS;HANSON, DANIEL A.;SIGNING DATES FROM 20060328 TO 20060329;REEL/FRAME:027350/0687 |
|
AS | Assignment |
Owner name: EXCELERON SOFTWARE, LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UTILITY PREPAID SOFTWARE, INC.;REEL/FRAME:034730/0929 Effective date: 20130722 Owner name: UTILITY PREPAID SOFTWARE, INC., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:EXCELERON SOFTWARE, INC.;REEL/FRAME:034771/0784 Effective date: 20130717 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |