ENHANCED ELECTRONIC ANONYMOUS PAYMENT SYSTEM

• US 20110184843A1
• Filed: 03/11/2011
• Published: 07/28/2011
• Est. Priority Date: 01/31/2008
• Status: Abandoned Application

• Current Assignee: Bill.com, Inc. (Bill.com Holdings, Inc.)
• Original Assignee: Bill.com, Inc. (Bill.com Holdings, Inc.)
• Inventors: Orttung, Mark, Lacerte, René
• Application Number:
  US13/045,948
• Publication Number:
  US 20110184843A1
• Time in Patent Office: Days
• US Class Current: 705/34
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Enhanced systems and methods for processing invoices, payments, and money transfers are described. One aspect of the invention is a computer-implemented method (and corresponding system and computer program product) for making payments between a plurality of different payors and a plurality of different issuers through a payment system, comprising: retrieving a plurality of invoices issued by a plurality of different issuers and issued to a plurality of different payors; receiving a request from at least one of the plurality of different payors for making a payment to at least one of the plurality of different issuers in response to at least one of the plurality of invoices; and in response to receiving the request, making a payment from a bank account of said payors to a bank account of said issuer without disclosing the bank accounts.

Claims

1. A computer-implemented method for making payments between a plurality of different payors and a plurality of different issuers through a payment system, the method comprising:

retrieving a plurality of invoices issued by a plurality of different issuers and issued to a plurality of different payors;

receiving a request from at least one of the plurality of different payors for making a payment to at least one of the plurality of different issuers in response to at least one of the plurality of invoices; and

in response to receiving the request, making a payment from a bank account of said payors to a bank account of said issuer without disclosing the bank account of said payor to said issuers and without disclosing the bank account of said issuer to said payor.

2. The method of claim 1, wherein said payor has a plurality of bank accounts and the method further comprises:

receiving from said payor a selection of one of the plurality of bank accounts, wherein making the payment comprises making the payment from the selected bank account of said payor.

3. The method of claim 1, wherein said issuer has a plurality of bank accounts and the method further comprises:

receiving from said issuer a selection of one of the plurality of bank accounts, wherein making the payment comprises making the payment to the selected bank account of said issuer.

4. The method of claim 1, wherein said issuers and payors are also referred to as entities, the method further comprising:

providing an entity with an option to allow information from the entity'"'"'s accounting system to propagate to accounting systems of entities with which the entity has one or more payment transactions.

5. The method of claim 4, further comprising:

receiving from the entity an input specifying values of data to be propagated to a specific entity, on a per entity basis, wherein the entity can further specify for each such value whether the value is on a per entity basis.

6. The method of claim 4, further comprising:

receiving from the entity a permissions mask specifying when and how the information from the entity'"'"'s accounting system is propagate to other accounting systems.

7. The method of claim 4, wherein said information comprises one or more documents.

8. The method of claim 4, further comprising:

synchronizing invoices, documents, and payments for said issuers and said payors.

9. The method of claim 1, wherein said issuers and payors are also referred to as entities and each entity has an entity identifier, and wherein entities involved in payment transactions are identified using their entity identifiers instead of bank accounts in the payment system.

10. The method of claim 1, wherein said payor has a fee-based accounts payable account with the payment system, the method further comprising:

transmitting an invitation from said payor to said issuer to set up a free accounts receivable account with the payment system for receiving the payment from the plurality of different payors through the payment system;

receiving an acceptance of the invitation from said issuer; and

responsive to receiving the acceptance, establishing the free accounts receivable account at the payment system for said issuer and making the payment using the free accounts receivable account.

11. The method of claim 10, further comprising:

assigning an entity identifier to said issuer;

linking the free accounts receivable account of said issuer with the fee-based accounts payable account of said payor; and

providing the issuer an option to upgrade to a fee-based accounts receivable account to access more functions of the payment system.

12. The method of claim 1, wherein said issuer has a fee-based accounts receivable account with the payment system, the method further comprising:

transmitting an invitation from said issuer to said payor to set up a free accounts payable account with the payment system for making the payment to the plurality of different issuers through the payment system;

receiving an acceptance of the invitation from said payor; and

responsive to receiving the acceptance, establishing the free accounts payable account at the payment system for said payor and making the payment using the free account payable account.

13. The method of claim 1, further comprising:

receiving an instruction from said payor for letting said issuer know payment statuses; and

responsive to receiving the instruction, notifying said issuer at least one of the following;

said payor received an invoice from said issuer, said payor has approved the invoice, and the time when a payment for the invoice is scheduled.

14. A non-transitory computer-readable storage medium encoded with executable computer program code for making payments between a plurality of different payors and a plurality of different issuers through a payment system, the computer program code comprising program code for:

retrieving a plurality of invoices issued by a plurality of different issuers and issued to a plurality of different payors;

receiving a request from at least one of the plurality of different payors for making a payment to at least one of the plurality of different issuers in response to at least one of the plurality of invoices; and

in response to receiving the request, making a payment from a bank account of said payors to a bank account of said issuer without disclosing the bank account of said payor to said issuers and without disclosing the bank account of said issuer to said payor.

15. The storage medium of claim 14, wherein said payor has a plurality of bank accounts and the computer program code further comprises program code for:

receiving from said payor a selection of one of the plurality of bank accounts, wherein making the payment comprises making the payment from the selected bank account of said payor.

16. The storage medium of claim 14, wherein said issuer has a plurality of bank accounts and the computer program code further comprises program code for:

receiving from said issuer a selection of one of the plurality of bank accounts, wherein making the payment comprises making the payment to the selected bank account of said issuer.

17. The storage medium of claim 14, wherein said issuers and payors are also referred to as entities, and the computer program code further comprises program code for:

providing an entity with an option to allow information from the entity'"'"'s accounting system to propagate to accounting systems of entities with which the entity has one or more payment transactions.

18. The storage medium of claim 17, wherein the computer program code further comprises program code for:

receiving from the entity an input specifying values of data to be propagated to a specific entity, on a per entity basis, wherein the entity can further specify for each such value whether the value is on a per entity basis.

19. The storage medium of claim 17, wherein the computer program code further comprises program code for:

receiving from the entity a permissions mask specifying when and how the information from the entity'"'"'s accounting system is propagate to other accounting systems.

20. The storage medium of claim 17, wherein said information comprises one or more documents.