Accounts payable process

• US 8,781,925 B1
• Filed: 03/15/2013
• Issued: 07/15/2014
• Est. Priority Date: 05/13/2002
• Status: Active Grant

• Current Assignee: The PNC Financial Services Group, Inc.
• Original Assignee: The PNC Financial Services Group, Inc.
• Inventors: Stone, James S., Domaracki, Greg
• Primary Examiner(s): Frenel, Vanel
• Application Number:
  US13/836,667
• Time in Patent Office: 487 Days
• Field of Search: 705/30, 705/28, 705/29, 705/26, 705/34, 705/44, 705/45, 705/37, 705/40, 705/52
• US Class Current: 705/30
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• 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: G06Q 40/12 Accounting

Abstract

Techniques for performing an accounts payable process may include receiving transaction data including at least one of invoice data, purchase order data, and vendor data; and verifying a transaction by matching a dynamic data set of client-specified multi-dimensional criteria to the transaction data. An accounts payable system may include a host system in communication with one or more client systems. The host system may include a matching database configured to receive an accounts payable file including at least one of invoice data, purchase order data, and vendor data; and verify a transaction by matching a dynamic data set of client-specified multi-dimensional records to attributes of the accounts payable file.

Claims

1. An accounts payable system comprising:

a host system in communication with one or more client systems, wherein the host system comprises at least one processor and an electronic memory in communication with the at least one processor, wherein the electronic memory comprises instructions that when executed by the at least one processor cause the at least one processor to;

receive invoice data describing a first invoice and vendor data describing a plurality of vendors;

determine whether the invoice data describes a purchase order;

match a first vendor identified by the first invoice to at least one vendor described by the vendor data, wherein the matching comprises comparing a set of multi-dimensional criteria identified by the first invoice and describing the first vendor to at least one vendor described by the vendor data, wherein the matching comprises;

performing a preliminary vendor match; and

conditioned on the preliminary vendor match being unsuccessful;

identifying a set of probable vendor matches based on the set of multi-dimensional criteria; and

simultaneously presenting the set of probable vendor matches selected from the plurality of vendors described by the vendor data on a graphical user interface;

retrieve a vendor profile from the vendor data, wherein the vendor profile describes the first vendor;

when the invoice data does not describe a purchase order and the vendor profile indicates that the vendor does not use purchase orders, match the first invoice to at least one recurring invoice type, wherein the matching the first invoice comprises comparing a second set of multi-dimensional criteria describing the at least one recurring invoice type to the first invoice, wherein the second set of multidimensional criteria comprise a range of receipt dates, an originating vendor, a product, and an invoice amount; and

conditioned upon successfully matching the first vendor to the at least one vendor and upon successfully matching the first invoice to the at least one recurring invoice type, transmit payment of the invoice to the first vendor.

2. The accounts payable system of claim 1, wherein the host system is accessible by at least one client system across a network.

3. The accounts payable system of claim 2, wherein the network comprises a wireless communications network.

4. The accounts payable system of claim 2, wherein the network comprises at least one of the Internet and World Wide Web.

5. The accounts payable system of claim 1, wherein the matching database stores the invoice data and the vendor data for a customer.

6. The accounts payable system of claim 1, wherein the invoice data and the vendor data are associated with a particular customer.

7. The accounts payable system of claim 1, wherein the matching database is configured to perform matching according to client-specific matching rules.

8. The accounts payable system of claim 1, wherein the matching database is configured to communicate probable matches to at least one client system.

9. The accounts payable system of claim 8, wherein the matching database is configured to allow the client system to manually select at least one probable match.

10. The accounts payable system of claim 1, further comprising a data transmission input device configured to communicate transaction information to the matching database.

11. The accounts payable system of claim 1, further comprising an unmatched processor configured to receive accounts payable files that are not successfully matched to at least one of the at least one vendor described by the vendor data and the at least one recurring invoice type.

12. The accounts payable system of claim 1, further comprising a matched file processor configured to receive and process accounts payable files that are successfully matched to at least one of the at least one vendor described by the vendor data and the at least one recurring invoice type.

13. A tangible computer readable medium comprising instructions that when executed by at least one processor cause the at least one processor to:

receive invoice data describing a first invoice and vendor data describing a plurality of vendors;

determine whether the invoice data describes a purchase order;

match a first vendor identified by the first invoice to at least one vendor described by the vendor data, wherein the matching comprises comparing a set of multi-dimensional criteria identified by the first invoice and describing the first vendor to at least one vendor described by the vendor data, wherein the matching comprises;

performing a preliminary vendor match; and

conditioned on the preliminary vendor match being unsuccessful;

identifying a set of probable vendor matches based on the set of multi-dimensional criteria; and

simultaneously presenting the set of probable vendor matches selected from the plurality of vendors described by the vendor data on a graphical user interface;

retrieve a vendor profile from the vendor data, wherein the vendor profile describes the first vendor;

when the invoice data does not describe a purchase order and the vendor profile indicates that the vendor does not use purchase orders, match the first invoice to at least one recurring invoice type, wherein the matching the first invoice comprises comparing a second set of multi-dimensional criteria describing the at least one recurring invoice type to the first invoice, wherein the second set of multi-dimensional criteria comprise a range of receipt dates, an originating vendor, a product, and an invoice amount; and

conditioned upon successfully matching the first vendor to the at least one vendor and upon successfully matching the first invoice to at least one recurring invoice type, transmit payment of the invoice to the first vendor.

14. The computer readable medium of claim 13, wherein the computer-readable medium comprises at least one of a disk and a device.

15. The computer readable medium of claim 14, further comprising instructions that when executed by at least one processor cause the at least one processor to initiate the electronic scanning of a paper invoice document.

16. The computer readable medium of claim 13, further comprising instructions that when executed by at least one processor cause the at least one processor to initiate the electronic scanning of a paper invoice document.

17. An accounts payable system comprising:

means for receiving invoice data describing a first invoice and vendor data describing a plurality of vendors;

means for determining whether the invoice data describes a purchase order;

means for matching a first vendor identified by the first invoice to at least one vendor described by the vendor data, wherein the matching comprises comparing a set of multi-dimensional criteria identified by the first invoice and describing the first vendor to at least one vendor described by the vendor data, wherein the matching comprises;

performing a preliminary vendor match; and

conditioned on the preliminary vendor match being unsuccessful;

identifying a set of probable vendor matches based on the set of multi-dimensional criteria; and

simultaneously presenting the set of probable vendor matches selected from the plurality of vendors described by the vendor data on a graphical user interface;

means for retrieving a vendor profile from the vendor data, wherein the vendor profile describes the first vendor;

means for matching the first invoice to at least one recurring invoice type when the invoice data does not describe a purchase order and the vendor profile indicates that the vendor does not use purchase orders, wherein the matching the first invoice comprises comparing a second set of multi-dimensional criteria describing the at least one recurring invoice type to the first invoice, wherein the second set of multi-dimensional criteria comprise a range of receipt dates, an originating vendor, a product, and an invoice amount; and

means for transmitting payment of the invoice to the first vendor, wherein the transmitting is conditioned upon successfully matching the first vendor to the at least one vendor and upon successfully matching the first invoice to at least one recurring invoice type.