Invoice verification hub

Abstract

A system includes a first business object including a first source of information, a second business object including a second source of information, and a hub operatively connected to the first business object and the second business object. The system also includes an information checking mechanism for comparing information from the first source and information from the second source with information from a third source. A method of checking invoices includes populating a local invoice due list with invoice information from distributed components as transactions occur, and checking an invoice against the local invoice due list.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an overall computing environment, according to an example embodiment.

FIG. 2 is a display of a model of a business object, according to an example embodiment.

FIG. 3 is a schematic view of a portion of the computing environment that includes a hub, according to an example embodiment.

FIG. 4 is a block diagram illustration of a value chain with prima nota and single point inventory objects, according to an example embodiment.

FIG. 5 is a flow diagram of a method for checking invoices, according to an example embodiment.

FIG. 6 is a schematic of a computer system that executes programming, according to an example embodiment.

Claims

1. A method of checking invoices comprising: populating a local invoice due list with invoice information from distributed components as transactions occur; andchecking an invoice against the local invoice due list.

2. The method of claim 1 wherein data in the local invoice due list is compatible with the format required by a local invoice checking process.

3. The method of claim 1 further comprising: providing a selected interface to the local invoice due list; andmatching the selected interface at each of the distributed components that populate the invoice due list.

4. The method of claim 1 wherein populating the local invoice due list further comprises: populating the local invoice due list with a first portion of invoice information from a first object; andpopulating the local invoice due list with a second portion of invoice information from a second object.

5. The method of claim 1 wherein populating the local invoice due list further comprises: populating the local invoice due list with a delivery information portion from a delivery object;populating the local invoice due list with a purchasing information portion from a purchasing object; andcomparing the delivery information portion from the delivery object to the purchasing information portion from the purchasing object.

6. The method of claim 1 further comprising: placing the invoice due list at a central invoice hub; anddelivering an image of the invoice to a central invoice hub.

7. The method of claim 1 further comprising: placing the invoice due list at a central invoice hub; anddelivering an electronic invoice to a central invoice hub.

8. The method of claim 1 further comprising booking an invoice when the amounts from the invoice information from distributed components in the local invoice due list correspond to amounts on the invoice.

9. The method of claim 8 further comprising communicating to a financial component when an invoice has been booked.

10. The method of claim 1 further comprising resolving an invoice when the amounts from the invoice information from distributed components in the local invoice due list fail to correspond to amounts on the invoice.

11. The method of claim 10 wherein resolving an invoice includes communicating with the source of the invoice.

12. The method of claim 1 further comprising providing a user interface for checking the invoice against the invoice due list.

13. A system comprising: a first business object including a first source of information;a second business object including a second source of information;a hub operatively connected to the first business object and the second business object, the hub for collecting information from the first source and the second source of information; andan information checking mechanism for comparing information from the first source and information from the second source with information from a third source independent from the first business object and the second business object.

14. The system of claim 13 wherein the third source of information includes an image.

15. The system of claim 13 wherein the third source of information originates from a company external to the system.

16. The system of claim 13 wherein the first source of information includes an a purchase order.

17. The system of claim 16 wherein the second source of information includes an indication of goods received.

18. The system of claim 17 wherein the third source of information includes an invoice.

19. The system of claim 18 wherein the hub further comprises an interface for receiving invoice information from the third source of information.

20. A computer readable medium having instructions for causing a computer to perform a method of checking invoices comprising: populating a local invoice due list with invoice information from distributed components as transactions occur; andchecking an invoice against the local invoice due list.