A retail business based financial document generation system and method

Abstract

This invention discloses a financial voucher generation system and method based on retail business, belonging to the field of data processing technology. The system includes the following steps: acquiring retail transaction data, which includes transaction amount and at least one transaction attribute information; dynamically matching corresponding accounting rules from a preset accounting rule library based on the transaction attribute information; and defining the amount allocation logic among multiple accounting entities using the accounting rules. This invention solves the problem of rigid accounting rules in existing systems by acquiring retail transaction data containing transaction amount and multi-dimensional transaction attributes, dynamically matching and adapting accounting rules from a preset accounting rule library based on the transaction attributes, and then dynamically determining the account mapping relationship from an accounting account mapping library by combining the accounting rules and transaction attributes, thus solving the problem of fixed account mapping. Finally, it automatically decomposes the transaction amount to generate multi-accounting entity accounting entries based on the accounting rules and account mapping relationship.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a financial voucher generation system and method based on retail business. Background Technology

[0002] In current retail operations, the automated generation of financial vouchers is a crucial technological support for improving business efficiency and compliance. Traditional methods rely on manual data entry and simple rule engines, capable of handling basic transaction scenarios such as routine sales and returns. However, with the deep integration of retail formats and business model innovation, numerous cross-channel, cross-time-period, and multi-entity revenue-sharing settlement transactions have emerged, such as joint sales, platform commissions, and multi-level distribution rebates—complex business models. These transactions often involve multiple participants flexibly splitting revenue according to real-time dynamic transaction data, requiring the immediate generation of independent financial vouchers for each party to ensure clear accounting and real-time settlement.

[0003] However, existing financial voucher generation systems generally suffer from rigid mappings between accounting rules and subjects when handling such complex accounting transactions. These systems typically pre-define accounting rules as fixed logic, making it difficult to dynamically adjust the mapping between accounting parameters and subjects based on actual transaction attributes during the business process. Due to this lack of flexibility in adapting to dynamic accounting scenarios, when there are multi-level accounting entries or temporary changes to the accounting scheme, the system cannot automatically and accurately break down a transaction amount into multiple accounting entries for multiple accounting entities, still requiring manual adjustments and post-entry updates. This approach not only increases the risk of delays and errors in financial processing but also fails to meet the high-frequency, real-time accounting management needs of retail businesses. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a financial voucher generation system and method based on retail business, which solves the problems of rigid mapping between accounting rules and accounting subjects, reliance on manual adjustment and supplementation leading to delays and errors in financial processing, and inability to meet the real-time requirements of complex retail accounting business.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for generating financial vouchers based on retail business, comprising:

[0006] S1. Obtain retail transaction data, wherein the retail transaction data includes transaction amount and at least one transaction attribute information;

[0007] S2. Based on transaction attribute information, dynamically match the corresponding accounting rules from the preset accounting rule library; the accounting rules define the amount allocation logic among multiple accounting entities;

[0008] S3. Based on the accounting rules and transaction attribute information, dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library; the accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects;

[0009] S4. Based on the accounting rules and the mapping relationship of accounting subjects, the transaction amount is decomposed to obtain the accounting entries corresponding to each of the multiple accounting entities;

[0010] S5. Based on the accounting entries, generate separate financial vouchers for each of the aforementioned accounting entities.

[0011] Furthermore, the acquisition of retail transaction data includes:

[0012] The system receives sales order data, return order data, or cross-channel settlement data from the retail operation platform. The data includes transaction serial number, transaction time, transaction channel, product category, sales quantity, transaction amount, payment method, customer identifier, customer type, and multiple accounting entity identifiers participating in the revenue sharing. The accounting entity identifiers include the platform, supplier, store, or distributor identifiers.

[0013] Furthermore, the step of dynamically matching corresponding revenue sharing rules from a preset revenue sharing rule base based on transaction attribute information includes:

[0014] Based on the transaction type, transaction channel, product category, or accounting entity identifier in the transaction attribute information, search the accounting rule base for one or more accounting rules that match the transaction attribute information;

[0015] When multiple matching revenue sharing rules exist, a unique matching revenue sharing rule is determined based on the preset rule priority, effective date, or business scenario type.

[0016] Furthermore, the step of dynamically determining the corresponding accounting subject mapping relationship from a preset accounting subject mapping library based on accounting rules and transaction attribute information includes:

[0017] Based on the transaction type, transaction channel, or accounting entity identifier in the adapted accounting rule identifier and transaction attribute information, query the accounting subject mapping configuration associated with the accounting rule identifier and transaction attribute information in the accounting subject mapping library;

[0018] The accounting subject mapping configuration associates the sub-account business type, accounting item, debit accounting subject code, credit accounting subject code and auxiliary accounting item.

[0019] Furthermore, the revenue sharing rules are defined as follows:

[0020] Fixed percentage revenue sharing rules are used to split the transaction amount according to a preset percentage or a fixed amount.

[0021] Tiered revenue sharing rules are used to apply different splitting ratios based on a preset range in which the transaction amount falls;

[0022] The revenue sharing rules by product category are used to allocate the transaction amount based on the category or brand of the products sold in the retail transaction data;

[0023] The revenue sharing rules based on the roles of participating parties are used to allocate amounts according to the roles of the multiple accounting entities in the retail business, such as platform providers, suppliers, or distributors.

[0024] Furthermore, the accounting subject mapping relationship includes:

[0025] Map the sales revenue items in the aforementioned accounting entries to the main business revenue or business revenue accounting subjects;

[0026] Map the expense categories in the aforementioned accounting entries to the accounting subjects of sales expenses, administrative expenses, or financial expenses;

[0027] Map the accounts receivable category in the aforementioned accounting entries to the accounts receivable or prepayment accounting subjects;

[0028] Map the accounts payable items in the accounting entries to the accounts payable or accounts receivable accounting subjects.

[0029] Furthermore, the breakdown of the transaction amount yields accounting entries for multiple accounting entities, including:

[0030] Based on the appropriate revenue sharing rules, and in conjunction with the transaction amount and other transaction attributes, calculate the debit and credit amounts that each accounting entity should receive;

[0031] The calculated debit and credit amounts are combined with the preset accounting subject mapping relationship to generate a set of accounting entries containing voucher date, summary, subject code, debit and credit amounts and auxiliary accounting information;

[0032] The auxiliary accounting information includes customer, supplier, department, project, or business unit information.

[0033] Furthermore, the generation of independent financial documents for multiple accounting entities includes:

[0034] For each accounting entity, based on its corresponding set of accounting entries, the system automatically fills in the voucher date, voucher number, summary, total debit and credit amounts, accounting subject codes for each journal entry, auxiliary accounting items and amounts, and generates an independent draft financial voucher.

[0035] The draft financial documents are subject to compliance verification, which includes verification of debit and credit balance, verification of account legality, and verification of document completeness.

[0036] Once the draft financial document passes verification, it is submitted to generate the official financial document and archived.

[0037] Furthermore, the method also includes:

[0038] Configure and maintain the revenue sharing rule base and the accounting subject mapping base through the user interface. Maintenance operations include adding, modifying, deleting, enabling or disabling revenue sharing rules or accounting subject mapping relationships.

[0039] The revenue sharing rule base and accounting subject mapping base support version management to record, audit, and trace historical configuration information and change history.

[0040] The present invention also provides a financial document generation system based on retail business, applied to any of the above-described financial document generation methods based on retail business, comprising:

[0041] The data acquisition module is used to acquire retail transaction data, which includes transaction amount and at least one transaction attribute information;

[0042] The rule matching module is used to dynamically match the corresponding accounting rules from the preset accounting rule library based on transaction attribute information. The accounting rules define the amount allocation logic among multiple accounting entities.

[0043] The mapping determination module is used to dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library based on the accounting rules and transaction attribute information. The accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects.

[0044] The amount decomposition module is used to decompose the transaction amount according to the accounting rules and the mapping relationship of accounting subjects, so as to obtain the accounting entries corresponding to multiple accounting entities.

[0045] The voucher generation module is used to generate multiple independent financial vouchers for each of the accounting entities based on the accounting entries.

[0046] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0047] This invention acquires retail transaction data containing transaction amounts and multi-dimensional transaction attributes. Based on these transaction attributes, it dynamically matches and adapts accounting rules from a pre-set accounting rule library, solving the problem of rigid accounting rules in existing systems. Then, it dynamically determines the account mapping relationship from an accounting account mapping library, addressing the issue of fixed account mappings, by combining the accounting rules and transaction attributes. Subsequently, it automatically decomposes transaction amounts into multi-accounting entity accounting entries based on the accounting rules and account mapping relationships, thereby generating independent financial vouchers for each entity and completing compliance verification and archiving. It also supports maintaining the accounting rule library and account mapping library through a user interface and provides version management. This solution eliminates the need for manual post-event adjustments and supplementary entries, reducing financial processing delays and error risks, meeting the high-frequency real-time accounting needs of retail businesses, improving financial processing efficiency and compliance, ensuring clear multi-entity accounting, and offering flexible rule and mapping configurations for easy auditing and historical information review. Attached Figure Description

[0048] Figure 1 This is a flowchart of the method of the present invention;

[0049] Figure 2 This is a system structure diagram of the present invention. Detailed Implementation

[0050] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0051] Please see Figure 1 This invention provides a method for generating financial vouchers based on retail business, comprising:

[0052] S1. Obtain retail transaction data, which includes transaction amount and at least one transaction attribute information;

[0053] S2. Based on transaction attribute information, dynamically match the corresponding accounting rules from the preset accounting rule library; the accounting rules define the amount allocation logic among multiple accounting entities;

[0054] S3. Based on the accounting rules and transaction attribute information, dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library; the accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects;

[0055] S4. Based on the accounting rules and the mapping relationship of accounting subjects, the transaction amount is decomposed to obtain the accounting entries corresponding to each of the multiple accounting entities;

[0056] S5. Based on accounting entries, generate independent financial vouchers for multiple accounting entities.

[0057] Specifically, taking a cross-channel joint retail scenario as an example, this scenario involves three accounting entities: the platform, the supplier, and the offline store. It requires handling the home appliance sales business that links the online mall with offline stores, addressing the issues of rigid accounting rules, fixed account mappings, and reliance on manual data entry in the existing system. First, retail transaction data is acquired. The system connects to the online mall operation platform and the offline store POS system, receiving a home appliance sales transaction in real time. The transaction amount is 10,000 yuan, and the transaction attribute information includes: transaction type is joint sales, transaction channel is online-offline linkage, product category is large home appliance, customer identifier is C001, and the accounting entity identifiers participating in the accounting are platform P001, supplier S001, and store M001. Next, the system dynamically matches the revenue sharing rules. It extracts the transaction type, product category, and accounting entity identifier from the transaction attributes and searches the preset revenue sharing rule library. Two relevant rules are found: one is a regular home appliance joint venture revenue sharing rule effective in January 2023, and the other is a 2024 quarterly home appliance joint promotion revenue sharing rule effective in April 2024. Based on the priority logic of the effective date, the quarterly promotion revenue sharing rule with the updated effective date is selected. This rule defines that the platform receives 12% of the transaction amount, the supplier receives 78%, and the store receives 10%. Then, the accounting subject mapping relationship is determined. Based on the selected quarterly promotion revenue sharing rule identifier and the transaction type in the transaction attributes, the system queries the associated configuration in the accounting subject mapping library to obtain the correspondence between the revenue sharing results and the accounting subjects. That is, the platform's revenue sharing amount is mapped to the main business revenue subject, the supplier's revenue sharing amount is mapped to the accounts payable subject, and the store's revenue sharing amount is mapped to the accounts payable subject. All of these are auxiliary accounting items for related customer C001, supplier S001, and store M001. The system breaks down the transaction amount and calculates the amount for each accounting entity according to the accounting rules. The platform's accounting amount is 10,000 × 12% = 1,200 yuan, the supplier's is 10,000 × 78% = 7,800 yuan, and the store's is 10,000 × 10% = 1,000 yuan. Combining the account mapping relationship, a set of accounting entries is generated. Each entry includes the voucher date as the transaction date May 20, 2024, the summary as online and offline linkage home appliance sales accounting, the account code such as the platform's main business revenue code 6001, the supplier's accounts payable code 2202, the debit and credit amounts, and the corresponding auxiliary accounting information. Finally, independent financial vouchers are generated. The system extracts the corresponding accounting entries for each accounting entity and automatically fills in the voucher elements. For the platform, a financial voucher is generated with a debit of RMB 1,200 for the Bank Deposit 1002 account and a credit of RMB 1,200 for the Main Business Revenue 6001 account. For the supplier, a financial voucher is generated with a debit of RMB 7,800 for the Main Business Cost 6401 account and a credit of RMB 7,800 for the Accounts Payable 2202 account. For the store, a financial voucher is generated with a debit of RMB 1,000 for the Main Business Cost 6401 account and a credit of RMB 1,000 for the Accounts Payable 2202 account.

[0058] In this embodiment, acquiring retail transaction data includes:

[0059] It receives sales order data, return order data, or cross-channel settlement data from the retail operation platform. The data includes transaction serial number, transaction time, transaction channel, product category, sales quantity, transaction amount, payment method, customer identifier, customer type, and multiple accounting entity identifiers participating in the revenue sharing. The accounting entity identifiers include the platform, supplier, store, or distributor identifiers.

[0060] Specifically, taking the omnichannel business scenario of retail enterprises as an example, when the system acquires retail transaction data, it simultaneously connects to multiple data ports both online and offline. Sales order data originates from the enterprise's online mini-program operation platform. For instance, if a customer places an order for 3 food items through the mini-program, the order data received by the system includes transaction serial number 20240520003, transaction time May 20, 2024, 2:30 PM, transaction channel: mini-program, product category: food, quantity: 3, transaction amount: 300 yuan, payment method: WeChat Pay, customer identifier: K008, customer type: member, accounting entity identifier for revenue sharing: platform P001, food supplier S003, offline delivery store M002. Return order data originates from the offline store's POS system. For example, if a customer returns 1 piece of clothing purchased last month, the return... The order data includes transaction serial number 20240520004, transaction time 16:10 on May 20, 2024, transaction channel: offline store, product category: clothing, transaction amount: negative 200 yuan, payment method: refund via the original payment path, customer identifier: K005, customer type: ordinary customer, and accounting entity identifiers for revenue sharing: platform P001, clothing supplier S002, and offline store M001. The cross-channel settlement data comes from the settlement system of the company's monthly online and offline joint promotional activities, including information such as the adjustment records of the revenue sharing ratio of the total transaction amount of each participant during the promotion period. The accounting entity identifiers cover all platform regional suppliers and stores participating in the promotion.

[0061] In this embodiment, based on transaction attribute information, the corresponding revenue sharing rules are dynamically matched from a preset revenue sharing rule base, including:

[0062] Based on the transaction type, transaction channel, category of goods sold, or accounting entity identifier in the transaction attribute information, search for one or more accounting rules that match the transaction attribute information in the accounting rule base;

[0063] When multiple matching revenue sharing rules exist, a unique matching revenue sharing rule is determined based on the preset rule priority, effective date, or business scenario type.

[0064] Specifically, taking a retail company's seasonal promotional business as an example, when the system obtains transaction data with the following attributes: transaction type: promotional activity; transaction channel: online APP; product category: digital products; accounting entity identifier: platform P001, digital supplier S005, offline experience store M003, the system initiates the revenue sharing rule matching process. The system first searches the revenue sharing rule database based on the transaction type, product category, and accounting entity identifier in the transaction attributes. Initially, two rules are matched: one is a standard online sales revenue sharing rule for digital products, effective from January 2024, with the platform receiving 15%, the supplier 80%, and the experience store 5%; the other is a revenue sharing rule for digital product promotions in May 2024, effective from May 1, 2024, with the platform receiving 10%, the supplier 85%, and the experience store 5%. Because multiple matching rules exist, the system processes them according to a preset rule priority logic. First, it compares the effective dates of two rules. The promotional rule has a more up-to-date effective date, and its business scenario type perfectly matches the current transaction's promotional activity scenario. Therefore, the system determines the May 2024 digital product promotion revenue sharing rule as the only suitable revenue sharing rule. If two rules have the same effective date, the system further determines the matching rule based on the priority of the business scenario type. For example, promotional scenarios have higher priority than regular sales scenarios, ensuring that the matched revenue sharing rule highly matches actual business needs. This avoids revenue sharing errors due to rule conflicts and improves the accuracy and flexibility of revenue sharing rule application.

[0065] In this embodiment, based on the accounting rules and transaction attribute information, the corresponding accounting subject mapping relationship is dynamically determined from a preset accounting subject mapping library, including:

[0066] Based on the transaction type, transaction channel, or accounting entity identifier in the adapted accounting rule identifier and transaction attribute information, query the accounting subject mapping configuration associated with the accounting rule identifier and transaction attribute information in the accounting subject mapping library;

[0067] The accounting subject mapping configuration associates the sub-account business type, accounting item, debit accounting subject code, credit accounting subject code and auxiliary accounting item.

[0068] Specifically, following the aforementioned revenue sharing rules for digital product promotions in May 2024 (identified as CZSM202405), the system, combining the current transaction's attribute information and transaction type (promotional activity), transaction channel (online app), accounting entity identifiers (platform P001, supplier S005, and experience store M003), initiates a query process in the accounting subject mapping database. The system retrieves the associated accounting subject mapping configuration through a combination of rule identifier and transaction attributes. This configuration specifies revenue sharing for digital product promotions, with accounting items including platform promotion revenue, supplier promotion revenue, and experience store promotion revenue. The platform's promotional revenue is assigned the following debit codes: Bank Deposit 1002, Main Business Revenue 6001, and auxiliary accounting items: Platform P001 and Online APP Channel. Supplier promotional revenue sharing is assigned the following debit codes: Main Business Cost 6401, Accounts Payable 2202, and Supplier S005. Experience store promotional revenue sharing is assigned the following debit codes: Main Business Cost 6401, Accounts Payable 2202, and Experience Store M003. This mapping configuration precisely links the allocation results of the revenue sharing rules with specific accounting subjects. Simultaneously, auxiliary accounting items record business details, ensuring that subsequent accounting entries comply with accounting standards, avoiding confusion in subject mapping, and improving the accuracy and traceability of financial data.

[0069] In this embodiment, the revenue sharing rule is defined as follows:

[0070] Fixed percentage revenue sharing rules are used to split transaction amounts according to a preset percentage or a fixed amount.

[0071] Tiered profit-sharing rules are used to apply different splitting ratios based on the preset range of the transaction amount;

[0072] The revenue sharing rules by product category are used to allocate transaction amounts based on the category or brand of the products sold in retail transaction data;

[0073] The revenue sharing rules based on participant roles are used to allocate amounts according to the roles of multiple accounting entities in the retail business, such as platform providers, suppliers, or distributors.

[0074] Specifically, the revenue-sharing rules are applied differently depending on the retail business scenario. In scenarios where a fixed percentage revenue-sharing rule is applied, such as the regular sales of daily necessities, the rule is set so that the platform receives 8% of the transaction amount and the supplier receives 92%. The formula for calculating the revenue-sharing amount is as follows:

[0075] ;

[0076] in, Represents the split amount of the i-th accounting entity. Represents the total amount of retail transactions. Represents the preset split ratio corresponding to the i-th accounting entity. All parameter dimensions are in monetary units and no normalization is required. For example, for a daily necessities transaction with a total amount of 5000 yuan, the platform's split amount is 5000×8% = 400 yuan, and the supplier's split amount is 5000×92% = 4600 yuan.

[0077] In the application scenario of the tiered ratio split rule, for example, in the sales of home appliance products, the rule is set that when the transaction amount T≤10000 yuan, the platform splits 10%; when 10000 < T≤20000 yuan, the platform splits 12%; when T > 20000 yuan, the platform splits 15%. The supplier's split ratio is 1 minus the platform's split ratio. The calculation formula is:

[0078] ;

[0079] ;

[0080] Among them, Is the platform's split amount, Is the supplier's split amount, T is the total transaction amount, and the dimensions are all in monetary units. For example, for a home appliance transaction with a total amount of 15000 yuan, the platform's split amount is 15000×12% = 1800 yuan, and the supplier's split amount is 15000 - 1800 = 13200 yuan.

[0081] In the application scenario of the split rule by commodity category, for example, for clothing products, the supplier splits 85% and the platform splits 15%; for home appliance products, the supplier splits 80% and the platform splits 20%. The calculation formula is:

[0082] ;

[0083] ;

[0084] Among them, Is the supplier's split ratio for the corresponding commodity category, T is the total transaction amount, and the dimensions are all in monetary units. For example, for a clothing transaction with a total amount of 800 yuan, the supplier's split amount is 800×85% = 680 yuan, and the platform's split amount is 800×15% = 120 yuan.

[0085] In the application scenario of the split rule by participant role, for example, in the joint operation business, the platform role splits 10%, the supplier role splits 75%, and the store role splits 15%. The calculation formula is:

[0086] ;

[0087] Among them, For the accounting amount of the j-th role accounting entity, Let T be the revenue sharing percentage for the j-th role, and T be the total transaction amount. All units are in currency. For example, if the total transaction amount of a joint venture is 20,000 yuan, the platform will receive 20,000 × 10% = 2,000 yuan, the supplier will receive 20,000 × 75% = 15,000 yuan, and the store will receive 20,000 × 15% = 3,000 yuan.

[0088] Various revenue sharing rules can be flexibly invoked according to business needs, meeting the amount allocation requirements under different retail scenarios and avoiding the problem of poor business adaptability caused by a single rule.

[0089] In this embodiment, the accounting subject mapping relationship includes:

[0090] Map the sales revenue category in the accounting entries to the main business revenue or business revenue accounting subject;

[0091] Map the expense categories in the accounting entries to the accounting subjects of sales expenses, administrative expenses, or financial expenses;

[0092] Map the accounts receivable category in the accounting entries to the accounts receivable or prepayment accounting subjects;

[0093] Map the accounts payable items in the accounting entries to the accounts payable or accounts receivable accounting subjects.

[0094] Specifically, in the accounting entries for retail transactions, the mapping relationships between accounting subjects are applied precisely by category. For sales revenue items in the accounting entries, such as the commission income obtained by the platform from joint venture transactions and the sales revenue of self-operated goods by stores, they are all mapped to the corresponding revenue accounting subjects. Among them, the platform's commission income is mapped to the main business revenue subject, and the sales revenue of self-operated goods by stores is mapped to the business revenue subject, ensuring that the revenue accounting complies with accounting standards and clearly reflects the revenue composition of each entity.

[0095] For revenue-sharing expenditure items in the accounting entries, such as the revenue sharing paid by the platform to suppliers for goods and the revenue sharing paid to cooperative promotion partners for channels, they are mapped to different expense accounts according to the nature of the expenditure. The revenue sharing for goods is mapped to the sales expense account, the revenue sharing for channels is mapped to the management expense account, and if the revenue sharing expenditure involves funds lending, it is mapped to the financial expense account. This achieves accurate classification of expenditure items and facilitates subsequent expense analysis and control.

[0096] For accounts receivable items in the accounting entries, such as unpaid amounts from customers purchasing goods on credit and unsettled advances from partners, they are all mapped to the accounts receivable or prepayment accounts. Unpaid amounts from customers are mapped to the accounts receivable account, and advances from partners are mapped to the prepayment account, ensuring clear accounting of receivable assets and reducing the risk of fund recovery.

[0097] For accounts payable items in the accounting entries, such as platform payments to suppliers for product revenue sharing and payments to stores for service fees, these are mapped to accounts payable or accounts receivable accounts. Specifically, supplier product revenue sharing is mapped to accounts payable, while store service fees, if collected in advance, are mapped to accounts receivable accounts. This ensures standardized accounting for liabilities and maintains a good cooperative reputation for the company. Through this mapping, the accounting entries are ensured to accurately correspond to the accounting subjects, reducing manual adjustments and improving the efficiency and accuracy of financial accounting.

[0098] In this embodiment, the transaction amount is broken down to obtain accounting entries corresponding to multiple accounting entities, including:

[0099] Based on the appropriate accounting rules, and taking into account the transaction amount and other transaction attributes, calculate the amount of debit and credit that each accounting entity should receive;

[0100] The calculated debit and credit amounts are combined with the preset accounting subject mapping relationship to generate a set of accounting entries containing voucher date, summary, subject code, debit and credit amounts and auxiliary accounting information;

[0101] The auxiliary accounting information includes customer, supplier, department, project or business unit information.

[0102] Specifically, taking a cross-channel home appliance sales transaction as an example, the transaction amount is 20,000 yuan, and the applicable revenue sharing rules are: platform revenue sharing 12%, supplier revenue sharing 80%, and store revenue sharing 8%. The transaction attributes include the transaction date May 21, 2024, the transaction summary cross-channel home appliance sales, customer identifier C006, supplier identifier S004, and store identifier M004. The system first calculates the debit and credit amounts for each accounting entity based on the revenue sharing rules and the transaction amount. The platform's revenue sharing amount is 20,000 × 12% = 2,400 yuan, the supplier's revenue sharing amount is 20,000 × 80% = 16,000 yuan, and the store's revenue sharing amount is 20,000 × 8% = 1,600 yuan.

[0103] Next, combined with the preset accounting subject mapping relationship, a set of accounting entries is generated. The accounting entries of the platform party include voucher date May 21, 2024, abstract cross-channel home appliance sales revenue sharing, debit subject code 1002 Bank deposits 2,400 yuan, credit 6001 Main business income 2,400 yuan, auxiliary accounting information customer C006, platform party P001; the accounting entries of the supplier include voucher date May 21, 2024, abstract payable cross-channel home appliance supplier share, debit subject code 6401 Main business cost 16,000 yuan, credit 2202 Accounts payable 16,000 yuan, auxiliary accounting information supplier S004; the accounting entries of the store include voucher date May 21, 2024, abstract payable cross-channel home appliance store share, debit subject code 6401 Main business cost 1,600 yuan, credit 2202 Accounts payable 1,600 yuan, auxiliary accounting information store M004.

[0104] Each accounting entry contains complete accounting elements, and the auxiliary accounting information covers the key entities related to the business, providing detailed data support for the subsequent generation of independent financial vouchers, while ensuring that the accounting entries of each entity are logically clear and the data is accurate, avoiding voucher generation errors caused by missing information.

[0105] In this embodiment, independent financial vouchers for each accounting entity are generated, including:

[0106] For each accounting entity, based on its corresponding set of accounting entries, the voucher date, voucher number, abstract, total debit and credit amounts, accounting subject codes of each entry item, auxiliary accounting items and amounts are automatically filled to generate a draft of the independent financial voucher;

[0107] Perform compliance checks on the draft financial vouchers, including debit and credit balance checks, subject legality checks and voucher integrity checks;

[0108] When the draft financial voucher passes the check, submit it to generate a formal financial voucher and file it.

[0109] Specifically, for the set of accounting entries of the above three accounting entities generated, the system starts the independent financial voucher generation process. For the platform party P001, the system extracts its accounting entries and automatically fills in the financial voucher elements. The voucher date is May 21, 2024, the voucher number is Jizi 20240521001, the abstract is cross-channel home appliance sales revenue sharing, the total debit and credit amounts are both 2,400 yuan, the entry items are debit 1002 Bank deposits 2,400 yuan, credit 6001 Main business income 2,400 yuan, and the auxiliary accounting item is customer C006 platform party P001, generating a draft financial voucher for the platform party.

[0110] The system then performs a compliance check on the draft. First, it checks the balance between debits and credits, finding that the total debit amount of 2400 yuan is equal to the total credit amount of 2400 yuan, thus passing the check. Next, it checks the legality of the accounts, finding that account codes 1002 and 6001 are both legal accounting accounts preset by the company, thus passing the check. Finally, it checks the completeness of the voucher, finding that the voucher date, serial number, summary, account code, amount, and auxiliary accounting items are all complete, thus passing the check.

[0111] Similarly, the system generates a draft financial voucher for supplier S004, dated May 21, 2024, with document number 20240521002. The summary states "Accounts Payable to Cross-Channel Home Appliance Suppliers," with a total debit and credit amount of 16,000 yuan. The journal entries are: Debit 6401 "Main Business Costs" (16,000 yuan) and Credit 2202 "Accounts Payable" (16,000 yuan). The auxiliary accounting item is "Supplier S004." After compliance verification, a formal voucher is generated. A draft financial voucher is also generated for store M004 after verification. Finally, the system automatically archives the three formal financial vouchers to the enterprise financial voucher management system for easy subsequent retrieval and auditing. This process automates voucher generation and ensures compliance control, avoiding oversights from manual verification and improving the efficiency and compliance of voucher generation.

[0112] In this embodiment, the method further includes:

[0113] Configure and maintain the revenue sharing rule base and accounting subject mapping base through the user interface. Maintenance operations include adding, modifying, deleting, enabling or disabling revenue sharing rules or accounting subject mapping relationships.

[0114] The revenue sharing rules library and accounting subject mapping library support version management to record, audit, and trace historical configuration information and change history.

[0115] Specifically, the system provides administrators with maintenance functions for the revenue sharing rule library and accounting subject mapping library through a visual user interface. After logging into the system, administrators can add temporary revenue sharing rules for the 618 promotion in the revenue sharing rule management module, setting the rule name as "618 Digital Promotion Revenue Sharing," the effective date as June 1 to June 20, 2024, and the revenue sharing ratio as follows: platform 8%, supplier 87%, and store 5%. Administrators can also modify the ratio of regular apparel revenue sharing rules, adjusting the platform's share from 15% to 12%. Expired 2024 Spring Festival promotion revenue sharing rules can be deleted. Furthermore, administrators can enable newly added summer beverage promotion revenue sharing rules or disable temporarily suspended regional store revenue sharing rules based on business needs.

[0116] In the accounting subject mapping library management module, administrators can add subject mapping configurations associated with the 618 promotion revenue sharing rules, mapping the platform's promotion revenue to the promotion revenue details under the main business revenue account; they can modify the auxiliary accounting items of the accounts payable account corresponding to supplier revenue sharing, and add regional attributes; and they can delete mapping configurations associated with disabled revenue sharing rules.

[0117] Meanwhile, the system manages all operations in the revenue sharing rule base and accounting subject mapping base using version control. Each maintenance operation generates a new version number and records the maintenance personnel's name, maintenance time, and maintenance content. For example, version V3.2 records the maintenance personnel as Li Si, the maintenance time as May 25, 2024, and the maintenance content as the addition of revenue sharing rules and associated subject mappings for the 618 digital promotion. Administrators can use the version management function to query historical configuration information, trace change paths, facilitate financial auditing and problem troubleshooting, ensure that changes to rule and mapping configurations are traceable and controllable, and improve the standardization of system operation and maintenance.

[0118] Please see Figure 2 The present invention also provides a financial voucher generation system based on retail business, comprising:

[0119] The data acquisition module is used to acquire retail transaction data, which includes transaction amount and at least one transaction attribute information;

[0120] The rule matching module is used to dynamically match the corresponding accounting rules from the preset accounting rule library based on transaction attribute information. The accounting rules define the amount allocation logic among multiple accounting entities.

[0121] The mapping determination module is used to dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library based on the accounting rules and transaction attribute information. The accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects.

[0122] The amount decomposition module is used to decompose the transaction amount according to the accounting rules and the mapping relationship of accounting subjects, so as to obtain the accounting entries corresponding to multiple accounting entities.

[0123] The voucher generation module is used to generate independent financial vouchers for multiple accounting entities based on accounting entries.

[0124] Specifically, the system operates its various modules collaboratively in actual retail business. The data acquisition module connects to the enterprise's online store mini-program, offline store POS system, and cross-channel settlement system via API interfaces, receiving retail transaction data such as sales orders, return slips, and cross-channel settlements in real time. After standardizing the data format, it is transmitted to the rule matching module.

[0125] The rule matching module receives transaction data transmitted by the data acquisition module, extracts transaction attribute information, calls the built-in rule matching algorithm, and searches for matching revenue sharing rules in the preset revenue sharing rule library. If multiple matching rules exist, the module determines the rule based on rule priority, effective date, and business scenario type, outputs a uniquely suitable revenue sharing rule, and simultaneously transmits the rule identifier and transaction attribute information to the mapping determination module.

[0126] The mapping determination module performs a combined query in the accounting subject mapping library based on the rule identifier and transaction attribute information transmitted by the rule matching module to obtain the associated accounting subject mapping configuration, including the debit and credit account codes and auxiliary accounting items for the accounting sub-items of the split account business type, and then transmits the mapping configuration to the amount decomposition module.

[0127] The amount decomposition module receives the transaction amount from the accounting rule mapping configuration and transaction data, calculates the accounting amount for each accounting entity according to the accounting rule, and generates a set of accounting entries containing complete accounting elements by combining the accounting subject mapping configuration, and transmits it to the voucher generation module.

[0128] The voucher generation module extracts the set of accounting entries corresponding to each accounting entity, calls the financial voucher template to automatically fill in the voucher elements, generates a draft financial voucher, performs a check on the draft to verify the legality and completeness of the debit and credit balance accounts, and generates and archives the formal financial voucher after the check passes. These modules work together to automate the entire process from retail transaction data to independent financial vouchers, improving the efficiency and accuracy of financial processing and meeting the financial accounting needs of complex retail businesses involving multiple entities.

[0129] In summary, this invention acquires retail transaction data containing transaction amounts and multi-dimensional transaction attributes. Based on these transaction attributes, it dynamically matches and adapts accounting rules from a pre-set accounting rule library, solving the problem of rigid accounting rules in existing systems. Furthermore, it dynamically determines account mapping relationships from an accounting subject mapping library by combining accounting rules and transaction attributes, addressing the issue of fixed account mappings. Subsequently, based on the accounting rules and account mapping relationships, it automatically decomposes transaction amounts to generate accounting entries for multiple accounting entities, thereby generating independent financial vouchers for each entity and completing compliance verification and archiving. It also supports maintaining the accounting rule library and account mapping library through a user interface and provides version management. This solution eliminates the need for manual post-event adjustments and supplementary entries, reducing financial processing delays and error risks, meeting the high-frequency, real-time accounting needs of retail businesses, improving financial processing efficiency and compliance, ensuring clear multi-entity accounting, and offering flexible rule and mapping configurations for easy auditing and historical information review.

[0130] 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 process, method, article, or apparatus.

[0131] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for generating financial vouchers based on retail business, characterized in that, include: S1. Obtain retail transaction data, wherein the retail transaction data includes transaction amount and at least one transaction attribute information; S2. Based on transaction attribute information, dynamically match the corresponding accounting rules from the preset accounting rule library; the accounting rules define the amount allocation logic among multiple accounting entities; S3. Based on the accounting rules and transaction attribute information, dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library; the accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects; S4. Based on the accounting rules and the mapping relationship of accounting subjects, the transaction amount is decomposed to obtain the accounting entries corresponding to each of the multiple accounting entities; S5. Based on the accounting entries, generate separate financial vouchers for each of the aforementioned accounting entities.

2. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The acquisition of retail transaction data includes: The system receives sales order data, return order data, or cross-channel settlement data from the retail operation platform. The data includes transaction serial number, transaction time, transaction channel, product category, sales quantity, transaction amount, payment method, customer identifier, customer type, and multiple accounting entity identifiers participating in the revenue sharing. The accounting entity identifiers include the platform, supplier, store, or distributor identifiers.

3. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The step of dynamically matching corresponding revenue sharing rules from a preset revenue sharing rule library based on transaction attribute information includes: Based on the transaction type, transaction channel, product category, or accounting entity identifier in the transaction attribute information, search the accounting rule base for one or more accounting rules that match the transaction attribute information; When multiple matching revenue sharing rules exist, a unique matching revenue sharing rule is determined based on the preset rule priority, effective date, or business scenario type.

4. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The step of dynamically determining the corresponding accounting subject mapping relationship from a preset accounting subject mapping library based on accounting rules and transaction attribute information includes: Based on the transaction type, transaction channel, or accounting entity identifier in the adapted accounting rule identifier and transaction attribute information, query the accounting subject mapping configuration associated with the accounting rule identifier and transaction attribute information in the accounting subject mapping library; The accounting subject mapping configuration associates the sub-account business type, accounting item, debit accounting subject code, credit accounting subject code and auxiliary accounting item.

5. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The revenue sharing rules are defined as follows: Fixed percentage revenue sharing rules are used to split the transaction amount according to a preset percentage or a fixed amount. Tiered revenue sharing rules are used to apply different splitting ratios based on a preset range in which the transaction amount falls; The revenue sharing rules by product category are used to allocate the transaction amount based on the category or brand of the products sold in the retail transaction data; The revenue sharing rules based on the roles of participating parties are used to allocate amounts according to the roles of the multiple accounting entities in the retail business, such as platform providers, suppliers, or distributors.

6. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The accounting subject mapping relationship includes: Map the sales revenue items in the aforementioned accounting entries to the main business revenue or business revenue accounting subjects; Map the expense categories in the aforementioned accounting entries to the accounting subjects of sales expenses, administrative expenses, or financial expenses; Map the accounts receivable category in the aforementioned accounting entries to the accounts receivable or prepayment accounting subjects; Map the accounts payable items in the accounting entries to the accounts payable or accounts receivable accounting subjects.

7. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The process of breaking down the transaction amount yields accounting entries for multiple accounting entities, including: Based on the appropriate revenue sharing rules, and in conjunction with the transaction amount and other transaction attributes, calculate the debit and credit amounts that each accounting entity should receive; The calculated debit and credit amounts are combined with the preset accounting subject mapping relationship to generate a set of accounting entries containing voucher date, summary, subject code, debit and credit amounts and auxiliary accounting information; The auxiliary accounting information includes customer, supplier, department, project, or business unit information.

8. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The generation of independent financial documents for multiple accounting entities includes: For each accounting entity, based on its corresponding set of accounting entries, the system automatically fills in the voucher date, voucher number, summary, total debit and credit amounts, accounting subject codes for each journal entry, auxiliary accounting items and amounts, and generates an independent draft financial voucher. The draft financial documents are subject to compliance verification, which includes verification of debit and credit balance, verification of account legality, and verification of document completeness. Once the draft financial document passes verification, it is submitted to generate the official financial document and archived.

9. The method for generating financial vouchers based on retail business according to claim 1, characterized in that, The method also includes: Configure and maintain the revenue sharing rule base and the accounting subject mapping base through the user interface. Maintenance operations include adding, modifying, deleting, enabling or disabling revenue sharing rules or accounting subject mapping relationships. The revenue sharing rule base and accounting subject mapping base support version management to record, audit, and trace historical configuration information and change history.

10. A financial voucher generation system based on retail business, applied to the financial voucher generation method based on retail business as described in any one of claims 1-9, characterized in that, include: The data acquisition module is used to acquire retail transaction data, which includes transaction amount and at least one transaction attribute information; The rule matching module is used to dynamically match the corresponding accounting rules from the preset accounting rule library based on transaction attribute information. The accounting rules define the amount allocation logic among multiple accounting entities. The mapping determination module is used to dynamically determine the corresponding accounting subject mapping relationship from the preset accounting subject mapping library based on the accounting rules and transaction attribute information. The accounting subject mapping relationship defines the correspondence between the accounting results and multiple accounting subjects. The amount decomposition module is used to decompose the transaction amount according to the accounting rules and the mapping relationship of accounting subjects, so as to obtain the accounting entries corresponding to multiple accounting entities. The voucher generation module is used to generate multiple independent financial vouchers for each of the accounting entities based on the accounting entries.

Images