WO2010111328A1 - Procédés, systèmes et logiciel de traitement de documents financiers - Google Patents

Procédés, systèmes et logiciel de traitement de documents financiers Download PDF

Info

Publication number
WO2010111328A1
WO2010111328A1 PCT/US2010/028405 US2010028405W WO2010111328A1 WO 2010111328 A1 WO2010111328 A1 WO 2010111328A1 US 2010028405 W US2010028405 W US 2010028405W WO 2010111328 A1 WO2010111328 A1 WO 2010111328A1
Authority
WO
WIPO (PCT)
Prior art keywords
mapping
list
lists
tag name
statements
Prior art date
Application number
PCT/US2010/028405
Other languages
English (en)
Inventor
Robert W. Blake
Original Assignee
Bowne & Co., Inc.
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
Application filed by Bowne & Co., Inc. filed Critical Bowne & Co., Inc.
Publication of WO2010111328A1 publication Critical patent/WO2010111328A1/fr

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
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • Reporting Language is an XML-based specification for representing business reporting information.
  • XBRL provides the business community with a standards-based method to prepare, publish in a variety of formats, reliably extract and automatically exchange financial report information. It provides a common way for disparate systems to exchange specific information and provides a means to separate data from formatting.
  • XBRL is a royalty-free technology developed and maintained by XBRL International, a not-for-profit consortium comprised of over 800 accounting, technology, financial services and regulatory-type organizations across the world.
  • XBRL international was formed in 2001 after the initial efforts to bring the concept of XBRL to market by the American Institute of Certified Public Accountants (AICPA).
  • AICPA American Institute of Certified Public Accountants
  • Local jurisdictions such as XBRL US, XBRL UK and XBRL Canada form the basis of XBRL International membership and help drive XBRL education and adoption within a specific country.
  • XBRL is machine-readable, and computers can use the tags to pull out comparable data from different companies from their filings. It saves a person from having to read through financial reports to find specific data, since companies typically have different styles of presenting their financial data in reports.
  • XBRL is used to digitally publish both internally and externally business reports such as financial statements.
  • An XBRL-based business report is a digitally enhanced version of a paper-based report such as the Balance Sheet, Income Statement. Statement of Cash Flows and Notes and Schedules to the Financial Statements.
  • XBRL reports can be prepared efficiently, exchanged reliably, published more easily, analyzed more quickly, and retrieved more simply.
  • XBRL can be used to address the following types of business reporting: (a) regulatory filings (filings required by government and regulatory agencies); (b) taxes and tax returns (submissions that collect personal and corporate tax return information); (c) internal reporting (management and accounting reports detailing internal performance that are typically created by an accounting/enterprise resource planning (ERP)/enterprise resource management (ERM) system; (d) metric/key performance indicator (KPI) reporting (represent ratios and other key metrics/indicators to enable companies within and across industries to easily benchmark performance); and (e) authoritative literature (provides a standard way to describe accounting-related authoritative literature published by the AICPA, FASB, ASB, IAS and others).
  • ERP accounting/enterprise resource planning
  • ERP enterprise resource management
  • KPI metric/key performance indicator
  • authoritative literature provides a standard way to describe accounting-related authoritative literature published by the AICPA, FASB, ASB, IAS and others).
  • An embodiment of the present invention comprises XBRLMark software that processes targeted financial documents into XBRL submissions for the SEC.
  • ACE is an acronym for Advanced Composition Engine.
  • ACE is a component of the Bowne Integrated Typesetting System (BITS) and is the part of BITS that manages positioning of characters in space.
  • EDGAR2 is a term referring to content that is compliant with the SECs HTML specification for documents filed on their Electronic Document Gathering And Retrieval (EDGAR) system.
  • EDG AR2 is HTML which the SEC has approved for EDGAR filings.
  • HTML filings EDGAR only accepts documents that have been formatted using a subset of the HTML 3.2 semantics (tags) and some HTML 4.0 attributes, as recommended and standardized by the W3C. Due to the SECs limited support of HTML, EDGAR enforces many restrictions relative to all HTML documents that are included in an EDGAR submission. Details are outlined in the EDGAR Filer Manual section 5.2.2.
  • the software takes ACE Typeset Format files and EDGAR2 HTML files as input and produces XBRL submissions including Tagged Instance, Schema XSD, Label Linkbase, and Presentation Linkbase files.
  • Microsoft Word files also can be used as input.
  • such files are simultaneously processed both as EDGAR2 HTML and XBRL submission documents.
  • the present invention comprises a computer-implemented method comprising: (a) electronically receiving a document comprising securities compliance data; and (b) electronically tagging with a computer processor terms in said document with XBRL tags; wherein said tagging comprises applying mapping lists, and wherein said mapping lists comprise a job list, a client list, a base list, and a taxonomy list.
  • mapping lists are applied in a hierarchical order;
  • said hierarchical order is (1) job list; (2) client list; (3) base list; and (4) taxonomy list;
  • the method further comprises building a tag name automatically if no match is found in said mapping lists;
  • said mapping lists comprise mapping statements;
  • said mapping statements each comprise a tag name and a matching pattern;
  • said mapping statements are grouped according to financial statement;
  • applying said mapping lists comprises identifying a financial statement and searching mapping statements grouped assigned to said identified financial statement;
  • the method further comprises building an element tag based on an associated tag name;
  • building said tag name automatically comprises application of mapping tokens: and
  • building said tag name automatically comprises application of wildcard variables.
  • the invention comprises a computer system comprising: (a) a processor that electronically receives data describing a document comprising securities compliance data; and (b) a processor that electronically tags terms in said document with XBRL tags; wherein said tagging comprises applying mapping lists, wherein said mapping lists comprise a job list, a client list, a base list, and a taxonomy list, and wherein said processor that receives data and said processor that tags may be the same or different proces sors .
  • mapping lists are applied in a hierarchical order;
  • said hierarchical order is (1) job list; (2) client list; (3) base list; and (4) taxonomy list;
  • the system further comprises a processor that builds a tag name automatically if no match is found in said mapping lists;
  • said mapping lists comprise mapping statements;
  • said mapping statements each comprise a tag name and a matching pattern;
  • said mapping statements are grouped according to financial statement;
  • applying said mapping lists comprises identifying a financial statement and searching mapping statements grouped assigned to said identified financial statement;
  • the system further comprises a processor that builds an element tag based on an associated tag name;
  • building said tag name automatically comprises application of mapping tokens; and
  • building said tag name automatically comprises application of wildcard variables.
  • the invention comprises an apparatus comprising: (a) software, stored in a computer readable medium, that electronically receives a document comprising securities compliance data; and (b) software, stored in a computer readable medium, that electronically tags terms in said document with XBRL tags; wherein said tagging comprises applying mapping lists, and wherein said mapping lists comprise a job list, a client list, a base list, and a taxonomy list.
  • mapping lists are applied in a hierarchical order;
  • said hierarchical order is (1) job list; (2) client list; (3) base list; and (4) taxonomy list;
  • the apparatus further comprises software, stored in a computer readable medium, that builds a tag name automatically if no match is found in said mapping lists;
  • said mapping lists comprise mapping statements;
  • said mapping statements each comprise a tag name and a matching pattern:
  • said mapping statements are grouped according to financial statement;
  • applying said mapping lists comprises identifying a financial statement and searching mapping statements grouped assigned to said identified financial statement;
  • the apparatus further comprises software, stored in a computer readable medium, that builds an element tag based on an associated tag name;
  • building said tag name automatically comprises application of mapping tokens; and
  • building said tag name automatically comprises application of wildcard variables.
  • FIGS. 1 and 2 depict exemplary interfaces for selecting a template.
  • FIGS. 3-6 depict exemplary interfaces for selecting an input file.
  • FIG. 7 depicts an exemplary interface for selecting processing options.
  • FIG. 8 depicts an exemplary display regarding processing status
  • FIG. 9 depicts an exemplary pre-process completion display.
  • FIG. 10 depicts an exemplary XMK file.
  • FIGS. 11-13 depict exemplary interfaces for saving and processing an intermediate XMK file.
  • FIG. 14 depicts an exemplary post-process completion display.
  • FIG. 15 depicts an exemplary interface for selecting an output display.
  • FIG. 16 depicts an exemplary browser output display.
  • FIG. 17 illustrates an exemplary tagging hierarchy.
  • FIG. 18 depicts an exemplary error message display.
  • FIG. 19 depicts an exemplary computer system that may be used with an embodiment of the invention. Detailed Description of Exemplary Embodiments
  • An exemplary embodiment of the present invention comprises software (referred to herein for convenience as "XBRLMark”) that may be a Microsoft Windows application and preferably comprises a "GUI” (Graphical User Interface) that runs a plurality of smaller program modules, which preferably run as batch processes in the background.
  • XBRLMark software
  • GUI Graphic User Interface
  • XBRLMark is a template-driven application, in that there are several supplied templates that can be cloned and customized by a user, either to address different document types or special customer needs.
  • Each template has an associated settings file called a Boilerplate file, in which a plurality of settings can be changed, to alter the behavior or the final output result. This may be carried out by a trained template person. This customization or set-up provides automation capability for a client's work, which may be processed on a repeat basis.
  • XBRLMark is supplied with three or more base (or master) templates: for example, one template for accepting client- supplied Word files as input; one for accepting ACE Typeset files as input; and one for accepting EDGAR2 as input.
  • XBRLMark may provide additional templates to address specific form types (e.g., 10- K, 10-Q, 20-F, etc.).
  • a user first selects an appropriate template from a "Templates” menu (see FIG. 1) - depending on the type of file to be processed.
  • a “Templates” menu see FIG. 1 - depending on the type of file to be processed.
  • the user selects the "Input” menu, and selects "Prepare and Open” (see FIG. 3).
  • the user is then presented with a dialog, where she can either type in an input filename to be processed, or select from a list of files, by hitting a button 410 to the right of the Filename field (see FIG. 4).
  • the user is presented with a dialog showing all the available input files (see FIG. 5). The user then chooses the desired file.
  • a dialog is opened (see FIG. 6).
  • the user selects a "Prepare” button 610, the first of the batch programs is launched, which searches the input file for a client name. If a client name is found, the fields of an XBRL Processing Options dialog are automatically populated, and the dialog is presented to the user (see FIG. 7).
  • the user then has the opportunity to either accept all of the automatically selected options, or to make changes as appropriate.
  • the user selects a "Continue" button 710. and a further series of batch modules is launched in the background.
  • all that the user sees at this point is a progress control showing which particular batch module is running, and how far through the process the user has progressed (see FIG. 8).
  • the post-process software of an exemplary embodiment runs through each line item of each Financial Statement, it extracts the "stub" language as a text string, and prepares it for parsing against one or more databases or lists.
  • Each of the databases or lists preferably contains a hierarchical list of "mapping statements", each of which preferably comprises two components: a search pattern (against which each stub of each line item of each financial statement is parsed), and a corresponding Tag name. If the text string extracted from the "stub" language matches the search pattern of one of the mapping statements, that is considered a "match," and that corresponding Tag name is used to form the basis of the Element tags that are applied to each data point or figure in the adjacent figure columns of that line item in the Financial Statement (see FIG. 17). Once a match is found, several other pieces of contextual information found in or around the Financial Statement may be used to complete the "attributes" of each
  • the first group is the "pre-process,” which prepares the data for use in the intermediate XMK file format that can be reviewed by the operator.
  • the second group is for the "post-process,” for the stages when the user has reviewed the XMK file and wants to process the data through to the final XBRL tagged "Instance" file.
  • the batch programs can all access the Boilerplate file and if necessary use designated "settings" to change the way the program processes the data. This is part of the "pre-engineering" process.
  • the list of batch programs used changes sometimes dependent on the Template that was selected, because certain templates require different processors in order to process a different input file format.
  • the pre-process may use the following batch programs:
  • acein.exe a. This program checks the selected input file to ensure and verify that it is an ACE typeset file; b. copies its corresponding E2 HTML version into a standard filename "e2copy.tmp"; and c. hands off the output to the next program in the chain.
  • prexb.exe a This program checks the input from the previous program, and searches for a valid client name; and b. supplies that information to the next program in the chain.
  • xib_xbrlmark.exe a This program takes the company information supplied by the previous program, looks up the required default data stored for the named client, and presents that data as default selected options in the XBRL Processing Options dialog.
  • startxb.exe a This program takes the options selected by the user in the previous dialog program and generates some tagging which contains the necessary information for subsequent processing and which will eventually be displayed in the XMK file at the end of the "pre-process" run.
  • prsnr.exe This program is run on the file supplied as modified input by the previous programs in the chain. b. This program looks up some user-defined search/replace patterns ("SNR") previously specified and stored by the template specialist in a "boilerplate” file and replaces, removes, or inserts data, according to the user-defined search/replace patterns. c. This is part of template “pre-engineering” or "pre- flighting.” d. This results in a further modified version of the input file, to be handed to the next processor in the chain. e.
  • SNR user-defined search/replace patterns
  • the primary function of this program is to allow the user to insert what "marks” or "Area Markers,” which provide the automated means of recognizing which chunks of data (e.g., Financial Statements, etc.) are to be processed through to XBRL tagging. This is "pre- engineering” of the automation process. 6. stag.exe
  • This program provides the user with the ability to further "pre-engineer” or “pre-flight” the automation process, and to clean up some of the data contained within the "Area Markers” previous inserted by prsnr.exe.
  • This program checks the previously saved E2 HTML version of the ACE input file, detects where "Notes to Financials" data is located, and individually “marks” or “area marks” each Note Title and Note Body.
  • This program also merges the modified ACE typeset data with the E2 HTML version of the data to produce a whole file which contains both the ACE version with "marked” Financial Statements and the HTML version with "marked” Notes to Financials.
  • ACE Input Template - "post-process" 1. pxtag.exe a. This program further simplifies and standardizes the data found in the XMK file, to prepare it for the next program in the chain; 2. xtag.exe
  • This program is the "main event" of an embodiment, since it performs the XBRL tagging of data.
  • This program a. reads the input data stream and identifies and stores information for use during processing of the required Financial
  • These Mapping Lists contain look up tables of "stub text" search strings, with associated "Tag Names” for building the eventual XBRL Element Tags.
  • the Lists are in order of precedence and may have been "pre-engineered” or "pre-flighted” by a template specialist, perhaps in consultation with the client, g.
  • the Lists are: i. the Job List (current job being processed); ii. the Client List (pre -determined standard Mapping Statements, to be used to process all that client's work;
  • a stub label is the contextual/text-based portion of a row on a financial statement; for example, a common row on a financial statement looks like this:
  • the "stub label” in this example would be “Cash and cash equivalents” while the “data points” would be 34 and 68, respectively.
  • the “stub label” provides insight into the "accounting” that goes into this row and therefore is important to finding the correct association in the taxonomy.]
  • the Base List - a context sensitive and intelligent set of Mapping Statements to be used for the "Form Type” being processed by the individual template (e.g., a 10-K or 10-Q). These "intelligent” mapping statements are built on rules supplied with whichever given "taxonomy” is being adhered to at the time.
  • the Taxonomy List is a standard set of Stub label text strings, and associated Tag Names.
  • mappings There is no contextual intelligence built into these mappings; they are simply copied from the taxonomy being adhered to, rather like a set of "fall back” defaults for the case in which the previous three more intelligent lists fail to produce a match, h. If none of the four lists produce a "match” to the stub label text being parsed - then internal "AI" logic kicks in, which uses all the information supplied in the data, to "build” a tag name automatically; i. This automatically built tag name may later be modified by a template specialist if required, since a matching "Mapping Statement" is also automatically generated and appended to the "Job List.” j. xtag.exe also examines the "Notes" data and renders the
  • An E2-only template of an embodiment contains batch programs similar to those of the ACE template, except that in the Pre-process stage, some batch programs convert the financial tables from HTML to "basic ACE" format and convert other HTML code to the ACE equivalent. Otherwise the processing is similar to ACE processing, as will be understood by those skilled in the art.
  • a Word template of an embodiment contains different programs in the Pre- process phase- the software pre-converts Microsoff's RTF format into an XMK file. This template also contains additional programs in the Post-process, which convert the XMK data into E2 HTML, and into XBRL tagging simultaneously. XBRLMark Mapping
  • XBRLMark When XBRLMark processes data, it identifies or "marks" the relevant Financial Statements and other sections of the job to be processed (e.g., Notes), and then extracts and tags the pertinent data.
  • the software extracts each table or financial statement and each data row in each table, or other designated section of the job, it looks through the four pre-existing mapping lists:
  • the 1 st is the active "Job List”; the 2 nd is the client- specific "Client List”; the 3 rd is the template- specific "Base List”; and the 4 is the "Taxonomy List.
  • an expert user perhaps in cooperation with a client, will have “pre-engineered” the mappings based on feedback from the client and their previous filings.
  • XBRLMark searches each of the four lists (which typically contain pre- engineered mappings for a particular client) and if it finds a match uses that match to process the data points in that data row. Mapping statements:
  • Element tag names are associated with data points extracted from Financial Statements via "mapping” a "Stub Label” to the associated Element "tag name.”
  • mapping statement has two parts - the "tag name” to be applied, followed by the "matching pattern” that looks for a "Stub Label” or data row to be matched.
  • the two parts of the mapping statement preferably are separated by "pipe” characters.
  • An example is:
  • each Financial Statement has its own group of mapping statements. For example, there may be different mapping statements for the Balance Sheets, versus the Statement of Cash Flows:
  • mapping statements When a data row is processed, depending on which Financial Statement it came from, the software searches for the mapping statements that were designated for that Financial Statement. Each time an XBRLMark process of an embodiment runs, and each time a data row is processed, those four lists are examined, in that order of precedence, to find a matching "mapping statement.” The software of an embodiment searches through each of the relevant mapping statements in the "Job List,” and if it does not find a match there, it will look through the relevant statements in the "Client List", then the "Base List”, then the "Taxonomy List.” If it finds a match in any of those lists, it builds the Element tags, based on the associated Tag name.
  • XBRLMark will build a tag name, based on the Stub Label and its context, and it will build an appropriate and associated mapping pattern and append that to the "Job List" for re -use on subsequent processes - see further description below.
  • mapping it is straightforward to create a mapping. For example, if the Stub label was "One of a kind", and that was the only instance likely to be found in the document, then the user could create a simple mapping:
  • the Heading token is only used in the string part of the pattern (2nd part), such as:
  • Cost of revenue (118, 442; (115, 890)
  • DesiredTagName I ⁇ all "A previous heading : " "Next heading : " * "Deferred income " * ⁇ Deferred income
  • the Total token is only used in the string part of the pattern (2nd part), and is usually used to describe a "stub-less" data row with figures preceded by leading currency symbols:
  • Wildcards are permitted in one or the other part of the tagname/string pattern list in the four list files. These wildcards will help associate stub data that varies with XML tagnames.
  • the Addition and Sum wildcards are used in the tagname part of the pattern to create multiple tags in the output file.
  • the "AccountsReceivableTradeNet" to the left of the ⁇ +> sign means: use that name for the data points found in the figure columns;
  • the Date wildcard will find either a single or double digit figure, optionally followed by "th”, “st”, “rd”, or “nd”, optionally followed by a comma.
  • Month wildcard finds one single month either: all caps, initial caps or lower letters in English, French, Spanish and German and generally accepted abbreviations in English, French and Spanish:
  • XBRLMark processes data, it identifies the relevant Financial Statements and other sections of the job to be processed, and then extracts and tags the pertinent data.
  • mapping lists the active "Job List " '; the client- specific "Client List”; the template- specific "Base List”; and lastly the "Taxonomy List”.
  • an expert user will have "pre-engineered” the mappings, based on feedback from a client, and previous filings.
  • XBRLMark looks through each of the four lists (which typically contain pre-engineered mappings for a particular client), and if it finds a match uses that match to process the data points in that data row. But if the software does not find a match, it will use its own internal logic
  • the internal logic to build a tag name uses the Stub label, if one exists (e.g., if it is not a stub-less total row).
  • AnotherNewStubLabel I Another new stub label
  • TotalLiabilities or “TotalAssets”).
  • the associated mapping will be built to include those items with “tokens”, including both the ⁇ head" -- ⁇ and ⁇ total ⁇ tokens - e.g., I TotalLiabilities
  • ⁇ head ...Liabilities
  • ⁇ head "Headmg” ⁇ Diluted
  • the Tag name will be consist of the main stub label - plus the heading data - e.g., "StubLabelTheHeading"; and b.
  • the Tag name will be consist of the main stub label - plus
  • mapping will be built to include the
  • Embodiments of the present invention comprise computer components and computer-implemented steps that will be apparent to those skilled in the art. For example, calculations and communications can be performed electronically.
  • An exemplary system is depicted in FIG. 19. As shown, computers 1900 communicate via network 1910 with a central server 1930. A plurality of sources of data 1960, 1970 relating to, for example, compliance data, also communicate via network 1910 with a central server 1930, processor 1950, and/or other component to calculate and transmit, for example, XBRL information.
  • the server 1930 may be coupled to one or more storage devices 1940, one or more processors 1950, and software 1960. Other components and combinations of components may also be used to support processing data or other calculations described herein as will be evident to those skilled in the art. Server 1930 may facilitate communication of data from a storage device 1940 to and from processor 1950, and communications to computers 1900.
  • Processor 1950 may optionally include local or networked storage (not shown) which may be used to store information.
  • Software 1960 can be installed locally at a computer 1900, processor 1950 and/or centrally supported for facilitating calculations and applications.
  • step or element of the present invention is explicitly described herein as part of a computer system and/or software, but those skilled in the art will recognize that each step or element may have (and typically will have) a corresponding computer system or software component.
  • Such computer system and/or software components are therefore enabled by describing their corresponding steps or elements (that is, their functionality), and are within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • Educational Administration (AREA)
  • Technology Law (AREA)
  • Game Theory and Decision Science (AREA)
  • Accounting & Taxation (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Selon un aspect, l'invention concerne un procédé mis en œuvre par ordinateur consistant à recevoir par voie électronique un document comprenant des données de conformité de titres de placement et à baliser par voie électronique les termes dans ledit document au moyen de balises XBRL, ledit balisage consistant à appliquer des listes de correspondances, et lesdites listes de correspondances comprenant une liste de travaux, une liste de clients, une liste de base et une liste de taxonomie. Dans un autre aspect, l'invention comprend un système informatique comprenant un processeur qui reçoit par voie électronique des données décrivant un document comprenant des données de conformité de titres de placement, et un processeur qui balise par voie électronique les termes dans ledit document au moyen de balises XBRL, ledit balisage consistant à appliquer des listes de correspondances, lesdites listes de correspondances comprenant une liste de travaux, une liste de clients, une liste de base et une liste de taxonomie, et ledit processeur qui reçoit les données et ledit processus qui balise pouvant être des processus identiques ou différents. Dans un autre aspect, l'invention comprend un logiciel correspondant enregistré sur un support lisible par ordinateur.
PCT/US2010/028405 2009-03-24 2010-03-24 Procédés, systèmes et logiciel de traitement de documents financiers WO2010111328A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US41001709A 2009-03-24 2009-03-24
US12/410,017 2009-03-24

Publications (1)

Publication Number Publication Date
WO2010111328A1 true WO2010111328A1 (fr) 2010-09-30

Family

ID=42781453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/028405 WO2010111328A1 (fr) 2009-03-24 2010-03-24 Procédés, systèmes et logiciel de traitement de documents financiers

Country Status (1)

Country Link
WO (1) WO2010111328A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10095672B2 (en) * 2012-06-18 2018-10-09 Novaworks, LLC Method and apparatus for synchronizing financial reporting data
US11367139B2 (en) * 2019-01-15 2022-06-21 Tangram Solutions LLC Performance measurement and reporting for guaranteed income financial products and services

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050144166A1 (en) * 2003-11-26 2005-06-30 Frederic Chapus Method for assisting in automated conversion of data and associated metadata
US20090006472A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Automatic Designation of XBRL Taxonomy Tags
US20090019358A1 (en) * 2005-02-11 2009-01-15 Rivet Software, Inc. A Delaware Corporation Extensible business reporting language (xbrl) enabler for business documents

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050144166A1 (en) * 2003-11-26 2005-06-30 Frederic Chapus Method for assisting in automated conversion of data and associated metadata
US20090019358A1 (en) * 2005-02-11 2009-01-15 Rivet Software, Inc. A Delaware Corporation Extensible business reporting language (xbrl) enabler for business documents
US20090006472A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Automatic Designation of XBRL Taxonomy Tags

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10095672B2 (en) * 2012-06-18 2018-10-09 Novaworks, LLC Method and apparatus for synchronizing financial reporting data
US10706221B2 (en) 2012-06-18 2020-07-07 Novaworks, LLC Method and system operable to facilitate the reporting of information to a report reviewing entity
US11210456B2 (en) 2012-06-18 2021-12-28 Novaworks, LLC Method relating to preparation of a report
US11367139B2 (en) * 2019-01-15 2022-06-21 Tangram Solutions LLC Performance measurement and reporting for guaranteed income financial products and services

Similar Documents

Publication Publication Date Title
US7590647B2 (en) Method for extracting, interpreting and standardizing tabular data from unstructured documents
US20200250763A1 (en) Processing securities-related information
US11210456B2 (en) Method relating to preparation of a report
US8468442B2 (en) System and method for rendering data
US7020320B2 (en) Extracting text written on a check
US9195639B2 (en) Computer-based system and method for generating, classifying, searching, and analyzing standardized text templates and deviations from standardized text templates
US8176003B2 (en) Automatic designation of XBRL taxonomy tags
Coderre Internal audit efficiency through automation
US7376552B2 (en) Text generator with an automated decision tree for creating text based on changing input data
US10535042B2 (en) Methods of offering guidance on common language usage utilizing a hashing function consisting of a hash triplet
US20160350823A1 (en) System and methods for automatically generating regulatory compliance manual using modularized and taxonomy-based classification of regulatory obligations
US20090132431A1 (en) System for mapping financial disclosure data into compliance information
US20070300295A1 (en) Systems and methods to extract data automatically from a composite electronic document
US20060184539A1 (en) XBRL Enabler for Business Documents
US20050182736A1 (en) Method and apparatus for determining contract attributes based on language patterns
EP1875388B1 (fr) Asppareil de mise a jour de dictionnaire de classification, produit-programme informatique associe et procede de mise a jour de dictionnaire de classification
EP2092447A1 (fr) Procédé et appareil d'analyse de courriels
US20110202545A1 (en) Information extraction device and information extraction system
US7856388B1 (en) Financial reporting and auditing agent with net knowledge for extensible business reporting language
Wu et al. XBRL: A new tool for electronic financial reporting
Maynard et al. Natural language technology for information integration in business intelligence
WO2010111328A1 (fr) Procédés, systèmes et logiciel de traitement de documents financiers
US9195661B2 (en) Method and system for click-thru capability in electronic media
JP6155409B1 (ja) 決算分析システムおよび決算分析プログラム
Castellanos et al. FACTS: an approach to unearth legacy contracts

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: 10756748

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: 10756748

Country of ref document: EP

Kind code of ref document: A1