ELECTRONIC INVOICING AND PAYMENT

• US 20140337188A1
• Filed: 05/09/2013
• Published: 11/13/2014
• Est. Priority Date: 05/09/2013
• Status: Abandoned Application

• Current Assignee: Invoice Cloud, Inc.
• Original Assignee: Invoice Cloud, Inc.
• Inventors: Bennett, Robert, Lapides, Robert, Morabito, John, Averyt, Kelton
• Application Number:
  US13/890,792
• Publication Number:
  US 20140337188A1
• Time in Patent Office: Days
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A method includes maintaining match data indicative of a correspondence between a past payment and a past invoice of a biller, the correspondence having previously been inferred from data associated with the past payment and data associated with the past invoice; and inferring a correspondence between a received payment and another invoice of the biller based on (i) data associated with the received payment and data associated with the other invoice and (ii) the match data for the biller.

Claims

1. A method comprising:

maintaining match data indicative of a correspondence between a past payment and a past invoice of a biller, the correspondence having previously been inferred from data associated with the past payment and data associated with the past invoice; and

inferring a correspondence between a received payment and another invoice of the biller based on (i) data associated with the received payment and data associated with the other invoice and (ii) the match data for the biller.

2. The method of claim 1, in which maintaining match data comprises maintaining match data for each of a plurality of billers, the match data for each biller indicative of a correspondence between a past payment and an invoice of the biller.

3. The method of claim 2, in which the match data for each biller is indicative of a correspondence between a plurality of past payments and a respective plurality of invoices of the biller.

4. The method of claim 1, in which maintaining match data comprises maintaining match data indicative of a correspondence between a plurality of past payments and a respective plurality of invoices of the biller.

5. The method of claim 1, in which the data associated with the received payment include one or more of a name associated with the received payment, an amount of the received payment, and contents of a memo associated with the received payment.

6. The method of claim 5, in which the data associated with the other invoice include one or more of a name associated with the other invoice, an amount due on the other invoice, a total amount due on an account associated with the other invoice, an account number associated with the other invoice, and an invoice number associated with the other invoice.

7. The method of claim 1, in which inferring a correspondence between a received payment and another invoice includes inferring the correspondence based on data associated with the past payment that matches data associated with the received payment, data associated with the past invoice that matches data associated with the other invoice, or both.

8. The method of claim 7, in which the data associated with the received payment comprises a name and the data associated with the past invoice comprises a name.

9. The method of claim 7, in which the data associated with the received payment comprises a name and the data associated with the past invoice comprises an account number.

10. The method of claim 1, in which inferring a correspondence between a received payment and another invoice includes rating the other invoice.

11. The method of claim 10, in which the rating is indicative of a degree of correspondence between the received payment and the other invoice.

12. The method of claim 10, in which rating the other invoice includes:

assigning a first rating to the other invoice based on the data associated with the received payment and data associated with the other invoice; and

assigning a second rating to the other invoice based on the match data.

13. The method of claim 12, in which the second rating is higher than the first rating.

14. The method of claim 13, in which the second rating is higher than the first rating when data associated with the past payment matches data associated with the received payment, data associated with the past invoice matches data associated with the other invoice, or both.

15. The method of claim 12, in which the match data are indicative of a correspondence between a plurality of past payments and a respective plurality of past invoices, and in which the second rating is based on a number of past payments for which data associated with the past payment matches data associated with the received payment, a number of past invoices for which data associated with the past invoice matches data associated with the other invoice, or both.

16. The method of claim 1, comprising identifying two or more other invoices corresponding to the received payment.

17. The method of claim 16, comprising rating each other invoice.

18. The method of claim 1, comprising associating the received payment with the other invoice.

19. The method of claim 18, comprising enabling processing of the received payment.

20. The method of claim 18, comprising enabling a payment confirmation notification to be sent to a recipient of the other invoice.

21. The method of claim 1, comprising enabling presentation of the data associated with the received payment, data associated with the other invoice, or both to a user.

22. The method of claim 1, comprising receiving input from a user about the other invoice.

23. The method of claim 22, in which the input from the user about the other invoice includes a confirmation of the inferred correspondence between the received payment and the other invoice.

24. The method of claim 23, comprising associating the received payment with the other invoice based on the confirmation.

25. The method of claim 1, comprising maintaining match data indicative of a correspondence between the received payment and the other invoice.

26. The method of claim 1, in which the past payment comprises a payment made by a paper check.

27. The method of claim 1, in which the past payment comprises a payment made by an online bank payment process.

28. A computer readable storage medium storing instructions for causing a computing system to:

maintain match data indicative of a correspondence between a past payment and a past invoice of a biller, the correspondence having previously been inferred from data associated with the past payment and data associated with the past invoice; and

infer a correspondence between a received payment and another invoice of the biller based on (i) data associated with the received payment and data associated with the other invoice and (ii) the match data for the biller.

29. A method comprising:

enabling a customer, through a user interface of a computing device, to specify a schedule for payment of an invoice, including enabling the customer to specify payment timing information; and

facilitating automatic payment of the invoice according to the payment schedule specified by the customer.

30. The method of claim 29, comprising determining a date and amount for each payment in the schedule based on the specified payment timing information.

31. The method of claim 30, comprising determining a data and amount for each payment in the schedule based on payment amount information specified by the customer.

32. The method of claim 29, comprising providing a date and an amount for each payment represented by the schedule for display on the user interface.

33. The method of claim 29, comprising enabling the customer to change a date, an amount, or both, for one or more payments represented by the schedule.

34. The method of claim 33, comprising determining an adjusted date, an adjusted amount, or both, for each payment represented by the schedule based on the change.

35. The method of claim 29, comprising enabling the customer to cancel a payment represented by the schedule.

36. The method of claim 35, comprising determining an adjusted date, an adjusted amount, or both, for each remaining payment represented by the schedule based on the cancellation.

37. The method of claim 29, in which the payment timing information includes one or more of a date for a particular payment, a number of payments, and a frequency of payments.

38. The method of claim 37, in which the date for a particular payment includes a date for a first payment in the schedule, a date for a last payment in the schedule, or both.

39. The method of claim 29, in which enabling a customer to specify a schedule includes enabling the customer to specify payment amount information.

40. The method of claim 29, in which the payment amount information includes an amount to be paid in each payment, a total amount to be paid over all payments, or both.

41. The method of claim 29, in which enabling a customer to specify a schedule includes enabling the customer to specify a schedule subject to a rule established by an entity issuing the invoice.

42. The method of claim 41, in which the rule includes a maximum number of payments, a minimum amount of each payment, or both.

43. The method of claim 41, comprising enabling the entity issuing the invoice to specify the rule.

44. The method of claim 29, comprising enabling a first customer to specify a schedule for payment of a first invoice issued by a first entity and enabling a second customer to specify a schedule for payment of a second invoice issued by a second entity independent of the first entity

45. The method of claim 44, in which enabling two or more customers to each specify a schedule includes enabling each customer to specify a schedule subject to a rule established by the entity issuing the invoice for the customer.

46. The method of claim 44, comprising enabling the first entity to specify a rule for the schedule independently of the second entity.

47. The method of claim 29, comprising enabling a schedule notification including the date, the amount, or both, of each payment represented by the schedule to be sent to the customer.

48. The method of claim 29, comprising enabling a scheduled payment notification to be sent to the customer a predetermined amount of time prior to the date of each particular payment represented by the schedule.

49. The method of claim 48, in which the predetermined amount of time is three days prior to the date of each payment.

50. The method of claim 29, comprising enabling a payment confirmation notification to be sent to the customer after each payment in the schedule is completed.

51. A computer readable storage medium storing instructions for causing a computing system to:

enable a customer, through a user interface of a computing device, to specify a schedule for payment of an invoice, including enabling the customer to specify payment timing information; and

facilitate automatic payment of the invoice according to the payment schedule specified by the customer.

52. A method comprising:

enabling a customer to establish automatic payments through a payment system for one or more invoices related to a property; and

based on a change related to a person associated with the property,

canceling the automatic payments through the payment system for the one or more invoices related to the property.

53. The method of claim 52, in which the change in a person associated with the property includes a change in ownership of the property.

54. The method of claim 53, in which the change of ownership of the property includes that the customer does not own the property.

55. The method of claim 53, in which detecting a change in ownership includes detecting that the property has been bought, sold, or both.

56. The method of claim 53, in which the change in ownership includes a name on a title for the property.

57. The method of claim 56, in which the change in ownership includes a change in the name on the title for the property.

58. The method of claim 56, in which the change in ownership of the property includes a change in a public record associated with the property.

59. The method of claim 52, in which the customer is a first customer, and in which the change in a person associated with the property includes that a second customer performs an action associated with the property through the payment system.

60. The method of claim 52, in which customer is a first customer, and in which the change in a person associated with the property includes that a second customer establishes an account with the payment system, links an established account with the property, or both.

61. The method of claim 52, in which a change in a person associated with the property includes a change in a name associated with the one or more invoices.

62. The method of claim 61, in which a change in a name associated with the one or more invoices includes that the name of the customer is not associated with the one or more invoices.

63. The method of claim 52, comprising detecting the change in a person associated with the property.

64. The method of claim 63, in which detecting the change includes automatically detecting the change.

65. The method of claim 64, in which automatically detecting the change includes detecting the change without requesting input from a user.

66. The method of claim 52, in which canceling the automatic payments includes automatically canceling the automatic payments.

67. The method of claim 66, in which automatically canceling the automatic payments includes canceling the automatic payments without requesting input from the customer, from a user other than the customer, or both.

68. The method of claim 52, comprising requesting confirmation of the cancellation from the customer.

69. The method of claim 68, in which requesting confirmation includes requesting confirmation prior to canceling the automatic payments.

70. The method of claim 52, comprising sending a cancellation notification to the customer.