What the documents look like
Producer export tax credit and refund combines domestic sales tax offset with export refund in one calculation. That calculation scope differs from the export refund calculation used by trading enterprises, and the difference shapes how operating reports draw their data. Within a single period, the export tax credit and refund declaration detail table, the sales subsidiary ledger, and the export customs declaration form must be gathered under consistent scopes such as self-produced exports and free-on-board price differences. A mismatch in any one scope makes the report disagree with the filed declaration.
Four sources feed this work: the electronic tax bureau, ERP sales records, customs electronic information, and financial ledgers. These four sources do not share field names or period boundaries. The database operations step therefore begins with comparability across the same entity, the same period, and the same field, and only then moves the data into one table. The declaration detail table, export contract, sales subsidiary ledger, and export customs declaration form are the documents that carry the values being compared.
Constraints at the database operations step
Business source data storage and the vector retrieval backend carry different responsibilities. Connection settings are checked separately for each, according to the actual deployment plan, and configuration values are not inferred from variable names. Connection count, errors, and latency are observed against the system's own workload rather than copied from an untested concurrency threshold. Backup generation and actual restore are verified as two separate actions, each keeping a checkable sample and record. After a database or service configuration change, the same business sample is rechecked; a running process does not by itself demonstrate that business output is correct.
Hypothetical drill sample: an export producer (recorded in the material as "Factory A") has a July 2024 export tax credit and refund declaration detail table stating "period July 2024, export sales 1,200,000 RMB, of which self-produced goods 1,000,000 RMB." The same month's sales subsidiary ledger states "export sales 1,200,000 RMB, domestic sales 800,000 RMB." The export customs declaration form states "export date 15 July 2024, terms FOB, total converted to 1,180,000 RMB." The draft sentence to be assessed is: "Factory A's self-produced exports for July 2024 have all completed export tax credit and refund declaration, and the declared amount matches the customs declaration amount." Two points require attention during review: the customs declaration amount of 1,180,000 RMB differs from the declaration detail table amount of 1,200,000 RMB by 20,000 RMB, which is an unverified FOB price difference item; the phrase "have all completed declaration" lacks evidence of acceptance or review status and can only be recorded as unverified.
Configuration and implementation checks
The table below lists only settings or implementation check items relevant to this page's primary task. The values are hypothetical starting points for this drill, used for comparison against the system's own observations, and do not represent official defaults.
| Item | Hypothetical starting point for this drill | Reason and comparison target |
|---|---|---|
| Database connection pool limit | 20 | Compared against the system's own observed peak for monthly report concurrent queries; no external threshold is cited |
| Business database and log database connection addresses | Configured separately | Check whether the two data sets land on the same instance, confirmed against the actual deployment |
| Vector retrieval backend connection address | Filled in per the chosen deployment | Checked separately from the business source database; purpose is not inferred from the name |
| Backup generation and restore verification | One checkable sample kept for each | Generation result and restore result are verified separately, not merged into one check |
| Post-change recheck sample | Fixed to Factory A data for July 2024 | The same sample is compared before and after a change to avoid sample drift |
| Report period field | Unified as the period attribute | Compared one by one against the period fields in the declaration detail table, sales subsidiary ledger, and customs declaration form |
Three common errors
- Treating the declaration detail table amount and the customs declaration amount as matching. The input is the two documents above; the comparison is 1,200,000 RMB against 1,180,000 RMB; the observable result is an unexplained 20,000 RMB difference, which is an unverified FOB price difference item and cannot be written as the declared amount matching the customs declaration.
- Treating a pending review status as a completed declaration. The input is the draft sentence and the available material; the comparison is "have all completed export tax credit and refund declaration" against the acceptance or review evidence absent from the material; the observable result is that the statement is unsupported and can only be recorded as unverified.
- Using retrieval similarity in place of permission or entity isolation. The input is a cross-database retrieval request; the comparison is the entity identifier and access scope of the returned records; the observable result is that a similarity score does not carry authorization judgment, and records outside the authorized scope still require manual exclusion.
How to verify the setup
- Verification one: Input the three hypothetical documents above together with the draft sentence. Compare the 1,200,000 RMB in the declaration detail table, the 1,180,000 RMB in the customs declaration form, and the 1,200,000 RMB in the sales subsidiary ledger, along with the period fields in all three. If the periods agree while a 20,000 RMB difference remains without explanation, the condition for "difference pending verification" is met and the condition for "amounts match" is not met.
- Verification two: Input the draft sentence "have all completed export tax credit and refund declaration." The comparison target is whether the material contains a declaration acceptance receipt, a review pass record, or a refund record. If all are absent, the condition for "unsupported" is met. If an acceptance receipt is later supplied, the receipt's entity and period must be rechecked against Factory A and July 2024.
- Verification three: Input a retrieval request that clearly labels the target database identifier. Compare the entity identifier of returned records against the request's authorized scope. If records with a mismatched entity identifier appear, the condition for "manual exclusion required" is met. If the result is empty, only that observation is recorded; no inference is drawn that a rule-based retrieval necessarily returns empty. Databases using different vector models are not associated together; identifiers are checked first, mismatched records are excluded, and the actual observation is recorded.