Solutions · Employee benefits

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

Medical scheme applications, beneficiary nominations, group life and funeral cover. Nine pages, a few hundred fields, four dependants — and every one of them tied to a person, not a box.

Start free — 5 envelopes a monthUpload a benefit form, no account
Medical scheme applications
Employer group, nine pages, every dependant named.
Beneficiary nominations
Retirement and group life, with witnesses.
Funeral and group cover
Extended family, conditional throughout.
Annual re-enrolment
Last year’s answers pre-filled; the member confirms.
Subjects

Fields bind to people, not to boxes.

On a benefit form, “Dependant 1” is a run of blank boxes. Nothing connects the name on page 2 to the ID number on page 5. Vumasign binds each field to a person — member, spouse, dependant_1. Mark a subject conditional and an absent spouse’s fields disappear rather than sit blank.

Other platforms model every person as a recipient, which cannot express a five-year-old who signs nothing.

Subjects on one application
284 fields
  • M
    member
    nameid_numberp.2 addressp.5 tax_nop.9 signature+36
  • S
    spouse ?
    nameid_numberp.6 signature+20
  • 1
    dependant_1
    namedobrelationship+15
  • —
    dependant_3
    absent — 18 fields hidden

Built and measured against the documents your members actually fill in.

Not a demo NDA. The field-discovery engine was developed against South African benefit paperwork as it is published — including the sixty-three fields one scheme left namedundefined_3 and the like.

DocumentPagesFieldsSubjects
Medical scheme application, employer group9284member · spouse · dependant 1–4 · employer
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

Field counts are as published in the source PDFs. Scheme and fund names withheld on this page.

One envelope, every party, in the right order.

Signers, subjects, approvers.
The member signs. The dependants are subjects — named on the form, they sign nothing. HR approves after the member. Each role is explicit, so nobody gets an email they cannot act on.
Conditional sections.
No spouse? The spouse’s twenty-three fields disappear from the signing view instead of sitting blank for a broker to query later. Three dependants means three, not a fourth block of empty boxes.
Pre-fill from what you already know.
Because fields are named for people, a member’s name, ID number and address flow from your system onto pages 1, 4 and 7 through the API or a template. The member checks and signs; they do not retype.
Data residency

Benefit forms carry the most sensitive data a company holds.

Health information is special personal information under POPIA s26. A medical scheme application sent through an offshore platform is that information leaving the country, every time. Vumasign processes it in Johannesburg, under an operator agreement, for a South African responsible party.

How we talk about POPIA
Member
Johannesburg
Your scheme
ID numbers, dates of birth, medical history and dependants’ details never leave South Africa. No POPIA s72 transfer to justify — on any plan.

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

R7 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.

Full pricing

Sign a real document. Then check the seal yourself.

No account. Sign, download the sealed PDF, open it in Adobe Reader and watch the signature validate. That is what a recipient's lawyer will do in two years.

Try it nowStart free — 5 envelopes a month
Free · 5 envelopes a month · no cardStart free