WO2018098507A1 - Système et procédé de création automatique de rapports réglementaires - Google Patents

Système et procédé de création automatique de rapports réglementaires Download PDF

Info

Publication number
WO2018098507A1
WO2018098507A1 PCT/US2017/064191 US2017064191W WO2018098507A1 WO 2018098507 A1 WO2018098507 A1 WO 2018098507A1 US 2017064191 W US2017064191 W US 2017064191W WO 2018098507 A1 WO2018098507 A1 WO 2018098507A1
Authority
WO
WIPO (PCT)
Prior art keywords
reporting
regulatory
electronic document
enterprise data
form electronic
Prior art date
Application number
PCT/US2017/064191
Other languages
English (en)
Inventor
Noam Guzman
Isaac SAFT
Original Assignee
Vatbox, Ltd.
M&B IP Analysts, LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US15/361,934 external-priority patent/US20170154385A1/en
Application filed by Vatbox, Ltd., M&B IP Analysts, LLC filed Critical Vatbox, Ltd.
Publication of WO2018098507A1 publication Critical patent/WO2018098507A1/fr
Priority to US16/376,854 priority Critical patent/US20190236126A1/en

Links

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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/10—Tax strategies
    • 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/26—Government or public services

Definitions

  • the present disclosure relates generally to regulatory reports, and more particularly to the creation and submission of regulatory reports based on enterprise data.
  • Taxes and other levies are imposed upon a taxpayer, whether they be an individual or a legal entity, by a state or subdivision thereof in order to fund various public expenditures. Taxes are also imposed by many administrative divisions for various activities. A failure to pay, evasion of, or resistance to taxation is usually punishable by law.
  • Certain embodiments disclosed herein include a method for creating regulatory reports based on enterprise data, including: determining if regulatory reporting requirements are satisfied based on enterprise data, wherein the enterprise data is from an enterprise server; retrieving a reporting form electronic document when the reporting requirements have not been satisfied, wherein the reporting form electronic document includes at least partially unstructured data; analyzing the reporting form electronic document to determine at least one reporting requirement parameter relevant to the regulatory reporting requirements; creating a template based on the analysis of the reporting form electronic document, wherein the template is a structured dataset including the determined at least one reporting requirement parameter; and creating a report electronic document based on the template and the enterprise data, wherein the report electronic document is the reporting form electronic document completed using at least a portion of the enterprise data in compliance with the regulatory reporting requirements.
  • Certain embodiments disclosed herein also include a non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to perform a process, the process comprising: determining if regulatory reporting requirements are satisfied based on enterprise data, wherein the enterprise data is from an enterprise server; retrieving a reporting form electronic document when the reporting requirements have not been satisfied, wherein the reporting form electronic document includes at least partially unstructured data; analyzing the reporting form electronic document to determine at least one reporting requirement parameter relevant to the regulatory reporting requirements; creating a template based on the analysis of the reporting form electronic document, wherein the template is a structured dataset including the determined at least one reporting requirement parameter; and creating a report electronic document based on the template and the enterprise data, wherein the report electronic document is the reporting form electronic document completed using at least a portion of the enterprise data in compliance with the regulatory reporting requirements.
  • Certain embodiments disclosed herein also include a system for creating regulatory reports based on enterprise data.
  • the system comprises: a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: determine if regulatory reporting requirements are satisfied based on enterprise data, wherein the enterprise data is collected from an enterprise server; retrieve a reporting form electronic document when the reporting requirements have not been satisfied, wherein the reporting form electronic document includes at least partially unstructured data; analyze the reporting form electronic document to determine at least one reporting requirement parameter relevant to the regulatory reporting requirements; create a template based on the analysis of the reporting form electronic document, wherein the template is a structured dataset including the determined at least one reporting requirement parameter; and create a report electronic document based on the template and the enterprise data, wherein the report electronic document is the reporting form electronic document completed using at least a portion of the enterprise data in compliance with the regulatory reporting requirements.
  • Figure 1 is a network diagram utilized to describe the various disclosed embodiments.
  • Figure 2 is a schematic diagram of a regulatory reporting system according to an embodiment.
  • Figure 3 is a flowchart illustrating a method for automatically submitting regulatory reports based on electronic documents according to an embodiment.
  • Figure 4 is a flowchart illustrating a method for creating a dataset based on at least one electronic document according to an embodiment.
  • the various disclosed embodiments include a method and system for the submission of regulatory reports based on enterprise data.
  • Enterprise data including financial statements, previously filed regulatory reports, and jurisdictions in which an enterprise is responsible to file such reports, is received.
  • Regulatory reporting requirements for the relevant jurisdictions are retrieved from a web source, and it is determined whether the regulatory reporting requirements have been satisfied. If not, a reporting form electronic document is retrieved from the web source, where the reporting form electronic document is an incomplete form for a regulatory report to be filed in compliance with the requirements.
  • the reporting form electronic document includes at least partially unstructured data.
  • a structured dataset template is created based on the reporting form electronic document.
  • a report electronic document is generated based on the template and the enterprise data. The report electronic document is sent, for example, to a server of a regulatory body in order to comply with the regulatory reporting requirements.
  • Fig. 1 shows an example network diagram 100 utilized to describe the various disclosed embodiments.
  • a regulatory report generator 120 an enterprise system 130, a database 140, and a plurality of web sources 150-1 through 150-N, where N is an integer equal to or greater than 1 (hereinafter referred to individually as a web source 150 and collectively as web sources 150, merely for simplicity purposes), are communicatively connected via a network 1 10.
  • the network 1 10 may be, but is not limited to, a wireless, cellular or wired network, a local area network (LAN), a wide area network (WAN), a metro area network (MAN), the Internet, the worldwide web (WWW), similar networks, and any combination thereof.
  • LAN local area network
  • WAN wide area network
  • MAN metro area network
  • WWW worldwide web
  • the enterprise system 130 is associated with an enterprise, and may store data related to purchases, income, or other financial data related to the enterprise or representatives of the enterprise as well as data related to the enterprise itself.
  • the enterprise system 130 may further store data related to previously filed regulatory reports.
  • the enterprise may be, but is not limited to, a business with presence in various jurisdictions requiring regulatory reports to be filed at specified time periods.
  • the enterprise system 130 may be, but is not limited to, a server, a database, an enterprise resource planning system, a customer relationship management system, or any other system storing relevant data.
  • the data stored by the enterprise system 130 includes enterprise data such as, but not limited to, financial statements, previously filed regulatory reports, jurisdictions in which an enterprise is responsible to file regulatory reports, confirmation communications (e.g., emails) indicating submission of regulatory reports, and the like.
  • enterprise data such as, but not limited to, financial statements, previously filed regulatory reports, jurisdictions in which an enterprise is responsible to file regulatory reports, confirmation communications (e.g., emails) indicating submission of regulatory reports, and the like.
  • the database 140 may store report electronic documents generated by the regulatory report generator 120. Each report electronic document is a completed reporting form electronic document including information required for regulatory reporting as indicated in the reporting form electronic document.
  • the web sources 150 store at least reporting form electronic documents that may be utilized as forms for satisfying regulatory reporting requirements.
  • the web sources 150 may include, but are not limited to, servers or devices of tax authority servers, accounting servers, regulatory bodies, and the like. As a non-limiting example, the web source 150 may be a government server storing forms to be filled and submitted for compliance with tax reporting requirements.
  • the regulatory report generator 120 is configured to retrieve regulatory reporting requirements from one or more of the web sources 150 based on enterprise data received from the enterprise system 130.
  • the enterprise data includes at least jurisdictions in which an enterprise is required to complete regulatory reports.
  • the regulatory reporting requirements may include rules indicating, for example, an indication of required forms, a time for submitting required forms, both, and the like.
  • the regulatory reporting requirements include an indication of a required type of form
  • the regulatory report generator 120 when the regulatory reporting requirements have not been met, is configured to retrieve a reporting form electronic document, e.g., from one of the web sources 150, for compliance with the regulatory reporting requirements with respect to each jurisdiction for which regulatory reporting requirements have not been met.
  • the regulatory report generator 120 is configured to create datasets based on the reporting form electronic documents including data at least partially lacking a known structure (e.g., unstructured data, semi-structured data, or structured data having an unknown structure). To this end, the regulatory report generator 120 may be further configured to utilize optical character recognition (OCR) or other image processing to determine data in the reporting form electronic document.
  • OCR optical character recognition
  • the regulatory report generator 120 may therefore include or be communicatively connected to a recognition processor (e.g., the recognition processor 235, Fig. 2).
  • the regulatory report generator 120 is configured to analyze the created datasets to identify reporting requirement parameters related to reporting requirements indicated in the reporting form electronic documents. In an embodiment, the regulatory report generator 120 is configured to create templates based on the created datasets. Each template is a structured dataset including the identified reporting requirement parameters.
  • regulatory reporting requirements indicating that a regulatory report must be filed for an enterprise in Germany in May and in the United States in July may be retrieved from a regulatory authority server. If at least one of the required regulatory reports has not been filed, the regulatory report generator is configured to retrieve a reporting form electronic document to be completed for the relevant regulatory authority i.e., Germany, United States, or both.
  • a template is created for each reporting form electronic document, where each template is a structured dataset including reporting requirements indicated in the reporting form electronic document.
  • a report electronic document is completed based on each template. The respective report electronic documents may then be submitted to the relevant regulatory bodies of Germany, the United States, or both.
  • Using structured templates for creating a report electronic document allows for more efficient and accurate form creation than, for example, by utilizing unstructured data.
  • corresponding enterprise data may be utilized only with respect to relevant portions of a reporting form electronic document (e.g., portions included in specific fields of a structured template), thereby improving accuracy of form completion using appropriate enterprise data.
  • data extracted from electronic documents and organized into templates requires less memory than, for example, images of scanned documents.
  • the enterprise system 130 may be queried for enterprise data, and at least a portion of the enterprise data may be utilized to complete portions of the reporting form electronic document associated with the reporting requirements indicated in the created template. For example, enterprise data including an annual income may be utilized to fill in a blank portion of the reporting form electronic document corresponding to a "name" reporting requirement indicated in the template.
  • the enterprise data may further include at least partially unstructured electronic documents such as, but not limited to, scans of previously completed reporting forms.
  • the regulatory report generator 120 may be configured to create templates based on the enterprise data electronic documents as described herein, where the values indicated in key fields of the enterprise data electronic document templates may be utilized to complete corresponding portions of the reporting form electronic document.
  • Fig. 2 is an example schematic diagram of the regulatory report generator 120 according to an embodiment.
  • the regulatory report generator 120 includes a processing circuitry 210 coupled to a memory 215, a storage 220, and a network interface 240.
  • the regulatory report generator 120 may include an optical character recognition (OCR) processor 230.
  • OCR optical character recognition
  • the components of the regulatory report generator 120 may be communicatively connected via a bus 250.
  • the processing circuitry 210 may be realized as one or more hardware logic components and circuits.
  • illustrative types of hardware logic components include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.
  • FPGAs field programmable gate arrays
  • ASICs application-specific integrated circuits
  • ASSPs application-specific standard products
  • SOCs system-on-a-chip systems
  • DSPs digital signal processors
  • the memory 215 may be volatile (e.g., RAM, etc.), non-volatile (e.g., ROM, flash memory, etc.), or a combination thereof.
  • computer readable instructions to implement one or more embodiments disclosed herein may be stored in the storage 220.
  • the memory 215 is configured to store software.
  • Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by the one or more processors, cause the processing circuitry 210 to perform the various processes described herein.
  • the storage 220 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs), or any other medium which can be used to store the desired information.
  • flash memory or other memory technology
  • CD-ROM Compact Discs
  • DVDs Digital Versatile Disks
  • the OCR processor 230 may include, but is not limited to, a feature and/or pattern recognition processor (RP) 235 configured to identify patterns, features, or both, in unstructured data sets. Specifically, in an embodiment, the OCR processor 230 is configured to identify at least characters in the unstructured data. The identified characters may be utilized to create a dataset including data required for verification of a request.
  • RP pattern recognition processor
  • the network interface 240 allows the regulatory report generator 120 to communicate with the enterprise system 130, the database 140, the web sources 150, or a combination of, for the purpose of, for example, collecting data, retrieving data, storing data, and the like.
  • Fig. 3 is an example flowchart 300 illustrating a method for automatically assessing and submitting regulatory required documents according to an embodiment.
  • the method may be performed by a regulatory report generator (e.g., the regulatory report generator 120 of Fig. 1 ).
  • enterprise data is collected.
  • the enterprise data includes at least jurisdictions in which an enterprise is required to report.
  • Enterprise data may further include country of origin of the enterprise revenue data, profit data, employee data, reporting history, reporting targets, and similar data related to regulatory and tax requirements.
  • the enterprise data may further include past fillings of regulatory documents, time periods represented by the regulatory documents, and dates and times that the documents had been submitted.
  • the enterprise data may be collected from an enterprise system, e.g., a database storing the enterprise data.
  • regulatory reporting requirements are retrieved.
  • Regulatory reporting requirements may be retrieved from web sources, such as governmental websites or databases accessible over a network, that are based on the collected enterprise data, such as which jurisdiction or jurisdictions an enterprise is required to report to.
  • the regulatory reporting requirements may include time periods associated with the regulatory reporting, deadlines associated with the regulatory reporting, evidence of submission of completed regulatory forms, and the like.
  • the regulatory reporting requirements may further include information from multiple regulatory bodies, such as various states and countries and regulatory and tax requirements associated therewith.
  • S320 also includes retrieving corresponding reporting form electronic documents for each set of regulatory reporting requirements from the respective web sources.
  • the enterprise data may include an electronic confirmation that is received by the enterprise when a regulatory reporting requirement has been satisfied, e.g., a confirmation email sent to an account associated with the enterprise.
  • the email account may be accessed and searched for such an electronic confirmation. If an electronic confirmation exists within the enterprise data, the regulatory requirements are determined to have been met, and execution terminates; otherwise, execution continues with S340.
  • a dataset is created based on a reporting form electronic document.
  • the reporting form electronic document may be accessed from a web source or database, and includes a reporting form for a regulatory report to be filed in compliance with regulatory reporting requirements.
  • the reporting form electronic document includes at least partially unstructured data.
  • S340 may further include analyzing the reporting form electronic document using optical character recognition (OCR) to determine key fields and values to be completed with relevant data from the enterprise data.
  • OCR optical character recognition
  • the dataset includes data associated with key fields and key values of the of the reporting form electronic document.
  • the reporting form electronic document includes, but is not limited to, unstructured data, semi-structured data, structured data with structure that is unanticipated or unannounced, or a combination thereof.
  • the dataset may include key values indicating reporting requirements to be supplied when submitting a reporting form electronic document. Creating datasets based on electronic documents is described further herein below with respect to Fig. 4.
  • analyzing the dataset may include, but is not limited to, identifying reporting requirement parameters related to reporting requirements indicated in the reporting form electronic documents.
  • the reporting requirement parameters may include key values that are required to be completed for compliance with the regulatory reporting requirements.
  • a template is created based on the dataset.
  • the template may be, but is not limited to, a structured dataset including a plurality of fields associated with key values.
  • the fields may include the identified reporting requirement parameters, and may be predefined.
  • Creating templates from electronic documents allows for faster processing due to the structured nature of the created templates. For example, query and manipulation operations may be performed more efficiently on structured datasets than on datasets lacking such structure. Further, organizing information from electronic documents into structured datasets, the amount of storage required for saving information contained in electronic documents may be significantly reduced. Electronic documents are often images that require more storage space than datasets containing the same information. For example, datasets representing data from 100,000 image electronic documents can be saved as data records in a text file. A size of such a text file would be significantly less than the size of the 100,000 images.
  • a report electronic document is created based on the template.
  • a report electronic document includes a completed form that is acceptable to be submitted to a regulatory body in compliance with the regulatory reporting requirements.
  • the report electronic document is created by accessing a reporting form electronic document from a web source that is relevant to the enterprise. For example, if certain financial data must be submitted within a predefined reporting form electronic document from a regulatory authority, the report electronic document will include a completed version of the reporting form electronic document with all relevant fields filled in based on the created template.
  • the report electronic document is submitted.
  • the submission may include uploading, emailing, or otherwise sending a completed form to a regulatory body in compliance with the regulatory reporting requirements.
  • Fig. 4 is an example flowchart S340 illustrating a method for creating a dataset based on an electronic document according to an embodiment.
  • the electronic document is obtained.
  • Obtaining the electronic document may include, but is not limited to, receiving the electronic document (e.g., receiving a scanned image) or retrieving the electronic document (e.g., retrieving the electronic document from a consumer enterprise system, a merchant enterprise system, or a database).
  • the electronic document may be a reporting form electronic document for compliance with regulatory reporting requirements.
  • the electronic document is analyzed.
  • the analysis may include, but is not limited to, using optical character recognition (OCR) to determine characters in the electronic document.
  • OCR optical character recognition
  • key fields and values in the electronic document are identified.
  • the key fields may include, but are not limited to, an enterprise name and address, date, income information, an enterprise's taxable status, and so on.
  • An electronic document may include unnecessary details that would not be considered to be key values.
  • a logo of the merchant may not be required and, thus, is not a key value.
  • a list of key fields may be predefined, and pieces of data that may match the key fields are extracted. Then, a cleaning process is performed to ensure that the information is accurately presented. For example, if the OCR would result in a data presented as "121 1212005", the cleaning process will convert this data to 12/12/2005. As another example, if a key field is presented as "Addre$s", this will change to "Address.” The cleaning process may be performed using external information resources, such as dictionaries, calendars, and the like.
  • S430 results in a complete set of the predefined key fields and values.
  • a structured dataset is generated.
  • the generated dataset includes the identified key fields and values.
  • any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations are generally used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise, a set of elements comprises one or more elements.
  • the phrase "at least one of” followed by a listing of items means that any of the listed items can be utilized individually, or any combination of two or more of the listed items can be utilized. For example, if a system is described as including "at least one of A, B, and C," the system can include A alone; B alone; C alone; A and B in combination; B and C in combination; A and C in combination; or A, B, and C in combination.
  • the various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof.
  • the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices.
  • the application program may be uploaded to, and executed by, a machine comprising any suitable architecture.
  • the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs"), a memory, and input/output interfaces.
  • CPUs central processing units
  • the computer platform may also include an operating system and microinstruction code.
  • a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Technology Law (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Data Mining & Analysis (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système et un procédé de création de rapports réglementaires sur la base de données d'entreprise, comprenant les étapes suivantes : détermination si des exigences de rapport réglementaire sont satisfaites sur la base de données d'entreprise, les données d'entreprise provenant d'un serveur d'entreprise ; récupération d'un document électronique de formulaire de rapport lorsque les exigences de rapport n'ont pas été satisfaites, le document électronique de formulaire de rapport contenant au moins des données partiellement non structurées ; analyse du document électronique de formulaire de rapport en vue de déterminer au moins un paramètre d'exigence de rapport pertinent pour les exigences de rapport réglementaire ; création d'un modèle basé sur l'analyse du document électronique de formulaire de rapport, le modèle étant un ensemble de données structuré contenant ledit paramètre d'exigence de rapport déterminé ; et création d'un document électronique de rapport sur la base du modèle et des données d'entreprise, le document électronique de rapport étant le document électronique de formulaire de rapport complété en utilisant au moins une partie des données d'entreprise en conformité avec les exigences de rapport réglementaire.
PCT/US2017/064191 2015-11-29 2017-12-01 Système et procédé de création automatique de rapports réglementaires WO2018098507A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/376,854 US20190236126A1 (en) 2015-11-29 2019-04-05 System and method for automatic creation of regulatory reports

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US15/361,934 2016-11-28
US15/361,934 US20170154385A1 (en) 2015-11-29 2016-11-28 System and method for automatic validation
US201662428568P 2016-12-01 2016-12-01
US62/428,568 2016-12-01

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US15/361,934 Continuation-In-Part US20170154385A1 (en) 2015-02-04 2016-11-28 System and method for automatic validation

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/376,854 Continuation US20190236126A1 (en) 2015-11-29 2019-04-05 System and method for automatic creation of regulatory reports

Publications (1)

Publication Number Publication Date
WO2018098507A1 true WO2018098507A1 (fr) 2018-05-31

Family

ID=62195404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/064191 WO2018098507A1 (fr) 2015-11-29 2017-12-01 Système et procédé de création automatique de rapports réglementaires

Country Status (1)

Country Link
WO (1) WO2018098507A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111881093A (zh) * 2020-07-22 2020-11-03 中国工商银行股份有限公司 一种数据报送方法、装置及报送系统
US20210233181A1 (en) * 2018-08-06 2021-07-29 Ernst & Young Gmbh Wirtschaftsprüfungsgesellschaft System and method of determining tax liability of entity
CN114140294A (zh) * 2021-11-26 2022-03-04 碳阻迹（北京）科技有限公司 一种企业碳排放信息实时分析展示的服务方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040034554A1 (en) * 2002-08-16 2004-02-19 Shirley David P. Request for conformity system
US20080126155A1 (en) * 2006-11-27 2008-05-29 Sap Ag Method and apparatus for enterprise operation assessment
US20100211609A1 (en) * 2009-02-16 2010-08-19 Wuzhen Xiong Method and system to process unstructured data
US20110093471A1 (en) * 2007-10-17 2011-04-21 Brian Brockway Legal compliance, electronic discovery and electronic document handling of online and offline copies of data

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040034554A1 (en) * 2002-08-16 2004-02-19 Shirley David P. Request for conformity system
US20080126155A1 (en) * 2006-11-27 2008-05-29 Sap Ag Method and apparatus for enterprise operation assessment
US20110093471A1 (en) * 2007-10-17 2011-04-21 Brian Brockway Legal compliance, electronic discovery and electronic document handling of online and offline copies of data
US20100211609A1 (en) * 2009-02-16 2010-08-19 Wuzhen Xiong Method and system to process unstructured data

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210233181A1 (en) * 2018-08-06 2021-07-29 Ernst & Young Gmbh Wirtschaftsprüfungsgesellschaft System and method of determining tax liability of entity
US11983780B2 (en) * 2018-08-06 2024-05-14 Ey Gmbh & Co. Kg Wirtschaftsp Üfungsgesell Schaft System and method of determining tax liability of entity
CN111881093A (zh) * 2020-07-22 2020-11-03 中国工商银行股份有限公司 一种数据报送方法、装置及报送系统
CN111881093B (zh) * 2020-07-22 2023-12-29 中国工商银行股份有限公司 一种数据报送方法、装置及报送系统
CN114140294A (zh) * 2021-11-26 2022-03-04 碳阻迹（北京）科技有限公司 一种企业碳排放信息实时分析展示的服务方法及系统

Similar Documents

Publication Publication Date Title
US10546351B2 (en) System and method for automatic generation of reports based on electronic documents
US11062132B2 (en) System and method for identification of missing data elements in electronic documents
US20190236126A1 (en) System and method for automatic creation of regulatory reports
US20190236128A1 (en) System and method for generating a notification related to an electronic document
US11138372B2 (en) System and method for reporting based on electronic documents
US20170169292A1 (en) System and method for automatically verifying requests based on electronic documents
US20190236127A1 (en) Generating a modified evidencing electronic document including missing elements
US20170193608A1 (en) System and method for automatically generating reporting data based on electronic documents
WO2018098507A1 (fr) Système et procédé de création automatique de rapports réglementaires
US20180018312A1 (en) System and method for monitoring electronic documents
EP3494495A1 (fr) Système et procédé pour remplir des documents électroniques
US20180025225A1 (en) System and method for generating consolidated data for electronic documents
EP3430540A1 (fr) Système et procédé pour la génération automatique de données de rapport basées sur des documents électroniques
US20180046663A1 (en) System and method for completing electronic documents
US20170161315A1 (en) System and method for maintaining data integrity
US10387561B2 (en) System and method for obtaining reissues of electronic documents lacking required data
US20190228475A1 (en) System and method for optimizing reissuance of electronic documents
US20170169519A1 (en) System and method for automatically verifying transactions based on electronic documents
EP3417383A1 (fr) Vérification automatique de demandes sur la base de documents électroniques
WO2017142615A1 (fr) Système et procédé de gestion d'intégrité de données
EP3494530A1 (fr) Obtention de réédition de documents électroniques manquant de données requises
US20170193609A1 (en) System and method for automatically monitoring requests indicated in electronic documents
EP3430584A1 (fr) Système et procédé de vérification automatique de transactions sur la base de documents électroniques
EP3526758A1 (fr) Recherche de documents électroniques d'attestation sur la base de données non structurées
EP3494531A1 (fr) Système et procédé de génération de données consolidées pour documents électroniques

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17873432

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17873432

Country of ref document: EP

Kind code of ref document: A1