Ensuring the accurateness and currentness of information provided by the submitter of an electronic invoice throughout the life of a matter using tentative electronic invoice submission

• US 20050049966A1
• Filed: 08/20/2004
• Published: 03/03/2005
• Est. Priority Date: 06/09/2003
• Status: Abandoned Application

• Current Assignee: Legal Systems Holding Company
• Original Assignee: Legal Systems Holding Company
• Inventors: Thomas, Robert, Murray, Donald, Wencel, Ronald, Shriber, Greg, Boone, Richard, Melling, Thomas G.
• Application Number:
  US10/923,606
• Publication Number:
  US 20050049966A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A facility for collecting specified information in conjunction with the submission of an invoice by submitter is described. The facility provides a mechanism usable by the submitter to provide the specified information. When the facility receives the invoice from the submitter, the facility makes the invoice available for payment only after the mechanism has been used by the submitter to provide the specified information.

Claims

1. A method in computing system for collecting specified information in conjunction with the submission of an invoice on behalf of a vendor, comprising:

providing a mechanism usable by users associated with the vendor to provide the specified information;

receiving the invoice from a user associated with the vendor;

accepting the received invoice without imposing conditions on such acceptance;

after the invoice has been accepted, determining whether the mechanism has been used by a user associated with the vendor to provide the specified information;

if the mechanism has been used by a user associated with the vendor to provide the specified information, making the received invoice available for payment;

if the mechanism has not been used by a user associated with the vendor to provide the specified information;

providing a notification to at least one user associated with the vendor that identifies specified information that must be provided before the received invoice will be made available for payment; and

making the received invoice available for payment only after the mechanism has been used by a user associated with the vendor to provide the specified information.

2. A method in computing system for collecting specified information in conjunction with the submission of an invoice by a submitter, comprising:

providing a mechanism usable by the submitter to provide the specified information;

receiving the invoice from the submitter; and

after the invoice has been received from the submitter, making the received invoice available for payment only after the mechanism has been used by the submitter to provide the specified information.

3. The method of claim 2 wherein the invoice is received before the mechanism has been used by the submitter to provide the specified information.

4. The method of claim 3, further comprising, in response to receiving the invoice before the mechanism has been used by the submitter to provide the specified information, generating a notification to the submitter that identifies specified information that must be provided before the received invoice will be made available for payment.

5. The method of claim 4 wherein the invoice is received from a first user associated with the submitter, and wherein the notification is generated for a second user associated with the submitter.

6. The method of claim 5 wherein the first user is a billing clerk.

7. The method of claim 5 wherein the second user is an account manager.

8. The method of claim 5 wherein the second user is an attorney.

9. The method of claim 5 wherein the second user is a non-attorney.

10. The method of claim 4 wherein the invoice is received from an automated billing system used by the submitter, and wherein the notification is generated for a human user associated with the submitter.

11. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises delivering the received invoice to a user belonging to the invoiced organization.

12. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises displaying the received invoice to a user belonging to the invoiced organization.

13. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting a user belonging to the invoiced organization to review the received invoice.

14. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting a user belonging to the invoiced organization to approve the received invoice for payment.

15. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting the invoiced organization to pay the received invoice.

16. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting an accounts payable branch of the invoiced organization to pay the received invoice.

17. The method of claim 2 wherein making the received invoice available for payment comprises arranging electronic payment of the received invoice.

18. The method of claim 2 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises forwarding the received invoice to an accounts payable branch of the invoiced organization.

19. The method of claim 2 wherein the invoice is received in connection with a distinguished matter being handled by the submitter, and wherein the specified information relates to the distinguished matter.

20. The method of claim 2 wherein the invoice is received in connection with a distinguished on of a plurality of matters being handled by the submitter, and wherein the specified information relates to one or more of a proper superset of the distinguished matters.

21. The method of claim 2 wherein the invoice is received in connection with a distinguished matter being handled by the submitter, and wherein the specified information relates to all work being handled by the submitter.

22. The method of claim 2 wherein the invoice is received in connection with a distinguished matter being handled by the submitter, and wherein the specified information does not relate to the distinguished matter.

23. The method of claim 2 wherein no conditions are imposed on receiving the submitted invoice.

24. The method of claim 2 wherein the only conditions imposed on receiving the submitted invoice relate to the properness of the invoice'"'"'s contents.

25. The method of claim 2 wherein the only conditions imposed on receiving the submitted invoice relate to the properness of the invoice'"'"'s formatting.

26. The method of claim 2 wherein the received invoice has a total amount, and wherein the specified information comprises an explanation of why the total amount exceeds an earlier-provided cost estimate.

27. The method of claim 2 wherein the specified information comprises a status report.

28. The method of claim 2 wherein the specified information comprises a budget.

29. The method of claim 2 wherein the specified information comprises an indication of a geographic location to which the invoice relates.

30. The method of claim 2 wherein the invoice relates to a litigation legal matter, and wherein specified information comprises a case analysis and assessment for the litigation legal matter.

31. The method of claim 2 wherein the invoice relates to a litigation legal matter, and wherein specified information comprises an estimate of exposure for the litigation legal matter.

32. The method of claim 2 wherein the specified information comprises confirmation of earlier-provided information.

33. A computer-readable medium whose contents cause a computing system to perform a method for collecting specified information in conjunction with the submission of an invoice by a submitter, the method comprising:

providing a mechanism usable by the submitter to provide the specified information;

receiving the invoice from the submitter; and

after the invoice has been received from the submitter, making the received invoice available for payment only after the mechanism has been used by the submitter to provide the specified information.

34. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises delivering the received invoice to a user belonging to the invoiced organization.

35. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises displaying the received invoice to a user belonging to the invoiced organization.

36. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting a user belonging to the invoiced organization to review the received invoice.

37. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting a user belonging to the invoiced organization to approve the received invoice for payment.

38. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting the invoiced organization to pay the received invoice.

39. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises permitting an accounts payable branch of the invoiced organization to pay the received invoice.

40. The computer-readable medium of claim 33 wherein making the received invoice available for payment comprises arranging electronic payment of the received invoice.

41. The computer-readable medium of claim 33 wherein the invoice is intended for an invoiced organization,

and wherein making the received invoice available for payment comprises forwarding the received invoice to an accounts payable branch of the invoiced organization.

42. A computing system for collecting specified information in conjunction with the submission of an invoice by a submitter, comprising:

a user interface component usable by the submitter to provide the specified information;

an invoice receiving component that receives the invoice from the submitter; and

a payment gating component that, after the invoice has been received from the submitter, makes the received invoice available for payment only after the mechanism has been used by the submitter to provide the specified information.

43. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by delivering the received invoice to a user belonging to the invoiced organization.

44. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by displaying the received invoice to a user belonging to the invoiced organization.

45. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by permitting a user belonging to the invoiced organization to review the received invoice.

46. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by permitting a user belonging to the invoiced organization to approve the received invoice for payment.

47. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by permitting the invoiced organization to pay the received invoice.

48. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by permitting an accounts payable branch of the invoiced organization to pay the received invoice.

49. The computing system of claim 42 wherein the payment gating component makes the received invoice available for payment by arranging electronic payment of the received invoice.

50. The computing system of claim 42 wherein the invoice is intended for an invoiced organization,

and wherein the payment gating component makes the received invoice available for payment by forwarding the received invoice to an accounts payable branch of the invoiced organization.

51. One or more generated data signals collectively conveying to a user associated with a vendor that has submitted an invoice a notification data structure relating to the submitted invoice, the notification data structure comprising:

information identifying one or more required information items; and

information indicating that the submitted invoice will only be made available for processing after the identified required information items are provided by the vendor.