+

WO2011008186A1 - Système et procédé à base de logiciel de gestion d'entreprise - Google Patents

Système et procédé à base de logiciel de gestion d'entreprise Download PDF

Info

Publication number
WO2011008186A1
WO2011008186A1 PCT/US2009/004042 US2009004042W WO2011008186A1 WO 2011008186 A1 WO2011008186 A1 WO 2011008186A1 US 2009004042 W US2009004042 W US 2009004042W WO 2011008186 A1 WO2011008186 A1 WO 2011008186A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
data set
processor
inputting
module
Prior art date
Application number
PCT/US2009/004042
Other languages
English (en)
Inventor
Bander Abdullah Mohammed Al-Saud
Tahir Rashid
Nader Jaber Saleh
Original Assignee
Soroof International
30550.03 Patent Trust
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 Soroof International, 30550.03 Patent Trust filed Critical Soroof International
Priority to PCT/US2009/004042 priority Critical patent/WO2011008186A1/fr
Publication of WO2011008186A1 publication Critical patent/WO2011008186A1/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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to computer systems and computerized methods for managing businesses. BACKGROUND ART
  • Computer database management systems are widely used in both standalone computer systems, as well as web-enabled distributed computer systems.
  • Database application programs operate by retrieving data from the database management system, performing modifications on the data and returning the data to the database management system.
  • Database management systems are accessed through interface functions that control the manner in which data is accessed.
  • the business may service a large number of accounts.
  • businesses typically maintain these records on multiple-user databases. Therefore, each department has a program that maintains these records.
  • information must be extensively duplicated and thus, over time, maintaining database system performance becomes a challenge.
  • Such platforms have a database that stores corporate information, business application software for its business functions (typically finance, sales, marketing, etc.), a security or user access system that controls access to the information by a number of users that are assigned roles that permit or deny access to the information, based on the assigned role of the individual, and a system bus that provides an interface permitting the various components of the system to communicate with each other according to certain protocols.
  • these business platforms may have developed separately over time so that the various modules relating to business functions, such as marketing and sales, may have different configurations, and may be coded in different software languages, thereby complicating communication between the modules and adding complexity to information sharing between corporate divisions and the generation of reports for management. Further, as business organizations grow in size, complexity and need for more information sharing, the business platforms and modules often lack sufficient scalability to keep pace.
  • the business platform is one that serves a variety of separate business entities, that may be independent corporations, partnerships or other business entities, and that may be hosted by a third party.
  • franchisees that are independent corporations
  • franchisees in a regional area to share information between themselves, with regard to certain functions, such as marketing, but perhaps not with regard to other functions, such as finance.
  • information sharing between franchises would not be desired or allowed but some franchisees might hold multiple franchises. Accordingly, the sharing of information is not only complicated due to the separate business entities involved, but also the degree and extent of information sharing that is required.
  • an inter-business software platform that may be hosted by a third party
  • the separate business entities may each have before hand developed their own business modules, for example each might already have developed their own marketing, sales, accounting and web management modules, before the advent of the hosted platform.
  • Business entities participating in an inter-business platform may share common data access on their networked computers. Maintaining uniform and consist data access is an important aspect of sales, customer relationships, and overall business strategy. Non-integrated and non- accessible data, flowing from one computer to another, may result in loss of sales and profits, due to lack of communication and inefficiency of data flow.
  • the software-based business management system is an integrated business management system for managing financial transactions and interactions of small and midsize businesses.
  • the system includes at least one central server having computer-readable memory and a computer display associated therewith. Multiple users of the business access the at least one server through remote network terminals.
  • the system allows integration of a wide variety of business-related tasks and functions, and may be integrated into an existing network, using existing software and hardware.
  • a plurality of software modules, each representing a different aspect of a business to be managed, are integrated into the system.
  • the system incorporates a financial module, a fixed asset module, a sales module, a security module, a purchasing module, an inventory module, a human resources module and a report module.
  • one or more users input financial-based data to establish a financial data set; sales-based data to establish a sales data set; purchasing-based data to establish a purchasing data set; inventory data to establish an inventory data set; and human resources-based data to establish a human resources data set.
  • These data sets are stored in a database associated with the computer-readable memory.
  • At least one journal voucher is generated, including calculated net financial data based upon the financial data set, the sales data set, the purchasing data set, the inventory data set and the human resources data set.
  • the net financial data is then recorded in a general ledger stored in the computer-readable memory, and at least one report is generated based upon the net financial data recorded in the general ledger. The report is then displayed on a computer display.
  • Fig. 1 is a block diagram illustrating the software-based system for business management according to the present invention.
  • Fig. 2 is a block diagram illustrating the overall software architecture for the software- based system for business management according to the present invention.
  • Fig. 5 is a flowchart illustrating data flow in the accounts payable sub-module of the software-based system for business management according to the present invention.
  • Fig. 7 is a flowchart illustrating data flow in the budget sub-module of the software- based system for business management according to the present invention.
  • Fig. 8 is a flowchart illustrating data flow in the general ledger sub-module of the software-based system for business management according to the present invention.
  • Fig. 9 is a flowchart illustrating data flow in the fixed asset module of the software- based system for business management according to the present invention.
  • Fig. 10 is a flowchart illustrating data flow in the inventory module of the software- based system for business management according to the present invention.
  • Fig. 11 is a flowchart illustrating data flow in the human resources module of the software-based system for business management according to the present invention.
  • Fig. 13 is a flowchart illustrating data flow in the security module of the software- based system for business management according to the present invention.
  • Fig. 14 is a flowchart illustrating data flow in a career development module of the software-based system for business management according to the present invention.
  • Fig. 15 is a flowchart illustrating data flow in a cash flow module of the software- based system for business management according to the present invention.
  • Fig. 16 is a flowchart illustrating data flow in a training module of the software-based system for business management according to the present invention.
  • Fig. 18 is a flowchart illustrating data flow in a purchasing module of the software- based system for business management according to the present invention.
  • the software-based business management system 10 is an integrated business management system for managing financial transactions and interactions of small and mid-size businesses.
  • the system 10 includes at least one central server 12 having a processor 20 (e.g., a microprocessor), computer-readable memory 14 (which may be volatile or non- volatile computer memory, and includes both an area of main memory connected to the processor 20 by a bus and a data storage device including read only memory [ROM], random access memory [RAM], or both) and a computer display 16 associated therewith.
  • the server 12 is connected to a network through a data communications device, which may be a modem, a network interface card, a router, etc.
  • the system 10 allows integration of a wide variety of business-related tasks and functions, and may be integrated into an existing network, using existing software and hardware.
  • a plurality of software modules each representing a different aspect of a business to be managed, are integrated into system 10.
  • Each module communicates via interconnection with processor 20 of server 12.
  • Processor 20 may be any suitable type of processor associated with a computer server, such as a programmable logic controller or the like.
  • Memory 14 associated with server 12 incorporates at least one database 15, and users may write to the database, change entries in the database, and read information from the database, either directly at server 12 or through the remote terminals illustrated in Fig. 1.
  • system 10 includes a security module 48, which may provide selective access to database 15, dependent upon a user's particular security level. For example, some users may be able to only read data, rather than write new data or change existing data entries.
  • System 10 incorporates a financial module 22, a fixed asset module 24, a sales module 26, a security module 48, a purchasing module 28, an inventory module 30, a human resources module 32 and a report module 34.
  • Each module may incorporate sub-modules.
  • human resources module 32 includes a payroll sub-module 46.
  • the financial module 22 includes a general ledger sub-module 36, a budget sub- module 38, an accounts payable sub-module 40 and an accounts receivable sub-module 42.
  • the general ledger sub-module 36 creates, stores and controls editing of a general financial ledger which is stored in database 15 and may be used to generate printable or displayable reports, as will be discussed in greater detail below.
  • Users may define general ledger account assignment models, which may save the user time and aids in preventing mistakes during the manual posting of journal entries.
  • users may reverse journal entries and ventures, allowing users to reverse month-end accruals postings automatically. By default, reversal of specified postings will occur on the first day of the following calendar month in the preferred embodiment, but if necessary, users can specify a different reversing date for each posting.
  • the financial module 22 in conjunction with updated information stored in database 15, allows the user to calculate exchange rate differences, which may be automatically applied to the general ledger. Thus, users may periodically evaluate their open items in foreign currencies, and then identify differences and choose the appropriate correction transaction.
  • Financial module 22 allows the user to access, generate and alter financial report templates. Users may generate any number of financial report templates. Users may create templates for any purpose, such as additional profit-and-loss statements, for example.
  • the budget sub-module 38 aids the user to define and manage budgets. Users can configure budget allocation methods and display a summarized budget report on display 16 that compares actual and planned figures. In addition, users can define an online alert that notifies them whenever a transaction exceeds a monthly or annual budget limit, which may be entered by the user or determined automatically through calculations to be described in greater detail below.
  • Users may also define different profit centers or departments. Users can allocate the corresponding revenue and cost accounts to a predefined profit center in the chart of accounts. In conjunction with the profit center allocation within financial module 22, profit center reports may be generated, to be displayed or saved in memory. The profit-and-loss statement is based on revenues and costs (both direct and indirect) as defined in the allocation rules (which may be entered by the user and stored in memory 14), and the report may be run for any profit center. Users may select between annual and monthly display formats and compare the results with figures for the previous period.
  • the fixed asset module 24 allows the streamlining of different fixed asset management functions, such as depreciation calculation, sale, disposal and exchange of assets and any asset-related expenditure.
  • the fixed asset module 24 provides users with forecasted information on depreciation costs of all fixed assets or a specific asset record in the system. Users may monitor any expenditure that will be incurred for given fixed assets. A budget may be set for these expenditures.
  • the sales module 26 allows users to record each sales opportunity, from a first phone call to the successful close of a transaction. Sales information is stored, as journal entries, vouchers or ledger entries, in database 15 of memory 14, and may be accessed by the users through the network. Users can enter various details concerning the sales opportunity, including the source, potential, closing date, competitors, and activities. As soon as the first relevant quotation is created, users can link it with the opportunity to simplify later tracking and analysis.
  • the sales quotation capability of system 10 offers flexibility when creating the contents of quotations or any marketing document.
  • credit memos may be generated automatically from templates, with the financial information either being manually entered, or filled automatically from information stored in database 15. Sales information, such as receipts, invoices and the like, may be displayed to the user on display 16 or printed.
  • the purchasing module 28 allows users to generate, save and edit purchase orders, and provides an integrated sub-system for ordering materials or services from vendors. These orders update the available quantity of the ordered items and inform the warehouse manager or the like of the expected delivery date. Users can split a single purchase order into multiple parts when, for example, items need to be shipped to multiple warehouses. The split or revisions are required so that different packing slips and delivery notes can be created for each shipment. Each line item within a purchase order or an account payable voucher can be shipped to, or specified as, a different warehouse location.
  • Users may also generate goods receipt purchase orders. This function allows users to receive a delivery at the warehouse or allocate deliveries to multiple warehouses. Goods receipts may be linked to a purchase order, and users can change the purchase order quantity versus the actual received quantity. Similarly, goods return documents may be generated, stored, displayed and/or printed. Such return documents are used when a vendor returns an item or items for repair or without credit.
  • the purchasing module 28 When processing vendor invoices, the purchasing module 28 creates a journal entry, to be stored in database 15. Users can use this information to process subsequent payments to the vendor. Credit memos may also be generated and issued to vendors for returned merchandise. The required data can be imported from the original invoice, stored in database 15, as it is with any other sales and purchasing document. All sales and purchasing documents, which are stored in database 15, may be displayed on display 16 or printed. Users accessing database 15 may search by period, document number, or document type.
  • System 10 Software tools relating to business partners are incorporated into the purchasing module 28 and the sales module 26. All critical information on customers and vendors, such as address, preferences, sales employees, and credit terms, for example, is entered in the business partner sub-modules. Users can define an unlimited number of contact persons for each business partner, along with their phone numbers, e-mail addresses, and other important data. Users may also enter a customer contact or vendor name and send e-mail or internal network messages. All relevant associated data, such as customer sales reports and detailed balances, can be displayed on display 16. Interactions with customers, such as phone calls, meetings, and follow-up tasks, may be tracked and saved automatically in database 15 as journal entries. Users may also modify these entries to include special notes and attachments to activities, and further schedule next action items. System 10 further allows users to maintain a calendar, which graphically displays the activities for one or more users. The calendar also provides functionality for scheduling activities as well as modifying scheduled activities. The calendar can be configured to show only specified activities and users.
  • the inventory module 30 enables users to manage item master information (to be described in greater detail below) and maintain, edit and store serial and batch numbers, as well as price lists. Users also may define alternative items, perform inventory increase or decrease adjustments, revalue inventory costs based on current market values, and perform cycle counts.
  • Control of item master data allows users to define production items, purchase items, or purchase non-inventory items, such as labor, travel, or fixed assets. Default information, such as purchasing vendor names, purchasing and selling units of measure and the like are stored in database 15, to be accessed for inventory purposes.
  • Stocked items can be maintained and tracked in multiple warehouses and system 10 further supports different inventory valuation methods on a per item basis. Such methods include standard cost, moving average, and "first in, first out”. Planning data is also maintained within item master data.
  • Serial numbers may be automatically generated based on predefined masks or methodologies. Serial numbers may also be manually created and assigned upon release of an item from inventory, or optionally on every transaction. A cross-reference table of vendor part numbers to inventory part numbers is further preferably maintained and stored in database 15. Vendor part numbers can be used on purchasing documents in lieu of inventory part numbers.
  • System 10 allows for the production of updated stock valuation method reports, where users can select items from a list and change the current valuation method to an alternative method.
  • inventory module 30 allows to record goods receipts and issues that are not directly related to a sales or purchasing document. Inventory module 30 may further be used to track stock transfers, where inventory is moved between warehouse locations, and to issue orders across the network for such a transfer. Through inventory module 30, users may enter opening balances for inventory items and also update warehouse data recorded in database 15.
  • a cycle counting sub-system is further provided. In large warehouses, counting stock is often a continual process. This sub-system streamlines the process by identifying when each item in stock is due to be counted. Alerts and reports are produced to help ensure that items of different levels of importance are counted as frequently as required.
  • users may make changes in existing inventory prices. This may be necessary when the current price of the material does not match the actual market price. In that case, the price is adjusted and a manual posting on the change is posted. Users may further define any number of price lists and link them with customers or vendors within database 15. In addition, they may create dynamic links between price lists, quickly and easily, updating the links automatically whenever the primary price list changes.
  • the human resources module 32 provides staff management capabilities, including employee details and contact information. Entry, display and modification of employee master data, stored in database 15, allows users to track important information about each employee, such as name, job title, skills, department, reporting manager, attendance information, salary, team membership, and address information.
  • the report module 34 enables users to create reports and initiate corrective actions immediately afterwards.
  • Module 34 includes generation of accounting reports, enterprise reports, inventory reports, financial reports, and reports to aid decision-making. Users can export any report to existing, integrated software, such as Microsoft Excel®, for example. All modules may be accessed through a separate security module 48, which is selectively controlled to determine and control levels of access for information.
  • Fig. 4 illustrates the production of payroll reports using payroll sub-module 46, which is part of human resources module 32.
  • Initial input occurs at 100, with the input including data related to monthly leave 102, employee payroll exceptions 104, allowances and deductions 106, loans 108, lateness and absences 110 and overtime 112. Termination or end of an employee's service is also incorporated at 114. Payroll calculation occurs at step 1 16.
  • the payroll calculation 116 is used to generate a payroll voucher at 118. Any necessary indemnity calculations are performed at 120, and the payroll voucher data and the indemnity calculations are used to produce a journal voucher 142, which is then written into the general ledger at 144, which may be stored in memory 14 and/or displayed on display 16.
  • the general ledger sub-module 36 which is part of financial module 22, will be described in detail below, with particular reference to Fig. 8.
  • the payroll calculation is posted at 122 and an employee pay slip is produced at 124.
  • invoice settlement is not needed, then flow proceeds directly to the decision to cancel the invoice at step 228.
  • the decision to cancel the invoice is made at step 228.
  • the invoice is canceled at 222, which is then recorded on a journal voucher 224 for recordation in the general ledger at 226. If the invoice is not canceled, then the invoice is paid at 230, which is then recorded in another journal voucher at 224, and results in the end of the process (at step 238) and the production of the final report at 240.
  • Fig. 6 illustrates the accounts receivable sub-module 42, which is part of financial module 22.
  • Initial input occurs at step 300, where either invoices are registered at 302, or accounts receivable advance payments are entered at 304.
  • invoices are registered at 302, they are then posted at 306, and a journal voucher is generated at 310 for recordation in the general ledger 308 (which may be stored in memory 14 and/or displayed on display 16).
  • a debit or credit memo is generated at 314 and posted at 320.
  • flow returns to the decision step at 312. If invoice settlement is not needed, then flow proceeds directly to posting at 320, where another journal voucher is produced at 318 for recordation in the general ledger at 308.
  • step 304 If an accounts receivable advanced payment is made at step 304, then the payment is posted at 332 and a journal voucher is produced at step 334 for recordation in the general ledger at 336. This ends the process at step 338 and the final report is produced at 340, for recordation in memory 14 and/or display on computer display 16.
  • Fig. 7 illustrates budget entry and calculation in budget sub-module 38, which is part of financial module 22.
  • Initial input occurs at step 400 and a budget template is provided for the user at 402.
  • the budget template allows the user to enter data into selected fields.
  • the budget is assigned at 404 and a first report is produced at 406 for recordation in memory 14 and/or display on computer display 16.
  • the user may then selectively approve the budget at 410. If the user does not approve the budget, then the flow passes back to step 404 for alteration of the budget parameters. If the user does approve the budget at 410, a second report is generated at 408, and the user has the option of further enhancing the budget parameters at step 412.
  • the budget may be enhanced at 414, with the user selectively increasing the budget by a selected amount at step 416.
  • the user may choose whether a transfer of the budget is required. If no transfer is required, then the process ends at step 418. If a transfer is selected at step 413, then the budget transfer occurs at step 415, and the budget amount is selectively increased or decreased at step 417.
  • the user may perform depreciation calculations on any stored assets. Depreciation is posted at 614 for the production of a report at 612. A journal voucher 616 is also produced, for recordation in the general ledger at step 618.
  • the user determines whether any assets require sale or disposal. The assets may be sold at 622, resulting in the production of a journal voucher at 626 for recordation in the general ledger at 618. If the assets are being disposed of, disposal occurs at step 624, and up-to-date depreciation is calculated at step 628. If no assets require selling or disposal, the process ends at step 632.
  • the user may also choose to upgrade or update the assets at step 608.
  • a journal voucher is then produced at step 630 and the process ends at step 632.
  • the user may further choose to transfer assets at step 606, and then the process ends at step 632. It should be noted that the user may sell or dispose of the asset at any time without needing to post the depreciation prior to selling or disposal of the asset.
  • the user When a new entry is stored at 702, the user also may report material damage at 714, a return of stock at 716, or a transfer of stock at 718. These are all recorded in the general ledger at step 726, and the process ends at step 738.
  • the user can decided between "regular” recruiting at 806 and immediate recruiting at 808.
  • regular recruiting the user may enter information and requirements for the manning of available positions at 810, and then form a "short list" of job candidates at 814.
  • Candidate evaluations are entered at 819, and the entry of a final candidate selection occurs at 820.
  • Interview scheduling may be input at 822, and further immediate recruiting may occur at 824.
  • recruiting information is then recorded in the employee master file at 826.
  • a job application is automatically generated and filled at 812, and a job offer is made and recorded at 816.
  • the application is electronically confirmed at 818, and the recruiting information is recorded in the employee master file at 826.
  • the process ends at 850, and the user may be returned to the main system menu.
  • the archive sub-system 828 is used for the filing and storage of official human resources-related documents at 830.
  • the system then ends at 850, once the documents have been recorded.
  • the user may enter information into previously generated forms, such as a car purchasing form 834, a multiple exit re-entry form 836, a form for opening a new account 838, or a passport release form 840. It should be understood that any desired form may be generated in this sub-system.
  • requests for general leave may be recorded at 844, and special requests may also be recorded, such as requests for family tickets and visas at 846.
  • requests for family tickets and visas may be recorded at 844, and special requests may also be recorded, such as requests for family tickets and visas at 846.
  • an employee's leave balance is adjusted, and the process ends at 850.
  • Fig. 12 illustrates the method of using the sales module 26. Initial input occurs at step
  • sales opportunities being entered at 902.
  • the user may either go immediately to production of a sales order at 908, or may request generation of a quotation at 904, which may include further material supply quotations (906).
  • order deliveries are scheduled and recorded at 910, and an invoice is produced at 912.
  • the invoice is passed to accounts receivable at step 914, and then recorded as a general ledger entry at 916.
  • the sales opportunity may also be a customer follow-up, which leads to step 918.
  • the user may enter a change of status regarding present or future sales opportunities with the clients, and data flow passes back to step 902. The process ends at 922.
  • Fig. 13 illustrates the methodology of security module 48.
  • Initial input occurs at 950, and from the end user list (952), the user may change a password at 954, copy a user access menu at 956, back up the system at 958, or assign a role for a position at 960.
  • the decision of password expiration is made at step 962.
  • the password is not set to expire, then the password may be changed at the first user entry (step 964). If the password is set to expire, then the remaining days to expiration are calculated at step 966, and recorded in a generated report at 974, with the process ending at 976.
  • Both the copying of an access menu (step956) and the backing up of the system (step 958) are single step processes, with the processes ending at 976 once complete, and a report generated on the activity at 974. If the user is assigning a role for a position at 960, the system records whether assignment is being made by employee (step 968) or by position level (step 970). Assignment is made and flow passes back to the user access menu at 972.
  • the system can be used as a career management system, with a career management module being coupled with human resources module 32.
  • a prospective employee submits an employment application at step 1000, which is input and stored in the database.
  • the prospective employee is nominated to a specific job at step 1002.
  • Each step, such as the nomination is recorded as a journal entry in the database.
  • the system then checks the applicant against a set of employment requirements, stored in the database, at step 1004. For each job created in the database (at step 1006), the users input a list of particular necessary skills, such as education, certifications, languages, etc. (step 1008).
  • step 1010 If the user passes the requirements check at step 1010, then a specific job is assigned to the user at step 1014. If the user does not pass at step 1010, then the user's application is transmitted to human resources for approval at step 1012. If approved at step 1016, then data flow returns to step 1014. If the application is not approved, then the application is saved as an archived application in the database at step 1018.
  • the system offers an annual appraisal of job performance at step 1024.
  • a promotion or raise is determined at step 1022, with a comparison of the yearly appraisal being made at step 1020 against the job requirements set at step 1004.
  • the employee may be assigned further job training at step 1026, including classes (step 1038), requiring both attendance and the passing of assigned coursework at step 1040.
  • the employee's profile is updated at step 1042 and the employee's status is recorded as a journal entry in the database.
  • the employee's performance is based upon meeting set goals (step 1032), on the evaluation of the employee's supervisors (step 1030) and on an evaluation by the human resources department (step 1028).
  • Suggestions for the employee may be made by any of the above at step 1034, along with the assignment of further tasks and job duties at step 1036. These may include further coursework at step 1026.
  • the training in step 1026 may be part of a training module, coupled with the human resources module.
  • Fig. 16 illustrates a training module, which may be used at step 1026, or may be used as a stand-alone module, to be implemented at any process step or time.
  • initial input is made at step 1100.
  • Planning of particular training or coursework occurs at step 1108, and the human resources module provides input at 1106 in the identification of needed training at step 1104.
  • organization of the course or courses occurs at 11 10, and trainees are selected and assigned to courses at step 1112.
  • the trainees, or job candidates are sorted at 1114, and attendance of courses occurs, and is recorded, at step 1116.
  • a course may be canceled (or an attendee removed from the course) at step 1118, which may result in creation of a wait list for attendees at 1120.
  • Normal coursework resumes at 1122, including an evaluation at 1124, resulting in generation of evaluation reports 1126, which may be stored as journal entries in the general ledger database.
  • the process closes at 1128.
  • a cash flow module may be coupled with financial module 22.
  • debtors' receipts, employee receipts and company returns checks 1050 may be recorded as receipt vouchers at step 1052, with review and auditing of the receipt vouchers occurring at step 1056. Approval occurs at step 1058. If the vouchers are not approved, they are checked for errors at step 1054. The approval is recorded as a journal entry at 1060, and then recorded in the general ledger module at step 1062. Once approved, bank deposit transactions occur at step 1064, and the transaction, along with any bank deposit slips (which may be generated at step 1066), is recorded as a journal entry at 1060, and then recorded in the general ledger module at step 1062. The nature of the transaction is entered at step 1070, including bank debit notes, bank credit notes, bank transfer notes and bank advice notes 1068.
  • Payment voucher information is also entered at step 1072, including input of voucher transactions from other modules at step 1078, and the printing of associated checks at step 1074. Approval and posting of the payment vouchers occurs at step 1080, at which point the printed checks are submitted at step 1076. This process is also recorded as a journal entry at 1060, and then recorded in the general ledger module at step 1062.
  • Bank statement and account reports and received and generated at 1084 and entered at step 1082. Any bank reconciliations at 1086 result in generation of reconciliation reports at step 1088.
  • closing reports are generated at step 1092, and any balances are re-evaluated at 1094, resulting in generation of a balance re-evaluation report at 1096. The process then ends at step 1098.
  • the above methodology allows a client who owns or operates a group of companies to operate all of the companies by buying one license of the above system, and then using a single database.
  • Each company has its own secure data and transactions, with the automatic production of special reports that accumulate data from all companies' data summarized it into a single report according to user requirements.
  • Any type of currency or exchange rate may be used, and an administrator of the above system has the ability to control the end user messages text, because all end user messages are saved on the system database.
  • the administrator can control whether the end user message is a warning message only, or if a system transaction should be stopped when this cause occurs. Further, the administrator can control whether this message should be displayed to the end user as an alert message or at the last line of the screen.
  • a historical file can be built for any system transaction that shows all types of Data Manipulation Language (DML) for that transaction, including display of DML date, time, terminal, user, and the old and the new values.
  • DML Data Manipulation Language
  • Fig. 18 illustrates the methodology of purchasing module 28.
  • Initial input begins at step 1300 and at step 1302, a purchase request is formatted. If the user has sufficient information, a purchase order may be automatically filled and sent directly to the supplier of the goods to be purchased at step 1304. A report of this is automatically generated at step 1306, and the process ends at step 1324.
  • a request for quotation is prepared at step 1308, and the request for quotation is either physically printed or electronically formatted and completed at 1310.
  • the request for quotation is sent to the supplier at step 1312 and the supplier delivers the quotation at step 1314.
  • a selection may then be made from the supplier's goods and services at step 1316, based upon the quotation(s), and a purchase order is prepared at step 1318.
  • the purchase order is delivered to the supplier at step 1320, and a report of the transaction is automatically generated at step 1322.
  • the process ends at step 1324.
  • Fig. 17 illustrates an intellectual property management example.
  • Fig. 2 shows a general system for a general business, including sales and purchases.
  • the "fixed assets" are replaced by a patent portfolio 1208, which may be managed in the same manner as tangible goods.
  • invention intake module 1206 takes the place of sales module 26.
  • Invention intake includes receipt of invention disclosures.
  • the intellectual property services are offered to clients in module 1206, including initial disclosure retrieval, which is then recorded in the database, and the offering of further legal services, such as patent application drafting, patent application prosecution, litigation matters, and the like.
  • the purchasing module 28 is replaced by an intellectual property transfer module 1200, where intellectual property may be purchased, licensed, assigned, or otherwise transferred between parties.
  • a client module 1202 replaces human resources module 32, with management of clients taking the place of managing employees.
  • payroll module 46 is replaced by a module for handling client financial matters, such as intellectual property royalties, fees on intellectual property (such as maintenance fees, for example), and the like.
  • the remaining architecture may remain the same, including security, financial records and the like.
  • the software may be embodied in a computer program product that includes a computer readable medium.
  • computer readable medium includes a hard disk, a floppy disk, a compact disk (CD), a DVD, a laser disk, or any physical medium readable by magnetic, optical, or other transducer for reading instructions recorded on the medium and converting the instructions into electronic signals that can be read by a computer processor when loaded into main memory, and executed by the processor to carry out the computer program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Le système de gestion d'entreprise à base de logiciel (10) est un système de gestion d'entreprise intégré pour gérer des transactions financières et des interactions de petites et moyennes entreprises. Le système (10) comprend au moins un serveur central (12) comportant une mémoire (14) pouvant être lue par un ordinateur et un afficheur d'ordinateur (16) associé à celui-ci. De multiples utilisateurs de l'entreprise accèdent au(x) serveur(s) (12) par l'intermédiaire de terminaux de réseau à distance (18). Le système (10) permet l’intégration d'un grand nombre de tâches et de fonctions associées à l'entreprise et peut être intégré dans un réseau existant, à l’aide d’un logiciel et d’un matériel existants. Une pluralité de modules logiciels, représentant chacun un aspect différent d'une entreprise à gérer, sont intégrés dans le système (10). Le système (10) incorpore un module financier (22), un module des immobilisations (24), un module des ventes (26), un module de sécurité (48), un module d'achat (28), un module d'inventaire (30), un module des ressources humaines (32) et un module de rapport (34).
PCT/US2009/004042 2009-07-13 2009-07-13 Système et procédé à base de logiciel de gestion d'entreprise WO2011008186A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2009/004042 WO2011008186A1 (fr) 2009-07-13 2009-07-13 Système et procédé à base de logiciel de gestion d'entreprise

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2009/004042 WO2011008186A1 (fr) 2009-07-13 2009-07-13 Système et procédé à base de logiciel de gestion d'entreprise

Publications (1)

Publication Number Publication Date
WO2011008186A1 true WO2011008186A1 (fr) 2011-01-20

Family

ID=43449607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/004042 WO2011008186A1 (fr) 2009-07-13 2009-07-13 Système et procédé à base de logiciel de gestion d'entreprise

Country Status (1)

Country Link
WO (1) WO2011008186A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014145121A1 (fr) * 2013-03-15 2014-09-18 Pacific Gas And Electric Company Système et procédé de gestion de ressources d'entreprise
CN105005883A (zh) * 2015-07-22 2015-10-28 上海递道信息技术有限公司 快递物流结算系统
WO2018199736A1 (fr) * 2017-04-27 2018-11-01 Foo Yong Système et procédé de détermination quotidienne de bénéfices et de pertes afin d'améliorer l'efficacité des activités opérationnelles commerciales quotidiennes
CN110197411A (zh) * 2018-02-27 2019-09-03 重庆凌域新科技有限责任公司 一种线上服务交易平台
CN111966764A (zh) * 2020-08-20 2020-11-20 上海明华电力科技有限公司 兼容Oracle EBS和SAP系统的数据处理系统
US11393045B2 (en) * 2017-06-27 2022-07-19 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
US20220327635A1 (en) * 2017-06-27 2022-10-13 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020188558A1 (en) * 2001-05-15 2002-12-12 Nobuyoshi Morimoto Real-time accounting using wireless traffic control
US20040111342A1 (en) * 2002-12-06 2004-06-10 Juei-Mei Wang General ledger management system and method
US20050125251A1 (en) * 2000-10-12 2005-06-09 Berger Kenneth A. System and method for enterprise resource management
US7177828B1 (en) * 2000-05-02 2007-02-13 General Electric Canada Equipment Finance G.P. Method and apparatus for managing account receivables

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7177828B1 (en) * 2000-05-02 2007-02-13 General Electric Canada Equipment Finance G.P. Method and apparatus for managing account receivables
US20050125251A1 (en) * 2000-10-12 2005-06-09 Berger Kenneth A. System and method for enterprise resource management
US20020188558A1 (en) * 2001-05-15 2002-12-12 Nobuyoshi Morimoto Real-time accounting using wireless traffic control
US20040111342A1 (en) * 2002-12-06 2004-06-10 Juei-Mei Wang General ledger management system and method

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014145121A1 (fr) * 2013-03-15 2014-09-18 Pacific Gas And Electric Company Système et procédé de gestion de ressources d'entreprise
CN105005883A (zh) * 2015-07-22 2015-10-28 上海递道信息技术有限公司 快递物流结算系统
WO2018199736A1 (fr) * 2017-04-27 2018-11-01 Foo Yong Système et procédé de détermination quotidienne de bénéfices et de pertes afin d'améliorer l'efficacité des activités opérationnelles commerciales quotidiennes
CN110709882A (zh) * 2017-04-27 2020-01-17 符翁 用于确定每日损益以改善日常业务营运效率的系统与方法
US11393045B2 (en) * 2017-06-27 2022-07-19 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
US20220327635A1 (en) * 2017-06-27 2022-10-13 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
US12217317B2 (en) * 2017-06-27 2025-02-04 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
CN110197411A (zh) * 2018-02-27 2019-09-03 重庆凌域新科技有限责任公司 一种线上服务交易平台
CN111966764A (zh) * 2020-08-20 2020-11-20 上海明华电力科技有限公司 兼容Oracle EBS和SAP系统的数据处理系统

Similar Documents

Publication Publication Date Title
RU2329538C2 (ru) Вычислительная система и способ формирования аналитических данных, относящиеся к способу обработки проектных предложений и заявок
US8204809B1 (en) Finance function high performance capability assessment
US8341089B2 (en) Real estate management system and method
Bragg The controller's function: the work of the managerial accountant
CN106716459A (zh) 用于跟踪开销和计费的系统和方法
WO2011008186A1 (fr) Système et procédé à base de logiciel de gestion d'entreprise
Parmenter Pareto's 80/20 rule for corporate accountants
JP2005216013A (ja) 業務統合管理システム
US20140297358A1 (en) Eyes on control --- a novel accounting system
Bragg Lean Accounting Guidebook
Kurbel et al. ERP: Enterprise resource planning
Bragg Fast Close: A Guide to Closing the Books Quickly
Chow Implementing Microsoft Dynamics NAV
Van Vossel et al. Streamline your Manufacturing Processes with OpenERP: A Simple Approach to Manage the Manufacturing and Supply Chain Complexity
Chibili Financial Control and the Accounting Department
Namli Centralization and harmonization of financial management processes for erp implementation
Hossan Traditional accounting vs. computer-based accounting: Challenges faced by accountants
bin Yaakob et al. COMPUTERIZED ACCOUNTING SYSTEM: TRANSACTIONS PROCESSING
Chow et al. Microsoft Dynamics NAV
Powell et al. Teaching Case: Integrating Systems at We Build Stuff: Analysis and Design Case
Walther et al. The Accounting Cycle-eBooks and textbooks from bookboon. com
Hamisu The impact of ERP system on financial accounting and reporting cycles of the company. Evidence from Ghana
Rashed Analysis of VAT collection, distribution, and audit of B-Trac Technologies Ltd.
Patel Discover SAP ERP Financials
Satyanarayana et al. Advanced Financial Accounting

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

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

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载