ARVATO LIMITED

Procurement & Purchase-to-Pay Saas (SAP S/4HANA & Unit4 ERP)

Cloud-hosted SaaS service providing procurement management capabilities, including purchasing workflows, supplier management and reporting. The service supports secure and governed procurement processes, enabling public sector buyers to manage sourcing, purchasing and spend in line with policy and regulatory requirements.

Features

• SAP S/4HANA procurement configuration supporting end-to-end purchase-to-pay processes
• Unit4 ERP procurement management for complex public sector organisations
• Cloud-hosted procurement SaaS supporting requisition-to-pay workflows
• Supplier onboarding and management within SAP and Unit4 ERP environments
• Contract and catalogue-based purchasing aligned to procurement policies
• Integration with finance systems for budget control and commitment accounting
• Role-based approval workflows supporting public sector governance requirements
• Secure procurement data management across ERP platforms
• Reporting and analytics for procurement spend and supplier performance
• Ongoing procurement SaaS support, configuration and optimisation services

Benefits

• Enables compliant procurement delivery across public sector organisations
• Improves control over spend through integrated purchase-to-pay processes
• Reduces manual procurement effort using ERP-integrated workflows
• Supports transparent supplier management and audit-ready procurement operations
• Enhances governance through standardised approval and control mechanisms
• Improves procurement efficiency across finance and operational teams
• Reduces procurement risk through secure cloud-based ERP platforms
• Supports shared services procurement models across multiple organisations
• Improves visibility of procurement spend and supplier performance
• Enables scalable procurement delivery aligned to public sector change

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at richard.husband@arvatoconnect.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

398232205384478

Contact

Richard Husband
07867464428
richard.husband@arvatoconnect.co.uk

About your service

• Service categories:

  Applications

  Enterprise resource management

  • Procurement
• Multi cloud support: Yes

Service scope

• Software add-on or extension: Yes, but can also be used as a standalone service
• What software services is the service an extension to: This service extends leading ERP and procurement platforms, including SAP S/4HANA, SAP Ariba, and Unit4 ERP. It integrates seamlessly with finance, supplier management, contract lifecycle, and reporting systems, enabling end-to-end source-to-pay processes within an integrated ERP and supply chain management environment.
• Cloud deployment model:
  • Public cloud
  • Private cloud
  • Community cloud
  • Hybrid cloud
• Service constraints: The service is delivered as a cloud-hosted SaaS solution and does not require buyers to provide or manage hardware or infrastructure. Planned maintenance and platform updates are scheduled and managed by the supplier, with advance notice provided where maintenance may impact service availability. The service relies on standard web access and secure network connectivity. Integration with third-party systems is subject to the availability and compatibility of those systems and agreed interfaces. Buyer-specific configuration is supported within standard service parameters.
• System requirements:
  • Secure procurement environment setup
  • Workflow and approval configuration
  • Supplier data configuration
  • User access and role configuration
  • Integration with finance systems
  • Data migration planning and execution
  • Reporting configuration
  • Testing and validation
  • Phased deployment approach
  • Go-live support and stabilisation

User support

• Email or online ticketing support: Yes
• Support response times: Email and online ticketing support requests are acknowledged within one working day during UK business hours. Issues are prioritised and responded to in line with agreed service levels, with critical incidents handled more urgently. Weekend and extended support options can be agreed at call-off.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: Yes
• Web chat support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support accessibility standard: WCAG 2.2 AA
• Web chat accessibility testing: Our web chat functionality is assessed as part of our wider accessibility assurance activities for online support tools. We undertake accessibility testing against WCAG 2.2 AA requirements, focusing on usability with common assistive technologies and inclusive interaction patterns.; Testing includes verification of compatibility with screen readers, keyboard-only navigation and screen magnification tools, ensuring that users can access, navigate and interact with web chat features without reliance on a mouse or visual cues alone. We check that chat controls, message input fields, notifications and status updates are correctly exposed to assistive technologies and that focus order and labelling are logical and consistent.; Where third-party web chat platforms are used, we review supplier accessibility documentation and conformance statements and validate behaviour through internal accessibility testing. Findings are reviewed as part of continuous service improvement, and issues are prioritised for remediation where required.; Accessibility considerations are also incorporated into support processes, ensuring that users who cannot easily use web chat are able to access alternative support channels such as email or phone. Accessibility testing is revisited following material changes to the web chat interface or platform to maintain ongoing compliance.
• Onsite support: Yes, at extra cost
• Support levels: We provide structured support levels aligned to buyer requirements and the criticality of procurement services. Support levels define how incidents, service requests and configuration queries are prioritised, handled and escalated.; Standard support is provided through email and ticketing channels during agreed service hours and covers incident management, purchasing issues, reporting queries and configuration support. Where required, enhanced support levels can be agreed at call-off to provide additional coverage for business-critical procurement activities, such as extended service hours or higher priority response.; Support delivery may include access to specialist procurement system or cloud support engineers where appropriate. A named technical account manager or service contact can be agreed at call-off to support coordination, communication and ongoing optimisation.; The cost of different support levels is agreed at call-off based on coverage, service hours and support requirements selected by the buyer, ensuring transparent and proportionate pricing.
• Support available to third parties: Yes
• AI chatbot: Yes

Onboarding and offboarding

• Getting started: We support users to start using the procurement service through a structured onboarding approach. Onboarding begins with initial setup of procurement environments, user access, roles and permissions aligned to buyer requirements.; We help users understand how to create requisitions, manage approvals, work with suppliers and use reporting features. Where required, onboarding includes validation of migrated data, confirmation of integrations and review of security and governance settings.; Guidance is provided through documentation, user guides and remote onboarding sessions where agreed. Onboarding scope and delivery are agreed at call-off to ensure they are proportionate and aligned to the buyer’s intended use of the service, supporting a smooth transition to live procurement operations.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: At the end of the contract, users are supported to extract their procurement data in a controlled and secure manner. Data extraction is carried out using standard service export functionality, subject to appropriate access permissions.; Data can be exported in commonly used, open formats to support audit, reporting or migration to alternative systems. Data extraction arrangements, including scope, format and timing, are planned as part of agreed exit management activities.; Access to export functionality is restricted through role-based access controls to ensure only authorised users can perform extraction activities. Where required, support can be provided to assist with data extraction, subject to agreement at call-off.; Following completion of data extraction, access is removed and remaining data is handled in line with agreed data sanitisation and retention processes.
• End-of-contract process: At the end of the contract, we support an orderly and controlled exit from the procurement service. End-of-contract activities include support for data extraction, removal of user access and secure handling of remaining service data.; The standard contract price includes normal service operation, routine support and end-of-contract activities required to securely close the service, including enabling users to extract their data.; Activities beyond standard exit support may incur additional cost. This may include extended transition assistance, bespoke procurement reporting, additional data transformation or continued access beyond the agreed contract end date.; All exit activities, scope and any associated additional costs are agreed at call-off to ensure transparency and alignment with buyer requirements.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
  • Linux or Unix
  • MacOS
  • Windows
  • ChromeOS
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: The service is designed to be accessible on mobile devices using modern web browsers or supported mobile applications where available. Core user functions, such as submitting requests, viewing status and completing approvals, are available on mobile. Some advanced administrative, configuration and reporting functions are optimised for desktop use due to screen size and complexity. The mobile experience focuses on usability for common tasks while maintaining consistent security and access controls across mobile and desktop platforms.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: The service is accessed through a secure, web-based user interface designed for role-based use across employees, managers and administrators. The interface provides dashboards, forms and workflow screens to support day-to-day tasks and approvals. Navigation is consistent and intuitive, with contextual guidance where appropriate. The service also exposes standards-based APIs and integration interfaces to support connectivity with related business systems. Access is controlled through authentication and role-based permissions to ensure users only see functions relevant to their role.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: Accessibility testing of the service interface is carried out as part of our wider usability and accessibility assurance activities. Testing is performed against WCAG 2.2 AA criteria to ensure the interface can be used effectively with common assistive technologies.; Testing includes validation of compatibility with screen readers, keyboard-only navigation, screen magnification and high-contrast settings. We assess focus management, logical reading order, form labelling, error messaging and the accessibility of interactive elements to ensure they are correctly exposed to assistive technologies.; Where the service relies on third-party platforms or components, we review supplier accessibility documentation and conformance statements and validate key user journeys through internal accessibility testing. Any accessibility issues identified are logged, prioritised and addressed through standard change and improvement processes.; Accessibility testing is repeated following material interface changes or platform updates to ensure continued compliance. Alternative support channels, such as email or phone support, remain available to ensure all users can access the service if accessibility needs cannot be fully met through the primary interface.
• API: Yes
• What users can and can't do using the API: The service provides standards-based APIs to support integration with other business systems and automation of defined service functions. APIs are primarily intended for data exchange and process integration rather than full service configuration.; Users can use the APIs to set up integrations with related systems, such as HR, finance, payroll, procurement or reporting platforms. This includes the automated exchange of master data, transactional data and status information required to support end-to-end business processes.; ; Users can make changes through the API where supported, such as updating records, submitting transactions, retrieving status information and triggering defined workflows. API access is secured and controlled through authentication and role-based permissions to ensure only authorised systems can interact with the service.; The service does not support full administrative or platform-level configuration through the API. Core service setup, structural configuration and security administration are managed through the standard user interface and controlled change processes. API usage is subject to documented limits, including rate limits and supported operations, to protect service performance, stability and security.
• API documentation: Yes
• API documentation formats:
  • HTML
  • PDF
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: The service supports configuration-based customisation to allow buyers to tailor functionality to their organisational needs while remaining within standard service parameters.; Users can customise elements such as business rules, workflows, approval hierarchies, user roles, data fields, reporting views and policy settings. These configurations enable alignment with organisational structures, governance requirements and operational processes without altering the underlying platform.; Customisation is carried out using built-in configuration tools and administration interfaces provided by the service. Changes are typically managed through controlled configuration processes and may be applied by authorised administrators within the buyer organisation or by the supplier on the buyer’s behalf.; Only users with appropriate administrative permissions can perform configuration activities. End users interact with the service based on configured roles and permissions but cannot alter core system behaviour.; The service does not support unrestricted bespoke development or modification of core platform code. Any customisation beyond standard configuration, such as integrations or extensions, is subject to agreed scope, governance and change control to ensure service stability, security and supportability.

Scaling

• Independence of resources: The service is designed so that demand from one user does not adversely affect others. This is achieved through cloud-hosted infrastructure supporting resource isolation, workload management and scalable capacity. Procurement workloads are monitored and resources adjusted to accommodate changes in demand. Configuration settings ensure appropriate separation between users, supporting consistent service performance and availability.

Analytics

• Service usage metrics: Yes
• Metrics types: The service provides usage and operational metrics to support service management and oversight. Metrics may include user activity levels, transaction volumes, processing status and service availability indicators. Administrative users can access standard reports and dashboards to monitor usage and operational performance. Where supported by the underlying platform, logs and reports can be used to support audit, troubleshooting and capacity planning. The availability and detail of metrics may vary by service component and agreed configuration.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: Yes

Resellers

• Supplier type: Reseller providing extra features and support
• Organisation whose services are being resold: SAP SE (SAP S/4HANA and SAP SuccessFactors) and Unit4

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: Security Clearance (SC)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations: United Kingdom
• User control over data storage and processing locations: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least every 6 months
• Penetration testing approach: ‘IT Health Check’ performed by a CHECK service provider
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase
  • Degaussing
  • Physical Destruction / Hardware containing data is completely destroyed

Data importing and exporting

• Data export approach: Users can export their procurement data using standard service export functionality, subject to access permissions. Data exports may include requisitions, purchase orders, supplier information, contracts and reports. Data is provided in commonly used, open formats to support reuse or transfer. Export functionality is restricted through role-based permissions to ensure only authorised users can perform exports.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • Microsoft Excel
  • XML
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • Microsoft Excel
  • XML

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection between networks: We operate a multi account strategy to AWS via Direct Connect link and VPN. SSL/TLS certificates are used to secure network communications and establish the identity of websites over the Internet as well as resources on private networks. Virtual Private Clouds (VPC's), subnets, routing tables, Internet Gateways, VPN connections, Security Groups and Network Access Control lists are used to deploy and run applications. Inbound and outbound traffic filtering is carried out at the instance and subnet level.
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection within supplier network: We operate a multi account strategy to AWS via Direct Connect link and VPN. SSL/TLS certificates are used to secure network communications and establish the identity of websites over the Internet as well as resources on private networks. Virtual Private Clouds (VPC's), subnets, routing tables, Internet Gateways, VPN connections, Security Groups and Network Access Control lists are used to deploy and run applications. Inbound and outbound traffic filtering is carried out at the instance and subnet level.

Availability and resilience

• Guaranteed availability: The service is delivered as a cloud-hosted SaaS solution with a target availability of 99.9% measured on a monthly basis, excluding planned maintenance. Availability is monitored continuously to ensure service performance and reliability.; Planned maintenance activities are scheduled outside of core UK business hours wherever possible and are communicated to users in advance. Emergency maintenance may be undertaken where required to protect service security or stability.; Service availability commitments and associated service levels are set out in the call-off contract and service schedule agreed with the buyer. Where availability falls below the agreed service level in a measurement period, service credits may be applied in line with the agreed Service Level Agreement (SLA). Service credits are typically calculated as a percentage of the monthly service charge for the affected service.; Service credits are the buyer’s sole financial remedy for failure to meet availability service levels, unless otherwise agreed in the call-off contract. Detailed SLA definitions, measurement methods, exclusions and credit arrangements are agreed at call-off to ensure transparency and alignment with buyer requirements.
• Approach to resilience: The service is designed to be resilient and to protect service assets in line with the government’s cloud security principles. It is delivered using cloud infrastructure that incorporates resilience at multiple layers, including compute, storage, network and application components.; The service is hosted in resilient data centre environments with redundancy built into power, cooling and network connectivity. Data is stored on resilient storage platforms with replication and backup mechanisms to protect against data loss. Service components are designed to recover automatically from common failure scenarios, reducing the risk of single points of failure.; Monitoring is in place to detect service issues and trigger response and recovery processes. Backup and restore capabilities support the recovery of data and service components in the event of an incident, with recovery objectives defined in line with service criticality.; Detailed information about the underlying data centre architecture, resilience design and recovery arrangements is available to buyers on request, subject to appropriate confidentiality controls. Resilience and recovery arrangements are reviewed regularly and form part of ongoing service assurance and improvement activities.
• Outage reporting: Service availability and outages are monitored continuously as part of standard service operations. Where a service disruption is identified, incidents are logged and managed through established incident management processes.; Users are informed of service outages and significant service issues through service communications, which may include email notifications to nominated contacts and updates via the service support channels. Communications provide information on the nature of the incident, current status and progress towards resolution, with follow-up updates provided as appropriate.; Where supported by the underlying platform, service status information may be made available through platform status pages or dashboards. Access to these dashboards is provided where applicable and may vary depending on the service component.; The service does not rely on a publicly accessible outage API. However, incident and availability information can be shared with buyers through agreed reporting and support channels.; Planned maintenance activities that may impact service availability are communicated in advance to minimise disruption. Detailed outage reporting, including root cause and corrective actions, can be provided to buyers on request in line with agreed service management arrangements.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password
• Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is restricted using role-based access controls. Users are granted access based on their role and responsibilities, applying the principle of least privilege. Authentication controls are used to ensure only authorised users can access administrative functions or raise support requests. Access rights are reviewed regularly and removed when no longer required. Support channels are restricted to authorised buyer contacts, and activity is monitored through logging and audit mechanisms to maintain security and accountability.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

• Access to user activity audit information: Users have access to real-time audit information
• How long user audit data is stored for: At least 12 months
• Access to supplier activity audit information: Users have access to real-time audit information
• How long supplier audit data is stored for: At least 12 months
• How long system logs are stored for: At least 12 months

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • CSA CSM version 4.0
  • ISO/IEC 27001
• Information security policies and processes: We follow a structured set of information security policies and processes designed to protect the confidentiality, integrity and availability of the service and service user data. These policies are aligned to recognised good practice and public sector security expectations.; Information security is governed through documented policies covering areas such as access control, data protection, risk management, incident management, change management and supplier management. Access to systems and data is controlled through role-based permissions and the principle of least privilege.; Security processes include monitoring and logging of security-relevant activity, vulnerability management, secure configuration management and defined incident response procedures. Security incidents are investigated, managed and resolved in line with documented processes, with appropriate communication to buyers where required.; Information security policies are supported by staff security awareness training and regular review of controls to ensure they remain effective and proportionate. Where buyers require additional assurance, further detail on relevant policies and processes can be provided at call-off.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: We manage configuration and change in line with ITIL best practice to maintain service stability, security and data integrity. Configuration items are recorded and maintained to support traceability, impact assessment and audit. Changes are managed through a formal change enablement process, with all changes assessed for risk, impact and dependencies before approval. Higher-risk changes receive additional governance and review. Testing and validation are performed proportionate to change risk prior to deployment. Buyers are notified of planned changes through agreed communication channels. Emergency changes follow controlled procedures to restore service quickly while maintaining governance and post-implementation review.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: We operate a structured vulnerability management process to identify, assess and remediate security threats to the service. Vulnerabilities are identified through risk-based reviews, system monitoring and changes in the threat landscape. Information is sourced from cloud provider advisories, supplier notifications and recognised vulnerability databases.; ; Identified vulnerabilities are assessed based on severity, impact and likelihood of exploitation, with remediation prioritised accordingly. Security patches and configuration updates are deployed in a timely manner, aligned to service criticality. Patching activities are planned and implemented using controlled change management processes to minimise service disruption.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: We operate protective monitoring processes to identify, assess and respond to potential security compromises affecting the service. Monitoring includes the collection and review of security-relevant events such as authentication activity, access attempts, system changes and anomalous behaviour.; ; Potential compromises are identified through alerts, log analysis and event correlation using defined thresholds and indicators. When a potential incident is detected, it is investigated in line with incident response procedures, with actions taken to contain, remediate and escalate where required. Buyers are informed in accordance with agreed communication processes. Monitoring processes are reviewed regularly to ensure they remain effective and proportionate.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: We operate protective monitoring processes to identify, assess and respond to potential security compromises affecting the service. Potential compromises are identified through monitoring and review of security-relevant events such as access attempts, authentication activity, system changes and anomalous behaviour.; When a potential compromise is identified, it is investigated in line with defined incident response procedures. Actions may include containment, further analysis, remediation and escalation to specialist security resources where required.; Response times are prioritised based on severity and impact. High-risk incidents are responded to promptly to minimise risk and restore service integrity.
• Post-quantum cryptography secure: Yes

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: Yes
• Connected networks: Public Services Network (PSN)

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: A free trial is not provided. The service is delivered as a fully managed SaaS solution configured to buyer requirements. Demonstrations and walkthroughs are available on request. Trial environments may be provided by agreement at call-off, subject to scope, security and commercial terms.

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 0%
• Between £250,000 and £500,000: 5%
• Between £500,001 and £1,000,000: 5%
• Between £1,000,001 and £2,500,000: 5%
• Between £2,500,001 and £5,000,000: 5%
• Over £5,000,001: 5%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: BSI
• ISO/IEC 27001 accreditation date: Wednesday 7 September 2022
• What the ISO/IEC 27001 doesn’t cover: While it is not practicable to list exclusions in isolation, our ISO 27001 certification supports all contracted services to ArvatoConnect customers, including contact centre, back-office and IT services.
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: BSI
• ISO 9001 accreditation date: Monday 16 January 2023
• What the ISO 9001 doesn’t cover: While it is not practicable to list exclusions in isolation, our ISO 9001 certification supports business process outsourcing, delivering a comprehensive range of front and back office services. This includes customer experience services and administrative services.
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: Fbb5c636-5561-4d78-b819-3360c25ffe07
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: A774e5a5-9ad4-4cbf-a7a3-e47ea2c0ef05
• Other security certifications: Yes
• Any other security certifications:
  • Tisax
  • ISO 20000-1:2018

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at richard.husband@arvatoconnect.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.