ACORD standards

At the heart of the modernisation of Lloyd’s is the use of standards; the next step being the use of standardised messaging between managing agents and brokers.

  • ACORD standards

    The market has made moves towards this with agreed stages in the core business processes and documents, but this must now be more widely adopted as the market standard and considered best practice. The Exchange will act as a vehicle for enforcing message standards and driving use within the market.

    ACORD and the Exchange

    The Exchange uses agreed ACORD messaging standards to ensure a common framework and guidelines for all electronic communication within the London market.

    The Exchange seeks to drive market standards and therefore will not accept non-ACORD messages. It will support the transfer of all messages to the agreed ACORD RLC and DRI standards being used.

    Structured information sent electronically will be validated against the agreed versions of the ACORD standard. Users are notified where validation has failed ensuring the common use of the standard.

    Ultimately, a single standard will be adopted and the market will move to the next version of a standard at the same time.

    A smarter way of sharing information

     Using ACORD standards a number of benefits can be achieved, including;

    • Enhanced interoperability; systems able to talk to each other in the same language.
    • ACORD messages can update back office systems and documents can be delivered directly to document repositories.
    • ACORD is a global standard - data becomes international and portable.

    Which ACORD version will be used?

    The Exchange will support a single version of the ACORD standard from ensuring the whole market speak the same language.

    Currently the Exchange enforces:

    • The exchange of messages conforming to an agreed messaging protol - ACORD AMS, currently version 1.4
    • The exchange of documents conforming to ACORD DRI, currently version 1.2
    • The exchange of placing information conforming to the current ACORD RLC Standard, currently versions 2009.1 (Placing) and 2010.2 (EBOT/ECOT)

    ACORD validation

    The Exchange provides ACORD schema & RLC placing validation at its centre.

    The Exchange will therefore validate the messages against the accepted versions of the ACORD standard and notify users where validation has failed. Users should also continue their own internal validation.

    Three types of validation as laid out in the ACORD guidelines for placing are:

    • Transport level (HTTPS)
    • SOAP level (SOAP signed)
    • Business level (Schema and ACORD RLC placing validator)
  • ACORD 2009.1

    The adoption by the market of a common version of the ACORD message standard is a key step in London’s development of electronic messaging to support the face to face process. 

    Market participants have put in a huge effort working with ACORD in specifying the 2009.1 version of the Placing standard, especially in aligning London market specialities with international practices.

    The market agreed to implement the ACORD 2009.1 structure for Placing on 19 February 2010.

  • ACORD certification

    It is a requirement that any organisation intending to directly connect to the Exchange is ACORD certified. This includes IT service providers and also managing agents and brokers that connect direct via internally developed systems.

    The Exchange has been certified by ACORD.

    ACORD Testing and Certification Facility (TCF)

    The ACORD Testing and Certification Facility (TCF) is a live application which organisations can interact with in order to test and certify their implementations of ACORD messages.

    TCF has two modes - message only certification and business trading partner certification:

    • The message only certification simply checks the XML message to see if it follows the various rules required by the standards.
    • The "virtual" business trading partner, allows ACORD messages to be sent to the TCF. The TCF will validate the messages, and then send back responses indicating acceptance or error(s). The TCF, in this mode, can also trigger messages to be sent.

    Getting certified via the Exchange

    Certification can be achieved via a direct connection to the TCF or alternatively organisations can connect via the Exchange, the former option means the process will be in line with how an organisation subsequently uses the Exchange.
    ACORD is the primary point of reference for all enquiries relating to ACORD certifications.

    Please refer to the ACORD website for details on how to request certification.

    If you have any questions, please email ACORD directly.



Our cookies are there to make it easier for you to use our website. They allow us to recognise our registered users, count visitor numbers and find out how they navigate the site; helping us make changes so you can find what you’re looking for faster. Find out more