How to Choose CSP Compliance Software in SingaporeA Demo Scorecard

Define the purchasing scope before the demonstration

Describe the work the initial rollout must cover. Record client and service types, jurisdictions, layered structures, approximate volumes and the systems that will remain. Distinguish incorporation work from continuing engagements where the information and hand-offs differ.

ACRA's guidelines for registered CSPs explain obligations under the Corporate Service Providers Act and associated regulations. Use these official materials to establish your control requirements. A vendor's claim that its product is “compliant” is not a substitute for that assessment.

Produce a one-page brief identifying:

• The client population and services in scope
• Who prepares, reviews, approves and handles exceptions
• Where authoritative client and risk records will sit
• Which unresolved issues prevent progress under your policy
• What evidence must remain retrievable after a record changes

Separate essential requirements from conveniences. Agree both before seeing products, so an attractive demonstration cannot quietly change the purchasing criteria.

Corporate-secretarial tools may handle filings, deadlines and billing. Ask where compliance decisions will be recorded if those activities stay elsewhere. A shared client name does not establish that the evidence and approval records are connected.

Set mandatory gates outside the scorecard

A weighted total helps compare strengths and trade-offs. Mandatory gates determine whether a product is eligible for your intended use.

Define each gate as a test with an expected result, an owner and retained evidence. For example, an intake user must not approve a case reserved for a reviewer. After a shareholder change, the earlier acceptance decision must remain reconstructable. An unresolved authority question must follow the restriction or exception route specified by your policy.

Do not write gates as vague statements such as “good security” or “audit-ready”. State the action attempted, the user role and what must happen. Agree which gates apply to the first deployment and which are relevant only to a later expansion.

Record a gate as passed, failed or not yet tested. A screenshot, roadmap statement or vendor assurance may explain a capability, but it does not pass a live test. If an essential feature is unfinished, keep the dependency visible rather than awarding conditional success.

Run the same three CSP demonstrations

Use synthetic records and consistent instructions. Give each vendor the same preparation time and evidence pack. Include an operational user as well as the people assessing governance and purchasing terms.

Case one: a straightforward incorporation engagement

Create a hypothetical Singapore company with two individual shareholders and an authorised representative. Supply complete, consistent documents. Ask the operator to take the case from intake through verification, screening, risk assessment and approval.

Observe where details are entered again and which evidence the reviewer actually sees. A document uploaded to a folder should remain distinguishable from a completed, attributable verification step.

Finish by asking another user to explain why the client was accepted. They should find the relevant people, roles, evidence and decision without relying on the demonstrator's memory. Retain the resulting case record as the reference for later change tests.

Case two: layered ownership with conflicting dates

Use a hypothetical client owned by two corporate shareholders in different jurisdictions. Include an ownership chart and a newer document that changes one relationship.

Ask the vendor to show the source behind each link, the relevant dates and any unresolved gap. The expected outcome is a reviewable ownership path and documented conclusion under your applicable policy. A diagram alone does not establish verification.

Then ask what happens if the intermediate company has a similar name to an existing record. Observe how the operator confirms the identifier and corrects a mistaken association. Keep economic ownership calculations distinguishable from control conclusions.

This case tests evidence handling rather than how many layers the demonstration can draw. The related KYC and KYB guide explains the broader distinction between individual and business checks.

Case three: approval attempted before an exception is resolved

Give the same client a possible screening match and missing evidence of the representative's authority. Ask the demonstrator to attempt approval using an ordinary intake account.

The expected result should follow your policy: a blocked action or a controlled exception route, with appropriate authority and a recorded reason. Test the authorised reviewer account separately. The existence of an administrator account should not obscure the permissions ordinary staff will receive.

Next, resolve only one issue. Check whether the remaining issue stays visible and continues to affect progress appropriately. Finally, reassign the case when its owner is absent and inspect the hand-over record.

These scenarios turn familiar CSP compliance challenges into observable purchasing criteria. Keep the broader problems in that guide; use the demonstration to prove how the proposed configuration handles them.

Apply the 100-point demo scorecard

This is an illustrative purchasing instrument, not an ACRA assessment framework. Adapt and freeze the weights before demonstrations begin. The weights below total 100.

Use the same zero-to-three rubric for every row:

• 0: Absent, unproven or not demonstrated
• 1: Demonstrated only through a substantial manual workaround
• 2: Demonstrated with a manageable, explicitly recorded limitation
• 3: Demonstrated against the agreed case, supported by retrievable evidence

For each row, multiply the weight by the score divided by three. Add the row results. The maximum total is 100.

For example, a score of two for ownership verification earns 15 × 2 ÷ 3 = 10 points. A score of three earns 15 points. Retain enough precision when calculating and round only the final presentation, so rounding does not change the comparison.

Keep the observations beside each result. “Export demonstrated, approval history missing” is more useful than a bare score of two. The scorecard explains relative fit; the separate gate register decides whether an essential failure blocks selection.

Make scoring reproducible across reviewers

Have assessors record provisional scores independently before discussing the result. If one person awards three and another awards one, compare their evidence and interpretation of the rubric. Do not settle the difference by averaging incompatible observations.

Record the case, product configuration, user role and demonstration date. Identify whether a step used the proposed standard configuration, custom development or a manual service. A capability shown in another package should not be scored as included in your quotation.

Give vendors a concise findings list and a chance to clarify factual misunderstandings. If a follow-up demonstration changes a result, retain both observations and explain the revised score. Apply the same opportunity to other shortlisted vendors where the issue affects comparability.

A hypothetical vendor with 82 points and a failed access gate remains unsuitable for the approved scope until that failure is resolved and retested. The number must not obscure the reason.

Retest historical retrieval and ongoing work

Use the client accepted in case one. Change a shareholder and update the risk assessment, then ask a user who did not prepare the case to retrieve the original decision.

They should identify the evidence considered at the time, the reviewer, approver and conditions. Check whether the earlier screening result remains available. Ask how data-source licensing affects later access to reports.

ACRA's compliance-review process includes examination of risk assessment, internal controls, customer verification and beneficial-ownership information. Treat evidence retrieval as an everyday operational requirement, rather than a special export assembled for a review.

Introduce a review becoming due and another ownership change. Observe assignment, absence cover and escalation. This is a short acceptance test, not a second monitoring strategy exercise. Configure retention and review responsibilities according to applicable rules and your approved policy.

Resolve purchasing dependencies before signing

Request a small migration and export trial. Include duplicate names, missing identifiers, historical approvals and attachments. Reconcile relationships as well as counts: a successful upload is insufficient if evidence reaches the wrong client.

Keep security assessment proportionate but documentary. Examine access controls, hosting, subprocessors, incident and recovery arrangements, and contractual responsibilities for the proposed service. A logo or broad assurance does not establish the scope of your deployment.

Ask each vendor to price the same volumes and services. Clarify entity, individual, screening, monitoring, user, storage, training and support charges. Identify which recurring activities consume credits or require paid assistance. Capture export formats, charges, access-end dates and exit support in writing.

Before recommendation, assign an owner to every remaining manual step. State its frequency, evidence and supervision needs. A known limitation may be manageable; an unowned dependency is a reason to pause.

The decision paper should contain the gate register, weighted scores, supporting observations, agreed scope and outstanding conditions. That gives management something stronger than a preference for the best-presented product.

Frequently asked questions