Unique Instance Identifiers for Tax Return Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing tax return preparation systems fail to uniquely identify and distinguish multiple instances of the same schema element, such as different Form W-2s from various employers, leading to confusion and errors in data processing and synchronization across different computing devices.

Innovation Solution

A computer-implemented method and system that generates unique instance identifiers for each instance of a schema element, allowing for differentiation and synchronization of electronic tax return data, using a UI controller, logic agent, and data store to manage and process these identifiers, ensuring accurate data handling and synchronization across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple instances of the same schema element are processed without unique identification, then data processing is simpler, but data accuracy and synchronization are compromised

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data processing system by introducing unique instance identifiers that distinguish individual instances of schema elements. Each instance of a tax form or data element receives a unique identifier, allowing the system to track and process multiple instances separately while maintaining overall system organization through the identifier structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The instance identifier acts as an intermediary between the schema element and the processing components. This intermediary enables accurate tracking, synchronization, and differentiation of multiple instances without requiring fundamental changes to the core processing logic, thus improving reliability while adding manageable complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If instance identifiers are generated and tracked across multiple components, then synchronization across devices is improved, but information loss and processing overhead increase

Engineering Contradiction:
Improvedata synchronization accuracyVSAvoidprocessing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

Instance identifiers are generated in advance when schema elements are created, rather than being assigned during processing or synchronization. This preliminary assignment ensures that all subsequent operations can reference pre-established identifiers, eliminating the need for complex matching algorithms and reducing processing time during synchronization operations.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If unique instance identifiers are implemented, then differentiation of multiple instances is improved, but system complexity increases

Engineering Contradiction:
Improveinstance identification precisionVSAvoidsystem architecture complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies local quality by making each instance identifiable through its unique identifier while keeping the overall schema structure unchanged. The differentiation is localized to the instance level rather than requiring global structural changes, allowing precise identification without fundamentally complicating the system architecture.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10977743B1Computer implemented methods systems and articles of manufacture for instance and suggestion differentiation during preparation of electronic tax return
Publication Date: 2021.04.13 INTUIT INC
  • US10977743B1 patent drawing
  • US10977743B1 patent drawing
  • US10977743B1 patent drawing

AI summary

Computer-implemented methods, systems and articles of manufacture for uniquely identifying instances during preparation of an electronic tax return. A user interface (UI) controller receives inputs related to respective electronic tax return data for the same element of a schema, e.g., different data for two different Form W-2 documents. The UI controller generates different instance identifiers, which are written to a data store with the electronic tax return data. A first instance for the first electronic tax return data is generated from the schema element for Form W-2 and identified by a first instance identifier, and a second instance for the second electronic tax return data is generated from the same schema element and identified by the different, second instance identifier. The instance identifiers are used by a logic agent that generates non-binding suggestions for the UI controller indicating a question nor topic to present to the user.