FinDock Standalone

When FinDock is use as a source, we call this setup FinDock Standalone. It means FinDock objects for one-time and recurring payments, Installment and Recurring Payment, respectively, are the primary source of payment data in an org.

FinDock Contact Layout

When using FinDock standalone, you can use the Contact FinDock layout on the contact record detail page to have the FinDock objects included on the layout. For more information on how to assign page layouts, see Assign Page Layouts from a Customize Page Layout or Record Type Page in the Salesforce Help.

One-time payments

Single invoices, other amounts receivable, as well as amounts payable are captured by the Installment object. The default status for newly created Installment records is Outstanding.

Recurring payments

The Recurring Payment object is used to register an amount, payment method, frequency and other information for collection recurring payments. A recurring payment can be created for either a contact or an account.

Key dates on recurring payments

The following key dates on a recurring payment can be modified by

• Manually creating the records and adjust dates before saving
• Explicitly setting the field values as part of the payment intent call to the Payment API
• Creating a custom process to set the field values using Salesforce tooling such as Flow

Start Date

This is the date the recurring payment was created. When FinDock is the source, FinDock uses today's date.

Collection Day of Month

When FinDock is the source, FinDock uses the 1st of the month for the Collection Day of Month.

End Date

This is an optional data point for recurring payments. If there is no end date, the recurring collection continues until the payer ends the agreement.

Collection dates

When a new Recurring Payment record is saved, the Next Collection Date field is automatically populated with a value that determines when the next installment is generated. This value is the next Collection Day of Month based on the Last Collection Date or the Start Date if the Last Collection Date is empty.

Closing recurring payments

If a payer wants to close a recurring payment, you will typically have business-specific logic to handle this scenario. The business logic needs to ensure the related mandate is inactive and no open installments are eligible for collection.

You can create a custom Flow, for example, to stop recurring payment collection. The closing process is:

1. Deactivate the related mandate by changing the Active checkbox from marked to unmarked.
2. Set the status of existing open installments to a closed state, such as Cancelled.
3. Deactivate the recurring payment by changing the Active checkbox from marked ot unmarked.
4. If relevant for the business case logic, change the Status value to e.g. On Hold.

Mandate generation

Mandate records can be automatically created by FinDock when required. FinDock determines when new mandate is required using the following conditions:

• The payment method is changed
• The Payment Processor is changed
• The Target is changed
• The payment profile is changed
• The mandate field is emptied
• The frequency value is changed

Collecting payments with FinDock Standalone

When using FinDock Standalone, you can collect and disburse payments using the standard payment schedule process.

When a payment schedule is processed successfully, depending on the payment processor, either the finished status is set or the installments are closed as completed.