Role-based access
Access is assigned by role so users can work within the responsibilities defined for their process.
Our approach
Controls should be understandable before deployment, not discovered afterwards.
Security requirements differ by product, integration and customer environment. SPC3 documents the applicable controls and confirms deployment-specific requirements during technical review.
We do not claim certifications that have not been independently awarded. Detailed architecture and operational evidence are shared through the appropriate procurement and security process.
Product controls
Built into the workflow.
Strict tenant isolation
Customer environments are separated so one organisation cannot access another organisation's product data.
Decision-level audit trail
Automated checks, matches, holds and hand-offs remain visible with the reason for each outcome.
Configurable controls
Rules and tolerances can be configured and tested against historical scenarios before release.
Duplicate prevention
DynaPay checks for duplicates at intake and against invoice history before an invoice is posted.
Microsoft Azure hosting
SPC3 product workloads are hosted on Microsoft Azure. Deployment details are confirmed during technical review.
Technical review
Bring your security and integration requirements into the evaluation.
Product and deployment architecture
Identity, roles and access model
ERP connection and data flows
Hosting and environment requirements
Retention and operational requirements