1. Engagement and Initial Request
For all new integrations, the client's first point of contact is their designated Client Success Manager (CSM). This is a deliberate gatekeeping step to ensure the request is logged within the account’s strategic roadmap. The CSM will provide the formal Integration Request Form, which serves as the foundational document for the project.
2. Scoping and Requirements Definition
Once the form is submitted, it undergoes a formal review process. This is not a simple "tick-box" exercise; it is an evaluation of:
Data Mapping: Ensuring the fields in the third-party ERP (e.g., Oracle, SAP, or Unit4) align with the Atamis schema.
Workflow Impact: Determining how the synchronisation of purchase orders or invoices affects existing procurement approvals.
Implementation Effort: Estimating the man-days required for configuration, testing, and go-live support.
3. Technical Implementation and Security
Following formal approval and scoping, the technical teams engage. This involves the configuration of secure APIs and the establishment of authentication protocols. In a UK public sector context, this must adhere to Cyber Essentials Plus or relevant ISO standards, ensuring data at rest and in transit is fully encrypted.
4. Testing and Validation
Rigorous UAT (User Acceptance Testing) is conducted in a staging environment. This is critical for financial integrations where an error in a payment status sync could result in duplicate payments or HMRC compliance issues regarding VAT treatment.
Updated