What the documents look like
Settlement between a supermarket and an entering supplier rests mainly on purchase-and-sale or consignment payables, and the supplier does not necessarily operate a staffed counter on site. That difference shapes the material set for inventory procurement and supplier records. The procurement contract fixes the supply relationship and the settlement basis. The delivery acceptance note records the quantity actually received. The rebate agreement states the deduction conditions. The statement of account carries the result of reconciling transactions over a period. These materials sit across ERP procurement, the supplier portal, POS sales and the finance system, and they refresh weekly or monthly.
For workflow routing, materials spread across several systems mean each node needs an explicit source and destination. A form input node triggers user interaction, the conversation enters an interaction state, and required information collected on submission passes to later nodes. A user selection node evaluates the choice a user makes and runs the matching branch. Both nodes collect values and route; neither performs a business write.
Constraints at the workflow routing step
Interaction nodes record workflow state and wait until the user finishes interacting before execution continues. That behavior belongs to the node itself, and no separate global state-recording switch exists. The dialog box is hidden while the conversation is in the interaction state.
Three constraints follow. First, node output must be passed explicitly to downstream retrieval, judgment or interface nodes, and each input and output is compared item by item. If a collected quantity, period or supplier identifier is not wired into the downstream node, the workflow cannot advance on it. Second, order writes, document backfill and external status synchronization require a separate business interface or a later process; the interaction node produces none of these actions. Third, retrieval returns materials and does not constitute authorization. A relevance setting does not exclude unrelated businesses or unauthorized records, and the same-vector-model requirement for a retrieval library does not extend to a business registration site or another external system.
Hypothetical paper exercise sample. A supplier portal submits a draft statement of account. The source text reads: "Supplier: Huadong Daily Chemical Products Co., Ltd.; settlement period: March 2025; cumulative delivery acceptance quantity: 1,200 cases; rebate agreement deduction: 2%; amount payable stated on the statement: RMB 86,400." A second sentence is proposed for judgment: "The supplier's March 2025 reconciliation has completed approval and payment may be executed." The evidence needed to judge it is an approval record and a payment authorization. The sample provides neither, so the proposed sentence is unsupported.
Configuration and implementation checks
| Configuration item | Setting or check on this page | Basis and comparison method |
|---|---|---|
| Form input node | Collect supplier name, settlement period, accepted quantity | Node enters the interaction state on trigger; submitted values pass to later nodes |
| User selection node | Configure the "reconciliation difference exists" branch | The node runs the matching branch after a user choice; verify each connection |
| Output handoff | Map form fields to the reconciliation check node input | Compare output fields against downstream input fields item by item |
| Retrieval scope | Limit to procurement contract, delivery acceptance note, rebate agreement, statement of account | Check the document type identifier in the library and exclude non-matching items |
| External write | Mark as requiring a separate business interface | The node performs no order write and no document backfill |
| Hypothetical starting value | Enter the rebate deduction as 2% for this trial | Chosen because that value appears in the hypothetical sample text; compare against the deduction stated on the statement |
Three common errors
- Treating the interaction node's state recording as a global switch. A form input node and a user selection node recording workflow state is node behavior. No separate global state-recording switch exists in configuration, and claiming one is unsupported configuration.
- Treating a retrieval result as an authorization basis. In the hypothetical sample, a retrieval hit on the draft statement does not mean the supplier holds payment authorization. The approval record and the payment authorization are both absent and remain unsupported.
- Extending the same-vector-model requirement to external systems. A retrieval library requires the same vector model for joint association. That condition does not apply to a business registration site or another external system; across models, check the identifier and exclude non-matching items.
How to verify the setup
- Enter the three source sentences and the proposed sentence from the hypothetical sample. Compare the claim "has completed approval and payment may be executed" against the fields the sample provides. The sample contains only supplier, period, quantity, deduction and amount, with no approval or authorization field. The expected result is unsupported, and the evidence gap is recorded.
- Enter an empty-result handoff case and check the downstream design against the explicit paper input []. Compare which branch the downstream node takes on receiving an empty array. The expected result is entry into a manual reconciliation branch; the check does not claim that a fictional rule retrieval necessarily returns empty.
- Enter the reconciliation difference selection. Compare the "yes" branch connection of the user selection node against the input of the following reconciliation node. The expected result is entry into the difference reconciliation node when "difference exists" is selected, with the node input fields matching the form output fields item by item. The check guarantees neither a first hit nor full recall.