For employee benefits

The form never knows who Dependant 1 is. We do.

The longest forms in the country, still going out to print. Send the application instead. Every box belongs to a person, so each one is filled in by the right one.

No card to start. Stored in South Africa.

Medical scheme applications

Employer group, nine pages, every dependant named.

Beneficiary nominations

Retirement and group life, with witnesses.

Funeral and group cover

Extended family, sections only where they apply.

Annual re-enrolment

Last year’s answers filled in. The member confirms.

Every box has an owner

Fields belong to people, not to boxes.

On paper, “Dependant 1” is a run of blank boxes, and nothing ties the name on page 2 to the ID number on page 5. Vumasign gives each field to a person: member, spouse, dependant. A spouse who doesn’t exist doesn’t get asked about.

The Subjects list in the Vumasign editor for an employer group medical scheme application: Spouse with 22 fields, and Dependants 1, 2 and 3 with 28 fields each. Every one is set to Ask the signer and marked only some envelopes.
Each dependant is a subject with their own boxes, asked about only when they exist. Screenshot of the product, October 2026.

One envelope. Everyone in the right order.

Signers, subjects, approvers

The member signs. Dependants are named on the form and sign nothing. HR approves after the member.

Sections that disappear

No spouse? The spouse’s twenty-two boxes are not shown, rather than sitting blank for a broker to query.

Filled in from what you know

Name, ID number and address flow from your system onto every page that asks. The member checks and signs.

Measured on the forms your members fill in.

Not a demo NDA. Field finding was built on South African benefit paperwork as published, including the sixty-three fields one scheme left named undefined_3 and the like.

DocumentPagesFieldsWho it's about
Medical scheme application, employer group9278member · spouse · dependants: 7 people, as setup found them
Retirement fund nomination of beneficiary6127member · beneficiary 1–6 · witness
Funeral cover application4—member · spouse · children · extended family
Group life insurance application4—member · beneficiaries · employer
Group life beneficiary nomination2—member · beneficiary 1–4

The employer group count is the boxes setup placed on the real form; the others are as published in the source PDFs. Scheme and fund names withheld on this page.

Data residency

Health data, stored in South Africa.

Health information is special personal information under POPIA s26. Send it through an offshore platform and it leaves the country every time. Vumasign stores and processes it in Johannesburg, under an operator agreement.

How we talk about POPIA
Member
Johannesburg
Your scheme
ID numbers, dates of birth, medical history and dependants’ details. Stored in Johannesburg, on every plan.Email is delivered by an email provider: invitations carry a link, and the executed copy travels with the completion email as an attachment.

Priced by the envelope. A nine-page application with four dependants counts once.

R7 an envelope on Team, R5 on Business, published. Building signing into your own product? The API plan is R500 a month with 50 included, then R10 each.

See pricing

Who even has a printer anymore?

Upload it instead. See every field found and named before you decide.

Signed, sealed, sorted. Lekker.

Free · 5 envelopes a month · no cardStart free