What the documents look like
Channel receivables collection happens after credit sales, so the working materials centre on credit limits and cash recovery. The documents in scope are the receivables ageing table, the collection letter, the credit agreement and the shipment freeze notice. Brand finance staff, sales back-office staff and distributor owners are the typical people handling them, and the underlying data comes from the finance system, bank receipts, distributor orders and sales contracts.
For copy drafting, these documents act as evidence. The ageing table supplies the period and the amount basis. The credit agreement supplies the limit and the payment term. The collection letter and the shipment freeze notice supply status descriptions. Each promotional sentence in a draft needs to trace back to wording in one of these materials. The update rhythm of the source data does not change how the routing step behaves, so it is not treated as a routing condition here.
Constraints at the workflow routing 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 only after the user completes the interaction. Required fields are collected on submission and passed to later nodes. The user selection node behaves the same way at the interaction level, and after the user makes a choice it runs the corresponding "yes" branch. Both nodes record workflow state and wait for the user before continuing.
For copy drafting, the constraint is that the ageing figures, credit terms and letter or notice statuses used as drafting evidence must be collected as explicit form fields or selection options and passed item by item to later nodes. Order writes, document backfill and external status synchronisation require a separate business interface or a later process. The interaction nodes themselves do not perform those actions.
Hypothetical paper exercise sample. The source material reads: "As of 30 June 2024, the receivables ageing table for Distributor A shows RMB 120,000 overdue in the 61 to 90 day band; the credit agreement sets that distributor's credit limit at RMB 500,000 with a 60 day payment term; the shipment freeze notice states that shipment to that distributor is suspended from 5 July 2024, with status issued but unconfirmed." The draft sentence to be assessed is: "This distributor's credit limit has been exhausted and the overdue amount has entered freeze processing." The checking points are these: the ageing table gives the overdue amount and band, the credit agreement gives the limit and term, and the freeze notice gives the suspension start date and status. The phrase "credit limit has been exhausted" needs both the credit agreement and order data to support it. The phrase "has entered freeze processing" needs a confirmed status on the freeze notice, and in this sample the notice status is issued but unconfirmed.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Ageing band field | Form input | Collects the overdue day band and the corresponding amount as the period basis for the draft |
| Credit limit field | Form input | Collects the credit limit and payment term for checking limit wording in the draft |
| Letter status selection | User selection | Selects the current status of the collection letter or freeze notice and follows the "yes" branch from that choice |
| Draft sentence handover | Output passing | Passes collected fields explicitly to later judging nodes so input and output can be compared item by item |
| External sync separation | Implementation check | Order writes and external status synchronisation connect to a separate business interface and are not performed by the interaction nodes |
Three common errors
- Writing the overdue amount from the ageing table as an exhausted credit limit. The ageing table gives only the overdue amount and band; whether the limit is exhausted needs the credit agreement and order data together. Check: input the sample source text and the draft sentence, compare whether the limit conclusion in the draft has a corresponding field, and observe whether a limit judgement was drawn from the ageing table alone.
- Writing the freeze notice status "issued but unconfirmed" as having entered freeze processing. Issued but unconfirmed and confirmed are two different states. Check: input the freeze notice status field and the draft sentence, compare the status values, and observe whether the draft presents an unconfirmed status as executed.
- Assuming information collected by the interaction nodes is written into the business system by default. Form input and user selection only collect and pass information. Check: input the node outputs and the downstream node connections, compare whether any connection points to an order write or external synchronisation, and observe whether those actions have a separate interface to carry them.
How to verify the setup
- Input the ageing table text, the credit agreement text and the draft sentence from the hypothetical sample. Compare whether the limit conclusion in the draft sentence has supporting credit agreement and order fields. Observe whether a limit judgement was drawn from the ageing table alone. Expected result: when the limit conclusion has no corresponding field, mark it as pending verification.
- Input the freeze notice text and the draft sentence. Compare the status field value with the wording of the draft sentence. Observe whether the draft presents issued but unconfirmed as executed. Expected result: when the status values do not match, mark it as pending verification.
- Input the list of node outputs and downstream node connections. Compare whether any connection points to an order write or external synchronisation. Observe whether those actions have a separate interface to carry them. Expected result: when no separate interface exists, record the gap and do not treat the action as implemented.