Advertisement expense automatic reconciliation and payment processing method based on special invoice of value-added tax

Abstract

The present application relates to the technical field of data processing of advertisement expense settlement and invoice verification, and particularly relates to an advertisement expense automatic reconciliation and payment processing method based on special value-added tax invoice. The method comprises the following steps: receiving special value-added tax invoice electronic files or scanning images, advertisement distribution platform account numbers, configuration relations, advertisement expense application rules and account period states, and generating an account ticket verification request; forming invoice content and invoice characteristic values through graphic recognition and text recognition, and obtaining alliance promotion data, self-owned station promotion data and settlement expense data to generate communication summary data; screening advertisement expense reconciliation bill data, generating account ticket to-be-processed credentials, generating over-account approval results through classification, repeated data filtering and one-by-one comparison, creating payment credentials in combination with authenticated invoice verification, and generating payment information. The present application effectively improves the automation level of ticket account matching, invoice verification, payment processing and record tracing.

Description

Technical Field

[0001] This invention relates to the field of data processing technology for advertising expense settlement and invoice verification, and in particular to a method for automatic reconciliation and payment processing of advertising expenses based on value-added tax invoices. Background Technology

[0002] In the field of data processing technology for advertising expense settlement and invoice verification, existing solutions typically involve manually receiving electronic files or scanned images of VAT invoices, followed by the management backend module reading the invoice information and verifying it against affiliate promotion data, proprietary site promotion data, and settlement fee data returned by the advertising distribution platform. This approach suffers from limitations such as unclear correlation between invoice content and communication summary data, insufficient involvement of configuration relationships and advertising fee application rules, and loose connection between payment period status and payment vouchers. Existing methods often rely on direct matching of invoice content with existing invoices, or on individual comparisons of amounts, tax rates, seller financial information, and buyer financial information, resulting in fragmented criteria for filtering advertising expense reconciliation data.

[0003] In scenarios where advertising distribution platforms, advertising fee application rules, and billing status all participate in advertising fee settlement, affiliate promotion data, proprietary site promotion data, and settlement fee data are typically distributed across different processing records. The seller's name, seller's taxpayer identification number, buyer's name, buyer's taxpayer identification number, amount, tax rate, tax amount, total price including tax, and remarks in the invoice content often cannot be directly correlated with the source data of the advertising fees. This situation easily leads to mismatches between invoice content and settlement fee data, and duplicate data entering subsequent payment voucher processing, making it difficult to meet the needs of continuous processing of advertising fee reconciliation data, pending invoices, posting approval results, and payment information.

[0004] For the joint processing of communication summary data and invoice content, existing technologies generally lack a processing link for reverse filtering of advertising expense reconciliation data from invoice content, and also lack a unified process for classifying, filtering duplicate data, and comparing one by one the pending vouchers for invoices. Existing processing flows struggle to establish a consistent workflow for receiving, identifying, filtering, comparing, verifying, paying, updating, and recording in scenarios involving automatic advertising expense reconciliation and payment processing. This results in incomplete correlation between posting approval results and subsequent certified invoices, payment vouchers, and payment period status. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a method for automatic reconciliation and payment processing of advertising expenses based on value-added tax (VAT) invoices, comprising:

[0006] S100: Receive electronic files or scanned images of VAT special invoices, advertising distribution platform accounts, configuration relationships, advertising fee application rules and billing status, and generate an invoice verification request.

[0007] S200: Based on the invoice verification request, perform graphic recognition and text recognition, read the invoice information, and generate invoice content and invoice feature values;

[0008] S300. Based on the invoice content and the invoice feature value, send a scheduled task instruction to the advertising distribution platform to obtain alliance promotion data, own site promotion data and settlement fee data, and generate communication summary data.

[0009] S400: Based on the communication summary data and the invoice content, filter the advertising expense statement data and generate an invoice pending processing voucher;

[0010] S500: Based on the classification of the pending vouchers, filter duplicate data, compare them one by one, and generate posting approval results;

[0011] S600: Based on the posting approval result and the invoice feature value, obtain the certified invoice, check for red-inked and duplicate data, and generate the invoice verification result;

[0012] S700: Based on the invoice verification result, create a payment voucher, send the payment voucher to the financial institution interface, and generate payment information;

[0013] S800: Receive settlement results based on the payment information, update the billing status, and generate system logs.

[0014] Furthermore, in S200, the electronic file or scanned image of the VAT special invoice is subjected to format recognition, orientation correction, edge cropping, clarity processing, and data cleaning to remove missing key information; the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, and seller's taxpayer identification number are read to form the invoice content and the invoice feature value.

[0015] Furthermore, in S300, the cloud cross-database access module accesses each advertising distribution platform according to the scheduled task instructions, obtains the advertising content, advertising playback plan, advertising plan budget, daily percentage limit corresponding to advertising, advertising creative content, configuration relationship, advertising view clicks, advertising traffic and settlement fee data of each advertising distribution platform, and writes the obtained data into the communication summary data.

[0016] Further, in S400, filtering the advertising expense reconciliation data includes: comparing the seller's name and taxpayer identification number in the invoice content with the advertising distribution platform account; comparing the buyer's name and taxpayer identification number in the invoice content with the configuration relationship; comparing the amount, tax rate, tax amount, and total price including tax in the invoice content with the settlement expense data; comparing the remarks in the invoice content with the payment period status; and extracting the advertising expense reconciliation data.

[0017] Furthermore, in S500, the classification includes single settlement fee data corresponding to a single advertising distribution platform, single invoice content corresponding to different advertising distribution platforms, different billing periods corresponding to a single advertising distribution platform, and single settlement fee data corresponding to different invoice contents; the comparison includes tax rate, amount, seller's financial information, buyer's financial information, configuration relationship, advertising fee application rules, and settlement fee data comparison.

[0018] Furthermore, in S600, an authenticated invoice is downloaded from the cloud platform system for digital invoice lifecycle management authorized by the tax bureau based on the invoice feature value; if the authenticated invoice is inconsistent with the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's taxpayer identification number or seller's taxpayer identification number in the invoice content, or if the authenticated invoice has been cancelled, an unqualified invoice verification result is generated.

[0019] Furthermore, in S700, before creating the payment voucher, the invoice feature value, the advertising expense statement data, the payment voucher, and the payment information are filtered for duplicate data; when the payment information indicates successful payment, the sending of the payment voucher to the financial institution interface is stopped; when the payment information indicates payment failure, the payment voucher is retained and payment status tracking continues.

[0020] Furthermore, in S800, the system log records the invoice content reading process, the advertising expense statement data filtering process, the invoice pending processing voucher classification process, the posting approval result generation process, the certified invoice acquisition process, the payment voucher creation process, the payment information generation process, and the settlement result receiving process.

[0021] Furthermore, the abnormal alarm status includes missing key information in the invoice content, inconsistent certified invoices, invoices that have been reversed, duplicate data, unqualified posting approval, payment vouchers that have been successfully paid, and payment failure; the result feedback module writes the abnormal alarm status into the system log.

[0022] Furthermore, in S800, when the settlement result is a successful payment, the settlement fee data, payment voucher, payment information, and billing status from the advertising fee statement data are written into the data storage module; when the settlement result is a failed payment, the payment voucher, payment information, and abnormal alarm status are written into the data storage module.

[0023] The key innovations of this invention include:

[0024] (1) Based on the communication summary data and the invoice content, filter the advertising expense statement data and generate the bill of invoice pending processing voucher, and incorporate the advertising distribution platform account, configuration relationship, advertising fee application rules, billing period status, alliance promotion data, self-owned site promotion data and settlement fee data into the same processing process.

[0025] (2) Based on the pending vouchers, classify, filter duplicate data and compare them one by one to generate posting approval results, so that tax rate, amount, seller's financial information, buyer's financial information, configuration relationship, advertising fee application rules and settlement fee data enter the posting approval process together.

[0026] (3) Based on the posting approval result and the invoice feature value, obtain the certified invoice, check for red-inked and duplicate data, generate the invoice verification result, and based on the invoice verification result, create payment vouchers, generate payment information, receive settlement results, update the billing period status and generate system logs.

[0027] The following are its main beneficial effects:

[0028] (1) To address the issue of unclear association between invoice content and communication summary data, advertising expense statement data is filtered based on the communication summary data and the invoice content, and an invoice pending processing voucher is generated. This allows invoice content, invoice feature value, advertising expense statement data, configuration relationship, advertising expense application rules, and payment period status to flow in the same processing record, forming a data foundation that can be called upon for subsequent posting approval results.

[0029] (2) To address the issue of scattered data filtering criteria for advertising expense statements, the classification, filtering of duplicate data, and comparison of pending vouchers are used to ensure that advertising distribution platform accounts, settlement expense data, invoice content, and payment status are processed in the same posting approval process, thereby reducing the situation where invoice content and settlement expense data are mismatched and enter into subsequent payment voucher processing.

[0030] (3) To address the issue of incomplete connection between posting approval results and certified invoices and payment vouchers, certified invoices are obtained based on the posting approval results and the invoice feature values. Red-inked and duplicate data are checked, so that the invoice verification results become the prerequisite input for creating payment vouchers, forming a continuous relationship between posting approval results, invoice verification results, payment vouchers and payment information.

[0031] (4) To address the issue of duplicate data entering the payment process, the system records the invoice feature value, advertising expense statement data, payment voucher and payment information in the pending voucher, and continuously calls the duplicate data status in the posting approval result and invoice verification result, so that the duplicate data enters the abnormal alarm status and system log before the payment voucher is created.

[0032] (5) To address the issue of scattered records of billing period status and payment information, the system receives settlement results based on the payment information, updates the billing period status, and generates system logs, so that advertising expense statement data, payment vouchers, payment information, billing period status, abnormal alarm status, and system logs form corresponding records in the data storage module. Attached Figure Description

[0033] Figure 1 A flowchart illustrating the automatic reconciliation and payment processing method for advertising expenses based on VAT invoices provided in this application embodiment;

[0034] Figure 2 This is a structural block diagram of the automatic reconciliation and payment processing method for advertising expenses based on VAT special invoices provided in the embodiments of this application. Detailed Implementation

[0035] Example 1: Refer to Figure 1 This is a flowchart illustrating the automatic reconciliation and payment processing method for advertising expenses based on value-added tax invoices provided in an embodiment of the present invention. The process may include at least steps S100-S800:

[0036] S100: Receive electronic files or scanned images of VAT special invoices, advertising distribution platform accounts, configuration relationships, advertising fee application rules and billing status, and generate an invoice verification request.

[0037] S200: Based on the invoice verification request, perform graphic recognition and text recognition, read the invoice information, and generate invoice content and invoice feature values;

[0038] S300. Based on the invoice content and the invoice feature value, send a scheduled task instruction to the advertising distribution platform to obtain alliance promotion data, own site promotion data and settlement fee data, and generate communication summary data.

[0039] S400: Based on the communication summary data and the invoice content, filter the advertising expense statement data and generate an invoice pending processing voucher;

[0040] S500: Based on the classification of the pending vouchers, filter duplicate data, compare them one by one, and generate posting approval results;

[0041] S600: Based on the posting approval result and the invoice feature value, obtain the certified invoice, check for red-inked and duplicate data, and generate the invoice verification result;

[0042] S700: Based on the invoice verification result, create a payment voucher, send the payment voucher to the financial institution interface, and generate payment information;

[0043] S800: Receive settlement results based on the payment information, update the billing status, and generate system logs.

[0044] S100: Receive electronic files or scanned images of VAT special invoices, advertising distribution platform accounts, configuration relationships, advertising fee application rules and billing status, and generate an invoice verification request.

[0045] This step serves as the entry point for the automatic reconciliation and payment processing of advertising expenses. The management backend module receives electronic files or scanned images of VAT invoices and simultaneously receives the advertising distribution platform account, configuration relationships, advertising fee application rules, and payment period status. The electronic VAT invoice file is an electronic invoice file containing the invoice information, and the scanned image is an image file formed from a paper VAT invoice through image capture. The advertising distribution platform account is the account identifier used by the advertising distribution platform during the advertising expense processing, used to associate affiliate promotion data, proprietary website promotion data, and settlement fee data. The configuration relationships refer to the placement and settlement relationships between the advertiser module, the advertising distribution platform, and the proprietary website module. The advertising fee application rules are the processing rules for advertising fee allocation, advertising media selection, activity rule data, and settlement fee data. The payment period status is the status information corresponding to the current advertising expense processing cycle, recording the pending, submitted, successful payment, and failed payment status of the advertising expense reconciliation data within the payment period.

[0046] Specifically, when an invoice upload operation occurs on the advertising distribution platform, advertising fee placement platform, or management backend module, the information transmission and receiving module receives the electronic file or scanned image of the VAT special invoice and reads the accompanying advertising distribution platform account, configuration relationship, advertising fee application rules, and billing status. The information transmission and receiving module transmits the received data to the information processing module. The information processing module first records the source of the VAT special invoice electronic file or scanned image, and then performs a field integrity check on the advertising distribution platform account, the configuration relationship, the advertising fee application rules, and the billing status. The field integrity check includes whether the file exists, whether the advertising distribution platform account is empty, whether the configuration relationship is written, whether the advertising fee application rules are written, and whether the billing status is written. After the check passes, the information processing module writes each field into the same processing record.

[0047] Specifically, when the electronic file or scanned image of the VAT invoice enters the processing record, the information processing module records the file name, file format, upload time, upload source, and file storage location. The upload source is an advertising distribution platform, advertising fee placement platform, or management backend module. The file format is used for image recognition and text recognition in S200. The file storage location is used for S200 to read the invoice information. If the electronic file or scanned image of the VAT invoice cannot be read, or the uploaded content does not contain invoice information, the information processing module marks the processing record as missing key information of the invoice content, generates an abnormal alarm status through the result feedback module, and writes the abnormal alarm status to the system log.

[0048] Specifically, when the advertising distribution platform account enters the processing record, the information processing module associates the advertising distribution platform account with the account information in the advertising distribution platform. This association process matches the advertising distribution platform account with the account records in the management backend module. After matching, the advertising distribution platform account serves as the input field for accessing the advertising distribution platform when the S300 sends a scheduled task instruction. If the advertising distribution platform account fails to correspond to an account record in the advertising distribution platform, the information processing module marks the processing record as an abnormal advertising distribution platform account and writes an abnormal alarm status through the result feedback module.

[0049] Specifically, when the configuration relationship is entered into the processing record, the information processing module reads the association information of the advertiser module, advertising distribution platform, proprietary website administrator module, and settlement fee data in the configuration relationship. The configuration relationship is used to mark the correspondence between advertising content, advertising playback plan, advertising plan budget, and the daily percentage limit corresponding to the advertising budget. The configuration relationship is also used in S400 to compare the buyer's name and buyer's taxpayer identification number in the invoice content with the communication summary data. If the configuration relationship is not written with the association information of the advertising distribution platform or proprietary website administrator module, the information processing module marks the processing record as an abnormal configuration relationship and writes this abnormal alarm status to the system log.

[0050] Specifically, when the advertising fee application rule enters the processing record, the information processing module reads the advertising fee allocation, advertising media selection, activity rule data, and settlement fee data writing conditions. The advertising fee application rule is used for a one-to-one comparison of the participating configuration relationships, advertising fee application rules, and settlement fee data in the S500. When the advertising fee application rule involves advertising playback plans, advertising plan budgets, and daily percentage-based limits for advertising, the information processing module associates these fields with the advertising distribution platform account to form the rule record required for advertising fee processing. If the advertising fee application rule lacks settlement fee data writing conditions, the information processing module marks the processing record as an advertising fee application rule anomaly and outputs an anomaly alarm status through the result feedback module.

[0051] Specifically, when the payment period status is entered into the processing record, the information processing module reads the start and end dates of the payment period, the payment period submission status, the payment voucher status, and the payment information status. The payment period status is used in S400 for comparison with the remarks in the invoice content, and also for updating in S800 based on the settlement result. When the payment period status is "payment successful," the information processing module hands over the processing records of the same advertising distribution platform account, the same configuration relationship, and the same payment period status to the result feedback module for processing, and no new invoice verification request is generated. When the payment period status is "payment failed," the information processing module retains the electronic file or scanned image of the VAT special invoice, the advertising distribution platform account, the configuration relationship, and the advertising fee application rules, and writes the payment failure to the system log.

[0052] Understandably, after completing the above receiving and checking, the information processing module encapsulates the electronic file or scanned image of the VAT special invoice, the advertising distribution platform account, the configuration relationship, the advertising fee application rules, and the billing period status according to the same processing record, and generates an invoice verification request. The invoice verification request includes invoice file fields, advertising distribution platform account fields, configuration relationship fields, advertising fee application rule fields, billing period status fields, abnormal alarm status fields, and system log fields. The invoice file field is used by S200 for image recognition and text recognition; the advertising distribution platform account field, configuration relationship field, advertising fee application rule field, and billing period status field are passed to S200 along with the invoice verification request and are subsequently called in S300, S400, and S500; the abnormal alarm status field and system log field are used to record the receiving process, checking process, and generation process of this step.

[0053] In one specific embodiment, after the billing period ends, the advertising distribution platform uploads an electronic VAT invoice file through the management backend module, and simultaneously submits the advertising distribution platform account, configuration relationship, advertising fee application rules, and billing period status. After receiving the uploaded content, the management backend module writes the electronic VAT invoice file into the data storage module, associates the advertising distribution platform account with the advertising distribution platform account record, associates the configuration relationship with the advertiser module and the self-owned website administrator module, associates the advertising fee application rules with the settlement fee data writing conditions, and associates the billing period status with the current processing record. After the information processing module checks that all the above fields have been written, it generates an invoice verification request and sends the invoice verification request to S200. S200 reads the invoice information based on the invoice verification request and generates invoice content and invoice feature values.

[0054] Summary of the technical effects of this step: This step synchronously binds the electronic file or scanned image of the VAT special invoice with the advertising distribution platform account, configuration relationship, advertising fee application rules, and payment period status in the invoice verification request. This step ensures that the invoice entry and advertising fee source flow within the same processing record. The invoice verification request generated in this step provides the input basis for S200 to read invoice information, S300 to obtain communication summary data, and S400 to filter advertising fee reconciliation data.

[0055] S200: Based on the invoice verification request, perform graphic recognition and text recognition, read the invoice information, and generate invoice content and invoice feature values;

[0056] This step follows the invoice verification request generated by S100. The information acquisition module reads the electronic file or scanned image of the VAT special invoice, the advertising distribution platform account, configuration relationship, advertising fee application rules, and payment period status from the invoice verification request. The image recognition is an operation that processes the invoice area, text area, amount area, and financial information area in the electronic file or scanned image of the VAT special invoice. The text recognition is an operation that reads characters from the text area obtained through image recognition. The invoice information includes invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks. The invoice content is a set of invoice fields after reading, organizing, and data cleaning. The invoice feature value is a combination of fields used by S600 to obtain authenticated invoices, including invoice code, invoice number, invoice date, invoice type, and amount excluding tax.

[0057] Specifically, the information acquisition module first reads the invoice file field from the invoice verification request, and then retrieves the electronic file or scanned image of the VAT special invoice based on the invoice file field. When the electronic file of the VAT special invoice is processed, the information acquisition module performs format recognition, reading the file format, number of pages, and invoice display status. When the scanned image is processed, the information acquisition module performs orientation correction, edge cropping, and sharpness processing. Orientation correction is used to adjust the tilted invoice orientation to a uniform reading direction. Edge cropping is used to remove blank areas and irrelevant image areas outside the edges of the invoice. Sharpness processing is used to enhance the image of the areas containing the invoice code, invoice number, amount, and taxpayer identification number. After completing the above processing, the information acquisition module obtains invoice image data that can be used for text recognition.

[0058] Furthermore, the information acquisition module performs graphic recognition on the invoice image data and divides it into the following areas according to the location of the invoice information: invoice code area, invoice number area, invoice date area, invoice type area, buyer information area, seller information area, amount area, tax rate area, tax amount area, total price including tax area, and remarks area. The buyer information area includes the buyer's name and buyer's taxpayer identification number. The seller information area includes the seller's name and seller's taxpayer identification number. The amount area includes the amount excluding tax. The remarks area is used for comparison with the payment period status in subsequent S400. After graphic recognition is completed, the information acquisition module records the location of each area in the system log and sends each area to the text recognition system.

[0059] Specifically, the character recognition module reads characters from each area to obtain the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks. After reading, the information collection module cleans the above fields. Data cleaning includes removing spaces, removing duplicate characters, standardizing the amount format, standardizing the date format, standardizing the tax rate format, and removing data with missing key information. The missing key information refers to data lacking the invoice code, invoice number, invoice date, invoice type, amount excluding tax, buyer's taxpayer identification number, or seller's taxpayer identification number. When such missing key information occurs, the information collection module submits the corresponding invoice verification request to the result feedback module for processing and writes the missing key information of the invoice content into the abnormal alarm status and system log.

[0060] Furthermore, the information collection module performs field mapping processing on the read invoice information. The invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks are written into the invoice content. The invoice code, invoice number, invoice date, invoice type, and amount excluding tax are written into the invoice feature value. Understandably, the invoice content is used by S300 to retain the invoice source when generating communication summary data, and also by S400 to filter advertising expense reconciliation data. The invoice feature value is used by S600 to download certified invoices from the tax bureau-authorized invoice digitization full lifecycle management cloud platform system, and to compare them with the certified invoices in S600.

[0061] Specifically, in one technical solution, when the electronic file of the VAT special invoice is an electronic invoice file, the information acquisition module directly reads the page content of the file and performs format recognition, image recognition, and text recognition on the page content. The invoice information in the electronic invoice file is written into the invoice content after data cleaning, and the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount are written into the invoice feature value. In another technical solution, when the scanned image is a paper invoice image, the information acquisition module first performs orientation correction, edge cropping, and sharpness processing, and then performs image recognition and text recognition. Both technical solutions write the reading results into the invoice content field and invoice feature value field of the same invoice verification request.

[0062] In one specific embodiment, the invoice verification request generated by the management backend module in S100 includes an electronic file of a VAT special invoice, an advertising distribution platform account, a configuration relationship, an advertising fee application rule, and a billing period status. After reading the invoice verification request, the information collection module first performs format recognition on the electronic file of the VAT special invoice, and then reads the invoice information. After reading, the information collection module writes the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks into the invoice content, and writes the invoice code, invoice number, invoice date, invoice type, and amount excluding tax into the invoice feature value. Subsequently, the invoice content and the invoice feature value enter S300 along with the invoice verification request, so that S300 can send a scheduled task instruction to the advertising distribution platform and generate communication summary data for retrieval.

[0063] In summary, this step transforms the invoice verification request in S100 into invoice content and invoice feature values, creating a seamless connection between the uploaded invoice and subsequent advertising expense data processing. This step integrates invoice information reading, data cleaning, and processing of missing key information into a single process. The invoice content generated in this step is processed in S300 and S400, while the invoice feature values ​​are processed in S300 and S600.

[0064] S300. Based on the invoice content and the invoice feature value, send a scheduled task instruction to the advertising distribution platform to obtain alliance promotion data, own site promotion data and settlement fee data, and generate communication summary data.

[0065] This step takes over the invoice content and invoice feature values ​​generated by S200, and calls the advertising distribution platform account, configuration relationship, advertising fee application rules, and billing status written in S100 along with the invoice verification request. The scheduled task instruction is a data access instruction sent by the cloud cross-database access module to the advertising distribution platform. The affiliate promotion data is the advertising content, advertising playback plan, advertising plan budget, daily percentage limit corresponding to advertising, advertising creative content, advertising views and clicks, advertising traffic, and settlement fee data recorded by the advertising distribution platform. The proprietary site promotion data is the advertising display, advertising views and clicks, advertising traffic, and settlement fee data recorded by the proprietary site administrator module. The settlement fee data is the fee data formed according to the configuration relationship and advertising fee application rules within the advertising fee processing cycle. The communication summary data is the data record formed by the central server after aggregating the affiliate promotion data, proprietary site promotion data, and settlement fee data, which is used by S400 to filter advertising fee reconciliation data.

[0066] Specifically, the cloud-based cross-database access module first reads the seller's name, seller's taxpayer identification number, buyer's name, buyer's taxpayer identification number, amount, tax rate, tax amount, total price including tax, and remarks from the invoice content. It also reads the invoice code, invoice number, invoice date, invoice type, and amount excluding tax from the invoice's characteristic values. The cloud-based cross-database access module then reads the advertising distribution platform account and payment period status, generating a scheduled task instruction. This scheduled task instruction is written with the advertising distribution platform account, payment period status, invoice code, invoice number, and invoice date. Upon receiving the scheduled task instruction, the advertising distribution platform retrieves the corresponding advertising content, advertising playback plan, advertising plan budget, daily percentage limit for advertising, advertising creative content, configuration relationships, advertising views and clicks, advertising traffic, and settlement fee data according to the advertising distribution platform account, and returns the retrieval results to the cloud-based cross-database access module.

[0067] Furthermore, when accessing the advertising distribution platform, the cloud-based cross-database access module limits the data range according to the billing period status. When the billing period status is "pending," the cloud-based cross-database access module reads settlement fee data that has not yet been written into payment vouchers. When the billing period status is "payment failed," the cloud-based cross-database access module reads settlement fee data related to the payment failure and the original processing record. When the billing period status is "payment successful," the cloud-based cross-database access module stops reading the corresponding settlement fee data and writes the billing period status to the system log. If the advertising distribution platform account has no corresponding data, or the advertising distribution platform does not return affiliate promotion data, the cloud-based cross-database access module writes this process into an abnormal alarm status and passes the abnormal alarm status to the result feedback module for recording.

[0068] Specifically, after the affiliate promotion data enters the cloud-based cross-database access module, the module categorizes it according to the ad distribution platform account, configuration relationship, and billing status. The configuration relationship connects the advertiser module, the ad distribution platform, and the owner's own website module. The ad fee application rules connect ad fee allocation, ad media selection, activity rule data, and settlement fee data. After categorization, the cloud-based cross-database access module writes the ad content, ad playback plan, ad plan budget, daily percentage limit corresponding to the ad, ad creative content, ad views and clicks, ad traffic, and settlement fee data into the same ad distribution platform record, and then transmits the ad distribution platform record to the central server.

[0069] Furthermore, the proprietary website administrator module sends its own website promotion data to the central server. This proprietary website promotion data includes advertising content, ad views and clicks, ad traffic, and settlement fee data generated by the proprietary website administrator module. After receiving the affiliate promotion data and the proprietary website promotion data, the central server aggregates them according to the ad distribution platform account, configuration relationship, ad fee application rules, and billing status. The aggregation process first groups data corresponding to the same ad distribution platform account into the same record, then groups affiliate promotion data and proprietary website promotion data corresponding to the same configuration relationship into the same record, and finally groups settlement fee data corresponding to the same billing status into the same record. After aggregation is complete, the central server generates communication summary data.

[0070] Understandably, the communication summary data retains associated fields between the invoice content and the invoice characteristic values. These associated fields include invoice code, invoice number, invoice date, invoice type, amount excluding tax, seller name, seller taxpayer identification number, buyer name, buyer taxpayer identification number, amount, tax rate, tax amount, total price including tax, and remarks. The communication summary data also includes the advertising distribution platform account, advertising content, advertising playback plan, advertising plan budget, daily percentage limit for advertising, advertising creative content, configuration relationships, advertising views and clicks, advertising traffic, proprietary website promotion data, affiliate promotion data, settlement fee data, advertising fee application rules, and billing status. These fields form a corresponding relationship within the same communication summary data, allowing S400 to filter the invoice content against the communication summary data.

[0071] In one technical solution, the advertising distribution platform is a single platform. The cloud-based cross-database access module sends scheduled task instructions according to the advertising distribution platform account, and the advertising distribution platform returns affiliate promotion data and settlement fee data from a single source. The central server writes the affiliate promotion data, the proprietary site promotion data, and the settlement fee data into the communication summary data. In another technical solution, the advertising distribution platform comprises multiple advertising distribution platforms. The cloud-based cross-database access module sequentially sends scheduled task instructions, and different advertising distribution platforms return affiliate promotion data and settlement fee data respectively. The central server summarizes the data returned by different advertising distribution platforms according to configuration relationships and billing status, generating communication summary data corresponding to the same invoice verification request.

[0072] In one specific embodiment, the invoice content generated by S200 includes the seller's name, seller's taxpayer identification number, amount, tax rate, tax amount, total price including tax, and remarks. The invoice feature values ​​include invoice code, invoice number, invoice date, invoice type, and amount excluding tax. The cloud cross-database access module reads the above invoice content and invoice feature values, and reads the advertising distribution platform account, configuration relationship, advertising fee application rules, and billing status written by S100. Subsequently, the cloud cross-database access module sends a scheduled task instruction to the advertising distribution platform. The advertising distribution platform returns advertising content, advertising playback plan, advertising plan budget, daily percentage limit corresponding to advertising, advertising creative content, advertising views and clicks, advertising traffic, and settlement fee data. The main server receives the above data and receives the self-owned website promotion data sent by the self-owned website administrator module. The main server writes the above data into communication summary data and transmits the communication summary data to S400. S400 filters advertising fee reconciliation data based on the communication summary data and the invoice content.

[0073] Summary of the technical effects of this step: This step introduces the invoice content and invoice feature values ​​generated in S200 into the data acquisition process of the advertising distribution platform, establishing a correspondence between invoice fields and advertising expense source data in the communication summary data. This step aggregates affiliate promotion data, proprietary site promotion data, and settlement fee data into communication summary data. The communication summary data generated in this step is entered into S400 as input for filtering advertising expense reconciliation data.

[0074] S400: Based on the communication summary data and the invoice content, filter the advertising expense statement data and generate an invoice pending processing voucher;

[0075] This step takes over the communication summary data generated by S300 and the invoice content generated by S200. The information processing module reads the advertising distribution platform account, advertising content, advertising playback plan, advertising plan budget, daily percentage limit for advertising, advertising creative content, configuration relationship, advertising views and clicks, advertising traffic, own site promotion data, affiliate promotion data, settlement fee data, advertising fee application rules, and billing status from the communication summary data. It also reads the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer name, seller name, buyer taxpayer identification number, seller taxpayer identification number, and remarks from the invoice content. The advertising expense reconciliation data consists of advertising expense data records extracted from the communication summary data that correspond to the invoice content. The pending processing vouchers are pending records bound to the invoice content, the invoice feature value, the advertising expense reconciliation data, the configuration relationship, the advertising fee application rules, the billing status, and the system log, which are then used by S500 for classification, filtering of duplicate data, and comparison.

[0076] Specifically, the information processing module first cleans and organizes the communication summary data. Data cleanup includes deleting null records, deleting duplicate records, correcting ad distribution platform account fields, organizing settlement fee data fields, and organizing billing status fields. After the field organization is completed, the information processing module writes affiliate promotion data, proprietary site promotion data, and settlement fee data under the same ad distribution platform account into the same communication summary record. It also writes ad content, ad playback plans, ad plan budgets, daily percentage limits for ads, ad creative content, ad views / clicks, and ad traffic under the same configuration relationship into the same communication summary record. The communication summary record retains the original system logs, recording the data source, reception time, and billing status.

[0077] Further, the information processing module compares the seller's name and taxpayer identification number in the invoice content with the advertising distribution platform account in the communication summary data. The seller's name is the name of the party issuing the VAT special invoice. The seller's taxpayer identification number is the identification number of the party issuing the VAT special invoice. The advertising distribution platform account is the account identifier of the advertising distribution platform in advertising fee processing. During the comparison, the information processing module first reads the financial information corresponding to the advertising distribution platform account from the data storage module, and then matches the seller's name and taxpayer identification number with the financial information. When the field matching is complete, the information processing module marks the corresponding communication summary record as a seller matching record; if the fields do not match, the information processing module writes the corresponding record to an abnormal alarm status, and the result feedback module writes it to the system log.

[0078] Specifically, the information processing module compares the buyer's name and taxpayer identification number in the invoice content with the configuration relationship. The buyer's name is the name of the party receiving the invoice in the VAT special invoice. The buyer's taxpayer identification number is the identification number of the party receiving the invoice in the VAT special invoice. The configuration relationship records the placement and settlement relationships between the advertiser module, the advertising distribution platform, and the proprietary website administrator module. During the comparison, the information processing module reads the financial information corresponding to the advertiser module from the configuration relationship, and then matches the buyer's name and taxpayer identification number with the financial information. When the field matching is complete, the information processing module marks the corresponding communication summary record as a buyer matching record; when the fields do not match, the information processing module writes the record to an abnormal alarm status and retains the reason for the mismatch.

[0079] Further, the information processing module compares the amount, tax rate, tax amount, and total price including tax in the invoice with the settlement fee data. The amount is the amount excluding tax, the tax rate is the tax rate recorded on the VAT invoice, the tax amount is the tax amount recorded on the VAT invoice, and the total price including tax is the invoice data after combining the amount and tax amount. The settlement fee data is the fee data generated within the advertising fee processing cycle according to the configuration relationship and advertising fee application rules. During the comparison, the information processing module first extracts candidate settlement fee data according to the advertising distribution platform account and billing period status, then matches the amount with the tax-exclusive data in the candidate settlement fee data, matches the tax rate with the tax rate field in the candidate settlement fee data, matches the tax amount with the tax amount field in the candidate settlement fee data, and matches the total price including tax with the total field in the candidate settlement fee data. When the field matching is complete, the information processing module writes the candidate settlement fee data into the advertising fee reconciliation statement data; if the fields do not match, the information processing module writes an abnormal alarm status indicating inconsistencies in the amount, tax rate, tax amount, or total price including tax.

[0080] Specifically, the information processing module compares the remarks in the invoice content with the payment period status. The remarks are the remarks field on the VAT special invoice, and the payment period status is the status information corresponding to the advertising expense processing cycle. During the comparison, the information processing module reads the advertising playback plan, advertising plan budget, payment period content, or advertising distribution platform account-related text from the remarks, and then matches it with the payment period status in the communication summary data. If the remarks contain payment period content, the information processing module extracts the communication summary record according to the payment period content. If the remarks do not contain payment period content, the information processing module extracts the communication summary record according to the invoice date, advertising distribution platform account, and configuration relationship. After the extraction is completed, the information processing module writes the corresponding record into the advertising expense reconciliation statement data.

[0081] Understandably, after the advertising expense statement data is generated, the information processing module encapsulates the invoice content, the invoice feature value, the advertising expense statement data, the configuration relationship, the advertising fee application rules, and the billing period status into a pending invoice credential. The pending invoice credential contains the following information: invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, remarks, advertising distribution platform account, affiliate promotion data, proprietary website promotion data, settlement fee data, configuration relationship, advertising fee application rules, billing period status, abnormal alarm status, and system logs. After the pending invoice credential is generated, it enters S500, where S500 performs classification, filters duplicate data, and compares data one by one based on the pending invoice credential.

[0082] In one implementation, when a single advertising distribution platform account corresponds to a single settlement fee data, the information processing module directly maps the seller's name and taxpayer identification number to the advertising distribution platform account, maps the buyer's name and taxpayer identification number to the configuration relationship, and maps the amount, tax rate, tax amount, and total price including tax to the settlement fee data, generating an advertising fee reconciliation statement. In another implementation, when different advertising distribution platform accounts correspond to a single invoice content, the information processing module first splits the communication summary data according to the configuration relationship and the payment period status, then maps the split settlement fee data to the invoice content field by field. After the field mapping is completed, multiple advertising fee reconciliation statements are generated under the same pending invoice voucher. In yet another implementation, when a single advertising distribution platform account corresponds to different payment period statuses, the information processing module extracts the communication summary record for the corresponding payment period based on the remarks, the invoice date, and the payment period status, and writes the extraction result into the advertising fee reconciliation statement data.

[0083] In one specific embodiment, the communication summary data generated by S300 includes the advertising distribution platform account, configuration relationship, advertising playback plan, advertising plan budget, daily percentage limit for advertising, advertising creative content, advertising views and clicks, advertising traffic, affiliate promotion data, proprietary website promotion data, and settlement fee data. The invoice content generated by S200 includes the seller's name, seller's taxpayer identification number, buyer's name, buyer's taxpayer identification number, amount, tax rate, tax amount, total price including tax, and remarks. The information processing module first maps the seller's name and seller's taxpayer identification number to the advertising distribution platform account, then maps the buyer's name and buyer's taxpayer identification number to the configuration relationship, subsequently maps the amount, tax rate, tax amount, and total price including tax to the settlement fee data, and finally maps the remarks to the payment period status. After mapping is completed, the information processing module generates advertising expense reconciliation data and writes the advertising expense reconciliation data, along with the invoice content and the invoice feature value, into the pending invoice voucher.

[0084] Summary of the technical effects of this step: This step maps the communication summary data and invoice content to fields to form advertising expense reconciliation data. This step binds the advertising expense reconciliation data, invoice content, and invoice feature values ​​into pending invoice vouchers. The pending invoice vouchers generated in this step are entered into S500 as input for classification, filtering duplicate data, and one-to-one comparison.

[0085] S500: Based on the classification of the pending vouchers, filter duplicate data, compare them one by one, and generate posting approval results;

[0086] This step takes over the pending invoice vouchers generated by S400. The information processing module calls the data set comparison algorithm engine module to classify, filter duplicate data, and compare them one by one. The pending invoice vouchers include invoice content, invoice feature values, advertising expense statement data, configuration relationships, advertising expense application rules, payment period status, abnormal alarm status, and system logs. The classification is based on the advertising distribution platform account, settlement fee data, invoice content, and payment period status to divide the types to be compared. The filtering of duplicate data involves retrieving existing invoice feature values, advertising expense statement data, payment vouchers, and payment information from the data storage module, and removing data that has already formed a payment success record. The one-by-one comparison involves matching the tax rate, amount, seller's financial information, buyer's financial information, configuration relationships, advertising expense application rules, and settlement fee data field by field. The posting approval result is the approval record output by the data set comparison algorithm engine module, which indicates whether it is qualified, unqualified, or pending. This record is used by S600 to obtain certified invoices and generate invoice verification results.

[0087] Specifically, the information processing module first reads the invoice content and advertising expense statement data from the pending invoice vouchers. The invoice content includes the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks. The advertising expense statement data includes the advertising distribution platform account, affiliate promotion data, proprietary website promotion data, settlement fee data, configuration relationships, advertising fee application rules, and payment period status. The information processing module transmits the above fields to the data set comparison algorithm engine module and writes the transmission time, pending invoice voucher number, and payment period status to the system log.

[0088] Furthermore, the data set comparison algorithm engine module categorizes the pending invoice vouchers. During categorization, the pending invoice vouchers are divided into: single settlement fee data corresponding to a single advertising distribution platform, single invoice content corresponding to different advertising distribution platforms, single advertising distribution platform corresponding to different billing period statuses, and single settlement fee data corresponding to different invoice contents. When a single advertising distribution platform corresponds to a single settlement fee data, the data set comparison algorithm engine module places a set of advertising distribution platform accounts, a set of settlement fee data, and a set of invoice contents into the same comparison record. When different advertising distribution platforms correspond to a single invoice content, the data set comparison algorithm engine module splits the advertising fee statement data according to the configuration relationship and places the split settlement fee data into different comparison records under the same invoice content. When a single advertising distribution platform corresponds to different billing period statuses, the data set comparison algorithm engine module splits the settlement fee data according to the billing period status. When different invoice contents correspond to a single settlement fee data, the data set comparison algorithm engine module splits the invoice content according to the invoice code, invoice number, and total price including tax.

[0089] Specifically, after classification, the data set comparison algorithm engine module performs duplicate data filtering. When filtering duplicate data, it first uses the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount from the invoice feature values ​​as search fields to retrieve existing pending invoice vouchers from the data storage module. If the same invoice feature values ​​are found and the payment information indicates successful payment, the data set comparison algorithm engine module marks the corresponding record as duplicate data and writes the duplicate data to an anomaly alarm status. If the same advertising expense statement data is found and the payment voucher already exists, the data set comparison algorithm engine module marks the corresponding record as duplicate data and writes the payment voucher status to the system log. If no identical invoice feature values, identical advertising expense statement data, or successful payment records are found, the data set comparison algorithm engine module retains the corresponding record as a record to be compared.

[0090] Furthermore, the data set comparison algorithm engine module performs a one-by-one comparison of the records to be compared. First, it compares the tax rate in the invoice content with the tax rate field in the advertising expense statement data. Then, it compares the amount in the invoice content with the amount field in the settlement expense data. Finally, it compares the tax amount and total price including tax in the invoice content with the tax amount field and total field in the settlement expense data. If the comparison passes, the data set comparison algorithm engine module records the tax rate, amount, tax amount, and total price including tax as consistent fields. If the comparison fails, the data set comparison algorithm engine module writes the inconsistent fields to an anomaly alarm status and records the pending processing voucher for the invoice containing the inconsistent fields.

[0091] Specifically, the data set comparison algorithm engine module continues to compare the seller's financial information and the buyer's financial information. The seller's financial information is formed by the seller's name, seller's taxpayer identification number, and advertising distribution platform account. The buyer's financial information is formed by the buyer's name, buyer's taxpayer identification number, and configuration relationship. When comparing the seller's financial information, the data set comparison algorithm engine module reads the financial information corresponding to the seller's name, seller's taxpayer identification number, and advertising distribution platform account, and performs field matching. When comparing the buyer's financial information, the data set comparison algorithm engine module reads the financial information corresponding to the buyer's name, buyer's taxpayer identification number, and configuration relationship, and performs field matching. If the fields do not match, the data set comparison algorithm engine module writes an abnormal alarm status indicating inconsistency between the seller's financial information and the buyer's financial information.

[0092] Furthermore, the data set comparison algorithm engine module compares the configuration relationships, advertising fee application rules, and settlement fee data. The configuration relationships record the placement and settlement relationships between the advertiser module, the advertising distribution platform, and the proprietary website owner module. The advertising fee application rules record the conditions for writing advertising fee allocation, advertising media selection, activity rule data, and settlement fee data. During comparison, the data set comparison algorithm engine module matches the advertising distribution platform account, proprietary website owner module, and advertiser module in the configuration relationships with the advertising fee reconciliation statement data; then it matches the fee allocation, advertising media selection, and activity rule data in the advertising fee application rules with the settlement fee data. When the field matching is complete, the data set comparison algorithm engine module marks the pending invoice as a candidate record for successful posting approval; if the fields do not match, the pending invoice is marked as a candidate record for unsuccessful posting approval.

[0093] Understandably, the data set comparison algorithm engine module generates posting approval results based on classification results, duplicate data filtering results, and one-by-one comparison results. The posting approval results include the pending voucher number, invoice feature value, advertising expense statement data, classification type, duplicate data status, tax rate comparison status, amount comparison status, seller's financial information comparison status, buyer's financial information comparison status, configuration relationship comparison status, advertising expense application rule comparison status, settlement expense data comparison status, and anomaly alarm status. When the posting approval result is satisfactory, the information processing module transmits the posting approval result and the invoice feature value to S600. When the posting approval result is unsatisfactory, the information processing module writes the anomaly alarm status to the system log through the result feedback module and retains the pending record of the pending voucher.

[0094] In one specific embodiment, the pending invoice corresponds to a single advertising distribution platform and a single settlement fee data. The data set comparison algorithm engine module first categorizes the pending invoice into the single settlement fee data corresponding to the single advertising distribution platform. Subsequently, the data set comparison algorithm engine module searches the data storage module based on the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount. If no successful payment record is found, it is retained as a record to be compared. Next, the data set comparison algorithm engine module compares the tax rate, amount, seller's financial information, buyer's financial information, configuration relationship, advertising fee application rules, and settlement fee data in sequence. After the comparison is completed, a posting approval result is generated, and the posting approval result and the invoice feature value are transmitted to S600.

[0095] Summary of the technical effects of this step: This step converts pending invoices into posting approval results that can be used for invoice verification. This step integrates advertising expense statement data, invoice content, and settlement expense data into a single processing procedure through classification, filtering of duplicate data, and one-by-one comparison. The posting approval results and invoice feature values ​​generated in this step are entered into S600 as input for obtaining certified invoices and checking for reversed and duplicate data.

[0096] S600: Based on the posting approval result and the invoice feature value, obtain the certified invoice, check for red-inked and duplicate data, and generate the invoice verification result;

[0097] This step follows the posting approval result generated by S500 and the invoice feature value generated by S200. The information processing module calls the tax bureau-authorized invoice digitization lifecycle management cloud platform system to obtain certified invoices and performs red-inking and duplicate data checks on the certified invoices. The posting approval result is an approval record formed by the data set comparison algorithm engine module after classifying, filtering duplicate data, and comparing the pending vouchers one by one. The invoice feature value includes invoice code, invoice number, invoice date, invoice type, and amount excluding tax. The certified invoice is the invoice record returned by the tax bureau-authorized invoice digitization lifecycle management cloud platform system based on the invoice feature value. Red-inking refers to the red-inking status corresponding to the certified invoice. Duplicate data refers to data in the data storage module that already contains the same invoice feature value, the same pending vouchers, the same advertising expense statement data, or successfully paid payment information. The invoice verification result is a qualified or unqualified record generated by the information processing module based on the certified invoice, red-inking, and duplicate data, and is used by S700 to create payment vouchers.

[0098] Specifically, the information processing module first reads the posting approval result. If the posting approval result is satisfactory, the information processing module extracts the following data from the posting approval result: pending invoice voucher number, invoice characteristic value, advertising expense statement data, classification type, duplicate data status, tax rate comparison status, amount comparison status, seller's financial information comparison status, buyer's financial information comparison status, configuration relationship comparison status, advertising expense application rule comparison status, and settlement expense data comparison status. These fields are then written into the verification record for this step. If the posting approval result is unsatisfactory, the information processing module does not execute the invoice authentication process and writes the unsatisfactory posting approval status into the abnormal alarm status and system log. The pending invoice voucher is retained as a pending record.

[0099] Further, the information processing module sends the invoice feature value to the tax authority-authorized invoice digitization lifecycle management cloud platform system. Before sending, the information processing module performs a field integrity check on the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount. If the fields are complete, the information processing module generates an invoice authentication request and writes the pending voucher number and invoice feature value into the request. If any fields are missing, the information processing module records the missing key information of the invoice content in an abnormal alarm status. After receiving the invoice authentication request, the tax authority-authorized invoice digitization lifecycle management cloud platform system retrieves the authenticated invoice according to the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount, and returns the retrieved authenticated invoice to the information processing module. If no authenticated invoice is found, the information processing module generates an unqualified invoice verification result and writes the inconsistency to the system log.

[0100] Specifically, after receiving the certified invoice, the information processing module compares the certified invoice with the invoice content by field comparison. The comparison fields include invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's taxpayer identification number, and seller's taxpayer identification number. The information processing module first compares the invoice code, invoice number, invoice date, and invoice type; then it compares the amount excluding tax, tax rate, tax amount, and total price including tax; and finally, it compares the buyer's taxpayer identification number and seller's taxpayer identification number. When all fields match, the information processing module writes the certified invoice to the verification record. If any field does not match, the information processing module writes the certified invoice inconsistency to an abnormal alarm status and generates an unqualified invoice verification result.

[0101] Furthermore, the information processing module performs a reverse cancellation check on the certified invoice. During the reverse cancellation check, the information processing module reads the reverse cancellation status from the certified invoice and writes the reverse cancellation status, the pending voucher number, the invoice code, the invoice number, and the invoice date into the same verification record. If the certified invoice is marked as reversed, the information processing module writes the reverse cancellation status to an abnormal alarm state, generates an unqualified invoice verification result, and writes the invoice verification result to the system log. If the certified invoice does not show as reversed, the information processing module continues to perform a duplicate data check.

[0102] Specifically, when the information processing module performs duplicate data checks, it searches the data storage module for identical invoice feature values, identical advertising expense statement data, identical payment vouchers, and identical payment information. If identical invoice feature values ​​are found and the payment information indicates successful payment, the information processing module marks the record as duplicate data, generates an invalid invoice verification result, and writes an anomaly alarm status through the result feedback module. If identical advertising expense statement data is found and the payment voucher already exists, the information processing module reads the payment information from the payment voucher. If the payment information indicates successful payment, the information processing module generates an invalid invoice verification result. If the payment information indicates a payment failure, the information processing module writes the original payment voucher status and the payment failure status into the verification record and retains the invoice pending processing for subsequent processing.

[0103] Understandably, the information processing module generates invoice verification results based on the comparison results of certified invoice fields, the results of red-ink reversal checks, and the results of duplicate data checks. The invoice verification results include the pending invoice voucher number, invoice characteristic value, certified invoice acquisition status, certified invoice field comparison status, red-ink reversal status, duplicate data status, anomaly alarm status, and system log index. When the invoice verification result is valid, the information processing module transmits the invoice verification result, the pending invoice voucher, and the advertising expense statement data to S700 for S700 to create payment vouchers. When the invoice verification result is invalid, the information processing module writes an anomaly alarm status through the result feedback module and writes the invalid record to the system log.

[0104] In one implementation, the certified invoice corresponds to the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's taxpayer identification number, and seller's taxpayer identification number in the invoice content. Furthermore, the certified invoice does not show any "red-inked" cancellation, the data storage module does not retrieve duplicate data indicating successful payment, and the information processing module generates a qualified invoice verification result. In another implementation, if the certified invoice does not match the amount excluding tax or the total price including tax in the invoice content, the information processing module generates an unqualified invoice verification result. In yet another implementation, the certified invoice does not show any "red-inked" cancellation, but the data storage module retrieves payment information corresponding to the same invoice characteristic value indicating successful payment; in this case, the information processing module generates an unqualified invoice verification result.

[0105] In one specific embodiment, if the posting approval result generated by S500 is qualified, the information processing module reads the invoice feature value from the posting approval result. The invoice feature value includes the invoice code, invoice number, invoice date, invoice type, and amount excluding tax. Based on the invoice feature value, the information processing module downloads the certified invoice from the tax authority-authorized invoice digital lifecycle management cloud platform system and compares the downloaded certified invoice with the invoice content generated by S200. After comparison, the information processing module checks whether the certified invoice has been reversed (red-inked) and retrieves duplicate data from the data storage module. When the certified invoice fields correspond, no reversed invoices are displayed, and no successfully paid duplicate data is found, the information processing module generates a qualified invoice verification result and transmits the invoice verification result to S700.

[0106] Summary of the technical effects of this step: This step incorporates the posting approval result generated by S500 and the invoice feature value generated by S200 into the invoice authentication acquisition process. This step merges the invoice field comparison, red-ink reversal check, and duplicate data check into a single invoice verification result. The invoice verification result generated in this step is entered into S700 as input for creating payment vouchers and sending them to the financial institution interface.

[0107] S700: Based on the invoice verification result, create a payment voucher, send the payment voucher to the financial institution interface, and generate payment information;

[0108] This step follows the invoice verification result generated by S600. The payment management module reads the invoice verification result, pending invoice processing vouchers, advertising expense statement data, invoice feature values, and payment period status. The payment management module receives the invoice verification result, creates payment vouchers, sends the payment vouchers to the financial institution interface, receives the interface's return information, and generates payment information. The payment voucher is a payment record that records the payer, payee, settlement expense data, invoice code, invoice number, payment period status, and advertising expense statement data. The financial institution interface receives the payment voucher and returns the payment status. The payment information is a payment record generated by the payment management module based on the content returned by the financial institution interface, including the payment voucher number, payment status, settlement expense data, sending time, return time, and abnormal alarm status.

[0109] Specifically, the payment management module first reads the pending invoice voucher number, invoice feature value, certified invoice field comparison status, reversed status, duplicate data status, and abnormal alarm status from the invoice verification result. If the invoice verification result is valid, the payment management module continues to read the advertising expense statement data, configuration relationships, advertising expense application rules, settlement expense data, and payment period status from the pending invoice voucher. If the invoice verification result is invalid, the payment management module does not create a payment voucher and writes the invalid invoice verification result to the system log. When the abnormal alarm status includes inconsistent certified invoices, reversed status, duplicate data, and unqualified posting approval, the payment management module retains the pending invoice voucher as a pending record and records the abnormal alarm status through the result feedback module.

[0110] Furthermore, the payment management module performs duplicate data filtering before creating a payment voucher. During duplicate data filtering, the payment management module transmits the invoice feature value, advertising expense statement data, payment voucher, and payment information to the data storage module for retrieval. Retrieval fields include invoice code, invoice number, invoice date, invoice type, amount excluding tax, advertising distribution platform account, settlement expense data, and payment period status. When the data storage module returns an existing payment voucher and the payment information indicates successful payment, the payment management module stops sending the payment voucher to the financial institution interface and writes "payment successful" to the abnormal alarm status. When the data storage module returns an existing payment voucher and the payment information indicates payment failure, the payment management module retains the payment voucher and continues tracking the payment status. If no existing payment voucher or successful payment record is found, the payment management module proceeds to the payment voucher creation process.

[0111] Specifically, when the payment management module creates a payment voucher, it writes the invoice content, invoice characteristic value, advertising expense statement data, settlement expense data, configuration relationship, advertising expense application rules, and payment period status from the pending voucher into the same payment voucher. The payment voucher records the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, seller name, seller taxpayer identification number, buyer name, buyer taxpayer identification number, advertising distribution platform account, settlement expense data, and payment period status. The seller name and seller taxpayer identification number serve as the payee field. The buyer name and buyer taxpayer identification number serve as the payment subject field. The settlement expense data serves as the payment amount source field. The payment period status serves as the payment cycle field. After the payment voucher is created, the payment management module writes the payment voucher number to the system log.

[0112] Further, the payment management module sends the payment voucher to the financial institution interface. Before sending, the payment management module reads the payment entity field, the payee field, settlement fee data, payment voucher number, and billing period status, and generates an interface sending record. After receiving the payment voucher, the financial institution interface returns the interface acceptance status, payment status, return time, and failure reason. The payment status includes payment success, payment failure, and processing. After receiving the interface return content, the payment management module writes the interface acceptance status, payment status, return time, and failure reason into the payment information. When the payment status is processing, the payment management module retains the payment voucher and continues to track the payment status according to the billing period status. When the payment status is payment failure, the payment management module writes the payment failure into the abnormal alarm status and retains the payment voucher. When the payment status is payment success, the payment management module writes the payment success into the payment information and transmits the payment information to S800.

[0113] Understandably, after payment information is generated, the payment management module associates the payment information with the payment voucher, the pending invoice voucher, the advertising expense statement data, and the payment period status. After association, the payment information retains the invoice characteristic value, advertising expense statement data, payment voucher number, content returned by the financial institution interface, payment status, and anomaly alarm status. When the payment information indicates successful payment, S800 receives the settlement result based on the payment information, updates the payment period status, and generates a system log. When the payment information indicates payment failure, S800 receives the settlement result based on the payment information and writes the payment voucher, the payment information, and the anomaly alarm status into the data storage module.

[0114] In one technical solution, if the invoice verification result is qualified and the data storage module does not retrieve a successful payment record, the payment management module creates a payment voucher based on the pending invoice and sends the payment voucher to the financial institution interface. When the financial institution interface returns a successful payment, the payment management module generates payment success information. In another technical solution, if the data storage module retrieves a payment voucher corresponding to the same invoice feature value and the payment information indicates successful payment, the payment management module stops sending the payment voucher to the financial institution interface and writes "payment successful" to the abnormal alarm status. In yet another technical solution, if the financial institution interface returns a payment failure, the payment management module retains the payment voucher and writes the payment failure to the payment information and system log.

[0115] In one specific embodiment, the invoice verification result generated by S600 is qualified. The pending voucher corresponding to the invoice verification result includes advertising expense statement data, settlement expense data, invoice feature value, and payment period status. After reading the invoice verification result, the payment management module sends the invoice code, invoice number, invoice date, invoice type, tax-exclusive amount, and advertising expense statement data to the data storage module for duplicate data filtering. If no payment success record is returned, the payment management module creates a payment voucher and writes the payer, payee, settlement expense data, payment voucher number, and payment period status into the payment voucher. Subsequently, the payment management module sends the payment voucher to the financial institution interface. After the financial institution interface returns the payment status, the payment management module generates payment information and transmits the payment information to S800.

[0116] Summary of the technical effects of this step: This step converts the invoice verification results generated by S600 into payment vouchers and payment information. This step performs duplicate data filtering before creating the payment voucher and incorporates invoice feature values, advertising expense statement data, payment vouchers, and payment information into the same processing procedure. The payment information generated in this step enters S800 as input for receiving settlement results, updating payment period status, and generating system logs.

[0117] S800: Receive settlement results based on the payment information, update the payment period status, and generate system logs.

[0118] This step follows the payment information generated by S700. The payment management module receives the settlement result returned by the financial institution interface, and the information processing module updates the billing period status, writes it to the data storage module, and generates a system log based on the settlement result. The payment information is the payment record formed after the payment voucher in S700 is sent to the financial institution interface, including the payment voucher number, payment status, settlement fee data, sending time, return time, and abnormal alarm status. The settlement result is the result returned by the financial institution interface indicating payment success, payment failure, or processing. The billing period status is the status information corresponding to the advertising fee processing cycle. The system log records the invoice content reading process, the advertising fee statement data filtering process, the classification process of pending vouchers, the generation process of posting approval results, the acquisition process of certified invoices, the creation process of payment vouchers, the generation process of payment information, and the receipt process of settlement results.

[0119] Specifically, the payment management module first reads the payment voucher number, payment status, settlement fee data, sending time, return time, and abnormal alarm status from the payment information, and submits the payment voucher number as a query field to the financial institution interface. The financial institution interface returns the settlement result based on the payment voucher number. When the settlement result is a successful payment, the payment management module writes the payment success into the payment information and transmits the payment information to the information processing module. When the settlement result is a failed payment, the payment management module writes the payment failure and the reason for failure into the payment information and writes the payment failure into the abnormal alarm status. When the settlement result is in progress, the payment management module retains the payment voucher and writes the progress status into the system log.

[0120] Further, after receiving the settlement result, the information processing module reads the pending invoice voucher, advertising expense statement data, payment voucher, and payment period status associated with the payment information. When the settlement result is a successful payment, the information processing module writes the settlement expense data from the advertising expense statement data, the payment voucher, the payment information, and the payment period status into the data storage module, and updates the payment period status to "payment successful." When the settlement result is a failed payment, the information processing module writes the payment voucher, the payment information, and the abnormal alarm status into the data storage module, and updates the payment period status to "payment failed." When the settlement result is "processing," the information processing module does not change the original payment period status and writes the payment information and the payment voucher into the pending record.

[0121] Specifically, when the data storage module receives the write data, it associates the settlement fee data in the advertising expense statement data with the payment voucher number, and associates the payment status in the payment information with the billing period status. When the payment status is successful, the data storage module records the invoice characteristic value, advertising expense statement data, payment voucher, payment information, settlement result, and billing period status. When the payment status is failed, the data storage module records the payment voucher, payment information, abnormal alarm status, and billing period status. After completing the write operation, the data storage module returns the write result to the information processing module. If the write result is abnormal, the information processing module writes the data storage abnormality to the system log and retains the payment information and the payment voucher.

[0122] Furthermore, when the information processing module generates system logs, it writes the following processes into the same log record: the invoice content reading process (S200), the advertising expense statement data filtering process (S400), the pending invoice classification process (S500), the posting approval result generation process (S500), the certified invoice acquisition process (S600), the payment voucher creation process (S700), the payment information generation process (S700), and the settlement result reception process in this step. The system log contains the pending invoice voucher number, invoice characteristic value, advertising distribution platform account, settlement expense data, payment voucher number, payment status, payment period status, abnormal alarm status, and writing time. The abnormal alarm status includes missing key information in the invoice content, inconsistent certified invoices, reversed invoices, duplicate data, unqualified posting approval, payment voucher successfully paid, and payment failed.

[0123] Understandably, after the payment period status is updated, the information processing module returns the updated payment period status to the management backend module. After reading the payment period status, the management backend module synchronizes the processing records corresponding to the same advertising distribution platform account, the same configuration relationship, and the same settlement fee data to the latest status. When the payment period status is "payment successful," if subsequent invoice feature values ​​or advertising fee statement data enters S700, the payment management module stops sending payment vouchers to the financial institution interface based on the payment information in the data storage module. When the payment period status is "payment failed," subsequent processing continues to read the retained payment vouchers and payment information, and uses the payment failure as input for S700 payment status tracking.

[0124] In one implementation, the financial institution interface returns a successful payment settlement result, and the payment management module writes the successful payment to the payment information. After reading the payment information, the information processing module writes the settlement fee data, payment voucher, payment information, and billing status from the advertising expense statement data to the data storage module and generates a system log. In another implementation, the financial institution interface returns a failed payment settlement result, and the payment management module writes the failed payment to the payment information and an anomaly alarm status. The information processing module writes the payment voucher, payment information, and anomaly alarm status to the data storage module and generates a system log. In yet another implementation, the financial institution interface returns a processing status, the payment management module retains the payment voucher, and the information processing module writes the processing status to the system log and retains the original billing status.

[0125] In one specific embodiment, the payment information generated by S700 includes a payment voucher number, payment status, settlement fee data, sending time, and return time. The payment management module receives the settlement result returned by the financial institution interface based on the payment voucher number. If the settlement result is a successful payment, the information processing module writes the settlement fee data, payment voucher, payment information, and billing status from the advertising expense statement data into the data storage module, and updates the billing status to successful payment. If the settlement result is a failed payment, the information processing module writes the payment voucher, payment information, and abnormal alarm status into the data storage module, and updates the billing status to failed payment. After writing is complete, the information processing module generates a system log, which records the entire processing procedure from reading the invoice content to receiving the settlement result.

[0126] Summary of the technical effects of this step: This step converts the payment information generated by S700 into settlement results, billing status, and system logs. This step writes the advertising expense statement data, payment vouchers, payment information, and billing status into the data storage module, forming a closed loop for advertising expense processing. The system logs generated in this step record the processing of each main step, providing a record basis for subsequent duplicate data filtering and abnormal alarm status handling.

[0127] Example 2: Figure 2 This diagram illustrates a structural block diagram of an automatic reconciliation and payment processing method for advertising expenses based on value-added tax (VAT) invoices, according to an embodiment of the present invention. Figure 2 As shown, the structure may include:

[0128] The information transmission and receiving module 01 is used to receive electronic files or scanned images of VAT special invoices, advertising distribution platform accounts, configuration relationships, advertising fee application rules, and payment period status, and transmit them to the information processing module to generate an invoice verification request. Specifically, the information transmission and receiving module receives electronic files or scanned images of VAT special invoices from advertising distribution platforms, advertising fee placement platforms, or management backend modules, and simultaneously receives advertising distribution platform accounts, configuration relationships, advertising fee application rules, and payment period status. The information transmission and receiving module registers fields for the received objects, recording the electronic files or scanned images of VAT special invoices as invoice file fields, the advertising distribution platform accounts as account fields, the configuration relationships as relationship fields, the advertising fee application rules as rule fields, and the payment period status as status fields. When an invoice file field, account field, relationship field, rule field, or status field is missing, the information transmission and receiving module transmits the corresponding content to the information processing module to register an abnormal alarm status. After the fields are registered, the information transmission and receiving module transmits the invoice file field, account field, relationship field, rule field, and status field to the information processing module. The information processing module then generates an invoice verification request and provides the invoice verification request to the information collection module for invocation.

[0129] Information acquisition module 02, connected to the information processing module, is used to perform graphic and text recognition on the electronic file or scanned image of the VAT special invoice based on the invoice verification request, read the invoice information, and generate invoice content and invoice feature values. Specifically, the information acquisition module receives the invoice verification request from the information processing module, retrieves the electronic file or scanned image of the VAT special invoice from the invoice verification request, and reads the advertising distribution platform account, configuration relationship, advertising fee application rules, and payment period status. The information acquisition module performs format recognition, orientation correction, edge cropping, clarity processing, and data cleaning on the electronic file or scanned image of the VAT special invoice, removing data with missing key information. The information acquisition module divides the invoice area through graphic recognition, reads the invoice information through text recognition, and writes the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, seller's taxpayer identification number, and remarks into the invoice content. The information collection module writes the invoice code, invoice number, invoice date, invoice type, and tax-exclusive amount into the invoice feature value. The information collection module then transmits the invoice content and the invoice feature value to the information processing module, which provides them to the cloud-based cross-database access module for use.

[0130] The cloud-based cross-database access module 03, connected to the information processing module and the advertising distribution platform, is used to send scheduled task instructions based on the invoice content and invoice feature values ​​to obtain affiliate promotion data, proprietary site promotion data, and settlement fee data, and generate communication summary data. Specifically, the cloud-based cross-database access module receives invoice content, invoice feature values, advertising distribution platform account, configuration relationship, advertising fee application rules, and billing status from the information processing module. The cloud-based cross-database access module generates scheduled task instructions based on the advertising distribution platform account and billing status, and sends the scheduled task instructions to the advertising distribution platform. The advertising distribution platform returns advertising content, advertising playback plan, advertising plan budget, daily percentage limit for advertising, advertising creative content, configuration relationship, advertising view clicks, advertising traffic, and settlement fee data. The cloud-based cross-database access module receives affiliate promotion data, proprietary site promotion data, and settlement fee data, and summarizes the above data according to the advertising distribution platform account, configuration relationship, advertising fee application rules, and billing status to form communication summary data. The cloud-based cross-database access module transmits the communication summary data to the information processing module, which then filters the advertising expense reconciliation data.

[0131] Information processing module 04 is used to filter advertising expense reconciliation data based on the communication summary data and the invoice content, generate pending invoice vouchers, and obtain certified invoices from the tax bureau-authorized invoice digital lifecycle management cloud platform system based on the posting approval results and the invoice feature values, check for red-inked and duplicate data, and generate invoice verification results. Specifically, the information processing module receives communication summary data from the cloud cross-database access module and calls the invoice content and invoice feature values ​​from the information collection module. The information processing module compares the seller's name and seller's taxpayer identification number in the invoice content with the advertising distribution platform account in the communication summary data, compares the buyer's name and buyer's taxpayer identification number in the invoice content with the configuration relationship, compares the amount, tax rate, tax amount, and total price including tax in the invoice content with the settlement expense data, and compares the remarks in the invoice content with the payment period status to extract advertising expense reconciliation data. The information processing module encapsulates the invoice content, invoice feature values, advertising expense reconciliation data, configuration relationships, advertising expense application rules, payment period status, abnormal alarm status, and system logs into an invoice pending processing credential, and transmits this credential to the data set comparison algorithm engine module. After receiving the posting approval result from the data set comparison algorithm engine module, the information processing module retrieves the certified invoice from the tax bureau-authorized invoice digital lifecycle management cloud platform system based on the invoice feature values, and performs field comparison, red-ink cancellation checks, and duplicate data checks on the certified invoice to generate an invoice verification result. The information processing module then transmits the invoice verification result to the payment management module.

[0132] The data set comparison algorithm engine module 05, connected to the information processing module, is used to classify, filter duplicate data, and compare them one by one based on the pending invoice vouchers to generate the posting approval result. Specifically, the data set comparison algorithm engine module receives the pending invoice vouchers from the information processing module and reads the invoice content, invoice feature values, advertising expense statement data, configuration relationships, advertising expense application rules, payment period status, abnormal alarm status, and system logs. The data set comparison algorithm engine module classifies the data according to the following categories: single settlement expense data corresponding to a single advertising distribution platform, single invoice content corresponding to different advertising distribution platforms, different payment period statuses corresponding to a single advertising distribution platform, and single settlement expense data corresponding to different invoice content. After classification, the data set comparison algorithm engine module calls the data storage module to retrieve identical invoice feature values, identical advertising expense statement data, identical payment vouchers, and identical payment information, filtering out duplicate data. The data set comparison algorithm engine module compares the tax rate, amount, seller's financial information, buyer's financial information, configuration relationships, advertising expense application rules, and settlement expense data one by one to generate the posting approval result. The data set comparison algorithm engine module transmits the posting approval result to the information processing module, which then obtains the certified invoice and generates the invoice verification result.

[0133] Payment management module 06, connected to the information processing module and the financial institution interface, is used to create payment vouchers based on the invoice verification results, send the payment vouchers to the financial institution interface, generate payment information, and receive settlement results based on the payment information. Specifically, the payment management module receives the invoice verification results from the information processing module and reads the pending invoice vouchers, advertising expense statement data, invoice feature values, and payment period status associated with the invoice verification results. When the invoice verification results are qualified, the payment management module calls the data storage module to retrieve the same invoice feature values, the same advertising expense statement data, the same payment vouchers, and the same payment information. When successfully paid payment information is retrieved, the payment management module stops sending payment vouchers to the financial institution interface and writes "payment successful" to the abnormal alarm status. When no successfully paid payment information is retrieved, the payment management module creates payment vouchers based on the invoice content, invoice feature values, advertising expense statement data, settlement expense data, configuration relationships, advertising expense application rules, and payment period status. The payment management module sends the payment vouchers to the financial institution interface and receives the payment status, return time, and failure reason returned by the financial institution interface, generating payment information. The payment management module receives the settlement result based on the payment information and transmits the settlement result to the information processing module and the data storage module.

[0134] Data storage module 07, connected to the information processing module and the payment management module, is used to write advertising expense statement data, payment vouchers, payment information, billing status, abnormal alarm status, and system logs. Specifically, the data storage module receives advertising expense statement data, billing status, abnormal alarm status, and system logs from the information processing module, and receives payment vouchers, payment information, and settlement results from the payment management module. The data storage module associates the settlement expense data in the advertising expense statement data with the payment vouchers, associates the payment status in the payment information with the billing status, and associates the abnormal alarm status with the system logs. When the settlement result is a successful payment, the data storage module writes the advertising expense statement data, payment vouchers, payment information, and billing status. When the settlement result is a failed payment, the data storage module writes the payment vouchers, payment information, and abnormal alarm status. The data storage module returns the writing result to the information processing module, and the information processing module generates system logs based on the writing result.

[0135] The result feedback module 08, connected to the information processing module, receives abnormal alarm statuses corresponding to missing key information in invoice content, inconsistent certified invoices, invoices already reversed, duplicate data, unqualified posting approval, successful payment of payment vouchers, and payment failure, and writes these abnormal alarm statuses to the system log. Specifically, the result feedback module receives abnormal alarm statuses from the information processing module, the data set comparison algorithm engine module, and the payment management module. The result feedback module registers abnormal alarm statuses according to the correlation between invoice verification requests, invoice content, invoice feature values, advertising expense statement data, pending invoice vouchers, posting approval results, invoice verification results, payment vouchers, and payment information. The result feedback module writes the missing key information invoice content, inconsistent certified invoices, invoices already reversed, duplicate data, unqualified posting approval, successful payment of payment vouchers, and payment failure to the system log, and transmits the system log to the data storage module. After completing the writing, the data storage module returns the writing result to the information processing module, and the information processing module updates the account period status based on the writing result.

Claims

1. A method for automatic reconciliation and payment of advertising expenses based on value-added tax (VAT) invoices, characterized in that, include: S100: Receive electronic files or scanned images of VAT special invoices, advertising distribution platform accounts, configuration relationships, advertising fee application rules and billing status, and generate an invoice verification request. S200: Based on the invoice verification request, perform graphic recognition and text recognition, read the invoice information, and generate invoice content and invoice feature values; S300. Based on the invoice content and the invoice feature value, send a scheduled task instruction to the advertising distribution platform to obtain alliance promotion data, own site promotion data and settlement fee data, and generate communication summary data. S400: Based on the communication summary data and the invoice content, filter the advertising expense statement data and generate an invoice pending processing voucher; S500: Based on the classification of the pending vouchers, filter duplicate data, compare them one by one, and generate posting approval results; S600: Based on the posting approval result and the invoice feature value, obtain the certified invoice, check for red-inked and duplicate data, and generate the invoice verification result; S700: Based on the invoice verification result, create a payment voucher, send the payment voucher to the financial institution interface, and generate payment information; S800: Receive settlement results based on the payment information, update the billing status, and generate system logs.

2. The method according to claim 1, characterized in that, In S200, the electronic file or scanned image of the VAT special invoice is subjected to format recognition, orientation correction, edge cropping, clarity processing, and data cleaning to remove missing key information; the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's name, seller's name, buyer's taxpayer identification number, and seller's taxpayer identification number are read to form the invoice content and the invoice feature value.

3. The method according to claim 1, characterized in that, In S300, the cloud-based cross-database access module accesses each advertising distribution platform according to the scheduled task instructions, obtains the advertising content, advertising playback plan, advertising plan budget, daily percentage limit corresponding to advertising, advertising creative content, configuration relationship, advertising view clicks, advertising traffic and settlement fee data of each advertising distribution platform, and writes the obtained data into the communication summary data.

4. The method according to claim 1, characterized in that, In S400, filtering the advertising expense reconciliation data includes: comparing the seller's name and taxpayer identification number in the invoice content with the advertising distribution platform account; comparing the buyer's name and taxpayer identification number in the invoice content with the configuration relationship; comparing the amount, tax rate, tax amount, and total price including tax in the invoice content with the settlement expense data; comparing the remarks in the invoice content with the payment period status; and extracting the advertising expense reconciliation data.

5. The method according to claim 1, characterized in that, In S500, the categories include single settlement fee data corresponding to a single advertising distribution platform, single invoice content corresponding to different advertising distribution platforms, different billing periods corresponding to a single advertising distribution platform, and single settlement fee data corresponding to different invoice contents; the comparison includes tax rate, amount, seller's financial information, buyer's financial information, configuration relationship, advertising fee application rules, and settlement fee data.

6. The method according to claim 1, characterized in that, In S600, an authenticated invoice is downloaded from the tax authority's authorized invoice digital lifecycle management cloud platform system based on the invoice characteristic value. If the authenticated invoice does not match the invoice code, invoice number, invoice date, invoice type, amount excluding tax, tax rate, tax amount, total price including tax, buyer's taxpayer identification number, or seller's taxpayer identification number in the invoice content, or if the authenticated invoice has been cancelled, an unqualified invoice verification result is generated.

7. The method according to claim 1, characterized in that, In S700, before creating the payment voucher, duplicate data filtering is performed on the invoice feature value, the advertising expense statement data, the payment voucher, and the payment information; when the payment information indicates successful payment, the sending of the payment voucher to the financial institution interface is stopped; when the payment information indicates payment failure, the payment voucher is retained and payment status tracking continues.

8. The method according to claim 1, characterized in that, In S800, the system log records the invoice content reading process, the advertising expense statement data filtering process, the invoice pending processing voucher classification process, the posting approval result generation process, the certified invoice acquisition process, the payment voucher creation process, the payment information generation process, and the settlement result receiving process.

9. The method according to claim 1, characterized in that, The abnormal alarm statuses include missing key information in invoice content, inconsistent certified invoices, invoices that have been reversed, duplicate data, unqualified posting approval, payment vouchers that have been successfully paid, and payment failure; the result feedback module writes the abnormal alarm statuses into the system log.

10. The method according to claim 1, characterized in that, In S800, when the settlement result is a successful payment, the settlement fee data, the payment voucher, the payment information and the billing status in the advertising fee statement data are written into the data storage module. When the settlement result is a payment failure, the payment voucher, the payment information, and the abnormal alarm status are written into the data storage module.

Images