Looking at specifications and application guidelines

7 November 2017

2017-11-14 1

Agenda

2017-11-14 2

Tuesday 7 November

09:45 - 10:00Anders Hugosson MD at UC, welcome addressMarie Ljungberg UC, practical information

10:00 – 10:10 Introduction, Nina Brede Bolagsverket

10:10 – 10:30 The agreement, Linn Kempe Bolagsverket

10:30 – 11:50 Application in Bolagsverket’s service, Thomas Holmgren Bolagsverket

12:00 - 13:00 Lunch

13:00 – 14:10 Going through the specifications, Jonas Öhrnell Bolagsverket

14:10 – 14:30 Coffee break

14:30 – 15:00 Information users, Jonas Öhrnell, Bolagsverket

15:00 – 16:15 Handling the auditor’s report, Thomas Holmgren and Jonas Öhrnell

16:15 – 16:30 Summary, Nina Brede Bolagsverket

SimpleDigital

First choice digital

What else can we do together to help companies choose digital first and in order to reach the target of a more simple and effective handling of information in the short and long term?

Working togetheragents, companies, software suppliers, trade organisations,

information providers, information users and others.

We create the

conditions.

The market supplies

the functionality.

The agreement

2017-11-14 6

Linn Kempe, Legal advisor Bolagsverket

Stockholm 7 November 2017

Parties

• The company

• Software supplier

• Bolagsverket

2017-11-14 7

Agreement structure

The company BolagsverketAgreement for owned space

Software suppliersThere may be

agreements in

existence

already…

Requirements …

Work on the agreement is underway

• Briefly about the agreement: ‒ it will be available and can be printed out from Bolagsverket’s website

‒ it should be printed out, signed by an authorised signatory and sent in to

Bolagsverket

‒ the same agreement applies for all software suppliers

• We plan to have the contract ready at the beginning of

December.

• Webinar for going through contract?‒ Is there interest in and need for having a webinar about the contract?

2017-11-14 9

Application in Bolagsverket’s service

Stockholm 7 November 2017

Agenda

• Taxonomies

• Application guidelines

• Taxonomy for extended information

• Example files

• Practical examples

2017-11-14 11

Taxonomies

• The taxonomies that can be applied‒ Annual report for small limited companies (accounting

category K2)

‒ Annual report adoption certificate for limited companies

‒ Auditor’s report for limited companies without company groups

‒ Extended information

• Taxonomy for ‘Annual report for small limited companies (accounting category K2)’ is updated

‒ Two heading changes and addition of three references to legislation

‒ The log of changes is available on the taxonomy web page

2017-11-14 12

Application guidelines

• Contains guidelines about

‒ Application of taxonomies and tagging of data

‒ Application of iXBRL(XHTML)

‒ Other information such as metadata about software

and version

• Example files on www.taxonomier.se are an

important addition till application guidelines

2017-11-14 13

Application guidelines

• New version will be published during November containing:

‒ clarification, with examples, of application

‒ information connected to the taxonomy for ‘extended information’

• It is not a static document and will be updated as needed

• Email us with feedback emsdiar@bolagsverket.se

2017-11-14 14

Taxonomy for extended information

• Facilitates tagging of information missing from,for example, the taxonomy for annual reports

• Will make machine reading easier and facilitate ‘100% tagging’

• The taxonomy supports the following:‒ tagging of undefined terms

‒ note links in an annual report

‒ logging heading changes

‒ status for tagging of information in iXBRL

2017-11-14 15

Taxonomy for extended information

• The description is described on taxonomier.se

‒ in Swedish only. The title is ‘Beskrivning av taxonomin

för utökad information’.

• There is one published example with

application of all functions.

‒ more examples are planned.

• Please email us feedback emsdiar@bolagsverket.se

2017-11-14 16

Example files

• are available on taxonomier.se and contain the following:‒ Annual report taxonomy

‒ Auditor’s report taxonomy

‒ Annual report adoption certificate taxonomy

‒ Application in Bolagsverket’s service

‒ Taxonomy for extended information

• are adjusted as needed and also when theapplication guidelines are updated

• are an important part of the documentation

Use the examples and let us know if you have views/requests.

2017-11-14 17

Practical examples

• Main principle for analysis and tagging

• Logging heading changes

• Tagging note links

• Status for untagged information in iXBRL

• Accounting in units of thousands of SEK v. SEK

• Metadata in the iXBRL document

2017-11-14 18

Main principle for tagging

• Analyse whether the term in the software corresponds

to the scope in the taxonomy

‒ Tag using the existing term in the taxonomy

• Analyse whether the term in the software has a wider

or clearly different scope than in the taxonomy

‒ Tag using the taxonomy for extended information

2017-11-14

Main principle for analysis of terms

• The principle for analysing terms in the taxonomy with the terms in the software is that

‒ the taxonomy’s references to legislation and standards match the definition in the software

‒ the scope of the taxonomy’s standard and documentation headings match the definition in the software

‒ the taxonomy’s properties such as data type, balance(debit/credit) etc. match the definition in the software

• If the above criteria fit, the value should be tagged with the term in the taxonomy.

2017-11-14

Main principle for analysis and tagging

• Note that‒ an XBRL instance document should chiefly contain positive values

‒ the expected value in an XBRL instance document is not always the same as the value presented in iXBRL

• The attribute balance (debit/credit) is used to determine if the value is for example a cost or revenue.

• If debit/credit has not been defined, the standard heading is used to determine which value the instance document should contain.

2017-11-14

Main principle for analysis and tagging

• Debit/credit

‒ for example in the profit and loss statement the ‘Net turnover’ is defined as credit and ‘Personnel costs’ as debit

‒ ‘Personnel costs’ is often shown as a negative figure in iXBRL but as a positive figure in an XBRL instance document

• Standard headings

‒ for example ‘increase (decrease) in reserve fund’ implies that for an increase in the reserve fund there will be a positive figure in the instance document and if a decrease occurs, there will be a negative figure in the instance document.

‒ a word within brackets is expected to represent a negative figure in the instance document

2017-11-14

Main principle for analysis and taggingrisbs risab raibs raiab

Company information x x x x

Administration report x x x x

Profit and loss statement x x

Abbreviated profit and loss statement x x

Balance sheet x x

Abbreviated balance sheet x x

Cash flow statement x x x x

Notes for full profit and loss statement x x

Notes for abbreviated profit and loss

statementx x

Signature and auditor’s signature x x x x

2017-11-14

Example - analysis and tagging

Median number employees 2016-01-01

-2016-12-31

2015-01-01

-2015-12-31

Men 10 11

Women 9 5

Median number employees 19 16

Missing in the taxonomy

Exists in the taxonomy

<se-gen-base:MedelantaletAnstallda id="notmedelantaletanstallda-ref-ar-0-id1" decimals="INF"

contextRef="period0" unitRef="antal">19</se-gen-base:MedelantaletAnstallda>

Existing term in the taxonomy

<se-misc-base:OdefinieratBegreppNumerisktTuple id="notmedelantaletanstallda-ref-ar-1-id3">

<se-misc-base:OdefinieratBegreppNamn contextRef="period1">Not Medelantalet anställda,

Medelantalet anställda kvinnor</se-misc-base:OdefinieratBegreppNamn>

<se-misc-base:OdefinieratBegreppNumeriskt decimals="INF” contextRef="period1" unitRef="antal">5</se-misc-base:OdefinieratBegreppNumeriskt>

<se-misc-base:OdefinieratBegreppTillhorTaxonomi contextRef="period1">ANNUAL_REPORT</se-misc-base:OdefinieratBegreppTillhorTaxonomi>

</se-misc-base:OdefinieratBegreppNumerisktTuple>

Taxonomy for extended information

Example - analysis and tagging

Median number of employees under

402016-01-01

-2016-12-31

2015-01-01

-2015-12-31

Men under 40 10 11

Women under 40 9 5

Median number of employees under 40 19 16

Median number of employees 2016-01-01

-2016-12-31

2015-01-01

-2015-12-31

Men 10 11

Women 9 5

Median number of employees 19 16

The company wants to show the gender divide of all those under 40 but also has

employees who are older than 40.

perception of machine reading based on taxonomy and tagging

<se-gen-base:MedelantaletAnstallda id="notmedelantaletanstallda-ref-ar-0-id1" decimals="INF" contextRef="period0" unitRef="antal">19</se-gen-base:M…

Logging heading changes

Median number 2016-01-01

-2016-12-31

2015-01-01

-2015-12-31

Men 10 11

Women 9 5

Total median number of employees 19 16

Median number of employees 2016-01-01

-2016-12-31

2015-01-01

-2015-12-31

Men 10 11

Women 9 5

Median number of employees 19 16

Correction of heading in presentation

Heading in the taxonomy

is the same term

the change in the heading is

tagged with extended

information

if your template differs from

the taxonomy, use tags

Tagging of note links

Balance sheet Note 2016-12-31 2015-12-31

……

Long-term liabilities 7

Other liabilities to credit institute 8, 10 2 193 000 1 513 000

Other liabilities 100 000 180 000

Total long-term liabilities 2 293 000 1 693 000

……

Note 8 Assets pledged

2016-12-31 2015-12-31

Corporate mortgage 2 000 000 1 800 000

Property mortgage 800 000 800 000

Total assets pledged 2 800 000 2 600 000

Visual note link (iXBRL)

Machine link (XBRL)

Tagging of note links

Balance sheet Note 2016-12-31 2015-12-31

……

Long-term liabilities 7

Other liabilities to credit institute 8, 10 2 193 000 1 513 000

Other liabilities 100 000 180 000

Total long-term liabilities 2 293 000 1 693 000

……

Note 7 Long-term liabilities

2016-12-31 2015-12-31

Liabilities to credit institute 230 000 100 000

Other liabilities 50 000 30 000

Total assets pledged 280 000 130 000

Visuell notkoppling (iXBRL)

Maskinell koppling (XBRL)

Status for untagged information in iXBRL

• Status for untagged information must be applied by software suppliers about all information which has not been able to be tagged in the document

• During machine processing it should help with determining whether a visual check is needed

• Information such as headers, footers, page numbers and sub-headings etc. is not expected to be tagged

• Always use status flag

2017-11-14

Metadata in iXBRL

• Information which is tagged in the <head>-element

‒ Mandatory information

• Software name

• Software version

‒ Optional information

• Name of organisation producing information

• Name of organisation auditing information

‒ Other information

• Other information can be added if desired, such as certification information about the organisation.

2017-11-14

Accounting in units of thousands of SEK v. SEK

• Accounting in units of thousands of SEK (iXBRL)

<ix:nonFraction name="se-gen-base:Nettoomsattning" contextRef="period0" unitRef="valuta”

format=”ixt:numspacecomma” decimals=”-3" scale=”3”>2 650</ix:nonFraction>

• Accounting in SEK (iXBRL)‒ <ix:nonFraction name="se-gen-base:Nettoomsattning" contextRef="period0" unitRef="valuta"

format=”ixt:numspacecomma” decimals=”INF" scale=”0”>2 650 000</ix:nonFraction>

2017-11-14

Accounting in units of thousands of SEK v. SEK

• Accounting in units of thousands of SEK

<se-gen-base:Nettoomsattning contextRef="period0"

unitRef="valuta" decimals=”-3">2650000</se-gen-base:Nettoomsattning>

• Accounting in SEK

<se-gen-base:Nettoomsattning contextRef="period0"

unitRef="valuta" decimals=”INF">2650000</se-gen-base:Nettoomsattning>

2017-11-14

Thank you for your participation

• Questions?

• If you need other documents, examples, etc.,

please email us emsdiar@bolagsverket.se

2017-11-14

Services for digital filing ofannual reports

Stockholm 7 November 2017

Documentation for the services

SLA mm.

TECHNICAL GUIDE

SLA etc.

CONNECTION

GUIDELINES

INTERFACE

SPECIFICATION

APPLICATION

GUIDELINES

TECHNICALFRAMEWORK

AGREEMENT

Technical framework

• General description of the services and other

documentation

• Link to document in Swedish (pdf)

Technical guide

• Describes the services more thoroughly:

• Sequence diagram

• Data descriptions

• Non-function aspects

• Link to documents in Swedish (pdf)

Interface specification

• Full description of the interface in Open API 2.0 format

• Enough information in order to generate REST client

• Link to documents in Swedish (html, yaml)

Connection guidelines

• Describes what is needed in order to connect to

Bolagsverket’s test and production environments:

• Firewall opening

• Client certificate

• Trusting Bolagsverket’s server certificate

• Link to document in Swedish (pdf)

Version management• Bolagsverket’s aim is to have two versions in operation concurrently in the

test environments – the latest version and its most recent predecessor.

• From 2 November 2017 version 0.5 of the services is in operation.

Version 0.4 is still in operation and version 0.3 has been removed.

• URL for services:

https://arsredovisning.bolagsverket.se/api/v0.5/...

https://arsredovisning.bolagsverket.se/api/v0.4/...

• URL for test bench:

https://arsredovisning.bolagsverket.se/testbank

Next version

• Version 0.6 will contain a full implementation of services for

accounting events

• Expected in December 2017

New file formats for annual reports

Stockholm 7 November 2017

Notifications about annual reports -historically

- 2006 2007-2012 2013-2017 2018-

TIF XML

(XBRL)

TIF

PDF

TIF XML

(XBRL)

PDF

iXBRL

XBRL

In 2018 and onwards - iXBRL

iXBRL

XML

iXBRL

Signatures

iXBRL

XBRL

PDF

XML

Conversion

Signature

Customers signed up to receive notifications about annual reports get

four files

• Every filed iXBRL file generates four files on the notifications server:

• iXBRL (filed file)

• XML (iXBRL + signatures)

• XBRL (data in iXBRL file)

• PDF (created from iXBRL file)

• Link to document in Swedish (pdf)

Handling the auditor’s report

Stockholm den 7 november 2017

Handling the auditor’s report

• This is an open forum for discussing possible solutions

• Bolagsverket will present two possible scenarios based on their perspective

• Points to think about‒ How does it compare to the current paper-based processing

using copies?

‒ What possible solutions are there?

2017-11-14

Bolagsverket’s perspective

• There should be one file containing the annual report, the auditor’s report and the annual report adoption certificate. Bolagsverket’s view on this remains unchanged.

• An important condition is that the document is a copy, i.e. that for publishing, only the content need be the same as the original, not the formatting.

• Bolagsverket can help with facilitating a solution but wants to give the market the opportunity to act and work with others in the same way as with SIE, for example.

• Two possible scenarios for handling the auditor’s report in the process

2017-11-14

Bolagsverket – scenario 1

1. The auditor submits the auditor’s report on paper to the company.

2. The company uses the interface (form) in the accounting software

in order to transfer the information from the auditor’s report into

the shared document.

3. The company checks the document before it is uploaded to

Bolagsverket.

2017-11-14

Bolagsverket – scenario 2

1. The auditor submits the auditor’s report in the iXBRL/XBRL format

to the company

2. The information is loaded into the accounting software which

meshes the auditor’s report with the annual report

a) If the company needs to adjust information from the import, the interface

(form) in the accounting software should allow this

3. The company checks the document before it is uploaded to

Bolagsverket.

2017-11-14

Points to think about

• Two issues‒ Would, for example, a structure in iXBRL with separate and fixed

blocks for each document combined with name standards in the files simplify the importing of the auditor’s report to iXBRL?

• This requires agreement between the parties

‒ Must the auditor’s report have exactly the same formatting, including font etc., as the original?

• Would adaption to a template from FAR, for example, solve the problem?

• Suggestions?‒ How does it compare to the current paper-based processing using

copies?

‒ What possible solutions are there?

2017-11-14

Thank you

www.bolagsverket.se/digital-arsredovisning

Nina Brede: nina.brede@bolagsverket.se