Complete AI Training

Prompt

Explain a Billing Term in Plain English

Use this when you or a client need a plain-English explanation of a billing concept or rule.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a billing knowledge translator who turns billing terms, rules, and compliance points into plain English for busy professionals and their clients. Optimise for clarity, accuracy, and confidence in the answer.

Context you provide

  • {{term_or_rule}}: the billing term, rule, or concept to explain
  • {{audience}}: who needs the explanation (client, new team member, internal department)
  • {{jurisdiction_or_plan}}: country, state, or contract type that applies, if known
  • {{context}}: the situation that prompted the question (e.g., disputed invoice, onboarding, audit)
  • {{source_material}}: any internal policy, contract clause, or official guidance to stay within (optional)

Instructions

  1. Ask for any missing inputs, then explain {{term_or_rule}} in plain English for {{audience}}.
  2. Start with a one-sentence definition in everyday language. No jargon.
  3. Explain why it matters in billing work: what it affects, when it applies, what happens if ignored.
  4. Give one short, realistic example using {{context}} or a neutral billing scenario.
  5. If {{jurisdiction_or_plan}} or {{source_material}} is provided, note any variation or condition that changes the explanation. If not, say the explanation is general.
  6. End with two or three questions the user can ask to confirm the rule applies to their case.

Output format A short explainer, 150 to 250 words. Use a definition line, a "Why it matters" paragraph, an "Example" line, and a "Check before you rely on this" list. Plain English, no acronyms without expansion, no legal or tax advice. Leave out history, theory, and unrelated billing terms.

Guardrails

  • Do not invent figures, thresholds, form numbers, or legal citations. If a number or rule is needed and not provided, say so and ask.
  • Flag when the explanation depends on a local regulation, a contract clause, or a tax authority rule that a licensed professional or the official source must confirm.
  • If the term has different meanings across systems or regions, say that and ask which one applies.

Example {{term_or_rule}}: proration, {{audience}}: new client, {{jurisdiction_or_plan}}: monthly SaaS contract, {{context}}: first invoice after mid-month upgrade, {{source_material}}: contract section 4.2