Answers for everyday policy administration.

Register an organisation, select an available plan and complete the administration setup steps. Confirm any member-data migration and external provider configuration before inviting staff to use live workflows.

The platform is designed for funeral businesses, brokers and life administrators, from owner-managed operations to teams with branches, administrators and agents. Feature access depends on account role and plan settings.

Member and policy imports depend on the source format and the migration options enabled for your account. Confirm a file review and migration plan with the Polisystem team before importing production data.

Decide who will manage products, member records, payments, claims and user access. Add staff with individual accounts and the lowest role access they need.

The platform supports configurable policy products and policy administration workflows. Product types and setup available to your organisation depend on the features enabled for your account.

Member, dependant and beneficiary records are supported in the member and policy administration workflow. Review the policy record and product configuration before relying on a relationship for a claim decision.

Use the member administration screens to review and update the record. Changes are subject to the permissions of your assigned role and should follow your organisation’s record-handling procedures.

No. Creating a run builds a draft from eligible active or authenticated mandates and active policies that match the selected debit day. An authorised user must separately submit the draft through the configured bureau.

A run requires a valid collection period, debit date and at least one matching mandate linked to an active policy. Check the mandate status and its debit day. Creating a draft does not submit a debit.

No. Use a confirmed provider result or a recorded payment outcome. A scheduled debit date on its own is not confirmation of success or failure.

Provider availability depends on your organisation’s approved, current provider setup. The collection-run workflow currently submits to Netcash when tenant credentials and provider readiness are in place.

A claim must first be moved to Under Review. Tenant Admin, Branch Manager, Claims Handler and Underwriter roles can record an approval or rejection decision. Finance can mark an approved claim as paid out.

Approval is only shown for a claim in Under Review and to a role with decision permission. If the claim is Pending or Submitted, an authorised reviewer must select Start Review first.

It means that no automated result is recorded on the claim. It is not a finding that fraud occurred. An authorised reviewer should follow the organisation’s manual review process and record the outcome.

An authorised staff member can publish a member-facing update on the claim record. Internal review notes and member-facing updates should be kept separate.

The Leads workspace supports prospect assignment, status and priority tracking, next-step dates, follow-up tasks and activity history. Agent visibility is restricted to leads assigned to that agent.

Available campaign and notification workflows depend on messaging-provider configuration, contact information and consent. A saved activity entry is not itself a sent call, email or message.

Commission administration and renewal workflows are available in the operations area when they are enabled for the account. Check your plan configuration and the records for each policy before processing a run.

Each funeral business, broker or insurer is responsible for its own licences, authorisations, lawful processing and regulatory obligations. Polisystem provides administration software and does not issue an operator licence.

Hosting location, backup and retention arrangements depend on the live deployment and hosting configuration. Ask the Polisystem team for current details before uploading member, payment or claims information.

Provide an individual login for each staff member, choose role permissions appropriate to their duties, review access when roles change and remove access when it is no longer needed.