What the documents look like
Channel receivables collection happens after credit sales. The work centres on credit control and cash recovery rather than on matching buyers with sellers. The documents handled day to day include the accounts receivable ageing table, the collection letter, the credit agreement and the shipment freeze notice. These materials come from the finance system, bank receipts, dealer orders and sales contracts.
For store service and internal training, these documents serve as the basis for checking and handover. The interactive forms step collects the information that later nodes need. Staff compare what a draft sentence or a handover request states against the wording of the source document, and they record any gap that the source does not cover.
Constraints at the interactive forms step
The form input node is a user interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. The node collects the information the user fills in and passes it to later nodes. It does not carry business database functions of its own. The user selection node is also a user interaction node with the same interaction state behaviour. It evaluates the user's choice and executes the corresponding branch.
Field validation, business approval, write-back and batch operations need to be implemented in an external system or in later nodes. Neither interaction node performs those actions. Retrieval and form submission are not authorization; a submitted value is not an approval, and a selected option is not an executed action.
Hypothetical paper exercise sample: A brand finance department holds a credit agreement text reading "Dealer A has a credit limit of RMB 500,000, payment term 30 days, and the shipment freeze condition is exceeding the credit limit without repayment." An accounts receivable ageing table shows Dealer A's current receivable balance as RMB 520,000. A draft sentence awaiting review reads "Dealer A has exceeded the credit limit, so the shipment freeze should be executed." The check compares the limit, payment term and freeze condition in the credit agreement against the ageing table figure, and confirms whether the draft sentence cites the freeze trigger condition as the agreement states it. The agreement text does not describe a specific authorization process for executing the freeze, so that authorization detail remains an evidence gap.
Configuration and implementation checks
| Configuration item | Setting relevant to this page | Note |
|---|---|---|
| Form input node | Can be added repeatedly, triggers execution | Collects filled form information and passes it to later nodes |
| User selection node | Can be added repeatedly, triggers execution | Executes a branch according to the user's choice |
| Required information check | List the information this task cannot omit | Test the missing-item behaviour and the completed behaviour separately |
| Interaction state | Workflow state is recorded when the node triggers | Execution continues after the interaction completes |
| Downstream division of work | Field validation, business approval, write-back | Implemented in an external system or later nodes |
| Hypothetical trial starting value | Credit limit RMB 500,000 | Starting value for this paper exercise, compared with the ageing table balance of RMB 520,000 |
The RMB 500,000 figure is a hypothetical starting value chosen for this exercise so that it sits below the RMB 520,000 balance and gives a clear comparison point. It is not an official default. The comparison method is a direct reading of the two stated amounts against the freeze condition in the agreement text.
Three common errors
- Treating information submitted through the form input node as a business approval result. The form node collects and passes on what was filled in; approval requires an external system or a later node. The check compares the submitted value with an approval status field and confirms whether a separate approval record exists.
- Treating the branch decision of the user selection node as a personnel directory or a business data selector. The node executes a branch according to the user's choice and does not filter business data. The check examines whether the branch condition references the correct selected value and confirms that the source of the options is unrelated to business data.
- Adding authorization or effectiveness clauses to a draft sentence that the source does not contain. In the hypothetical sample, the credit agreement states only the limit, payment term and freeze condition, and does not describe a specific authorization process for executing the freeze. The check compares the draft sentence against the original agreement wording; missing authorization information is recorded as an evidence gap.
How to verify the setup
- Input the credit agreement text and the ageing table data from the hypothetical sample, then compare the draft sentence "Dealer A has exceeded the credit limit, so the shipment freeze should be executed" against the freeze condition in the agreement. The expected observation is that the limit, payment term and freeze condition cited in the draft match the agreement wording, and that no authorization or effectiveness clause absent from the agreement has been added.
- Input the credit agreement text from the hypothetical sample and compare the required information collected by the form input node against the key fields in the agreement: limit, payment term and freeze condition. The expected observation is that a missing item prompts the user to supply it, and that once completed the information is passed to later nodes.
- Input the credit agreement text and the ageing table data from the hypothetical sample and compare the branch condition of the user selection node against the freeze condition in the agreement. The expected observation is that a matching selected value executes the corresponding branch, while a selected value that does not match the agreement condition is recorded as pending verification rather than automatically judged as exceeding the credit limit.