Custom Form Template Mapping in Financial Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional financial management systems require users to switch to native form templates, leading to inconvenience, increased error likelihood, and significant time investment, hindering market growth and user acceptance.

Innovation Solution

A financial management system that generates customized form templates by mapping user-provided data to system data fields, allowing users to maintain their preferred form formats and reducing the need for template re-creation, using techniques like naïve Bayes' classifiers and conditional probabilities to identify relevant data fields.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional financial management systems require users to switch to native form templates, then the system maintains standardized data processing, but user convenience deteriorates and time investment increases

Engineering Contradiction:
Improvestandardized data processingVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system copies the user's existing custom form template and creates a standardized version by mapping data fields from the custom template to the standardized template structure. This allows the system to maintain standardized data processing while preserving the user's original form design, thereby improving both reliability and ease of operation simultaneously.

Inventive Principle:
Principle #26Copying

2Reliability

If users switch to native form templates, then data processing standardization is maintained, but the likelihood of errors increases

Engineering Contradiction:
Improvedata processing standardizationVSAvoiderror rate
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

By copying and mapping data fields from the user's proven custom template to the standardized template, the system preserves the error-free data structures the user has already validated, while still achieving standardized processing. This reduces the likelihood of errors compared to forcing users to adopt entirely new native templates.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary field mapping and validation before finalizing the standardized template, identifying and resolving potential error sources in advance. This preliminary action reduces the likelihood of errors in the standardized output while maintaining data processing standardization.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If users are forced to use native templates, then system standardization is maintained, but time investment for template re-creation increases

Engineering Contradiction:
Improvesystem standardizationVSAvoidtemplate re-creation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically copies the user's existing template structure and maps data fields, eliminating the need for manual re-creation of templates. This automated copying process maintains system standardization through structured field mapping while reducing template re-creation time from hours to minutes.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs automated field mapping and template conversion in advance, before the user needs to use the standardized forms. This preliminary automated processing eliminates the time users would otherwise spend on manual template re-creation, while ensuring proper standardization is achieved.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If custom form templates are supported, then user experience improves, but system complexity increases

Engineering Contradiction:
Improveuser experienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system uses automated copying and field mapping techniques to handle custom templates, which simplifies the underlying complexity. Instead of requiring complex custom processing logic, the system copies standard templates and maps fields automatically, improving user experience while keeping system complexity manageable through automation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11734771B2System and method for detecting and mapping data fields for forms in a financial management system
Publication Date: 2023.08.22 INTUIT INC
  • US11734771B2 patent drawing
  • US11734771B2 patent drawing
  • US11734771B2 patent drawing

AI summary

Systems and methods for generating a custom document template are disclosed. An example method may be performed by one or more processors of a system and include retrieving a user document including a user data entry in a user data field, identifying a set of system data fields within a plurality of system documents potentially relevant to the user document, determining, for each of the set of system data fields, a weighted value indicative of a likelihood that the system data field is relevant to the user data field, identifying a most relevant system data field of the set of system data fields, the most relevant system data field having a highest weighted value of the determined weighted values, and generating a custom document template including a dynamic data region for the user data entry, the dynamic data region mapped to the most relevant system data field.