Keeping a Paused Fractional Engagement and a Clawback Fee on Separate Rails

Say a boutique advisory firm places a fractional CFO with a client at a flat monthly rate, and six months later the same client asks the firm to run an executive search for a VP of Sales. The fractional engagement is genuinely recurring: same fee, same billing date, until either side ends it. The search placement is a one-time fee, paid on placement, with a clawback that refunds a portion if the candidate leaves within, say, ninety days. Billing both through the same recurring subscription object, because it's the same client and it feels simpler, is the mistake that causes problems later.

When the client pauses the fractional engagement for the summer, both Stripe Billing and Chargebee support pausing a subscription rather than canceling it, which preserves the original start date and terms for when it resumes. Chargebee's pause feature is a straightforward toggle an account manager can use directly. In Stripe Billing, pausing typically means updating the subscription's billing cycle anchor or using its native pause collection feature, which works but is a slightly more technical operation. Either way, avoid the shortcut of just skipping an invoice manually for the paused months without formally pausing the subscription object, since that leaves the platform's own records out of sync with what actually happened on the account.

The search placement fee should be a standalone one-time invoice, generated when the candidate accepts the offer, not folded into the next recurring invoice cycle just because the dates happen to line up. This matters most when the clawback clause activates: if the candidate leaves within the guarantee period and a partial refund is owed, that refund needs to apply cleanly against a specific, identifiable charge. A placement fee buried inside a blended monthly invoice makes issuing that refund, and explaining it in your own books, far messier than it needs to be.

Neither platform has a native clawback or guarantee-period feature, since both are built for subscription billing, not conditional refund logic tied to an external event like a candidate's tenure. Track the guarantee period and its conditions in your own client relationship system, and when a clawback triggers, issue a refund or a credit against the original one-time placement invoice directly in whichever platform processed it. Chargebee's credit note functionality handles a partial refund cleanly; Stripe Billing's refund API does the same thing with slightly more manual entry of the specific amount and reason.

Handle a placement clawback in this order:

1. Bill the placement fee as a standalone one-time invoice when the candidate accepts the offer, not inside the next recurring cycle.
2. Track the guarantee period and its conditions in your own client relationship system, since neither platform has a native clawback feature.
3. When the candidate leaves inside the guarantee period, issue a refund or credit against the original placement invoice.
4. Leave the fractional subscription untouched so its billing history and recurring revenue stay clean.

A firm that blends recurring fractional revenue with one-time placement fees on its own books can't answer a basic question a lender or a potential acquirer will ask: how much of this firm's revenue is contracted and predictable versus dependent on landing new search mandates each quarter. Keeping the two revenue types as distinct billing objects from day one, even when the extra setup takes a bit longer for that first blended client, is what makes that question answerable later without a manual reconstruction of every invoice the firm has ever sent.

A pause that only exists as a toggle in the billing platform, with nothing written down about the resume date or whether the rate stays the same, tends to turn into a dispute later if the client's circumstances changed while the engagement was paused. Send a short written confirmation whenever a pause is set up: the last billed date, the planned resume date if there is one, and whether the rate on resumption is the original rate or subject to renegotiation. That document, not the subscription object itself, is what protects both sides if the client comes back after a longer gap than either party expected and questions what was agreed. Store that confirmation alongside the client file, not just in an inbox, so whoever handles billing months later has the same context the original conversation did.