Funds transfer method and system including payment enabled invoices

• US 20080015982A1
• Filed: 07/19/2007
• Published: 01/17/2008
• Est. Priority Date: 09/20/2000
• Status: Abandoned Application

• Current Assignee: CashEdge Incorporated (Fiserv Incorporated)
• Original Assignee: CashEdge Incorporated (Fiserv Incorporated)
• Inventors: Panthaki, Behram, Rudenstine, Aaron, Sattar, Azeem, Dheer, Sanjeev, Sokolic, Jeremy
• Application Number:
  US11/879,818
• Publication Number:
  US 20080015982A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Embodiments described herein include a financial management system that transfers funds on behalf of a user. Embodiments further include a payment enabled invoice method and system including a payment application and payment hubs through which invoicing entities may create and modify invoices, and through which a payer may view and pay the invoices. The invoicing entity and the payer do not exchange financial account information, which is confidentially held by the payment enabled invoice system. Invoices are paid according to funds transfer embodiments, wherein a transfer comprises the financial management system executing a debit transaction from a first financial institution, holding the debited funds in an intermediary account owned by the financial management system at a second financial institution, and executing a credit transaction to credit the funds to an account at a third financial institution.

Claims

1. A financial management method, comprising:

receiving an input from an invoicing entity accessing a financial management system via an invoicing user interface (UI) to create a payer, wherein a payer owes an outstanding balance to the invoicing entity;

via the invoicing UI, receiving a request to create an invoice, wherein creating an invoice comprises setting payment terms on the invoice, wherein the invoice states an amount comprising at least part of the outstanding balance;

via the invoicing UI, receiving a destination account to associate with the invoice, wherein the destination account is an account designated to receive funds to be credited against the invoice;

posting the invoice to at least one payment hub, and storing the invoice in an invoice database;

receiving payer account data input from a payer accessing the at least one payment hub via a payment hub UI, wherein the payer account data includes access information for at least one payer financial account;

via the payment hub UI, receiving a selection one of the at least one payer financial account for funding payment of the invoice;

via the payment hub UI, receiving payer direction to pay the invoice;

paying the invoice, comprising executing a transfer of funds from the payment account to the destination account; and

updating the invoice to reflect payment of the invoice.

2. The method of claim 1, wherein payment terms comprise:

a time for paying the invoice;

discounts to be applied to the invoice;

circumstances under which to apply the discounts;

penalties to be applied to the invoice; and

circumstances under which to apply the penalties.

3. The method of claim 1, further comprising displaying the invoice to the payer, including automatically updating one or more of discounts and penalties based on the payment terms.

4. The method of claim 1, further comprising:

automatically updating one or more of discounts and penalties based on the payment terms and current date; and

storing the updated invoice in the invoice database.

5. The method of claim 1, further comprising:

storing the invoice as a template; and

receiving an input from the invoicing entity selecting the template for modification.

6. The method of claim 1, further comprising:

receiving input from the invoicing entity comprising a schedule of recurring invoicing events associated with at least one invoice;

automatically generating the at least one invoice according to the schedule, including updating the invoice; and

making the at least one invoice available on the at least one payment hub.

7. The method of claim 1, further comprising:

receiving input from the invoicing entity comprising a schedule of recurring invoicing events associated with at least one invoice;

storing the invoice as a template; and

automatically generating the at least one invoice according to the schedule, including updating the invoice.

8. The method of claim 1, further comprising generating an aggregate invoice based on the invoice and past invoices, wherein the aggregate invoice combines amounts due from the invoice and from past invoices.

9. The method of claim 1, further comprising generating an aging report based on the invoice and past invoices.

10. The method of claim 1, further comprising generating a statement based on the invoice and past invoices.

11. The method of claim 1, further comprising:

receiving a request from the payer to view at least one additional invoice other than the invoice; and

displaying the invoice and the at least one additional invoice on the payer UI.

12. The method of claim 11, further comprising:

receiving a selection of at least one payment account from which to pay selected ones of the displayed invoices; and

initiating payment of selected ones of the displayed invoices as indicated by the selection.

13. The method of claim 11, further comprising:

receiving at least one payment amount to be applied to at least one of the displayed invoices; and

initiating payment of the at least one of the displayed invoices as indicated by the at least one payment amount, wherein payment comprises,

full payment of each displayed invoice from different selected payment accounts;

full payment of all of the displayed invoices from one of the selected payment accounts; and

partial payment of the displayed invoices from at least one of the selected payment accounts.

14. The system of claim 1, further comprising automatically generating electronic communications to the payer comprising:

notifications of new invoices;

alerts regarding payment terms; and

payment confirmations.

15. The system of claim 1, wherein the payer account data further comprises payer registration information, and wherein the payer registration information is stored in the system for recognizing the payer on subsequent accesses of the at least one payment hub.

16. The method of claim 1, further comprising:

presenting the payer with a quick pay option;

receiving a selection of the quick pay option;

receiving the payer account data, wherein the at least one payer financial account includes one payer financial account;

initiating payment of the invoice from the one payer account; and

purging the payer account data.

17. The method of claim 1, wherein the invoice comprises a payment enabled settlement statement.

18. The method of 17 wherein the settlement statement comprises a payment enabled medical insurance explanation of benefits (EOB).

19. A system, comprising:

a financial management system coupled to a plurality of financial institutions via at least one network, the financial management system configurable to execute a debit transaction with one of the financial institutions and to execute a credit transaction with another one of the financial institutions, wherein the debit transaction and the credit transaction are parts of a same transaction;

an invoicing application module coupled to the financial management system, the invoicing application module comprising at least one invoicing user interface (UI) via which an invoicing entity registers a payer and creates an invoice for the payer;

at least one payment hub coupled to the invoicing application module and to the financial management system, the at least one payment hub comprising at least one payment hub UI via which a payer accesses and views the invoice and directs payment from an account; and

wherein the financial management system is further configurable to pay the invoice, including executing the debit transaction and executing the credit transaction, and to update the invoice to reflect payment.

20. The system of claim 19, wherein the financial management system comprises an invoice database that stores invoices created by a plurality of invoicing entities via different invoicing UIs.

21. The system of claim 19, wherein the at least one payment hub is configured by an institution to appear with branding of the institution, and wherein the at least one payment hub UI is accessed via a web site administered by the institution.

22. The system of claim 21, wherein a payer accessing the at least one payment hub can view invoices from any of the plurality of invoicing entities.

23. The system of claim 19, wherein the at least one payment hub is configured by an invoicing entity to appear with branding of at least one of a plurality of invoicing entities, and wherein the at least one payment hub UI is accessed via a web site administered by an institution on behalf of the plurality of invoicing entities.

24. The system of claim 23, wherein a payer accessing the at least one payment hub can view invoices from any of the plurality of invoicing entities.

25. The system of claim 19, wherein the at least one payment hub is configured by an invoicing entity to appear with branding of the invoicing entity, and wherein the at least one payment hub UI is accessed via a web site administered by the invoicing entity.

26. The system of claim 25, wherein a payer accessing the at least one payment hub can view invoices from the invoicing entity.

27. A financial management system, comprising:

at least one coupling to a plurality of financial institutions via at least one network, wherein the financial management system is configurable to execute a debit transaction with one of the financial institutions and to execute a credit transaction with another one of the financial institutions, wherein the debit transaction and the credit transaction are parts of a same transaction;

an invoicing application module coupled to the financial management system, the invoicing application module comprising at least one invoicing user interface (UI) via which an invoicing entity registers a payer and creates an invoice for the payer;

at least one payment hub coupled to the invoicing application module and to the financial management system, the at least one payment hub comprising at least one payment hub UI via which a payer accesses and views the invoice and directs payment from an account; and

wherein the financial management system is further configurable to pay the invoice, including executing the debit transaction and executing the credit transaction, and to update the invoice to reflect payment.

28. The system of claim 27, wherein the financial management system comprises an invoice database that stores invoices created by a plurality of invoicing entities via different invoicing UIs.

29. The system of claim 28, wherein the at least one payment hub is configured by an invoicing entity to appear with branding of at least one of a plurality of invoicing entities, and wherein the at least one payment hub UI is accessed via at least one web site administered by at least one institution on behalf of the plurality of invoicing entities.

30. The system of claim 29, wherein a payer accessing the at least one payment hub can view invoices stored on the invoicing database from any of the plurality of invoicing entities.

31. An invoicing user interface method, comprising:

providing a plurality of invoicing user interfaces to a plurality of invoicing entities;

receiving data to create invoices from the plurality of invoicing entities, wherein the data comprises payment terms and payment amounts;

making the invoices available to a plurality of payers;

receiving data from the plurality of payers, including direction to pay invoices; and

updating the invoices in real time in response to data received from the plurality of invoicing entities and data received from the plurality of payers.

32. A payment hub user interface method, comprising:

providing a plurality of payment hubs to a plurality of payers, wherein the plurality of payment hubs are coupled to an invoice database storing invoices;

receiving requests via a payment hub user interface to,

view invoices, comprising current and aged invoices from at least one invoicing entity; and

pay invoices; and

executing the received requests; and

updating invoices in real time based on executed requests.