METHOD FOR DETECTING FRAUDULENT TRANSACTIONS BETWEEN PRACTICE MANAGEMENT AND ACCOUNTING SOFTWARE

• US 20110137761A1
• Filed: 05/27/2010
• Published: 06/09/2011
• Est. Priority Date: 05/27/2009
• Status: Abandoned Application

• Current Assignee: Mckean Enterprises LLC
• Original Assignee: Mckean Enterprises LLC
• Inventors: McDermott, Steven E., Kim, Ernie
• Application Number:
  US12/789,336
• Publication Number:
  US 20110137761A1
• Time in Patent Office: Days
• US Class Current: 705/30
• 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

A method for detecting fraudulent transactions includes acquiring transaction data entered into an accounting software program and a practice management software program by a monitoring software program. The monitoring software program can be configured to detect any unusual activity in the acquired transaction data and to store detected unusual activity for later review. The monitoring software can be directed to notify a responsible party that unusual activity has been found in the originally acquired data. The monitoring software can be configured to format the acquired data and the data of the unusual activity into a report reviewable by the responsible party.

Claims

1. A method for detecting fraudulent transactions;

comprising;

acquiring transaction data entered into an accounting software program by a monitoring software program;

acquiring transaction data entered into a practice management software program by a monitoring software program;

configuring the monitoring software program to detect any unusual activity in the acquired transaction data and to store detected unusual activity for later review;

directing the monitoring software to notify a responsible party that unusual activity has been found in the originally acquired data; and

configuring the monitoring software to format the acquired data and the data of the unusual activity into a report reviewable by the responsible party.

2. A method in accordance with claim 1, wherein the operation of acquiring transaction data further includes interfacing the monitoring software program with the accounting software program and the practice management software program to provide access to the data entered into the accounting software program and the practice management software program by the monitoring software program.

3. A method in accordance with claim 1, wherein the acquired transaction data includes key fraud indicators selected from the group consisting of:

date change, service amount change, service code change, deposit amount change, deleted transactions, deleted entries, modified transactions, modified entries, and combinations thereof.

4. A method in accordance with claim 1, wherein the operation of detecting discrepancies includes detecting and recording changes made in the entered data after an initial entry in the accounting software program or the practice management software program.

5. A method in accordance with claim 1, wherein the operation of detecting discrepancies includes comparing and recording differences between the entered data and a predetermined acceptable range of values.

6. A method in accordance with claim 5, wherein the predetermined acceptable range is determined by a fee per service schedule.

7. A method in accordance with claim 1, wherein the operation of notifying a responsible party includes sending an electronically transmitted message selected from the group consisting of an email, an instant message, a text message, a voice message, and combinations thereof.

8. A method in accordance with claim 1, wherein the operation of notifying a responsible party includes providing the responsible party with instructions to review the acquired data and the stored detected changes data and resolve discrepancies if differences are found between the acquired data, the stored detected changes data, and a predetermined acceptable range of values determined by a fee per service schedule.

9. A method in accordance with claim 1, further comprising:

configuring the monitoring software to allow the responsible party to direct the monitoring software to populate an affidavit and police report with the acquired data, the stored detected changes data, and the predetermined acceptable range data.

10. A method in accordance with claim 1, further comprising notifying the responsible party that no discrepancies have been found.

11. A method for detecting fraudulent transactions;

comprising;

a) enabling a monitoring software program to access entries into an accounting software program;

b) enabling a monitoring software program to access entries into a practice management software program;

c) configuring the monitoring program to compare and verify entries into the accounting program and practice management program during regular intervals to detect any unusual activity and to store the unusual activity as data for later review;

d) notifying a responsible party of the status of the comparison and verification by the monitoring program;

e) providing access to the responsible party to data relevant to the unusual activity; and

f) allowing the responsible party to resolve unusual activity detected and stored by the monitoring software.

12. A method in accordance with claim 11, wherein the operation of notifying the responsible party includes sending a message to the responsible party that no unusual activity has been detected.

13. A method in accordance with claim 11 wherein the operation of notifying the responsible party includes sending a message to the responsible party that the stored unusual activity data needs to be reviewed if unusual activity is detected.

14. A method in accordance with claim 11, further comprising configuring the monitoring program to organize data from the accounting program and the practice management program into categories selected from the group consisting of aging accounts receivable, top procedures performed, client vitae, unusual activity as detected throughout a monitoring period, and combinations thereof.

15. A method in accordance with claim 11, wherein the operation of providing access to the responsible party of data relevant to the unusual activity includes identifying employees who entered the data, and identifying types of transactions involved in the unusual activity.

16. A method in accordance with claim 11, wherein the operation of allowing the responsible party to resolve the unusual activity includes deleting unusual transaction data if desired, and saving unusual transaction data for later use if unusual activity is unresolvable.

17. A method in accordance with claim 16, further comprising:

creating a police report and affidavit used in reporting and prosecuting embezzlement crimes with the saved unusual transaction data.

18. A method for detecting fraudulent transactions;

comprising;

a) enabling a monitoring software program to access entries into an accounting software program;

b) enabling a monitoring software program to access entries into a practice management software program;

b) configuring the monitoring program to compare and verify entries into the accounting program and the practice management program during regular intervals to detect any unusual activity and to store the unusual activity as data for later review;

c) notifying a responsible party of the status of the comparison and verification by the monitoring program;

d) providing access to the responsible party to data relevant to the unusual activity;

e) allowing the responsible party to resolve unusual activity flagged by the monitoring software by deleting unusual transaction data if desired, and saving unusual transaction data for later use if unusual activity is unresolvable; and

f) creating a police report and affidavit used in reporting and prosecuting embezzlement crimes with the saved unusual transaction data.

19. A method in accordance with claim 18, wherein the operation of creating a police report and affidavit further includes accessing a report wizard in the monitoring software program.

20. A method in accordance with claim 18, wherein notifying a responsible party further comprises determining a type or degree of the unusual activity to determine whether to immediately notify the responsible party or to delay notifying the responsible party.