A method, system and related device for generating accounting entry data
By classifying application sources, entities, and events based on document data and parsing accounting entry data using preset configuration files, the problems of repetitive development and high costs in existing technologies are solved, enabling seamless access and flexible configuration across business systems.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GUANGZHOU PINWEI SOFTWARE CO LTD
- Filing Date
- 2022-11-30
- Publication Date
- 2026-06-23
AI Technical Summary
Existing accounting systems require separate development of journal entry generation programs, leading to redundant development and high labor costs, and making it difficult to achieve unified access across multiple business systems.
By classifying application sources, entities, and events based on document data, the system uses a pre-defined accounting information configuration file to obtain journal entry line definitions, determine line type allocation rules and account derivation rules, and parse and store accounting entry data.
It enables seamless integration across business systems, shortens the development cycle, improves the system's flexibility and configurability, and reduces labor costs.
Smart Images
Figure CN115841395B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of accounting and bookkeeping technology, and more specifically, to a method, system and related equipment for generating accounting entry data. Background Technology
[0002] Existing accounting operations typically rely on accounting subsystems within office systems (such as the SLA subledger system in Oracle EBS). In this model, each business system needs to develop its own journal entry generation program to perform functions such as debit / credit and account selection, resulting in redundant development.
[0003] For multiple business systems, the ability to use a common subledger entry calculation service, miscellaneous subledger module, and general ledger interface when integrating with the general ledger system would be a significant technological breakthrough. Summary of the Invention
[0004] In view of this, this application provides a method, system and related equipment for generating accounting entry data to solve at least one of the technical problems mentioned above.
[0005] To achieve the above objectives, the first aspect of this application provides a method for generating accounting entry data, comprising:
[0006] Based on the input document data, the application source, entity, and event category to which the document belongs are determined. The application source is used to indicate the application origin of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document.
[0007] Based on the application source, the entity, and the event classification, the journal line definition matching the document data is obtained from the preset accounting information configuration file;
[0008] Based on the defined journal row, the row type allocation rules and account derivation rules are determined;
[0009] Based on the row type allocation rules, the account derivation rules, and the data structure of the document data, the document data is parsed to obtain the header data and row data of the accounting entries, and the header data and row data are stored in the database.
[0010] Preferably, the process of parsing the document data to obtain the header data and line data of the accounting entries based on the row type allocation rules, the account derivation rules, and the data structure of the document data includes:
[0011] Based on the row type allocation rules and the data structure of the document data, the document data is parsed to obtain the original header data and original row data of the accounting entries;
[0012] Based on the account derivation rules, account information is supplemented in the original header data and original line data to obtain the header data and line data of the accounting entries.
[0013] Preferably, the process of storing the header data and the row data in a database includes:
[0014] The header data and the row data are stored in a local database;
[0015] or,
[0016] The header data and the row data are stored in a cloud database.
[0017] A second aspect of this application provides an apparatus for generating accounting entry data, comprising:
[0018] The data information determination unit is used to determine the application source, entity, and event category of the document based on the input document data. The application source is used to indicate the application source of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document.
[0019] The journal entry line determination unit is used to obtain the journal entry line definition matching the document data from a preset accounting information configuration file based on the application source, the entity, and the event classification.
[0020] The combination rule determination unit is used to determine the row type allocation rule and the account derivation rule based on the journal row definition;
[0021] The accounting entry determination unit is used to parse the document data based on the row type allocation rules, the account derivation rules, and the data structure of the document data to obtain the header data and row data of the accounting entries.
[0022] An accounting entry storage unit is used to store the header data and the row data in a database.
[0023] A third aspect of this application provides an apparatus for generating accounting entry data, comprising: a memory and a processor;
[0024] The memory is used to store programs;
[0025] The processor is used to execute the program to implement each step of the above-described method for generating accounting entry data.
[0026] A fourth aspect of this application provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for generating accounting entry data as described above.
[0027] The fifth aspect of this application provides a system for generating accounting entry data, including an accounting information configuration module, an accounting engine interface module, and an accounting entry processing module;
[0028] The accounting information configuration module is used to generate an accounting information configuration file based on the information input by the user.
[0029] The accounting engine interface module is used to receive document data input from the application source and transmit the document data to the accounting entry processing module.
[0030] The accounting entry processing module is used to implement each step of the method for generating accounting entry data as described in any one of claims 1 to 3.
[0031] Preferably, the accounting information configuration module includes an application source configuration component, an entity configuration component, and an event classification configuration component;
[0032] The application source configuration component is used to configure the application source of the document;
[0033] The entity configuration component is used to configure the properties of the document;
[0034] The event classification component is used to configure the type of document.
[0035] Preferably, the accounting information configuration module further includes a row type configuration component;
[0036] The row type configuration component is used to configure the accounting attributes of documents.
[0037] Preferably, the accounting information configuration module further includes an account derivation configuration component;
[0038] The account derivation configuration component is used to configure the account derivation rules for documents.
[0039] As described in the above technical solution, this application first determines the application source, entity, and event category of the document based on the input document data. The application source indicates the application origin of the document, the entity indicates the nature of the document, and the event category indicates the classification of the document. Then, based on the application source, the entity, and the event category, the journal entry line definition matching the document data is obtained from a preset accounting information configuration file. It is understood that the accounting information configuration file is pre-generated based on the user's document characteristics and contains the journal entry line definition information for the document data. Next, based on the journal entry line definition, row type allocation rules and account derivation rules are determined. Finally, based on the row type allocation rules, the account derivation rules, and the data structure of the document data, the document data is parsed to obtain the header data and row data of the accounting entries, and the header data and row data are stored in the database. Through the pre-generated accounting information configuration file, this application can connect to any business system, use a unified subledger entry calculation service and miscellaneous subledger module to parse the document data from the business system, and finally obtain the corresponding accounting entry data. Attached Figure Description
[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0041] Figure 1 This is a schematic diagram of the accounting entry data generation system disclosed in an embodiment of this application;
[0042] Figure 2 The system architecture diagram disclosed in the embodiments of this application is illustrated;
[0043] Figure 3 This is a schematic diagram of the method for generating accounting entry data disclosed in the embodiments of this application;
[0044] Figure 4 This is a schematic diagram of the accounting entry data generation apparatus disclosed in the embodiments of this application;
[0045] Figure 5 This is a schematic diagram of the device for generating accounting entry data disclosed in the embodiments of this application. Detailed Implementation
[0046] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0047] The inventors of this application discovered that existing business systems require the development of specific business modules to achieve accounting entry posting and general ledger transmission. The development cycle is over 1.5 months, and these systems are not fully configurable. As business expands and changes, code adjustments are needed, requiring additional workload and incurring high labor costs. To solve this problem, the system can be divided into a business adaptation module and a general accounting entry processing module. The business adaptation module generates corresponding business configuration files through user customization. The accounting entry processing module then reads these configuration files and applies the business attributes to the accounting entry processing, enabling seamless integration with various business systems. By adopting the technical solution proposed in this application, the development cycle for business integration is shortened to half a month, and the functional modules are configurable, offering high flexibility.
[0048] The following describes the accounting entry data generation system provided in the embodiments of this application. Please refer to... Figure 1 The accounting entry data generation system provided in this application embodiment may include an accounting information configuration module 10, an accounting entry processing module 20, and an accounting engine interface module 50.
[0049] The accounting information configuration module 10 is used to generate an accounting information configuration file based on the information input by the user. This accounting information configuration file describes the data structure and other information of the documents. By reading this accounting information configuration file, the data structure and other information of the corresponding documents can be obtained, thereby enabling the parsing of the document data.
[0050] The accounting engine interface module 50 is the interface between the specific business system and this system. It is used to receive document data input from the application source (i.e., the business system) and transmit the document data to the accounting entry processing module 20.
[0051] The accounting entry processing module 20 is the core processing module of this system. It is used to make accounting entries on document data, thereby generating the header data and line data of the accounting entries.
[0052] Understandably, this system is adaptable to various business systems, such as inventory management systems, accounts payable management systems, and accounts receivable management systems. When interfacing with different business systems, users need to configure the corresponding items through the accounting information configuration module 10 according to the characteristics of the interfacing business system, thereby generating an accounting information configuration file corresponding to that business system. Furthermore, users need to transmit document data to the accounting entry processing module 20 according to the interface specifications of the accounting engine interface module 50. When performing accounting entries on the document data from the business system, the accounting entry processing module 20 and the accounting engine interface module 50, in conjunction with the accounting information configuration file, perform specific data processing to ultimately obtain the header data and line data of the accounting entries. Therefore, this system possesses SaaS (Software as a Service) capabilities, enabling it to perform accounting entries on document data from different business systems.
[0053] For example, please see Figure 2 The business system assembles the transaction processing object parameters based on business documents (such as invoice information) and calls the accounting center service or SDK code on the server to obtain the return values of the accounting entry header and row. The execution logic within the accounting center service or SDK is as follows:
[0054] (1) First, check the application, entity, and event classification of the document to find the corresponding journal entry definition;
[0055] (2) Determine the number of rows to generate debit and credit entries based on the row type allocated according to the journal row definition;
[0056] (3) In each row type, the accounting attribute value is obtained based on the accounting attribute allocation; if an accounting attribute is bound to a local interface, the local Java code will be executed to obtain it.
[0057] (4) Calculate the final account value in each row type according to the account derivation rules;
[0058] (5) Finally, assemble the accounting attribute values and account values to output the accounting entry header and line.
[0059] In the allocation of accounting attributes, custom sources can be used to determine certain accounting attributes and assist in account derivation. For example, assuming that the document data only contains the name of the invoice issuer, the custom source can be used to find information related to the invoice issuer's department, position, etc., thereby deriving the invoice issuer's complete information.
[0060] In some embodiments of this application, the accounting information configuration module 10 includes an application source configuration component, an entity configuration component, and an event classification configuration component. The application source configuration component configures the application source of documents. For example, if the document data to be entered into originates from the inventory management system, the application source is configured as the inventory management system. The entity configuration component configures the nature of documents. For example, if the document to be entered into is an invoice, the entity is configured as an invoice. The event classification component configures the type of documents. Document types can include prepayments, loans, credit loans, payments, refunds, etc., and the event classification is configured to the corresponding type based on the type of the document to be entered into.
[0061] In some embodiments of this application, the accounting information configuration module 10 may further include a line type configuration component. This line type configuration component is used to configure the accounting attributes of a document. For example, the accounting attributes of a document may include liabilities, expenses, taxes, etc.
[0062] In some embodiments of this application, the accounting information configuration module 10 may further include an account derivation configuration component. This component is used to configure the account derivation rules for documents. It is understood that the account content in a document may contain only one or two fields; the account derivation rules can complete all the account content. For example, the company field can be obtained based on the organization ID, the account field can be obtained based on the account alias, and so on.
[0063] The accounting entry processing module 20 of this system is the core part of the accounting entry function, and it is mainly used to execute the method for generating accounting entry data proposed in the embodiments of this application. The method is described in detail below. Please refer to... Figure 3 The method for generating accounting entry data provided in this application embodiment may include the following steps:
[0064] Step S101: Based on the input document data, determine the application source, entity, and event category to which the document belongs.
[0065] As mentioned above, the application source is used to indicate the application source of the document, which may include inventory management system, accounts payable management system, accounts receivable management system, etc.; the entity is used to indicate the nature of the document, which may include prepayment and borrowing, loan, payment, refund, etc.; the event category is used to indicate the category of the document, which may include liabilities, expenses and taxes, etc.
[0066] Step S102: Based on the application source, entity, and event classification, obtain the journal line definition that matches the document data from the preset accounting information configuration file.
[0067] The definition of journal entries is recorded in the accounting information configuration file. It records the row type allocation rules and account derivation rules for certain documents. It can be understood that the type of these documents is uniquely determined by the application source, entity, and event classification.
[0068] Step S103: Based on the definition of journal entries, determine the row type allocation rules and account derivation rules.
[0069] For example, the row type allocation rule may include a row type ID and a journal row description ID. Specifically, the row type ID may include allocation-closing account, allocation-inventory-goods inventory, etc., and the journal row description ID may include expense allocation: journal row description, etc.
[0070] Step S104: Based on the row type allocation rules, account derivation rules, and document data structure, the document data is parsed to obtain the header data and row data of the accounting entries, and the header data and row data are stored in the database.
[0071] This application first determines the application source, entity, and event category of the input document data. The application source indicates the application origin of the document, the entity indicates the nature of the document, and the event category indicates the classification of the document. Then, based on the application source, entity, and event category, it retrieves journal entry definitions matching the document data from a pre-defined accounting information configuration file. It is understood that the accounting information configuration file is pre-generated based on the user's document characteristics and contains journal entry definition information for the document data. Next, based on the journal entry definitions, it determines row type allocation rules and account derivation rules. Finally, based on the row type allocation rules, account derivation rules, and the data structure of the document data, it parses the document data to obtain the header data and row data of the accounting entries, and stores the header data and row data in a database. Through the pre-generated accounting information configuration file, this application can interface with any business system, using a unified sub-ledger entry calculation service and miscellaneous sub-ledger module to parse document data from the business system and ultimately obtain the corresponding accounting entry data.
[0072] In some embodiments of this application, step S104, which parses the document data based on row type allocation rules, account derivation rules, and the data structure of the document data to obtain the header data and row data of the accounting entries, may include:
[0073] S1, based on the row type allocation rules and the data structure of the document data, parses the document data to obtain the original header data and original row data of the accounting entries.
[0074] S2, based on the account derivation rules, completes the account information of the original header data and original line data to obtain the header data and line data of the accounting entries.
[0075] In some embodiments of this application, the process of storing header data and row data in the database in step S104 can be:
[0076] S1 stores header and row data in a local database;
[0077] or,
[0078] S2, store the header data and the row data in a cloud database.
[0079] For example, when the number of documents is large, the header and row data obtained from the entries can be stored in a local database to avoid network congestion. When the number of documents is small and needs to be shared across multiple locations, the header and row data obtained from the entries can be stored in a cloud database.
[0080] The following describes the accounting entry data generation apparatus provided in the embodiments of this application. The accounting entry data generation apparatus described below and the accounting entry data generation method described above can be referred to in correspondence.
[0081] Please see Figure 4 The accounting entry data generation apparatus provided in this application embodiment may include:
[0082] The data information determination unit 21 is used to determine the application source, entity, and event category of the document based on the input document data. The application source is used to indicate the application source of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document.
[0083] The journal entry determination unit 22 is used to obtain the journal entry definition matching the document data from a preset accounting information configuration file based on the application source, the entity, and the event classification.
[0084] The combination rule determination unit 23 is used to determine the row type allocation rule and the account derivation rule based on the journal row definition;
[0085] The accounting entry determination unit 24 is used to parse the document data based on the row type allocation rule, the account derivation rule and the data structure of the document data to obtain the header data and row data of the accounting entry;
[0086] The accounting entry storage unit 25 is used to store the header data and the row data in the database.
[0087] In some embodiments of this application, the process by which the accounting entry storage unit 25 parses the document data based on the row type allocation rules, the account derivation rules, and the data structure of the document data to obtain the header data and row data of the accounting entries may include:
[0088] Based on the row type allocation rules and the data structure of the document data, the document data is parsed to obtain the original header data and original row data of the accounting entries;
[0089] Based on the account derivation rules, account information is supplemented in the original header data and original line data to obtain the header data and line data of the accounting entries.
[0090] In some embodiments of this application, the process by which the accounting entry storage unit 25 stores the header data and the row data in the database may include:
[0091] The header data and the row data are stored in a local database;
[0092] or,
[0093] The header data and the row data are stored in a cloud database.
[0094] The accounting entry data generation apparatus provided in this application embodiment can be applied to accounting entry data generation devices, such as computers. Optionally, Figure 5 The diagram shows the hardware structure of the device for generating accounting entry data. Figure 5 The hardware structure of the accounting entry data generation device may include: at least one processor 31, at least one communication interface 32, at least one memory 33 and at least one communication bus 34.
[0095] In this embodiment, the number of processor 31, communication interface 32, memory 33 and communication bus 34 is at least one, and processor 31, communication interface 32 and memory 33 communicate with each other through communication bus 34;
[0096] The processor 31 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.
[0097] The memory 33 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;
[0098] The memory 33 stores a program, and the processor 31 can call the program stored in the memory 33. The program is used for:
[0099] Based on the input document data, the application source, entity, and event category to which the document belongs are determined. The application source is used to indicate the application origin of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document.
[0100] Based on the application source, the entity, and the event classification, the journal line definition matching the document data is obtained from the preset accounting information configuration file;
[0101] Based on the defined journal row, the row type allocation rules and account derivation rules are determined;
[0102] Based on the row type allocation rules, the account derivation rules, and the data structure of the document data, the document data is parsed to obtain the header data and row data of the accounting entries, and the header data and row data are stored in the database.
[0103] Optionally, the refined and extended functions of the program can be found in the description above.
[0104] This application embodiment also provides a storage medium that can store a program suitable for execution by a processor, the program being used for:
[0105] Based on the input document data, the application source, entity, and event category to which the document belongs are determined. The application source is used to indicate the application origin of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document.
[0106] Based on the application source, the entity, and the event classification, the journal line definition matching the document data is obtained from the preset accounting information configuration file;
[0107] Based on the defined journal row, the row type allocation rules and account derivation rules are determined;
[0108] Based on the row type allocation rules, the account derivation rules, and the data structure of the document data, the document data is parsed to obtain the header data and row data of the accounting entries, and the header data and row data are stored in the database.
[0109] Optionally, the refined and extended functions of the program can be found in the description above.
[0110] In summary:
[0111] The accounting entry data generation system of this application has SaaS capabilities. The accounting entry processing module of this system first determines the application source, entity, and event category of the input document data. The application source indicates the application origin of the document, the entity indicates the nature of the document, and the event category indicates the classification of the document. Then, based on the application source, entity, and event category, it retrieves the journal entry line definition matching the document data from a preset accounting information configuration file. It is understood that the accounting information configuration file is pre-generated based on the user's document characteristics and contains the journal entry line definition information for the document data. Next, based on the journal entry line definition, it determines the line type allocation rules and account derivation rules. Finally, based on the line type allocation rules, the account derivation rules, and the data structure of the document data, it parses the document data to obtain the header data and line data of the accounting entries, and stores the header data and line data in the database. Through the pre-generated accounting information configuration file, this application can connect to any business system, use a unified subledger entry calculation service and miscellaneous subledger module to parse the document data from the business system, and finally obtain the corresponding accounting entry data.
[0112] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0113] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.
[0114] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method of generating accounting entry data, characterized by, The method comprises: determining, based on inputted bill data, an application source, an entity, and an event classification of the bill, the application source being used to represent the application source of the bill, the entity being used to represent the nature of the bill, and the event classification being used to represent the classification of the bill; obtaining, based on the application source, the entity, and the event classification, a journal line definition matched with the bill data from a preset accounting information configuration file; determining, based on the journal line definition, a line type assignment rule and an account derivation rule; wherein the line type assignment rule is used to determine the number of debit and credit lines generated according to the line type assigned by the journal line definition, and obtain the accounting attribute value according to the accounting attribute assignment in each line type; and the account derivation rule is used to complete all contents of the account, including obtaining the company field according to the organization ID or obtaining the account field according to the account alias; and the line type assignment rule comprises a line type ID and a journal line description ID, the line type ID comprises a split-accounting closing subject and a split-accounting inventory commodity, and the journal line description ID comprises a cost split: journal line description; parsing the bill data based on the line type assignment rule, the account derivation rule, and the data structure of the bill data to obtain head data and line data of the accounting entry, and storing the head data and the line data in a database; wherein the process of parsing the bill data based on the line type assignment rule, the account derivation rule, and the data structure of the bill data to obtain head data and line data of the accounting entry comprises: parsing the bill data based on the line type assignment rule and the data structure of the bill data to obtain original head data and original line data of the accounting entry; completing the account information of the original head data and the original line data based on the account derivation rule to obtain the head data and the line data of the accounting entry; and the process of storing the head data and the line data in the database comprises: storing the head data and the line data in a local database or storing the head data and the line data in a cloud database.
2. A system for generating accounting entry data, characterized by The method comprises: an accounting information configuration module, an accounting engine interface module, and an accounting entry processing module; the accounting information configuration module is used to generate an accounting information configuration file according to the information inputted by a user; the accounting engine interface module is used to receive bill data inputted by an application source and transmit the bill data to the accounting entry processing module; 3. The system of claim 2, wherein, the accounting entry processing module is used to implement each step of the method for generating accounting entry data according to claim 1. The accounting information configuration module comprises an application source configuration component, an entity configuration component, and an event classification configuration component; the application source configuration component is used to configure the application source of a bill; the entity configuration component is used to configure the nature of a bill; 4. The system of claim 3, wherein, the event classification configuration component is used to configure the type of a bill. The accounting information configuration module further comprises a line type configuration component; the line type configuration component is used to configure the accounting attribute of a bill.
5. The system of claim 3, wherein, The accounting information configuration module also includes an account derivation configuration component; The account derivation configuration component is used to configure the account derivation rules for documents.
6. An apparatus for generating accounting entry data, characterized by include: The data information determination unit is used to determine the application source, entity, and event category of the document based on the input document data. The application source is used to indicate the application source of the document, the entity is used to indicate the nature of the document, and the event category is used to indicate the classification of the document. The journal entry line determination unit is used to obtain the journal entry line definition matching the document data from a preset accounting information configuration file based on the application source, the entity, and the event classification. The combination rule determination unit is used to determine the row type allocation rule and the account derivation rule based on the journal row definition; The row type allocation rule is used to determine the number of rows for generating debit and credit entries based on the row type allocated according to the journal row definition, and to obtain the accounting attribute value by allocating according to the accounting attribute in each row type. Furthermore, the account derivation rules are used to complete all the content of the account, including obtaining the company field based on the organization ID or obtaining the account field based on the account alias; Furthermore, the row type allocation rule includes row type ID and journal row description ID. The row type ID includes allocation-closing account and allocation-inventory-inventory goods. The journal row description ID includes expense allocation: journal row description. The accounting entry determination unit is used to parse the document data based on the row type allocation rules, the account derivation rules, and the data structure of the document data to obtain the header data and row data of the accounting entries. The accounting entry determination unit, based on the row type allocation rules, the account derivation rules, and the data structure of the document data, parses the document data to obtain the header data and row data of the accounting entries in the following specific ways: Based on the row type allocation rules and the data structure of the document data, the document data is parsed to obtain the original header data and original row data of the accounting entries; Based on the account derivation rules, account information is supplemented in the original header data and original line data to obtain the header data and line data of the accounting entries; An accounting entry storage unit is used to store the header data and the row data in a database; The specific methods by which the accounting entry storage unit stores the header data and the row data in the database include: storing the header data and the row data in a local database or storing the header data and the row data in a cloud database.
7. An accounting entry data generating apparatus characterized by comprising: include: Memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the method for generating accounting entry data as described in claim 1.
8. A storage medium having stored thereon a computer program, characterized in that When the computer program is executed by the processor, it implements each step of the method for generating accounting entry data as described in claim 1.