US 11,748,831 B2
System and method for document transformation
Edward Wu, San Mateo, CA (US); Guy Gal, San Francisco, CA (US); Christopher Dzoba, San Francisco, CA (US); Jeffrey Judkins, Richmond, CA (US); Mark J. Stefik, Portola Valley, CA (US); and Adriano Castro, San Francisco, CA (US)
Assigned to Side, Inc., San Francisco, CA (US)
Filed by SIDE, INC., San Francisco, CA (US)
Filed on Jan. 17, 2022, as Appl. No. 17/577,179.
Application 17/577,179 is a continuation of application No. 16/560,984, filed on Sep. 4, 2019, granted, now 11,227,350.
Claims priority of provisional application 62/728,051, filed on Sep. 6, 2018.
Prior Publication US 2022/0138878 A1, May 5, 2022
Int. Cl. G06F 17/00 (2019.01); G06Q 50/16 (2012.01); H04L 9/06 (2006.01); G06F 16/182 (2019.01); G06Q 20/38 (2012.01); G06F 16/27 (2019.01); G06Q 10/0631 (2023.01); G06F 40/186 (2020.01); G06F 40/174 (2020.01); G06F 21/64 (2013.01); G06V 30/418 (2022.01); G06F 16/13 (2019.01); G06F 16/248 (2019.01); G06F 16/23 (2019.01); H04L 9/00 (2022.01); G06Q 20/02 (2012.01); H04L 9/08 (2006.01); H04L 9/32 (2006.01)
CPC G06Q 50/167 (2013.01) [G06F 16/137 (2019.01); G06F 16/1834 (2019.01); G06F 16/1837 (2019.01); G06F 16/2358 (2019.01); G06F 16/248 (2019.01); G06F 16/27 (2019.01); G06F 21/64 (2013.01); G06F 40/174 (2020.01); G06F 40/186 (2020.01); G06Q 10/06314 (2013.01); G06Q 20/02 (2013.01); G06Q 20/3827 (2013.01); G06Q 50/16 (2013.01); G06V 30/418 (2022.01); H04L 9/0637 (2013.01); H04L 9/0643 (2013.01); H04L 9/0825 (2013.01); H04L 9/3236 (2013.01); H04L 9/50 (2022.05); G06Q 2220/00 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A system for document transformation, comprising: a database of documents; and a compliance server comprising memory and a processor, wherein the computer processor is configured to perform the following: receive an address from a user;
generate a set of documents for a transaction based on the address, wherein each document comprises one or more data fields and an identifier comprising a string of one or more of numbers and letters for each of the data fields; assign a transaction number to the set of documents; receive data values from the user for population of at least a portion of the data fields in one of the documents in the set; store the data values and the identifier for the data field in which each data value is populated with the transaction number; generate a data model for the transaction comprising the identifiers having the string of one or more numbers and letters, and the data values; and populate remaining documents in the set using the data model, comprising: identify one of the identifiers comprising the string of one or more of numbers and letters for one of the data fields in one or more of the remaining documents; select the data model associated with the transaction from a collection of data models for other transactions; look up the identifier in the data model; determine for one of the data fields in one of the remaining documents, the data value associated with the data field based on the identifier comprising the string of one or more of numbers and letters and the transaction number; and populate the data fields in the remaining documents with the determined data value.