Proposal and reminder example
Illustrative sample data from a fictional company. It demonstrates the records and relationships described on this page.
| Customer workflow | Example | Value / date | State |
|---|---|---|---|
| Quotation · QTN-00042 | Crescent Distribution · phase 2 | PKR 185,000.00 | Sent for review |
| Milestone 1 | Discovery and process review | 40% · PKR 74,000.00 | On acceptance |
| Invoice reminder | INV-00128 · Crescent Distribution | Overdue 5 days | Prepared, not sent |
Illustrative fictional records. Reminder delivery remains a deliberate, manual send action after review.
Build a useful proposal
Prepare quotations with line items, milestone and payment-stage details, and formatted terms and conditions. Choose from three print styles before generating the customer document.
Send consistent company documents
Use company branding and profile details on printable quotations, invoices and customer or supplier statements. Company reply-to addresses can be configured and verified for document email workflows.
Follow overdue invoices deliberately
The payment-reminder centre shows overdue invoices, the last follow-up and the next planned reminder. Prepare, review and send manually. Settled invoices leave the reminder queue and duplicate sends are guarded against.
Keep email expectations clear
Email delivery is an explicit send action, not an automatic reminder campaign. Confirm the company sender/reply-to setup and review each document before sending it to a customer.