CN111626703A - Event-recording accounting counting project management system based on item form - Google Patents

Event-recording accounting counting project management system based on item form Download PDF

Info

Publication number
CN111626703A
CN111626703A CN202010445161.7A CN202010445161A CN111626703A CN 111626703 A CN111626703 A CN 111626703A CN 202010445161 A CN202010445161 A CN 202010445161A CN 111626703 A CN111626703 A CN 111626703A
Authority
CN
China
Prior art keywords
project
module
item
management
entry
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.)
Pending
Application number
CN202010445161.7A
Other languages
Chinese (zh)
Inventor
廖大超
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.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to CN202010445161.7A priority Critical patent/CN111626703A/en
Publication of CN111626703A publication Critical patent/CN111626703A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (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)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention provides a note accounting counting project management system based on an item, which comprises a client module and a server module; the client module includes: the login module is used for realizing user registration, authentication and login; the project module is used for realizing project creation and management; the member management module is used for realizing member management; an administrator module for implementing administrator appointments and appointments; the tag module is used for realizing item tag management; an item management module for implementing item management; an account group module for implementing account group management; a statistic module for implementing data statistics; the server module is used for receiving and processing the information sent by the client module and sending the information to the client module after processing. The system can realize common event recording and accounting counting of a single person and multiple persons based on projects, can realize check, retrieval, tracing, statistics and interaction, and can complete management and auditing, team voting, financial reimbursement, marketing follow-up, customer management and customer service functions.

Description

Event-recording accounting counting project management system based on item form
Technical Field
The invention relates to a note accounting counting project management system based on an item.
Background
People often need to manage and record life events and work events in daily life work, but the professional system is too complicated to use, and meanwhile, the system arrangement and the personnel learning have higher thresholds; if the paper and pen fragments with great randomness and brain memory are used or social software, telephone and other tools are used for assisting memory, the mistakes and the mistakes are missed frequently, and the disputes are more when problems occur, so that the existing modes are all indiscreet. In summary, the invention provides an item-based event-recording, accounting, counting and project management system, which can systematically record events and management problems commonly used in daily life and work, such as event recording, accounting, counting and the like, and meanwhile, the system can simplify the process on the premise of realizing complete functions, thereby reducing the use threshold and the learning cost while completely meeting the requirements of the use functions.
Disclosure of Invention
The invention aims to provide a note accounting counting project management system based on an entry type, aiming at the defects of the prior art, and the note accounting counting project management system based on the entry type can well solve the problems.
In order to meet the requirements, the technical scheme adopted by the invention is as follows: the system comprises a client module and a server module, wherein the client module is used for receiving the event data;
the client module includes:
the login module is used for realizing user registration, identity authentication and login;
the project module is used for realizing project creation and management;
the member management module is used for realizing project member management;
an administrator module for implementing administrator appointments and appointments;
the label module is used for realizing item classification label management;
an item management module for implementing item management;
an account group module for implementing account group management;
a statistic module for implementing data statistics;
and the server module is used for receiving and processing the information sent by the client module and sending the processed information to the client module.
The event-recording accounting counting project management system based on the item type has the advantages that:
(1) the team use value is as follows: the software can be used for a working team to complete simply and efficiently: 1. the accounts required by the team are input, checked and counted; 2. information required by team management is distributed, shared and audited; 3. client follow-up, information sharing and client service work required by team marketing; 4. and counting the number of workers in team production. The method is not limited to team organization forms, and can be companies, units, individual households and employees, and also can be a family, a plurality of friends, tourist groups, associations, sales and customers, a team and the like.
(2) Personal use value: for an individual user, from the perspective of the user, besides the software can be used for completing personal record and accounting, the user can also add more projects, and through activities in different projects, information management and interaction under various scenes such as a life level, a family level, a work level, an hobby level and the like can be simultaneously completed through one software: such as work in conjunction with others to keep track of events, account, count and check, statistics, voting, customer and provider management, customer service, etc.
(3) Cost and efficiency values: the logic and the method defined by the scheme have higher implementation degree in the aspects of data consistency, timeliness, traceability, statistics and safety. The accounting method and the data display are closer to the daily thinking mode of common people who do not receive professional finance and management training, and the time cost, the learning cost and the management cost of the team in the aspects of accounting, recording, counting, piece counting, project management and customer service can be greatly reduced. Can provide remarkable benefits for multi-person cooperation and partnering projects in social activities.
(4) The value of reducing disputes and internal consumption: the data has good consistency, timeliness and traceability, and can greatly reduce the cooperation dispute of personnel.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 schematically illustrates a system block diagram of an item-based memo billing accounting project management system in accordance with one embodiment of the present application.
FIG. 2 schematically illustrates a diagram of essential basic attributes for an entry of an entry-based memo counting project management system according to one embodiment of the present application.
FIG. 3 schematically illustrates a diagram of a statistics template for an item-based docketing count piece item management system according to one embodiment of the present application.
FIG. 4 schematically illustrates a diagram of a statistics template for an entry-based docketing count piece item management system according to one embodiment of the present application.
FIG. 5 schematically illustrates a diagram of a statistics template for an entry-based docketing count piece item management system according to one embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings and specific embodiments.
In the following description, references to "one embodiment," "an embodiment," "one example," "an example," etc., indicate that the embodiment or example so described may include a particular feature, structure, characteristic, property, element, or limitation, but every embodiment or example does not necessarily include the particular feature, structure, characteristic, property, element, or limitation. Moreover, repeated use of the phrase "in accordance with an embodiment of the present application" although it may possibly refer to the same embodiment, does not necessarily refer to the same embodiment.
Certain features that are well known to those skilled in the art have been omitted from the following description for the sake of simplicity.
According to one embodiment of the application, a system for managing event-keeping accounting and event-counting project based on an item is provided, which comprises a client-side module and a server-side module.
According to one embodiment of the present application, the client module of the itemized bookkeeping count event management system comprises:
the login module is used for realizing user registration, identity authentication and login;
the project module is used for realizing project creation and management;
the member management module is used for realizing project member management;
an administrator module for implementing administrator appointments and appointments;
the label module is used for realizing item classification label management;
an item management module for implementing item management;
an account group module for implementing account group management;
and the statistical module is used for realizing data statistics.
According to one embodiment of the application, the server-side module of the entry-based memo counting project management system is used for receiving and processing the information sent by the client-side module and sending the processed information to the client-side module.
According to one embodiment of the application, the project module of the itemized bookkeeping counting project management system further comprises a sub-project module for realizing sub-project management.
According to one embodiment of the application, the project module of the entry-based memo count event project management system is further used for setting, modifying, destroying, deactivating and displaying project units and management information, project introduction information, project creation time information, project content information, project authority information, project members, project tag information and sub-project information.
According to one embodiment of the present application, the destruction and deactivation functions of the project module of the itemized bookkeeping count project management system are displayed only to the project administrator.
Voting is carried out when destruction is carried out, and voting is terminated if an administrator carries out operation against destruction at the client.
According to one embodiment of the application, the member management module of the entry-based memo counting project management system identifies whether each member is the same person according to the phone number at the time of registration.
According to one embodiment of the application, the client module of the itemized event-keeping accounting event project management system further comprises an interaction module for realizing the establishment and disconnection of interaction of project members.
According to one embodiment of the application, the tag module of the itemized bookkeeping counting project management system is used for selecting, adding, viewing and modifying project tags.
According to one embodiment of the application, the item management module of the item-based memo accounting counting project management system is used for realizing the following functions.
Creating an item, selecting an item type, selecting an occurrence time, selecting an item to which the item belongs, selecting a tag to which the item belongs, selecting or inputting an element, and adding or subtracting an account group;
the content, remark, modification record information, entry voting form record and entry log display, visibility operation and stamping operation of the entry;
the operation of entry table state includes three options of support, non-support and question;
and (4) commenting, invalidating, withdrawing and deleting the item.
According to one embodiment of the application, the accounting group module of the itemized bookkeeping count item management system provides six basic combined account group statements and two composite combinations.
According to one embodiment of the application, the statistical module of the item-based memo accounting counting project management system is used for managing and displaying the internal and external member logic related to the sub-projects and the screening conditions of statistical samples;
the statistical module is used for counting the information in the project and counting according to the screening conditions, and the statistical result is stored as a statistical item or exported to a file.
According to an embodiment of the present application, a systematic introduction description is given below for the specific implementation and the noun definitions of the itemized event-keeping accounting project management system:
the first item:
1. the internal structure of the project is as follows: the method comprises the following steps: the following attributes or data are under the project, described in the following, respectively: 1. a project member; 2. item entries; 3. an item label; 4. child items (internal structure consistent with parent items, thus enabling multi-level item nesting); 5. item units; 6. configuring member authority; 7. there may be other conventional attributes and may be extended as appropriate, non-method core content: item introduction, item rights, etc.
2. And (3) project establishment: the user can create a new project, define the project name by himself, and automatically become the first administrator of the project. Other items may also be added and become members of other items.
3. Adding items: the administrator may add other members to the project. A user can join multiple items simultaneously.
4. Items can be destroyed: all project managers, after agreeing to destroy the project, clear all data of the project. The components are resolved.
5. The item may be deactivated: the items after being stopped can only be viewed, and data cannot be added.
6. And (4) sub-item: sub-items may be built under the item.
(1) The administrator of the parent and child items forces consistency: an administrator designated as a parent also automatically becomes an administrator for all children. The parent project administrator is given charge, and all child project administrators are given charge automatically.
(2) The members of the parent and child items may be inconsistent: if it is only a member of the parent item and not a member of the child item, the content of the child item is not visible. Otherwise, only the members of the child item cannot see the content of the parent item.
(3) The label of the parent project can be used by the child project. But the tags of the child items cannot be used by the parent item.
II, item members:
1. under one project, there may be one or more project members (called members for short).
2. According to the relationship between the members and the project, the method can be divided into an inner member and an outer member:
(1) inner member: project insiders, partners, employees, and project subject, account, warehouse, etc. should be added as inside members.
(2) Outer member: project customers, suppliers, temporary personnel, and other external business partners, or business logic belonging to external accounts, etc., should be added as external members.
(3) The classification according to whether the member is associated with a real registered user can be divided into a real user member and a virtual member:
(4) real user member: i.e., the member is associated with a registered user of the system.
(5) Virtual member: the member is not associated with a system real registered user. Or even just a name. Thus, members of the project will allow addition of bank accounts, unknown payees that are not registered with the system, and any virtual accounting subjects, headings, warehouses, etc., to be added as virtual members of the project.
The method comprises the following steps: if the project member fills in the contact information, the system will scan the user database, if the contact information is consistent with the contact information of a registered user, the member will be automatically marked as a real member. Otherwise, the project member has no contact address or the contact address is not consistent with any registered user, and the member is a virtual member.
The method comprises the following steps: the members in different projects judge whether the two members refer to the same person (or the same object, etc.) in real life according to the following rules according to the contact telephone:
(1) if the contact calls are consistent, the method judges that the two members are the same person: for example: the contact telephone of a member in the project A is 888, the contact telephone of a member in the project B is 888, and the system considers that the two members are the same person in real life whether the names of the members in the projects are consistent or not.
(2) If none of the contact phones are filled in, even if their member names are identical, then the two virtual members are considered to be different people: for example, if the parent item has member "zhang san" and its contact phone is empty, and the child item also has member "zhang san" and its contact phone is empty, the system considers that "zhang san" of the parent item and "zhang san" of the child item are not the same person.
(3) The member's contact phone may or may not be filled, and if filled, under the same item (the sub-item is also considered as a different item), the phone of any two members is not allowed to be identical, and if a member of the same phone is added, the member phone is prompted to exist in the item.
(4) These decision rules may be manifested in certain filters or statistics. This is particularly important in the parent-child project hierarchy. For example: if the system is to determine that the "company account" of the parent project and the "company account" of the child project are the same account, the unique method assigns the same telephone number, for example, one telephone which is optionally identical but is called 222.
3. The classification can be divided into interactive members and non-interactive members according to whether the members can participate in the project activity.
(1) And (3) interaction members: the item can only establish an interactive state with a real user member. After interaction, the user associated with the member can see the content which the member has the authority to view in the project after logging in, and can also participate in various activities such as note and account keeping of the project within the authority range.
(2) Non-interactive members: and corresponding to the interactive members, the members which do not establish the interaction are in a non-interactive state. All virtual members can only be non-interactive members. The real user members who do not establish the interactive state are also non-interactive members. Non-interactive members exist only as the roles of accounting the project, selecting the number of the first party, the second party and the third party (the receiving and paying parties) and carrying out business in statistics. If the non-interactive member is a real member, the user associated with the non-interactive member cannot sense any content in the project, and even the project name cannot be seen. All is project-wise unilateral.
4. According to the authority of the member: the members are divided into managers and common members:
(1) the administrator: the administrator has the right to manage the project. Only if the member is an internal member and an interactive member at the same time, the member administrator is possible.
(2) Common members: corresponding to the administrator, other members which are not the administrator are ordinary members.
Appointments and appointments of administrators:
(1) the user creates a new project and automatically becomes the chief manager of the project.
(2) The method provides that: there may be multiple administrators, and an incumbent administrator may promote other interactive, real, in-person members to an administrator. This is also the only way to become an administrator, in addition to automatically creating a leader for the new project.
(3) The only way to relieve the administrator is for the administrator to click the task-off function and then change the task-off function into a member in the common interaction. In the actual production life, other administrators should give up themselves after negotiating with the administrators. If the administrator is an item only administrator, then the disbursement is prohibited.
(4) The rights of multiple administrators of the project are equal. Some partner projects may share an administrator to ensure that data is not left or right by one party. For significant transactions within a project, multiple administrators may implement a voting scheme, with all consent to pass. If any party does not agree, the current status is maintained. Such as item destruction, item deletion.
(5) The method comprises the following steps: the appointments or dismissals of the parent project administrator are automatically made or dismissed as well as the child project administrator, i.e., the child project and administrator are in strong agreement with the parent project administrator and are automatic.
5. According to the member aging state: the method comprises the following steps of (1) dividing into normal members and historical members:
the member with authority can delete other common members in the item. When a member is deleted, the member can only be converted into a history member. The meaning of the existence of a history member is to leave the item that previously referred to the member unaffected. But also allows the project customer data not to be substantially lost. But the newly added entry will no longer be related to the history member. The member with authority can also restore the history member to a normal member. When an entry is newly entered, the history member will no longer be selected.
6. Member attributes: the most important and fundamental attributes are the item to which it belongs, the name within the item, and the contact phone.
(1) The method comprises the following steps: the item to which the member belongs is marked. This item cannot be left blank.
(2) The name in the project is as follows: may be consistent with a user nickname. Or may be non-uniform. This item cannot be left blank.
(3) And (4) contacting the telephone: when the interaction is established, the system searches the contact telephone registered by the registered user according to the telephone. Members in different projects, if their contact phones are the same, the system decides that the two members are in the same person (or account, etc.) in real life. The phone, unlike the other, is not necessarily the same person or account in real life. If the phone is left blank, the member and all members of all projects are determined not to be the same person in real life (even if the names in the projects are the same, the calculation is not carried out), and the judgment rule generated according to the phone is reflected during statistics or screening.
(4) There are other necessary attributes: such as member introduction, member tag, member join time, etc., more attributes may also be extended.
7. Authority of each member:
authority of administrator: the administrator has all the rights of the members within the normal interaction. The management rights of the items are as follows: (1) changing project names, changing project introduction, adding and deleting labels in projects, adding and deleting members, changing member types and attributes, enabling projects to be interacted with members or disconnected, disabling projects, initiating destruction of projects or participating in destruction of projects voting, modifying contents or attributes of all projects in projects, initiating deletion of projects or participating in deletion of projects voting, invalidating or cancelling all projects in projects, managing project counting units, counting projects, and exporting projects to other format file backups. (2) The same project management rights as described above are given to sub-projects. (3) The expanded project can manage the function, and the administrator can be authorized to use the function. (4) The administrator can also appoint a new administrator, and can assign single item management authority to other members: such as managing count unit rights, statistical rights, exporting backup rights, etc. (5) If the administrator is not the only administrator for the project, the administrator may be given the responsibility of the administrator. After unloading, the member is automatically converted into the interactive member. (6) The administrator cannot directly quit the project, and only the administrator is given charge and then quits the project by the identity of the member in the interaction.
The non-interactive member does not have any rights to the item.
Member authority in common interaction: (1) all entries within the project may be viewed by default. Except that the entry publisher, at the time of publication, has masked the member alone. (2) The settings, tags, members, rights assignments, etc. for the item may be viewed. But if not a member within a particular sub-item interaction, the sub-item is not visible. (3) Entries may be published under the project and self-published entries may be withdrawn within a defined time (e.g., 10 minutes). If the items released by the self are not modified by any administrator, the self has the right to modify. If the modification is modified by the administrator, the modification right is lost. (4) The items released by the users or modified last by the users have the right to initiate the deletion right and participate in the deletion voting right. If the administrator initiates a delete vote, if the entry is self-issued or last modified, then it must also be self-agreed that the delete can be followed. Deletion is also terminated if the user disagrees with the information. (5) The entries released by themselves or modified last may be invalidated, and after invalidation, may also be authorized to be cancelled. The entry is invalidated or cancelled by the administrator, and the revocation (or cancellation) rights are lost. (6) Comments, replies, votes may be reviewed within the entry that is entitled to see. The delivery of the item can be viewed. (7) The single administrative right may be exercised if assigned certain administrative rights by an administrator. (8) The member in the interaction can select the exit item, and after exiting, the member is converted from the member in the interaction to the member in the non-interaction. The member will no longer be able to see everything about the item. But the data of the project party relating to the member is not affected.
General interaction outsider authority: (1) by default, not all of the contents of the item can be viewed: including items, settings, tags, members, etc. But some of the specified entries can be seen, namely: when an entry is published, the entry is specifically designated to allow the interactive outsider to view, and the entry can be viewed by the interactive outsider. (2) The name of the item can be seen, as well as its name and identity within the item. (3) The entry delivery can be reviewed, replied to, voted for, and viewed within the entry that is allowed to be seen. (4) The interactive external member can select the quit item, and the interactive external member is converted into the non-interactive external member after quitting. The member will no longer be able to see everything about the item. But the data of the project party relating to the member is not affected.
8. Addition, deletion and modification of project members:
(1) the project administrator can add, delete, and modify members of the project (including insiders and outsiders).
(2) Members within an item interaction may add, delete, change members outside the item by default (except where specifically prohibited by the administrator).
(3) Adding members: when adding, the name of the member in the project can be directly input. Optionally, contact phone calls and other data (e.g., member tags, member notes, etc.) can be filled in.
(4) The default is a non-interactive state after adding a member.
(5) And (3) interaction is established: the member with authority can establish an interactive relation for the non-interactive member of the project, when the interaction is applied, the user is searched for the phone to be registered consistently, and if the user cannot be found, the user is prompted that the phone is not registered and cannot interact. If the user finds the user, the user can establish interaction after the user needs to be informed by the member.
(6) Disconnection interaction: the member can click to exit the project by himself, thereby breaking the interaction with the project. The member with the authority in the project can also disconnect the interaction state of other members. Become non-interactive members after disconnection.
(7) And (3) deleting members: the member with authority can delete the member and becomes a history member after deletion.
(8) And (3) recovering history members: the member with authority can restore the history member to a normal member.
(9) And (4) contacting the telephone: the authorized member can modify the contact telephone of the project member, but the interactive member must disconnect the interaction before modification because the contact telephone with the interactive member can not be modified.
Thirdly, item classification labels:
1. under the item, a plurality of classification labels, hereinafter referred to as labels, can be established.
2. The tags are of the following types:
1) inner member label: may be associated with the inner member to group the inner member for easy retrieval and viewing.
2) Outer member label: may be associated with the foreign member to group the foreign member for easy retrieval and viewing.
3) Note tag: can be associated with the event record type entry to facilitate searching and viewing the event record entry.
4) Account number labeling: may be associated with the account type entries to facilitate retrieval and viewing of the account entries.
5) Stamping a label: can be associated on all types of items, can be used to display all items marked, and facilitates retrieval and viewing of items. The most characteristic of the seal is that all entries are available. The memo tag and the account tag only can be used for memo entries or account entries.
3. Label add \ change \ disable \ restore:
2) the system may define some common tags that are present in all items and may be used directly.
3) The authorized members can add tags to the item that are only used within the item.
4) In the project, the same type label and the same name are allowed to be established only once. Nor can it be the same name as a system public label.
5) Authorized members may modify the tag name.
6) The tag cannot be deleted and can only be deactivated. The authorized member may deactivate or restore the tag. After the tag is deactivated, the entry previously used for the tag will not be affected, but the newly entered entry will not be able to reuse the tag.
Item four
1. Item: are the fundamental data elements of the method for storing or retrieving data. The core rules and functions of the method are implemented on an item basis.
2. The record keeping and account content recorded by each user are arranged into items with a uniform format and are firstly stored in the server. The client obtains the items which the user has the right to check from the server through the network according to the items which the user belongs to and the read-write authority in the items. Entries may also be added to the item to which they pertain by the client.
3. Item base attributes: the method provides that the basic properties that the item must possess are shown in fig. 2. Depending on the type of item, these attributes must be available, vacant, and selectable. Finally, the items with uniform format are formed, so that the items with different types can be stored together, and the attributes can be used for screening, indexing, counting, sorting and the like. In practical use, more attributes can be expanded on the basis of the attributes, the item format can refer to but is not limited to the format of fig. 1, and the various attributes need to be fully and clearly shown:
(1) time of occurrence (mandatory): for marking the event to which the entry refers to event/account/count the time that this real life event occurred. May coincide with the recording time or may specify a time. When the client displays, if the difference between the recording time and the designated time is large, the item can be marked as a 'supplementary note' or 'supplementary note after xx days'. So as to check the timeliness of the record.
(2) Entry type (mandatory): for marking item types, there can be only one type per item. Possible type values include at least the following:
(1) basic types:
A. note entry
B. Account entry
(2) The extension type is as follows: on the basis of basic types, some attributes can be expanded to have richer functions, and the method defines two expansion types:
A. entry of the project log: the event record item is an extension of the event record item, and is automatically generated when a heavy event with a heavy class is set and modified in the project so as to realize the traceability of the project content.
B. Entry of statistical report: the link of a statistical report is attached to the extension of the note entry, so that the statistical report can be stored for subsequent reference.
C. In practical systems, some more types can be extended: such as system notifications, schedules, approvals, documentary entries, photographic entries, etc
2) The items (essential) are as follows: for marking the item to which the item belongs.
3) The tag is (optional): the items may be tagged with a series of tags to mark the category, nature, of the item.
4) Visibility of inner member (mandatory): default to all members within the project, but may also individually specify which members are to be seen by the entry, or not.
5) Extrinsic visibility (mandatory): none of the default outsiders are visible, but the entries may also specify individually which outsiders are visible.
6) Account group (account entry is indispensable, note entry is vacant): there must be one to more account groups in the account entries. Each accounting set describes a specific accounting, counting or piece-counting transaction. The note class entry is vacant. Each account set, consisting of 8) -14) of these properties defined flexibly:
7) account number a party (account number requisite): the value of this attribute must be one of the members of the project in which the item is located and the system will automatically provide an "outside other" alternative member to represent the unknown outside payee. This is indispensable in all account sets.
8) Account action one (account group required): this attribute defines the first action of the accounting or counting. This is indispensable in all account sets. The method defines the following seven alternative values (or the same meaning): (1) non-loan payment (2) non-loan receipt (3) return type payment (4) due (or owed, or borrowed) (5) count increase (6) count decrease (7) generation (collection or payment type), wherein 1-6 are basic actions, and 7 is a compound action. In practical implementation systems, it is allowed to extend more optional values.
9) Account b (as determined by the account action, either mandatory or absent): this is not the case when the value of "accounting action one" is "count up" or "count down", and the attribute is not the case when it is other values. The value of this attribute must be one of the members of the project at which it is located and the system will automatically provide an "outside other" alternative member to represent the unknown outside payee.
10) Account action two (depending on the account action one, either mandatory or absent): this attribute defines the second action of the accounting or counting. This is indispensable when the value of "billing action one" is "generation (collection or payment type)". This is a gap for other values. This term must be one of the following two values (or the same meaning): (1) non-loan payment (2) non-loan receipt.
11) Account number three (mandatory if the account number has action two, otherwise blank): the attribute defines the object of the second action of the accounting or counting. This is indispensable when the value of "billing action one" is "generation (collection or payment type)". This is a gap for other values. The value of this attribute must be one of the members of the project at which it is located and the system will automatically provide an "outside other" alternative member to represent the unknown outside payee.
12) Account number (account number mandatory): the item is indispensable, must be greater than zero, can take the decimal.
13) Account unit (account is mandatory): the default unit is "element", and any custom unit can be input. However, if the unit is a currency unit such as "Yuan", the account set is an account. If it is other unit, the account is a count or piece of count.
14) Stamping (optional): the authorized member may tag the entry with a stamp. The stamp label should be visibly marked to facilitate a one-glance identification of some aspect or category of this entry. An entry can only have one stamp at a time. Can be vacant.
15) Content or notes (mandatory): account entry, this attribute is the remark of account; if the attribute is event record item, the attribute is event record content.
16) Primary record information (mandatory): some initial information is stored, including the actual recording time of the entry, the recorder and the like. The item is automatically generated when the entry is first recorded and cannot be modified any more. This attribute is indispensable.
17) Modification information (necessary if modified): modification information for marking an entry. An entry is empty if it has not been modified. If yes, the last modification time and the last modifier information are saved, and the number of modifications is accumulated. This item is automatically generated when the item is modified.
18) Delivery situation (mandatory): the member who has the right to view the item can view the delivery condition of the item to other members.
19) Entry table result (automatically generated with table): each entry allows a member to express at least three attitudes of support, objection and question for the entry, which are described in detail in the entry table function description.
20) Entry log (automatically generated due to member operations): for recording some necessary information generated in the interaction, recording, modification, etc. of the item. The information in the entry log plays a role in playing a key role in the purpose of the method. The following definitions are given for the entry log:
(1) the entry log is divided into: a formal log, a modification log, a comment log and a deletion voting log. Allowing more types of entry logs to be extended. The generation and content of various logs are described in the functions of the entries: item modification, item form, item review, item deletion.
(2) The entry log may not be modified. Can only be automatically generated by the system according to the method definition. Only entries that are voted for deletion will be deleted together.
(3) Members who have access to view entries all have access to view their entry logs.
(4) When the content of the item is displayed, all the item logs of the item should be displayed in time sequence.
21) On the basis of the above basic attributes, in the specific implementation, the item is allowed to be extended by some attributes: such as attachments (files, pictures, recordings, etc.), reminder alarms, type-in location, links, etc.
3. And (4) storing the items:
all entries should be stored first at the server side, and database storage is the preferred method. When the server receives the request of the client, the server synchronously distributes the items which the current login user of the client has the right to see to the user. If the client side has technical conditions, a copy of the item which the user has the right to view is stored in the local (local cache) of the mobile terminal, so that the experience is improved, and the pressure of the server is reduced. The latest entries and their additional information are obtained to the server by push, trigger or timing synchronization. The cache is forced to be consistent with the server data. And if the data are inconsistent, the server data is taken as the standard.
5. Entry input:
the user uses the network-connected client device to enter each attribute of the item through a mobile phone program or a computer program meeting the definition of the method, and stores the item data in the server through the network by using the server program of the method arranged on the server. The server simultaneously distributes the entry to other client users who have the right to see the entry.
6. Item retrieval:
1) the user may retrieve the item by any attribute or attributes of the item. Such as: only items specified, types specified, tags specified, members specified, time specified, or items searched for specified content may be viewed, and so on.
2) If the client device has a local cache entry, the entry retrieval should be preferentially performed in the local cache. Therefore, when the device is off-line, the reading content can not be influenced.
7. Item modification:
1) the entry may be modified. The method provides, however, that no modification of the item to which the entry belongs is allowed. After the entry is recorded, a recorder can hide the once-recorded entry by modifying the belonged entry, so that the traceability of the entry content is lost.
2) All administrators of the project, entry logger, last modifier of the entry (if any) have modification rights. After the project manager modifies the entry, the recorder of the entry, and the last modifier before (if any), lose the modification right.
3) When the entry is modified, the system automatically saves an entry modification log in the log of the entry.
4) Entry modification log: the entry modification log should save a snapshot of the content before modification, the person of the modification, the time of the modification, and where the modification was made. And when viewing the modification log, the complete content of the entry before modification can be restored. To ensure traceability and verifiability of the item modifications.
8. Entry table state:
1) members who have the right to view the entry can perform the tabulation of the entry. The formal value has at least three values: approval (or approval, support, etc.), disapproval (or disapproval, etc.), and doubt (or unclear, not understood, etc.). And a table remark can be input in the table.
2) The members who have the right to view the item can view the state condition, the state time, the state remark and the state log of other members to the item.
3) The same member can repeat the form, and the subsequent form opinion replaces the previous form opinion, but each form will automatically generate the form log.
4) A formal log: including the statement opinions, the statement persons, the statement times and the statement remarks. The form log can clearly reflect the history and the change of the repeated forms of the member. The form of the member is traceable and verifiable.
5) When viewing the entries, the last morphological case should be presented. A list of various form values, and a percentage of the number of various forms.
6) After the entry is modified, the entry table result is cleared. But the formal log in the entry log should be preserved.
9. Item review:
1) the members who have the right to view the item can comment on the item and can reply the comment of others on the item.
2) All comments are saved in the entry log in the form of a comment log.
3) And (4) commenting a log: commentators, time of commentary, content of commentary, and responses to whom, if any, should be included.
10. Invalidation, or cancellation of entries:
1) any time after the entry is published, it may be invalidated, or the invalidated entry may be invalidated. The overriding nature is to modify the entry. The attribute of validity of the entry is modified.
2) Members having the right to modify an item may invalidate an item.
3) Invalidation should generate a modification log. But instead of saving the modified snapshot, a textual description may be used, such as: somebody has invalidated or cancelled the entry at some time.
4) The invalidated entry can still be viewed from the original content. But should mark significantly that the entry has been invalidated (e.g., by adding a strikethrough to the contents of the entry).
5) The invalidated entry will be excluded from subsequent statistics.
11. And (3) item revocation:
1) the entry may be revoked within a defined time after publication. (to ensure the traceability of data, the method is recommended to be used as a rescue measure after the publisher misoperates and missends sensitive information within 10 minutes.)
2) Revocation can only be revoked by the publisher itself.
3) After revocation, all members will no longer be able to see the content before revocation. The content of the item is replaced by "this item has been revoked" (or the same meaning).
4) The revoked entries will not be able to be modified, formalized, commented on, and not counted. Revocation of entries does not necessarily generate an entry log.
12. Item deletion:
1) entries are allowed to be deleted after a vote passes.
2) The method defaults to stipulate: entry is deleted only if the entry logger, last modifier (if any), and all administrators of the project agree. If any person object to the system, the voting is deleted and the system is maintained. If only one person item exists, the items are inevitably satisfied at the same time, and the only one person item is also meant, and the items can be deleted at will. In practice, the project manager is allowed to add additional members needing to agree in the project setting according to the actual situation of production and life.
3) And (3) initiating deletion: members with authority to participate in the deletion vote may initiate the deletion vote for an entry.
4) After the deletion is passed, the substantive content of the entry and all entry logs are deleted. And does not provide a recovery function.
13. Entry:
1) when the entry is carried out, the accuracy, convenience and data consistency of the entry attribute of the entry are provided as much as possible. For example: the principle of multiple selection and less input should be followed.
2) Members and administrators within the project interaction may enter entries into the project.
3) The entry type, the entry belonging item, the belonging label, the account group A, B and C, the account group action, the previously used account unit, the seal and the member visibility list are all input in a selection mode. To ensure error-free and quick. A
4) The entries of the project log, the modification log of the entries, the log of the entries, etc. should be automatically generated and saved by the client or the server. Some non-input attributes of the item should be automatically filled or left blank according to the rules of the method.
5) When the member or the tag is selected, a quick search function is supported, so that when the selectable items are excessive, the member or the tag can be quickly searched through the member name, the member tag name, the member telephone and the like.
14. Item display:
1) at the client, the entries that can be seen by the currently logged-on user should be retrievable and readable. And should provide convenient search, retrieve, sort, search function according to various attributes.
2) The entries should be displayed in order of occurrence by default.
3) The concept of "additional recording" should be provided, the recording time is delayed from the entry occurrence time, and additional character samples are marked to improve the timeliness of recording in the project management. And provides assessment convenience for project managers.
4) The item display may be directly in text typesetting. But for clarity and order, the defined elements of the item should be displayed as completely as possible. Attributes that do not create ambiguity or vacancy may be simplified or omitted.
Fifthly, accounting counting method:
1. the method sets up a relatively complete accounting counting method on the basis of the items, the projects and the members. The system can simulate activities such as bookkeeping, counting, piece counting, returning, goods delivery and the like in daily life and production completely, the thought is close to common people daily life thinking, professional accounting knowledge is not needed, accounts can be processed easily, and meanwhile, derived data are supported to be used as original data to be analyzed and processed in the next step.
2. First, the method considers the account number to have three properties: counting increase and decrease property, non-borrow and return balance property, borrow and return property:
(1) counting increase and decrease property: entries recorded by the account actions "count up" and "count down" are both of this nature. Such properties are used to simulate situations that appear directly, or disappear directly, in productive life: for example, the running mileage is increased, the integral is increased or decreased, the product is produced, or the product is scrapped or lost;
(2) non-loan balance property: the entries recorded by the account actions "not borrowed for" and "not borrowed for" are both of this nature. Such properties are used to simulate the transfer of money or material from one party to another in productive life, but without regard to the recovery: if the sales generate income, the money of the goods is not considered to be returned to the opposite side; and when the goods are purchased, the money is not considered to be collected, and the donation is the same.
(3) Borrowing and returning properties: entries recorded by the account action "return type pay" and "due (or owed, or borrowed)" are both of this nature. Such properties are used to simulate the transfer of money or things from one party to another in productive life, and are the case of return or to be withdrawn: the borrowing and the transferring of the money in two opposite directions can be balanced out, and after the balance is balanced out, the net borrowing and returning is 0 which is the state pursued by the borrowing and returning business.
(4) The method is defined by the three types of account properties, and divides common account business of life and production into three completely independent types. The data of these three properties, even if the units are the same, should be counted independently. And cannot be accumulated with each other, the mutual accumulation is considered to be meaningless by the method. These rules are also a more central part of the method. In the accounting transaction in the actual production life, people often pay attention to the three types of numbers: if the number of products is produced (the counting and increasing property), the number of sales is generated, the cost is spent (the non-borrowing and returning property), the number of the people owed by the person and the number of the people owed by the person (the borrowing and returning property). These three types of data are summarized separately, but not accumulated with each other.
3. The account group concept: as described in the previous entry attribute, there may be one to more account groups for an account entry. The same activity or business can be decomposed into a plurality of accounting groups to summarize and record accounting counting and charging and discharging behaviors. The account group is an understandable sentence formed by flexibly combining a plurality of elements including a party A, a party B, an amount and a unit. To express the corresponding billing count transaction. And the attributes of the combinations are stored separately during storage, so as to facilitate analysis and retrieval.
4. Account set basic combination statements: the method defines the following basic account combination statements:
(1) party A + (not borrowed) pay + Party B + quantity + units: the combination is used for recording the activities such as purchase payment, goods delivery and donation in daily life and production without returning of the other party, the unit is currency to indicate that the first party pays the money of the second party, and the unit is goods or other units to indicate that the first party delivers the goods of the second party, and the like.
(2) Party A + (not yet borrowed) receives + Party B + quantity + units: the combination is used to record the activities of sales collection, goods received after purchase, donations received, etc. that do not require return to the other party. The unit is currency which indicates that the first party receives money of the second party, and the unit is goods or other units which indicate that the first party receives goods of the second party, and the like.
(3) Party A + (Return) pay + Party B + quantity + units: this combination is used to record the return arrears. The unit is currency to indicate that the first party returns money to the second party, and the unit is goods or other units to indicate that the first party returns goods to the second party, and the like.
(4) Prescription A + due (or owed) + prescription B + quantity + unit: this combination is used to record the act of debiting the loan. The unit is currency to indicate that the first party deals with the money of the second party or the second party borrows the money of the first party; the unit is goods or other units which indicate that the first party deals with goods of the second party or goods of the second party are borrowed by the first party. (Note that the first party deals with the second party, the first party owes the second party, and the second party borrows the first party, expressing that the two parties are the same meaning in fact.)
(5) Prescription a + increase in count + number + unit: this combination is used to record the case of a direct addition of a count, piece count class. Such as an increase in running mileage, an increase in the number of workers produced, and the like.
(6) Prescription a + reduction in count + number + units: this combination is used to record the case of direct reduction of count, piece count classes. Such as a reduction in body weight, loss of product, damage, etc., a reduction in remaining tasks, etc.
5. Account group composite combination statement: by a compound statement, his business logic can be split into multiple base statements. But compound sentences are more convenient and intuitive and are easier to understand. The method defines two compound combined sentences which can be directly used, and the system for realizing the method can expand some compound sentences which can be more.
(1) Party A + Party B + (not borrowed) are paid + Party C + quantity + units: the combination is used for recording the behavior of paying money or things of the third party by the first party and the second party. This compound statement is associated with: the superposition equivalence of two basic combinations of 'Party A + (not borrowing) paying + Party C + quantity + Unit', and 'Party B + due (or owing) + Party A + quantity + Unit'. For example, the combination can be used to record the reimbursement costs paid by the employee: such as a 100 dollar fee paid by an employee agent to the taxi driver. The resolution means that: the employee pays the taxi driver 100 dollars while the company deals with the employee 100 dollars.
(2) Party A + Party B + (not borrowed) receive + Party C + quantity + units: the combination is used for recording the behavior of the Party A and the Party B receiving the money or the things of the Party A and the Party B. This compound statement is associated with: the 'Party A + (No borrowing) receives + Party C + quantity + Unit', and the superposition equivalence of two basic combinations of 'Party A + due (or owed) + Party B + quantity + Unit' is realized. For example, the combination can be used for recording the behavior of collecting the goods by employees: such as an employee agent receiving 10000 dollar money from a customer. The resolution means that: the employee receives 10000 dollars for a customer while the employee deals with 10000 dollars for a company.
6. A plurality of account groups: within one account entry, more complex cases can be described using multiple account groups, exemplified by the following direct list of several examples:
example 1, when buying the product B, the first party needs to pay 90 yuan, the first party pays 100 yuan, the second party needs to make up 10 yuan, but the second party has no change, and then the agreement is paid down for account first and then settled. Two sets of accounts can be used to describe within one entry:
[1] paying 100 yuan to B
[2] 10 Yuan for B (or owe) A
And the specific matters and circumstances are explained in the remarks.
Example 2: a sells 4 tons of cement to B, and receives the cost of 1200 Yuan. This delivery and collection transaction, if required to record both goods and money, can be described in one account entry using the following two account sets, and using the custom unit "ton cement" directly:
[1] the first (non-borrowing) gives the second 4 tons of cement
[2] Receiving B1200 yuan by A (non-borrowing and returning)
And the specific matters and circumstances are explained in the remarks.
Example 3: the E-vinyl butyl has invested a shop together, each 25% share, the rent of this month is 10000 ten thousand, should each person divide 2500 yuan by reason, but for convenience, this rent is collected by the A, however, the round trip between the E-vinyl butyl is frequent, this one more than, so they adopt the way of checking the account regularly and settling accounts, so when the A receives the rent, this account should be paid down first, can describe this business by following several basic combinations:
[1] the first (not borrowing) receives other 10000 yuan
[2] 2500 yuan for A (or B) treatment
[3] Jia cong (or owing) third 2500 yuan
[4] 2500 yuan for Jiaying (or owing) Ding
And the specific matters and circumstances are illustrated in the remarks, note that where "external other" is used herein, the system will provide a common alternative to "external other" without the need to remember other acquirers.
Example 4: the first owes 10000 Yuan from the second, the second needs to urge the first to return because the fund is needed, and the first has no money to return at present, so borrows the third, and directly transfers 10000 Yuan from the third to the second party after the third agrees, and then the first owes 10000 Yuan. This is a logic for returning class a to class b 10000 yuan, which can be recorded as follows:
[1] the first (return) gives 10000 yuan to the second
[2] A copes with (or owes to) C10000 yuan
And the specific matters and circumstances are explained in the remarks.
7. The unit of account number:
(1) the method extends the recording range from accounting to the keeping of belongings or numbers through the flexibility of units.
(2) The method considers that the account numbers of different units do not have any correlation, and the account numbers cannot be accumulated mutually in statistics and are completely independent.
(3) The method defaults to using common currency units, such as "dollars" as default units, but any other unit may be selected and entered: such as "ton", "kilometer", "worker day" etc., for the convenience of explaining the material, can bring the material name behind the unit, have better readability: the effect of taking "ton of cement" as a unit directly: "Jia Fang (non-borrowing) gives xx tons of cement to second party. "
(4) The monetary units are used, meaning that this accounting set is accounting. Non-monetary units are used, meaning that the account set is a note, count or piece of note.
(5) The system for realizing the method can automatically record the user-defined unit used by the project and can select the user-defined unit in the next account record of the project. Later when the administrator modifies the used units of the project, the items previously related to the units should not be affected.
Sixthly, an account number statistical method comprises the following steps:
1. the system implementing the method should have a statistical function. The specified set of items may be counted and presented as follows.
2. And (5) counting results: the method defines the result data to be counted and defines the statistical result reference format of the text version, which can also be tabulated and graphed. But the data to be expressed should be the same. It also allows the results to be extended. As shown in fig. 3 to 5, below, on the left, there is a reference format and on the right, there is a numbered note explaining the logic and definition of the terms:
3. and (3) counting:
(1) first, a range of items to be counted should be specified. And statistics should be limited to a certain item (which may include its sub-items), and then the set of items that it screens out may be screened or searched according to specified conditions as a statistical sample.
(2) Secondly, all the account groups of the related items are analyzed one by one, the composite combined statement is divided into a plurality of basic combined statements, and then the analysis is carried out. And according to the method, corresponding unit parts, various secondary items (overall items, member items and label items) and tertiary items (one-to-one member items under the member items and member items under the category under the label items) are searched (not generated). In each term, there are one to more "statistically summarized terms". And according to the analysis result of the item, carrying out accumulated addition, subtraction or refreshing on each item of data of the statistical summary items to finally obtain accumulated numbers. The statistical work is preferably done at the client side to save server computational resources. When an item is analyzed, if a hurdle item or summary item does not already exist, one is created immediately.
(3) And displaying the statistical result according to a reference format or other formats.
(4) Item analysis and statistical methods: during statistics, the composite account number combination statement is divided into basic combination statements and then participates in analysis, the analysis and statistical method of the basic combination statements is as follows, for convenience of description, the comment number on the right side of the previous statistical format is directly referred to represent an item to be updated, and xx in the statements represents the account number.
"Party A (not yet borrowed) pays Party B xx units":
A. first, the operation is limited to the corresponding unit section. The other unit sections do nothing.
B. Cumulative total itemized release 7 "total foreign member non-loan balance summary":
a) if both the first member and the second member are the inner member or the outer member, the items are not accumulated.
b) If A is the inner member and B is the outer member, then A of Note 7 is incremented by xx and C is refreshed by the difference between A and B.
c) If A is the outer member and B is the inner member, then B of Note 7 increments xx and refreshes C according to the difference between A and B.
C. Then, add a series of summary items in the "A" item of the member under the unit part:
a) note 11 "the member non-loan balance summary for the foreign member", note 12 "the member non-loan balance summary for the foreign member", and note 13 "the member non-loan balance summary for the foreign and foreign members".
b) If B is an inner member, A of notes 12 and 13 increases xx. And refreshing C according to the difference value of A and B.
c) If B is an outer member, then A of notes 11 and 13 increases xx. And refreshing C according to the difference value of A and B.
d) The member under the member "A" and the member "B" are added with one-to-one sub-terms: note 18 that A increases xx and refreshes C according to the A, B difference.
D. Then, add a series of summary items in the "B" item of the member under the unit part:
a) note 11 "the member non-loan balance summary for the foreign member", note 12 "the member non-loan balance summary for the foreign member", and note 13 "the member non-loan balance summary for the foreign and foreign members".
b) B of notes 12 and 13 increases xx if a is an inner member. And refreshing C according to the difference value of A and B.
c) B of notes 11 and 13 increases xx if nail is an outer member. And refreshing C according to the difference value of A and B.
d) The sub-terms of member "B" and member "A" under member "B": b in note 18 increases xx and refreshes C according to the a, B difference.
E. If the entry has a tag: and accumulating a series of summary items in the corresponding label item under the unit part:
a) under the label item, comment 24: "the non-borrowing and returning balance summary under the label" is accumulated according to the B logic of this section.
b) Under the item of member ' a ' under the label, the comment 28 ' summary of non-borrowing and collection of the class of the external member of the member ', the comment 29 ' summary of non-borrowing and collection of the class of the internal member of the member ', and the comment 30 ' summary of non-borrowing and collection of the class of the internal and external members ' of the member ' should be accumulated. And C logic accumulation according to the section.
c) Under the item "b" of member under the label, the comment 28 "summary of non-borrowing and collection of the external member of this kind of member" should be accumulated ", comment 29" summary of non-borrowing and collection of internal member of this kind of member "should be accumulated", and comment 30 "summary of non-borrowing and collection of internal and external member of this kind of member". And D logic accumulation is carried out according to the section.
"Party A (not yet borrowed) receives Party B xx units":
after it is converted into 'Party B (non-borrow) pays Party A xx unit', the statistics are analyzed according to the former rule.
"Party A (Return) pays Party B xx units":
A. first, the operation is limited to the corresponding unit section. The other unit sections do nothing.
B. Cumulative total terms release 8 "total foreign member borrowing summary":
a) if both the first member and the second member are the inner member or the outer member, the items are not accumulated.
b) If A is an inner member and B is an outer member, C of note 8 increments xx and refreshes E according to the value of ABCD.
c) If A is the outer member and B is the inner member, D of note 8 is incremented by xx and E is refreshed according to the value of ABCD.
C. A series of summary entries within the Member "A" entry are then accumulated:
a) note 14 "summary of member external member borrowing", note 15 "summary of member internal member borrowing", and note 16 "summary of member internal and external member borrowing" should be accumulated.
b) If B is an inner member, C for notes 15 and 16 increases xx. And refreshes E according to the value of ABCD.
c) If B is an outsider, C for comments 14 and 16 increases xx. And refreshes E according to the value of ABCD.
d) The member under the member "A" and the member "B" are added with one-to-one sub-terms: c in comment 19 increases xx and refreshes E according to the value of ABCD.
D. Then add a series of summary entries in the member "" B "":
a) note 14 "summary of member external member borrowing", note 15 "summary of member internal member borrowing", and note 16 "summary of member internal and external member borrowing" should be accumulated.
b) If nail is an inner member, D for comments 15 and 16 increases xx. And refreshes E according to the value of ABCD.
c) If nail is an outsider, then D for comments 14 and 16 increases xx. And refreshes E according to the value of ABCD.
d) The member "B" in the "B" and the member "A" in one-to-one terms are added: d in comment 19 increments xx and refreshes E according to the value of ABCD.
E. If the entry has a tag: the series of summary items within each respective tag item is then accumulated:
a) under the label item, note 25: "borrow and return summary under this label", and accumulate according to B pieces of logic in this section.
b) Under the item "A" of the member under the label, the comment 31 "the member borrows and summarizes the foreign members like this", the comment 32 "the member borrows and summarizes the member like this", and the comment 33 "the member borrows and summarizes the foreign members like this". And C logic accumulation according to the section.
c) Under the item "b" of member under the label, the comment 31 "this member this kind of external member borrows and summarizes", comment 32 "this member this kind of internal member borrows and summarizes", comment 33 "this member this kind of internal and external member borrows and summarizes" should be added. And D logic accumulation is carried out according to the section.
"Party A pays (or owes) Party B xx units":
A. first, the operation is limited to the corresponding unit section. The other unit sections do nothing.
B. Cumulative total terms release 8 "total foreign member borrowing summary":
a) if both the first member and the second member are the inner member or the outer member, the items are not accumulated.
b) If A is an inner member and B is an outer member, then B of note 8 increments xx and refreshes E according to the value of ABCD.
c) A is the outer member and b is the inner member, then a of note 8 increments xx and refreshes E according to the values of ABCD.
C. Then add a series of summary entries in the member 'A' entries:
a) note 14 "summary of member external member borrowing", note 15 "summary of member internal member borrowing", and note 16 "summary of member internal and external member borrowing" should be accumulated.
b) If B is an inner member, B of notes 15 and 16 increases xx. And refreshes E according to the value of ABCD.
c) If B is an outsider, B of notes 14 and 16 increases xx. And refreshes E according to the value of ABCD.
d) The member under the member "A" and the member "B" are added with one-to-one sub-terms: b in comment 19 increases xx and refreshes E according to the value of ABCD.
D. Then add a series of summary entries in the member "" B "":
a) note 14 "summary of member external member borrowing", note 15 "summary of member internal member borrowing", and note 16 "summary of member internal and external member borrowing" should be accumulated.
b) If A is an inner member, A of notes 15 and 16 increases xx. And refreshes E according to the value of ABCD.
c) If nail is an outer member, A of notes 15 and 16 increases xx. And refreshes E according to the value of ABCD.
d) The sub-terms of member "B" and member "A" under member "B": a in comment 19 increments xx and refreshes E according to the value of ABCD.
E. If the entry has a tag: the series of summary items within each respective tag item is then accumulated:
a) under the label item, note 25: "borrow and return summary under this label", and accumulate according to B pieces of logic in this section.
b) Under the item "A" of the member under the label, the comment 31 "the member borrows and summarizes the foreign members like this", the comment 32 "the member borrows and summarizes the member like this", and the comment 33 "the member borrows and summarizes the foreign members like this". And C logic accumulation according to the section.
c) Under the item "b" of member under the label, the comment 31 "this member this kind of external member borrows and summarizes", comment 32 "this member this kind of internal member borrows and summarizes", comment 33 "this member this kind of internal and external member borrows and summarizes" should be added. And D logic accumulation is carried out according to the section.
"increased xx units in first Party count" and "decreased xx units in first Party count"
A. First, the operation is limited to the corresponding unit section. The other unit sections do nothing.
B. Cumulative population terms lower release 6 "population count increase and decrease summary":
a) if the count is incremented, A of note 6 is incremented by xx, and C is refreshed according to the value of AB.
b) If the count is decreasing, B of note 6 increases xx and C is refreshed according to the value of AB.
C. Then add the member in the item of "A" comment 10 "the member count increase and decrease summary":
a) if the count is incremented, A of note 10 increments xx and C is refreshed according to the value of AB.
b) If the count is decremented, B of note 10 increments xx and refreshes C according to the value of AB.
D. If the entry has a tag: the series of summary items within each respective tag item is then accumulated:
a) under the label item, note 23: "count increase and decrease summary under this label", add up according to B pieces of logic in this section.
b) Under the item of member ' A ' under the label, the notation 27 ' this member's count increase and decrease summary ' should be accumulated, and the logical accumulation is performed according to the section C.
Compound combined sentence: after the sentences are decomposed into basic sentences, the method is used for analyzing and counting one by one.
Internal and external member definition rules when referring to child items: as can be seen from section 5), there are many times when it is determined whether party a or party b is an outside or inside member of the project. Typically, this is directly based on the identity of the member in the project. But when in statistics, if the statistics is carried out on the parent project, the statistics can be carried out together with the child project. At this time, the identities of the internal and external members have some special rules:
A. if the members of the child project are not members of the parent project at the same time (the same telephone is considered as the same person), the members are uniformly considered as the outer members.
B. If the member of the child item is also a member of the parent item (if the phone numbers are consistent, the same person is considered), the identity of the child item in the parent item is uniformly determined. For example, the following steps are carried out: if the parent project has an outer member of three, the telephone 222, the child project has an inner member of three, and the telephone is also 222, the system judges that the three of the parent project and the child project of three are the same role in real life according to the same telephone, if the parent project is counted and the child project is included, the data on the three of the parent project and the data on the three of the child project are accumulated, and the identity of the outer member in the parent project is taken as the standard. This accumulated number is considered to be of an extrinsic nature.
4. And (4) saving a statistical result:
(1) and obtaining a statistical result after the statistics is completed according to the statistical method. The results may or may not be saved. If not, the result disappears after the result page exits. The method mainly defines the following two preservation modes:
(2) one way is to derive: the statistics page, which provides export buttons, may output txt files or other readable format files in an as-received format. Such as an excel file.
(3) Another way is to save as a statistics report entry: an online storage function is provided in the statistical result page, and the result can be stored in the system in the form of a statistical report entry. As described in the previous entry types, a statistical report entry is an extension of a story entry. A link with a statistical result is added inside. And opening the link, and directly displaying the statistical result page as is, so that the statistical result can be traced. After the statistics, if the entries in the statistics are modified, the statistics report is not affected. Moreover, the method requires that when the item snapshot in the historical statistics is displayed, the item snapshot should be compared with the latest state of the current item and prompt which items are modified later. To achieve clearer traceability.
Seventhly, a method for performing more functions such as project management and the like comprises the following steps:
(1) the project management is carried out by using the method, and a system realized by using the method is taken as a tool, which is called the system for short. Due to the characteristics of the method, the use characteristics of the method are different from those of the traditional mode when the functions such as project management and the like are realized. In general, the system is flexible and simple, and some controls need team coordination.
(2) And (3) docking with professional finance: first, a hand of financial material for a team member may be obtained using the present system. Secondly, files, such as Excel files, can be exported by using the system and serve as a hand of material for professional financial accounting.
(3) Application and approval, member's consent: the method considers that under the interactive system, a note is recorded in a note-recording mode (an application label can be built by self), and after the leader sees the note, the examination and approval are finished by directly commenting and replying the agreement or the formal support or adding a stamp of the agreement. The method is operated by the leader, and the generated entry log cannot be deleted, so that the method has approval effect. Even after the entry shows that the party is reached, the party does not make an objection to the opinion and may be considered as an agreement. The simple mode greatly reduces the complexity of the system and can completely meet the requirements of production and living at the same time.
(4) And (3) financial reimbursement: the employee can record the expense of the company through the system. After being viewed as a member of the project's finance, the agreement is returned in a number of ways, and a self-created stamp "agreement reimbursement" is created, from which a log of entries is generated, which is considered to pass the reimbursement audit. After actual reimbursement, the finance can enter return property items to complete reimbursement.
(5) And (4) reporting work: similar tags such as 'work logs' or 'work weekly reports' can be built by self, and employees are required to issue event-recording items of the corresponding tags in the project every day or every week in a timely manner. And determining which employees do not report the work reports in time according to the 'supplementary notes' attribute.
(6) Marketing follow-up: sub-projects can be built for a large marketing project, branch, internal team, and pull in required personnel. The progress of the marketing item and the preservation of various feedback may also be discussed and followed in an entry in the form of a review reply. A plurality of shops can report sales volume, inventory and other conditions every day through the system.
(7) Customer and supplier management: all customers are added as outsiders of the project, custom outsider tags such as 'customers' are attached, and telephone calls and brief descriptions can be recorded in the details of the outsiders. The generated accounts and transactions can be stored in the system in an entry mode. The outsiders may also be designated in the screening, and the sales, the purchase, the loan, etc. generated therewith may be counted.
(8) Customer service: customers can be added as outsiders and interactions established. Some notes or accounts associated with him may be allowed to see while recording so that he may discuss replies together in this entry. The consent or denial of the client may also be used as evidence for the project service. The customer can also see the increase and decrease of the integral, the progress record of the project and the like.
(9) Voting: an item to be determined by a project may be represented by recording a note and then asking the relevant member to be in the lower form. The voting rate, the support rate or the rejection rate is displayed in the formal region. And each time a member's status is represented, a log of entries is kept in time. The voting is convenient and quick, and the defects of no evidence for oral voting repentance and too troublesome signature voting are avoided.
(10) And (3) conservation of promise: in the project, if all matters of daily commitment of the leader or the staff, such as bonus of the leader commitment, are subjected to the surface treatment by the signature, the items are sent out by the system, and the other party replies confirmation. Is an electronic contract which can not be erased. Even if modified, the modification evolution process can be seen in the entry modification log, with no repudiation.
(11) And (3) piece counting production: in production, if the design production is met, interactive recording can be carried out in the system in a counting increase and decrease mode, and a manager and workers can immediately confirm whether errors exist in a comment mode. Thus, the method is convenient and clear and does not cause disputes.
(12) And (3) performing employee performance assessment: if the business is evaluated by sales performance, a label can be directly established for each employee, when a company is input, the label of the employee to which the business belongs is attached, and data of the corresponding label item is checked during statistics. If the assessed indexes are converted into integrals, the increase and decrease of the integral of the staff can be recorded directly in a counting increase and decrease mode.
(13) And (4) post handover: at ordinary times, the staff should be required to remember all data of related work in the system, for example, the telephone of a client, the client side find out who examines and approves, and who is engaged with, construction progress, settlement progress and items needing attention. The phenomenon that people lose when walking is prevented.
(14) Partner investment supervision: when participating in a project as a partner, the manager of the member project can be required, so that the cooperative shareholders can have the effects of mutual supervision and mutual balance. The shareholder may have an informed right to all operations of the project. When the stockholder exits, the stockholder can give up the administrator under the condition of agreement. Preventing the practical operator from operating in one way. For large transactions, a formal voting vote may also be utilized in the entries. When items need to be deleted and destroyed, all administrators are required to agree with each other to perform the operations. The method considers that the administrator voluntarily gives up and agrees to delete the shareholder, the shareholder is the result of offline mutual coordination between the shareholder, and the shareholder can not negotiate consistently, so that the current situation is maintained.
(15) And (3) warehouse management: building a warehouse as an inner member. The member of the warehouse-out and warehouse-in is used as the A, B and C prescription and matched with a user-defined unit. And the goods entering and exiting management of the warehouse is realized.
(16) Order and contract management: specially, a self-defined label called order or contract is established, under which notes are added, and under each note, the progress of the order or contract is reported or updated by commenting or replying. And stamp marks are added, such as stamps of 'contract signed', 'order in progress', 'money received', 'order completed', and the like, and then the stamps are marked on corresponding record.
(17) Arrears and project cash flow management: by the loan statistics, the loan and fund overstock condition between the client or the supplier, the staff and the like and the project can be checked.
(18) Department management: each subordinate department is simulated by the sub-project, and the department member is pulled into the sub-project member. The company administrator automatically acts as an administrator for the department sub-project. And gives the department manager some administrative rights in the sub-project. Management in the department is realized.
Eighthly, data backup and export
All data should be able to export a readable file in a common format: such as txt file, Excel format file, for the user to do further processing or data backup.
Ninth, data security should be emphasized:
all data should be stored in an encrypted manner, and the security during transmission and use is ignored.
Ten, allowing expansion:
the method only defines the most core basic logic and method in the set of system. In specific implementation, the method can be expanded on the basis of the method according to actual production and living conditions so as to realize richer functions and stronger social benefits.
The above-mentioned embodiments only show some embodiments of the present invention, and the description thereof is more specific and detailed, but should not be construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the claims.

Claims (8)

1. A kind of note account-keeping count project management system based on clauses and subclauses, characterized by that: the system comprises a client module and a server module;
the client module includes:
the login module is used for realizing user registration, identity authentication and login;
the project module is used for realizing project creation and management;
the member management module is used for realizing project member management;
an administrator module for implementing administrator appointments and appointments;
the label module is used for realizing item classification label management;
an item management module for implementing item management;
an account group module for implementing account group management;
a statistic module for implementing data statistics;
the server module is used for receiving and processing the information sent by the client module and sending the processed information to the client module.
2. The itemized bookkeeping count event management system of claim 1, wherein: the project module also includes a sub-project module for implementing sub-project management.
3. The itemized bookkeeping count event management system of claim 1, wherein: the project module is also used for setting, modifying, destroying, deactivating and displaying project units and management information, project introduction information, project creation time information, entry content information, project authority information, project members, project label information and sub-project information;
the destroying function and the stopping function in the project module are only displayed for a project manager;
voting is carried out when destruction is carried out, and voting is terminated if an administrator carries out operation against destruction at the client.
4. The itemized bookkeeping count event management system of claim 3, wherein: the member management module identifies whether each member is the same person according to the telephone number during registration; it is not necessarily the same person if the telephone number is not filled in.
5. The itemized bookkeeping count event management system of claim 1, wherein: the client module also comprises an interaction module for realizing the establishment and disconnection of interaction of project members;
the tag module is used for selecting, adding, viewing and modifying the item tag.
6. The itemized bookkeeping count event management system of claim 1, wherein: the item management module is used for realizing the following functions:
creating an item, selecting an item type, selecting an occurrence time, selecting an item to which the item belongs, selecting a tag to which the item belongs, selecting or inputting an element, and adding or subtracting an account group;
the content, remark, modification record information, entry voting form record and entry log display, visibility operation and stamping operation of the entry;
the operation of entry table state includes three options of support, non-support and question;
and (4) commenting, invalidating, withdrawing and deleting the item.
7. The itemized bookkeeping count event management system of claim 1, wherein: the account group module provides six basic combined account array statements and two composite combinations.
8. The itemized bookkeeping count event management system of claim 1, wherein: the statistical module is used for managing and displaying internal and external member logics related to the sub-items and screening conditions of statistical samples;
the statistical module is used for counting the information in the project and counting according to the screening conditions, and the statistical result is stored as a statistical item or exported to be a file.
CN202010445161.7A 2020-05-23 2020-05-23 Event-recording accounting counting project management system based on item form Pending CN111626703A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010445161.7A CN111626703A (en) 2020-05-23 2020-05-23 Event-recording accounting counting project management system based on item form

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010445161.7A CN111626703A (en) 2020-05-23 2020-05-23 Event-recording accounting counting project management system based on item form

Publications (1)

Publication Number Publication Date
CN111626703A true CN111626703A (en) 2020-09-04

Family

ID=72261188

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010445161.7A Pending CN111626703A (en) 2020-05-23 2020-05-23 Event-recording accounting counting project management system based on item form

Country Status (1)

Country Link
CN (1) CN111626703A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114357953A (en) * 2021-07-07 2022-04-15 北京国电通网络技术有限公司 Engineering data management method, equipment, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040068517A1 (en) * 2002-10-02 2004-04-08 Bank One Corporation System and method for network-based project management
CN106845923A (en) * 2016-12-20 2017-06-13 柳州顺联科技有限公司 A kind of project management system
CN107730217A (en) * 2017-11-10 2018-02-23 上海申磊信息科技有限公司 A kind of business model method of customer relation management

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040068517A1 (en) * 2002-10-02 2004-04-08 Bank One Corporation System and method for network-based project management
CN106845923A (en) * 2016-12-20 2017-06-13 柳州顺联科技有限公司 A kind of project management system
CN107730217A (en) * 2017-11-10 2018-02-23 上海申磊信息科技有限公司 A kind of business model method of customer relation management

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114357953A (en) * 2021-07-07 2022-04-15 北京国电通网络技术有限公司 Engineering data management method, equipment, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
Loshin Enterprise knowledge management: The data quality approach
CN108133299A (en) A kind of smart items manage system
CN106796674A (en) For the system and method that business debt is collected money automatically
CN110751361B (en) Bank demand entry level management method and system
CN109214892A (en) A kind of e-commerce platform management system
CN112581283A (en) Method and device for analyzing and alarming business bank employee transaction behaviors
CN113919927A (en) Auditing platform based on data processing
JP7057588B2 (en) Transaction audit system
Bidabad et al. IT role in fulfillment of Profit & Loss Sharing (PLS) mechanism
CN115170090A (en) Project management method and device, electronic equipment and readable storage medium
Accorsi et al. A practitioner’s view on process mining adoption, event log engineering and data challenges
TWM582187U (en) Supply chain financial service system combining big data information in blockchain technology
CN109508947A (en) A kind of electric contract operation method and system based on credit system
CN111626703A (en) Event-recording accounting counting project management system based on item form
CN107924534A (en) Banking system, method and program for the credit management of structural financing
JP5082370B2 (en) Internal audit control support system, control server used in the system, internal audit control support method, internal audit control support program
JP2003296554A (en) Customer requirement system
CN111626702A (en) Event-recording accounting counting project management method based on item form
Alles et al. Process mining: A new research methodology for AIS
CN114254908A (en) Risk perception and supervision platform for regional financial non-bank financial institution
Singh A conceptual model for proactive detection of potential fraud enterprise systems: exploiting SAP audit trails to detect asset misappropriation
KR100796056B1 (en) System and method for integrated management of credit information
Chiantera Data quality and data governance in insurance corporations
Alamaki et al. The Effectiveness of Regulatory Reporting by Banking Institutions
Affum Effect of integrated management information systems on services of private organizations in Takoradi Ghana

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20200904