WO2011005247A1 - Systèmes et procédés d’établissement de situation et de rapport de trésorerie - Google Patents

Systèmes et procédés d’établissement de situation et de rapport de trésorerie Download PDF

Info

Publication number
WO2011005247A1
WO2011005247A1 PCT/US2009/049671 US2009049671W WO2011005247A1 WO 2011005247 A1 WO2011005247 A1 WO 2011005247A1 US 2009049671 W US2009049671 W US 2009049671W WO 2011005247 A1 WO2011005247 A1 WO 2011005247A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
account information
bank account
computer
cash
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.)
Ceased
Application number
PCT/US2009/049671
Other languages
English (en)
Inventor
John E. Scully
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of America Corp
Original Assignee
Bank of America Corp
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 Bank of America Corp filed Critical Bank of America Corp
Priority to KR1020117004871A priority Critical patent/KR20120047839A/ko
Priority to CN2009801333409A priority patent/CN102138154A/zh
Priority to EP09847168A priority patent/EP2297691A1/fr
Priority to PCT/US2009/049671 priority patent/WO2011005247A1/fr
Priority to MX2011002146A priority patent/MX2011002146A/es
Publication of WO2011005247A1 publication Critical patent/WO2011005247A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/10—Office automation; Time management

Definitions

  • Cash positioning typically refers to tracking daily cash positions for an entity. Such tracking may include determining the amount of cash on hand as well as the cash required for the continued functioning of an entity.
  • Cash forecasting may refer to determining the amount of cash on hand at a future date as well as the cash required for the continued functioning of an entity at a future date.
  • ERP enterprise resource planning
  • GL general ledger
  • a method according to the invention may include receiving a user selection to update a data store — i.e., receiving an indication from a user that he or she desires to update a store of data.
  • the data store may include cash positioning and cash reporting information.
  • the method may further include calling a controller module.
  • the method may include using the controller module to call a web service module.
  • the method may include retrieving bank account information data.
  • the bank account information data may be retrieved from various banking web sites.
  • the method may also include populating a spreadsheet application with the retrieved bank account information.
  • the spreadsheet application may be local to a client.
  • FIG. 1 illustrates a schematic diagram of a general-purpose digital computing environment in which one or more aspects of the present invention may be implemented
  • FIG. 2 illustrates a schematic diagram of another digital computing environment in which one or more aspects of the present invention may be implemented
  • FIG. 3 shows a logical view that presents the core design of the system
  • FIG. 4 shows a get data scenario according to the invention
  • FIG. 5 shows an update display scenario according to the invention
  • FIG. 6 shows a data view of the invention
  • FIG. 7 shows a process view according to the invention
  • FIG. 8 shows a portion of a spreadsheet according to the invention
  • FIG. 9 shows a screen shot that illustrates the creating of detailed transaction spreadsheets according to the invention.
  • FIG. 10 shows a screen shot that illustrates that a user can create granular reports according to the invention
  • FIG. 11 shows a portion of a spread sheet that shows that currency rates can be automatically populated according to the invention
  • FIG. 12 shows a dialogue box that allows a user to set default display currency for reports according to the invention
  • FIG. 13 shows a portion of a spread sheet that
  • FIG. 14 shows a dialogue box that allows a user to specify accounts for which the user desires to obtain a report
  • FIG. 15 shows a dialogue box that allows a user to restrict access to selected accounts and set different passwords to access data and download data according to the invention.
  • aspects described herein may be embodied as a method, a data processing system, or a computer program product. Accordingly, those aspects may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, such aspects may take the form of a computer program product stored by one or more computer-readable storage media having computer-readable program code, or instructions, embodied in or on the storage media. Any suitable computer readable storage media may be utilized, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and/or any combination thereof.
  • a cash positioning and reporting tool may be implemented using a Microsoft Excel spreadsheet application and Extensible Markup Language ( 11 XML) technology.
  • a cash positioning and reporting tool may gather data from bank websites or other data sources and populate that information into Microsoft Excel spreadsheets or other suitable spreadsheet applications.
  • Such a system, according to the invention can save time and improve accuracy over any manual method of data entry.
  • a system according to the invention may require minimal training compared to more complex systems. Its implementation time has averaged less than a month compared with 9-12 months for a standard dedicated workstation.
  • Some of the problems addressed by a system according to the invention may include:
  • a system according to the invention preferably gives the client sufficient flexibility to create custom- built spreadsheets to fit their respective reporting needs.
  • Systems according to the invention may store historical account data that can be imported and populated in the spreadsheets for a predetermined period of time and, once imported, the data is available until the client elects to delete it.
  • a system according to the invention may store data locally in both summary and detail form for future analysis thus reducing redundant download fees.
  • a special reconciliation feature according to the invention allows clients to compare forecasts from the day before with what actually posted that night.
  • Systems and methods according to the invention may include the following aspects.
  • One aspect of the invention preferably uses strong type-checking — i.e., a feature dedicated to catching erroneous modifications at compile time — and compile-time binding — i.e., a feature that chooses (binds) a method or methods to be executed in response to a request, based on the operation and objects in the request. If the information is known at compile time, the compiler verifies it is correct.
  • strong type-checking i.e., a feature dedicated to catching erroneous modifications at compile time
  • compile-time binding i.e., a feature that chooses (binds) a method or methods to be executed in response to a request, based on the operation and objects in the request. If the information is known at compile time, the compiler verifies it is correct.
  • a component view according to the invention may be formed from three layers - a user interface ("UI") layer, a business layer, and a data layer.
  • the UI Layer may bind attributes of business value objects to UI objects, present them to the user, accept inputs and process user "submit" requests by unbinding UI objects from business objects attributes.
  • the business layer checks business rules and passes business objects to the data layer.
  • the data layer preferably maps business attributes to persistent storage and encapsulates the data layer processing in a single, atomic transaction.
  • Advantages of the invention may include maximizing leverage of proven standards and technology, and the application of principles such as a single point of maintenance, configurability, extensibility and scalability.
  • the architecture of a software system may require the following views: a deployment view, a logical view, a data view and process view as shown in FIGs. 2, 3, 6, and 7.
  • a deployment view a logical view
  • a data view and process view as shown in FIGs. 2, 3, 6, and 7.
  • FIGs. 2, 3, 6, and 7. The portion of the specification corresponding to the FIGs. describes the views in more detail.
  • Each view preferably focuses on different aspects of the system.
  • One purpose of the view structure set forth herein is to communicate the major components of the system, how each is structured, the process flows between the components, and the major interfaces between the components. From a high level, a goal of the views, as set forth herein, is to examine the system from several different perspectives, each providing a different ⁇ view" in order to capture system features .
  • Deployment View This view documents the physical topology of the system modeled in the Deployment Model.
  • the deployment view as described below shows that each computer in the implementation may be coupled to a system according to the invention via the Internet.
  • Data View - Classes of data in the logical view are classified as transient or persistent.
  • the persistent classes are mapped to structures on disk, usually into a combination of rows in a relational database.
  • An entity- relationship data model can be used to describe the database schema. This view also communicates how the classes are mapped to the relational tables.
  • Process (Concurrency) View This view focuses on the concurrency aspects of the system and how the different aspects contend for shared resources.
  • the process view documents the independent threads of execution within the system and describes how they communicate. It also preferably lists the resources in contention by these threads.
  • the process view may also set forth a transaction model for maintaining integrity among these resources.
  • FIG. 1 illustrates a block diagram of a generic computing device 101 (alternatively referred to herein as a "server") that may be used according to an illustrative embodiment of the invention.
  • the computer server 101 may have a processor 103 for controlling overall operation of the server and its associated components, including RAM 105, ROM 107, input/output module 109, and memory 115.
  • I/O module 109 may include a microphone, keypad, touch screen, and/or stylus through which a user of device 101 may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual and/or graphical output.
  • Software may be stored within memory 115 and/or storage to provide instructions to processor 103 for enabling server 101 to perform various functions.
  • memory 115 may store software used by server 101, such as an operating system 117, application programs 119, and an associated database 121.
  • server 101 computer executable instructions may be embodied in hardware or firmware (not shown) .
  • database 121 may provide centralized storage of account information and account holder information for the entire business, allowing interoperability between different elements of the business residing at different physical locations.
  • Server 101 may operate in a networked environment supporting connections to one or more remote computers, such as terminals 141 and 151.
  • Terminals 141 and 151 may be personal computers or servers that include many or all of the elements described above relative to server 101.
  • the network connections depicted in FIG. 1 include a local area network (LAN) 125 and a wide area network (WAN) 129, but may also include other networks.
  • LAN local area network
  • WAN wide area network
  • server 101 may include a modem 127 or other means for establishing communications over WAN 129, such as Internet 131.
  • network connections shown are illustrative and other means of establishing a communications link between the computers may be used.
  • the existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed, and the system can be operated in a client-server configuration to permit a user to retrieve web pages from a web-based server.
  • Any of various conventional web browsers can be used to display and manipulate data on web pages.
  • application program 119 used by server 101 may include computer executable instructions for invoking user functionality related to communication, such as email, short message service (SMS) , and voice input and speech recognition applications.
  • SMS short message service
  • Computing device 101 and/or terminals 141 or 151 may also be mobile terminals, such as personal digital assistants ("PDAs") including various other components, such as a battery, speaker, and antennas (not shown) .
  • PDAs personal digital assistants
  • components such as a battery, speaker, and antennas (not shown) .
  • FIG. 2 shows a high level diagram that includes a client system 202, the Internet 204, and a web service 206.
  • a system may preferably be used to implement that shows a data request ("get") made by the client system 202. That request may be made through web service 206 via the Internet 204.
  • Web service 206 may validate the user credentials and return the requested data via Internet 204.
  • FIG. 3 shows a logical view that presents an exemplary design of a system according to the invention.
  • the invention may provide a "middleman" application that crawls the web and retrieves cash reporting and positioning information for an entity. Thereafter, the invention may populate a client-side spreadsheet application with the client information that has been retrieved from the web. The various efficiencies and flexibility that this affords a client are part of the invention as well.
  • the system may be formed from less than all the components shown in FIG. 3. FIG. 3, however, does present primary classes that collaborate to implement system functionality according to the invention.
  • One embodiment of the invention may contain the following three software layers: presentation layer 302, business layer 304, and data layer 306.
  • Presentation layer 302 may include a .Net component implemented in the C# language which is responsible for informing a spreadsheet resident at the client which values belong in which cells. The cells are displayed in display 308.
  • Business layer 304 insulates the UI Layer from the design of the datastore 310 in data layer 306. However, business layer 304 preferably does not maintain knowledge — i.e., store — of the presentation of data. This insulation provided business layer 304 allows the data to be retrieved from data layer 306 and populated into a client-side spreadsheet. Thus, the client is not required to take the data and code it into a spreadsheet. Business layer 304 may also be responsible for complex business rule logic, which may be implemented in datamanager 312, according to the invention. [064] Data layer 306 preferably manages persistent data and current transactions. Data layer 306 may also map data objects to physical storage. Data layer 306 may also be responsible for data integrity and transactions. Data layer 306 may preferably include a communicator 314 and CashPro application 316.
  • CashPro application 316 may retrieve the latest data from the web and store all the relevant data in the client computer via business layer 304.
  • the data can be maintained in an encrypted state in the client computer.
  • Communicator 314 may be tasked with providing the latest data to data manager 312 (while datastore 310, on the other hand, may be tasked with providing historic data to data manager 312) .
  • FIG. 4 shows a get data scenario according to the invention.
  • a get data scenario according to the invention may include the following steps (the process steps have been illustrated in FIG. 4 and labeled with element numbers for clarity) :
  • Controller calls system according to the invention 404.
  • Controller passes Bai2 data to BaiParser 406.
  • BaiParser translates Bai2 data into XML
  • Controller passes Bai2 XML to StoreManager 408.
  • FIG. 5 shows an update display scenario according to the invention.
  • An update display scenario according to the invention may include the following steps, following a user selection of an update:
  • Controller requests data map from StoreManager 504.
  • Controller requests Bai2 data files from StoreManager 508.
  • Controller evaluates data map against Bai2 data 512 and constructs a Display instance 512.
  • FIG. 6 shows a data view of the invention.
  • the local file system i.e., user isolated storage — can act as the persistent data store for a cash reporting and positioning system according to the invention.
  • the following exemplary list details each of the exemplary files and their contents :
  • BaiCodes.xml 604 all Bai data codes and their associated data labels.
  • BaiData.xml 608 Bai2 data downloaded from the CashPro web service and parsed into an XML format. There can be multiple Bai2 data files (1 per day) and they can follow the naming pattern XXXXXXX.bai where XXXXXXX represents the date of the file (i.e. 04112005).
  • FIG. 7 shows a process view according to the invention.
  • Process 700 may be implemented on client system 702, which may be running spreadsheet 704.
  • Main thread 706 may preferably utilize controller 708 and storemanager 710 to communicate with file system 712.
  • Process 700 may also utilize a separate worker thread (such as CashPro thread 701 and updater thread 703) for interactions with the CashPro server 714 (including downloading of data and application updates) . This can allow the UI to remain responsive while the positioning and reporting data is being downloaded.
  • FIG. 8A shows a portion 802 of a spreadsheet that indicates that outstanding issue information can be mapped over time. Such mapping preferably allows the understanding of trends with respect to the outstanding issue information. Such outstanding issues may relate to problematic accounts or problematic entries. Furthermore, FIG. 8B shows that outstanding issues can be mapped in an ad hoc report 804. While this feature has been described in terms of outstanding issue mapping, nevertheless the feature of mapping over time can be used to analyze any suitable trend of information that is resident in the application according to the invention.
  • FIG. 9 shows a screen shot 900 that illustrates a dialogue box which may be used for creating of detailed sheets of transaction by the transaction remitter. Such sheets may include high dollar transaction reports as well as negative balance alert reports. Such detailed sheets implement filtering conditions 902 and/or date restrictions 904 which may be used to specify transaction sheets.
  • FIG. 10 shows a screen shot 1000 that illustrates that a user can create granular reports based on information in their BAI2 files. Section 1002 indicates that such reports may be filtered to allow the splitting of transaction types based on internal divisions. Furthermore, lockbox deposits may be split by lockbox number and ACH transactions may be split according to the sender of the ACH.
  • FIG. 11 shows a portion 1102 of a spread sheet that shows that currency rates can be automatically populated, or can be changed manually.
  • FIG. 12 shows a dialogue box 1202 that allows a user to set default display currency for reports.
  • fixed sheets may auto convert data based on currency rates that are downloaded daily or at some other preferably predetermined interval .
  • FIG. 13 shows a portion of a spread sheet that indicates that the user is not required to open Excel® for the operation of systems and methods according to the invention — nor is the user required to be logged ON to the PC. In fact, the only requirement may be to have the PC ON and connected to the appropriate network in order to download the appropriate information.
  • FIG. 14 shows a dialogue box 1402 that allows a user to identify the accounts for which the user desires to obtain a report. Such a dialogue box may also allow a user to sort by account number and account name.
  • FIG. 15 shows a dialogue box 1502 that allows a user to restrict access to selected accounts and set different passwords to access data and download data.
  • data can be stored on a network and can be securely shared between many disparately- authorized users.
  • Another feature may include the ability to create self-designed ad hoc reports and have these reports automatically updated with data from multiple banks. Such a feature may allow a user to use his/her current format and design a sheet that he/she is familiar with, but still retains the benefit of auto population.
  • Yet another feature may include providing an ability to click on a summary data item and see the detail associated with the item. Such a feature may allow a user to view detail data without having to go back to the website.
  • Yet a further feature of the invention is an ability to reconcile the prior day's forecast with the up-to- date data. Such a feature may allow a user to understand daily difference in cash flows.
  • the invention may also provide the ability to create GL files based on downloaded BAI2 data. Accordingly, GL files do not need to be created manually.
  • the data can be automatically mapped based on user-defined (or system- defined) rules that can be maintained in the spreadsheet.
  • systems and methods may present the ability to select which accounts to use from the user available accounts in order to calculate the data to be shown on the spreadsheets. Such a feature may allow the user to get the cash position on one or many accounts without having to re-retrieve that data from an associated bank.
  • the invention is operational with numerous other general purpose or special purpose computing system environments or configurations.
  • Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
  • the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including memory storage devices .
  • TheSoftwareArchitecture Documentcapturesallofthe internal-"in betweenthewalls"-decisionsrequiredto implementthesystem.
  • Thearchitectureofasoftwaresystem mayrequiresixdistinctviews,eachviewfocusingon differentaspectsofthe system.
  • DeploymentView Thisviewdocumentsthe physicaltopologyofthe system modeled in the Deployment Model. It includes each computer in the implementation and describes how they are interconnected. The configuration foreach nodeisalsospecified-O/S,DB,COTSandcustomapplications.
  • Logical View The logical view documents the Design Model, which defines the layers of the application and the primary classes within each layer. The system architect identifies patterns of functionality and creates common mechanismsto provide this functionalityto several areas across the application.
  • Data View - Classes in the logical view are classified as transient or persistent.
  • the persistent classes are mapped to structures on disk, usually into a combination of rows in a relational database.
  • An entity-relationship data model describes the database schema. This view also communicates how the OO classes are mapped to the relational tables.
  • Process (Concurrency) View This view focuses on the concurrency aspects of the system and how they contend for shared resources (i.e., transaction semantics, etc.).
  • the process view documents the independent threads of execution within the system and describes how they communicate. It also lists the resources in contention by these threads and the transaction model for maintaining integritywith these resources.
  • Implementation View This view maps the classes in the Logical View to physical source files and combines the files into deployable components. The implementation view also tracks the dependencies among the components.
  • Security View This view focuses on how the system identifies end users, grants authorization to them based on their identity, ensuring integrity of the system and of the data and properly tracking and auditing of system activity.
  • the component view is formed along three layers - Ul Layer, Business Layer, and Data Layer.
  • the Ul Layer binds attributes of business value objects to Ul objects, presents them to the user, accepts input and processes "submit" requests by unbinding from Ul objects to business objects attributes.
  • the business layer checks business rules and passes business objects to the data layer.
  • the data layer maps business attributes to persistent storage and encapsulates its processing in a single, atomic transaction.
  • the deploymentview presents the topology and its physical and logical connections, followed by the detailed configuration for each node in the network.
  • a .NET security policy is created giving full trustto the custom application assemblies. This is necessaryto allow Excel to load the custom application assemblies at runtime.
  • Theapplication isstructured alongthreedistinctlayers-Presentation,Business,and Data.
  • Controller requests data map from StoreManager
  • Controller evaluates data map against Bai data and constructs a Display instance
  • Controller updates the internal data map
  • the local file system will act as the persistent data storefor CashPro Accelerate.
  • the following list details each of the file and their contents:
  • CashPro Accelerate will utilize a separate workerthread for all interactions with the CashPro server (including downloading ofCashPro data and application updates). This will allowthe Ul to remain responsive while CashPro data is being downloaded.
  • the implementation view describes how the classes and logic in the Design Model are physically implemented with source code. It also describes how the implementation source is physically contained in files and how these files combine to form executable components.
  • the Implementation Model combines source units into packages to form components, such as a .jar, .ear, war, .dll or a .Net assembly. As a result the Implementation Model serves as the roadmap to the source implementation of the system.
  • the CashPro Accelerate application is implemented as four DLLs as depicted in the following diagram:
  • the main Infrastructure assembly is subdivided into namespaces as follows:
  • CashPro.Accelerate.UI All shared user interface functionality including the CashPro toolbar and user settings dialog. Accelerate utilizesthe following CashPro web services:
  • the security view describes howthe system implements the security requirements specified in the Detailed Spec. Security design is presented in the following sub-areas.
  • CashPro Excel User Identification can be performed via a login dialog. Actual authentication can be performed by the CashPro web service using credentials passed to it during the web service calls. AUTHORIZATION
  • Date entitlementforthe CashPro data can be determined by the CashPro web service. DATAINTEGRITYAND PRIVACY
  • All downloaded CashPro data, user settings, and any other stored data will be stored in a user's documents folder (i.e. C: ⁇ My Documents ⁇ CashPro ⁇ Accelerate) making it unavailable to other non-administrative users ofthe system.
  • all locally stored data can be encrypted to prevent reverse engineering ofthe application.
  • Rijndael private key encryption can be used for all locally stored data files. This encryption scheme, also known as Advanced Encryption Standard (AES) utilizes a 265-bit private key.
  • AES Advanced Encryption Standard

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Development Economics (AREA)
  • Technology Law (AREA)
  • Human Resources & Organizations (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Des systèmes et des procédés d’établissement de situation et de rapport de trésorerie sont de préférence fournis. Un système pour établir un rapport de trésorerie et pour établir une situation de trésorerie selon l'invention peut comprendre un module de contrôleur et un module de service Web. Le module de contrôleur peut être conçu pour recevoir une sélection pour mettre à jour une mémoire de données. Le module de service Web peut être conçu pour recevoir un appel du module de contrôleur. L'appel provenant du module de contrôleur peut être envoyé en réponse à la sélection de mise à jour de la mémoire de données. Le module de service Web peut être configuré pour récupérer des données d'informations de compte bancaire en réponse à l'appel provenant du module de contrôleur.
PCT/US2009/049671 2009-07-06 2009-07-06 Systèmes et procédés d’établissement de situation et de rapport de trésorerie Ceased WO2011005247A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020117004871A KR20120047839A (ko) 2009-07-06 2009-07-06 현금 포지셔닝 및 리포팅을 위한 방법들 및 시스템들
CN2009801333409A CN102138154A (zh) 2009-07-06 2009-07-06 现金定位和报告用系统和方法
EP09847168A EP2297691A1 (fr) 2009-07-06 2009-07-06 Systèmes et procédés d'établissement de situation et de rapport de trésorerie
PCT/US2009/049671 WO2011005247A1 (fr) 2009-07-06 2009-07-06 Systèmes et procédés d’établissement de situation et de rapport de trésorerie
MX2011002146A MX2011002146A (es) 2009-07-06 2009-07-06 Sistemas y metodos para la ubicacion y reporte de dinero.

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2009/049671 WO2011005247A1 (fr) 2009-07-06 2009-07-06 Systèmes et procédés d’établissement de situation et de rapport de trésorerie

Publications (1)

Publication Number Publication Date
WO2011005247A1 true WO2011005247A1 (fr) 2011-01-13

Family

ID=43429441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/049671 Ceased WO2011005247A1 (fr) 2009-07-06 2009-07-06 Systèmes et procédés d’établissement de situation et de rapport de trésorerie

Country Status (5)

Country Link
EP (1) EP2297691A1 (fr)
KR (1) KR20120047839A (fr)
CN (1) CN102138154A (fr)
MX (1) MX2011002146A (fr)
WO (1) WO2011005247A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020129054A1 (en) * 2000-07-11 2002-09-12 Ferguson Charles H. Method and system for integrating network-based functionality into productivity applications employing spreadsheets
US20050246269A1 (en) * 2004-03-12 2005-11-03 Sybase, Inc. System Providing Methodology for Consolidation of Financial Information

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020129054A1 (en) * 2000-07-11 2002-09-12 Ferguson Charles H. Method and system for integrating network-based functionality into productivity applications employing spreadsheets
US20050246269A1 (en) * 2004-03-12 2005-11-03 Sybase, Inc. System Providing Methodology for Consolidation of Financial Information

Also Published As

Publication number Publication date
MX2011002146A (es) 2011-04-05
CN102138154A (zh) 2011-07-27
KR20120047839A (ko) 2012-05-14
EP2297691A1 (fr) 2011-03-23

Similar Documents

Publication Publication Date Title
US10783116B2 (en) Systems and methods for managing data
US8131666B2 (en) Context-based user authentication, workflow processing, and data management in a centralized application in communication with a plurality of third-party applications
US8639729B2 (en) Executing a business process in a framework
US20120143634A1 (en) Systems, Methods, and Computer Program Products for Processing Insurance Claims
CN111382279B (zh) 审单方法和装置
US11941068B2 (en) Case leaf nodes pointing to business objects or document types
US9208522B2 (en) Systems and methods for cash positioning and reporting
US20050187852A1 (en) Method and system for account reconciliation in a wealth management system
US20020184145A1 (en) Methods and system for integrating XML based transactions in an electronic invoice presentment and payment environment
US8352958B2 (en) Systems and methods for providing a generic audit trail service
US20230394478A1 (en) Generating and publishing unified transaction streams from a plurality of computer networks for downstream computer service systems
US20130080338A1 (en) Ideas promoted to projects and synchronization of status information
US12413599B2 (en) Systems, methods, apparatuses and computer program products for executing data verification operations between independent computing resources
US10915968B1 (en) System and method for proactively managing alerts
US20120158583A1 (en) Automated bank transfers using identifier tokens
US20160027121A1 (en) Insurance risk management systems and methods
US20260120202A1 (en) Disbursement authorization data object processing system utilizing real-time status data and authentication keys
EP2351285B1 (fr) Authentification d utilisateur basée sur le contexte, traitement d un flux de travaux, et gestion des données
EP2297691A1 (fr) Systèmes et procédés d'établissement de situation et de rapport de trésorerie
US20140229344A1 (en) Systems and methods for parsing unknown codes obtained from a customizable spreadsheet application interface
US20260111430A1 (en) User interfaces and object graphs for content item customization and transmission
CN121684910A (zh) 一种面向车联网的支付清结算处理方法及装置
So et al. Enhancing Bank Reputation by Centralizing Bank Debtor Information System
Edidin et al. Best Practices for HL7 with BizTalk
AU2008269925A1 (en) Context-based user authentication, workflow processing, and data management in a centralized application in communication with a plurality of third-party applications

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980133340.9

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2009847168

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: MX/A/2011/002146

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 20117004871

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2012519523

Country of ref document: JP

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

Ref document number: 09847168

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: JP

ENPW Started to enter national phase and was withdrawn or failed for other reasons

Ref document number: PI0917720

Country of ref document: BR

Free format text: PEDIDO RETIRADO, UMA VEZ QUE, SEGUNDO O ART. 216 INCISO 2O DA LPI, O DOCUMENTO DE PROCURACAO NAO FOI PROTOCOLADO EM SESSENTA DIAS CONTADOS DA PRATICA DO PRIMEIRO ATO DA PARTE NO PROCESSO, E NAO HOUVE MANIFESTACAO DO REQUERENTE FRENTE A PUBLICACAO DO ARQUIVAMENTO DA PETICAO (11.6.1) NA RPI 2354 DE 16/002/2016.