What the documents look like
Creator commission settlement and commission deduction happen after a sale closes. The objects being checked are valid promotion and after-sales deduction. This page covers citation source tracing during order fulfillment and after-sales question handling, and the materials involved are commission setting records, settlement statements, refund deduction details, and invoices. These materials update weekly or monthly. A single statement can span multiple orders, and a time gap exists between refund deduction details and the settlement statement. Finance settlement staff, Selected Alliance operations staff, and creator business staff each hold different materials. Before citing a source, confirm which entity, which settlement period, and which field the material belongs to.
Constraints at the citation tracing step
The knowledge base search node outputs citation content as an array, and the length can be zero, which means the output path still runs when no content is found. The citation limit is controlled by tokens. The minimum relevance value takes effect only under semantic retrieval or when result reranking is used. Associated knowledge bases require the same vector model; libraries with different vector models cannot be associated together. After the retrieval output is passed to the answering step, each answer sentence must be checked against the cited source text. Retrieval itself does not constitute authorization, and it does not complete approval, payment, or commission deduction.
Hypothetical paper exercise sample: the source text reads, "Party A and Party B signed the Creator Promotion Cooperation Contract on March 1, 2025, agreeing that the settlement cycle is the natural month, commission is calculated on valid orders in the Selected Alliance backend, and refunded orders are deducted in the following month's statement. The April 2025 statement shows March valid order commission totaling RMB 8,600, of which refund deduction is RMB 1,200." The draft sentence to be judged reads, "Party B has completed all March refund deductions, and Party A may arrange payment." This draft sentence treats the existence of refund deduction details as completed deduction. The material only shows statement amounts and does not show deduction execution status or payment authorization.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | Comparison method |
|---|---|---|
| Associated knowledge base | Select the commission setting record library with the same vector model | Check whether the vector model identifier of each selected library matches; exclude libraries that do not match |
| Citation limit | Set to 3000 tokens as the hypothetical starting point for this exercise | Compare with the length of a single statement or refund deduction detail; observe whether citations are truncated |
| Minimum relevance | Set to 0.4 as the hypothetical starting point for this exercise | Compare with semantic retrieval or rerank scores; observe whether low-scoring content is filtered |
| Search mode | Hybrid retrieval | Compare with semantic retrieval alone; observe whether numbered fields are matched |
| Result reranking | Enabled as configured | Compare with unrereanked candidates; observe changes in relevance scores |
| Citation output handoff | Citation array passed to the answering step | Compare each answer sentence with the entity, period, and field in the cited source text |
The starting values are used only for this paper exercise. The reason is that statement text is long and numbered fields need exact matching. Adjust after comparing with single-material length and score distribution.
Three common errors
- Treating retrieval output as completed commission deduction. Retrieval returns citation content only. Deduction execution requires downstream system implementation. The presence of a citation does not equal completed deduction.
- Treating minimum relevance as a permission filter. Relevance is a filtering threshold. It does not exclude unrelated business or unauthorized records. Retrieval does not constitute authorization.
- Associating libraries with different vector models together. Libraries with different vector models cannot be associated together. Check identifiers first, exclude those that do not match, and record the actual observation.
How to verify the setup
- Compare the hypothetical sample source text with the draft sentence. The input is the above material source text and the draft sentence. Compare whether the entity, settlement period, and deduction field match. The draft sentence states "completed deduction" while the source text only shows statement amounts, so the judgment is unsupported.
- Use an empty citation array to check downstream handoff. The input is an explicit paper citation array []. Compare whether the downstream answering step still runs. Observe whether an error or empty answer appears. Do not claim that a fictional rule retrieval will necessarily return [].
- Use different versions of the same statement to check the source. The input is the current version and a historical version of the statement. Compare the values of the same field in the same period. When values are mutually exclusive, record a contradiction. When not stated, record as pending verification.