Invoice Mailing SOP

Write an invoice mailing SOP for [BUSINESS_NAME], a [BUSINESS_TYPE]. Facts: - Accounting tool, or "none": [ACCOUNTING_TOOL] - Who is allowed to send an invoice: [SENDER_ROLE] - What has to be true before an invoice goes out: [READY_WHEN] - How it is delivered: [DELIVERY] (email, mail, or both) - Where the customer pays: [PAY_PATH] - Reminder days, using only the numbers given: [REMINDER_DAYS] - Who gets told if it is still unpaid after the last reminder: [ESCALATE_TO] - What the tool already does by itself, or "nothing": [TOOL_DOES] - What a person still does by hand: [PERSON_DOES] Format: 1. Title, version v1.0, blank last-updated date. 2. Purpose: get a correct invoice to the customer and know the date it went. 3. Trigger: the moment [READY_WHEN] is true. 4. Steps in order. Mark each step "Person" or "Tool". 5. A "sent" definition. Sent means the customer has the invoice, not that someone meant to send it. 6. The reminder schedule from [REMINDER_DAYS] only. Do not add extra reminders. 7. The failure case: bounced email, wrong amount, or no pay path. Name [ESCALATE_TO]. 8. A one-line note titled "Automate after this is true" that lists only the [TOOL_DOES] steps. If [TOOL_DOES] is "nothing", say the SOP stays manual until the tool can send and log the invoice. Rules: - Do not invent prices, late fees, interest, or legal threats. - Do not invent a software feature. If [TOOL_DOES] does not name it, a person does it. - If [ACCOUNTING_TOOL] is "none", say "the invoice tool" and do not pick QuickBooks, Xero, or any other product. - No "just circling back". The reminder wording can be firm and plain.