What the documents look like
Dealer rebate calculation happens after the sale. The work centers on reconciling policy definitions against financial treatment rather than on moving stock. The data sources named for this category are ERP sales records, dealer remittances, the contract ledger, and the finance system. The day-to-day documents are the rebate policy, the volume attainment table, the reconciliation statement, and the red-letter invoice. Updates follow a monthly and quarterly rhythm.
For order fulfillment and after-sales questions, the practical task is to line up the volume attainment table, the reconciliation statement, and the rebate policy, then work through three time-consuming steps: reconciling the attainment definition, deducting returned-goods amounts, and handling invoice offset. Errors here surface as rebate disputes, channel conflict, and incorrect revenue recognition, so the routing step needs to keep collection, branching, and business execution clearly separated.
Constraints at the workflow routing step
The Form Input node and the User Selection node are both user-interaction nodes. When either is triggered, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. The Form Input node collects required information and passes it to later nodes. The User Selection node evaluates the user's choice and executes the corresponding "yes" branch. These two nodes carry collection and branch judgment only. Order writes, document backfill, and external status synchronization require a separate business interface or a later process.
Hypothetical drill sample: the source material reads, "A brand and a dealer signed a 2024 annual rebate agreement providing that the quarterly volume attainment rate is calculated on the net amount after deducting returns, and that the rebate is offset by a red-letter invoice. The dealer submitted the 2024 second-quarter reconciliation statement listing volume and return amounts." The draft sentence to be judged is, "The rebate amount for this quarter has been fully reconciled and can be directly offset by invoice." The draft sentence does not state the reconciling party, the reconciliation period, or the fields reconciled. The source material states only the calculation basis and the offset method. It does not state a completed reconciliation status.
Configuration and implementation checks
| Configuration item | Relation to this page's documents | Implementation check |
|---|---|---|
| Form Input node | Collects required information from the dealer's submitted reconciliation statement | Check whether the submitted information is passed to later nodes |
| User Selection node | Offers a branch choice for questions about the attainment definition | Check whether the "yes" branch connection is verified item by item |
| Interaction state recording | Records workflow state after an interaction node is triggered | Check whether the interaction state appears as described in the documentation |
| Output handoff | Passes collected information to a later retrieval or judgment node | Compare output against input item by item |
| External operation split | Invoice offset requires a separate business interface | Check whether it is declared as a later process |
| Hypothetical trial starting point | This drill uses a quarterly net attainment rate of 90% as the comparison starting point | Compare against the quarterly net figure stated in the contract ledger |
The 90% figure is a hypothetical starting value for this drill only. It was chosen so that the comparison method is explicit: read the quarterly net attainment rate from the contract ledger for the same quarter, then compare the two values on the same basis. It is not an official default, limit, or unit.
Three common errors
- Treating reconciliation-statement information collected by the Form Input node as a completed reconciliation. The form collects values only. A reconciliation conclusion requires separate human judgment or a downstream node.
- Treating the "yes" branch of the User Selection node as authorized execution. The branch decides workflow direction only. Invoice offset requires a separate business interface.
- Judging the draft sentence as fully reconciled when the material does not state the reconciliation period or fields. An unstated status is unsupported and must be recorded as an evidence gap.
How to verify the setup
- Input the source material and the draft sentence from the hypothetical drill sample. Compare whether the draft sentence states the reconciling party, the period, and the fields. The material states only the calculation basis and the offset method, and the draft sentence does not state a completed reconciliation status, so the judgment is unsupported.
- Input the information submitted at the Form Input node. Compare whether that information reaches the later node. If the later node does not receive it, the output handoff is incomplete.
- Input the selection result from the User Selection node. Compare whether the "yes" branch connection is verified item by item. If the branch is not connected or not verified, the branch execution condition is not met.
These checks describe expected observations. They do not report a completed test, an approval, or a deployment. Retrieval and form submission do not constitute authorization. Where a document field is not provided, the value remains unknown.