Release 27-07-2026

 This release of OnboardMe introduces a range of new features and bug fixes. The changes are outlined below.

Send proposal to all signatories

Practices can now invite every unsigned signatory at once, so co-signers can review and accept in parallel instead of waiting for a strict signing order.

Where to turn it on

Settings → Business details → Engagement settings → “Send proposal to all signatories”

• Yes invites all eligible unsigned signatories together (subject to the exceptions below)

• No (signing order) keeps the existing behaviour: invite the next unsigned signatory only after the previous one accepts

When it sends to everyone at once

With the setting enabled, a normal multi-signatory proposal (no ethical letter, single package / no package choice) works like this:

1. User sends the proposal.

2. All unsigned signatories receive the invite (email/SMS as configured).

3. Signatories can open their links and review in parallel.

4. The proposal stays in awaiting additional acceptances until the last person accepts.

5. Only when everyone has accepted:

   • payment is processed (if applicable)

   • the final signed PDF / signed-proposal email is issued

   • acceptance integrations and job deploys run as usual

Automated reminders follow the same rules as invites (they remind whoever is currently eligible to be invited).

When it still goes primary-first

Even with “send to all” enabled, some proposals must wait for the primary signatory before everyone else is invited:

Why the gate exists: package choice and ethical-letter client details need to be settled by the primary before other signatories review a settled proposal.

Workflow with ethical letters

1. Users send the proposal.

2. Only the primary signatory is invited to the proposal.

3. The ethical letter still follows its own send option:

   • Immediately when sending proposal: sent on first send (unchanged)

   • After proposal acceptance: sent only when all signatories have accepted

4. Primary completes review/acceptance (including any ethical-letter client details required on their path).

5. On primary accept, all remaining unsigned signatories are invited together.

6. They review/sign in parallel until the last acceptance completes the proposal.

Workflow with packages

1. Users send a multi-package proposal.

2. Only the primary signatory is invited.

3. Primary selects a package during review (required before they can continue).

4. Primary accepts.

5. Remaining signatories are invited together and review the proposal with the chosen package already set.

6. Final payment, signed copy, and post-acceptance automation wait until everyone has signed.

What users will notice in the app

• Copy client link may ask which signatory’s link to copy when send-to-all is on and there is more than one signer.

• Signatories see messaging that either:

  • others have also been invited (true parallel send), or

  • remaining signatories will be invited after they accept (primary-first / ethical / packages).

What this does not change

• It does not mean the proposal is fully complete after the first signature. All named signatories still need to accept.

• It does not process payment or issue the final signed proposal until all signatories have accepted.

• It does not bypass package selection or ethical-letter requirements on primary-gated proposals.

eForm Attachments

Practices can upload reusable files into an eForm attachment library, then attach those files to sections or questions so clients can download them while filling an eForm.

Where to manage the library

Templates → eForm Templates → Attachments

On that tab you can:

1. Click New attachment (or open an existing row) to create or edit an attachment.

2. Give it an Attachment name (what staff see in pickers).

3. Optionally add Document information (internal notes for your team on when/how to use it).

4. Upload a file (most common file types, max 10 MB).

5. Preview (PDFs only), download, search, and mark attachments inactive when they should no longer appear in pickers.

These files are practice-wide and reusable across eForm templates and form instances. You do not re-upload the same file for every form.

Supported files

• Upload any common file type (Word, Excel, images, ZIP, PDF, and similar), not PDF only.

• In-app preview is available for PDFs only. Other types can still be downloaded.

• Executable-like types (for example .exe, .bat, .msi, .dll, .ps1) are blocked for security.

• Max size: 10 MB.

How to reference attachments on an eForm

Open an eForm template (or form builder) and attach library files in either place:

1. On a section
Use the section Share documents with client control (document icon).
Chosen files appear at the top of that section when the client fills the form.

2. On a question
Open the question settings and use Share documents with client.
Chosen files appear with that question so the client can download them while answering.

In both places the picker lets you:

• Select one or more files from the practice library

• Reorder them

• Remove ones you no longer want shared

If the library is empty, add files under eForm Templates → Attachments first.

What clients see when the form is sent

When a client opens the eForm:

• Section-level documents show at the top of the relevant section

• Question-level documents show with that question

• Clients download via secure links (they only get files that were attached on that form)

Staff preview/response views use the same shared-document list so you can confirm what the client will see.

Typical workflow

1. Upload files once under eForm Templates → Attachments.

2. Build or edit the eForm template.

3. Attach the right library files to the section and/or questions that need them.

4. Save the template.

5. Send the eForm to the client as usual.

6. The client reviews/downloads those files while completing the form.

Notes

• Inactive library items are hidden from pickers; existing forms that already referenced them are unchanged until you edit those forms.

• This is separate from “allow document upload” on a question (that lets the client upload files as answers). Shared attachments are documents you provide for the client to download.

• This is also separate from Proposal Attachments under proposal templates.

ID Verification Sending

If a client has an ID Verification already in flight in the ID Verification area and a process or user tries to send another ID Verification for that user, the system will not create a new ID Verification but just update the existing ID Verification currently in progress.

CDD Case Reopening

Users can now reopen completed Customer Due Diligence cases to make additional changes.

When a CDD case is completed, a new Reopen button will appear which can be used to update the status to Draft.

Reopening a CDD case will add in a history row noting the user who unlocked it and when.

Pinch Payments - Direct Debit Process Flow

After numerous discussions with Pinch and customers, we've disabled the ability process payments using Direct Debit in the Bills & Payments area in OnboardMe.

Due to the nature of Direct Debit and the length of which it takes to process, duplicate payments are possible.

A new Alert will prompt users to process the Direct Debit directly in the Pinch Merchant Portal

Associated Entities + ID Verifications

When sending an ID Verification only to a new client, the system will no longer create a client record but an Associated Entity (Associated Entities are not integrated into Practice Management Systems and are only records needed for ID Verification and CDD purposes).

To enable this, the New Client Option has been removed from the New ID Verification area, users can continue to send to Existing Clients or Associated Entities now.