Six kinds of proposal exist today, and each one ends at a draft — the last step is always a person's, in the ordinary screens:
- Draft purchase order. A supplier, a currency (or the party's own default) and the order lines — product, quantity, unit of measure, warehouse, and a price and its recorded source per line. A line's price may be deliberately left blank: it stays blank on the proposal and is stored at 0.00 on the draft until a person prices it — nothing fills it in silently.
- Draft sales order. The same shape, for a customer.
- Draft payment reminders. The proposal carries the chasing rules — how many days overdue, above what minimum amount — and executing it runs the dunning selection and records the reminder runs, unsent. Sending the reminders stays where it has always been: with a person, in the receivables workflow, who can read what they are about to send.
- File a captured document. Documents that arrive through capture (Chapter 14) wait to be turned into records. The proposal names a processed capture, and executing it creates the draft bill or expense from it and files the capture against that draft — nothing approved, nothing posted. If the capture is not ready, the proposal's preview says so and why.
- Draft a stock adjustment. Product, warehouse, counted quantity and the adjustment account — all four are required, because an adjustment without an account to land in would be a fiction. Executing creates the draft adjustment document carrying the counted quantity. No stock moves; stock moves when a person posts the adjustment through its own workflow.
- Create replenishment drafts. Draft purchase orders, draft work orders, or both, generated from the replenishment position — the same generator the Inventory chapter describes, with the same coverage netting. This one depends on the inventory planning or advanced switch; with both off, the preview names that as the reason it cannot run, and execution refuses with the same reason in plain words.