Reference · built on requestOperator by FibricFinance & billing

Dunning Cadence

Overdue invoices read beside open support threads, with the next reminder, escalation, or pause proposed for each account.

Request accessPricing ↗

About

A reminder sent to a customer who is disputing the invoice with your support team makes two problems out of one. This operator reads open invoices past their due date in your ledger or billing system, the reminders already sent and whether they were delivered, and the support conversations open for the same customer. Then it picks the next step from the cadence you wrote.

It proposes one step per account, not per invoice: a reminder with the invoices listed, an escalation to the account owner, or a pause while a dispute is open. You approve the step, the message goes out once, and the receipt keeps the text, the recipient, and the delivery event.

This is a reference listing. It documents what Fibric would read from Dunning Cadence and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Xero ACCREC invoices with Status AUTHORISED, a DueDate in the past, and AmountDue above zero, and the SentToContact flag
  • Open invoices with a balance in QuickBooks Online, NetSuite, or Business Central, and the payment terms on the customer
  • Chargebee invoices in payment_due or not_paid with their dunning_status, and Recurly invoices inside a dunning cycle
  • Payments and credit notes applied since the last reminder, so a paid invoice drops out before the next step
  • Open Zendesk or Kustomer conversations for the same customer, and the tags you mark as billing disputes
  • Delivery, bounce, and open events for earlier reminders from Twilio SendGrid or Amazon SES
  • Public holidays for the customer's country, so a step is not proposed on a day nobody is at work

Proposed actions

  • Target capability: propose the next reminder in the cadence, addressed to the billing contact, with the overdue invoices and amounts listed
  • Target capability: propose an escalation to the account owner in Slack or Microsoft Teams with the balance and the history of reminders
  • Target capability: propose a pause on the account while a support conversation tagged as a billing dispute stays open
  • Target capability: propose stopping dunning on a Chargebee invoice when the customer has a promise to pay on record
  • Target capability: propose a note on the customer record with the step taken and the next date

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Pause the reminder while support has the case

    A Zendesk ticket tagged billing-dispute on the same organization pauses the Xero cadence. When the ticket is solved, the next step is proposed again.

    With Zendesk, Xero

  • Escalate to the owner, not the inbox

    After the last reminder step, the account and its overdue QuickBooks Online invoices go to the owner's Slack channel with an approve button for the escalation.

    With QuickBooks Online, Slack

  • Stop Chargebee retries for a promised payment

    When a Kustomer conversation records a promise to pay, it proposes stopping dunning on the Chargebee invoice until the promised date.

    With Chargebee, Kustomer

  • Skip the public holiday

    Reminders due on a public holiday in the customer's country are proposed for the next working day instead, and sent through Twilio SendGrid once approved.

    With Holidays & FX Reference, Twilio SendGrid

Requirements

  • A ledger or billing connector with invoice due dates and balances: Xero, QuickBooks Online, NetSuite, Chargebee, or Recurly
  • A help desk connector for open conversations: Zendesk, Kustomer, Gorgias, or Freshdesk
  • An email or chat connector for the reminder and the escalation: Twilio SendGrid, Amazon SES, Slack, or Microsoft Teams
  • A written cadence: the steps, the days between them, and the tag or condition that pauses it
  • A billing contact on each customer record. Without one, the account is listed and no reminder is proposed
Authentication
It stores no customer credentials. Ledger, billing, help desk, and email reads and sends use the connectors you attach with the scopes you grant.

Limits

  • It sends reminders; it does not take payment or card details. Collection happens in your billing system.
  • Chargebee and Recurly run their own retry schedules. This operator proposes stopping or resuming those; it does not replace them.
  • A bounce is read from the email provider's event. A reminder that was delivered but unread counts as delivered.
  • One cadence per customer segment. It chooses the step; it does not write the steps.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dunning Cadence ↗

Questions and answers

What does approving a step involve?
One step per account: the reminder text with invoices listed, the escalation message, or the pause with its reason. You can edit the text, change the recipient, or skip the step. No message leaves until you approve.
What is kept for each reminder or pause?
A receipt per step: message text, recipient, who approved, when, and the delivery or bounce event from the email provider. Pauses record the conversation that caused them and when they lifted.
Will it send a reminder on its own?
No. Every reminder and escalation waits for approval, then goes once. If a payment lands between approval and send, it withdraws the step and shows you why.
Ask about Dunning Cadence

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy