AddThisFeature
Sign in

Billing Contact Management

Send invoices to the people who pay, without giving them account access.

moderate Monetization

What it adds

A list of billing recipients per account who receive invoices and payment notices but hold no login or permissions.

What your agent is told to do

5
  1. 1

    Model a billing contact as an email address on the account, not as a user. Adding one must never create a login, a seat, or any read access to the product.

  2. 2

    Allow several recipients and let each be added or removed by an account admin, with a record of who changed the list.

  3. 3

    Send invoices, receipts and payment-failure notices to every billing contact. Keep owner-critical notices — cancellation, ownership change, security events — going to the account owner regardless of this list.

  4. 4

    Verify a new address before relying on it as the only recipient. Token mechanics are owned by Email Verification; reuse that flow rather than writing a second one.

  5. 5

    Do NOT let this list be emptied. An account with no billing recipient silently stops receiving invoices, and the first anyone hears of it is a failed payment.

Edge cases it handles

6
  • A billing contact who is also a member must not have their product notification preferences changed by being added here.
  • Marketing and product email opt-outs must not suppress invoices. Those preferences are owned by the Email Preference Center; transactional billing mail sits outside them.
  • A bouncing billing address must be surfaced to an admin rather than retried forever. Bounce detection itself is owned by Notification Delivery Failures; consume its signal.
  • Removing a contact stops future delivery only. Invoices already sent stay sent, and past invoices remain visible to admins.
  • The same address may be a billing contact on several accounts. Verification and removal must be scoped per account, not globally.
  • A departing employee's address often lingers as the only billing contact. Prompt for a replacement when the matching member is removed from the account.

Definition of done

8
  • Adding a billing contact grants no login, seat, or data access.
  • An account supports multiple billing contacts and records who added or removed each one.
  • Invoices and payment notices reach every verified billing contact.
  • Owner-critical notices still reach the account owner independently of this list.
  • Marketing opt-out does not suppress billing mail.
  • The system prevents an account from being left with no billing recipient, and flags bouncing addresses to an admin.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.