EP3497589A1 - System and method for identifying unclaimed electronic documents - Google Patents
System and method for identifying unclaimed electronic documentsInfo
- Publication number
- EP3497589A1 EP3497589A1 EP17840055.2A EP17840055A EP3497589A1 EP 3497589 A1 EP3497589 A1 EP 3497589A1 EP 17840055 A EP17840055 A EP 17840055A EP 3497589 A1 EP3497589 A1 EP 3497589A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- electronic document
- unclaimed
- data
- identifying
- electronic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
- G06F16/86—Mapping to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/047—Payment circuits using payment protocols involving electronic receipts
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/123—Tax preparation or submission
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
- G06V30/40—Document-oriented image-based pattern recognition
- G06V30/41—Analysis of document content
- G06V30/418—Document matching, e.g. of document images
Definitions
- the present disclosure relates generally to analyzing electronic documents, and more particularly to identifying unclaimed electronic documents.
- a customer may input credit card information pursuant to a payment, and the merchant may verify the credit card information in real-time before authorizing the sale. The verification typically includes determining whether the provided information is valid (i.e., that a credit card number, expiration date, PIN code, and/or customer name match known information).
- a purchase order may be generated for the customer.
- the purchase order provides evidence of the order such as, for example, a purchase price, goods and/or services ordered, and the like.
- an invoice for the order may be generated. While the purchase order is usually used to indicate which products are requested and an estimate or offering for the price, the invoice is usually used to indicate which products were actually provided and the final price for the products. Frequently, the purchase price as demonstrated by the invoice for the order is different from the purchase price as demonstrated by the purchase order. As an example, if a guest at a hotel initially orders a 3-night stay but ends up staying a fourth night, the total price of the purchase order may reflect a different total price than that of the subsequent invoice.
- existing image recognition solutions may be unable to accurately identify some or all special characters (e.g., "!,” “@,” “#,” “$,” “ ⁇ ,” “%,” “&,” etc.). As an example, some existing image recognition solutions may inaccurately identify a dash included in a scanned receipt as the number “1 .” As another example, some existing image recognition solutions cannot identify special characters such as the dollar sign, the yen symbol, etc.
- such solutions may face challenges in preparing recognized information for subsequent use. Specifically, many such solutions either produce output in an unstructured format, or can only produce structured output if the input electronic documents are specifically formatted for recognition by an image recognition system. The resulting unstructured output typically cannot be processed efficiently. In particular, such unstructured output may contain duplicates, and may include data that requires subsequent processing prior to use.
- VAT The value-added tax, or VAT, is a broadly-based consumption tax applied to goods and services purchased in some countries.
- VATs paid abroad may be reclaimed by submitting a VAT reclaim request along with evidence of the purchase.
- Many companies have employees purchase goods and services that may be subject to VATs and, therefore, seek to reclaim those VATs.
- VATs may go unclaimed. For example, employees may not be sufficiently motivated to apply for reclaims at the airport, or companies may be concerned about punishments for accidentally submitting requests for reclaiming duplicate VATs (i.e., two different requests seeking to reclaim VATs paid on the same transaction).
- VATs may be reclaimed retroactively, they are nevertheless typically not ultimately reclaimed.
- Certain embodiments disclosed herein include a method for identifying unclaimed electronic documents among at least one electronic document, each electronic document including at least partially unstructured data.
- the method comprises: analyzing each electronic document to determine at least one transaction parameter of the electronic document; creating a template for each electronic document, wherein each template is a structured dataset including the at least one transaction parameter determined for the electronic document; and determining whether each electronic document is unclaimed, wherein determining whether an electronic document is unclaimed further comprises comparing at least a portion of the template created for the electronic document to identifying data of a plurality of previous reclaims.
- Certain embodiments disclosed herein also include a non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to perform a process for identifying unclaimed electronic documents among at least one electronic document, each electronic document including at least partially unstructured data the process comprising: analyzing each electronic document to determine at least one transaction parameter of the electronic document; creating a template for each electronic document, wherein each template is a structured dataset including the at least one transaction parameter determined for the electronic document; and determining whether each electronic document is unclaimed, wherein determining whether an electronic document is unclaimed further comprises comparing at least a portion of the template created for the electronic document to identifying data of a plurality of previous reclaims.
- Certain embodiments disclosed herein also include a system for identifying unclaimed electronic documents among at least one electronic document, each electronic document including at least partially unstructured data.
- the system comprises: a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: analyze each electronic document to determine at least one transaction parameter of the electronic document; create a template for each electronic document, wherein each template is a structured dataset including the at least one transaction parameter determined for the electronic document; and determine whether each electronic document is unclaimed, wherein determining whether an electronic document is unclaimed further comprises comparing at least a portion of the template created for the electronic document to identifying data of a plurality of previous reclaims.
- Figure 1 is a network diagram utilized to describe the various disclosed embodiments.
- Figure 2 is a schematic diagram of a validation system according to an embodiment.
- Figure 3 is a flowchart illustrating a method for identifying unclaimed electronic documents according to an embodiment.
- Figure 4 is a flowchart illustrating a method for creating a dataset based on at least one electronic document according to an embodiment.
- the various disclosed embodiments include a method and system for identifying unclaimed electronic documents.
- datasets are created based on electronic documents.
- a template of transaction attributes is created based on each dataset.
- a certainty score may be determined based on the template created for the electronic document and templates of the reclaimed electronic documents.
- An electronic reclaim document may be generated for each electronic document having a certainty score above a threshold.
- the disclosed embodiments allow for unclaimed electronic documents illustrating, for example, evidence of transactions. More specifically, the disclosed embodiments include providing structured dataset templates for electronic documents, thereby allowing for more accurately identifying unclaimed electronic documents that are unstructured, semi- structured, or otherwise lacking a known structure. For example, image files showing invoices that were not previously submitted for reclaim may be determined from among a group of image files showing invoices.
- Fig. 1 shows an example network diagram 100 utilized to describe the various disclosed embodiments.
- an unclaimed electronic document identifier 120 an enterprise system 130, a database 140, and a plurality of data sources 150-1 through 150-N (hereinafter referred to individually as a data source 150 and collectively as data sources 150, merely for simplicity purposes), are communicatively connected via a network 1 10.
- the network 1 10 may be, but is not limited to, a wireless, cellular or wired network, a local area network (LAN), a wide area network (WAN), a metro area network (MAN), the Internet, the worldwide web (WWW), similar networks, and any combination thereof.
- LAN local area network
- WAN wide area network
- MAN metro area network
- WWW worldwide web
- the enterprise system 130 is associated with an enterprise, and may store data related to purchases made by the enterprise or representatives of the enterprise as well as data related to the enterprise itself.
- the enterprise may be, but is not limited to, a business whose employees may purchase goods and services subject to VAT taxes while abroad.
- the enterprise system 130 may be, but is not limited to, a server, a database, an enterprise resource planning system, a customer relationship management system, or any other system storing relevant data.
- the data stored by the enterprise system 130 may include, but is not limited to, electronic documents (e.g., an image file showing, for example, a scan of an invoice, a text file, a spreadsheet file, etc.). Each electronic document may show, e.g., an evidence of a transaction such as an invoice, a tax receipt, a purchase number record, and the like. Data included in each electronic document may be structured, semi-structured, unstructured, or a combination thereof. The structured or semi-structured data may be in a format that is not recognized by the identifier 120 and, therefore, may be treated as unstructured data. In some implementations, at least some of the electronic documents may be received or retrieved from one or more client devices (not shown) associated with the enterprise.
- client devices not shown
- the database 140 may store electronic reclaim documents generated by the identifier 120.
- the data sources 150 store at least data of previously VAT reclaims.
- the data sources 150 may include, but are not limited to, servers or devices of merchants, tax authority servers, accounting servers, a database associated with an enterprise, and the like.
- the data of the previous reclaims may include unstructured electronic documents (e.g., the previously reclaimed electronic documents), or other data indicating parameters of the transactions for which reclaims have been obtained.
- the identifier 120 is configured to create templates based on transaction parameters identified using machine vision electronic documents. Each electronic document indicates information related to a transaction. In a further embodiment, the identifier 120 may be configured to retrieve the electronic documents from, e.g., the enterprise system 130.
- the identifier 120 is configured to create datasets based on electronic documents including data at least partially lacking a known structure (e.g., unstructured data, semi-structured data, or structured data having an unknown structure).
- the identifier 120 may be further configured to utilize optical character recognition (OCR) or other image processing to determine data in the electronic document.
- OCR optical character recognition
- the identifier 120 may therefore include or be communicatively connected to a recognition processor (e.g., the recognition processor 235, Fig. 2).
- the identifier 120 is configured to analyze the created datasets to identify transaction parameters related to transactions indicated in the electronic documents and to create a template based on each created dataset for an electronic document.
- Each template is a structured dataset including the identified transaction parameters for a transaction. More specifically, each template may include a data element in each field, where each transaction parameter is a value of the data element.
- Using structured templates for completing electronic documents allows for more efficient and accurate identification of unclaimed electronic documents than, for example, by utilizing unstructured data. Specifically, data of previous reclaims may be compared to data of the electronic documents with respect to fields of the structured templates. Further certainty scores indicating likelihood that reclaims will be successful may be determined with respect to data in specific fields of the templates.
- the identifier 120 is configured to determine whether any of the electronic documents are unclaimed.
- An electronic document may be unclaimed when a set of uniquely identifying transaction parameters of the electronic document (e.g., as indicated in the created template for the electronic document) do not match any sets of uniquely identifying transaction parameters of a previous reclaim, or do not match above a predetermined threshold.
- an electronic document indicating a payment of 200 Euros made by an employee John Smith on July 25, 2016, may be unclaimed when no previous reclaim was based on a transaction having a price of 200 Euros made by John Smith on July 25, 2016.
- an electronic document indicating a transaction identifier of "123456" may be unclaimed when no previous reclaim was based on an electronic document including a transaction identifier of "123456.”
- the identifier 120 is configured to determine a certainty score for each unclaimed electronic document.
- Each certainty score indicates a likelihood that a reclaim requested based on the electronic document will be successful.
- the certainty scores may be determined by comparing data of the created templates to data of previous reclaims. More specifically, the certainty scores may be determined with respect transaction parameters such as, for example, date of transaction, description of goods or services purchased, and the like. For example, a certainty score may be determined for an unclaimed invoice for a transaction made in January 2015 for a purchase of a hotel stay with respect to 100 previously reclaimed electronic documents made in January 2015. As a non-limiting example, if only 2 out of 10 previously reclaimed electronic documents related to purchases of hotel stays were successfully reclaimed, a certainty score of 0.1 may be determined.
- the identifier 120 is configured to compare each certainty score to a predetermined certainty threshold. For each electronic document having a certainty score above the certainty threshold, the identifier 120 may be configured to determine that the electronic document should have been reclaimed and, accordingly, may be configured to generate an electronic reclaim document based on the template for the electronic document. The generated electronic reclaim documents and corresponding unclaimed electronic documents may be sent to, for example, one of the data sources 150 (e.g., a server of a tax authority).
- the data sources 150 e.g., a server of a tax authority
- Fig. 2 is an example schematic diagram of the identifier 120 according to an embodiment.
- the identifier 120 includes a processing circuitry 210 coupled to a memory 215, a storage 220, and a network interface 240.
- the identifier 120 may include an optical character recognition (OCR) processor 230.
- OCR optical character recognition
- the components of the identifier 120 may be communicatively connected via a bus 250.
- the processing circuitry 210 may be realized as one or more hardware logic components and circuits.
- illustrative types of hardware logic components include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), Application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.
- the memory 215 may be volatile (e.g., RAM, etc.), non-volatile (e.g., ROM, flash memory, etc.), or a combination thereof.
- computer readable instructions to implement one or more embodiments disclosed herein may be stored in the storage 220.
- the memory 215 is configured to store software.
- Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code).
- the instructions when executed by the one or more processors, cause the processing circuitry 210 to perform the various processes described herein. Specifically, the instructions, when executed, cause the processing circuitry 210 to complete electronic documents, as discussed herein.
- the storage 220 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs), or any other medium which can be used to store the desired information.
- flash memory or other memory technology
- CD-ROM Compact Discs
- DVDs Digital Versatile Disks
- the OCR processor 230 may include, but is not limited to, a feature and/or pattern recognition processor (RP) 235 configured to identify patterns, features, or both, in unstructured data sets. Specifically, in an embodiment, the OCR processor 230 is configured to identify at least characters in the unstructured data. The identified characters may be utilized to create a dataset including data required for verification of a request.
- RP pattern recognition processor
- the network interface 240 allows the identifier 120 to communicate with the enterprise system 130, the database 140, the data sources 150, or a combination of, for the purpose of, for example, collecting metadata, retrieving data, storing data, and the like.
- Fig. 3 is an example flowchart 300 illustrating a method for completing an electronic document according to an embodiment.
- the method may be performed by an unclaimed electronic document identifier (e.g., the identifier 120).
- the electronic document may be an electronic receipt (e.g., an image showing a scanned receipt).
- datasets are created based on electronic documents including information related to transactions.
- the electronic documents may include, but is not limited to, unstructured data, semi-structured data, structured data with structure that is unanticipated or unannounced, or a combination thereof.
- S310 may further include analyzing each electronic document using optical character recognition (OCR) to determine data in the electronic document, identifying key fields in the data, identifying values in the data, or a combination thereof.
- OCR optical character recognition
- analyzing each dataset may include, but is not limited to, determining transaction parameters such as, but not limited to, at least one entity identifier (e.g., a consumer enterprise identifier, a merchant enterprise identifier, or both), information related to the transaction (e.g., a date, a time, a price, a type of good or service sold, etc.), or both.
- entity identifier e.g., a consumer enterprise identifier, a merchant enterprise identifier, or both
- information related to the transaction e.g., a date, a time, a price, a type of good or service sold, etc.
- analyzing each dataset may also include identifying the transaction based on the dataset.
- Each template is created based on each dataset.
- Each template may be, but is not limited to, a data structure including a plurality of fields.
- the fields may include the identified transaction parameters.
- the fields may be predefined.
- Creating templates from electronic documents allows for faster processing due to the structured nature of the created templates. For example, query and manipulation operations may be performed more efficiently on structured datasets than on datasets lacking such structure. Further, identifying incomplete date elements in structured templates may result in more accurate identification of incomplete data elements based on unstructured data. Additionally, searching for complementary data based on incomplete data elements identified in structured templates may be performed with respect to fields of the templates, thereby more accurately identifying complementary data.
- S340 includes comparing data of the template for the electronic document to data associated with previous reclaims. Based on the comparison, it may be determined whether the transaction indicated in the electronic document matches any of the previously reclaimed transactions. To this end, the comparison may include comparing one or more uniquely identifying transaction parameters for the electronic document to transaction parameters associated with each of the previous reclaims, where an electronic document is unclaimed when identifying transaction parameters of the electronic document do not match identifying transaction parameters of any of the previous reclaims.
- a template may be created for an electronic document associated with each previous reclaim, and values in one or more fields of the unclaimed electronic document template may be compared to values in corresponding fields of each previous reclaim template.
- a certainty score is determined for the electronic document.
- the certainty score indicates a likelihood that the unclaimed electronic document can be successfully reclaimed, and may be determined based on the unclaimed electronic document and data of previous reclaims.
- the certainty score may be determined based on one or more transaction parameters that are common to the unclaimed electronic document and one or more of the previous reclaims.
- the certainty score may be determined based further on the number of previous reclaims sharing common transaction parameters, the total number of previous reclaims, or both.
- a certainty score of 7 may be determined an unclaimed electronic document indicating the same time period and expense description as multiple previous reclaims among 30 previous reclaims.
- the certainty score for the electronic document is compared to a predetermined certainty threshold.
- the certainty threshold may establish a minimum certainty score that indicates that an electronic document should be reclaimed.
- an electronic reclaim document is generated for the electronic document.
- the electronic reclaim document may include the unclaimed electronic document and may indicate a request for a reclaim.
- the electronic reclaim document may further include one or more required transaction parameters for reclaiming VATs paid for the transaction indicated in the electronic document.
- Fig. 4 is an example flowchart S310 illustrating a method for creating a dataset based on an electronic document according to an embodiment.
- the electronic document is obtained.
- Obtaining the electronic document may include, but is not limited to, receiving the electronic document (e.g., receiving a scanned image) or retrieving the electronic document (e.g., retrieving the electronic document from a consumer enterprise system, a merchant enterprise system, or a database).
- the electronic document is analyzed.
- the analysis may include, but is not limited to, using optical character recognition (OCR) to determine characters in the electronic document.
- OCR optical character recognition
- the key field may include, but are not limited to, merchant's name and address, date, currency, good or service sold, a transaction identifier, an invoice number, and so on.
- An electronic document may include unnecessary details that would not be considered to be key values. As an example, a logo of the merchant may not be required and, thus, is not a key value.
- a list of key fields may be predefined, and pieces of data that may match the key fields are extracted. Then, a cleaning process is performed to ensure that the information is accurately presented. For example, if the OCR would result in a data presented as "121 1212005", the cleaning process will convert this data to 12/12/2005. As another example, if a name is presented as "Mo$den”, this will change to "Mosden”.
- the cleaning process may be performed using external information resources, such as dictionaries, calendars, and the like.
- S430 results in a complete set of the predefined key fields and their respective values.
- a structured dataset is generated.
- the generated dataset includes the identified key fields and values.
- any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations are generally used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise, a set of elements comprises one or more elements.
- the phrase "at least one of” followed by a listing of items means that any of the listed items can be utilized individually, or any combination of two or more of the listed items can be utilized. For example, if a system is described as including "at least one of A, B, and C," the system can include A alone; B alone; C alone; A and B in combination; B and C in combination; A and C in combination; or A, B, and C in combination.
- the various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof.
- the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices.
- the application program may be uploaded to, and executed by, a machine comprising any suitable architecture.
- the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs"), a memory, and input/output interfaces.
- CPUs central processing units
- the computer platform may also include an operating system and microinstruction code.
- a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662371771P | 2016-08-07 | 2016-08-07 | |
US15/361,934 US20170154385A1 (en) | 2015-11-29 | 2016-11-28 | System and method for automatic validation |
PCT/US2017/045488 WO2018031402A1 (en) | 2016-08-07 | 2017-08-04 | System and method for identifying unclaimed electronic documents |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3497589A1 true EP3497589A1 (en) | 2019-06-19 |
EP3497589A4 EP3497589A4 (en) | 2020-04-15 |
Family
ID=61162477
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17840055.2A Withdrawn EP3497589A4 (en) | 2016-08-07 | 2017-08-04 | System and method for identifying unclaimed electronic documents |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3497589A4 (en) |
WO (1) | WO2018031402A1 (en) |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5956722A (en) * | 1997-09-23 | 1999-09-21 | At&T Corp. | Method for effective indexing of partially dynamic documents |
US7363308B2 (en) * | 2000-12-28 | 2008-04-22 | Fair Isaac Corporation | System and method for obtaining keyword descriptions of records from a large database |
US7818657B1 (en) * | 2002-04-01 | 2010-10-19 | Fannie Mae | Electronic document for mortgage transactions |
US20090193210A1 (en) * | 2008-01-29 | 2009-07-30 | Hewett Jeffrey R | System for Automatic Legal Discovery Management and Data Collection |
US8774516B2 (en) * | 2009-02-10 | 2014-07-08 | Kofax, Inc. | Systems, methods and computer program products for determining document validity |
-
2017
- 2017-08-04 WO PCT/US2017/045488 patent/WO2018031402A1/en unknown
- 2017-08-04 EP EP17840055.2A patent/EP3497589A4/en not_active Withdrawn
Also Published As
Publication number | Publication date |
---|---|
WO2018031402A1 (en) | 2018-02-15 |
EP3497589A4 (en) | 2020-04-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11062132B2 (en) | System and method for identification of missing data elements in electronic documents | |
US20170323006A1 (en) | System and method for providing analytics in real-time based on unstructured electronic documents | |
US11138372B2 (en) | System and method for reporting based on electronic documents | |
US10509811B2 (en) | System and method for improved analysis of travel-indicating unstructured electronic documents | |
US20170169292A1 (en) | System and method for automatically verifying requests based on electronic documents | |
US20180011846A1 (en) | System and method for matching transaction electronic documents to evidencing electronic documents | |
US20170323157A1 (en) | System and method for determining an entity status based on unstructured electronic documents | |
EP3494495A1 (en) | System and method for completing electronic documents | |
US20180018312A1 (en) | System and method for monitoring electronic documents | |
US20180025225A1 (en) | System and method for generating consolidated data for electronic documents | |
US20180046663A1 (en) | System and method for completing electronic documents | |
US20180025224A1 (en) | System and method for identifying unclaimed electronic documents | |
US20170161315A1 (en) | System and method for maintaining data integrity | |
US10387561B2 (en) | System and method for obtaining reissues of electronic documents lacking required data | |
US20180025438A1 (en) | System and method for generating analytics based on electronic documents | |
WO2018027130A1 (en) | System and method for reporting based on electronic documents | |
WO2017201012A1 (en) | Providing analytics in real-time based on unstructured electronic documents | |
US20170169519A1 (en) | System and method for automatically verifying transactions based on electronic documents | |
WO2017142618A1 (en) | Automatic verification of requests based on electronic documents | |
US20170323106A1 (en) | System and method for encrypting data in electronic documents | |
EP3497589A1 (en) | System and method for identifying unclaimed electronic documents | |
WO2017201292A1 (en) | System and method for encrypting data in electronic documents | |
WO2017142615A1 (en) | System and method for maintaining data integrity | |
US20170193609A1 (en) | System and method for automatically monitoring requests indicated in electronic documents | |
US20170323395A1 (en) | System and method for creating historical records based on unstructured electronic documents |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20190222 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20200317 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 40/00 20120101ALI20200311BHEP Ipc: G06Q 20/04 20120101ALI20200311BHEP Ipc: G06K 9/62 20060101ALI20200311BHEP Ipc: G06Q 20/38 20120101ALI20200311BHEP Ipc: G06F 16/84 20190101ALI20200311BHEP Ipc: G06Q 30/04 20120101ALI20200311BHEP Ipc: G06Q 10/10 20120101AFI20200311BHEP Ipc: G06K 9/00 20060101ALI20200311BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20201014 |