Automation and emails

Finance feeds the automation engine with events about payment plans and fees, and sends a fixed set of system emails: publication notices, fee reminders and external payer messages. All the emails are system email templates that staff can edit like any other.

Automation triggers on a payment plan template

Rules that react to payment plans are set up on the payment plan template, in its Automation tab. A rule there only fires for plans created from that template.

Trigger Fires when
payment plan is published A plan is published for the first time from the profile, by an application on submission, or by the Create payment plan action.
payment plan is fully paid The plan's status becomes Paid: nothing is outstanding on any fee.
payment plan fee is paid A fee becomes fully paid, by a completed transaction or by a discount that covers it.
payment plan first fee is paid The first fee of the plan to become fully paid. It fires together with payment plan fee is paid.

Two exit rules stop a running automation: payment plan is deleted and payment plan fee is deleted.

The actions available in these rules are Send email to profile, Send email to staff, Transition profile, Add tag to profile and Wait.

Note: Update status on the Payment plans list publishes plans without firing payment plan is published. See Payment plans.

Examples

  • Transition the profile to student::enrolled when the first fee is paid.
  • Email the admissions team when a plan is fully paid.
  • Tag profiles whose deposit has been paid, for a segment used in a campaign.

Creating plans with automation

The Create payment plan action creates a plan from a chosen Payment plan template for the profile and the class or course of the event that triggered it. When the event comes from an application, the plan is linked to that application. Answering yes to Would you like to publish the payment plan automatically? publishes the plan straight away, with the publication email and trigger.

The action is offered in lifecycle workflow groups and in class automation, when finance is switched on for the institution.

Two more automation pieces relate to finance:

  • The application trigger application is pending payment fires when an applicant reaches the payment step. See Finance across the platform.
  • The built-in Update course fees on payment plan action runs when a registration is registered, adding a fee for each newly registered course to plans that charge per study plan course, and removing unpaid fees for courses the student is unregistered from.

Payment plan published email

Payment plan published notification for candidates is sent to the profile the first time a plan is published, with a link to their Payments page. Institutions can switch it off; see Settings and permissions.

Fee reminders

When a template has Send payment notifications on, its plans send reminders before and after each fee's due date. A daily job sends them for six moments:

Email template Sent
Payment plan fee due in 14 days notification 14 days before the due date
Payment plan fee due in 7 days notification 7 days before
Payment plan fee due tomorrow notification The day before
Payment plan fee overdue notification The day after the due date
Payment plan fee 7 days overdue notification 7 days after
Payment plan fee 14 days overdue notification 14 days after

A reminder is only sent when the plan is published and not fully paid, and the fee is neither paid nor waived. It goes to the profile's notification email, or to the external payer when the fee has an external payer request and the payer has an email address. The email links to the applicant's Payments page, or to the external payer's payment page.

Note: The setting is copied to a plan when it is created. Switching it on in the template does not start reminders for existing plans.

External payer emails

Email template Sent to When
External payer request The external payer A request is approved, or renewed
External payment confirmation for candidate The student A fee allocated to an external payer is fully paid

See Payers.

Payment receipts

Full Fabric does not send its own receipt for a payment. Stripe is given the payer's email address for a receipt, which Stripe sends according to the Stripe account's own settings. Flywire payments send Email for candidates when a payment is received through flywire when Flywire guarantees the payment. See Payment gateways.

Merge fields

Finance emails can use these merge fields, besides the usual profile ones:

Group Fields
Payment plan Name, Link, Outstanding amount
Payment plan fee Description, Amount, Outstanding amount, Due date, Payer's first name
Other Programme or subject, Class or course, External payer's name

Letters

Generated letters can include payment plan tables: the plan chosen when generating the letter, or else every plan the profile has for the letter's class or course. The tables list fees with their due dates and totals, optionally with subtotals and discounts, plus the payers, the discounts and the instalment schedule.

Note: The payment plan letter tags are not listed in the letter merge field picker. Ask your Full Fabric contact for the tags to use.