Method and system for credit card reimbursements for health care transactions

Information

  • Patent Grant
  • 7743979
  • Patent Number
    7,743,979
  • Date Filed
    Monday, June 2, 2008
    16 years ago
  • Date Issued
    Tuesday, June 29, 2010
    14 years ago
Abstract
According to one embodiment, the present invention relates to a method and a system for reimbursing credit card transactions for health care services and/or products. An exemplary method and system may involve registering a user for reimbursement wherein the user identifies one or more payment mechanisms and one or more reimbursement methods; identifying a user transaction with the one or more payment mechanisms at a merchant wherein the user transaction comprises one or more purchases; receiving merchant data regarding the user transaction; determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the merchant data; and reimbursing the user for eligible purchases via the one or more reimbursement methods.
Description
FIELD OF THE INVENTION

The present invention relates generally to reimbursements for transactions and, more particularly, to a method and system for reimbursing credit card and other transactions for health care services and/or products.


BACKGROUND OF THE INVENTION

As health care expenses continue to rise, consumers are taking on a bigger role in paying and managing health care costs. This increase in consumer responsibility ranges from greater cost-sharing for medical services to having to choose among increasing health care financing options. One important tool for consumer participation in health care is the use of consumer-directed accounts. Consumer-directed accounts are dedicated funding pools used for health care expenses at the discretion of an individual. These accounts can be procured either individually or through an employer, and may or may not involve tax advantages to the user of the account. A key requirement in the use of consumer-directed accounts is that they finance only those goods and services that are authorized by the Internal Revenue Service (IRS) as eligible medical expenses. This creates the need for close oversight of consumer-directed account programs, which involves high paper volumes, manual intervention, and substantial administrative expense to ensure compliance. In addition, the current process often requires participants to pay for goods and services and then file for reimbursement out of the funds contributed to the consumer-directed account. This requires participants to make the payment up-front even though the funds may have already been set aside and to handle a variety of paper documents during filing and reimbursement. These challenges significantly undermine the efficiency of consumer-directed account programs, resulting in dissatisfied participants and program sponsors. Given these difficulties, there is a clear need for an electronic solution that automates the administration and use of consumer-directed accounts, while maintaining compliance with the rules and regulations under which consumer-directed accounts are governed.


The trend to consumer-directed health care has been supported by three major legislative innovations within the past thirty years; namely, the Revenue Act of 1978, the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and a ruling in 2002 by the IRS establishing Health Reimbursement Arrangements. Each of these initiatives created the model for a consumer-directed account in use today. The Revenue Act of 1978 created Flexible Spending Accounts (FSA), which are employer-sponsored accounts funded by employees' pre-tax contributions from payroll. Flexible Spending Accounts can be established and used for a variety of purposes, such as the payment of health care, dependent care, or public transportation expenses. Because Flexible Spending Accounts are funded with pre-tax dollars, participants in an FSA program can realize substantial savings on eligible expenses. Employers value FSA programs because these accounts provide benefits to employees and reduce employees' taxable income on which an employer must pay Federal Insurance Contributions Act (FICA) taxes. Currently, there are more than 8 million Health Flexible Spending Accounts in the US, with over 9 billion dollars in annual contributions. Health FSA contributions are expected to grow significantly over the next several years, as consumers take on more of the burden for health care costs and seek tax-advantaged tools to finance those expenses.


Two other types of consumer-directed accounts—the Medical Savings Account (MSA) and the Health Reimbursement Arrangement (HRA)—were introduced within the past decade. The MSA was established with the passage of HIPAA in 1996. The MSA provides for a tax-advantaged account reserved for individuals who are self-employed or employed at a small business, and who use a qualifying high-deductible health plan. The MSA is designed to provide tax benefits on payments towards a deductible portion of a high-deductible health plan. A key advantage of the MSA to participants is the ability to carry over unused funds in the account from one plan year to the next. This differs from FSA programs that require unused funds to be forfeited by the employee and turned over to the employer health plan, a requirement commonly known as the FSA “use it or lose it” provision. The IRS established the HRA in June 2002, drawing on the strengths of both the FSA and the MSA. For example, employers of all sizes may implement an HRA program (e.g., FSA). In addition, unused funds contributed to an HRA may roll over from one plan year to the next, like MSA. Due to its flexibility and attractiveness to employees, the HRA is expected to quickly become prevalent throughout the employee benefits marketplace.


A result of these initiatives is the proliferation of consumer-directed accounts used to provide tax advantages for health care spending. Although FSA, MSA, and HRA are the most common forms of consumer-directed accounts, others may also exist. As consumer-directed health care evolves, there will be continued innovation in the field of consumer-directed accounts This will likely result in new account structures being introduced over time.


Because consumer-directed accounts are legal structures, there are a wide variety of associated rules and regulations. Some important rules include provisions on the types of expenses that can be financed through a consumer-directed account, as determined by the IRS. In general, consumer-directed accounts can only pay for expenses that are medically necessary (such as prescription eye care, prescription drugs, hearing devices, or any other medically necessary expenses), whereas expenses that are not medically necessary (typically “cosmetic” goods and services such as non-prescription sunglasses, cosmetic surgery, or any other non-medically necessary expenses) are deemed ineligible. Because consumer-directed accounts confer tax advantages to participants, the IRS requires strict compliance from employers and their agents to ensure that only eligible medical expenses are financed through a consumer-directed account. If ineligible medical expenses are paid for through a consumer-directed account, tax advantages are being made available inappropriately. As a result, the IRS can assign and enforce penalties for non-compliance.


Most consumer-directed accounts offered through an employer benefits plan are managed and administered by an entity other than the employer itself usually a Third Party Administrator (TPA). A TPA can provide a variety of services to employers, such as managing claim submissions from employees and generating reports on plan usage. The requirements to comply with IRS guidelines for expense eligibility create a heavy burden on the TPA in managing a consumer-directed account program. Whenever an employee files for reimbursement out of a consumer-directed account, the TPA must audit and validate the claim to ensure that it is for a valid medical expense. Typically, the employee will provide proof of eligibility in the form of a paper receipt or invoice documenting the nature of the expense, which the TPA reviews to confirm compliance. This validation process is extremely labor-intensive and generally requires TPA personnel to review a given claim manually. Further complicating the TPA's task of ensuring compliance is the ability of employers to customize expense eligibility rules to their particular program. That is, although the IRS governs what is potentially allowed, employers have the option to limit further the specific types of expenses that their particular consumer-directed account program will authorize. A TPA must therefore consult the plan rules for a given program before granting approval to an employee's claim. After the claim has been deemed eligible and sufficient funds have been confirmed within the employee's consumer-directed account, the TPA will remit funds, usually by paper check, with a paper explanation of payment to the employee.


Because of the challenges associated with the current manual processing and administration of consumer-directed accounts, industry participants have attempted to develop a variety of mechanisms to streamline activities and improve automation. As consumer-directed accounts grow in importance and usage, these efforts will become increasingly relevant to the ways in which health care expenses are paid and managed.


Efforts to innovate within the administration and use of consumer-directed accounts have historically proceeded in two key ways. First, many Third Party Administrators have attempted to manage the existing paper process better without actually reducing the submissions of paper claim forms. An example of this type of innovation is the use of scanning and character-recognition technology to store an electronic copy of paper claims as they are received and to adjudicate claims based on the information contained in the electronic image. Using this type of technology reduces the amount of paper that a TPA has to keep on file and enables better management of claim documents than if such documents were to remain in paper form. Although this approach may realize certain cost savings, the key problems associated with the current process for managing consumer-directed accounts still remain. That is, participants still have to prepare and file paper claims and front payment for goods and services, and Third Party Administrators must still handle paper documents and manually review the expense eligibility of submitted claims.


The second way industry participants have sought to improve the administration and use of consumer-directed accounts is to attempt to reduce the number of paper claim forms submitted by participants. Manual mechanisms for obviating claim form submission have existed for several years. For example, in some cases, a TPA may be able to make a direct payment from a consumer-directed account to a provider of eligible goods or services without the participant having to file a claim form or initiate a payment. This method is usually applied for payments that are recurring in nature (such as elder care or regular prescription drug purchases), because it requires notifying the provider to change their process and forward an invoice for payment to the TPA directly rater than to the employee. In addition, such payments are only possible when payment is not required at the time services are rendered. For prescription drug transactions within a pharmacy, for example, payment is expected at the point of sale, precluding a post-hoc payment from the TPA to the provider. Moreover, although the participant does not have to file a paper claim form, the TPA must still employ a manual process for adjudicating and paying claims.


Another manual mechanism for reducing the number of paper claim submissions by savings account participants is to automatically apply consumer-directed account funds towards deductibles or co-payments determined under an employer-sponsored health plan. This option has historically been possible only when the TPA manages claims for both the consumer-directed account and the health plan for a given employer. In this scenario, an employee obtains goods or services from a medical provider, causing the provider to generate and submit a claim to the employee's health plan. Once the TPA has adjudicated the claim and determined the employee's payment responsibility, the TPA remits funds from the consumer-directed account directly to the provider, eliminating the need for the employee to pay the provider up-front and then prepare and file a claim with the TPA for reimbursement from the consumer-directed account. However, instances when an individual TPA manages both the consumer-directed accounts and the health plan for a given employer are limited, making this option available to relatively few consumer-directed account participants.


An alternative mechanism for reducing paper claims submissions and improving efficiencies involves enabling electronic claim submission and payment through the use of a stored value program. A stored value program typically includes supplying each participant with a payment card that is linked to a consumer-directed account. A participant then presents the physical card or the card number for payment wherever medical expenses are incurred. The health care provider initiates a payment transaction, that transfers funds from the consumer-directed account to the provider's bank account, eliminating the need for the participant to provide up-front payment and then file for later reimbursement through the TPA. Likewise, the TPA benefits by not having to manage and process paper forms and claims associated with the card-initiated transaction. Because of the wide acceptance of payment cards, participants are able to use consumer-directed account funds in a variety of venues, such as in a retail location, through the mail, or over the phone and other types of transactions.


In stored value arrangements, payments are made directly from the FSA without being substantiated first as eligible expenses. This forces the TPA to solicit receipts from the employee and make restitution to the FSA for non-compliant claims. Often, the employee is lax with submission and sometimes may fail to submit receipts at all.


Although stored value programs have the potential to create substantial efficiencies and benefits, they also have the potential for substantial abuse. In particular, current programs risk exposing employers and Third Party Administrators to non-compliance with IRS guidelines for consumer-directed account expense eligibility. Unlike the current manual process that allows a TPA to audit detailed transaction information in the form of a submitted receipt, card transactions generally communicate only the payment amount requested and the type of merchant that is initiating the transaction (e.g., a pharmacy, a toy store, etc.). Many stored value programs thus authorize the use of card payments to merchants that are considered “health care providers” (such as doctors, optometrists, pharmacies, etc.) and deny card transactions at non-health care merchants (such as a toy store or apparel retailer). This type of filtering is inadequate because many putative health care merchants may still sell goods or services that do not meet the IRS guidelines for payment from a consumer-directed account. For example, a consumer-directed account participant receiving services from a physician's office may be receiving cosmetic enhancements that are not medically necessary. Alternatively, a participant may present their card at a pharmacy for payment toward a wide variety of non-eligible goods (e.g., magazines, office supplies, etc.). Unless a stored value program analyzes detailed, individual transaction data to determine expense eligibility, ineligible expenses may be inappropriately authorized and funded by the consumer-directed account.


Because of the risk of non-compliance associated with card programs, many Third Party Administrators review card transactions post-payment and audit them for inappropriate activity. According to IRS guidelines, claims do not need to be confirmed as eligible expenses prior to payment as long as 100% of all claims are reviewed post-payment. In cases where expenses paid by a consumer-directed account are later deemed ineligible, participants must be made to restore misappropriated funds to the savings account, forcing the TPA into the costly and awkward role of collections officer. Due to the risk of fraudulent payment, a TPA may even require that a participant substantiate every card transaction with paper documentation, which then fails to relieve employees and Third-Party Administrators of the traditional challenges associated with participating in and managing a consumer-directed account. Frequent TPA audits and collection activities can significantly undermine the efficiencies that stored value programs were designed to achieve.


Because the IRS has the ability to levy substantial fines for non-compliance, many employers are unwilling to accept the risks associated with current stored value programs, opting instead for the less efficient but potentially more compliant traditional, manual process.


SUMMARY OF THE INVENTION

According to an embodiment of the present invention, a method and system facilitates the reimbursement of eligible transactions, such as health care transactions.


According to an exemplary embodiment of the present invention, a computer implemented method for facilitating reimbursements for eligible transactions comprising the steps of registering a user for reimbursement wherein the user identifies one or more payment mechanisms and one or more reimbursement methods; identifying a user transaction with the one or more payment mechanisms at a merchant wherein the user transaction comprises one or more purchases; receiving merchant data regarding the user transaction; determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the merchant data; and reimbursing the user for eligible purchases via the one or more reimbursement methods.


In accordance with other aspects of this exemplary embodiment of the present invention, the payment mechanism comprises one or more of a credit card, debit card and token; the reimbursement method comprises an electronic deposit in an account; the reimbursement method comprises credit against an credit card balance; the reimbursement method comprises deposit in an investment account; the merchant data comprises line item data of the user transaction; the step of determining eligibility comprises applying a filter to the merchant data; the filter comprises one or more IRS guidelines; the filter comprises additional one or more employer specified guidelines; the user transaction comprises ineligible and eligible purchases; the ineligible purchases are applied to a payment channel associated with the payment mechanism; reimbursement is made from a consumer-directed account; the consumer-directed account comprises a Flexible Spending Account associated with the participant wherein the participant designates a predetermined amount of pre-taxed dollars to be deducted from the participant's paycheck and contributed to the participant's consumer-directed account; the consumer-directed account comprises a Medical Savings Account associated with the participant; the consumer-directed account comprises a Health Reimbursement Arrangement account associated with the participant.


According to another exemplary embodiment of the present invention, a computer implemented method for facilitating reimbursements for eligible transactions comprises the steps of: identifying one or more payment mechanisms with a computer implemented reimbursement system; identifying one or more reimbursement methods with the computer implemented reimbursement system; making one or more purchases at a merchant entity with the one or more identified payment mechanisms; and receiving reimbursement for eligible purchases via the one or more reimbursement methods.


In accordance with other aspects of this exemplary embodiment of the present invention, the payment mechanism comprises one or more of a credit card, debit card and token; the reimbursement method comprises one or more of an electronic deposit in an account, credit against an credit card balance and deposit in an investment account; ineligible purchases are applied to a payment channel associated with the payment mechanism; reimbursement is made from a consumer-directed account.


According to another exemplary embodiment of the present invention, a computer implemented system for facilitating reimbursements for eligible transactions comprises: register module for registering a user for reimbursement wherein the user identifies one or more payment mechanisms and one or more reimbursement methods; payment module for identifying a user transaction with the one or more payment mechanisms at a merchant wherein the user transaction comprises one or more purchases and receiving merchant data regarding the user transaction; eligibility module for determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the merchant data; and reimbursement module for reimbursing the user for eligible purchases via the one or more reimbursement methods.


According to another exemplary embodiment of the present invention, a computer implemented system for facilitating reimbursements for eligible transactions comprises: payment module for identifying one or more payment mechanisms with a computer implemented reimbursement system; and reimbursement module for identifying one or more reimbursement methods with the computer implemented reimbursement system; where the user makes one or more purchases at a merchant entity with the one or more identified payment mechanisms and receives reimbursement for eligible purchases via the one or more reimbursement methods.





BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present invention, reference is now made to the appended drawings. These drawings should not be construed as limiting the present invention, but are intended to be exemplary only.



FIG. 1 is an exemplary diagram of a system for facilitating health care reimbursement, according to an embodiment of the present invention.



FIG. 2 is an exemplary flowchart of a method for obtaining reimbursements for various transactions, according to an embodiment of the present invention.



FIG. 3 is an exemplary flowchart of a method for providing reimbursements for various transactions, according to an embodiment of the present invention.



FIG. 4 is an exemplary diagram of a system for facilitating health care reimbursements, according to an embodiment of the present invention.





DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENT(S)

An embodiment of the present invention is directed to a method and system for facilitating reimbursements for eligible health care transactions. Health care transactions may involve various spending categories, which may include but are not limited to pharmaceuticals, co-payments (co-pays), dental expenses, eye care services, etc.


Traditional mechanisms for reimbursement require submitting paper receipts and claim forms to get reimbursed from a health care account, such as Flexible Spending Account (FSA). Other health care accounts may include Health Reimbursement Arrangements (HRAs), Medical Savings Accounts (MSAs), Dependent Care Flexible Spending Accounts or other consumer-directed accounts, including consumer-directed savings accounts. According to an embodiment of the present invention, a user (e.g., consumer, employee, etc.) may use a credit card (or other card product or payment mechanism) to pay for health care goods and services, where reimbursement is automatic for eligible medical expenses, such as prescription drugs, doctor's office co-pays, etc. As a result, users are not required to save or send in receipts, forms or other paperwork.


According to an embodiment of the present invention, the user may register with a reimbursement system of an embodiment of the present invention. Registration may be performed through the employer, which may include the employer's human resources department, other department or personnel. Registration may also be performed online, over the phone, through mail, in person or through other forms of communication. During registration, the user may identify a payment mechanism and reimbursement preference, e.g., how the user wants payments for qualified health care purchases reimbursed. The payment mechanism may include credit cards, debit cards, stored value cards, tokens and other types of payment. In addition, the user may direct finds to be reimbursed electronically in a designated account, such as a checking account; credited against an outstanding credit card balance; placed in an investment account to accumulate additional savings over time or other account; or other reimbursement method. Other information and/or preferences may be provided. Once the payment mechanism is registered, the user may use the registered payment mechanism at a doctor's office, pharmacy and various health care and/or other locations. Purchases may also be made at other merchants who offer eligible as well as ineligible health care products and/or services. Purchases may be made at a merchant store, online, via phone order, mail order or other method of purchasing products and/or services. Through an embodiment of the present invention, whenever the user purchases something (e.g., product, service, etc.) that is eligible for reimbursement from a participating account (e.g., Flexible Spending Account or other account), the funds will be automatically reimbursed in the manner specified. As reimbursement is made automatically, the user can avoid forfeiting unused balances in the participating account by forgetting to submit receipts and/or other paperwork.



FIG. 1 is an exemplary diagram of a system for facilitating health care reimbursement, according to an embodiment of the present invention. User 140, 142 may represent any participant (e.g., employee, etc.) who may engage in a transaction for health care products and/or services (e.g., prescription drugs, etc.). Merchant 144, 146 may represent a retail store, a mail order facility, a website, a physician affiliated store, pharmacy or other entity providing products and/or services. Merchants may provide health care products and/or services as well as other products and/or services.


Other participants may include Health Care Provider 148, Pharmacy Benefit Manager (PBM) and/or other health care participants. The user (e.g., employee, etc.) may receive services and/or products from Health Care Provider 148. For example, a user may visit a doctor or hospital (or other health care provider) to receive treatment, advice or other services and/or products. Health Care Provider may include a physician, hospital, specialist, psychologist, physical therapist, optometrist, dentist or other provider. According to another example, PBM may manage claims from one or more pharmacies and perform claim adjudication. For example, a pharmacy may verify claim or prescription eligibility and determine a co-pay amount through PBM. More specifically, PBM may adjudicate the claim, which may involve determining whether the transaction is covered by insurance (or other entity) and the amount owed by the user (e.g., self-pay due). Self-pay due may represent the remaining balance due or the amount due by the user. For example, a user may purchase a prescription drug from a pharmacy. Based at least in part on information provided by the pharmacy, PBM may determine that the prescription drug will cost $100, where $80 will be covered by insurance and the participant will be liable for $20 (e.g., the self-pay due). Thus, PBM may determine the amount owed by the participant and payable by the participant's account (e.g., FSA, MSA, HRA or other consumer-directed account), if the claim is eligible for payment.


An embodiment of the present invention may also support various transaction environments. For example, a user may purchase one or more products and/or services through a Merchant. The user may engage in a transaction using a card or other payment mechanism. In addition, the participant may purchase the one or more products and/or services via the Internet, phone order or other point of sale by providing an identifier (e.g., account number, password, PIN, etc.) associated with a participant's payment mechanism.


System 100 provides reimbursement functionality provided by an embodiment of the present invention. System 100 may be associated with one or more employers 160, TPAs 162 and/or other entities. Employer 160 may set up an account for one or more users 140, 142, who may be associated with employer 160. The account may include various accounts, such as consumer-directed accounts, FSAs, MSAs, HRAs, etc. TPA 162 may manage the accounts for the employer or other entity. In accordance with various embodiments of the present invention, communication may be established via Internet, Ethernet, Intranet, wireless communication and/or other modes of electronic communication or other form of communication.


As shown in FIG. 1, System 100 provides reimbursement functionality in accordance with various embodiments of the present invention. Credit Card Company 150 may be separate or combined with System 100. In addition, Employer 160 may be separate or combined with System 100. Other various combinations may be implemented. System 100 may include modules for providing reimbursement functionality. Modules may include Register Module 112, Payment Mechanism Module 114, Reimbursement Module 116, Eligibility Module 118, User Interface 120, Billing Module 122 and/or other modules. The modules of System 100 may be further combined, duplicated and/or separated. In addition, the modules of System 100 may also be provided across multiple systems and/or other platforms. Other implementations may be realized.


The various modules of System 100 may access and/or store data at Databases 130, 132. In the exemplary embodiment of FIG. 1, Filters Database 130 and Eligibility Database 132 are provided. Additional databases may be implemented. Further, the databases may be consolidated into a single database or further separated. Filters Database 130 may provide various filters for identifying eligible expenses. Eligibility Database 132 may provide data (e.g., data tables, data sets, binary fields, etc.) for identifying eligible expenses. In addition, the databases may also store customer data, payee/recipient data, payment data, etc. Other data may be stored and/or accessed. Other sources of information (e.g., external and/or internal sources of data) may also be accessed by the various modules of System 100.


An embodiment of the present invention is directed to the automated matching of card transaction activity with batch data feeds from entities involved in health care and/or other transactions. The batch data feeds may include line-level information for substantiating transactions as eligible medical expenses and automating the reimbursement process. Data may be received or accessed from card-acquiring merchants, such as Walgreens™, LensCrafters™, etc., and non-merchant partners such as Pharmacy Benefit Managers (PBMs) and Insurers, as well as other entities, such as credit card companies, third parties and/or other participants. The batch data feeds may include detailed transaction information for determining whether each product and/or service is eligible for reimbursement. Based on the information received, a determination may be made as to whether each purchase is eligible for reimbursement or not. For example, the information may include type of product or service, price, purpose, product or service code, date/time of purchase, merchant data, etc.


An embodiment of the present invention may be facilitated through a data table of medical products and services. Data may be presented in other formats as well. For example, the data table may be developed for various potential health care transactions using publicly available data sets and/or other sources of data. Data sets may include Prescription drugs (NDC); Dental (CDT); Medical (CPT/ICD-9) and/or Non-prescription medical products (UPC). Other data sets may also be included. As eligible transactions may change in the future, data sets may be modified, added, deleted, etc.


According to another example, each product and service may contain a binary field for expense eligibility where eligibility may be determined by passing the product or service through one or more filters. Filters may include mandatory guidelines as well as individual imposed guidelines. While IRS guidelines may apply to most or all participants, a particular employer (or other entity) may restrict or expand reimbursement coverage for certain transactions. According to an embodiment of the present invention, data may be passed through one or more filters. For example, a first filter may include IRS guidelines (which may be common to some or all plans) and a second filter may include additional restrictions set by employers and/or TPA agents (which may be unique to particular plans). Additional filters may also be employed. According to an exemplary scenario, plan rules may be established when each employer is configured to enroll employees in the service. At that time, employers may also enable other guidelines for their plans (FSA vs. HRA draw-down priority, etc.). Other methods for identifying eligible expenses may also be implemented in accordance with the various embodiments of the present invention.


On a periodic or other basis, card activity of participating employees may be matched against substantiation partners' line-item data feeds. Adjudication may be driven by the business rules contained in the data table to guarantee compliance and facilitate the reimbursement process in an automated way.


Register Module 112 may receive registration information from a user. Registration information may include user identification information and/or contact information. Users may register directly with the system, through an employer or other department associated with the employer (e.g., human resources department), a credit card company, third party participant and/or other registration entity. Users may register in person, or via other communication methods, such as online, phone, etc. Register Module 112 may confirm registration eligibility which may include determining whether the user is eligible to participate in a health care program, whether the user has a valid participating account (e.g., FSA, MSA, HRA, or other consumer-directed account), whether the user is in good standing (e.g., delinquency, etc.) and/or other qualifications.


The card product may be registered with any participating account an employer (or other entity) sets up for the user. In addition, multiple card products may be implemented based on various consumer and/or business needs and/or preferences. Further, multiple participating accounts may be implemented. Participating accounts may include FSAs, HRAs, MSAs, other consumer directed accounts, and/or other accounts. Other participating accounts may also be identified according to the various embodiments of the present invention. In addition, general accounts, not necessarily health care accounts, may also participate in a system of the present invention where eligible transactions may be reimbursed.


Payment Mechanism Module 114 may receive data concerning a user's preferred payment mechanism. Payment mechanism may include a credit card, debit card, savings account, checking account, stored value card, token and/or other mechanism for making a payment. The user may provide payment mechanism identification, which may include a card number and/or other identifier. In addition, the user may also designate multiple payment mechanisms. In this exemplary embodiment, a user may designate one payment mechanism for certain transactions and another payment mechanism for other transactions. For example, the user may designate a primary credit card for transactions under a certain limit (e.g., equal to and less than $20) and a check card for transactions above a certain limit (e.g., over $20). In another example, transactions for nominal amounts (e.g., less than $7) may be applied to another payment mechanism, such as a token, stored value card, etc. Certain payment mechanisms may have more attractive interest rates, bonus arrangements and/or other considerations. In addition, a user may want to categorize certain payments for reimbursement through particular payment mechanisms. For all doctor related visits, a user may designate payment to be made to a debit card while all other transactions may be applied to a regular credit card. In yet another example, transactions at an identified merchant location may be applied to a merchant sponsored credit card while all other transactions are applied to another credit card.


Reimbursement Module 116 may receive data concerning how a user wants to be reimbursed. Reimbursement may be made to a specific account, against a credit card balance, as check or cash, to a retirement account, via payroll and/or other method for reimbursement. For example, as a savings mechanism, a user may designate a retirement account or other savings plan to receive reimbursements payments. In addition, users may designate one or more accounts or one or more reimbursements methods for receiving payments. Further, the user may designate certain reimbursements for one account and other reimbursements for another account. For example, for large reimbursement amounts (e.g., over $50), those reimbursements may be made into a retirement account while smaller amounts (e.g., $50 and under) may be made towards a credit card balance. Other arrangements may be specified, as desired by the user. Reimbursement Module 116 may also confirm that there are sufficient funds in a participating account (e.g., FSA, MSA, HRA or other consumer-directed account) from which funds may be reimbursed.


Eligibility Module 118 may determine whether each transaction or group of transactions is eligible for reimbursement. As payment is already made for the transaction through a designated payment mechanism, a determination of eligibility is performed at module 118. Claim eligibility may refer to determining whether the transaction qualifies for payment. For example, FSA (or other) payment may be restricted for certain types of transactions. For example, if the claim is associated with valid prescription drugs, such as antibiotics for an illness or other infection, the claim may be considered a valid medical expense. However, if the claim is for cosmetic purposes or other enhancements, such as certain anti-aging products, the claim may not be eligible for payment from the consumer-directed account. Each individual expense may be adjudicated against established guidelines (e.g., IRS guidelines) to determine eligibility. In addition, FSA (or other) sponsors, such as employers or Third Party Administrators, may add additional eligibility restrictions based on specific requirements of a particular FSA (or other consumer directed account) program. An employer may also impose additional restrictions for reimbursement. In addition, other restrictions may be applied in determining claim eligibility.


In determining eligibility, an embodiment of the present invention may receive claims data from a merchant entity or other entity from which a transaction has been made. For example, a data feed may be received from merchant 144 which provides information concerning each purchase. Other forms of data may be received and analyzed from other sources, such as credit card company, third party and/or other participant The information may be used to determine whether each purchase of a transaction is eligible or not. In addition, filters stored in database 130 may be used to identify eligible purchases. Other information may also be accessed.


An embodiment of the present invention may provide real time or batch claim substantiation to validate that a claim is for a valid purpose. Therefore, manual claim submission is unnecessary. Moreover, because authorization may be based on specific transaction-level data, there is no or minimal risk of non-compliance with guidelines (e.g., IRS guidelines) for the types of purchases that may be made through a consumer-directed account.


User Interface 120 may provide a user with access to various data concerning reimbursement of eligible transactions. For the health care accounts that are registered with a user's card product (e.g., a credit card, debit card, etc.), the user may view detailed transaction history, status of reimbursement and/or other information.


Billing Module 122 may manage charges and/or fees associated with various services provided by the embodiments of the present invention. For example, the cost of services may involve a flat fee of $X for a time period (e.g., per month, per quarter, per year, etc.) or a variable amount for a time period. For added convenience, the fee may be billed directly to a designated credit card (or other card product or payment mechanism). The payment may be made periodically, at certain events, or as directed by the user. The user may also have the fee deducted tax-free from the participating account (e.g., FSA, MSA, HRA, or other consumer-directed account). This may be established when the card product is registered or at a later time. Other fee arrangements and payment structures may be realized.


For a credit card application, because payments may be settled through a credit card network, substantiation may or may not be in real-time. As substantiation may not occur in real time, this approach is fundamentally different from stored value, and thus is not subject to stored value's challenges and limitations.


In accordance with an embodiment of the present invention non-compliant expenses are not made from a participating account, such as an FSA. In the example of a registered credit card, charges may be made to a credit account as a normal credit card transaction. After determining eligibility of each transaction, reimbursement may be made for those transactions that are positively substantiated through the data feed or other source of data or confirmation. As such, there is little or no concern regarding non-compliant reimbursement activity, employee delinquency in receipt submission or other impediment. According to this example, the employee pays the balance on his or her credit card or face the consequences (e.g., interest, adverse credit reporting, etc.). Therefore, the interests of all parties are therefore aligned and compliance is ensured.



FIG. 2 is an exemplary flowchart of a method for obtaining reimbursements for various transactions, according to an embodiment of the present invention. At step 210, a user may register with a system of an embodiment of the present invention. At step 212, the user may identify a payment mechanism. At step 214, the user may identify a reimbursement method. At step 216, the user may make purchases at various locations with the registered payment mechanism. At step 218, the user may receive reimbursement for the eligible purchases. While the process illustrated in FIG. 2 discloses certain steps performed in a particular order, it should be understood that the present invention may be practiced by adding one or more steps to the process, omitting steps within the process and/or altering the order in which one or more steps are performed.


At step 210, a user may register with a system of an embodiment of the present invention. Registration may occur with an employer, human resources department or other registration entity. Registration information may include user identification data, contact data, and/or other information. The user may register in person, online, by phone, by mail or other form of communication.


At step 212, the user may identify a payment mechanism. The payment mechanism may include a credit card, debit card, stored value card, token, checking account, savings account, and/or other manner of making a payment. The user may present the payment mechanism or provide a payment mechanism identifier for online purchases, for example. In addition, multiple payment mechanisms may be identified. Certain conditions may also be defined for triggering a particular payment mechanism. For example, for transactions over an amount may be charged to a credit card and other transactions may be charge to a different payment instrument.


At step 214, the user may identify a reimbursement method. The user may specify one or more methods of reimbursement for one or more identified payment mechanisms. For example, the user may identify reimbursement to a checking account, savings account, retirement fund and/or other account. The user may also specify that reimbursement is made towards a credit card (or other) balance. In addition, predetermined conditions for reimbursement may also be specified. For example, for purchases from a particular merchant (or type of merchant), reimbursement may be made to a user identified account. In another example, reimbursement amounts exceeding a dollar limit may be deposited into a savings account, while reimbursements of smaller value may be sent to the user as a check (e.g., regular check, paycheck, etc.). Other criteria may also be applied.


At step 216, the user may make purchases at various locations with the registered payment mechanism. The user may purchase eligible as well as ineligible services and/or products at various locations. For example, the user may visit a merchant and purchase groceries as well as pharmacy goods all with the registered payment mechanism. After the purchases are made, a system of an embodiment of the present invention may receive data to determine whether each product or service is eligible for reimbursement. Data may be received as a data feed from the merchant or other form of data. In addition, data may be received from a credit card company, third party and/or other participant. The data may identify line item data for each transaction, which may include a plurality of individual purchases. Data may include binary code, or other identifier that may be used to indicate what type of purchase was made. In addition, a system of an embodiment of the present invention may apply filters to the data to determine whether each individual purchase is eligible or not. Other methods for identifying eligible purchases may be applied as well.


At step 218, the user may receive reimbursement for the eligible purchases. Once eligibility determinations have been made to the transactions, the user may receive an authorized reimbursement amount by the identified reimbursement method. In addition, a determination of whether there are sufficient funds for reimbursement may also be made. For example, a user's FSA may have $40 while the eligible reimbursement amount is $50. In this example, a reimbursement of $40 may be made while the remaining $10 is applied to the purchase mechanism. Other arrangements may be applied. Therefore, the user is not required to submit documentation or other forms to verify eligible purchases for reimbursement.



FIG. 3 is an exemplary flowchart of a method for providing reimbursements for various transactions, according to an embodiment of the present invention. At step 310, a system of an embodiment of the present invention may register the user. At step 312, user payment mechanism data may be received. At step 314, user reimbursement method data may be received. At step 316, the payment mechanism may be activated for FSA functionality provided by an embodiment of the present invention. At step 318, a user transaction made with the payment mechanism may be identified. At step 320, data concerning the user transaction may be received from a merchant. At step 322, it may be determined whether one or more expenses from the user transaction is an eligible expense. If not, the expenses may be charged to the regular channels, at step 324. If the expenses are eligible, the user may be reimbursement through the preferred reimbursement method. While the process illustrated in FIG. 3 discloses certain steps performed in a particular order, it should be understood that the present invention may be practiced by adding one or more steps to the process, omitting steps within the process and/or altering the order in which one or more steps are performed.


At step 310, a system of an embodiment of the present invention may register the user. During registration, the user may provide identification data, contact data and other information. Communication between the user and the system may be performed via various modes of communication, including online interface, phone call, mail, electronic communication (e.g., email), wireless phone, etc.


At step 312, user payment mechanism data may be received. User specified payment mechanism data may include card identifier, password/PIN, type of payment mechanism (e.g., VISA™, Mastercard™, etc.), etc. Additional security information may also be collected (e.g., mother's maiden name, social security number, etc.). As discussed above, one or more payment mechanisms may be registered with an embodiment of the present invention. In addition, a participating account may be identified which may include FSA, MSA, HRA, other consumer-directed account and/or other account.


At step 314, user reimbursement method data may be received. As discussed above, the user may specify various reimbursement methods for receiving payment. In addition, reimbursement conditions may also be applied in depositing finds to one or more reimbursement accounts. Further, reimbursement conditions may apply to determine which reimbursement method to use depending on the purchase or transaction. Other specifics may be identified.


At step 316, the payment mechanism may be activated for reimbursement functionality provided by an embodiment of the present invention. After registration, a system of an embodiment of the present invention may enable the registered one or more payment mechanisms for use at various participating merchants and other venues.


At step 318, a user transaction made with the payment mechanism may be identified. When a transaction is made at a participating merchant, a system of an embodiment of the present invention may be notified or alerted. User transaction data may include merchant name, merchant location, time and day of purchase, type of purchase, purchase venue, and/or other data associated with the transaction. Based on relationships and/or other arrangements, data may be received from merchants, credit card companies, third parties and/or other participant.


At step 320, data concerning the user transaction may be received. Transaction data from participating merchants may be received. This data may be received from merchants, credit card companies, third parties and/or other participant. Transaction data may include line item data for identifying each purchase made during each transaction with the registered payment mechanism by the user. The line item data may be used to determine reimbursement eligibility. In another example, the transaction data may be submitted through one or more filters for identifying eligible purchases. Other methods for identifying eligible purchases may be applied as well.


At step 322, it may be determined whether one or more expenses from the user transaction is an eligible expense. If not, the expenses may be charged to the regular channels, at step 324. For example, a user may use a registered credit card to make a transaction at a participating merchant. The transactions may be charged to the credit card. For the purchases that are determined to be eligible, those purchases may be reimbursed through a preferred reimbursement method (e.g., towards the credit card balance, checking account, paycheck, etc.). For the remaining ineligible purchases, these purchases will be charged to the credit card used to make the transactions.



FIG. 4 is an exemplary diagram of a system for facilitating health care reimbursements, according to an embodiment of the present invention. User 410 may register a payment mechanism 420 with system 440 which provides reimbursement functionality of an embodiment of the present invention. In addition, user 410 may identify an account, such as Reimbursement account 412, to which fuids may be deposited. User 410 may also identify a participating account, such as FSA 414, from which reimbursements may be made. In this example, a user may contribute a predetermined amount of pre-taxed dollars from the user's payroll periodically to the participating account, e.g., FSA 414. Other payment mechanisms, reimbursement methods and participating accounts may be identified and applied in accordance with various other scenarios and applications. User 410 may use payment mechanism 420 to make various purchases at merchant locations 430, 432. Purchases may be made via Internet 422 or other venue. Merchant 430 may then forward transaction data that provides line item data. System 440 may use the line item data to determine whether each purchase of the transaction is eligible for reimbursement. Eligibility may be determined using filters, binary codes, data tables, data sets, and/or other method. Funds may be retrieved from a participating account, such as FSA, MSA, HRA, or other consumer-directed account, and reimbursed to the user through a preferred reimbursement method, in this example, to a reimbursement account 412.


Benefits and advantages may be realized by various embodiments of the present invention. For employees, submission of paper receipts and claim forms may be substantially reduced or eliminated, end-of-year forfeitures may be reduced, a need to front cash for payment (credit card float) may be reduced or eliminated, a need to carry a stored value card to enable FSA and HRA automation may be eliminated and attractiveness of FSA and HRA participation may be enhanced. For employers, significant employee benefits at little to no cost may be provided, automated FSA and HWA transactions compliance with plan rules may be enhanced, administrative costs may be reduced and FSA and HRA participation (which may further reduce FICA and lowers plan expenses) may be increased. For Third-Party Administrators, an embodiment of the present invention may differentiate TPA and their competitors, ensure automated FSA and HRA transactions are compliant with plan rules, reduce administrative costs, and increase FSA and HRA participation (e.g., TPA revenues are per-member, per-month, etc.). For participating merchants, advantages may include increased traffic to stores, increased sales volume, enhanced customer loyalty and/or other benefits. Other advantages may be realized for various participants.


The present invention is not to be limited in scope by the specific embodiments described herein. Indeed, various modifications of the present invention, in addition to those described herein, will be apparent to those of ordinary skill in the art from the foregoing description and accompanying drawings. Thus, such modifications are intended to fall within the scope of the following appended claims. Further, although the present invention has been described herein in the context of a particular implementation in a particular environment for a particular purpose, those of ordinary skill in the art will recognize that its usefulness is not limited thereto and that the present invention can be beneficially implemented in any number of environments for any number of purposes. Accordingly, the claims set forth below should be construed in view of the full breadth and spirit of the present invention as disclosed herein.

Claims
  • 1. A computer implemented method for facilitating reimbursements for eligible transactions, the computer implemented method comprising the steps of: registering a user for reimbursement through an interface wherein the user identifies one or more payment mechanisms and one or more reimbursement methods for purchases, prior to a user transaction;identifying the user transaction made with the one or more payment mechanisms at a provider wherein the user transaction comprises one or more purchases;receiving data regarding the user transaction;determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the data; andreimbursing the user for one or more eligible purchases via the one or more reimbursement methods.
  • 2. The method of claim 1, wherein at least one purchase is related to healthcare expenses.
  • 3. The method of claim 1, wherein at least one purchase is related to dependent care expenses.
  • 4. The method of claim 1, wherein at least one purchase is related to dental expenses.
  • 5. The method of claim 1, wherein at least one purchase is related to eye care expenses.
  • 6. The method of claim 1, wherein at least one purchase is related to transportation expenses.
  • 7. The method of claim 1, wherein the data is received as batch data feeds from the provider.
  • 8. The method of claim 7, wherein the batch data feeds comprise line-level transaction data for the user transaction.
  • 9. The method of claim 1, wherein the data comprises one or more of: type of product, type of service, price, purpose, product code, service code, date of purchase, time of purchase, merchant data, insurance entity data and credit card company data.
  • 10. The method of claim 1, wherein the data is from one or more merchants.
  • 11. The method of claim 1, wherein the data is from an insurance entity.
  • 12. The method of claim 1, wherein the data is from one or more of credit card company, pharmacy benefit manager and third party administrator.
  • 13. The method of claim 1, wherein the step of determining reimbursement eligibility further comprises the step of determining one or more sources of payment for at least a portion of the one or more eligible purchases.
  • 14. The method of claim 13, wherein the one or more sources comprise one or more of: an insurance entity, an employer associated with the user and a designated payment entity.
  • 15. The method of claim 1, wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
  • 16. The method of claim 1, wherein the reimbursement method is a direct payment to the user.
  • 17. The method of claim 16, wherein the direct payment comprises one or more of cash and check.
  • 18. The method of claim 1, further comprising the step of: determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases.
  • 19. The method of claim 18, wherein if the reimbursement account does not have sufficient funds to pay for the one or more eligible purchases, a remaining amount is applied to a payment mechanism.
  • 20. The method of claim 19, wherein the payment mechanism involves an extension of credit.
  • 21. A computer implemented method for facilitating reimbursements for eligible transactions, the computer implemented method comprising the steps of: identifying one or more payment mechanisms through an interface of a computer implemented reimbursement system;identifying one or more reimbursement methods through the interface of the computer implemented reimbursement system;making one or more purchases with the one or more identified payment mechanisms; andreceiving reimbursement for one or more eligible purchases via the one or more reimbursement methods;wherein the step of identifying one or more payment mechanisms and the step of identifying one or more reimbursement methods are performed prior to the step of making one or more purchases.
  • 22. The method of claim 21, wherein at least one purchase is related to healthcare expenses.
  • 23. The method of claim 21, wherein at least one purchase is related to dependent care expenses.
  • 24. The method of claim 21, wherein at least one purchase is related to dental expenses.
  • 25. The method of claim 21, wherein at least one purchase is related to eye care expenses.
  • 26. The method of claim 21, wherein at least one purchase is related to transportation expenses.
  • 27. The method of claim 21, wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
  • 28. The method of claim 21, wherein the one or more reimbursement methods comprises a direct payment to the user.
  • 29. The method of claim 28, wherein the direct payment comprises one or more of cash and check.
  • 30. The method of claim 21, further comprising the step of; determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases.
  • 31. The method of claim 30, wherein if the reimbursement account does not have sufficient funds to pay for the one or more eligible purchases, a remaining amount is applied to a payment mechanism.
  • 32. The method of claim 31, wherein the payment mechanism involves an extension of credit.
  • 33. A computer implemented system for facilitating reimbursements for eligible transactions, the computer implemented system comprising: register module for registering a user for reimbursement through an interface wherein the user identifies one or more payment mechanisms and one or more reimbursement methods for purchases, prior to a user transaction;payment module for identifying the user transaction made with the one or more payment mechanisms at a provider wherein the user transaction comprises one or more purchases and wherein data regarding the user transaction is received;eligibility module for determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the data; andreimbursement module for reimbursing the user for one or more eligible purchases via the one or more reimbursement methods.
  • 34. The system of claim 33, wherein at least one purchase is related to healthcare expenses.
  • 35. The system of claim 33, wherein at least one purchase is related to dependent care expenses.
  • 36. The system of claim 33, wherein at least one purchase is related to dental expenses.
  • 37. The system of claim 33, wherein at least one purchase is related to eye care expenses.
  • 38. The system of claim 33, wherein at least one purchase is related to transportation expenses.
  • 39. The system of claim 33, wherein the data is received as batch data feeds from the provider.
  • 40. The system of claim 39, wherein the batch data feeds comprise line-level transaction data for the user transaction.
  • 41. The system of claim 33, wherein the data comprises one or more of: type of product, type of service, price, purpose, product code, service code, date of purchase, time of purchase, merchant data, insurance entity data and credit card company data.
  • 42. The system of claim 33, wherein the data is from one or more merchants.
  • 43. The system of claim 33, wherein the data is from an insurance entity.
  • 44. The system of claim 33, wherein the data is from one or more of credit card company, pharmacy benefit manager and third party administrator.
  • 45. The system of claim 33, wherein the eligibility module further determines one or more sources of payment for at least a portion of the one or more eligible purchases.
  • 46. The system of claim 45, wherein the one or more sources comprise one or more of: an insurance entity, an employer associated with the user and a designated payment entity.
  • 47. The system of claim 33, wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
  • 48. The system of claim 33, wherein the reimbursement method is a direct payment to the user.
  • 49. The system of claim 48, wherein the direct payment comprises one or more of cash and check.
  • 50. The system of claim 33, wherein the eligibility module determines whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases.
  • 51. The system of claim 50, wherein if the reimbursement account does not have sufficient funds to pay for the one or more eligible purchases, a remaining amount is applied to a payment mechanism.
  • 52. The system of claim 51, wherein the payment mechanism involves an extension of credit.
  • 53. A computer implemented system for facilitating reimbursements for a user for eligible transactions, the computer implemented system comprising: payment module for identifying one or more payment mechanisms through an interface of a computer implemented reimbursement system; andreimbursement module for identifying one or more reimbursement methods through the interface of the computer implemented reimbursement system;wherein the user makes one or more purchases with the one or more identified payment mechanisms and the user receives reimbursement for one or more eligible purchases via the one or more reimbursement methods; wherein the user identifies one or more payment mechanisms and one or more reimbursement methods prior to making one or more purchases.
  • 54. The system of claim 53, wherein at least one purchase is related to healthcare expenses.
  • 55. The system of claim 53, wherein at least one purchase is related to dependent care expenses.
  • 56. The system of claim 53, wherein at least one purchase is related to dental expenses.
  • 57. The system of claim 53, wherein at least one purchase is related to eye care expenses.
  • 58. The system of claim 53, wherein at least one purchase is related to transportation expenses.
  • 59. The system of claim 53, wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
  • 60. The system of claim 53, wherein the one or more reimbursement methods comprises a direct payment to the user.
  • 61. The system of claim 60, wherein the direct payment comprises one or more of cash and check.
  • 62. The system of claim 53, wherein the reimbursement module determines whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases.
  • 63. The system of claim 62, wherein if the reimbursement account does not have sufficient funds to pay for the one or more eligible purchases, a remaining amount is applied to a payment mechanism.
  • 64. The system of claim 63, wherein the payment mechanism involves an extension of credit.
  • 65. A computer implemented method for facilitating reimbursements for eligible transactions, the computer implemented method comprising the steps of: registering a user for reimbursement through an interface wherein the user identifies one or more payment mechanisms and one or more reimbursement methods for purchases, prior to a user transaction;identifying the user transaction made with the one or more payment mechanisms at a provider wherein the user transaction comprises one or more purchases;receiving data regarding the user transaction;determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the data;determining one or more sources of payment for at least a portion of the one or more eligible purchases; wherein the one or more sources comprise one or more of: an insurance entity, an employer associated with the user and a designated payment entity;determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases; andreimbursing the user for one or more eligible purchases via the one or more reimbursement methods;wherein at least one purchase is related to one or more of healthcare expenses, dependent care expenses, dental expenses, eye care expenses, transportation expenses.
  • 66. A computer implemented method for facilitating reimbursements for eligible transactions, the computer implemented method comprising the steps of: identifying one or more payment mechanisms through an interface of a computer implemented reimbursement system;identifying one or more reimbursement methods through the interface of the computer implemented reimbursement system;making one or more purchases with the one or more identified payment mechanisms;determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases; andreceiving reimbursement for one or more eligible purchases via the one or more reimbursement methods;wherein the step of identifying one or more payment mechanisms and the step of identifying one or more reimbursement methods are performed prior to the step of making one or more purchases;wherein at least one purchase is related to one or more of: healthcare expenses; dependent care expenses; dental expenses; eye care expenses; and transportation expenses;wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
  • 67. A computer implemented system for facilitating reimbursements for eligible transactions, the computer implemented system comprising: register module for registering a user for reimbursement through an interface wherein the user identifies one or more payment mechanisms and one or more reimbursement methods for purchases, prior to a user transaction;payment module for identifying the user transaction made with the one or more payment mechanisms at a provider wherein the user transaction comprises one or more purchases and wherein data regarding the user transaction is received;eligibility module for determining reimbursement eligibility of the one or more purchases of the user transaction based at least in part on the data; determining one or more sources of payment for at least a portion of the one or more eligible purchases, wherein the one or more sources comprise one or more of: an insurance entity, an employer associated with the user and a designated payment entity; and determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases; andreimbursement module for reimbursing the user for one or more eligible purchases via the one or more reimbursement methods;wherein at least one purchase is related to one or more of healthcare expenses, dependent care expenses, dental expenses, eye care expenses, and transportation expenses.
  • 68. A computer implemented system for facilitating reimbursements for a user for eligible transactions, the computer implemented system comprising: payment module for identifying one or more payment mechanisms through an interface of a computer implemented reimbursement system; andreimbursement module for identifying one or more reimbursement methods through the interface of the computer implemented reimbursement system and determining whether a reimbursement account has sufficient funds to pay for the one or more eligible purchases;wherein the user makes one or more purchases with the one or more identified payment mechanisms and the user receives reimbursement for one or more eligible purchases via the one or more reimbursement methods; wherein the user identifies one or more payment mechanisms and one or more reimbursement methods prior to making one or more purchases;wherein at least one purchase is related to one or more of: healthcare expenses; dependent care expenses; dental expenses; eye care expenses; and transportation expenses;wherein at least a partial payment of the one or more eligible purchases is made by an insurance entity.
RELATED APPLICATIONS

This patent application is a Continuation of U.S. patent application Ser. No. 11/065,029 filed Feb. 25, 2005, now. U.S. Pat. No. 7,380,707, issued Jun. 3, 2008 and claims Priority to U.S. Provisional Application No. 60/547,074 filed Feb. 25, 2004, which are hereby incorporated by reference herein in their entirety. The present application claims priority to U.S. Provisional Patent Application No. 60/547,074, filed Feb. 25, 2004, which is hereby incorporated by reference herein in its entirety.

US Referenced Citations (392)
Number Name Date Kind
3653480 Yamamoto et al. Apr 1972 A
4050375 Orleans Sep 1977 A
4141078 Bridges et al. Feb 1979 A
4205780 Burns et al. Jun 1980 A
4264808 Owens et al. Apr 1981 A
4321672 Braun et al. Mar 1982 A
4396985 Ohara Aug 1983 A
RE31692 Tyburski et al. Oct 1984 E
4495018 Vohrer Jan 1985 A
4617457 Myers et al. Oct 1986 A
4672377 Murphy Jun 1987 A
4694397 Grant et al. Sep 1987 A
4700055 Kashkashian, Jr. Oct 1987 A
4713761 Sharpe et al. Dec 1987 A
4752877 Roberts et al. Jun 1988 A
4797913 Kaplan Jan 1989 A
4799156 Shavit Jan 1989 A
4807177 Ward Feb 1989 A
4812628 Boston Mar 1989 A
4823264 Deming Apr 1989 A
4893333 Baran et al. Jan 1990 A
4931793 Fuhrmann et al. Jun 1990 A
4939674 Price et al. Jul 1990 A
4948174 Thomson et al. Aug 1990 A
4974878 Josephson Dec 1990 A
4975841 Kehnemuyi et al. Dec 1990 A
4988849 Sasaki Jan 1991 A
4992646 Collin Feb 1991 A
4992940 Dworkin Feb 1991 A
5023904 Kaplan Jun 1991 A
5053607 Carlson Oct 1991 A
5054096 Beizer Oct 1991 A
5080748 Bonomi Jan 1992 A
5111395 Smith May 1992 A
5121945 Thomson et al. Jun 1992 A
5122950 Mee et al. Jun 1992 A
5136502 Van Remortel et al. Aug 1992 A
5175682 Higashiyama Dec 1992 A
5187750 Behera Feb 1993 A
5198975 Baker et al. Mar 1993 A
5220501 Lawlor Jun 1993 A
5225978 Peterson Jul 1993 A
5237159 Stephens Aug 1993 A
5265007 Barnhard, Jr. et al. Nov 1993 A
5283829 Anderson Feb 1994 A
5287269 Dorrough et al. Feb 1994 A
5311594 Penzias May 1994 A
5315508 Bain et al. May 1994 A
5321238 Watanabe et al. Jun 1994 A
5326959 Perazza Jul 1994 A
5336870 Hughes Aug 1994 A
5349170 Kern Sep 1994 A
5350906 Brody et al. Sep 1994 A
5367581 VanHom et al. Nov 1994 A
5373550 Campbell Dec 1994 A
5396417 Burks Mar 1995 A
5402474 Miller Mar 1995 A
5412190 Kopesec et al. May 1995 A
5424938 Wagner Jun 1995 A
5430644 Deaton et al. Jul 1995 A
5432506 Chapman Jul 1995 A
5444794 Uhland Aug 1995 A
5444841 Glasser et al. Aug 1995 A
5446740 Yien Aug 1995 A
5448471 Deaton et al. Sep 1995 A
5459482 Orlen Oct 1995 A
5465206 Hilt et al. Nov 1995 A
5477040 Lalonde Dec 1995 A
5479494 Clitherow Dec 1995 A
5483445 Pickering Jan 1996 A
5484988 Hills Jan 1996 A
5502576 Ramsay et al. Mar 1996 A
5504677 Pollin Apr 1996 A
5506691 Bednar et al. Apr 1996 A
5508731 Kohorn Apr 1996 A
5513250 McAllister Apr 1996 A
5532464 Josephson et al. Jul 1996 A
5544043 Miki et al. Aug 1996 A
5544046 Niwa Aug 1996 A
5550734 Tater Aug 1996 A
5551021 Harada Aug 1996 A
5557515 Abbruzzese et al. Sep 1996 A
5563400 Le Roux Oct 1996 A
5566330 Sheffield Oct 1996 A
5568489 Yien Oct 1996 A
5570465 Tsakanikas Oct 1996 A
5572004 Raimann Nov 1996 A
5583759 Geer Dec 1996 A
5583760 Klesse Dec 1996 A
5590196 Moreau Dec 1996 A
5590197 Chen Dec 1996 A
5592377 Lipkin Jan 1997 A
5592378 Cameron Jan 1997 A
5599528 Igaki Feb 1997 A
5603025 Tabb Feb 1997 A
5615109 Eder Mar 1997 A
5621201 Langhans Apr 1997 A
5640577 Scharmer Jun 1997 A
5642419 Rosen Jun 1997 A
5649117 Landry Jul 1997 A
5652786 Rogers Jul 1997 A
5659165 Jennings Aug 1997 A
5659469 Deaton et al. Aug 1997 A
5659741 Eberhardt Aug 1997 A
5666493 Wojcik et al. Sep 1997 A
5677955 Doggett et al. Oct 1997 A
5679938 Templeton Oct 1997 A
5679940 Templeton Oct 1997 A
5687250 Curley et al. Nov 1997 A
5692132 Hogan Nov 1997 A
5699528 Hogan Dec 1997 A
5703344 Bezy et al. Dec 1997 A
5704044 Tarter et al. Dec 1997 A
5708422 Blonder et al. Jan 1998 A
5715298 Rogers Feb 1998 A
5715314 Payne Feb 1998 A
5715399 Bezos Feb 1998 A
5717989 Tozzoli et al. Feb 1998 A
5724424 Gifford Mar 1998 A
5727153 Powell Mar 1998 A
5748780 Stolfo May 1998 A
5751842 Eccles et al. May 1998 A
5757917 Rose et al. May 1998 A
5770843 Rose et al. Jun 1998 A
5774553 Rosen Jun 1998 A
5783808 Josephson Jul 1998 A
5784696 Melnikof Jul 1998 A
5793861 Haigh Aug 1998 A
5794221 Egendorf Aug 1998 A
5802498 Comesanas Sep 1998 A
5802499 Sampson et al. Sep 1998 A
5819236 Josephson Oct 1998 A
5819238 Fernholz Oct 1998 A
5826241 Stein Oct 1998 A
5826245 Sandberg-Diment Oct 1998 A
5832447 Rieker Nov 1998 A
5832460 Bednar Nov 1998 A
5832464 Houvener et al. Nov 1998 A
5832488 Eberhardt Nov 1998 A
5835580 Fraser Nov 1998 A
5835603 Coutts Nov 1998 A
5835899 Rose et al. Nov 1998 A
5852812 Reeder Dec 1998 A
5859419 Wynn Jan 1999 A
5864609 Cross et al. Jan 1999 A
5870456 Rogers Feb 1999 A
5870721 Norris Feb 1999 A
5870723 Pare Feb 1999 A
5870725 Belinger et al. Feb 1999 A
5873072 Kight Feb 1999 A
5878141 Daly et al. Mar 1999 A
5883810 Franklin et al. Mar 1999 A
5884288 Chang Mar 1999 A
5884290 Smorodinsky et al. Mar 1999 A
5897625 Gustin Apr 1999 A
5898157 Mangili et al. Apr 1999 A
5903881 Schrader May 1999 A
5910896 Hahn-Carlson Jun 1999 A
5910988 Ballard Jun 1999 A
5915246 Patterson et al. Jun 1999 A
5917965 Cahill et al. Jun 1999 A
5920847 Kolling et al. Jul 1999 A
5930778 Geer Jul 1999 A
5940811 Norris Aug 1999 A
5940844 Cahill et al. Aug 1999 A
5943656 Crooks Aug 1999 A
5945653 Walker et al. Aug 1999 A
5956700 Landry Sep 1999 A
5963659 Cahill et al. Oct 1999 A
5963925 Kolling et al. Oct 1999 A
5966698 Pollin Oct 1999 A
5978780 Watson Nov 1999 A
5987435 Weiss et al. Nov 1999 A
5987436 Halbrook Nov 1999 A
5987439 Gustin et al. Nov 1999 A
5991750 Watson Nov 1999 A
6000832 Franklin et al. Dec 1999 A
6003762 Hayashida Dec 1999 A
6006208 Forst et al. Dec 1999 A
6009442 Chen et al. Dec 1999 A
6014636 Reeder Jan 2000 A
6016482 Molinari et al. Jan 2000 A
6016484 Williams et al. Jan 2000 A
6018718 Walker et al. Jan 2000 A
6026388 Liddy et al. Feb 2000 A
6029139 Cunningham et al. Feb 2000 A
6032133 Hilt et al. Feb 2000 A
6032137 Ballard Feb 2000 A
6035281 Crosskey et al. Mar 2000 A
6035285 Schlect et al. Mar 2000 A
6035287 Stallaert et al. Mar 2000 A
6038553 Hyde, Jr. Mar 2000 A
6041312 Bickerton et al. Mar 2000 A
6041315 Pollin Mar 2000 A
6044362 Neely Mar 2000 A
6045039 Stinson et al. Apr 2000 A
6047261 Siefert Apr 2000 A
6052674 Zervides et al. Apr 2000 A
6058380 Anderson et al. May 2000 A
6058381 Nelson May 2000 A
6061665 Bahreman May 2000 A
6064764 Bhaskaran et al. May 2000 A
6064987 Walker et al. May 2000 A
6065675 Teicher May 2000 A
6067524 Byerly et al. May 2000 A
6070150 Remington et al. May 2000 A
6070798 Nethery Jun 2000 A
6073104 Field Jun 2000 A
6073113 Guinan Jun 2000 A
6076072 Libman Jun 2000 A
6078907 Lamm Jun 2000 A
6081790 Rosen Jun 2000 A
6085168 Mori et al. Jul 2000 A
6088683 Jalili Jul 2000 A
6088685 Kiron et al. Jul 2000 A
6088686 Walker et al. Jul 2000 A
6092056 Tull, Jr. et al. Jul 2000 A
6098053 Slater Aug 2000 A
6098070 Maxwell Aug 2000 A
6105011 Morrison, Jr. Aug 2000 A
6108639 Walker et al. Aug 2000 A
6110044 Stern Aug 2000 A
6111858 Greaves et al. Aug 2000 A
6115690 Wong Sep 2000 A
6119106 Mersky et al. Sep 2000 A
6119107 Polk Sep 2000 A
6125354 MacFarlane et al. Sep 2000 A
6128602 Northington et al. Oct 2000 A
6128603 Dent et al. Oct 2000 A
6129273 Shah Oct 2000 A
6138118 Koppstein et al. Oct 2000 A
6144946 Iwamura Nov 2000 A
6148293 King Nov 2000 A
6149055 Gatto Nov 2000 A
6149056 Stinson et al. Nov 2000 A
6173272 Thomas et al. Jan 2001 B1
6181837 Cahill et al. Jan 2001 B1
6185544 Sakamoto et al. Feb 2001 B1
6202054 Lawlor et al. Mar 2001 B1
6205433 Boesch et al. Mar 2001 B1
6213391 Lewis Apr 2001 B1
6227447 Campisano May 2001 B1
6233565 Lewis et al. May 2001 B1
6233566 Levine et al. May 2001 B1
6236972 Shkedy May 2001 B1
6240444 Fin et al. May 2001 B1
6278981 Dembo et al. Aug 2001 B1
6289322 Kitchen et al. Sep 2001 B1
6292789 Schutzer Sep 2001 B1
6301379 Thompson et al. Oct 2001 B1
6301567 Leong et al. Oct 2001 B1
6304858 Mosler et al. Oct 2001 B1
6321212 Lange Nov 2001 B1
6324524 Lent et al. Nov 2001 B1
6338047 Wallman Jan 2002 B1
6338049 Walker et al. Jan 2002 B1
6343279 Bissonette et al. Jan 2002 B1
6363164 Jones et al. Mar 2002 B1
6363364 Nel Mar 2002 B1
6363365 Kou Mar 2002 B1
6366967 Wagner Apr 2002 B1
6374235 Chen et al. Apr 2002 B1
6390362 Martin May 2002 B1
6393409 Young et al. May 2002 B2
6405173 Honarvar et al. Jun 2002 B1
6415259 Wolfinger et al. Jul 2002 B1
6418419 Nieboer et al. Jul 2002 B1
6418420 DiGiorgio et al. Jul 2002 B1
6418430 DeFazio et al. Jul 2002 B1
6434159 Woodward et al. Aug 2002 B1
6446072 Schulze et al. Sep 2002 B1
6460020 Pool et al. Oct 2002 B1
6490568 O'Mara et al. Dec 2002 B1
6493685 Ensel et al. Dec 2002 B1
6535896 Britton et al. Mar 2003 B2
6536663 Lozier et al. Mar 2003 B1
6554185 Montross et al. Apr 2003 B1
6574350 Rhoads et al. Jun 2003 B1
6574377 Cahill et al. Jun 2003 B1
6578000 Dodrill et al. Jun 2003 B1
6578015 Haseltine et al. Jun 2003 B1
6609113 O'Leary et al. Aug 2003 B1
6609125 Layne et al. Aug 2003 B1
6629081 Cornelius et al. Sep 2003 B1
6636615 Rhoads et al. Oct 2003 B1
6658393 Basch et al. Dec 2003 B1
6661910 Jones et al. Dec 2003 B2
6704714 O'Leary et al. Mar 2004 B1
6721715 Nemzow Apr 2004 B2
6728397 McNeal Apr 2004 B2
6820058 Wood et al. Nov 2004 B2
6825940 Wu et al. Nov 2004 B1
6860375 Hallowell et al. Mar 2005 B2
6954896 Dodrill et al. Oct 2005 B1
6965882 Lapstun et al. Nov 2005 B1
6970259 Lunt et al. Nov 2005 B1
6970855 Das et al. Nov 2005 B2
RE38957 Laussermair et al. Jan 2006 E
7004382 Sandru Feb 2006 B2
7062456 Riehl et al. Jun 2006 B1
7068832 Price et al. Jun 2006 B1
7104443 Paul et al. Sep 2006 B1
7133846 Ginter et al. Nov 2006 B1
7177836 German et al. Feb 2007 B1
7194437 Britto et al. Mar 2007 B1
7200255 Jones et al. Apr 2007 B2
7313543 Crane et al. Dec 2007 B1
7317823 Price et al. Jan 2008 B1
7337148 Xie et al. Feb 2008 B2
7349884 Odom Mar 2008 B1
7380707 Fredman Jun 2008 B1
7401048 Rosedale et al. Jul 2008 B2
20010011222 McLauchlin et al. Aug 2001 A1
20010018666 Sugiyama et al. Aug 2001 A1
20010018739 Anderson et al. Aug 2001 A1
20010032139 Debonnet, Jr. Oct 2001 A1
20010037300 Miyazaki et al. Nov 2001 A1
20010037309 Vrain Nov 2001 A1
20010047334 Nappe et al. Nov 2001 A1
20010047489 Ito et al. Nov 2001 A1
20010051533 Wietzke et al. Dec 2001 A1
20020012445 Perry Jan 2002 A1
20020013728 Wilkman Jan 2002 A1
20020023055 Antognini et al. Feb 2002 A1
20020026394 Savage et al. Feb 2002 A1
20020038363 MacLean Mar 2002 A1
20020046169 Keresman et al. Apr 2002 A1
20020052842 Schuba et al. May 2002 A1
20020055907 Pater et al. May 2002 A1
20020069134 Solomon Jun 2002 A1
20020072976 Virtanen et al. Jun 2002 A1
20020077978 O'Leary et al. Jun 2002 A1
20020082985 MacKay Jun 2002 A1
20020087415 Allen et al. Jul 2002 A1
20020087468 Ganesan et al. Jul 2002 A1
20020087469 Ganesan et al. Jul 2002 A1
20020091635 Dilip et al. Jul 2002 A1
20020100803 Sehr Aug 2002 A1
20020107770 Meyer et al. Aug 2002 A1
20020107788 Cunningham Aug 2002 A1
20020111837 Aupperle Aug 2002 A1
20020128981 Kawan et al. Sep 2002 A1
20020138398 Kalin et al. Sep 2002 A1
20020169658 Adler Nov 2002 A1
20020170966 Hannigan et al. Nov 2002 A1
20020178071 Walker et al. Nov 2002 A1
20020184151 Maloney Dec 2002 A1
20020194096 Falcone et al. Dec 2002 A1
20020198817 Dhir Dec 2002 A1
20020199182 Whitehead Dec 2002 A1
20030018557 Gilbert et al. Jan 2003 A1
20030037002 Higgins et al. Feb 2003 A1
20030040959 Fei et al. Feb 2003 A1
20030046218 Albanese et al. Mar 2003 A1
20030055675 Klein Twennaar Mar 2003 A1
20030069780 Hailwood et al. Apr 2003 A1
20030097335 Muskowitz et al. May 2003 A1
20030105641 Lewis Jun 2003 A1
20030110442 Battle Jun 2003 A1
20030120686 Kim et al. Jun 2003 A1
20030130945 Force et al. Jul 2003 A1
20030130952 Bell et al. Jul 2003 A1
20030144942 Sobek Jul 2003 A1
20030187789 Karas et al. Oct 2003 A1
20030191710 Green et al. Oct 2003 A1
20030200107 Allen et al. Oct 2003 A1
20030208421 Vicknair et al. Nov 2003 A1
20030208441 Poplawski et al. Nov 2003 A1
20030225663 Horan et al. Dec 2003 A1
20030233305 Solomon Dec 2003 A1
20030237046 Parker et al. Dec 2003 A1
20040064409 Kight et al. Apr 2004 A1
20040078328 Talbert et al. Apr 2004 A1
20040133516 Buchanan et al. Jul 2004 A1
20040201735 Baron Oct 2004 A1
20040228514 Houle et al. Nov 2004 A1
20050033690 Antognini et al. Feb 2005 A1
20050055254 Schmidtberg et al. Mar 2005 A1
20050086178 Xie et al. Apr 2005 A1
20050091156 Hailwood et al. Apr 2005 A1
20050144059 Schuessler Jun 2005 A1
20050177480 Huang Aug 2005 A1
20050209954 Asher et al. Sep 2005 A1
20050261955 Humble et al. Nov 2005 A1
20060106650 Bush et al. May 2006 A1
20060106717 Randle et al. May 2006 A1
20060136335 Ferguson, III Jun 2006 A1
20060178986 Giordano et al. Aug 2006 A1
20060206427 Love et al. Sep 2006 A1
20060282389 Gupte Dec 2006 A1
20060287953 Chauhan Dec 2006 A1
20080193008 Mount et al. Aug 2008 A1
Foreign Referenced Citations (17)
Number Date Country
0099999 Jul 1983 EP
421808 Apr 1991 EP
1014318 Jun 2000 EP
WO 9745796 Apr 1991 WO
WO 9116691 Oct 1991 WO
WO 9308545 Apr 1993 WO
WO 9428497 Dec 1994 WO
WO 9608783 Mar 1996 WO
WO 9612242 Apr 1996 WO
WO 9714108 Apr 1997 WO
WO 9745814 Dec 1997 WO
WO 9809260 Mar 1998 WO
WO 9910823 Mar 1999 WO
WO 0039979 Jul 2000 WO
WO 0175730 Oct 2001 WO
WO 02063432 Aug 2002 WO
WO 2004079603 Sep 2004 WO
Related Publications (1)
Number Date Country
20080228641 A1 Sep 2008 US
Provisional Applications (1)
Number Date Country
60547074 Feb 2004 US
Continuations (1)
Number Date Country
Parent 11065029 Feb 2005 US
Child 12131302 US