Payment entity account set up for multiple payment methods

• US 8,311,913 B2
• Filed: 02/13/2008
• Issued: 11/13/2012
• Est. Priority Date: 10/30/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Marchetti, John N., Mullen, Matthew
• Primary Examiner(s): NGUYEN, TIEN C
• Application Number:
  US12/030,785
• Publication Number:
  US 20090112659A1
• Time in Patent Office: 1,735 Days
• Field of Search: 705/14.1, 705 30- 45, 705/7
• US Class Current: 705/35
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 20/3572 Multiple accounts on card
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07F 7/10 together with a coded signal , e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data

Abstract

A method begins with a payment entity device receiving payables process data from a client device. The payables process data includes a list of a plurality of creditors and associated payment data, wherein, for a creditor of the plurality of creditors, the associated payment data includes at least one payment scheme for paying at least a portion of debt owed to the creditor via at least one of: a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account. The method continues with the payment entity device determining level of service for a client associated with the client device. The method continues with the payment entity device generating a payables profile for the client based on the payables process data in accordance with the level of service.

Claims

1. A method for creating a payables profile in an automated accounts payable process, the method comprising:

receiving payable process data at a payment entity device that is configured to facilitate payment and reconciliation of accounts payable from a client device that is operated by a client that pays a plurality of creditors, wherein the payable process data includes identification information for the plurality of creditors and associated payment data for each of the plurality of creditors, wherein the associated payment data includes at least a first payment scheme for a first type of transaction with a first creditor of the plurality of creditors and a second payment scheme for a second type of transaction with a second creditor of the plurality of creditors;

wherein the first payment scheme includes at least one of;

a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account and the second payment scheme includes a different one of;

a business credit card, a funds transfer, commercial paper, monetary consideration such as a rebate, refund, or exchange, and a debit account;

wherein the first type of transaction includes individual transactions corresponding to a first category of services or goods, and wherein the second type of transaction includes individual transactions within a value threshold;

generating a payables profile for the client by the payment entity device based on the payables process data;

determining, by the payment entity device, whether the client device is associated with a level of service comprising a first level of service or another level of service that is not the first level of service;

in response to a determination of the first level of service, determining by the payment entity device;

that the payables process data identifies multiple payment methods, and in response to determining multiple methods of payment for a selected creditor, storing a payment scheme, by the payment entity device, for portions of debt owed to the selected creditor in accordance with the multiple methods of payment and repeating for each creditor identified in the payables process data;

or

that the payables process data indentifies a single method of payment, and storing a payment scheme, by the payment entity device, for each creditor identified in the payables process data;

in response to a determination of another level of service that is not the first level of service, performing a process by the payment entity device in which the payables profile may be changed based on payment program data that is generated by the payment entity device; and

wherein the payment schemes are stored in the payables profile at the payment entity device, such that the payment entity device responds to payment data from the client device by generating a first payment of the first creditor by the first payment scheme for the first type of transaction and by generating a second payment of the second creditor by the second payment scheme for the second type of transaction in accordance with the payables process data.

2. The method of claim 1 further comprising:

when the level of service is the first level of service, the generating the payables profile for the plurality of creditors comprises;

storing identification information for the plurality of creditors; and

storing the payment scheme for each of the plurality of creditors received in the payables process data from the client device as the associated payment data for the plurality of creditors in the payment entity device.

3. The method of claim 1 further comprising:

when the level of service is the first level of service, the generating the payables profile for the first creditor of the plurality of creditors comprises;

storing identification information for the first creditor; and

storing the first payment scheme for the first type of transaction with the first creditor.

4. The method of claim 3, wherein the generating the associated payment data for the first creditor of the plurality of creditors stored in the payables profile for the client comprises at least one of:

storing a shipping payment scheme for paying shipping costs as part of the associated payment data; and

storing a tax payment scheme for paying taxes associated with goods or services purchased from the first creditor as part of the associated payment data.

5. The method of claim 1,

wherein when the level of service is a second level of service, the generating the payables profile for the first creditor of the plurality of creditors comprises:

generating payment program data that, at least, includes a payment program from a financial entity;

transmitting the payment program data to the client device;

storing at least one altered payment scheme in accordance with a selected payment program when a response from the client device indicates changing the associated payment data, wherein the selected payment program is a payment program selected from the payment program data;

storing the first payment scheme when a response from the client device indicates using the first payment scheme; and

storing identification information for the first creditor.

6. The method of claim 1, wherein when the level of service is a third level of service, the generating the payables profile for the first creditor of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the first payment scheme, generating at least one recommended altered payment scheme;

transmitting the at least one recommended altered payment scheme to the client device;

storing the at least one recommended altered payment scheme when a response from the client device to use the at least one recommended altered payment scheme is received;

storing the first payment scheme when a response from the client device to use the first payment scheme is received; and

storing identification information for the first creditor.

7. The method of claim 1, wherein when the level of service is a fourth level of service, the generating the payables profile for the first creditor of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the first payment scheme, generating at least one recommended altered payment scheme;

storing identification information for the first creditor; and

storing the at least one recommended altered payment scheme.

8. The method of claim 1 further comprising:

receiving updated associated payment data for the first creditor from the client device; and

updating the payables profile in accordance with the updated associated payment data.

9. The method of claim 1 further comprising, when a first update service is enabled:

generating updated payment program data that, at least, includes an updated or new payment program from a financial entity;

transmitting the updated payment program data to the client device; and

overwriting the first payment scheme with at least one updated payment scheme in accordance with a selected updated payment program when a response from the client device indicates updating the associated payment data, wherein the selected updated payment program is a payment program selected from the updated payment program data.

10. The method of claim 1 further comprising, when a second update service is enabled:

generating updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the first payment scheme, generating at least one recommended updated payment scheme;

transmitting the at least one recommended updated payment scheme to the client device; and

overwriting the first payment scheme with the at least one recommended updated payment scheme when a response from the client device to use the at least one recommended updated payment scheme is received.

11. The method of claim 1 further comprising, when a third update service is enabled:

generating updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the first payment scheme, generating at least one recommended updated payment scheme; and

overwriting the first payment scheme with the at least one recommended updated payment scheme.

12. The method of claim 1 wherein the associated payment data further includes one payment scheme for one portion of a debt owed to a creditor and another payment scheme for another portion of the debt owed to the creditor.

13. The method of claim 12 wherein the payment entity device provides a report to the client device.

14. The method of claim 1 wherein the payment entity device is part of a proprietary payment network.

15. An apparatus comprising:

a processing module; and

memory coupled to the processing module, wherein the processing module functions, at least partially based on operational instructions stored in the memory, for;

receiving payables process data at the apparatus from a client device that is operated by a client that pays a plurality of creditors, wherein the payables process data includes identification information for the plurality of creditors and associated payment data for each of the plurality of creditors, wherein the associated payment data includes at least a first payment scheme for a first type of transaction with a first creditor of the plurality of creditors and a second payment scheme for a second type of transaction with a second creditor of the plurality of creditors;

wherein the first payment scheme includes at least one of;

a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account and the second payment scheme includes a different one of;

a business credit card, a funds transfer, commercial paper, monetary consideration such as a rebate, refund, or exchange, and a debit account;

wherein the first type of transaction includes individual transactions corresponding to a first category of services or goods, and wherein the second type of transaction includes individual transactions within a value threshold,

generating a payables profile for the client by the apparatus based on the payables process data;

determining by the apparatus whether the client device is associated with a level of service comprising a first level of service or another level of service that is not the first level of service;

in response to a determination of the first level of service, determining by the apparatus;

that the payables process data identifies multiple payment methods, and in response to determining multiple methods of payment for a selected creditor, storing a payment scheme, by the apparatus, for portions of debt owed to the selected creditor in accordance with the multiple methods of payment and repeating for each creditor identified in the payables process data;

or

that the payables process data indentifies a single method of payment, storing a payment scheme, by the payment entity device, for each creditor identified in the payables process data;

in response to a determination of another level of service that is not the first level of service, performing a process by the apparatus in which the payables profile may be changed based on payment program data that is generated by the payment entity device; and

wherein the payment schemes are stored in the payables profile at the apparatus, such that the apparatus responds to payment data from the client device by generating a first payment of the first creditor by the first payment scheme for the first type of transaction and by generating a second payment of the second creditor by the second payment scheme for the second type of transaction in accordance with the payables process data, and

wherein the apparatus is configured to facilitate payment and reconciliation of accounts payable.

16. The apparatus of claim 15, wherein when the level of service is the first level of service, the processing module generates the payables profile for the plurality of creditors by:

storing identification information for the plurality of creditors; and

storing the payment scheme for each of the plurality of creditors received in the payables process data from the client device as the associated payment data for the plurality of creditors in the payment entity device.

17. The apparatus of claim 15, wherein when the level of service is the first level of service, the processing module generates the payables profile for the first creditor of the plurality of creditors by:

storing identification information for the first creditor; and

storing the first payment scheme for the first type of transaction with the first creditor.

18. The apparatus of claim 17, wherein the processing module generates the payables profile for the first creditor of the plurality of creditors by at least one of:

storing a shipping payment scheme for paying shipping costs as part of the associated payment data; and

storing a tax payment scheme for paying taxes associated with goods or services received from the first creditor as part of the associated payment data.

19. The apparatus of claim 15, when the level of service is a second level of service, the processing module generates the payables profile for the first creditor of the plurality of creditors by:

generating payment program data that, at least, includes a payment program from a financial entity;

transmitting the payment program data to the client device;

storing at least one altered payment scheme in accordance with a selected payment program when a response from the client device indicates changing the associated payment data, wherein the selected payment program is a payment program selected from the payment program data;

storing the first payment scheme when a response from the client device to use the first payment scheme; and

storing identification information for the first creditor.

20. The apparatus of claim 19, wherein when the level of service is a third level of service, the processing module generates the payables profile for the first creditor of the plurality of creditors by:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the first payment scheme, generating at least one recommended altered payment scheme;

transmitting the at least one recommended altered payment scheme to the client device;

storing the at least one recommended altered payment scheme when a response from the client device to use the at least one recommended altered payment scheme is received;

storing the first payment scheme when a response from the client device to use the first payment scheme is received; and

storing identification information for the first creditor.

21. The apparatus of claim 20, wherein when the level of service is a fourth level of service, the processing module generates the payables profile for the first creditor of the plurality of creditors by:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the first payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the first payment scheme, generating at least one recommended altered payment scheme;

storing identification information for the first creditor; and

storing the at least one recommended altered payment scheme.

22. The apparatus of claim 15, wherein the processing module further functions to:

receive updated associated payment data for the first creditor from the client device; and

update the payables process data in accordance with the updated associated payment data.

23. The apparatus of claim 15, wherein the processing module further functions, when a first update service is enabled, to:

generate updated payment program data that, at least, includes an updated or new payment program from a financial entity;

transmit the updated payment program data to the client device; and

overwrite the first payment scheme with at least one updated payment scheme in accordance with a selected updated payment program when a response from the client device indicates updating the associated payment data, wherein the selected updated payment program is a payment program selected from the updated payment program data.

24. The apparatus of claim 15, wherein the processing module further functions, when a second update service is enabled, to:

generate updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

compare the first payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the first payment scheme, generate at least one recommended updated payment scheme;

transmit the recommended updated payment scheme to the client device; and

overwrite the first payment scheme with the at least one recommended updated payment scheme when a response from the client device to use the at least one recommended updated payment scheme is received.

25. The apparatus of claim 15, wherein the processing module further functions, when a third update service is enabled, to:

generate updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

compare the first payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the first payment scheme, generate at least one recommended updated payment scheme; and

overwrite the first payment scheme with the at least one recommended updated payment scheme.