US20220188507A1 - System And Method For Document Transformation And Compliance - Google Patents
System And Method For Document Transformation And Compliance Download PDFInfo
- Publication number
- US20220188507A1 US20220188507A1 US17/683,177 US202217683177A US2022188507A1 US 20220188507 A1 US20220188507 A1 US 20220188507A1 US 202217683177 A US202217683177 A US 202217683177A US 2022188507 A1 US2022188507 A1 US 2022188507A1
- Authority
- US
- United States
- Prior art keywords
- data
- documents
- document
- compliance
- data field
- 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.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 230000009466 transformation Effects 0.000 title claims abstract description 34
- 238000012546 transfer Methods 0.000 claims abstract description 10
- 230000008859 change Effects 0.000 claims description 19
- 238000012790 confirmation Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 16
- 230000001105 regulatory effect Effects 0.000 claims description 6
- 239000003795 chemical substances by application Substances 0.000 description 54
- 238000010586 diagram Methods 0.000 description 29
- 230000002452 interceptive effect Effects 0.000 description 25
- 238000013499 data model Methods 0.000 description 24
- 238000012552 review Methods 0.000 description 14
- 238000007726 management method Methods 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 9
- 230000010365 information processing Effects 0.000 description 7
- 238000012360 testing method Methods 0.000 description 7
- 230000008520 organization Effects 0.000 description 5
- ORILYTVJVMAKLC-UHFFFAOYSA-N Adamantane Natural products C1C(C2)CC3CC1CC2C3 ORILYTVJVMAKLC-UHFFFAOYSA-N 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012937 correction Methods 0.000 description 3
- 238000013479 data entry Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000007689 inspection Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 230000000644 propagated effect Effects 0.000 description 3
- 241000220317 Rosa Species 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000007639 printing Methods 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- UGFAIRIUMAVXCW-UHFFFAOYSA-N Carbon monoxide Chemical compound [O+]#[C-] UGFAIRIUMAVXCW-UHFFFAOYSA-N 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 229910002091 carbon monoxide Inorganic materials 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013501 data transformation Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 238000009428 plumbing Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000000758 substrate Substances 0.000 description 1
- 230000009182 swimming Effects 0.000 description 1
- 238000000844 transformation Methods 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- 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
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/16—Real estate
- G06Q50/167—Closing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/137—Hash-based
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
- G06F16/1837—Management specially adapted to peer-to-peer storage networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06314—Calendaring for a resource
-
- 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- 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/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- 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/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
-
- 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
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/16—Real estate
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- 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
- G06Q2220/00—Business processing using cryptography
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
Definitions
- This application relates in general to identifying and populating documents, and in particular to a system and method for document grouping and transformation.
- Real estate purchases and sales are the largest financial transactions and investments for many people, especially with the increasing cost of real estate. Due to the cost and time required for a real estate transaction, many individuals are infrequently involved in such transactions and may not be familiar with regulations governing the transactions and issues that can arise. Additionally, real estate transactions are complex and involve many details and issues. Accordingly, many purchasers and buyers choose to hire a knowledgeable advocate to assist with the transaction, including a real estate agent or broker. Real estate agents and brokers can provide a party to such transaction with useful information, including options and risks regarding the transaction. Further, agents and brokers have legal and financial responsibilities to ensure that a transaction is successfully performed and that the transaction complies with all applicable guidelines and regulations.
- U.S. Pat. No. 9,330,375 covers loading virtual forms with selected properties.
- the virtual forms are electronic documents designed to have the appearance of standard real estate contract forms and act as placeholder documents into which data from a warehouse is inserted.
- data insertion fails to include checking of the data to ensure compliance, correctness, completeness, and consistency of the data being inserted.
- U.S. Pat. No. 8,423,469 covers a simplified loan process for a real estate transaction that is provided for the buyer based on unified communication between the buyer, relator, and mortgage originator and fails to cover transforming document to ensure complete, correct, consistent, and compliant data population.
- U.S. Pat. No. 8,442906 covers automating the performance and processing of tasks associated with a home sale or mortgage origination by making available pricing information matching real estate pricing criteria and generated loan information to a buyer.
- automation of task processing fails to consider methods for ensuring data associated with the home sale or mortgage origination is complete, correct, consistent, and compliant.
- U.S. Pat. No. 7,640,204 covers a digital marketplace in which real estate members can interact and facilitate transactions by exchanging accurate and standardized information.
- the marketplace can include survey and transaction tools, as well as tour scheduling.
- the marketplace fails to include document transformation via population and data checking.
- U.S. Pat. No. 6,684,196 covers facilitating real property transactions between a buyer and seller by providing real estate services to facilitate a negotiation related to the transaction, rather than populating documents and checking for data completeness, consistency, correctness, and compliance.
- U.S. Pat. No. 6,321,202 covers managing real estate transactions, including accessing vendor data based upon a phase of a real estate transaction and providing the vendor data to a contact upon the occurrence of the real estate transaction phase.
- the communication of data focuses on building relationships in real estate transactions, rather than document transformation based on a set of rules and checking data of the documents.
- U.S. Pat. No. 9,672,524 covers managing data related to a corporate entity to enhance retrieval of the documents database using tags.
- the retrieval enhancement fails to consider or include data population and checking.
- a need remains for improving processing of a computer to be able to automatically transform documents by changing a form of the documents based on received data, and identify errors and ensure compliance of data between different documents by checking for document completeness, consistency, correctness, and confirmation of data populating the documents.
- Real estate transactions can be extremely complex and generally require many documents for review and execution to formalize the transaction.
- Such transactions are performed manually via a real estate agent or broker that fills out each document.
- manual processing of the documents often results in inconsistencies of data across the documents, incorrect data values based on a failure to identify and enter updated values, data values that are not compliance with local regulations, and other errors.
- Ensuring the correctness of the documents is extremely important because errors in the documents may invalidate the associated real estate transaction.
- Representations of documents that enable both human usability and automation by allowing data entry and automated checking of the data helps ensure data completeness, consistency, compliance, and correctness of the documents.
- An embodiment provides a system and method for document transformation and compliance.
- a set of documents for a transfer of real property is accessed by a user.
- Each document includes one or more data fields each associated with a data field identifier.
- a data value is received from the user.
- One of the data fields in one of the documents is identified as associated with the received data value via the data field identifier for that data field.
- the associated data field is determined to be already populated with a different data value.
- the different data value is replaced with the received data value.
- Other data fields associated with a same data field identifier as the data field identifier of the associated data field are identified.
- FIG. 1 is a block diagram showing a system for document grouping and transformation, in accordance with one embodiment.
- FIG. 2 is a block diagram showing, by way of example, the compliance system of FIG. 1 .
- FIG. 3 is a functional block diagram showing, by way of example, the compliance information management system of FIG. 2 .
- FIG. 4 is a screenshot showing, by way of example, an interactive form for form element identifiers.
- FIG. 5 is a diagram of an interactive form showing, by way of example, a document template with defined form elements.
- FIG. 6 is a diagram of an interactive form showing, by way of example, information for generating a data field identifier associated with a data field in a document template.
- FIG. 7 is a functional block diagram showing a method for document transformation and compliance, in accordance with one embodiment.
- FIG. 8 is a diagram of a webpage showing, by way of example, a transaction cover sheet with data fields for obtaining data values.
- FIG. 9 is a block diagram showing, by way of example, data models.
- FIG. 10 is a diagram showing, by way of example, a document template library.
- FIG. 11 is a diagram showing by way of example, an interactive form for identifying document templates for a transaction.
- FIG. 12 is a diagram showing, by way of example, an interactive form displaying a document package.
- FIG. 13A is a diagram of an interactive form showing, by way of example, a portion of the cover sheet of FIG. 8 .
- FIG. 13B is a diagram of an interactive form showing, by way of example, the portion of the cover sheet of FIG. 13A with a different data value.
- FIG. 14 is a diagram of a document template with data fields for property price.
- Document package refers to a collection of documents prepared for, signed, and executed by parties of a real estate transaction.
- the package can include documents for listings or offers, including documents about real estate services performed in support of transactions, such as proofs of availability of funds, contracts with real estate agents and brokers, disclosures, inspection reports, and marketing agreements, as well as other types of documents.
- Different subsets of a document package may be provided to different parties of a transaction. For example, different documents are typically provided for buyers and sellers.
- Completeness testing a document package for completeness refers to automated testing to ensure that all of the required documents are included in the package and that all required fields in the documents are filled out.
- a trigger can add additional fields to the document beyond the initial fields displayed. Additionally, received data may also trigger one or more additional documents to be added to the document package.
- Consistency testing documents for consistency refers to automated testing to ensure that values of related fields in the documents are filled out in a semantically-consistent way. For example, every “initials” field for the same person should contain the same initials. Additionally, fields that have different representations for the same information (e.g. “one thousand dollars” versus $1,000.00) should have the same or compatible meanings. All related fields should convey consistent meanings.
- Correctness refers to automated verification that data values and combinations of related fields have been verified by one or more authoritative sources.
- entries specified for street address, City, County, State, and Zip Code correspond to a correct combination recorded by an authoritative entity.
- the specified street address is within the specified city
- the specified city is within the specified county
- the specified county is within the specified state
- the zip code corresponds properly to the combination, and the property exists.
- information about a “parcel number” for a property paired with an address corresponds to county land records.
- Another example is a bank statement vouching for the availability of funds.
- testing documents for compliance refers to automated testing to ensure that the data values provided in the documents and the transactions proposed comply with all legal requirements. For a successful property transaction, no required documents can be omitted and the document versions must meet current requirements.
- governing organizations including federal, state, county, city, and sometimes local organizations such as property owner associations. State and federal laws require that purchasers of property be informed of certain conditions of the property for consumer protection. Further, governing organizations may require disclosure of the nature, limitations, and conflicts regarding the responsibilities of the real estate agents. Compliance requires that the document package be complete, consistent, and correct.
- Common practice for compliance for avoiding potential legal liability is to provide explicit places in the documents for dated confirmation signatures on documents and for particular data fields. The steps involved include assuring that the documents include proper places for signatures or initials and dates in the documents presented to clients and others and also checking that a document package is thoroughly checked that all required signatures or initials are properly filled out and dated by clients.
- Active documents refer to programmatically-supported information that can be presented in a human-readable and legally appropriate form (“documents”) in a computational medium, with a computational substrate (“active document) that enables people to fill in or select information and to interact with it, that efficiently supports information processing of the information such as checking it for completeness, consistency, correctness, compliance and confirmation.
- active documents support understanding and processing of information by people and active computational agents intended to assure that a real estate transaction is compliant with requirements.
- Transaction identifier a string of numbers and/or letters that uniquely identify a specific transaction of property.
- Form element corresponds to a region on a form that takes a value from a data field.
- Form element identifier a string of numbers and/or letters that are unique to a particular form element in a document.
- Form element name a human-readable name used to describe and identify a particular form element in a document.
- Data field location for storage of data, such as in a database.
- Data field definition human-readable information describing an associated data field in the database to which the data field definition is assigned and can include data field identifiers.
- Data field identifier a string of numbers and/or letters that uniquely identify a specific data field in the database.
- Data field values data values that populate a data field.
- Conveyance is the act of transferring an ownership interest in real property from one party to another. Conveyance also refers to the written instrument, such as a deed or lease that transfers legal title of a property from the seller to a buyer.
- Escrow refers to money held by a third-party on behalf of transacting parties.
- the duty of a title and/or escrow company is to act as a neutral third party.
- the escrow company holds all documents and money until all of the terms and conditions in the contract have been met and the property is in title insurable condition.
- the transfer can then be made from the Seller to the Purchaser.
- Title companies do not work for the Seller or for the Purchaser. They are employed by both parties and act only upon mutually agreed upon written instructions. In Arizona, a title company, or an escrow company, rather than an attorney, serves this purpose.
- the rights in the bundle may be separated and held by different parties. It may also refer to a formal document, such as a deed, that serves as evidence of ownership. Conveyance of the document may be required in order to transfer ownership in the property to another person.
- Title insurance is a form of indemnity insurance which insures against financial loss from defects in title to real property and from the invalidity or unenforceability of mortgage loans.
- the vast majority of title insurance policies are written on land within the United States. Unlike some land registration systems in countries outside the US, the US states' recorder of deeds generally does not guarantee indefeasible title to those recorded titles.
- Title insurance will defend against a lawsuit attacking the title or reimburse the insured for the actual monetary loss incurred up to the dollar amount of insurance provided by the policy.
- Listing Agent represents the seller in a real estate transaction.
- Buying Agent also known as Selling Agent—represents the buyer in a real estate transaction.
- Real estate transactions are complicated and time consuming.
- Such transactions are performed manually by a real estate agent or broker for a stakeholder, which is commonly the buyer or seller of a property that is the focus of the transaction.
- the manual process includes identifying and collecting required documents for all governing jurisdictions, identifying and applying all relevant and current jurisdictional regulations to the documents, populating the document with required data, checking that the populated data is consistent, accurate and compliant with the regulations, revising the documents when information changes, incorporating new information arising from negotiations between the parties of the transaction, adding new documents when new requirements are enacted, providing the completed documents to the other party of the transaction, and coordinating signatures of the documents.
- the challenges include designing representations for documents and document packages that enable both human usability and automation.
- the document information should be presentable in natural language, able to be printed or presented in digital media, while also ensuring that the information is in a form practical for information processing.
- the information processing can include symbolic and numeric processing of data values entered into the documents, including determining whether fields are populated with proper values, enabling entry of data fields manually or automatically and comparing the data values with reference values and constraints.
- information processing can require access and integration with one or more databases, networked information exchange with trusted and authoritative servers, and maintaining a history or log of changes to the documents and data values.
- Other challenges include integrating automated information processing with ongoing human activities with respect to the documents, including automatically keeping track of a status of multiple interdependent activities and related services, coordinating activities and document changes, and managing incremental and ongoing document and information changes, such as ensuring compliance when information changes during a transaction.
- the automatic document transformation system includes a multi-tier system that utilizes data models for checking and automating compliance, as well as computational agents, and multiple networked, authenticated and cloud-based servers, which allow a computer to perform the task of compliance.
- a compliance status of documents and field values can change as information changes during a transaction.
- FIG. 1 is a block diagram showing a system for document grouping and transformation, in accordance with one embodiment.
- Real estate agents 11 or brokers 12 assisting a party or stakeholder 13 to a real estate transaction can access a compliance server 15 via an internetwork 29 , such as the Internet, to identify, prepare, and verify documents for the transaction as a compliance system 15 .
- the real estate agents and clients of the real estate agents or brokers can access, fill in, and sign documents for the transaction.
- the compliance system 15 can be executed by two or more servers.
- the compliance system 15 can operate via a cloud computing environment, which allows users, such as the agents, brokers, and parties to the transaction, to access and utilize remotely-stored applications (not shown) of the compliance system without requiring the users to install software or personal data.
- the users can access the compliance system 15 via a computing device, such as a computer or a mobile computing device (not shown), including a cell phone, laptop, or tablet.
- the compliance system 15 can include a compliance information management system 16 , a compliance performance system 17 , a compliance outreach system 18 , an input port 31 to receive compliance rules, databases of addresses and document templates, and an output port 32 to provide populated and checked document packages for a transaction.
- the compliance information management system 16 encodes information and logic representations for automating compliance of the transactions.
- Real estate subject matter experts 14 and information technology specialists 30 are responsible for the creation and maintenance of the information and logic used by the compliance system 15 .
- subject matter experts 14 can curate and annotate a library of documents 24 for real estate transactions that is stored by a database 19 associated with the compliance system 15 .
- the library of documents is discussed in detail below with respect to FIG. 10 .
- the documents reflect different jurisdictional transaction requirements, including federal, state, county, city, and local compliance requirements.
- information technology specialists 30 can encode, check, embed, and maintain compliance logic executed by computational agents of the compliance system with the documents in the library and associated databases.
- the information management system 16 also enables the compliance performance system 17 to support and automate real estate transactions.
- the compliance performance system 17 records information for a transaction, selects a set of documents for the transaction based on at least a portion of the recorded information, and transforms documents in the set by populating form elements of one or more of the documents processed by the information management system 16 .
- the real estate brokers 12 , agents 11 , support staff, and parties 13 can provide the information for the transaction via a form or coversheet. Based on the received information, the compliance performance system can populate the documents on which automatic compliance is performed.
- the performance system 17 performs compliance checking of the document set for consistency, correctness, completeness, and compliance, as well as confirmation.
- the compliance outreach system 18 interacts with third-party institutions 20 , 22 , as authoritative sources, to access transaction documents 28 , jurisdictional regulations 27 , property records (not shown), and financial data 26 for compliance checking with the set of populated documents.
- the third-party institutions can include city or county property records, real estate boards, financial institutions, or jurisdictional real estate regulatory institutions, including federal, state, county, city and neighborhoods jurisdictions. Other third-party institutions and document types are possible.
- Any errors in the documents regarding consistency, completeness, correctness, and compliance of the data can be identified via the performance system 17 .
- errors are detected at the time data is entered.
- the error can be flagged, making a visible note for stakeholders and preventing an erroneous value from being accepted and propagated in the document set.
- the note can suggest corrections to the data entry or prompt a user to correct the entry at that time.
- the errors can be automatically corrected; however, in a further embodiment, a notification can be transmitted to one or more of the broker, agent, or stakeholder for correction. Any time new data is entered, the compliance checking process can automatically occur to ensure that no errors are present in the transaction document set. Once the documents are complete and correct, the documents can be provided to the other party of the transaction for review and possibly, further revision.
- FIG. 2 is a block diagram 40 showing, by way of example, the compliance system 15 of FIG. 1 .
- the compliance system 15 includes the compliance information management system 16 , the compliance performance system 17 , and the compliance outreach system 18 .
- real estate subject matter experts 14 and information technology specialists 30 provide information and logic representations that are encoded and saved for performing compliance checking of the populated documents for a real estate transaction.
- Documents are identified and populated at the compliance performance system level 17 during which users, such as brokers, agents, and stakeholders to the transaction provide data regarding the transaction for populating at least a portion of the documents using the information and logic representations from the information management system 16 .
- compliance logic from the information management level 16 is applied to the documents to check for correctness, completeness, consistency, and compliance of the data and the documents, using the information gathered by the compliance information management system and the compliance outreach system.
- the compliance outreach system 18 Prior to or during the compliance checking, the compliance outreach system 18 performs interactions with third party systems to obtain additional information against which the populated documents of the transaction documents are checked.
- FIG. 3 is a functional block diagram 50 showing, by way of example, the compliance information management system 16 of FIG. 2 .
- Real estate subject matter experts and information technology specialists enter automation information 58 and automation logic 52 via a transaction coordinator platform 51 .
- the automation information 58 can include field definitions 59 , field values 60 , a library of document templates 61 , and case documents 62 , which are human-readable forms of a current state of transaction documents for each transaction, while the automation logic 52 can include population logic (not shown) that performs document population and revision, and review logic to ensure compliance, correctness, completeness, and consistency of the populated documents.
- the document templates 61 can be obtained from jurisdictional real estate organizations, generated by the subject matter experts, or uploaded via the subject matter experts or a third party, as well as from other sources.
- each jurisdictional real estate organization requires a pledge to a code of ethics and implements a standard of practice required by all members.
- Many brokers and realtors belong to one or more organizations to utilize document templates prepared, maintained, and updated by the organizations.
- new real estate regulations are implemented or laws are enacted, federally or by state, those real estate organizations covering the affected jurisdictions work to revise their documents and ensure that their templates are up to date and in compliance with the new regulations or laws.
- Each of the documents in the template library 61 includes multiple form elements for entry of transaction data, including data field values, which are each stored in a data field, such as in a database or spreadsheet.
- the data fields values are used within a data model for checking and automating compliance, and are accessed for populating the form elements.
- a real estate document template can include form elements for party names, street address, city, county, zip code, and sales price for the property of the transaction.
- Each data field that stores a data field value is associated with a data field definition 59 , which can be human-readable information describing that data field to which the data field definition is assigned.
- the data field definition is also associated with a data field identifier, such as a string of numbers and letters, that uniquely identify a specific data field in the database.
- the information of the data field definition can include one or more of a text comment describing a meaning of the field, a data type, routines for converting a value into printable text, computational modules for carrying out operations on a field, and a syntax checker.
- a data field definition for a property address can include a data field name of “street address,” a data field identifier of “Street.Address.1,” a data type of “street-address,” a description of “this is the first street address for the property, must include a number and a street name, and be consistent with a lot number in county records,” and a module for operations to carry out entering, printing, checking, comparing a received data value to trigger compliance checking and syntax checking.
- the data field identifiers and names index access to populated data values for information processing and support specific access for automating document population and compliance checking, including completeness, consistency, correctness, compliance, and confirmation processing.
- the syntax checker can be used to look up a data field value for populating a form element based on the data field identifier of the data field definition associated with the data field and a transaction identifier assigned to the transaction.
- a property transaction in which the data field for street address has been populated, can have an identifier “Trans CAL-387654-Smith-Jones-31-Dec-2018.” Based on the transaction identifier and the data field identifier, the street address data value “1302 Broadway E” is accessed and used to populate the data field. Data field identifiers and names for related data fields within a single document or across different documents are the same for different transactions. However, data values populating the data fields are specific to a transaction and are usually different for different transactions.
- Each transaction can be associated with a data model, which can include the data field identifiers or names for documents in a document package for the transaction and data values that populate data fields associated with the data field identifiers.
- the data models are discussed in detail below with respect to FIG. 9 .
- the field definitions 59 are stored in a persistent data access system, such as a relational database or a NOSQL database.
- the database is a reference source for field definitions.
- other kinds of linked data structures for the field definitions are possible, such as hash tables, tree-based structures, and look-up representations and information retrieval structures.
- the field definitions 59 are distributed and combined with a library 61 of the document templates so that the field definitions 59 are defined and stored in a distributed fashion across a set of document templates, rather than in a monolithic database for all document templates.
- a document template is designated a reference template and the source of the field definition. Having data represented as explicit data fields enables controlled and specific access to the compliance data and enables automating compliance checking and enforcement.
- FIG. 4 is a diagram showing, by way of example, an interactive form 130 for form element identifiers 135 .
- the interactive form 130 can be delivered via a web page or directly by an application.
- the interactive form 130 includes a listing 131 of “form elements” 135 that can be defined by a real estate expert or information technology specialist and associated with a data field in a document template.
- Each form element 135 can be represented by a data box in a template and listed via a form element identifier 131 .
- the interactive form 130 can provide a name 132 of the element and actions 133 , which can be performed for or on the form element that corresponds with the form element identifier 131 and name 132 .
- the actions can include printing of an associated data value, triggering when the data value has changed, converting the data value from a numerical value to text and vice versa, and when a new data value has arrived. Other actions are possible.
- New form elements 135 can be added using an “add form element” button 134 .
- FIG. 5 is a diagram of an interactive form 140 showing, by way of example, a document template 143 with defined form elements 144 .
- the interactive form 140 can include a data frame 141 and a display frame 142 , and is displayed to the real estate experts and information technology specialists for entering field definitions to the document templates.
- the data frame 141 can provide tabs for metadata 141 , inputs, and experts, as well as other tabs.
- the meta data tab 141 provides information for defining the document template 143 and can be populated by the real estate experts and information technology specialists.
- the defined document template is provided to the users, such as the real estate agents and clients.
- document information fields can be provided, including a date that the document template was published and last edited, the document name, the date the document template was last revised, a type of transaction covered by the document, and a locale represented by the document.
- the display panel 142 can display one or more pages of a document template 143 .
- Each document template displayed can include one or more form elements 144 , at least one of which is defined for automated population and compliance.
- Each defined form element 144 is associated with a data field identifier that indicates a type of data to populate that data field.
- the defined form elements can be highlighted, color coded, or otherwise marked to indicate a blank field that must be populated by the user.
- FIG. 6 is a diagram of an interactive form 150 showing, by way of example, information for generating a data field identifier associated with a form element in a document template.
- the interactive form 150 can include a data frame 151 and a display frame 152 .
- the data frame 151 can include tabs for metadata, input 153 , and expert, while the display frame 152 can display a document 154 or a portion of a document 154 with one or more data fields 155 .
- a form element 155 can be defined using an “add input” button 158 after providing information about the form element, including providing an editing string, which can be the form element identifier 156 , a page of the document displayed, and a name 157 of the form element identifier, which in this example is “Buyer1And2.” Other information, such as tabIndex, top, type, value, and width can be used for formatting of the data field to populate the form element with a data value.
- the form element identifier 156 provides that the name of Buyer 1 and Buyer 2, if any, should be entered into the form element 155 for which the data field identifier 156 is associated.
- programming information for triggering processing logic is also included. For instance, selecting a particular box, may add additional form elements to the form for answering by the user or add additional documents to the document package.
- a data field definition can also be included in the inputs tab to provide information about the type of data to populate the form element, as well as information regarding where to access the data once received and how to process the data.
- users populate the defined form element with data values, which can be stored in the field value database 60 .
- the data field values 60 are stored in a persistent data access system, such as a relational database, NOSQL database, or any other persistent data structure that can provide similar indexing functionality.
- the database 60 functions as a reference source for the data values for all of the documents in the package associated with the transaction. Additional information to assist information processing can be stored together with the data field values or in additional storage. The additional information can include date and time the data was last changed, provenance information about who entered the data or where the data originated, and links to related information, such as confirmation information that logs whether a stakeholder or user has confirmed receipt and acknowledgement.
- Automation logic utilizes the automation information, such as the data field identifiers 59 , to create and maintain accurate information for automating compliance.
- the subject matter experts and information technology specialists generate automation logic 52 , which includes population logic for automating document transformation and review logic for performing compliance checking of the documents.
- the review logic can include logic for completeness 53 , consistency 54 , correctness 55 , compliance 56 , and confirmation 57 , which is encoded by the compliance information management system, to automate compliance of the documents for a transaction.
- Completeness logic 53 ensures that all required documents for a transaction are included in a document package and that all required form elements for each document in the package are populated.
- Consistency logic 54 ensures that related fields in the documents are populated in a semantically-consistent way, as further described below with respect to FIG. 14 .
- Correctness logic 55 ensures that the data field values are verified by authoritative sources, as described below in detail with respect to FIGS. 8, 13A, and 13B , and compliance logic 56 ensures that the packaged documents for a transaction comply with all regulatory requirements.
- Confirmation logic 57 ensures that all of the required signature and date fields in the packaged documents are populated.
- FIG. 7 is a functional block diagram showing a method 80 for document transformation and compliance, in accordance with one embodiment.
- a library of document templates for real estate transactions is maintained (block 81 ) for a plurality of jurisdictions.
- the maintained documents include templates from different real estate organizations or that are newly generated.
- Each document template in the library has been processed by real estate experts and information technology specialists to group documents for different transactions in different jurisdictions and to define the form elements.
- the documents can be grouped using a document identifier or by storing related documents in folders; however, other methods for grouping documents are possible.
- a user accesses the document transformation and compliance system to generate a document package for a transfer of real property, such as a sale or purchase of the property.
- the user can include a real estate agent, broker, or other types of real estate professionals, as well as a party to the transaction.
- Different documents are relevant and appropriate for different stakeholders, which consequently have access to different documents in the document package.
- a listing agent can create transaction documents shared between a property seller and the listing agent, such as a listing agreement, as well as documents that are provided to another party of the transaction, such as a counteroffer, which is compliance checked and included in the property transaction itself.
- a selling agent can create transaction documents shared between the selling agent and client, and transaction documents, such as an offer, that are provided to another party to the transaction.
- the user can provide (block 82 ) information about the property transfer, such as a type of property transfer or property address, price, type, and owner, via a cover sheet.
- information about the property transfer such as a type of property transfer or property address, price, type, and owner, via a cover sheet.
- the information can be provided as data values that populate the form elements in the documents. Other types of information are possible.
- a data model is generated (block 83 ).
- the data model can include the data values and data field identifiers for corresponding data field definitions, as well as additional information. Additionally, the data model is updated as data values change, new documents are added, and new form elements are added. Data models are discussed in further detail below with respect to FIG. 9 .
- a package of document templates for the transaction can be generated (block 84 ) based on the received data values. For example, upon receipt of the transaction type and property address, a set of compliance rules can be identified and subsequently, the identified compliance rules can be used to identify documents for including in the document package for the transaction. For example, at least a portion of the documents associated with the city, county, or state in which the property is located can be used to generate the document package. Further, properties located in a particular location may be part of a homeowner's association and the rules of the homeowner's association will apply to the property in the transaction.
- the document package can be automatically generated based on the received data values or selected by a user. Additionally, the document package can be generated based on a combination of automatic generation and user selected generation. At any point prior to providing the document package to the other party, documents can be removed or added to the package.
- the documents in the package can be auto-populated (block 85 ). Specifically, form elements within the documents are populated (block 85 ) with data values from the cover sheet based on the data field identifiers associated with the form elements. Any form elements in the documents not automatically populated can be filled in by the user. For automatic population, data values from the coversheet, which can be stored in a database with field identifiers, are used as reference sources for populating the form elements of the documents with data field values. Other reference sources for populating the form elements are possible, such as other documents, as discussed in detail below with respect to FIG. 9 .
- the documents can be populated once identified and if further documents are later added to the package, auto-population can occur once the document has been added. Auto-population is also used when data values are changed. For example, if the price of the property changes in one form element, the new price is entered in the data model and will be used to replace the old price in the other documents in the package.
- Additional information can be stored with the populated form element values or in additional storage accessible using case and field identifiers.
- the additional information can include date and time the data was last changed, provenance information about who entered the data or where the data originated, and links to related information, such as confirmation information that logs whether a stakeholder has confirmed receipt and acknowledgement of the data values.
- review logic such as completeness logic (block 86 ), consistency logic (block 87 ), correctness logic (block 88 ), compliance logic (block 89 ), and confirmation logic (block 90 ) can be applied to the document package to ensure a validity of the data values.
- the review logic is applied in real time as the data values are being entered in the form elements, either via auto-population or via the user. Additionally, the review logic can be applied at a later time, such as all the required data is entered in the documents. For instance, for related form elements, checking cannot occur until multiple fields are entered, either in the same document or across different documents.
- the review logic can be applied separately or simultaneously. Once the documents in a package have been checked for compliance, consistency, correctness and completeness, any identified errors or inconsistencies can be automatically corrected or a notification can be provided to the user to correct the error. Once the document package satisfies all checks for completeness, consistency, correctness, compliance, and confirmation, the document package can be provided (block 91 ) to the other party to the transaction.
- updates may be required prior to providing the document package to the other party or after providing the package.
- the other party receiving the document package may want to change a term or form element value in one or more of the documents.
- one or more terms of the transaction may change, such as based on an outcome of the property inspection or by mutual agreement.
- regulations regarding the transaction can change and must be reflected in the document package. All such changes must be reflected in the transaction documents.
- a change to a value populating a form element in a document could, for example, occur via a user interaction when the document is stored in the compliance system or by a fresh upload of a copy of the document. Every change to a data field value is logged and time-stamped. Whenever a new value of the form element becomes available to the compliance system, the system updates the data value in the caching database. Additionally, whenever a new copy of the reference document is made available to the system, the system synchronizes the data so that the most recently updated value is reflected in the database for populating form elements. Other implementations for storing the data field values are possible.
- consistency rules assure that when a change to a referenced data field value for a document package becomes known, the new data value is propagated to derivative form elements across the documents in the document package.
- the compliance system keeps a log showing the dates and times of any change, and indicates where reconfirmation is required of any stakeholder's acknowledgement of a value. The log can be used to verify and confirm certain changes, as well as track the user that made the change should a dispute regarding the property arise.
- any updates (block 92 ) to a data field value are necessary, one or more data field values are changed (block 93 ) and propagated across the documents in the package. Additionally, a change can be made to a form element and that change is updated to reflect across all document templates in a document package that include that form element. Subsequently, the review logic, including completeness logic (block 86 ), consistency logic (block 87 ), correctness logic (block 88 ), compliance logic (block 89 ), and confirmation logic (block 90 ) is applied to the updates. Otherwise, if no updates are required, the document package is considered to be successfully complete and can be provided to the other party.
- the document transformation and compliance system helps reduce the amount of time required for preparing documents for a real estate transactions, such as a sale or purchase of property, and increases confidence that the documents are accurately prepared.
- a potential purchaser reviews multiple properties, which have been listed for sale. Each listed property requires a listing agreement, which includes large amounts of information that must be correctly listed for the property and comply with jurisdictional regulations.
- FIG. 8 is a diagram of an interactive form 100 showing, by way of example, a transaction cover sheet 102 with form elements for obtaining data values.
- the interactive form 100 can include a navigation bar for an index 101 of pages for the transaction and a display of the cover sheet 102 .
- the index 101 can include content links for the cover sheet 102 , including a document link, listing services link, and marketing service link.
- the listing services and marketing services are described in commonly-owned U.S. patent application Ser. No. 16/560,966, titled “System and Method for Listing Document Transformation and Compliance,” filed on Sep. 4, 2019, and U.S. Pat.
- index links are possible, including purchase service links, which can be utilized by a buying party to the transaction, as described in commonly-owned U.S. patent application Ser. No. 16/560,971, titled “System and Method for Purchase Document Transformation and Compliance,” filed on Sep. 4, 2019, and U.S. patent application Ser. No. 16/560,980, titled “Blockchain-Based System and Method for Purchase Document Transformation and Accountability,” filed Sep. 4, 2019 the disclosures of which are hereby incorporated by reference.
- the cover sheet 102 can include multiple form elements, which are used to generate a data model for the transaction.
- the data fields of the cover sheet can include fields for at least one broker or agent name 103 , at least one party name 104 , contract and market dates 105 , and property information 106 , including property identification number, street address, city, state and zip code, and purchase price (not shown).
- data specific to a seller and his listing agent can be requested via the cover sheet, such as a lock box code to access a key for the property or a gate code to the property, as well as other types of property access information, such as a combination to enter a condominium complex.
- Other types of form elements are possible.
- a user such as an agent, broker or stakeholder, can populate the form elements of the cover sheet 102 with data field values that are used for generating a data model to identify a document package and perform compliance checking.
- a check mark or other symbol or color can be used to provide a status of the cover sheet in the index 101 , which in this case, is complete.
- one or more compliance checks can be applied via the review logic as the data values are entered into the cover sheet.
- correctness logic can be used to check data values entered into the form elements of the cover sheet. Specifically, the data values can be checked to prevent propagation of incorrect information in the other documents of the document package.
- a real estate agent is completing the cover sheet for his client, the seller, and fills out the seller's email address as adam.able.gmail.com.
- the correctness logic identifies that the email address is invalid due to lacking the conventional syntax character “@” to separate the name of the email holder from the name of the email service and marks the incorrect data value as an error.
- the error can be provided as a pop-up message or by highlighting the incorrect data value, and can be removed upon correction of the data value. Other displays of the error notification are possible.
- the correctness logic can also connect to authoritative sources to retrieve authoritative information for checking the data values.
- the property for sale is located at 1120 Rose Avenue, Mountain View, Calif. 94040.
- an authoritative source such as a multiple listing service database, is accessed to obtain and display valid property addresses matching the partial address entered.
- the real estate agent can then select the property address representing the property for sale by Adam Able.
- Consistency and compliance logic can also be applied to the data values entered in the cover sheet.
- FIG. 9 is a block diagram showing, by way of example, parts of data models 107 for different transactions.
- Each data model can include data field identifiers 108 and data field values 109 .
- the data field identifiers are associated with a form element in the cover sheet and documents in the library.
- the data field values are used to populate all form elements with the corresponding data field identifier.
- the same data field identifiers can be used across documents, as well as transactions; however, the data field values differ for each transaction.
- the seller name is split into two fields with the field for first name associated with a field identifier “seller.first.name” and the field for last name associated with the identifier “seller.last.name.”
- the received data values of Adam for first name and Able for second name are stored with the associated identifiers in a data model having an extensible set of data field identifiers for accessing and displaying information populating the documents. All the received data values in the cover sheet and document templates for the property transaction can be stored together as the data model.
- one or more data values from the data model can be used to identify rules for a particular transaction and the identified rules can then be used to select documents for a document package for the transaction.
- the data values from the data model can be used to populate a disclosure document outlining a relationship between a real estate agency and a seller or buyer.
- the template for the disclosure document can include interactive fields for ensuring acknowledgement by the seller or buyer, and signature, date, and license fields.
- FIG. 10 is a diagram showing, by way of example, a part of a document template library 61 .
- the library 61 provides a listing of document templates 70 that are necessary for meeting compliance regulations and practices for different jurisdictions.
- Each document template 70 can be stored with information, including template name 71 , a date of last revision 72 , whether the document appears in a listing 73 of documents relevant to the listing agent and seller, whether the document appears in an offer 74 for the property, last publication date 75 , last edit date 76 , locale type 77 , and assigned locale 78 .
- the assigned locale 78 can list the jurisdiction which requires the document, while the locale type 77 provides a classification for the type of jurisdiction, including city, county, or state, as well as other types of jurisdictions.
- each document template 70 can be accessed by clicking on the template name. Further document templates 70 can be added using an “add document template” button 79 .
- one or more data values received via the cover sheet can be used to identify a set of rules for the transaction.
- one or more documents can be selected from the library to form the document package.
- the transaction can be assigned a unique transaction identifier, which can then be used to uniquely identify the document package.
- the transaction identifier can be a unique number or string, or could be generated as a string that includes some human-interpretable information, such as the real estate agent's name, seller's name, and a date together with a number.
- FIG. 11 is a diagram showing by way of example, an interactive form 110 for identifying document templates for a transaction.
- the interactive form 110 includes a navigation bar for an index of pages 101 and a documents section 111 .
- the documents section 111 provides one or more property type selections 112 , a search bar 113 , and a listing 114 of document templates 115 .
- the property type selections 112 can be identified and presented based on the address entered in the cover sheet and a type of transaction, such as a selling or buying transaction.
- the address can be used to identify jurisdictional organizations that cover the location of the property, while the transaction type is used to identify listing or purchase documents.
- a property located in Mountain View, Calif. must comply with real estate regulations enacted by the state of California, as well as any local regulations.
- To list the property located in the Mountain View for sale document templates for listing agreements that comply with real estate regulations in one or more of California or locally are identified and presented.
- a listing agreement represents a contract between a real estate agent and an owner of the property to be sold and can include a list price for the property, a beginning and end date for the property listing, an amount of compensation for the real estate agent, and authorization for the agent to work with third parties to further the sale of the property, as well as other types of information.
- listing agreements drafted by different organizations can include different conditions based on location, property type, and preference of that organization.
- one professional organization in California includes, by default, a clause in the listing agreement that requires a property to be delivered to a buyer in operational order, while the listing agreement drafted by a different professional organization does not require, by default, the seller to make any repairs.
- the property type selections for the Mountain View property can include a manufactured home, residential home or vacant land, or a residential home however, other property type selections are possible.
- document templates for listing agreements for each of the property types that conform with California and local regulations are identified and displayed.
- the user such as a real estate agent or broker, can choose one or more of the transaction type selections 112 for generating a document package for the transaction. For example, if the property is a residential home, the user can select residential documents associated with the selected property types are displayed or selected for display in the document template list 114 in the document section 111 .
- all the documents associated with the selected property types can be selected for display and inclusion in the document package.
- all the documents associated with the selected property types can be displayed and a user can select certain documents for inclusion in the document package.
- the document section 111 includes a search bar 113 , which can be used to identify additional document templates for adding to the document package.
- An agent may use the search bar if he or she has information about the property or transaction that is not evident yet from the information that has been entered in the active documents. In this way, the agent can add relevant documents to the package. For instance, the residential Mountain View property may have water conserving plumbing fixtures, which require an additional document for disclosure or is offered for sale as a short sale, which also requires additional documents. Accordingly, based on those special circumstances, the document templates are accessed via the search bar 113 and added to the document package.
- the interactive form 110 can include a generate documents button 116 , which allows a user to view the document templates selected for inclusion in the document package.
- FIG. 12 is a diagram showing, by way of example, an interactive form 120 displaying document templates for possible inclusion in a document package 121 .
- the web page 120 provides a listing of documents 122 for a listing agreement, for example, that can be included in the document package 121 for the property transaction upon confirmation of the transaction.
- the documents templates can be displayed as thumbnail images, and selected for review and revision.
- Each thumbnail representation of the active documents can include a title of the document and a menu, which allows the user to edit or obtain additional information about that document.
- Each of the documents in the package can be auto-populated with the data values entered in the cover sheet prior to display or upon display.
- users can upload external documents via an add document button 123 on the interactive form 120 . For example, homeowner association guidelines and papers may not be easily available to individuals that do not belong to the homeowner association and thus, can be uploaded.
- the population logic processes the documents selected for the package by reviewing the form elements, looking up data field identifiers for the data fields in the data model, and populating the form elements with the data values in the data model that correspond with the data field identifiers.
- the user can select a thumbnail for each document and review the documents with the populated data values. If any form element remains unpopulated, the user can enter a data value, which is saved with a data field identifier associated with the unpopulated form element and stored in the data model. Other documents in the package that include a form element associated with the data field identifier can be populated with the corresponding data value.
- the data field values for a document package are stored in both a database and a reference document as a value for a corresponding form element.
- the reference document data field or source includes the data value of record and the database functions as a cache for that value.
- the cache is used to simplify accelerated data field access for populating other documents.
- the data values can be stored in the data fields of a reference document in the package and any changes to the data values can be made immediately to the respective form elements in the other documents.
- the data values are stored in a database and accessed upon display of the documents in the package. For instance, when a change is made to a data value, the value is changed in the database and the next time the documents in the package are displayed, the fields are populated with the updated values stored in the database just prior to display.
- compliance logic can be performed to ensure the completeness, correctness, consistency, and compliance of the documents.
- Completeness logic helps ensure that all required documents are included in the document package for the transaction and that all required fields for each document are filled in.
- Rules regarding each form element are associated with the field definitions and based on the information provided by the field definition, a determination can be made that the associated form element remains blank. For example, a signature field must be signed prior to finalizing the document package for providing to the other party. If no signature has been entered, completeness logic can identify the field and send a notification to at least one user, such as the real estate agent or client.
- completeness logic can be used to create status indicators that indicate unfinished elements, such as empty form elements within one or more documents.
- the status indicators can indicate that some fields in a required document have not yet been filled in.
- the indicators can appear as a pop-up message or other type of notification while the user is working on the document in which a completeness error is identified, when the user leaves the document with the completeness error, or during checking of the document package.
- Ensuring that a document package is complete by including all necessary documents for a transaction and that all form elements within the documents of the package are filled in helps limit interactions with parties to or stakeholders of a transaction before information in the document package is complete.
- the system can prevent a document package from being sent to another party to the transaction for signatures before required information is filled in, which can prevent multiple rounds of back and forth communication between the parties to fix the error and result in completing the transaction in less time.
- FIG. 13A is a diagram of an interactive form showing, by way of example, a portion of the cover sheet 170 of FIG. 8 .
- the cover sheet 170 can include form elements for identifying a county 171 in which a property is located and the type of ownership 172 of the property, including individual, trust, and entity.
- the property is owned by an individual and the individual's name, which can be provided under the seller's name form element as described above with reference to FIG. 8 , can be used to populate form elements associated with identifiers for the owner's name or identity.
- FIG. 13B is a diagram of an interactive form showing, by way of example, the portion of the cover sheet 180 of FIG. 13A with a different data value.
- the cover sheet 180 can include form elements for identifying a county 181 in which a property is located and the type of ownership 182 of the property, including individual, trust, and entity.
- a trust 183 owns the property, which is the subject of the transaction.
- additional information about the trust is necessary to complete the documents in the package because the previous form elements did not include a request for trust name.
- the completeness logic identifies the trust selection 183 and displays an additional field 184 for a name of the trust.
- FIG. 14 is a diagram of a document template 190 with form elements 191 , 192 for property price.
- the document 190 includes form elements for two different representations 191 , 192 of the sales price for a property.
- the price data value 191 should be spelled out in words, as is common practice for paper bank checks.
- the other form element 192 requires the price to be entered with a currency indicator, such as a dollar sign followed by a number.
- the consistency logic for checking syntax can refer to the data field indicator “Prop.Sales.Price.Num,” which is associated with the form element 192 for sales price number and the data field identifier “Prop.Sales.Price.Str” for the sales price string of words. Based on the similarity of the identifiers, including the common portion “Prop.Sales.Price,” the data value of the spelled-out field could be checked for consistency against the numeric sales price via the consistency logic.
- the consistency logic together with a data entry system could derive a string representation of the sales price consistently and automatically after the numeric representation of the price is entered.
- the consistency logic can also identify and input the numeric representation of the sales price after a string representation of the sales price.
- Other form elements that can benefit from a consistency check include ensuring that the property address in numbers matches with a spelled-out version of the property number.
- correctness logic can also be performed to ensure that data values populating the form element are verified by authoritative sources.
- the correctness logic can identify invalid data values and provide suggestions for data values via an authoritative source, as described above with respect to FIGS. 8, 13A, and 13B .
- the correctness logic can identify invalid email addresses, such as those without the ampersand symbol or a domain.
- the correctness logic can connect to a multiple listing service or regional database that stores addresses and utilize those addresses to provide suggestions for partial data values entered by a user for an address.
- form elements on which the correctness logic can be applied include zip code and state, and street address and city, as well as many other form elements. The correctness that a particular zip code is located within a particular state can be verified by a mapping database or property records database.
- the data values can be checked using compliance logic, which helps ensure that the documents in the package comply with all regulatory requirements.
- the compliance logic can access and use one or more authoritative sources to look up a required set of documents based on the address of the property being sold.
- the regulatory information is entered into the compliance system by real estate subject matter experts using a Transaction Coordinator Platform. The human experts consult appropriate governmental and other sources, create document templates, and assign the templates to the proper geographic region.
- the document templates can be generated from documents prepared by different organizations, such as regional real estate associations and groups. Additionally, online government sources can be used to obtain information.
- confirmation logic can be applied to the document package prior to sending the completed document package to the other party.
- the confirmation logic ensures that all of the required signing and dating of the documents are completed.
- a notification can be provided to the user to identify any blank fields that should have a signature or date. The notification can be provided by a pop-up notification or by highlighting the blank field.
- Multi-tier or single tier blockchains can be used, as described in detail with respect to commonly-owned U.S. patent application Ser. No. 16/560,988, titled “Single-Tier Blockchain-Based System and Method for Document Transformation and Accountability,” filed Sep. 4, 2019, and in commonly-owned U.S. Pat. No. 11,227,350, titled “Single-Tier Blockchain-Based System and Method for Document Transformation and Accountability via Different Node Types,” issued Jan. 18, 2022, the disclosures of which are hereby incorporated by reference.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Engineering & Computer Science (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Economics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Accounting & Taxation (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Entrepreneurship & Innovation (AREA)
- Computational Linguistics (AREA)
- Artificial Intelligence (AREA)
- Finance (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Power Engineering (AREA)
- Computing Systems (AREA)
- Bioethics (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Multimedia (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- This application relates in general to identifying and populating documents, and in particular to a system and method for document grouping and transformation.
- Real estate purchases and sales are the largest financial transactions and investments for many people, especially with the increasing cost of real estate. Due to the cost and time required for a real estate transaction, many individuals are infrequently involved in such transactions and may not be familiar with regulations governing the transactions and issues that can arise. Additionally, real estate transactions are complex and involve many details and issues. Accordingly, many purchasers and buyers choose to hire a knowledgeable advocate to assist with the transaction, including a real estate agent or broker. Real estate agents and brokers can provide a party to such transaction with useful information, including options and risks regarding the transaction. Further, agents and brokers have legal and financial responsibilities to ensure that a transaction is successfully performed and that the transaction complies with all applicable guidelines and regulations.
- Over the years, the amount of documentation involved in supporting real estate transactions and financing of such transactions has grown. The required documents have become increasingly numerous and complex, and assuring compliance has become more difficult. The documentation requirements generally differ from one community to another, so agents and brokers must pay attention to the differences in local regulations. They must also keep up with changes in the regulations for all of the relevant governing bodies for every transaction. Also, governing bodies are overlapping and any transaction occurring within the jurisdiction of both governing bodies, must comply with the regulations of the governing bodies. For example, there are often separate regulations for a neighborhood, city, county and state in which a piece of property is located.
- Ensuring compliance with all guidelines and regulations can be time consuming and difficult. However, failure to comply with the regulations can potentially invalidate real estate transactions and can expose real estate brokers and agents to litigation and possible liability for failed transactions.
- Currently, most real estate transactions are preformed manually, requiring an individual, such as an agent or broker, to identify, collect, and populate documents required to complete a real estate transaction. The agent or broker must also ensure that the documents contain any updates and are correctly populated. Such manual tasks can be time consuming due to a number of documents required and the different requirements established by differing regulations between governing bodies. Additionally, the manual process for real estate transactions is prone to several sources of compliance errors as real estate agents and brokers prepare document packages for real estate transactions. Such errors and other failures to comply with the required regulations can invalidate a transaction and can expose agents and brokers to costly litigation, as well as stain a reputation of the agent or broker. Challenges associated the manual process for real estate transactions that make manual compliance difficult and error prone include large numbers of documents, different regulations and rules for different locations, and new information that becomes available during the transaction, which must be identified and included in the documents.
- However, automation of real estate transactions has been attempted. For example, U.S. Pat. No. 9,330,375 covers loading virtual forms with selected properties. The virtual forms are electronic documents designed to have the appearance of standard real estate contract forms and act as placeholder documents into which data from a warehouse is inserted. However, such data insertion fails to include checking of the data to ensure compliance, correctness, completeness, and consistency of the data being inserted.
- U.S. Pat. No. 8,423,469 covers a simplified loan process for a real estate transaction that is provided for the buyer based on unified communication between the buyer, relator, and mortgage originator and fails to cover transforming document to ensure complete, correct, consistent, and compliant data population.
- U.S. Pat. No. 8,442906 covers automating the performance and processing of tasks associated with a home sale or mortgage origination by making available pricing information matching real estate pricing criteria and generated loan information to a buyer. However, such automation of task processing fails to consider methods for ensuring data associated with the home sale or mortgage origination is complete, correct, consistent, and compliant.
- U.S. Pat. No. 7,640,204 covers a digital marketplace in which real estate members can interact and facilitate transactions by exchanging accurate and standardized information. The marketplace can include survey and transaction tools, as well as tour scheduling. Thus, the marketplace fails to include document transformation via population and data checking.
- U.S. Pat. No. 6,684,196 covers facilitating real property transactions between a buyer and seller by providing real estate services to facilitate a negotiation related to the transaction, rather than populating documents and checking for data completeness, consistency, correctness, and compliance.
- U.S. Pat. No. 6,321,202 covers managing real estate transactions, including accessing vendor data based upon a phase of a real estate transaction and providing the vendor data to a contact upon the occurrence of the real estate transaction phase. Thus, the communication of data focuses on building relationships in real estate transactions, rather than document transformation based on a set of rules and checking data of the documents.
- Further, U.S. Pat. No. 9,672,524 covers managing data related to a corporate entity to enhance retrieval of the documents database using tags. However, the retrieval enhancement fails to consider or include data population and checking.
- Therefore, a need remains for improving processing of a computer to be able to automatically transform documents by changing a form of the documents based on received data, and identify errors and ensure compliance of data between different documents by checking for document completeness, consistency, correctness, and confirmation of data populating the documents.
- Real estate transactions can be extremely complex and generally require many documents for review and execution to formalize the transaction. Currently, such transactions are performed manually via a real estate agent or broker that fills out each document. However, manual processing of the documents often results in inconsistencies of data across the documents, incorrect data values based on a failure to identify and enter updated values, data values that are not compliance with local regulations, and other errors. Ensuring the correctness of the documents is extremely important because errors in the documents may invalidate the associated real estate transaction. Representations of documents that enable both human usability and automation by allowing data entry and automated checking of the data helps ensure data completeness, consistency, compliance, and correctness of the documents.
- An embodiment provides a system and method for document transformation and compliance. A set of documents for a transfer of real property is accessed by a user. Each document includes one or more data fields each associated with a data field identifier. A data value is received from the user. One of the data fields in one of the documents is identified as associated with the received data value via the data field identifier for that data field. The associated data field is determined to be already populated with a different data value. The different data value is replaced with the received data value. Other data fields associated with a same data field identifier as the data field identifier of the associated data field are identified. The other data fields are populated with the received data value. Compliance checking of the documents is performed.
- Still other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein is described embodiments of the invention by way of illustrating the best mode contemplated for carrying out the invention. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modifications in various obvious respects, all without departing from the spirit and the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
-
FIG. 1 is a block diagram showing a system for document grouping and transformation, in accordance with one embodiment. -
FIG. 2 is a block diagram showing, by way of example, the compliance system ofFIG. 1 . -
FIG. 3 is a functional block diagram showing, by way of example, the compliance information management system ofFIG. 2 . -
FIG. 4 is a screenshot showing, by way of example, an interactive form for form element identifiers. -
FIG. 5 is a diagram of an interactive form showing, by way of example, a document template with defined form elements. -
FIG. 6 is a diagram of an interactive form showing, by way of example, information for generating a data field identifier associated with a data field in a document template. -
FIG. 7 is a functional block diagram showing a method for document transformation and compliance, in accordance with one embodiment. -
FIG. 8 is a diagram of a webpage showing, by way of example, a transaction cover sheet with data fields for obtaining data values. -
FIG. 9 is a block diagram showing, by way of example, data models. -
FIG. 10 is a diagram showing, by way of example, a document template library. -
FIG. 11 is a diagram showing by way of example, an interactive form for identifying document templates for a transaction. -
FIG. 12 is a diagram showing, by way of example, an interactive form displaying a document package. -
FIG. 13A is a diagram of an interactive form showing, by way of example, a portion of the cover sheet ofFIG. 8 . -
FIG. 13B is a diagram of an interactive form showing, by way of example, the portion of the cover sheet ofFIG. 13A with a different data value. -
FIG. 14 is a diagram of a document template with data fields for property price. - Document package—a document package refers to a collection of documents prepared for, signed, and executed by parties of a real estate transaction. The package can include documents for listings or offers, including documents about real estate services performed in support of transactions, such as proofs of availability of funds, contracts with real estate agents and brokers, disclosures, inspection reports, and marketing agreements, as well as other types of documents. Different subsets of a document package may be provided to different parties of a transaction. For example, different documents are typically provided for buyers and sellers.
- Completeness—testing a document package for completeness refers to automated testing to ensure that all of the required documents are included in the package and that all required fields in the documents are filled out. When specific information is provided as a value for a field, a trigger can add additional fields to the document beyond the initial fields displayed. Additionally, received data may also trigger one or more additional documents to be added to the document package.
- Consistency—testing documents for consistency refers to automated testing to ensure that values of related fields in the documents are filled out in a semantically-consistent way. For example, every “initials” field for the same person should contain the same initials. Additionally, fields that have different representations for the same information (e.g. “one thousand dollars” versus $1,000.00) should have the same or compatible meanings. All related fields should convey consistent meanings.
- Correctness—testing documents for correctness refers to automated verification that data values and combinations of related fields have been verified by one or more authoritative sources. For examples, entries specified for street address, City, County, State, and Zip Code correspond to a correct combination recorded by an authoritative entity. The specified street address is within the specified city, the specified city is within the specified county, the specified county is within the specified state, and the zip code corresponds properly to the combination, and the property exists. Another example is that information about a “parcel number” for a property paired with an address corresponds to county land records. Another example is a bank statement vouching for the availability of funds. There can be different requirements on what it means for a source to be “authoritative,” including having a well-known identity, using secure and digitally-signed communications, meeting government-approved requirements, backing by financial guarantees, and meeting certification requirements of legal, real estate, and banking institutions.
- Compliance—testing documents for compliance refers to automated testing to ensure that the data values provided in the documents and the transactions proposed comply with all legal requirements. For a successful property transaction, no required documents can be omitted and the document versions must meet current requirements. In real estate transactions, there are often multiple governing organizations, including federal, state, county, city, and sometimes local organizations such as property owner associations. State and federal laws require that purchasers of property be informed of certain conditions of the property for consumer protection. Further, governing organizations may require disclosure of the nature, limitations, and conflicts regarding the responsibilities of the real estate agents. Compliance requires that the document package be complete, consistent, and correct.
- Confirmation—brokers and agents are obligated to inform their clients about important information in the transactions. Common practice for compliance for avoiding potential legal liability is to provide explicit places in the documents for dated confirmation signatures on documents and for particular data fields. The steps involved include assuring that the documents include proper places for signatures or initials and dates in the documents presented to clients and others and also checking that a document package is thoroughly checked that all required signatures or initials are properly filled out and dated by clients.
- Active documents—refer to programmatically-supported information that can be presented in a human-readable and legally appropriate form (“documents”) in a computational medium, with a computational substrate (“active document) that enables people to fill in or select information and to interact with it, that efficiently supports information processing of the information such as checking it for completeness, consistency, correctness, compliance and confirmation. In this way, active documents support understanding and processing of information by people and active computational agents intended to assure that a real estate transaction is compliant with requirements.
- Transaction identifier—a string of numbers and/or letters that uniquely identify a specific transaction of property.
- Form element—corresponds to a region on a form that takes a value from a data field.
- Form element identifier—a string of numbers and/or letters that are unique to a particular form element in a document.
- Form element name—a human-readable name used to describe and identify a particular form element in a document.
- Data field—location for storage of data, such as in a database.
- Data field definition—human-readable information describing an associated data field in the database to which the data field definition is assigned and can include data field identifiers.
- Data field identifier—a string of numbers and/or letters that uniquely identify a specific data field in the database.
- Data field values—data values that populate a data field.
- Bureau of Real Estate (BRE)—is a state level agency that makes rules for real estate transactions.
- Conveyance—is the act of transferring an ownership interest in real property from one party to another. Conveyance also refers to the written instrument, such as a deed or lease that transfers legal title of a property from the seller to a buyer.
- Escrow—refers to money held by a third-party on behalf of transacting parties. The duty of a title and/or escrow company is to act as a neutral third party. The escrow company holds all documents and money until all of the terms and conditions in the contract have been met and the property is in title insurable condition. The transfer can then be made from the Seller to the Purchaser. Title companies do not work for the Seller or for the Purchaser. They are employed by both parties and act only upon mutually agreed upon written instructions. In Arizona, a title company, or an escrow company, rather than an attorney, serves this purpose.
- Title—is a bundle of rights in a piece of real estate in which a party may own either a legal interest or equitable interest. The rights in the bundle may be separated and held by different parties. It may also refer to a formal document, such as a deed, that serves as evidence of ownership. Conveyance of the document may be required in order to transfer ownership in the property to another person.
- Title insurance—is a form of indemnity insurance which insures against financial loss from defects in title to real property and from the invalidity or unenforceability of mortgage loans. The vast majority of title insurance policies are written on land within the United States. Unlike some land registration systems in countries outside the US, the US states' recorder of deeds generally does not guarantee indefeasible title to those recorded titles. Title insurance will defend against a lawsuit attacking the title or reimburse the insured for the actual monetary loss incurred up to the dollar amount of insurance provided by the policy.
- Listing Agent—represents the seller in a real estate transaction.
- Buying Agent (also known as Selling Agent)—represents the buyer in a real estate transaction.
- Real estate transactions are complicated and time consuming. Currently, such transactions are performed manually by a real estate agent or broker for a stakeholder, which is commonly the buyer or seller of a property that is the focus of the transaction. The manual process includes identifying and collecting required documents for all governing jurisdictions, identifying and applying all relevant and current jurisdictional regulations to the documents, populating the document with required data, checking that the populated data is consistent, accurate and compliant with the regulations, revising the documents when information changes, incorporating new information arising from negotiations between the parties of the transaction, adding new documents when new requirements are enacted, providing the completed documents to the other party of the transaction, and coordinating signatures of the documents. However, due to the increasing number of documents and constantly changing regulations, there is a substantial risk of human error, which can, at times, invalidate the transaction. Further, even if the documents are completed electronically, computers are currently unable to verify or ensure compliance of the populated data based merely on the electronic preparation of the transaction documents.
- Automatic document transformation and compliance can prevent error and reduce an amount of time required to identify and complete the required documents. However, automating such document transformation, especially for real estate transactions, is challenging and many factors must be considered to ensure that automated document transformation and compliance is accurate, quick, and reliable. The challenges include designing representations for documents and document packages that enable both human usability and automation. Specifically, the document information should be presentable in natural language, able to be printed or presented in digital media, while also ensuring that the information is in a form practical for information processing. The information processing can include symbolic and numeric processing of data values entered into the documents, including determining whether fields are populated with proper values, enabling entry of data fields manually or automatically and comparing the data values with reference values and constraints. To perform such steps, information processing can require access and integration with one or more databases, networked information exchange with trusted and authoritative servers, and maintaining a history or log of changes to the documents and data values. Other challenges include integrating automated information processing with ongoing human activities with respect to the documents, including automatically keeping track of a status of multiple interdependent activities and related services, coordinating activities and document changes, and managing incremental and ongoing document and information changes, such as ensuring compliance when information changes during a transaction. To overcome such challenges, the automatic document transformation system, as discussed in detail below, includes a multi-tier system that utilizes data models for checking and automating compliance, as well as computational agents, and multiple networked, authenticated and cloud-based servers, which allow a computer to perform the task of compliance. A compliance status of documents and field values can change as information changes during a transaction.
- Compliance System Architecture and Operation
- Document transformation and compliance checking reduces errors during real estate transactions to ensure that the transactions are successfully and timely completed.
FIG. 1 is a block diagram showing a system for document grouping and transformation, in accordance with one embodiment.Real estate agents 11 orbrokers 12 assisting a party orstakeholder 13 to a real estate transaction can access acompliance server 15 via aninternetwork 29, such as the Internet, to identify, prepare, and verify documents for the transaction as acompliance system 15. The real estate agents and clients of the real estate agents or brokers can access, fill in, and sign documents for the transaction. In a further embodiment, thecompliance system 15 can be executed by two or more servers. - In one embodiment, the
compliance system 15 can operate via a cloud computing environment, which allows users, such as the agents, brokers, and parties to the transaction, to access and utilize remotely-stored applications (not shown) of the compliance system without requiring the users to install software or personal data. The users can access thecompliance system 15 via a computing device, such as a computer or a mobile computing device (not shown), including a cell phone, laptop, or tablet. - The
compliance system 15 can include a complianceinformation management system 16, acompliance performance system 17, acompliance outreach system 18, aninput port 31 to receive compliance rules, databases of addresses and document templates, and anoutput port 32 to provide populated and checked document packages for a transaction. The complianceinformation management system 16 encodes information and logic representations for automating compliance of the transactions. Real estatesubject matter experts 14 andinformation technology specialists 30, among other individuals, are responsible for the creation and maintenance of the information and logic used by thecompliance system 15. For example,subject matter experts 14 can curate and annotate a library ofdocuments 24 for real estate transactions that is stored by adatabase 19 associated with thecompliance system 15. The library of documents is discussed in detail below with respect toFIG. 10 . The documents reflect different jurisdictional transaction requirements, including federal, state, county, city, and local compliance requirements. Meanwhile,information technology specialists 30 can encode, check, embed, and maintain compliance logic executed by computational agents of the compliance system with the documents in the library and associated databases. - The
information management system 16 also enables thecompliance performance system 17 to support and automate real estate transactions. For instance, thecompliance performance system 17 records information for a transaction, selects a set of documents for the transaction based on at least a portion of the recorded information, and transforms documents in the set by populating form elements of one or more of the documents processed by theinformation management system 16. Thereal estate brokers 12,agents 11, support staff, andparties 13 can provide the information for the transaction via a form or coversheet. Based on the received information, the compliance performance system can populate the documents on which automatic compliance is performed. - During or after population, the
performance system 17 performs compliance checking of the document set for consistency, correctness, completeness, and compliance, as well as confirmation. Thecompliance outreach system 18 interacts with third-party institutions 20, 22, as authoritative sources, to accesstransaction documents 28,jurisdictional regulations 27, property records (not shown), andfinancial data 26 for compliance checking with the set of populated documents. The third-party institutions can include city or county property records, real estate boards, financial institutions, or jurisdictional real estate regulatory institutions, including federal, state, county, city and neighborhoods jurisdictions. Other third-party institutions and document types are possible. - Any errors in the documents regarding consistency, completeness, correctness, and compliance of the data can be identified via the
performance system 17. In one embodiment, errors are detected at the time data is entered. The error can be flagged, making a visible note for stakeholders and preventing an erroneous value from being accepted and propagated in the document set. The note can suggest corrections to the data entry or prompt a user to correct the entry at that time. In another embodiment, the errors can be automatically corrected; however, in a further embodiment, a notification can be transmitted to one or more of the broker, agent, or stakeholder for correction. Any time new data is entered, the compliance checking process can automatically occur to ensure that no errors are present in the transaction document set. Once the documents are complete and correct, the documents can be provided to the other party of the transaction for review and possibly, further revision. - The compliance
information management system 16,compliance performance system 17, andcompliance outreach system 18 work in conjunction with each other to automate document transformation and compliance checking.FIG. 2 is a block diagram 40 showing, by way of example, thecompliance system 15 ofFIG. 1 . As described above, thecompliance system 15 includes the complianceinformation management system 16, thecompliance performance system 17, and thecompliance outreach system 18. At the level of the complianceinformation management system 16, real estatesubject matter experts 14 andinformation technology specialists 30 provide information and logic representations that are encoded and saved for performing compliance checking of the populated documents for a real estate transaction. - Documents are identified and populated at the compliance
performance system level 17 during which users, such as brokers, agents, and stakeholders to the transaction provide data regarding the transaction for populating at least a portion of the documents using the information and logic representations from theinformation management system 16. Once populated, compliance logic from theinformation management level 16 is applied to the documents to check for correctness, completeness, consistency, and compliance of the data and the documents, using the information gathered by the compliance information management system and the compliance outreach system. Prior to or during the compliance checking, thecompliance outreach system 18 performs interactions with third party systems to obtain additional information against which the populated documents of the transaction documents are checked. - Documents and Data Fields
- Ensuring accurate document transformation and compliance requires automation information and logic representations.
FIG. 3 is a functional block diagram 50 showing, by way of example, the complianceinformation management system 16 ofFIG. 2 . Real estate subject matter experts and information technology specialists, among other qualified individuals, enterautomation information 58 andautomation logic 52 via atransaction coordinator platform 51. Theautomation information 58 can includefield definitions 59, field values 60, a library ofdocument templates 61, and case documents 62, which are human-readable forms of a current state of transaction documents for each transaction, while theautomation logic 52 can include population logic (not shown) that performs document population and revision, and review logic to ensure compliance, correctness, completeness, and consistency of the populated documents. - The
document templates 61 can be obtained from jurisdictional real estate organizations, generated by the subject matter experts, or uploaded via the subject matter experts or a third party, as well as from other sources. Generally, each jurisdictional real estate organization requires a pledge to a code of ethics and implements a standard of practice required by all members. Many brokers and realtors belong to one or more organizations to utilize document templates prepared, maintained, and updated by the organizations. When new real estate regulations are implemented or laws are enacted, federally or by state, those real estate organizations covering the affected jurisdictions work to revise their documents and ensure that their templates are up to date and in compliance with the new regulations or laws. - Each of the documents in the
template library 61 includes multiple form elements for entry of transaction data, including data field values, which are each stored in a data field, such as in a database or spreadsheet. The data fields values are used within a data model for checking and automating compliance, and are accessed for populating the form elements. A real estate document template can include form elements for party names, street address, city, county, zip code, and sales price for the property of the transaction. Each data field that stores a data field value is associated with adata field definition 59, which can be human-readable information describing that data field to which the data field definition is assigned. The data field definition is also associated with a data field identifier, such as a string of numbers and letters, that uniquely identify a specific data field in the database. - The information of the data field definition can include one or more of a text comment describing a meaning of the field, a data type, routines for converting a value into printable text, computational modules for carrying out operations on a field, and a syntax checker. For example, a data field definition for a property address can include a data field name of “street address,” a data field identifier of “Street.Address.1,” a data type of “street-address,” a description of “this is the first street address for the property, must include a number and a street name, and be consistent with a lot number in county records,” and a module for operations to carry out entering, printing, checking, comparing a received data value to trigger compliance checking and syntax checking.
- The data field identifiers and names index access to populated data values for information processing and support specific access for automating document population and compliance checking, including completeness, consistency, correctness, compliance, and confirmation processing. Specifically, the syntax checker can be used to look up a data field value for populating a form element based on the data field identifier of the data field definition associated with the data field and a transaction identifier assigned to the transaction. For example, returning to the street address example above, a property transaction, in which the data field for street address has been populated, can have an identifier “Trans CAL-387654-Smith-Jones-31-Dec-2018.” Based on the transaction identifier and the data field identifier, the street address data value “1302 Broadway E” is accessed and used to populate the data field. Data field identifiers and names for related data fields within a single document or across different documents are the same for different transactions. However, data values populating the data fields are specific to a transaction and are usually different for different transactions. Each transaction can be associated with a data model, which can include the data field identifiers or names for documents in a document package for the transaction and data values that populate data fields associated with the data field identifiers. The data models are discussed in detail below with respect to
FIG. 9 . - In one embodiment, the
field definitions 59 are stored in a persistent data access system, such as a relational database or a NOSQL database. The database is a reference source for field definitions. However, other kinds of linked data structures for the field definitions are possible, such as hash tables, tree-based structures, and look-up representations and information retrieval structures. - In a further embodiment, the
field definitions 59 are distributed and combined with alibrary 61 of the document templates so that thefield definitions 59 are defined and stored in a distributed fashion across a set of document templates, rather than in a monolithic database for all document templates. In such embodiments, a document template is designated a reference template and the source of the field definition. Having data represented as explicit data fields enables controlled and specific access to the compliance data and enables automating compliance checking and enforcement. - To access data values and populate form elements in the document templates, the field definitions can be associated with the form elements, such as via a look-up table or stored with the form elements.
FIG. 4 is a diagram showing, by way of example, aninteractive form 130 forform element identifiers 135. Theinteractive form 130 can be delivered via a web page or directly by an application. Theinteractive form 130 includes a listing 131 of “form elements” 135 that can be defined by a real estate expert or information technology specialist and associated with a data field in a document template. Eachform element 135 can be represented by a data box in a template and listed via aform element identifier 131. For each form element, theinteractive form 130 can provide aname 132 of the element andactions 133, which can be performed for or on the form element that corresponds with theform element identifier 131 andname 132. The actions can include printing of an associated data value, triggering when the data value has changed, converting the data value from a numerical value to text and vice versa, and when a new data value has arrived. Other actions are possible.New form elements 135 can be added using an “add form element”button 134. - Data field definitions can be assigned to the form elements within documents templates by a subject matter expert or real estate professional that can work with information technology specialists to define the data fields.
FIG. 5 is a diagram of aninteractive form 140 showing, by way of example, adocument template 143 with definedform elements 144. Theinteractive form 140 can include adata frame 141 and adisplay frame 142, and is displayed to the real estate experts and information technology specialists for entering field definitions to the document templates. Thedata frame 141 can provide tabs formetadata 141, inputs, and experts, as well as other tabs. Themeta data tab 141 provides information for defining thedocument template 143 and can be populated by the real estate experts and information technology specialists. In turn, the defined document template is provided to the users, such as the real estate agents and clients. Under themetadata tab 141, document information fields can be provided, including a date that the document template was published and last edited, the document name, the date the document template was last revised, a type of transaction covered by the document, and a locale represented by the document. - The
display panel 142 can display one or more pages of adocument template 143. Each document template displayed can include one ormore form elements 144, at least one of which is defined for automated population and compliance. Each definedform element 144 is associated with a data field identifier that indicates a type of data to populate that data field. The defined form elements can be highlighted, color coded, or otherwise marked to indicate a blank field that must be populated by the user. - The inputs tab of the data frame can be used by real estate experts and information technology specialists to define a form element with a data field definition or provide information about the field definition associated with that form element.
FIG. 6 is a diagram of aninteractive form 150 showing, by way of example, information for generating a data field identifier associated with a form element in a document template. Theinteractive form 150 can include adata frame 151 and adisplay frame 152. Thedata frame 151 can include tabs for metadata,input 153, and expert, while thedisplay frame 152 can display adocument 154 or a portion of adocument 154 with one or more data fields 155. When theinput tab 153 is selected, aform element 155 can be defined using an “add input”button 158 after providing information about the form element, including providing an editing string, which can be theform element identifier 156, a page of the document displayed, and aname 157 of the form element identifier, which in this example is “Buyer1And2.” Other information, such as tabIndex, top, type, value, and width can be used for formatting of the data field to populate the form element with a data value. Theform element identifier 156 provides that the name ofBuyer 1 andBuyer 2, if any, should be entered into theform element 155 for which thedata field identifier 156 is associated. Under theinput tab 153, programming information for triggering processing logic is also included. For instance, selecting a particular box, may add additional form elements to the form for answering by the user or add additional documents to the document package. - A data field definition can also be included in the inputs tab to provide information about the type of data to populate the form element, as well as information regarding where to access the data once received and how to process the data. Once the form elements of a document template have been defined, the template can be added to the document library for access and use by real estate agents for real estate transactions.
- Returning to the discussion with respect to
FIG. 3 , users, such as real estate agents or clients, populate the defined form element with data values, which can be stored in thefield value database 60. In one embodiment, the data field values 60 are stored in a persistent data access system, such as a relational database, NOSQL database, or any other persistent data structure that can provide similar indexing functionality. Thedatabase 60 functions as a reference source for the data values for all of the documents in the package associated with the transaction. Additional information to assist information processing can be stored together with the data field values or in additional storage. The additional information can include date and time the data was last changed, provenance information about who entered the data or where the data originated, and links to related information, such as confirmation information that logs whether a stakeholder or user has confirmed receipt and acknowledgement. - Automation logic utilizes the automation information, such as the
data field identifiers 59, to create and maintain accurate information for automating compliance. The subject matter experts and information technology specialists generateautomation logic 52, which includes population logic for automating document transformation and review logic for performing compliance checking of the documents. The review logic can include logic forcompleteness 53,consistency 54,correctness 55,compliance 56, andconfirmation 57, which is encoded by the compliance information management system, to automate compliance of the documents for a transaction.Completeness logic 53 ensures that all required documents for a transaction are included in a document package and that all required form elements for each document in the package are populated.Consistency logic 54 ensures that related fields in the documents are populated in a semantically-consistent way, as further described below with respect toFIG. 14 .Correctness logic 55 ensures that the data field values are verified by authoritative sources, as described below in detail with respect toFIGS. 8, 13A, and 13B , andcompliance logic 56 ensures that the packaged documents for a transaction comply with all regulatory requirements.Confirmation logic 57 ensures that all of the required signature and date fields in the packaged documents are populated. - Each property transaction generally requires a large amount of documents to be completed. Automated document transformation and compliance provides convenient, accurate and timely checking and transformation of the documents to prevent errors.
FIG. 7 is a functional block diagram showing amethod 80 for document transformation and compliance, in accordance with one embodiment. A library of document templates for real estate transactions is maintained (block 81) for a plurality of jurisdictions. The maintained documents include templates from different real estate organizations or that are newly generated. Each document template in the library has been processed by real estate experts and information technology specialists to group documents for different transactions in different jurisdictions and to define the form elements. The documents can be grouped using a document identifier or by storing related documents in folders; however, other methods for grouping documents are possible. - A user accesses the document transformation and compliance system to generate a document package for a transfer of real property, such as a sale or purchase of the property. The user can include a real estate agent, broker, or other types of real estate professionals, as well as a party to the transaction. Different documents are relevant and appropriate for different stakeholders, which consequently have access to different documents in the document package. For example, a listing agent can create transaction documents shared between a property seller and the listing agent, such as a listing agreement, as well as documents that are provided to another party of the transaction, such as a counteroffer, which is compliance checked and included in the property transaction itself. Similarly, a selling agent can create transaction documents shared between the selling agent and client, and transaction documents, such as an offer, that are provided to another party to the transaction. Further, different users can have different access to the data transformation and compliance system. For instance, real estate agents and brokers cannot sign on behalf of the buyer or seller, whereas the buyer and seller may not be able to access the same document templates as the real estate agent or broker, such as when the documents are only available based on membership in an organization from which the documents originated.
- Upon access, the user can provide (block 82) information about the property transfer, such as a type of property transfer or property address, price, type, and owner, via a cover sheet. Specifically, the information can be provided as data values that populate the form elements in the documents. Other types of information are possible.
- Based on the data values received from the user, a data model is generated (block 83). The data model can include the data values and data field identifiers for corresponding data field definitions, as well as additional information. Additionally, the data model is updated as data values change, new documents are added, and new form elements are added. Data models are discussed in further detail below with respect to
FIG. 9 . - Prior to, simultaneously or after generation of the data model, a package of document templates for the transaction can be generated (block 84) based on the received data values. For example, upon receipt of the transaction type and property address, a set of compliance rules can be identified and subsequently, the identified compliance rules can be used to identify documents for including in the document package for the transaction. For example, at least a portion of the documents associated with the city, county, or state in which the property is located can be used to generate the document package. Further, properties located in a particular location may be part of a homeowner's association and the rules of the homeowner's association will apply to the property in the transaction. The document package can be automatically generated based on the received data values or selected by a user. Additionally, the document package can be generated based on a combination of automatic generation and user selected generation. At any point prior to providing the document package to the other party, documents can be removed or added to the package.
- Once identified, the documents in the package can be auto-populated (block 85). Specifically, form elements within the documents are populated (block 85) with data values from the cover sheet based on the data field identifiers associated with the form elements. Any form elements in the documents not automatically populated can be filled in by the user. For automatic population, data values from the coversheet, which can be stored in a database with field identifiers, are used as reference sources for populating the form elements of the documents with data field values. Other reference sources for populating the form elements are possible, such as other documents, as discussed in detail below with respect to
FIG. 9 . The documents can be populated once identified and if further documents are later added to the package, auto-population can occur once the document has been added. Auto-population is also used when data values are changed. For example, if the price of the property changes in one form element, the new price is entered in the data model and will be used to replace the old price in the other documents in the package. - Additional information can be stored with the populated form element values or in additional storage accessible using case and field identifiers. The additional information can include date and time the data was last changed, provenance information about who entered the data or where the data originated, and links to related information, such as confirmation information that logs whether a stakeholder has confirmed receipt and acknowledgement of the data values.
- During or after data population, review logic, such as completeness logic (block 86), consistency logic (block 87), correctness logic (block 88), compliance logic (block 89), and confirmation logic (block 90) can be applied to the document package to ensure a validity of the data values. In one example, the review logic is applied in real time as the data values are being entered in the form elements, either via auto-population or via the user. Additionally, the review logic can be applied at a later time, such as all the required data is entered in the documents. For instance, for related form elements, checking cannot occur until multiple fields are entered, either in the same document or across different documents.
- The review logic can be applied separately or simultaneously. Once the documents in a package have been checked for compliance, consistency, correctness and completeness, any identified errors or inconsistencies can be automatically corrected or a notification can be provided to the user to correct the error. Once the document package satisfies all checks for completeness, consistency, correctness, compliance, and confirmation, the document package can be provided (block 91) to the other party to the transaction.
- However, prior to providing the document package to the other party or after providing the package, updates (block 92) to one or more of the form elements may be required. For example, the other party receiving the document package may want to change a term or form element value in one or more of the documents. Alternatively, one or more terms of the transaction may change, such as based on an outcome of the property inspection or by mutual agreement. Additionally, regulations regarding the transaction can change and must be reflected in the document package. All such changes must be reflected in the transaction documents.
- A change to a value populating a form element in a document could, for example, occur via a user interaction when the document is stored in the compliance system or by a fresh upload of a copy of the document. Every change to a data field value is logged and time-stamped. Whenever a new value of the form element becomes available to the compliance system, the system updates the data value in the caching database. Additionally, whenever a new copy of the reference document is made available to the system, the system synchronizes the data so that the most recently updated value is reflected in the database for populating form elements. Other implementations for storing the data field values are possible. In each variation, consistency rules assure that when a change to a referenced data field value for a document package becomes known, the new data value is propagated to derivative form elements across the documents in the document package. To maintain transparency and consistency, the compliance system keeps a log showing the dates and times of any change, and indicates where reconfirmation is required of any stakeholder's acknowledgement of a value. The log can be used to verify and confirm certain changes, as well as track the user that made the change should a dispute regarding the property arise.
- If any updates (block 92) to a data field value are necessary, one or more data field values are changed (block 93) and propagated across the documents in the package. Additionally, a change can be made to a form element and that change is updated to reflect across all document templates in a document package that include that form element. Subsequently, the review logic, including completeness logic (block 86), consistency logic (block 87), correctness logic (block 88), compliance logic (block 89), and confirmation logic (block 90) is applied to the updates. Otherwise, if no updates are required, the document package is considered to be successfully complete and can be provided to the other party.
- Process and Document Transformations
- The document transformation and compliance system helps reduce the amount of time required for preparing documents for a real estate transactions, such as a sale or purchase of property, and increases confidence that the documents are accurately prepared. Generally, during a property sale and purchase transaction, a potential purchaser reviews multiple properties, which have been listed for sale. Each listed property requires a listing agreement, which includes large amounts of information that must be correctly listed for the property and comply with jurisdictional regulations.
- Eventually, the potential purchaser identifies an available property for sale and generates an offer for sending to the seller of the listed property selected. Generating the offer can be tedious and time consuming based on the information that must be provided and disclosed. Once the offer is accepted, all paper work for the transaction must be completed before closing. Such paper work includes documents relevant to the particular property and transaction, and can include proof of title search, insurance, flood certification, proof of homeowners insurance and mortgage insurance, home appraisal, inspection reports, and closing disclosure, among other documents, such as carbon monoxide detector notice, new construction addendum, vacant land listing agreement, and water heater statement of compliance. Other types of documents are possible.
- Users can utilize the document transformation and compliance system to prepare the listing, offer, and related documents. Such documents are prepared using information received from a user, such as via a questionnaire or cover sheet.
FIG. 8 is a diagram of aninteractive form 100 showing, by way of example, atransaction cover sheet 102 with form elements for obtaining data values. Theinteractive form 100 can include a navigation bar for anindex 101 of pages for the transaction and a display of thecover sheet 102. Theindex 101 can include content links for thecover sheet 102, including a document link, listing services link, and marketing service link. The listing services and marketing services are described in commonly-owned U.S. patent application Ser. No. 16/560,966, titled “System and Method for Listing Document Transformation and Compliance,” filed on Sep. 4, 2019, and U.S. Pat. No. 11,145,017, titled “Blockchain-Based System and Method for Listing Document Transformation and Accountability,” issued Oct. 12, 2021, the disclosures of which are hereby incorporated by reference. However, other index links are possible, including purchase service links, which can be utilized by a buying party to the transaction, as described in commonly-owned U.S. patent application Ser. No. 16/560,971, titled “System and Method for Purchase Document Transformation and Compliance,” filed on Sep. 4, 2019, and U.S. patent application Ser. No. 16/560,980, titled “Blockchain-Based System and Method for Purchase Document Transformation and Accountability,” filed Sep. 4, 2019 the disclosures of which are hereby incorporated by reference. - The
cover sheet 102 can include multiple form elements, which are used to generate a data model for the transaction. The data fields of the cover sheet can include fields for at least one broker oragent name 103, at least oneparty name 104, contract and market dates 105, andproperty information 106, including property identification number, street address, city, state and zip code, and purchase price (not shown). Further, data specific to a seller and his listing agent can be requested via the cover sheet, such as a lock box code to access a key for the property or a gate code to the property, as well as other types of property access information, such as a combination to enter a condominium complex. Other types of form elements are possible. A user, such as an agent, broker or stakeholder, can populate the form elements of thecover sheet 102 with data field values that are used for generating a data model to identify a document package and perform compliance checking. Once the cover sheet has been completed, a check mark or other symbol or color can be used to provide a status of the cover sheet in theindex 101, which in this case, is complete. - In one embodiment, one or more compliance checks can be applied via the review logic as the data values are entered into the cover sheet. For example, correctness logic can be used to check data values entered into the form elements of the cover sheet. Specifically, the data values can be checked to prevent propagation of incorrect information in the other documents of the document package. For example, a real estate agent is completing the cover sheet for his client, the seller, and fills out the seller's email address as adam.able.gmail.com. The correctness logic identifies that the email address is invalid due to lacking the conventional syntax character “@” to separate the name of the email holder from the name of the email service and marks the incorrect data value as an error. The error can be provided as a pop-up message or by highlighting the incorrect data value, and can be removed upon correction of the data value. Other displays of the error notification are possible.
- The correctness logic can also connect to authoritative sources to retrieve authoritative information for checking the data values. For example, the property for sale is located at 1120 Rose Avenue, Mountain View, Calif. 94040. As the real estate agent types in the address “1120 Rose,” an authoritative source, such as a multiple listing service database, is accessed to obtain and display valid property addresses matching the partial address entered. The real estate agent can then select the property address representing the property for sale by Adam Able. Consistency and compliance logic can also be applied to the data values entered in the cover sheet.
- Data Models and Process Logic
- Once obtained and checked, the data values of the cover sheet are used to generate a data model.
FIG. 9 is a block diagram showing, by way of example, parts ofdata models 107 for different transactions. Each data model can includedata field identifiers 108 and data field values 109. In this example, the data field identifiers are associated with a form element in the cover sheet and documents in the library. The data field values are used to populate all form elements with the corresponding data field identifier. The same data field identifiers can be used across documents, as well as transactions; however, the data field values differ for each transaction. - Returning to the above example regarding seller, Adam Able, the seller name is split into two fields with the field for first name associated with a field identifier “seller.first.name” and the field for last name associated with the identifier “seller.last.name.” The received data values of Adam for first name and Able for second name are stored with the associated identifiers in a data model having an extensible set of data field identifiers for accessing and displaying information populating the documents. All the received data values in the cover sheet and document templates for the property transaction can be stored together as the data model.
- Once generated, one or more data values from the data model can be used to identify rules for a particular transaction and the identified rules can then be used to select documents for a document package for the transaction. However, prior to generating a document package, the data values from the data model can be used to populate a disclosure document outlining a relationship between a real estate agency and a seller or buyer. The template for the disclosure document can include interactive fields for ensuring acknowledgement by the seller or buyer, and signature, date, and license fields.
- Once the relationship between the real estate agent and buyer or seller has been established, documents can be selected from a document template library for inclusion in the document package.
FIG. 10 is a diagram showing, by way of example, a part of adocument template library 61. Thelibrary 61 provides a listing ofdocument templates 70 that are necessary for meeting compliance regulations and practices for different jurisdictions. Eachdocument template 70 can be stored with information, includingtemplate name 71, a date oflast revision 72, whether the document appears in alisting 73 of documents relevant to the listing agent and seller, whether the document appears in anoffer 74 for the property,last publication date 75,last edit date 76,locale type 77, and assignedlocale 78. The assignedlocale 78 can list the jurisdiction which requires the document, while thelocale type 77 provides a classification for the type of jurisdiction, including city, county, or state, as well as other types of jurisdictions. In one example, eachdocument template 70 can be accessed by clicking on the template name.Further document templates 70 can be added using an “add document template” button 79. - To generate a document package for a transaction, one or more data values received via the cover sheet, such as the property address, can be used to identify a set of rules for the transaction. Subsequently, based on the identified rule set, one or more documents can be selected from the library to form the document package. The transaction can be assigned a unique transaction identifier, which can then be used to uniquely identify the document package. For example, the transaction identifier can be a unique number or string, or could be generated as a string that includes some human-interpretable information, such as the real estate agent's name, seller's name, and a date together with a number.
- As more data values are provided for the form elements, additional documents may be identified as required for the transaction. Accordingly, templates for those documents are instantiated and some of the field values can be filled in where they have already been established. In this way, the document package grows incrementally and automatically as needed.
- In one embodiment, a listing of document templates can be presented and an agent can select one or more documents to add to the document package, as needed.
FIG. 11 is a diagram showing by way of example, aninteractive form 110 for identifying document templates for a transaction. Theinteractive form 110 includes a navigation bar for an index of pages101 and adocuments section 111. Thedocuments section 111 provides one or moreproperty type selections 112, asearch bar 113, and alisting 114 ofdocument templates 115. Theproperty type selections 112 can be identified and presented based on the address entered in the cover sheet and a type of transaction, such as a selling or buying transaction. Specifically, the address can be used to identify jurisdictional organizations that cover the location of the property, while the transaction type is used to identify listing or purchase documents. For example, a property located in Mountain View, Calif. must comply with real estate regulations enacted by the state of California, as well as any local regulations. To list the property located in the Mountain View for sale, document templates for listing agreements that comply with real estate regulations in one or more of California or locally are identified and presented. A listing agreement represents a contract between a real estate agent and an owner of the property to be sold and can include a list price for the property, a beginning and end date for the property listing, an amount of compensation for the real estate agent, and authorization for the agent to work with third parties to further the sale of the property, as well as other types of information. However, different listing agreements drafted by different organizations can include different conditions based on location, property type, and preference of that organization. For example, one professional organization in California includes, by default, a clause in the listing agreement that requires a property to be delivered to a buyer in operational order, while the listing agreement drafted by a different professional organization does not require, by default, the seller to make any repairs. - The property type selections for the Mountain View property can include a manufactured home, residential home or vacant land, or a residential home however, other property type selections are possible. Thus, document templates for listing agreements for each of the property types that conform with California and local regulations are identified and displayed. The user, such as a real estate agent or broker, can choose one or more of the
transaction type selections 112 for generating a document package for the transaction. For example, if the property is a residential home, the user can select residential documents associated with the selected property types are displayed or selected for display in thedocument template list 114 in thedocument section 111. In one embodiment, all the documents associated with the selected property types can be selected for display and inclusion in the document package. Alternatively, all the documents associated with the selected property types can be displayed and a user can select certain documents for inclusion in the document package. - Further, the
document section 111 includes asearch bar 113, which can be used to identify additional document templates for adding to the document package. An agent may use the search bar if he or she has information about the property or transaction that is not evident yet from the information that has been entered in the active documents. In this way, the agent can add relevant documents to the package. For instance, the residential Mountain View property may have water conserving plumbing fixtures, which require an additional document for disclosure or is offered for sale as a short sale, which also requires additional documents. Accordingly, based on those special circumstances, the document templates are accessed via thesearch bar 113 and added to the document package. Further, theinteractive form 110 can include a generatedocuments button 116, which allows a user to view the document templates selected for inclusion in the document package. - Based on the document template selections in the
document page 111, a package of documents is generated for the transaction and displayed to the user.FIG. 12 is a diagram showing, by way of example, aninteractive form 120 displaying document templates for possible inclusion in adocument package 121. Theweb page 120 provides a listing ofdocuments 122 for a listing agreement, for example, that can be included in thedocument package 121 for the property transaction upon confirmation of the transaction. In one embodiment, the documents templates can be displayed as thumbnail images, and selected for review and revision. Each thumbnail representation of the active documents can include a title of the document and a menu, which allows the user to edit or obtain additional information about that document. Each of the documents in the package can be auto-populated with the data values entered in the cover sheet prior to display or upon display. Further, users can upload external documents via anadd document button 123 on theinteractive form 120. For example, homeowner association guidelines and papers may not be easily available to individuals that do not belong to the homeowner association and thus, can be uploaded. - During auto-population, the population logic processes the documents selected for the package by reviewing the form elements, looking up data field identifiers for the data fields in the data model, and populating the form elements with the data values in the data model that correspond with the data field identifiers. The user can select a thumbnail for each document and review the documents with the populated data values. If any form element remains unpopulated, the user can enter a data value, which is saved with a data field identifier associated with the unpopulated form element and stored in the data model. Other documents in the package that include a form element associated with the data field identifier can be populated with the corresponding data value.
- In different embodiments, different methods for looking up the data field values to populate the documents are possible, depending on whether the data field values are stored in a reference database, in a reference document, or in a combination of both. In one example, the data field values for a document package are stored in both a database and a reference document as a value for a corresponding form element. The reference document data field or source includes the data value of record and the database functions as a cache for that value. The cache is used to simplify accelerated data field access for populating other documents. In a different example, the data values can be stored in the data fields of a reference document in the package and any changes to the data values can be made immediately to the respective form elements in the other documents. In a further example, the data values are stored in a database and accessed upon display of the documents in the package. For instance, when a change is made to a data value, the value is changed in the database and the next time the documents in the package are displayed, the fields are populated with the updated values stored in the database just prior to display.
- At the same time or after auto-population of the documents, compliance logic can be performed to ensure the completeness, correctness, consistency, and compliance of the documents. Completeness logic helps ensure that all required documents are included in the document package for the transaction and that all required fields for each document are filled in. Rules regarding each form element are associated with the field definitions and based on the information provided by the field definition, a determination can be made that the associated form element remains blank. For example, a signature field must be signed prior to finalizing the document package for providing to the other party. If no signature has been entered, completeness logic can identify the field and send a notification to at least one user, such as the real estate agent or client.
- In one embodiment, completeness logic can be used to create status indicators that indicate unfinished elements, such as empty form elements within one or more documents. For example, the status indicators can indicate that some fields in a required document have not yet been filled in. The indicators can appear as a pop-up message or other type of notification while the user is working on the document in which a completeness error is identified, when the user leaves the document with the completeness error, or during checking of the document package. Ensuring that a document package is complete by including all necessary documents for a transaction and that all form elements within the documents of the package are filled in helps limit interactions with parties to or stakeholders of a transaction before information in the document package is complete. For instance, the system can prevent a document package from being sent to another party to the transaction for signatures before required information is filled in, which can prevent multiple rounds of back and forth communication between the parties to fix the error and result in completing the transaction in less time.
- Completeness logic can also be used to identify form elements to be added to a document depending on data values that are filled in for other form elements in documents included in the package.
FIG. 13A is a diagram of an interactive form showing, by way of example, a portion of thecover sheet 170 ofFIG. 8 . Thecover sheet 170 can include form elements for identifying acounty 171 in which a property is located and the type ofownership 172 of the property, including individual, trust, and entity. In this example, the property is owned by an individual and the individual's name, which can be provided under the seller's name form element as described above with reference toFIG. 8 , can be used to populate form elements associated with identifiers for the owner's name or identity. - However, additional information may be required based on a data value entered by a user. For example, if information is added indicating that a property has a swimming pool, additional forms may be required. The completeness logic can be performed to request the additional information.
FIG. 13B is a diagram of an interactive form showing, by way of example, the portion of thecover sheet 180 ofFIG. 13A with a different data value. Thecover sheet 180 can include form elements for identifying acounty 181 in which a property is located and the type ofownership 182 of the property, including individual, trust, and entity. In this example, atrust 183 owns the property, which is the subject of the transaction. However, additional information about the trust is necessary to complete the documents in the package because the previous form elements did not include a request for trust name. The completeness logic identifies thetrust selection 183 and displays anadditional field 184 for a name of the trust. - Prior to, during, or after application of the completeness logic, consistency logic can be performed to ensure that related form elements in the documents in a document package are filled in in a semantically-consistent manner.
FIG. 14 is a diagram of adocument template 190 withform elements document 190 includes form elements for twodifferent representations field 191, theprice data value 191 should be spelled out in words, as is common practice for paper bank checks. Theother form element 192 requires the price to be entered with a currency indicator, such as a dollar sign followed by a number. The consistency logic for checking syntax can refer to the data field indicator “Prop.Sales.Price.Num,” which is associated with theform element 192 for sales price number and the data field identifier “Prop.Sales.Price.Str” for the sales price string of words. Based on the similarity of the identifiers, including the common portion “Prop.Sales.Price,” the data value of the spelled-out field could be checked for consistency against the numeric sales price via the consistency logic. - In a further embodiment, the consistency logic together with a data entry system could derive a string representation of the sales price consistently and automatically after the numeric representation of the price is entered. The consistency logic can also identify and input the numeric representation of the sales price after a string representation of the sales price. Other form elements that can benefit from a consistency check include ensuring that the property address in numbers matches with a spelled-out version of the property number.
- In addition to performing consistency logic on the document package, correctness logic can also be performed to ensure that data values populating the form element are verified by authoritative sources. Specifically, the correctness logic can identify invalid data values and provide suggestions for data values via an authoritative source, as described above with respect to
FIGS. 8, 13A, and 13B . For instance, the correctness logic can identify invalid email addresses, such as those without the ampersand symbol or a domain. Additionally, the correctness logic can connect to a multiple listing service or regional database that stores addresses and utilize those addresses to provide suggestions for partial data values entered by a user for an address. Other examples of form elements on which the correctness logic can be applied include zip code and state, and street address and city, as well as many other form elements. The correctness that a particular zip code is located within a particular state can be verified by a mapping database or property records database. - Also, the data values can be checked using compliance logic, which helps ensure that the documents in the package comply with all regulatory requirements. The compliance logic can access and use one or more authoritative sources to look up a required set of documents based on the address of the property being sold. In one example, the regulatory information is entered into the compliance system by real estate subject matter experts using a Transaction Coordinator Platform. The human experts consult appropriate governmental and other sources, create document templates, and assign the templates to the proper geographic region. The document templates can be generated from documents prepared by different organizations, such as regional real estate associations and groups. Additionally, online government sources can be used to obtain information.
- Finally, confirmation logic can be applied to the document package prior to sending the completed document package to the other party. The confirmation logic ensures that all of the required signing and dating of the documents are completed. A notification can be provided to the user to identify any blank fields that should have a signature or date. The notification can be provided by a pop-up notification or by highlighting the blank field. Once the document package has been populated and checked, and no errors exist, the package can be provided to the other party.
- Once the document package for a real estate transaction is generated, documentation of the transaction is important to properly record in order to protect the rights of people to own and use particular parcels of land and land-related resources. Although buyers and sellers may have their own copies of records, their copies can be lost, discarded, damaged or destroyed over time. Property owners rely on other institutions to maintain backup or master copies of various documents.
- Such obstacles of recording publicly accessible transaction documents and confidential records regarding the transaction can be overcome by bringing together all the important records of a real estate transaction and recording the records in an accountability blockchain ledger with a timestamp so that all of the documents for a transaction are available at once in a single block on a blockchain under a compliance and accountability blockchain approach. Recording publicly accessible documents is described in detail in commonly-owned U.S. patent application Ser. No. 16/560,973, titled “Blockchain-Based System and Method for Document Transformation and Accountability,” filed Sep. 4, 2019, and U.S. patent application Ser. No. 16/560,982, titled “Multi-Tier Blockchain-Based System and Method for Document Transformation and Accountability,” filed Sep. 4, 2019, the disclosures of which are herein incorporated by reference. Multi-tier or single tier blockchains can be used, as described in detail with respect to commonly-owned U.S. patent application Ser. No. 16/560,988, titled “Single-Tier Blockchain-Based System and Method for Document Transformation and Accountability,” filed Sep. 4, 2019, and in commonly-owned U.S. Pat. No. 11,227,350, titled “Single-Tier Blockchain-Based System and Method for Document Transformation and Accountability via Different Node Types,” issued Jan. 18, 2022, the disclosures of which are hereby incorporated by reference.
- While the invention has been particularly shown and described as referenced to the embodiments thereof, those skilled in the art will understand that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/683,177 US20220188507A1 (en) | 2018-09-06 | 2022-02-28 | System And Method For Document Transformation And Compliance |
US18/517,339 US20240087063A1 (en) | 2018-09-06 | 2023-11-22 | Computer-implemented document transformation systems and methods |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862728051P | 2018-09-06 | 2018-09-06 | |
US16/560,964 US11263395B1 (en) | 2018-09-06 | 2019-09-04 | System and method for document transformation and compliance |
US17/683,177 US20220188507A1 (en) | 2018-09-06 | 2022-02-28 | System And Method For Document Transformation And Compliance |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/560,964 Continuation US11263395B1 (en) | 2018-09-06 | 2019-09-04 | System and method for document transformation and compliance |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/560,980 Continuation-In-Part US11803923B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for purchase document transformation and accountability |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220188507A1 true US20220188507A1 (en) | 2022-06-16 |
Family
ID=78007841
Family Applications (18)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/560,980 Active US11803923B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for purchase document transformation and accountability |
US16/560,988 Active US11314699B1 (en) | 2018-09-06 | 2019-09-04 | Single-tier blockchain-based system and method for document transformation and accountability |
US16/560,964 Active US11263395B1 (en) | 2018-09-06 | 2019-09-04 | System and method for document transformation and compliance |
US16/560,973 Active US11557011B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for document transformation and accountability |
US16/560,976 Active 2039-10-22 US11145017B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for listing document transformation and accountability |
US16/560,984 Active 2039-10-11 US11227350B1 (en) | 2018-09-06 | 2019-09-04 | Single-tier blockchain-based system and method for document transformation and accountability via different node types |
US16/560,982 Active US11341102B1 (en) | 2018-09-06 | 2019-09-04 | Multi-tier blockchain-based system and method for document transformation and accountability |
US17/498,513 Active US11488269B2 (en) | 2018-09-06 | 2021-10-11 | Blockchain-based system and method for listing document transformation and accountability |
US17/577,179 Active US11748831B2 (en) | 2018-09-06 | 2022-01-17 | System and method for document transformation |
US17/683,177 Abandoned US20220188507A1 (en) | 2018-09-06 | 2022-02-28 | System And Method For Document Transformation And Compliance |
US17/728,755 Active US11734781B2 (en) | 2018-09-06 | 2022-04-25 | Single-tier blockchain-based system and method for document transformation and accountability |
US17/751,387 Active US11869107B2 (en) | 2018-09-06 | 2022-05-23 | Multi-tier blockchain-based system and method for document transformation and accountability |
US17/978,034 Active US11676229B2 (en) | 2018-09-06 | 2022-10-31 | System and method for document transformation and accountability |
US18/154,583 Abandoned US20230153933A1 (en) | 2018-09-06 | 2023-01-13 | Method for document transformation |
US18/333,387 Abandoned US20240233054A9 (en) | 2018-09-06 | 2023-06-12 | System and method for document transformation and accountability |
US18/453,246 Pending US20240153021A1 (en) | 2018-09-06 | 2023-08-21 | System and method for document transformation and accountability |
US18/460,388 Pending US20240144404A1 (en) | 2018-09-06 | 2023-09-01 | System and method for document transformation |
US18/497,981 Pending US20240177254A1 (en) | 2018-09-06 | 2023-10-30 | Blockchain-based system and method for purchase document transformation and accountability |
Family Applications Before (9)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/560,980 Active US11803923B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for purchase document transformation and accountability |
US16/560,988 Active US11314699B1 (en) | 2018-09-06 | 2019-09-04 | Single-tier blockchain-based system and method for document transformation and accountability |
US16/560,964 Active US11263395B1 (en) | 2018-09-06 | 2019-09-04 | System and method for document transformation and compliance |
US16/560,973 Active US11557011B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for document transformation and accountability |
US16/560,976 Active 2039-10-22 US11145017B1 (en) | 2018-09-06 | 2019-09-04 | Blockchain-based system and method for listing document transformation and accountability |
US16/560,984 Active 2039-10-11 US11227350B1 (en) | 2018-09-06 | 2019-09-04 | Single-tier blockchain-based system and method for document transformation and accountability via different node types |
US16/560,982 Active US11341102B1 (en) | 2018-09-06 | 2019-09-04 | Multi-tier blockchain-based system and method for document transformation and accountability |
US17/498,513 Active US11488269B2 (en) | 2018-09-06 | 2021-10-11 | Blockchain-based system and method for listing document transformation and accountability |
US17/577,179 Active US11748831B2 (en) | 2018-09-06 | 2022-01-17 | System and method for document transformation |
Family Applications After (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/728,755 Active US11734781B2 (en) | 2018-09-06 | 2022-04-25 | Single-tier blockchain-based system and method for document transformation and accountability |
US17/751,387 Active US11869107B2 (en) | 2018-09-06 | 2022-05-23 | Multi-tier blockchain-based system and method for document transformation and accountability |
US17/978,034 Active US11676229B2 (en) | 2018-09-06 | 2022-10-31 | System and method for document transformation and accountability |
US18/154,583 Abandoned US20230153933A1 (en) | 2018-09-06 | 2023-01-13 | Method for document transformation |
US18/333,387 Abandoned US20240233054A9 (en) | 2018-09-06 | 2023-06-12 | System and method for document transformation and accountability |
US18/453,246 Pending US20240153021A1 (en) | 2018-09-06 | 2023-08-21 | System and method for document transformation and accountability |
US18/460,388 Pending US20240144404A1 (en) | 2018-09-06 | 2023-09-01 | System and method for document transformation |
US18/497,981 Pending US20240177254A1 (en) | 2018-09-06 | 2023-10-30 | Blockchain-based system and method for purchase document transformation and accountability |
Country Status (1)
Country | Link |
---|---|
US (18) | US11803923B1 (en) |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10409783B1 (en) * | 2018-06-06 | 2019-09-10 | Capital One Services, Llc | Distributed work data management |
US20200059363A1 (en) * | 2018-08-17 | 2020-02-20 | Walmart Apollo, Llc | Systems and methods of authenticating items |
WO2020112484A1 (en) * | 2018-11-26 | 2020-06-04 | Kansas State University Research Foundation | Puf-ipa: a puf-based identity preserving lightweight authentication protocol using binary string shuffling |
US11444776B2 (en) * | 2019-05-01 | 2022-09-13 | Kelce S. Wilson | Blockchain with daisy chained records, document corral, quarantine, message timestamping, and self-addressing |
US11567904B2 (en) * | 2019-05-03 | 2023-01-31 | First American Financial Corporation | Distributed ledger systems and methods for importing, accessing, verifying, and comparing documents |
US20220284524A1 (en) * | 2019-06-14 | 2022-09-08 | Arrowhead Development Company Ltd. | Blockchain based real estate registry |
CA3106721A1 (en) * | 2020-01-21 | 2021-07-21 | A Listr Inc. | Web based real estate transaction management platform and methods |
US20230139678A1 (en) * | 2020-03-25 | 2023-05-04 | Boris PAVIC | A digital artwork content digital rights management and content distribution network |
US11568482B1 (en) | 2020-07-29 | 2023-01-31 | Federal Home Loan Mortgage Corporation (Freddie Mac) | Systems and methods for detecting and linking data objects across distributed platforms |
US20220129443A1 (en) * | 2020-10-27 | 2022-04-28 | Genetec Inc. | Document management system and related method |
WO2022104392A1 (en) * | 2020-11-16 | 2022-05-19 | Jpmorgan Chase Bank, N.A. | Systems and methods for blockchain-based data-driven property management |
US20220172308A1 (en) * | 2020-12-02 | 2022-06-02 | Lisa Troyano-Ascolese | Systems, methods, and applications for exchanging, transferring, or conveying objects and/or products within one or more communities |
KR20220099016A (en) * | 2021-01-05 | 2022-07-12 | 삼성전자주식회사 | Electronic apparatus and controlling method thereof |
CN115280717B (en) * | 2021-01-11 | 2024-06-07 | 微福斯有限责任公司 | Blockchain auditing system and method |
US12033195B1 (en) * | 2021-03-29 | 2024-07-09 | Amazon Technologies, Inc. | E-commerce document framework with cross-source and cross-document validation |
US20220391575A1 (en) * | 2021-06-06 | 2022-12-08 | Cinergy Technology Ltd (t/a Gatekeeper) | System for Automated Touchless Contract Management |
US20220398678A1 (en) * | 2021-06-15 | 2022-12-15 | J.E. Fox Company | Automated system to facilitate real estate transactions |
US20220405467A1 (en) * | 2021-06-22 | 2022-12-22 | GovPlus LLC | Automatic form completion |
US11468007B1 (en) * | 2021-09-24 | 2022-10-11 | Reasonal, Inc. | Predictive revision recommendations |
US20230236802A1 (en) * | 2022-01-27 | 2023-07-27 | Accenture Global Solutions Limited | Intelligent industry compliance reviewer |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060010367A1 (en) * | 2004-07-09 | 2006-01-12 | Juergen Sattler | System and method for spreadsheet data integration |
US10740550B1 (en) * | 2017-11-20 | 2020-08-11 | Amazon Technologies, Inc. | Network-accessible data management service with web-of-sheets data model |
US10887357B2 (en) * | 2018-08-22 | 2021-01-05 | International Business Machines Corporation | Document collaboration tool |
Family Cites Families (195)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5848426A (en) | 1993-03-05 | 1998-12-08 | Metanetics Corporation | Automatic data translation between different business systems |
US6658624B1 (en) | 1996-09-24 | 2003-12-02 | Ricoh Company, Ltd. | Method and system for processing documents controlled by active documents with embedded instructions |
US6778651B1 (en) | 1997-04-03 | 2004-08-17 | Southwestern Bell Telephone Company | Apparatus and method for facilitating service management of communications services in a communications network |
US6240429B1 (en) | 1998-08-31 | 2001-05-29 | Xerox Corporation | Using attached properties to provide document services |
US6684196B1 (en) | 1999-07-07 | 2004-01-27 | Ziprealty, Inc. | Beginning-to-end online automation of real estate transactions |
US20010047282A1 (en) | 1999-12-10 | 2001-11-29 | Raveis William M. | System and method for managing real estate transactions |
US6321202B1 (en) | 1999-12-10 | 2001-11-20 | Home Link Services, Inc. | System and method for managing transactions relating to real estate |
US7124354B1 (en) | 2000-03-24 | 2006-10-17 | Hewlett-Packard Development Company, L.P. | Enterprise application transactions as shared active documents |
CA2306579A1 (en) | 2000-04-21 | 2001-10-21 | Malibu Engineering & Software Ltd. | Document-based database management system and method |
US9875492B2 (en) | 2001-05-22 | 2018-01-23 | Dennis J. Dupray | Real estate transaction system |
US7640204B2 (en) | 2000-10-23 | 2009-12-29 | Costar Group, Inc. | System and method for collection, distribution, and use of information in connection with commercial real estate |
US20030074248A1 (en) | 2001-03-31 | 2003-04-17 | Braud Kristopher P. | Method and system for assimilating data from disparate, ancillary systems onto an enterprise system |
US20030036922A1 (en) * | 2001-08-15 | 2003-02-20 | Fries John A. | Method and system for examining real estate abstracts of title |
US20070157079A1 (en) | 2001-08-31 | 2007-07-05 | Baker Jeffrey T | Apparatus and method for negotiating and generating contract documents on-line |
US7818219B2 (en) | 2001-12-27 | 2010-10-19 | American Hungarian Technologies Inc. | Electronic realty and transaction system and method therein |
US7818657B1 (en) | 2002-04-01 | 2010-10-19 | Fannie Mae | Electronic document for mortgage transactions |
US7444302B2 (en) | 2002-06-14 | 2008-10-28 | Ellie Mae, Inc. | Online system for fulfilling loan applications from loan originators |
US20040083164A1 (en) | 2002-07-08 | 2004-04-29 | Schwartz Dennis P. | System and method for generating residential loan documents from multiple and diverse databases |
WO2005006138A2 (en) | 2003-06-30 | 2005-01-20 | Idocuments, Llc | Worker and document management system |
US7548884B1 (en) | 2003-10-21 | 2009-06-16 | Neil Thomas | Computerized process to, for example, automate the home sale, mortgage loan financing and settlement process, and the home mortgage loan refinancing and settlement processes |
US8433650B1 (en) | 2003-10-21 | 2013-04-30 | Neil Thomas | Computerized process to, for example, automate the home sale, mortgage loan financing and settlement process, and the home mortgage loan refinancing and settlement processes |
AU2004237874A1 (en) | 2003-12-23 | 2005-07-07 | Canon Kabushiki Kaisha | Method for Specifying Data for the Assembly of a Document Set |
US7822690B2 (en) | 2004-02-10 | 2010-10-26 | Paul Rakowicz | Paperless process for mortgage closings and other applications |
US7801739B2 (en) | 2004-04-27 | 2010-09-21 | Smith Jeffrey C | System, method and computer program product for facilitating a real estate exchange |
WO2006020801A2 (en) * | 2004-08-11 | 2006-02-23 | Docutech Corporation | Technique for automatically determining and populating mortgage lending documents |
KR101277385B1 (en) | 2004-10-19 | 2013-06-20 | 아폴로 엔터프라이즈 솔루션스, 엘엘씨 | System and method for resolving transactions |
US9076185B2 (en) * | 2004-11-30 | 2015-07-07 | Michael Dell Orfano | System and method for managing electronic real estate registry information |
US20060235715A1 (en) * | 2005-01-14 | 2006-10-19 | Abrams Carl E | Sharable multi-tenant reference data utility and methods of operation of same |
US7568104B2 (en) | 2005-01-19 | 2009-07-28 | International Business Machines Corporation | Method and apparatus for adding signature information to electronic documents |
US7725359B1 (en) | 2005-04-21 | 2010-05-25 | Jennifer Katzfey | Electronic realty systems and methods |
US7941744B2 (en) | 2005-04-25 | 2011-05-10 | Adp, Inc. | System and method for electronic document generation and delivery |
US20080091700A1 (en) | 2005-05-31 | 2008-04-17 | Brotherson Bradley R | Network-based document generation and processing |
US8438476B2 (en) | 2005-10-14 | 2013-05-07 | Uhlig Llc | Dynamic variable-content publishing |
US20070214120A1 (en) * | 2006-03-08 | 2007-09-13 | Barrett Burke Wilson Castle Daffin & Frappier Llp | System and Method for Electronic Processing of Title Records |
US20070244798A1 (en) | 2006-03-22 | 2007-10-18 | Jason Weidenbenner | Systems and methods for real estate process management |
US8423469B2 (en) | 2006-04-07 | 2013-04-16 | Michael B. Marlow | System and method for enhancing the efficiency of real estate transactions |
US10176540B2 (en) * | 2006-10-17 | 2019-01-08 | First American Title Insurance Company | Apparatus and method for generating title products |
US20080091954A1 (en) | 2006-10-17 | 2008-04-17 | Morris Daniel R | Method and system for facilitating printed page authentication, unique code generation and content integrity verification of documents |
US20080133572A1 (en) | 2006-12-05 | 2008-06-05 | Siemens Medical Solutions Usa, Inc. | System and User Interface for Adaptively Migrating, Pre-populating and Validating Data |
US8046389B2 (en) | 2006-12-22 | 2011-10-25 | Sap Ag | Automatic data determination |
US8165939B1 (en) | 2007-04-23 | 2012-04-24 | Reass Richard M | Method of settling a real estate transaction and system implementing the method |
US8200713B2 (en) | 2008-02-28 | 2012-06-12 | Research In Motion Limited | Database exploration for building wireless component applications |
US20090319927A1 (en) | 2008-06-21 | 2009-12-24 | Microsoft Corporation | Checking document rules and presenting contextual results |
US7992037B2 (en) | 2008-09-11 | 2011-08-02 | Nec Laboratories America, Inc. | Scalable secondary storage systems and methods |
CA2736502C (en) | 2008-09-18 | 2017-10-17 | Burton Kozak | Peg board hook |
US7930447B2 (en) | 2008-10-17 | 2011-04-19 | International Business Machines Corporation | Listing windows of active applications of computing devices sharing a keyboard based upon requests for attention |
US8417625B2 (en) | 2008-10-27 | 2013-04-09 | Bank Of America Corporation | Apparatus and methods for facilitating real estate transactions |
US8805861B2 (en) | 2008-12-09 | 2014-08-12 | Google Inc. | Methods and systems to train models to extract and integrate information from data sources |
US20190311447A1 (en) | 2018-01-08 | 2019-10-10 | Domos. LLC | Method and apparatus for real time, dynamic management of real estate finance, services, and reporting |
US20100293108A1 (en) | 2009-05-14 | 2010-11-18 | Sam Gurvitch | Automated Practice Management System |
US8095427B1 (en) | 2009-07-04 | 2012-01-10 | Buxton Brad B | Methods for facilitating an online transaction of a firearm |
US20110270766A1 (en) | 2010-05-02 | 2011-11-03 | Offer XChange, LLC. | Internet Based Offer Routing and Workflow Engine Method |
US20110276395A1 (en) | 2010-05-04 | 2011-11-10 | Gaton Jonathan L | New age real estate marketing method and system |
US20110289010A1 (en) | 2010-05-21 | 2011-11-24 | Rankin Jr Claiborne R | Apparatuses, methods and systems for an activity tracking and property transaction facilitating hub user interface |
US9152946B2 (en) | 2010-05-21 | 2015-10-06 | Brokersavant Inc. | Apparatuses, methods and systems for a lead generating hub |
US10109027B1 (en) | 2010-09-01 | 2018-10-23 | Brian T. Stack | Database access and community electronic medical records system |
US8880538B1 (en) | 2011-02-08 | 2014-11-04 | Google Inc. | Electronic document encoding |
US20120221944A1 (en) | 2011-02-28 | 2012-08-30 | Bloomfield Richard H | System for digital and remote document revision and execution with document escrow |
US8718612B2 (en) | 2011-03-08 | 2014-05-06 | Bank Of American Corporation | Real-time analysis involving real estate listings |
US20120246084A1 (en) | 2011-03-23 | 2012-09-27 | Ryan Marshall | Systems and Methods for Real Estate Documentation Preparation |
US20130290195A1 (en) * | 2012-04-27 | 2013-10-31 | Lps Ip Holding Company, Inc. | Determination of appraisal accuracy |
US20130144683A1 (en) | 2011-12-06 | 2013-06-06 | HMVP Partners, LLC | Determining residential transaction price indices based on prior transaction prices |
US20130198598A1 (en) | 2012-01-18 | 2013-08-01 | OneID Inc. | Secure population of form data |
US20170039604A1 (en) | 2012-03-07 | 2017-02-09 | Hobart Sze | Tracking Metrics for Display in Advertisements |
US20130262290A1 (en) | 2012-03-30 | 2013-10-03 | Alan Hanson | Method and system to automatically generate loan offer information based upon the geo-location of an end-users mobile computing device or apparatus. |
WO2013170268A2 (en) | 2012-05-11 | 2013-11-14 | Contract Room, Inc. | System and method for dynamic transaction management and collaborative authoring of a negotiable document |
US11631265B2 (en) | 2012-05-24 | 2023-04-18 | Esker, Inc. | Automated learning of document data fields |
US20130339189A1 (en) | 2012-06-18 | 2013-12-19 | Jonathan Minerick | Method and apparatus for facilitating real estate transactions |
US20140279573A1 (en) | 2013-03-15 | 2014-09-18 | Walter E. Coats Revocable Trust | System and method for automatic and intelligent form generation |
US8949151B2 (en) | 2013-04-24 | 2015-02-03 | Tpp Holdings, Llc | System and method for transferring a timeshare property |
US10332216B2 (en) | 2013-05-10 | 2019-06-25 | Intuit, Inc. | Streamlined sales tax return preparation |
US9659334B2 (en) | 2013-07-12 | 2017-05-23 | Mls Offers Llc | Systems and methods for facilitating real estate transactions with purchase offer processing feature |
US20150052080A1 (en) * | 2013-08-15 | 2015-02-19 | Creisoft, Inc. | Systems and methods for managing real estate investments |
US20150081497A1 (en) | 2013-09-17 | 2015-03-19 | Tarun Patel | System and method for managing a real estate and/or business transaction process between a buyer and a seller |
US9563617B2 (en) | 2013-09-23 | 2017-02-07 | Oracle International Corporation | Custom validation of values for fields of submitted forms |
CA2829469A1 (en) | 2013-10-07 | 2015-04-07 | Milan Baic | Computer system and method for providing a multi-user transaction platform accessible using a mobile device |
US9507760B2 (en) * | 2013-12-19 | 2016-11-29 | Citrix Systems, Inc. | Methods and apparatus for electronic document handling |
US20150193892A1 (en) * | 2014-01-06 | 2015-07-09 | X Stream Info, Llc | Parcel data collection and analysis systems, devices, and methods |
US9286403B2 (en) | 2014-02-04 | 2016-03-15 | Shoobx, Inc. | Computer-guided corporate governance with document generation and execution |
US10552525B1 (en) | 2014-02-12 | 2020-02-04 | Dotloop, Llc | Systems, methods and apparatuses for automated form templating |
US20150261795A1 (en) | 2014-03-12 | 2015-09-17 | SeyfarthLean Consulting LLC | Computer-based system and method of structuring a specialized database for automatically generating financial disclosure documents |
US10013411B2 (en) | 2014-04-30 | 2018-07-03 | Adobe Systems Incorporated | Automating data entry for fields in electronic documents |
US10133718B2 (en) | 2014-07-18 | 2018-11-20 | FHOOSH, Inc. | Systems and methods for locating, identifying and mapping electronic form fields |
US9608829B2 (en) | 2014-07-25 | 2017-03-28 | Blockchain Technologies Corporation | System and method for creating a multi-branched blockchain with configurable protocol rules |
US20160035053A1 (en) * | 2014-08-01 | 2016-02-04 | Key DMS, Inc. | Web based electronic and paperless real estate transaction and closing system |
US10997643B2 (en) | 2014-09-05 | 2021-05-04 | Realogy Holdings Corp. | Real estate offer management system |
US10592985B2 (en) | 2015-03-02 | 2020-03-17 | Dell Products L.P. | Systems and methods for a commodity contracts market using a secure distributed transaction ledger |
US10740372B2 (en) | 2015-04-02 | 2020-08-11 | Canon Information And Imaging Solutions, Inc. | System and method for extracting data from a non-structured document |
US20160300234A1 (en) | 2015-04-06 | 2016-10-13 | Bitmark, Inc. | System and method for decentralized title recordation and authentication |
KR101628009B1 (en) * | 2015-04-20 | 2016-06-13 | 주식회사 코인플러그 | System for dealing a digital currency with block chain |
US20160342977A1 (en) * | 2015-05-20 | 2016-11-24 | Vennd.io Pty Ltd | Device, method and system for virtual asset transactions |
US10075298B2 (en) | 2015-06-02 | 2018-09-11 | ALTR Solutions, Inc. | Generation of hash values within a blockchain |
AU2016288644A1 (en) | 2015-07-02 | 2018-02-22 | Nasdaq, Inc. | Systems and methods of secure provenance for distributed transaction databases |
US9696817B2 (en) | 2015-07-09 | 2017-07-04 | Blackberry Limited | Portable electronic device including keyboard and method of controlling the same |
US10402792B2 (en) * | 2015-08-13 | 2019-09-03 | The Toronto-Dominion Bank | Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers |
US10785033B2 (en) | 2015-09-04 | 2020-09-22 | Nec Corporation | Method for storing an object on a plurality of storage nodes |
CA2941896C (en) | 2015-09-14 | 2020-10-13 | The Toronto-Dominion Bank | Connected device-based property evaluation |
US20170186116A1 (en) | 2015-10-05 | 2017-06-29 | 1Tract Llc | System and method of monitoring, measuring and reporting of post-closing processes in real estate purchase transactions and delivery of title insurance policies |
US10013573B2 (en) | 2015-12-16 | 2018-07-03 | International Business Machines Corporation | Personal ledger blockchain |
US10521780B1 (en) | 2015-12-16 | 2019-12-31 | United Services Automobile Association (Usaa) | Blockchain based transaction management |
US10255108B2 (en) * | 2016-01-26 | 2019-04-09 | International Business Machines Corporation | Parallel execution of blockchain transactions |
US9849364B2 (en) * | 2016-02-02 | 2017-12-26 | Bao Tran | Smart device |
US20170236104A1 (en) | 2016-02-12 | 2017-08-17 | D+H Usa Corporation | Peer-to-Peer Financial Transactions Using A Private Distributed Ledger |
US20170243193A1 (en) * | 2016-02-18 | 2017-08-24 | Skuchain, Inc. | Hybrid blockchain |
US10026118B2 (en) | 2016-02-22 | 2018-07-17 | Bank Of America Corporation | System for allowing external validation of data in a process data network |
US20200327498A1 (en) * | 2016-03-21 | 2020-10-15 | National Ict Australia Limited | Business Process Execution on a Blockchain Platform |
GB201705016D0 (en) | 2016-03-31 | 2017-05-10 | Sei Global Services Inc | Dynamic generation of electronic forms and documents |
US10521775B2 (en) | 2016-04-18 | 2019-12-31 | R3 Ltd. | Secure processing of electronic transactions by a decentralized, distributed ledger system |
US10046228B2 (en) * | 2016-05-02 | 2018-08-14 | Bao Tran | Smart device |
US10022613B2 (en) | 2016-05-02 | 2018-07-17 | Bao Tran | Smart device |
US10532268B2 (en) | 2016-05-02 | 2020-01-14 | Bao Tran | Smart device |
US10362058B2 (en) | 2016-05-13 | 2019-07-23 | Vmware, Inc | Secure and scalable data transfer using a hybrid blockchain-based approach |
WO2017203093A1 (en) * | 2016-05-25 | 2017-11-30 | Nokia Technologies Oy | Method, device and system for utilizing block chain to define trusted circle |
US20170345011A1 (en) * | 2016-05-26 | 2017-11-30 | Hitfin, Inc. | System and method executed on a blockchain network |
CA3024078C (en) | 2016-05-29 | 2024-04-09 | Wix.Com Ltd. | Creation and update of hierarchical websites based on collected business knowledge |
US10291604B2 (en) | 2016-06-03 | 2019-05-14 | Docusign, Inc. | Universal access to document transaction platform |
WO2018006072A1 (en) * | 2016-06-30 | 2018-01-04 | Clause, Inc. | Systems and method for forming, storing, managing,and executing contracts |
US20180018738A1 (en) | 2016-07-14 | 2018-01-18 | Digital Asset Holdings | Digital asset platform |
US10097344B2 (en) | 2016-07-15 | 2018-10-09 | Mastercard International Incorporated | Method and system for partitioned blockchains and enhanced privacy for permissioned blockchains |
US20180018311A1 (en) | 2016-07-15 | 2018-01-18 | Intuit Inc. | Method and system for automatically extracting relevant tax terms from forms and instructions |
US10878522B2 (en) | 2016-08-18 | 2020-12-29 | First American Financial Corporation | Systems and methods for using blockchains to record, manage, and transfer ownership rights to land titles |
US20180053265A1 (en) * | 2016-08-19 | 2018-02-22 | Benjamin Wade Lyon | Method and System for Engaging and Coordinating Real Estate Transactions from Contact to Contract |
WO2018061027A1 (en) * | 2016-09-28 | 2018-04-05 | Ankur Gupta | Systems, methods, and devices for facilitating property based transactions |
US20180096362A1 (en) | 2016-10-03 | 2018-04-05 | Amy Ashley Kwan | E-Commerce Marketplace and Platform for Facilitating Cross-Border Real Estate Transactions and Attendant Services |
US20180108089A1 (en) | 2016-10-14 | 2018-04-19 | International Business Machines Corporation | Transactions and linked assets on a blockchain |
US20180130034A1 (en) | 2016-11-07 | 2018-05-10 | LedgerDomain, LLC | Extended blockchains for event tracking and management |
US20180137479A1 (en) | 2016-11-16 | 2018-05-17 | Digifund LLC | Secure system for implementing an international currency unit platform |
US20180143975A1 (en) | 2016-11-18 | 2018-05-24 | Lionbridge Technologies, Inc. | Collection strategies that facilitate arranging portions of documents into content collections |
US10586210B2 (en) * | 2016-11-30 | 2020-03-10 | International Business Machines Corporation | Blockchain checkpoints and certified checkpoints |
US10984016B2 (en) | 2016-12-02 | 2021-04-20 | Persephone GmbH | Apparatuses, systems and methods for processing, acknowledging, transferring and custody of assets or rights on a distributed ledger |
US20180167198A1 (en) | 2016-12-09 | 2018-06-14 | Cisco Technology, Inc. | Trust enabled decentralized asset tracking for supply chain and automated inventory management |
US10552381B2 (en) | 2016-12-16 | 2020-02-04 | International Business Machines Corporation | Shared document editing in the blockchain |
US20180205546A1 (en) | 2016-12-31 | 2018-07-19 | Assetvault Limited | Systems, methods, apparatuses for secure management of legal documents |
US10608824B1 (en) * | 2017-01-09 | 2020-03-31 | Amazon Technologies, Inc. | Merkle signature scheme tree expansion |
US10713714B2 (en) | 2017-01-10 | 2020-07-14 | Escrowtab, Inc. | Escrow tab mobile application system and method |
US10776879B1 (en) | 2017-01-17 | 2020-09-15 | State Farm Mutual Automobile Insurance Company | Blockchain controlled multi-carrier auction system for usage-based auto insurance |
US10158479B2 (en) | 2017-02-06 | 2018-12-18 | Northern Trust Corporation | Systems and methods for generating, uploading and executing code blocks within distributed network nodes |
US11755997B2 (en) | 2017-02-22 | 2023-09-12 | Anduin Transactions, Inc. | Compact presentation of automatically summarized information according to rule-based graphically represented information |
US10402480B2 (en) | 2017-03-28 | 2019-09-03 | Experian Health, Inc. | PDF to web form conversion |
US20180285810A1 (en) | 2017-03-29 | 2018-10-04 | Ripe Technology, Inc. | Systems and methods of blockchain transaction recordation in a food supply chain |
US10832357B1 (en) | 2017-03-30 | 2020-11-10 | Jamie Michele Pagliano | Real estate transaction facilitating process and incoming property offer notification system |
US11250500B2 (en) * | 2017-03-31 | 2022-02-15 | Loancraft, Llc | Method and system for performing income analysis from source documents |
US10102265B1 (en) | 2017-04-12 | 2018-10-16 | Vijay K. Madisetti | Method and system for tuning blockchain scalability for fast and low-cost payment and transaction processing |
US10404471B1 (en) | 2017-04-26 | 2019-09-03 | Wells Fargo Bank, N.A. | Secure ledger assurance tokenization |
US10943294B1 (en) | 2017-05-10 | 2021-03-09 | State Farm Mutual Automobile Insurance Company | Continuously monitoring and updating mortgage ready data |
US10896169B2 (en) | 2017-05-12 | 2021-01-19 | International Business Machines Corporation | Distributed system, computer program product and method |
WO2018209543A1 (en) | 2017-05-16 | 2018-11-22 | 北京大学深圳研究生院 | Method for maintaining indexes and chain topology between multi-level blockchain systems |
US10740733B2 (en) * | 2017-05-25 | 2020-08-11 | Oracle International Corporaton | Sharded permissioned distributed ledgers |
DE102017209014A1 (en) | 2017-05-30 | 2018-12-06 | Robert Bosch Gmbh | Method and apparatus for attaching transactions to a block chain |
JP2020522796A (en) | 2017-06-01 | 2020-07-30 | シュヴェイ, インク. ディー/ビー/エー アクソーニSCHVEY, INC. d/b/a AXONI | A distributed, privately subspaced blockchain data structure that manages secure access restrictions |
US20180365201A1 (en) * | 2017-06-14 | 2018-12-20 | Clause, Inc. | System and method for compound data-driven contracts and documentation |
GB2563429A (en) | 2017-06-15 | 2018-12-19 | Hsbc Group Man Services Limited | System for dynamic user interface generation |
CA3068427A1 (en) | 2017-06-27 | 2019-01-03 | Jpmorgan Chase Bank, N.A. | System and method for using a distributed ledger gateway |
US10944546B2 (en) | 2017-07-07 | 2021-03-09 | Microsoft Technology Licensing, Llc | Blockchain object interface |
US10616324B1 (en) * | 2017-07-20 | 2020-04-07 | Architecture Technology Corporation | Decentralized ledger system and method for enterprises |
US10452776B2 (en) * | 2017-07-28 | 2019-10-22 | International Business Machines Corporation | Cognitive mediator for generating blockchain smart contracts |
US11146380B2 (en) | 2017-08-03 | 2021-10-12 | Parity Technologies Ltd. | Methods and systems for a heterogeneous multi-chain framework |
US20190066101A1 (en) | 2017-08-22 | 2019-02-28 | Sap Se | Transaction Platform Providing Unified View on Multiple Heterogeneous Blockchains |
US20190066068A1 (en) | 2017-08-22 | 2019-02-28 | Sap Se | Transaction Platform Providing Unified Interaction with Multiple Heterogeneous Blockchains |
CN109426949B (en) | 2017-08-29 | 2021-02-09 | 华为技术有限公司 | Cross-chain transaction method and device |
US20190066205A1 (en) | 2017-08-30 | 2019-02-28 | StartEngine Crowdfunding, Inc. | Peer-to-peer trading with blockchain technology |
US11062407B2 (en) | 2017-09-05 | 2021-07-13 | Shelterzoom Corp. | Blockchain-powered real estate sales and rental system |
US20190087547A1 (en) | 2017-09-15 | 2019-03-21 | Go Daddy Operating Company, LLC | Data capture method |
US11023608B2 (en) | 2017-09-15 | 2021-06-01 | Identify3D, Inc. | System and method for data management and security for digital manufacturing |
US10002398B1 (en) | 2017-09-27 | 2018-06-19 | Jilla Gila Isaacson | System for facilitating real estate transaction |
US10977629B2 (en) | 2017-09-29 | 2021-04-13 | Oracle Financial Services Software Limited | Computerized messaging module for blockchain networks |
US11449864B2 (en) | 2017-10-31 | 2022-09-20 | R3 Ltd. | Reissuing obligations to preserve privacy |
US10911219B2 (en) | 2017-12-01 | 2021-02-02 | International Business Machines Corporation | Hierarchical blockchain consensus optimization scheme |
WO2019118447A1 (en) * | 2017-12-11 | 2019-06-20 | Celo Labs Inc. | Decentralized database associating public keys and communications addresses |
US11032293B2 (en) | 2018-02-10 | 2021-06-08 | SmartAxiom, Inc. | System and method for managing and securing a distributed ledger for a decentralized peer-to-peer network |
US20190251199A1 (en) | 2018-02-14 | 2019-08-15 | Ivan Klianev | Transactions Across Blockchain Networks |
US11088826B2 (en) | 2018-02-27 | 2021-08-10 | International Business Machines Corporation | Managing assets with expiration on a blockchain |
US11095446B2 (en) | 2018-02-27 | 2021-08-17 | Anchor Labs, Inc. | Cryptoasset custodial system with different rules governing access to logically separated cryptoassets and proof-of-stake blockchain support |
US20190266683A1 (en) | 2018-02-28 | 2019-08-29 | Greg Burns | Method and System for Automated Real Estate Information and Offers |
US20190279321A1 (en) | 2018-03-12 | 2019-09-12 | IdeaBlock LLC | Proof of public idea disclosure using blockchain |
US20190311343A1 (en) | 2018-04-06 | 2019-10-10 | Walmart Apollo, Llc | Point of sale system network with distributed ownership record database |
US10728219B2 (en) | 2018-04-13 | 2020-07-28 | R3 Ltd. | Enhancing security of communications during execution of protocol flows |
US10084600B1 (en) * | 2018-04-16 | 2018-09-25 | Xage Security, Inc. | Decentralized information protection for confidentiality and tamper-proofing on distributed database |
US11010403B2 (en) | 2018-04-24 | 2021-05-18 | Microsoft Technology Licensing, Llc | Relational distributed ledger for smart contracts |
US20190332711A1 (en) | 2018-04-30 | 2019-10-31 | Nutanix, Inc. | Initialization of a disaster recovery site from a physically-transported initial dataset |
US10747201B2 (en) * | 2018-05-02 | 2020-08-18 | Rockwell Automation Technologies, Inc. | Subscription-based services using industrial blockchains |
US20190361917A1 (en) * | 2018-05-25 | 2019-11-28 | Bao Tran | Smart device |
US11049148B2 (en) * | 2018-06-01 | 2021-06-29 | Concord Technologies Inc. | User control of anonymized profiling data using public and private blockchains in an electronic ad marketplace |
US20190378134A1 (en) | 2018-06-08 | 2019-12-12 | R3 Ltd. | Annotations for protocol flow implementing transactions of a distributed ledger system |
US20190378165A1 (en) | 2018-06-11 | 2019-12-12 | Coin Mutual Funds LLC | Inducing actions in consumer entities |
CA3046542A1 (en) | 2018-06-15 | 2019-12-15 | Bank Of Montreal | New issue management system |
US20200007343A1 (en) | 2018-06-28 | 2020-01-02 | Blockchain Integrated Partners, Llc | Systems and methods for data validation and assurance |
US11682086B2 (en) | 2018-06-29 | 2023-06-20 | Itron, Inc. | Operating smart sensors using distributed ledgers |
US20200034940A1 (en) | 2018-07-24 | 2020-01-30 | Opendoor Labs Inc. | Contract generation and templating |
US20200042989A1 (en) | 2018-07-31 | 2020-02-06 | Ramesh Ramadoss | Asset-backed tokens |
US20200051186A1 (en) | 2018-08-10 | 2020-02-13 | Drift Marketplace, Inc. | Real-time renewable energy credits |
US20200058023A1 (en) | 2018-08-14 | 2020-02-20 | Grandata Inc. | Decentralized Data Marketplace |
US11424938B1 (en) * | 2018-09-06 | 2022-08-23 | Fall Guy Llc | Credentialed miners for a blockchain |
US11860822B2 (en) * | 2018-11-19 | 2024-01-02 | Luther Systems Us Incorporated | Immutable ledger with efficient and secure data destruction, system and method |
US11301845B2 (en) * | 2019-08-19 | 2022-04-12 | Anchor Labs, Inc. | Cryptoasset custodial system with proof-of-stake blockchain support |
-
2019
- 2019-09-04 US US16/560,980 patent/US11803923B1/en active Active
- 2019-09-04 US US16/560,988 patent/US11314699B1/en active Active
- 2019-09-04 US US16/560,964 patent/US11263395B1/en active Active
- 2019-09-04 US US16/560,973 patent/US11557011B1/en active Active
- 2019-09-04 US US16/560,976 patent/US11145017B1/en active Active
- 2019-09-04 US US16/560,984 patent/US11227350B1/en active Active
- 2019-09-04 US US16/560,982 patent/US11341102B1/en active Active
-
2021
- 2021-10-11 US US17/498,513 patent/US11488269B2/en active Active
-
2022
- 2022-01-17 US US17/577,179 patent/US11748831B2/en active Active
- 2022-02-28 US US17/683,177 patent/US20220188507A1/en not_active Abandoned
- 2022-04-25 US US17/728,755 patent/US11734781B2/en active Active
- 2022-05-23 US US17/751,387 patent/US11869107B2/en active Active
- 2022-10-31 US US17/978,034 patent/US11676229B2/en active Active
-
2023
- 2023-01-13 US US18/154,583 patent/US20230153933A1/en not_active Abandoned
- 2023-06-12 US US18/333,387 patent/US20240233054A9/en not_active Abandoned
- 2023-08-21 US US18/453,246 patent/US20240153021A1/en active Pending
- 2023-09-01 US US18/460,388 patent/US20240144404A1/en active Pending
- 2023-10-30 US US18/497,981 patent/US20240177254A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060010367A1 (en) * | 2004-07-09 | 2006-01-12 | Juergen Sattler | System and method for spreadsheet data integration |
US10740550B1 (en) * | 2017-11-20 | 2020-08-11 | Amazon Technologies, Inc. | Network-accessible data management service with web-of-sheets data model |
US10887357B2 (en) * | 2018-08-22 | 2021-01-05 | International Business Machines Corporation | Document collaboration tool |
Also Published As
Publication number | Publication date |
---|---|
US20240153021A1 (en) | 2024-05-09 |
US11227350B1 (en) | 2022-01-18 |
US11748831B2 (en) | 2023-09-05 |
US20220027345A1 (en) | 2022-01-27 |
US11314699B1 (en) | 2022-04-26 |
US20240144404A1 (en) | 2024-05-02 |
US11145017B1 (en) | 2021-10-12 |
US11676229B2 (en) | 2023-06-13 |
US11263395B1 (en) | 2022-03-01 |
US11488269B2 (en) | 2022-11-01 |
US20220138878A1 (en) | 2022-05-05 |
US11734781B2 (en) | 2023-08-22 |
US20220284525A1 (en) | 2022-09-08 |
US20240135476A1 (en) | 2024-04-25 |
US20240177254A1 (en) | 2024-05-30 |
US20240233054A9 (en) | 2024-07-11 |
US11557011B1 (en) | 2023-01-17 |
US20230153933A1 (en) | 2023-05-18 |
US11803923B1 (en) | 2023-10-31 |
US11341102B1 (en) | 2022-05-24 |
US11869107B2 (en) | 2024-01-09 |
US20230051175A1 (en) | 2023-02-16 |
US20220253959A1 (en) | 2022-08-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11263395B1 (en) | System and method for document transformation and compliance | |
US8078512B1 (en) | Document manifest and publication in association with dataset quality control | |
Spielman | Blockchain: digitally rebuilding the real estate industry | |
US8527401B2 (en) | Product, system and method for certification of closing and mortgage loan fulfillment | |
US7742991B2 (en) | Method & system for managing and preparing documentation for real estate transactions | |
US20220405852A1 (en) | System and method for tracking proof of insurance and insurance compliance | |
US20060074793A1 (en) | Transaction management system | |
US7313540B1 (en) | Electronic communication system and method for facilitating financial transaction bidding and reporting processes | |
US20060155570A1 (en) | Aggregation and control of documents in the document repository using meta data and context information and creation of online info binder | |
US8799117B2 (en) | Record retention and post-issuance compliance system and method for municipal bonds | |
US7146333B2 (en) | Report generator for allowing a financial entity to monitor securities class action lawsuits and potential monetary claims resulting therefrom | |
US20150006436A1 (en) | Report generator for allowing a financial entity to monitor securities class action lawsuits and potential monetary claims resulting therefrom | |
US20100257109A1 (en) | System and Method for Associating Documents in a Transaction with Transaction Data | |
US20240087063A1 (en) | Computer-implemented document transformation systems and methods | |
Grody | Can a globally endorsed business identity code be the answer to risk data aggregation? | |
EP1211607A2 (en) | Automated document drafting system and method | |
Boritz et al. | Computer-assisted functions for auditing XBRL-related documents | |
Kutan | BANKABILITY OF CUSTOMARY LAND IN PAPUA NEW GUINEA: CHALLENGES AND PROSPECTS | |
Lambert | System for Award Management (SAM)--creating efficiencies in federal government contracting through the use of streamlining and integration | |
CA2317280A1 (en) | Automated use of public record information to automatically complete real estate transactions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:SIDE, INC.;REEL/FRAME:065488/0201 Effective date: 20231107 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |