Finance across the platform

Finance is not a separate system: payment plans are created by applications and automation, fees can hold up a submission, and finance records follow the profile through merges, withdrawals and deletion. This page covers where finance meets the rest of Full Fabric.

Applications and registrations

An application or registration template collects money in one of two ways, chosen on its Payment tab once Enable payment is on:

Fee requirement What the applicant pays
Application fee One fee set on the template, optionally different per programme, paid through the template's gateway.
Required fee(s) from Payment Plan Fees from a payment plan the applicant chooses while applying. Registrations with payment plans switched on always use this.

The application fee itself is covered in the applications documentation; staff can mark it paid, waived or not paid on the application.

The Payment plan tab

With payment plans switched on, the plan the applicant selects is created automatically when the application or registration is submitted, if it does not exist yet. The template's Payment plan tab has these settings:

Setting Effect
Instructions to the applicant Text shown with the plan choice.
Automatically publish the payment plan on application submission? Publishes the plan as soon as the application is submitted, with the publication email and automation trigger.
Applicant discount codes Lets applicants enter discount codes. Staff-assigned and automatic discounts are always applied, regardless of this setting.

The tab needs the form to have a single primary programme choice field; otherwise it shows "Currently unavailable".

Choosing a plan

The plans offered depend on the class or course the applicant chooses as their primary choice:

  • If staff have already created plans for the profile in that product, only those are offered.
  • Otherwise the payment plan templates for that product are offered. Templates where applicants define their own fees are hidden when the product has no price.
  • When there is exactly one option, it is chosen automatically. Changing the primary choice clears the choice.

Until a plan is chosen, the application cannot go further: "A payment plan must be selected". Before the plan exists, the applicant sees a preview of what it will contain.

From payment to submission

  1. Start payment. When everything else in the form is valid, the applicant moves to the payment step. The plan is created from the chosen template, with any discount codes they entered, and the application is pending payment automation trigger fires.
  2. Pay. The applicant pays from the application's payment page. On a plan with staff-defined fees, every fee marked To be paid before enrolment or registration must be paid: "Payment plan fees must be paid before applying". On a plan where the applicant defines their own fees, the fees and discounts must add up to the product price and every external payer request must still be valid: "The payment plan must be correctly set up".
  3. Submit. On submission, the fees the applicant pays themselves are divided into the instalments they chose, and the plan is published if the template says so.

If the application goes back from the payment step to started, the choice is cleared and the plan created for it is deleted, unless money is already against one of its fees. While the application is waiting for payment, its plan cannot be deleted.

Offers

Offers and payment plans are not linked directly: accepting an offer does not create a plan. Two features bring them together:

  • A lifecycle workflow can Create and make offer and Create payment plan as separate actions. See Automation and emails.
  • A letter can include both the offer and the profile's payment plans.

Profiles

  • Financials tab. A profile's plans and transactions live on its Financials tab, for staff with access to it.
  • Withdrawing a profile from a class can also Unpublish payment plans for that class, hiding them from the student. This works for single and bulk withdrawals.
  • Removing a profile from a class or course is refused while they have a payment plan for it.
  • Merging profiles moves the merged profile's plans, transactions, payers and discounts to the surviving profile, and re-points who created, paid, waived or refunded them.
  • Deleting or forgetting a profile deletes its transactions.

Courses and registration

On plans that charge per study plan course, registering a student on a course adds a fee for it, and unregistering removes that course's fee if nothing has been paid on it. Deleting a course updates the fees on existing plans in the same way.

When a study plan course fee is fully paid, a conditional registration on that course becomes registered.

Exports

Export Columns
Payment plans Name, Email, Payment plan name, Product, Publish status, Fee status, Overdue outstanding, Paid, Outstanding, Subtotal, Total, Discount total, plus chosen profile and journey fields
Transactions (spreadsheet) Name, Payer, Description, Transaction date, Amount, State, Gateway, Reference, plus chosen profile fields

Profile and journey exports can include a Payment plans column, listing each plan as product, plan name and status (Paid, the number of payments overdue, or Not due).

Public API

The Payments API reads payment plans, plan templates and transactions, creates and deletes plans, records manual transactions against a fee and reverses them. The Applications API marks an application fee paid, waived or unpaid. See the API reference.