Subscription process: deferring a payment

Overview

By default a transaction's payment must be received and verified before its documents can be signed (A8.11). Deferring the payment reverses that for one transaction: the documents are signed, and the money follows.

The setting lives on the transaction, not on the payment and not on the process. So it is decided per transaction, in the first stage, alongside everything else about that transaction.

What you'll learn

• Where the toggle is, and what it says

• How to set it across a bulk import instead

• The two movement types it does not apply to

• How to find the deferred set again afterwards

Before you start

The process exists and its transactions are in the table — added manually (A8.3) or imported (A8.4).

Steps

1. From the project Dashboard, open the process under Active Operations. On the Subscription Dashboard, open Transactions Setup.

2. Click the transaction's row. Its detail panel opens on the right.

3. Find Deferred Payment in that panel.

4. Turn on Post-signature payment.

The panel states the consequence outright, and it is worth reading rather than inferring:

"Enable this option when the payment should occur after the documents are signed. If disabled, the payment will be required before any signature."

Off means payment gates signature. On means signature proceeds and the payment is owed afterwards.

Setting it across a bulk import

The transaction import file carries a column for it: Payment Deferred Post-Signature? Enter Yes to defer that row.

Anything else leaves the default in place — No, or an empty cell, defers nothing. That is the safe direction: a file with the column left blank throughout defers nothing at all rather than everything.

On a large process this is the easier route. Deciding row by row in a spreadsheet, while you have the commercial terms in front of you, beats opening several dozen detail panels afterwards.

Where it does not apply

Two movement types involve no payment, so the panel says so rather than offering the toggle:

• Free shares — "No payment required for the issuance of free shares."

• Contributions — "No payment required for contribution."

Nothing is gating those signatures, so there is nothing to defer.

Finding the deferred set again

Once set, Deferred appears as a column and as a Deferred payment only filter — on the transactions table, the payments table, the templates table, and the document creation dialog.

Use it deliberately. A deferred payment is money owed against a document that has already been signed, which is the one category in a subscription process you cannot afford to lose track of. Reviewing that filtered list before you close is cheaper than reconstructing it later (A8.13).

Common problems

There is no toggle in the panel. Check the movement type. Free shares and contributions have no payment to defer.

A signature is blocked and you expected it not to be. The payment is neither verified nor deferred. Do one or the other.

The import deferred nothing. The column has to read Yes. A blank cell is a valid "no", not a missing value, so it fails silently by design.

You deferred the wrong transaction. Turn the toggle off again while the process is still in preparation, and check the Deferred payment only filter to confirm what is actually set.

Related

• A8.11 — Subscription process: choosing your payment and signature order · the decision this carries out

• A8.13 — Subscription process: payments · requesting and verifying the money afterwards

• A8.4 — Adding subscribers in bulk · the import column

• A8.5 — Subscription process: reviewing before you commit · where the Deferred filter first appears