Instrument Code Matching for Automated Transaction Disambiguation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in accurately disambiguating transactions when traditional instruments like checks are used, as third-party systems often provide deposit/withdrawal information that lacks context, leading to ambiguity and requiring manual human intervention for record updates.

Innovation Solution

A method is introduced that involves generating a unique code associated with a transaction record, which is then printed on the instrument and verified upon deposit, allowing automated updating of the transaction status without human input by matching the code in the instrument's image with the record.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual human intervention is used to disambiguate transactions, then accuracy can be maintained, but productivity decreases and time is lost

Engineering Contradiction:
Improvetransaction disambiguation accuracyVSAvoidrecord updating efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system enables automated self-service by having the instrument image and deposited amount automatically populate the payment record. The code on the instrument serves as a self-identifying marker that links the physical instrument to its corresponding electronic record without requiring human intervention for matching or disambiguation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-generating unique codes and embedding them on instruments before they are processed. This preliminary coding allows the system to automatically identify and match instruments to transactions during clearing, eliminating the need for manual disambiguation later in the process.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If no unique identifier is used on instruments, then device complexity is reduced, but measurement precision decreases making it difficult to match instruments to transactions

Engineering Contradiction:
Improveinstrument-to-transaction matching accuracyVSAvoidinstrument structure
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system applies local quality by placing a concentrated unique identifier (code) at a specific location on the instrument. This localized code provides all the necessary identification information in a compact form, enabling precise matching without requiring complex instrumentation or multiple identification features across the entire instrument.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If third-party systems provide deposit information without context, then ease of operation is improved for external systems, but loss of information occurs making disambiguation difficult

Engineering Contradiction:
Improvedata import simplicityVSAvoidtransaction context
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The unique code on the instrument acts as an intermediary that bridges the gap between the physical instrument and the electronic record system. This code carries identification information that allows the system to automatically link deposited instruments to their corresponding transactions, preserving transaction context even when third-party systems import data without contextual information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10803139B2Instrument disambiguation to facilitate electronic data consolidation
Publication Date: 2020.10.13 INTUIT INC
  • US10803139B2 patent drawing
  • US10803139B2 patent drawing
  • US10803139B2 patent drawing

AI summary

Embodiments presented herein provide systems and methods for disambiguating the identity of a record to which information imported from a third-party data source pertains. For example, in one embodiment, a record-storage service creates a record of a transaction between a first entity and a second entity. Upon receiving an indication that an instrument will be used to transfer a value for the transaction, the record-storage service associates a code to be printed on the instrument with the record and sends the code to an application that will be used to generate the instrument. Subsequently, the record-storage service receives information imported from electronic records provided by a third-party institution. The information also includes a code provided on the instrument and a status. Upon determining that the code provided on the instrument matches the code associated with the record, the record-storage service updates the record to reflect the status.