Systems and methods for analyzing telecommunications invoices for payment

• US 8,712,878 B2
• Filed: 02/14/2008
• Issued: 04/29/2014
• Est. Priority Date: 02/10/2003
• Status: Active Grant

• Current Assignee: Tangoe US, Inc. (Asentinel Holdings LP)
• Original Assignee: Asentinel LLC (Asentinel Holdings LP)
• Inventors: Fisher, Jason M.
• Primary Examiner(s): Zeender, F.
• Assistant Examiner(s): BUCHANAN, CHRISTOPHER R
• Application Number:
  US12/031,399
• Publication Number:
  US 20080285733A1
• Time in Patent Office: 2,266 Days
• Field of Search: None
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• 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
• CPC Class Codes: G06Q 40/10 Tax strategies
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/58 based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/70 Administration or customization aspects; Counter-checking correct charges
• CPC Class Codes: H04M 15/73 Validating charges
• CPC Class Codes: H04M 15/7655 shared by technologies
• CPC Class Codes: H04M 15/772 per service, e.g. prepay or post-pay
• CPC Class Codes: H04M 15/773 per technology, e.g. PSTN or wireless
• CPC Class Codes: H04M 2215/0104 Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• CPC Class Codes: H04M 2215/0176 Billing arrangements using internet
• CPC Class Codes: H04M 2215/0188 Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04M 2215/70 Administration aspects, modify settings or limits or counter-check correct charges
• CPC Class Codes: H04M 2215/7072 Validate charges
• CPC Class Codes: H04M 2215/725 Shared by technologies, e.g. one account for different access technologies
• CPC Class Codes: H04M 2215/7263 per service, e.g. prepay and post-pay
• CPC Class Codes: H04M 2215/7268 : per technology, e.g. PSTN or wireless

Abstract

A system and method for management and processing a plurality of types of telecommunication invoices at a user'"'"'s site involving importing the plurality of types of telecommunication invoices to provide comparable telecommunication invoices and auditing the comparable telecommunication invoices by performing an automated reasonability test on the comparable telecommunication invoices. The system and method also provide a means for approving, processing and reporting on the comparable telecommunication invoices.

Claims

1. A method for electronically processing a telecommunications invoice from one or more vendors, comprising:

(a) importing the telecommunications invoices into a computing device;

(b) within the computing device extracting elements from the imported telecommunications invoices;

(c) within the computing device performing a reasonability test on the imported telecommunications invoices;

wherein performing the reasonability test includes evaluating the telecommunication invoice on an element basis to determine whether an element billing exception exists, wherein a reasonability test comprises an automated comparison against established criteria; and

wherein the reasonability test includes determining whether a cost center associated with an element among the extracted elements is active; and

(d) generating by the computing device a report that makes apparent element billing exceptions.

2. The method of claim 1, wherein an element of a telecommunications invoice is an individual charge at its smallest component available on the telecommunications invoice.

3. The method of claim 1, further comprising performing a pre-analysis communication error check on the imported telecommunications invoices, wherein an imported telecommunications invoice is rejected when a transmission exception is found.

4. The method of claim 1, wherein extracting elements from the imported telecommunications invoices includes applying a set of vendor mapping rules to vendor specific nomenclature for elements to transform the vendor specific nomenclature to categories that are comparable.

5. The method of claim 1, further comprising performing an initial invoice sanity check, wherein a total sum of line item charges is compared to an invoice total of a imported telecommunications invoice.

6. The method of claim 1, further comprising displaying the report that makes apparent element billing exceptions.

7. The method of claim 6, further comprising displaying additional information regarding an element billing exception upon receiving a request for more information on the element billing exception.

8. The method of claim 7, wherein the displayed report includes Universal Service Ordering Codes (USOC) codes and a USOC description for selected line item charges.

9. The method of claim 6, further comprising changing an exception status of an element billing exception upon receiving a request to change the exception status of the element billing exception.

10. The method of claim 1, further comprising displaying a status for a telecommunications invoice that indicates whether the telecommunications invoice has been approved.

11. The method of claim 1, further comprising electronically paying a telecommunications invoice.

12. The method of claim 1, further comprising conducting within the computing device trend analysis based at least in part on the telecommunications invoices.

13. The method of claim 1, further comprising:

(e) receiving instructions within the computing device for treatment of element billing exceptions; and

(e) transmitting by the computing device approved invoice information.

14. The method of claim 1, wherein an element on a telecommunications invoice is a line item available on the telecommunications invoice.

15. The method of claim 1, wherein an element on a telecommunications invoice is a service code available on the telecommunications invoice.

16. The method of claim 15, wherein a service code is a Universal Service Ordering Code (USOC).

17. The method of claim 1, wherein the reasonability test includes evaluating quantitative elements.

18. The method of claim 1, wherein the reasonability test includes evaluating non-quantitative elements.

19. The method of claim 1, wherein the reasonability test includes an audit of quantitative elements.

20. The method of claim 19, wherein the audit of quantitative elements includes analyzing individual charges on a telecommunications invoice at their smallest components available on the telecommunications invoice.

21. The method of claim 1, wherein performing the reasonability test comparing an element against a contracted rate for the element.

22. The method of claim 1, wherein performing the reasonability test on an element includes performing the reasonability test only on elements within a selected portion of the telecommunications invoice.

23. The method of claim 1, wherein performing the reasonability test includes determining whether a phone number appearing on a telecommunications invoice for a first vendor is designated to a different vendor.

24. The method of claim 1, wherein performing the reasonability test on an element includes determining whether a wireless roaming charge is correct.

25. The method of claim 1, wherein performing the reasonability test includes deter whether the number of wireless telecommunications minutes billed is correct.

26. The method of claim 4, further comprising interfacing with a remote system to received vendor mapping rules updates.

64. The method of claim 13, wherein transmitting approved invoice information includes transmitting approved invoice information to either or both of an accounts processing system and a general ledger system.

27. A system for electronically processing wireless telecommunications invoices from one or more vendors, comprising:

a user database configured to store vendor mapping rules, wireless telecommunications invoices and data extracted from wireless telecommunications invoices; and

a computer system storing a user application module coupled to the user database, wherein the user application module includes;

(b) means for extracting elements from the imported wireless telecommunications invoices;

(c) means for performing a reasonability test on the imported wireless telecommunications invoices, wherein performing the reasonability test includes evaluating wireless telecommunication invoices on an element basis to determine whether an element billing exception exists, wherein performing the reasonability test includes determining whether the number of wireless telecommunications minutes billed is correct and determining whether a cost center associated with the element is active;

(d) means for generating a report that makes apparent element billing exceptions;

(e) means for receiving instructions for treatment of element billing exceptions; and

(f) means for transmitting approved invoice information to either or both of an accounts processing system or a general ledger system.

28. The system of claim 27, wherein an element of a telecommunications invoice is an individual charge at its smallest component available on the telecommunications invoice.

29. The system of claim 27, wherein the wireless telecommunications invoices are provided by at least two different vendors.

30. The system of claim 27, further comprising means for performing a two-part prescreening analysis that comprises performing a pre-analysis communication error check on the imported wireless telecommunications invoices, wherein an invoice is rejected when a transmission exception is found and performing an initial invoice sanity check, wherein a total sum of element charges is compared to the an invoice total of a received invoice, and generating an error report when an invoice fails the initial invoice sanity check.

31. The system of claim 30, wherein a transmission exception includes a syntax error, a missing vendor, or a duplicate invoice.

32. The system of claim 27, wherein the means of extracting elements from imported wireless telecommunications invoices includes a means applying a set of vendor mapping rules to vendor specific nomenclature for elements to transform the vendor specific nomenclature for the elements to categories that are comparable.

33. The system of claim 27, further comprising means to customize billing exception criteria.

34. The system of claim 27, wherein the means for performing a reasonability test includes means for performing a reasonability test on an element by comparing an element charge against the contracted rate for the element.

35. The system of claim 27, further comprising means for displaying the report that makes apparent element billing exceptions.

36. The system of claim 35, wherein the displaying means includes means for displaying additional information regarding an element billing exception upon receiving a request for more information on the element billing exception.

37. The system of claim 27, further comprising means for interfacing with a remote system to receive vendor mapping rules updates.

38. The system of claim 27, wherein performing the reasonability test includes determining that a wireless roaming charge is incorrect.

39. The system of claim 27, wherein performing the reasonability test includes performing the reasonability test on a selected portion of an invoice based on whether an invoice portion has been modified.

40. A computer program product comprising a computer usable non-transitory medium having control logic stored therein for causing a computer to process telecommunications invoices received from one or more vendors, said control logic comprising:

computer readable program code means for causing the computer to extract elements from telecommunications invoices;

computer readable program code means for causing the computer to perform a reasonability test on the imported telecommunication invoices, wherein performing the reasonability test includes evaluating the telecommunication invoices on an element basis to determine whether an element billing exception exists and determine whether a cost center associated with the element is active;

computer readable program code means for causing the computer to receive instructions for treatment of element billing exceptions; and

computer readable program code means for causing the computer to transmit approved invoice information.

41. The computer program product of claim 40, wherein extracting means further comprises computer readable program code means for causing a computer to apply a set of vendor mapping rules to vendor specific nomenclatures for elements to transform the vendor specific nomenclature for the elements to categories that are comparable.

42. The computer program product of claim 40, further comprising computer readable program code means for causing a computer to perform an initial invoice sanity check, wherein a total sum of element charges is compared to an invoice total of a received invoice, and generating an error report when an invoice fails the initial invoice sanity check.

43. The computer program product of claim 40, wherein an element on a telecommunications invoice is an individual charge at its smallest component available on the telecommunications invoice.

44. The computer program product of claim 40, wherein the transmitting means further comprises computer readable program code means for transmitting approved invoice information to either or both of an accounts processing system and a general ledger system.

45. The computer program product of claim 40, further comprising computer readable program code means for performing a pre-analysis communication error check on the imported telecommunications invoices, wherein an imported telecommunications invoice is rejected when a transmission exception is found.

46. The computer program product of claim 40, wherein the extracting means further includes computer readable program code means for applying a set of vendor mapping rules to vendor specific nomenclature for elements to transform the vendor specific nomenclature to categories that are comparable.

47. The computer program product of claim 40, further comprising computer readable program code means for displaying a report that makes apparent element billing exceptions.

48. The computer program product of claim 47, wherein the displaying means further comprises computer readable program code means for displaying additional information regarding an element billing exception upon receiving a request for more information on the element billing exception.

49. The computer program product of claim 40, further comprising computer readable program code means for changing an exception status of an element billing exception upon receiving a request to change the exception status of the element billing exception.

50. The computer program product of claim 40, wherein further comprising computer program codes means for displaying a status for a telecommunications invoice that indicates whether the telecommunications invoice has been approved.

51. The computer program product of claim 40, further comprising computer program code means for electronically paying the telecommunications invoices.

52. The computer program product of claim 40, wherein an element on a telecommunications invoice is a line item available on the telecommunications invoice.

53. The computer program product of claim 40, wherein an element on a telecommunications invoice is a service code available on the telecommunications invoice.

54. The computer program product of claim 40, wherein a service code is a Universal Service Ordering Code (USOC).

55. The computer program product of claim 40, wherein reasonability means includes computer program code means for evaluating quantitative elements.

56. The computer program product of claim 40, wherein reasonability means includes computer program code means for evaluating non-quantitative elements.

57. The computer program product of claim 40, wherein reasonability means includes computer program code means for conducting an audit of quantitative elements.

58. The computer program product of claim 57, wherein the auditing means of quantitative elements further includes computer program code means for analyzing individual charges at their smallest components available within a telecommunications invoice.

59. The computer program product of claim 40, wherein reasonability means includes computer program code means for comparing an element against a contracted rate for the element.

60. The computer program product of claim 40, wherein reasonability means includes computer program code means performing a reasonability test only on elements within a selected portion of a telecommunications invoice.

61. The computer program product of claim 40, wherein reasonability means includes computer program code means for determining whether a phone number appearing on an invoice for a first vendor is designated to a different vendor.

62. The computer program product of claim 40, wherein reasonability means includes computer program code means for determining whether a wireless roaming charge is correct.

63. The computer program product of claim 40, wherein reasonability means includes computer program code means for determining whether the number of wireless telecommunications minutes billed is correct.