Transactions

A transaction is one movement of money against a fee: a card payment through a gateway, a bank transfer staff record by hand, a refund, or a reversal. A fee's paid amount is the sum of its completed transactions, so transactions are what move a fee, and through it the plan, towards Paid.

Transactions belong to the profile that owes the fee, whoever actually paid it. Each one also records its payer.

What counts as paid

  • Only completed transactions count. A payment still waiting on its gateway, a failed payment and a refunded payment do not.
  • Only transactions in the fee's currency count towards its paid amount. A payment received in another currency is kept on record but leaves the fee outstanding until staff reconcile it.
  • Discounts reduce what is owed but are not transactions. See Discounts.

Every new, changed or deleted transaction recalculates the fee and the plan status at once, and can fire the fee paid automation triggers. See Automation and emails.

Transaction states

Each kind of transaction has its own states. The completed state is the one that counts as paid.

Kind States Completed when
Manual Succeeded Always
Stripe Created, Succeeded, Waiting for refund, Refunded, Failed Succeeded
PayPal Pending, Succeeded, Failed Succeeded
Flywire Initiated, Guaranteed, Cancelled Guaranteed
Adumo Created, Succeeded, Failed Succeeded

Some states mean money is on its way even though nothing counts as paid yet: an Initiated Flywire transfer waiting for the bank, and a Stripe refund Waiting for refund. While a fee has one of these, it shows as pending payment, and it cannot be divided, re-divided or deleted. See Payment gateways for how each gateway reports back.

Manual transactions

Staff record payments made outside a gateway, such as a bank transfer or a cheque, as manual transactions. To record a payment against a fee, open the fee's Transactions action on the plan's Fees tab and add a transaction. The Add a transaction dialog asks for:

Field Description
Description What the payment was.
Date When the money was received.
Amount and Currency What was received. Use the fee's currency for it to count towards the fee.
Reference The bank or remittance reference, for reconciliation.

A manual transaction is completed as soon as it is saved. Manual transactions have edit and delete icons in the list: editing opens Transaction details, where each field saves as it changes, and deleting asks "Are you sure you want to delete this transaction?". Both recalculate the fee.

Warning: A transaction added from the profile's All transactions tab is not linked to any fee, so it does not pay anything. Add payments from the fee's Transactions page.

Refunds

A successful Stripe payment made in the last 30 days can be refunded from the refund icon on its row in the profile's All transactions tab, by staff with the refund permission. The Refund transaction dialog asks for a Reason (Duplicate payment, Fraudulent payment or Requested by customer) and a Description. The whole payment is refunded; partial refunds are not available.

The refund is sent to Stripe at once, and the transaction moves to Waiting for refund until Stripe confirms it, then to Refunded. From the moment the refund is requested the payment no longer counts towards a plan fee, so the fee and plan show it as outstanding again.

The transaction records who requested the refund, when, and the reason.

Note: Refunds through Full Fabric are only available for Stripe. A PayPal, Flywire or Adumo payment refunded in the gateway's own dashboard still counts as paid in Full Fabric.

Reversals

A reversal corrects a manual transaction without deleting it: a new manual transaction for the same amount, negative, linked to the one it reverses. Both stay on record, and the fee's paid amount nets them out. Reversals are recorded through the Payments API.

  • Only manual transactions can be reversed. Gateway payments are refunded instead.
  • A transaction can be reversed once. A second attempt is refused.
  • A reversal cannot itself be reversed. Record a new manual transaction if the money arrives after all.
  • Without a reason, the reversal is described as "Reversal of transaction" followed by the original's ID.

Where transactions are listed

The profile's All transactions tab, under Financials, lists that profile's transactions with their Description, Payer, Payment plan, Fee, Currency, Amount, Date, Reference, State and Gateway (Manual, PayPal, Stripe, Flywire or Adumo). A refunded payment shows its refund reason under the state. A fee's Transactions page shows the same list for one fee.

Finance > Transactions lists transactions across all profiles, newest first, for staff with transactions access. It can be searched and filtered by State (Pending, Succeeded, Failed, Created, Initiated, Cancelled, Guaranteed), and shows the profile Name, Payer, Description, Date, Amount, State, Gateway and Reference, with profile fields available as extra columns. Export downloads the list straight away as an Excel file.

Transactions and profile changes

  • Merging profiles moves the merged profile's transactions to the surviving profile, together with its plans, payers and discounts.
  • Deleting or forgetting a profile deletes its transactions.

See Finance across the platform.