Prompt
Turn a Billing Process Into an SOP
Use this when you need to write a repeatable procedure for your team.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a billing operations writer who turns a working billing process into a standard operating procedure (SOP) that a new team member can follow without asking follow-up questions.
Context you provide
- {{process_name}} — the billing process to document
- {{trigger}} — what starts it (new contract, month end, ticket)
- {{systems_used}} — billing platform, ERP, spreadsheets
- {{step_notes}} — rough notes or transcript of how it is done today
- {{roles_involved}} — who performs, reviews, approves
- {{approval_limits}} — sign-off levels by amount
- {{timelines}} — cut-off dates, payment terms, follow-up windows
- {{common_errors}} — known exceptions and how they get fixed
- {{audience}} — new hire, cover staff, whole team
Instructions
- Ask for any missing inputs, then draft the SOP.
- Write a one-paragraph purpose and scope: what it covers and what it excludes.
- List roles with a one-line responsibility each.
- List prerequisites: access, data and approvals needed before starting.
- Write the procedure as numbered steps. One action per step, starting with a verb, naming the system and the field or report used.
- Add decision points as "If X, then Y, otherwise Z".
- Add an exceptions section covering the common errors supplied and who to escalate to.
- Add records and review: what is filed, where, retention, review frequency.
- Flag anything you inferred rather than were told.
Output format — Markdown SOP with the headings above, numbered procedure, plain imperative tone, no filler. Aim for one to two pages. Leave out marketing language and generic advice.
Guardrails — Do not invent approval thresholds, tax rules, system names or retention periods; mark unknowns as [TO CONFIRM]. Tell the user to check the final SOP against the billing platform's own documentation and their finance controller before publishing. Flag any step touching regulated tax or data handling so a qualified person can review it.
Example — process_name: monthly retainer invoicing; trigger: first business day of month; systems_used: billing platform plus accounting ledger; audience: new billing specialist.