SYSTEM AND METHOD FOR INTEGRATED TRAVEL AND EXPENSE MANGEMENT AND DETECTING DUPLICATE TRAVEL PATH INFORMATION

• US 20130218615A1
• Filed: 03/15/2013
• Published: 08/22/2013
• Est. Priority Date: 02/26/2003
• Status: Abandoned Application

• Current Assignee: Concur Technologies Incorporated (SAP SE)
• Original Assignee: Concur Technologies Incorporated (SAP SE)
• Inventors: FREDERICKS, MICHAEL, OLLENBERGER, BRIAN, SILVERIA, LISA, DENMARK, RICHARD, DUNNICK, JOSEPH, GORODNICHEV, VALERY, ARMSTRONG, JEANNINE
• Application Number:
  US13/842,913
• Publication Number:
  US 20130218615A1
• Time in Patent Office: Days
• US Class Current: 705/6
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/10 Tax strategies
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Methods and systems may retrieve travel data records corresponding to travel requests; retrieve expense data records reflecting expense transactions, compare the expense data records to the travel data records, and determine a likelihood that the expense data records match the travel data records. Methods and systems may also detect possible duplicate travel path information by obtaining a set of travel paths with at least two travel paths, breaking each travel path into at least one segment comprising a single unit of travel with an origin and a destination, comparing each leg in each travel path to each leg in every other travel path to determine whether any travel paths are duplicates, and listing any segment paths that are possible duplicates.

Claims

1. A computerized method for integrating travel and expense information, comprising:

receiving, by a server module, travel request data and/or travel reservation data corresponding to a travel event type, the request and/or reservation data further including travel request and/or reservation attributes and a set of travel paths comprising at least two travel paths;

breaking, by the server module, each travel path into at least one leg, wherein the at least one leg comprises at least one segment, wherein the at least one segment comprises a single unit of travel with an origin and a destination;

comparing, by the server module, each leg in each travel path to each leg in every other travel path in the set of travel paths to determine whether any travel paths are duplicates by determining whether any segments in any legs are similar by determining whether any segments have the same origin and/or the same destination as other segments in other legs in the set of travel paths wherein the legs are defined as computerized sequences of segment origins and destinations, and at least one computerized subsequence is utilized to find common segment origins and destinations;

generating, by the server module, a travel request record, wherein the travel record includes the travel request and/or travel reservation information and any travel paths that are possible duplicates;

receiving from a plurality of sources, by the server module, travel expense transaction data, the travel expense transaction data further comprising an expense transaction attribute;

generating, by the server module, a travel expense transaction record, wherein the travel expense transaction record comprises the expense transaction data;

designating, by a matching module, an attribute included in the expense transaction record for comparison to a corresponding attribute included in the travel request record;

retrieving, by the matching module, pre-determined matching criteria corresponding to the travel event type and to the designated expense transaction attribute, wherein at least one criterion describes how to evaluate travel paths that are possible duplicates;

comparing, by the matching module, the expense transaction attribute to any corresponding request attribute using the pre-determined matching criteria and determining an initial matching score based on the comparison;

iteratively repeating the comparisons for each attribute included in the expense transaction record and the travel request record to produce an adjusted matching score;

determining, by the matching module, whether the total matching score exceeds a first pre-determined threshold defined by the pre-determined matching criteria for the travel event type and the travel request attribute;

designating, by the matching module, the expense transaction record and the travel request record as a positive match when the total matching score is above the first threshold;

determining, by the matching module, whether the total matching score does not exceed the first pre-determined threshold defined by the pre-determined matching criteria for the travel event type, but does exceed a second pre-determined threshold, the second pre-determined threshold also defined by the pre-determined matching criteria for the travel event type; and

designating, by the matching module, the expense transaction record and the travel request record as a possible match when the total matching score does not exceed the first pre-determined threshold but is above the second threshold.

2. The method of claim 1, wherein the listing of any travel paths that are possible duplicates further comprises:

at the at least one server module, constructing at least one similar leg graph where nodes of the leg graph represent origins and destinations of legs.

3. The method of claim 1, further comprising:

at the at least one server module, allowing the user to select the correct travel path from a list of travel paths that are possible duplicates.

4. The method of claim 1, wherein the possible duplicates are sorted according to which travel path information was imported into the system most recently.

5. The method of claim 3, further comprising:

at the at least one server module, resolving any duplicate similar travel paths.

6. The method of claim 1, wherein the at least two travel paths compare:

air travel, car travel, rail travel, or bus travel, or any combination thereof.

7. The method of claim 1, further comprising:

determining whether any legs are similar to any other legs by determining whether any segments in any legs contain at least one start point and/or at least one end point.

8. The method of claim 1, further comprising:

at the at least one server module, excluding any travel path that incorporates more than zero but fewer than all possible segments from more than one reservation.

9. A computerized system for integrating travel and expense information, comprising:

a processor configured for;

receiving travel request data and/or travel reservation data corresponding to a travel event type, the request and/or reservation data further including travel request and/or reservation attributes and a set of travel paths comprising at least two travel paths;

breaking each travel path into at least one leg, wherein the at least one leg comprises at least one segment, wherein the at least one segment comprises a single unit of travel with an origin and a destination;

comparing each leg in each travel path to each leg in every other travel path in the set of travel paths to determine whether any travel paths are duplicates by determining whether any segments in any legs are similar by determining whether any segments have the same origin and/or the same destination as other segments in other legs in the set of travel paths wherein the legs are defined as computerized sequences of segment origins and destinations, and at least one computerized subsequence is utilized to find common segment origins and destinations;

generating a travel request record, wherein the travel record includes the travel request and/or travel reservation information and any travel paths that are possible duplicates;

receiving from a plurality of sources, travel expense transaction data, the travel expense transaction data further comprising an expense transaction attribute;

generating a travel expense transaction record, wherein the travel expense transaction record comprises the expense transaction data;

designating an attribute included in the expense transaction record for comparison to a corresponding attribute included in the travel request record;

retrieving pre-determined matching criteria corresponding to the travel event type and to the designated expense transaction attribute, wherein at least one criterion describes how to evaluate travel paths that are possible duplicates;

comparing the expense transaction attribute to any corresponding request attribute using the pre-determined matching criteria and determining an initial matching score based on the comparison;

iteratively repeating the comparisons for each attribute included in the expense transaction record and the travel request record to produce an adjusted matching score;

determining whether the total matching score exceeds a first pre-determined threshold defined by the pre-determined matching criteria for the travel event type and the travel request attribute;

designating the expense transaction record and the travel request record as a positive match when the total matching score is above the first threshold;

determining whether the total matching score does not exceed the first pre-determined threshold defined by the pre-determined matching criteria for the travel event type, but does exceed a second pre-determined threshold, the second pre-determined threshold also defined by the pre-determined matching criteria for the travel event type; and

designating the expense transaction record and the travel request record as a possible match when the total matching score does not exceed the first pre-determined threshold but is above the second threshold.

10. The system of claim 9, wherein the listing of any travel paths that are possible duplicates further comprises:

constructing at least one similar leg graph where nodes of the leg graph represent origins and destinations of legs.

11. The system of claim 9, wherein the processor is further configured for:

allowing the user to select the correct travel path from a list of travel paths that are possible duplicates.

12. The system of claim 9, wherein the possible duplicates are sorted according to which travel path information was imported into the system most recently.

13. The system of claim 11, wherein the processor is further configured for:

resolving any duplicate similar travel paths.

14. The system of claim 9, wherein the at least two travel paths compare:

air travel, car travel, rail travel, or bus travel, or any combination thereof.

15. The system of claim 9, wherein the processor is further configured for:

determining whether any legs are similar to any other legs by determining whether any segments in any legs contain at least one start point and/or at least one end point.

16. The system of claim 9, wherein the processor is further configured for:

excluding any travel path that incorporates more than zero but fewer than all possible segments from more than one reservation.