Invoicing And Payments

Each sub-account connects its own Stripe through Stripe Connect, so payments, customers, and payouts stay fully isolated per client. The charge routes directly to the account that owns it, and refunds route back through the same account. There is no platform markup skimmed off the top, because the transaction is yours, not ours. The connect panel names whatever Stripe is still waiting for rather than just reading "not ready", so a stalled onboarding tells you which document to chase.

Billing passthrough is per client. Leave it off and a client's messaging and call usage bills through to them; switch it on and your agency absorbs it instead, so you can put a client on a flat all-in retainer without them ever seeing a usage line. It is a setting per sub-account, not an all-or-nothing platform mode.

Payments recorded by hand, cash, cheque, or bank transfer, land in the payments ledger like any other, so revenue reporting counts them. A partial refund takes off what was refunded and leaves the rest of the invoice intact. A lost chargeback updates the invoice instead of leaving it reading as paid. An invoice paid through a Stripe-hosted page reconciles back automatically, and a payment against a voided invoice does not quietly un-void it.

Build invoices from your product catalog or custom amounts, with line items, percentage or fixed discounts, per-line tax, and tip and gratuity support. While an invoice is in draft you see a live preview of exactly what the client will receive, so nothing goes out looking wrong.

Send an estimate as a public link. The client accepts or declines without logging in, and an accepted estimate converts straight to an invoice carrying its line items across. Statuses track the whole path: Draft, Sent, Viewed, Accepted, Declined, Invoiced, Expired. What the customer does on that page fires your automations, so an acceptance can book the follow-up, alert the owner, and draft the invoice on its own. Deposits work end to end, so you can take money up front on the same estimate rather than chasing it separately.

A sub-account's messaging and calling run off a prepaid wallet. Set a floor and a top-up amount and the wallet recharges from the saved card on its own when it runs low, so a campaign does not stop mid-send because a client forgot to add funds. When a top-up fails, the reason is recorded rather than swallowed, and the send stops instead of quietly running on your money. Pair it with billing passthrough and a client's usage funds itself.

An estimate can be signed in person, on your device, with the customer standing there, and paid on the spot. The deal that closes while you are still in the room is the one that does not go quiet for three weeks waiting on an emailed link nobody opens.

Sync products from Stripe into the CRM catalog rather than typing them twice and watching the two drift apart. The prices you sell from are the prices Stripe charges, because they are the same records.

Put clients on automatic invoicing on a weekly, biweekly, monthly, quarterly, or yearly schedule, and pause or resume any recurring invoice without rebuilding it.

Invoices detect when they go overdue and run a multi-level reminder sequence, a friendly nudge, a firmer follow-up, then a final notice, over email or SMS, so you stop chasing payment by hand.

Keep a reusable library of products with SKU, description, image, and price. Sell bundles at a bundle price, set quantity-based pricing tiers, and define dependencies (a product that requires, excludes, or recommends another) for cross-selling. Import products directly from your Stripe account so the catalog and Stripe stay in sync.

Design invoice and estimate layouts in a drag-and-drop block editor with global styling, organized in folders. Configure your own invoice number prefix and starting number, default payment terms (Net 15, Net 30, Due on Receipt, or custom), discount codes (fixed or percentage, with usage limits and valid dates), and a public payment link plus PDF download on every invoice.