MCP guides
How Qualy reminds
For assistants
An assistant connected to the Qualy MCP server reads this guide as the resource qualy://guides/how-qualy-reminds. Generated from the Qualy MCP server’s guide registry.
Qualy suppresses reminders that are no longer relevant: a payment reminder will not be sent if the payment has been paid already. These are the rules it applies, read from the code that applies them.
Which payments get reminders
Reminders only go out for draft, due, partially paid or overdue payments.
Checked again just before sending
Qualy decides when a reminder goes out, not when it was scheduled. Just before it sends a Payment reminder, Late payment fee warning or Overdue payment reminder, it looks at the payment as it is at that moment, and suppresses the reminder when:
- it is no longer a draft, due, partially paid or overdue payment, for example it has been paid already (
due-to-payment-status). - it is part of an early payoff, so it can only be paid through the early payoff (
early-payoff-frozen). - it is collected by direct debit (
bank-debit-authorization). - its supplier is set to Suppress payment reminders (
partnership-suppress-payment-reminders).
These are the reasons that come from the payment itself. A suppressed reminder stays in the queue with status ignored and the reason in ignoredReason, which notification_queue_list shows.
A reminder someone asks for
A reminder sent on request, from the dashboard's Remind customer or with payment_intent_remind, goes out about 3 minutes after it is asked for, or at the send time given to payment_intent_remind, and the same check runs then: a payment paid in the meantime gets no reminder.
Before contacting someone yourself
notification_list shows what Qualy already sent, and notification_queue_list what it is about to send. contact_outreach_check puts both together for one contact, says whether Qualy itself would contact them about each payment now and why not, and gives the pay link to put in any message you send yourself.