NordicSmartGovernment
-
-
- Authentication
- 7. Analytics
- Business management
- 6.1 National Governance
- Encryption
- Risk management
- Data architecture and catalogueing
- 2.2. Manage change and deviations (was: Correctness incl. error detection and correction)
- 1.1 Adoption of eInvoices
- 1.1 Adoption of digital business documents
- Handle life cycle of transactions (versions)
- 1. Use of digital business documents
- Asset management
- Tax insepctions and audit
- 4. Compliance
- Financial accounting
- Accounts recievable and revenue
- 5.3 Maintaining availability
- Operational procurement
- 3.4 High avaliability
- 2.2. Open accounting (Legal access to real time financial transactions in business systems)
- Employee administration
- Payroll
- Taxation services
- Procurement
- General accounting
- 5. Data protection
- Data governance
- Information exchange
- Compensation and benefit
- Financial service regulations
- Tracking / logging
- 7.3 EU Governance
- 3.2 Non-financial automated reports
- Standardisation
- 7.2 Provide anonymised access to aggregated data
- Financial reporting
- Economic and financial management
- Mergers and acquisitions
- Reference and master data management
- Vendor management
- 3.4 Obtaining disclosure control while analysing data
- Customer credit ratings
- Business and industry regulation
- 1.4 Standardisation of eReceipts
- Administrative law
- Financial operations
- 1.3 Adoption of eReceipts
- Justice administration
- Standardized access (APIs)
- Data security
- Transaction processing
- Capability Increment
- Payroll reporting
- 4.1 Born digital
- 4.3 Common representation of businesses (semantics)
- Customer relationship management
- Accounts management
- Data quality
- Sales
- Assosications and corporate law
- ICT Service Design and Development
- Technology management
- 5.1 Provide and maintain confidentiality
- Inventory your data
- 1.2 Adoption of digital product and service information
- Purchase planning
- Capability area
- 5.2 Keeping the data safe (integrity and ownership)
- Data discovery
- 2.1 Provide technical access points to detailed transaction data
- 6.2 Nordic Governance
- 4.3 Maintain avaliability
- Business support and reguslations
- Accounts payable
- Financial auditing
- Time and attendance
- Data management
- Payments
- 3.3 Adressing
- Information delivery
- 2.3. Common representation of transactions (semantics)
- 3. Reporting and analytics
- 6. Governance
- 4.2 Compliance confirmation services
- User consent for B2B sharing
- 2.Transaction availability
- 5.3 Operational metadata on quality and life cycle
- 1.3 VAT automation
- Statistical production management
- 5. Common interpretation
- Business and industry development
- ICT Service Delivery
- Authorisation and access control
- Factoring
- 1.3 Product information - avaliable
- Structured data management
- Capability
- 3.3 Access to data across businesses
- 5.4 Provide traceability
- 1.2 Adoption of eOrders
- Human resource operations
- Product Catalogue management
- Privacy guideline monitoring
- 3.1 Financial reporting
- 1.2.6 Product catalogues should be used with standardized product codes to provide access to machine readable descriptions of product information that can be used thoughout the supply chain. Product codes must be mapped to general codes; UNSPC and Customs code.
- 5.1.3 Provide the mapping between national selected transaction standard and the common reference data model for transactions
- The lookup services (APIs) must be able to identify the format and version of the content.
- 4.1.1 National Solution Building Blocks (SBBs) should provide authorization by power of mandates
- C. Adoption of eReceipts
- 1.1.3 Market the eInvoice feature to their customers. E.g. recommend the sending of an eInvoice if the customer is able to receive it
- F. VAT automation between businesses and business systems
- 1.1.13 Implement mapping and routing from national eReceipts systems to the OpenPeppol network
- Course of Action
- 1.2.4 Enforce the use of product ans service codes in the supply chain.
- 4.1.4 Business registration process should be changed so that businesses are encouraged to be digital and enable registration in the OpenPeppol SMPs
- J2. Enable access to financial transactions in business systems (legal interoperability)
- Bundle (copy)
- 1.1.20 Implement in OpenPeppol BIS eCatalog for Business systems
- 1.1.12 Implement receiving eReceipts in Business systems
- Business systems should provide mechanisms that ensure high availability of APIs (copy)
- 1.3.5 Access to a service that checks the validity of a bank account number against the company number
- 1.3.1 Access to a digital business documents validation services that check that necessary contents are present and used codes etc. are correct
- G. Integrity in the business document exchange
- 1.2.9 Enable to have enough information on domestic level (codes & rules)
- 2.1.1 Establish a standardised service, API, for accessing transactional data about a business
- 4.1.2 Making sure business system (accounting system) fulfill a set of requirements
- Business systems must ensure that the data is kept safe and not compromised so that business secrets isn ́t unwillingly shared with wrong parties.
- 1.2.3 The ordering systems must provide product codes.
- 1.2.5 Enforce a best practice for use of product and service codes in eInvoicing.
- H. Integrity by not having to exchange documents
- 1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses
- Business system provide solutions to ensure that the data is not altered without authorization
- 1.3.9 Access to a service that provides a warning function related to well known "fraud companies" or the bank account number that is used could also be relevant.
- Consumers of data from business systems must be provided a service where businesses, by their organization number, to be mapped to lookup access points (end points). (copy)
- 1.1.10 Standardize the content of eReceipts
- National Solution Building Blocks (SBBs) should provide authorization through user’s consent in B2B
- 1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices)
- Business systems must recognize parts of information that could be considered as a business secret.
- 1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x)
- J1. Enable standarized access to business systems transactional data (technical interoperability)
- 1.1.4 Communicate and promote the business case to the SMEs
- D. Adoption of eOrders, eCatalogs
- 1.1.6 Create incentives in when governments require payments e.g. extending the payment deadline for businesses that can receive an eInvoice
- Secure chain approach
- 1.2.8 Standardize a common mandatory set of product and service information, and make this standard flexible enough that it may be extended with sector-specific information and/or information necessary for compliance
- 1.2.12 Progress in line with the options and possibilities studied earlier eg. proceed towards the goal set by implementing.
- 1.2.1 Include and process product information/codes in the business documents
- National Solution Building Blocks (SBBs) should provide authentication of a company
- 1.3.8 Access to a service that checks that trading partners really exist before sending documents (is registered in business registries)
- 1.1.1 Compliance with CEN semantic model EN-16931 for invoices
- 2.2.1 Require a lookup service to be available (similar to PSD2 directive Account Information Service Provider (AISP) for banks)
- A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement
- 1.3.10 Implement warning services for suspicious events (B2B)
- 1.3.7 Access to a service that checks the “seriousness” of a company, e.g. are taxes paid etc.
- 1.3.4 Legal changes to remove the need to store and archive copies of vouchers
- 2.1.2 Establish a (standardized) role based authorization service for the businesses to grant access to different parties to read/write data (B2B, …)
- 5.1.1 Select a common standard as the core for the semantic representation of transactions
- 1.2.2 Discover product information/codes and access services providing additional information about the product.
- 1.3.6 Access to a service that checks for VAT-registration
- 1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them
- 2.1.5 Provided a service to find the actual lookup access points for a business (eAdressing)
- 1.2.10 Enable to have enough information on cross-border level (code & rules)
- 1.1.19 Compliant with eCatalog BIS format
- 1.3.2 Insist that the digital business document stays entirely unchanged for both the originator and the receiver (meaning that exactly the same physical document must be found on both sides on request) in order to make sure that a voucher is only used once. This enables automated checks (based on hash calculations)
- 2.1.4 Provide mechanisms that ensure high availability of APIs
- 1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them
- 1.1.16 Have an eReceipt follow the Credit/debit card transaction flow
- Business systems can encrypt the communication channels.
- 2.1.3 implement a standardised format for transferring detailed bookkeeping data between systems (portability)
- 1.1.15 Implement eReceipts for all PoS-systems (are able create them)
- E. Adoption of structured product information
- 2.1.5 Provided a service to find the actual lookup access points for a business
- Business systems should have the ability to restrict access to their data, e.g. through an API-manager.
- B. Increase SMEs use of digital business system - born digital
- 4.1.1 Demand a certain group of companies to use digital accounting systems. E.g. remove the minimum capital requirement for limited companies, but demand a digital accounting system
- 1.2.7 Synchronize the processes regarding requiring product and service information to make sure product information is digital before encouraging and demanding it
- 1.1.8 Buyer can demand an eInvoice
- 5.1.2 Ensure a common semantics in supplemental information to the transaction (e.g. business activities, categorization, product information etc.) in order to make comparative analysis
- 4.1.3 Enable registration of business directly from business systems (accounting system, banks or other) (“born digital”)
- 1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering)
- Course of Action
- 1.1.14 Mobile payment services sends eReceipts (B2B)
- 1.2.11 Study the possibilities to utilize eDocuments product information in VAT automation between business systems
- K. Standardize content of business system transactional data (semantic interoperability)
- 1.1.9 Making eInvoicing mandatory in the Nordics
- I. Trust services that enable and increase secure business
- 1.3.3 Enforce a system where sales documents are not sent at all, but stored in one place and being referenced. Eliminates the challenges of having two different copies at each end
- 5.1.4 Base their delivery model on the common representations, and provide access to this as well as the national selected standard
- 2.1.4 Provide mechanisms that ensure high availability of APIs
- Resource (future environment)
- Adressing SBB
- Infrastructure for document exchange SBB
- Product catalog providers
- Regulators
- Standardisation organisations
- Point of sales systems
- Business systems
- Authentication SBB
- 850 kNOK FI (0 kNOK own contribution + 850 kNOK NI contribution) (copy) (copy) (copy)
- Lawmaker
- 433 kNOK NO (133 kNOK own contribution + 500 kNOK NI contribution) (copy)
- Business systems (copy)
- 250 kNOK SE (0 kNOK own contribution + 250 kNOK NI contribution) (copy) (copy)
- OpenPeppol
- 3550 kNOK NO (0 kNOK own contribution + 3550 kNOK NI contribution)
- Architecure Building Block
- Resource
- 3.017 kNOK SE cont. (167 kNOK own contribution + 2.850 kNOK NI contribution)
- NO: 766 kNOK (167 kNOK own contribution + 600 kNOK NI contribution)
- 516 kNOK FI cont. (167 kNOK own contribution + 350 kNOK NI contribution)
- DK: 2.367 kNOK (167 kNOK own contribution + 2.200 kNOK NI contribution)
- Users consent SBB
- Architecure Building Block (copy)
- Authorization/power of mandates SBB
-
- Roles and actors
- Business Actor
- Astrid Sky, Product manager - grapql
- Ranveig Eliassen, release manager
- Business Actor
- Ann-Sofie Silversedt (SE)
- Collaboration with value added services
- Reporting and analytics
- Business partners purchase-to-pay and order-to-cash (rulebook)
- Business Collaboration
- Born digital
- Fraud detection
- Finished
- Receive payment from bank
- Receive Purchase order
- Sale force management
- Account receivables
- Change accounting vendor
- Marketing
- Sales (order handling) and Marketing function
- Inventory Management
- Public procurement
- Account payables
- Financial service offering
- Account and contact management
- Customer Relationship Management (CRM) Function
- General Ledger
- Forecasting and analytics
- Credit lending evaluation
- Cash sales
- Employee
- Data analysis
- Stock/inventory
- Recruitment and onboarding
- Sales order
- Procurement
- Inventory control (tracking inventory transactions)
- Investors evaluation
- Payroll
- Time management
- Other reporting
- Product information management
- Marketing services
- Periodic Financial reporting
- Bank transactions
- Accounting
- Business Function
- Insuring credit
- Human Resources
- Inventory management
- Business analytics
- Provide political influence
- Managing invoices
- Finance and Accounting
- Custom reporting (on request for data capture by Statistics)
- Lead and Opportunity management
- VAT reporting
- Organization
- Bookkeeping
- Tax Audit
- Tax filing
- Product and service catalog function
- Other business opportunities
- Purchase order
- Billing
- Selling
- Purchasing
- Stock utilization reporting
- Annual Reporting
- Maintain partner masterdata
- Benefits administration
- Inventory Replenishment
- Financial Management
- Adjustments
- Income
- VAT Payable
- Profit and loss statement accounts
- Lønnsdokumentasjon
- Receipt
- Purchase invoices
- Dokumentasjon av andre regnskapsmessige disposisjoner
- Catalog (NACE, ...)
- Business document
- Fullfilled order (sales order)
- Statement of balance
- Salgsdokument
- payment
- Account
- Proof of transaction
- price
- Organizational info
- Accounts payable
- Kontospesifikasjon
- Kontoopplysninger
- Order Cancellation
- Set of transactions
- Betalingsdokumentasjon
- Bokføringsspesifikasjon
- company name
- Catalogue
- Catalogue Pricing Update
- Kundespesifikasjon
- Omsetningsoppgave MVA
- Released (purchase) order
- line
- Reminder
- Bank transaction
- Journal
- Receipt
- A-meldingen lønn
- Application Response
- Company
- Merverdiavgiftspesifikasjon
- Balance sheet accounts
- Order Response Simple aka Order Acknowledgement, PO Response
- Cost center attribution
- date of supply
- Payment transactions aka Statements of Account
- Cash Memo
- Product or Service Catalog
- amount/price
- Lønnsspesifikasjon
- Equity
- Catalogue Deletion
- VAT Recveivable
- Leverandørspesifikasjon
- (Purchase) Order
- General Ledger (no: hovedbok)
- Loans
- period
- Credit Note
- Expenses
- Specification Update
- Andre spesifikasjoner
- Annen pliktig regnskapsrapportering
- Sales invoices
- Annen dokumentasjon av bokførte opplysninger
- Purchase ledger/Accounts payable (no: Leverandørreskontro)
- Invoice
- Liabilites
- buyer
- Product or Service
- Catalogue Request
- Payroll slip
- Sales Ledger/Accounts receivable (no:Kunderreskontro)
- Chart of accounts
- Order Change
- Entry
- Quantities of goods and services
- Catalogue Item
- Customer invoice
- Årsregnskap
- Accounts receivalbe
- Vendor details
- Order Response aka Order Acknowledgement, PO Response
- seller
- Debit Note
- Transaction
- Shipping confirmation
- Purchase invoice/supplier invoice
- General Ledger
- Submitted order (purchase order)
- Kjøpsdokument
- Likningsoppgave
- Assets
- Business Process
- Fieldwork: collect information and optain evidence
- Call for tender
- Shipping/delivery
- manage access to aggegated data for reporting, statistics and analytics
- Obtain payment
- Translate
- Internal financial reporting
- Order - buyer places an order
- Invoice Approval and Payment
- Tendering
- Receipt activities
- Catalogue of products and services
- Årsoppgjør og rapportering
- Invoice - seller sends an invoice
- Purchasing (post award)
- Business operations
- Bookkeeping - internal process
- Supply
- External financial reporting
- Invoicing
- Credit Lending Evaluation
- Order processing
- Deliver service or product
- Publish
- Call-off on established contracts
- Payment validation
- Submission and evalutation of tenders
- Provide sales receipt
- Fullfill
- Planning
- Contract management
- Audit panning and strategy
- Notification
- Source
- Contract
- Stock transfer out
- Receive service or product
- Reporting - to government
- Verification of business needs and requirements
- sending and recieving business documents
- Preparation and publication of competition
-
- Accounts Payables
- Inventory count
- Analysis: Evaluate and asses the impact of evidence
- Award
- Establish contract
- manage the detailed transactions and give access to transactions
- Create order for service or product
-
- Purchase order creation
- Payment finalizaion
- Pay
- Tendering (pre-award)
- Enrich
- stjeler bedriftspost og lager en identisk faktura med nytt kontonummer.
- Receipt - seller provides a receipt
- Create invoice
- Tax Auditing
- Payment reservation
- Recieve order
- 3rd party sharing
- Investment, lending and regulation
- Capture/receive/review customers' purchase order
- Know your client/orgaization (KYC)
- Falske faktura, med kjent leverandør som "avsender"
- Classify
- Receive receipt
- False invoice
- Sales order processing
- Sales queries
- Faktura uten forutgående avtale eller bestilling
- Purchase
- Fullfillment i.e. delivery and receipt of goods and services
- Payment
- Employee
- Business Registries
- NCC
- Microsoft Dynamics
- Statistics
- Xledger
- B2B services, Banks, insurance
- Fiken
- Tax,
- DNB
- SME (copy)
- Virke
- Regnskaps Norge IKT-forum
- Investor
- Business Role
- Power office
- Zirius
- Investors
- Identifyuser (authentcation)
- Tax Audit
- Receive order
- Check seriousness
- Check known fraudent actors
- Identify rights (authorization)
- Purchasing
- Finalizing payment
- Receive Shipping Confirmation
- Receive payment
- Stock management
- Getting good trading terms by showing solvency
- Deliver non-financial report to government
- Access transactions
- Receive invoice
- Product catalog lookup
- Deliver financial report to government
- Validating payment
- Validate bank account
- Accepting Invoice
- Report summarizing receipts pertaining to specific products
- Analysis to create added value to the transaction
- Register company API
- Pay invoice
- Access historical transactions
- Send invoice
- Create and send order
- Business Service
- Customer to bank payment
- Dashboard and Progonosis
- Transfering out stock
- Summaries of invoices pertaining specific products
- Receive order goods
- Benchmarking
- Credit rating
- Statistics
- Dynamic financing
- Report on the price levels of products
- Making adjustments
- Check business registration
- Receive order confirmation
- Marketing services
- Bank transaction
- Receive payment
- Send receipt from POS
- Giving credit
- Reserving payment
- Integrity check of business document
- Register accounting system (SMP)
- Pricing statistics
- Analytics
- Exchanging business documents
- Payment clearing and settlement
- Report on specific keywords across invoices
- Discover product information/codes
- Paying
- Registration in OpenPeppol SMP
- Report on sales or purchases for product groups
- Managing inventory
- Check VAT registration
- Store transaction (copy)
- Insurance
- Tracability of products
- Receive receipt
- Portability
- Automatic reporting to government
- Store transaction
- Access data for analytics
- Send order confirmation
- Buffer
- Product
- Nordic API gateway
- Danish Saxo Bank, that opened up for their APIs in September 201510
- Puls
- Transaction
- e-receipts
- fullstendig oversikt over transaksjoner som er debitert konto (camt 054d)
- Innbetalinger (camt.054 credit)
- Bank statement
- betalingsinstruksjoner (betalingsfiler) fra kunde til bank (pain 001)
- kvitteringsfiler (returfiler) fra bank til kunde (pain 002 og pain 003).
- Kontoutskrift (camt.053)
- e-invoice
- e-order
- B01. Gather information
- Phase A. Exploring
- Phase D. Dissolving
- Phase C. Running and Developing
- A02 Business plan
- B02. Gather capital
- B03. Establish [Stifte]
- B05. Register
- B04. Secure Intellectual Property Rights
- B06. Digital tools
- B07. Launch
- B08. Get necessary permits and licences
- B09. Tax and insurance
- C01. Buying and selling
- C02. [Leverandørstyring]
- C05. Credit
- C03. Service providing
- C10. Changes in the organisation
- C06. Need for extra capital
- C07. Employing
- C11. Board and ownership
- C12. Paying taxes (running and periodically)
- C14. Government reporting (annual)
- C16. Payment problems and [innkreving]
- C15. Controls [tilsyn]
- C17. Advice on debts
- C18. Downsizing
- D01. Voluntary dissolving
- D02. Bankrupcy
- A01 Business idea
- Phase B. Establishing
- C09. Manage employees
- C13. End of year accounting
- D03. Forced dissolution
- CXX. Government reporting (running)
- SME
- Reporter
- Statistics Norway
- Recieve Reports
- SME
- Reporter
- Statistics Norway
- Recieve Reports
- SME
- Reporter
- Statistics Norway
- Recieve Reports
- SME
- Reporter
- Statistics Norway
- Recieve Reports
- Statistical Survey
- C04. Adjust excpected turnover, income and VAT
- C08. Paying salary
- C19. Negotiation of debt and restructuring
- D04. Delete and/or dissolving
- CXX. B2B documentation and reporting
-
-
-
- Concepts
- Stakeholders
- 25 % av SME-er benytter skyløsninger for regnskap
- Velddeidge organisasjopner en viktig kundegruppe
- 3. Verdien av komplementære tjenester vil øke og verdian av subsitutter ofr prediksjon vil synke
- The subjects have an interest in how information concerning themselves is handled
- Hvordan ønsker dere å bli involvert? (poll)
- Sikkerhet
- Digitale handelsdokumenter: 2014: 99.000, 2019: 1.600.000
- Administrative burdens too high
- Assessment
- Intervju med SSB
- Need to improve the use of existing data for improving public andministation and services
- Trenger offentlig sektor å blande seg inn for å bidra til at SMB-ene får bedre kontroll over egne data og kan utnytte dem bedre? (poll)
- Råd: Kan være smart å veldge de områdene med størst mlig gevinst og minst innsats først
- High impact (for the invoice receiver), low cost due to public procurement already demands this. Finland may have more legacy than others.
- Verdien av ferske data. Kanskje skal etterhvert lånet ditt betjenes fra nettbanken.
- Hvordan får vi til økosystemet? (poll)
- Lack of quality decision data
- Felles nordisk seriøs-aktør liste
- Tilgang til data
- Store potensialer for forenklinger, men utfordringer
- Sikre kjeder
- individual national systems are gradually being replaced by SEPA-based implementations of ISO 20022.
- Machine-readable transaction-data is an asset
- Konkurransen ligger i front-end og apper
- Data is not exploited
- SSB er med
- Missing good handling of Payments - bank account statements
- Tillit: Det er ca. 1/3 av ressurser brukt på administrasjon sammenliknet med en ameriansk bedift
- Ulke tidspunkt for innrapporteirng osv. i ulike land. Innholdet det samme.
- Getting rid of the pdfs and paper
- Regnskap norge er positive - og støtter - den overordnede målsetningen med konseptet Nordic Smart Government
- Support the vision of standardized APIs, but it is hard work, and will take time
- De 40 bankene er ikke like ISO 20222
- Skjemaorienterte. Systemaenee er designet etter prosess for skjemaer. Brukerne forventer skjemaer. Adferdsendring. Eksempel Skatt og MVA
- globally recognised and used code lists are commonly in use, e.g. UNSPSC.
- Visma: Gevinsiter med XBRL. Ikke noe problem med overgang fra SAF-T
- 1. Økt anvendelse av prediksjoner i prosesser som allerede prediksjonsbasertee
- Hvilke aktører mangler i referansegruppen? (poll)
- Lower businesses transaction cost by standardizing data formats
- Largest cloud ERP-software vendor in Europe
- Missing good handling of Ordering system/purchase invoices
- What is needed? (DK?)
- Gevinsten ligger hos "feil aktør". Ikke alltid hos den som initierer orosiosess
- Auditing is a business where there is high cost by doing the wrong assessment. The support functions will be automated, not the auitor...
- 2. Prediksjoner vil anvedes i ehlt nye problemstilinger
- Delays/not realtime - mye ressurser brukes på avstemming. Kontrollen er manuell.
- Nordisk bank-ID
- Financial Invoice
- BEAst Supply Rental
- BIM
- UBL (one version)
- OIOUBL v.2.02
- Norsk Standard Kontoplan NS 4102
- Transaction standards
- CEN BII profile for public procurement
- NemHandel
- XBRL Global Ledger Taxonomy
- PEPPOL BIS 3
- ISO 20022 camt 053
- SAFT-T Accounting
- UBL
- FUT
- SWIFT
- e-order
- BEAst Invoicing
- EDIFACT
- BEAst Supply Material
- Norsk bokføringsstandard NBS 1 Sikring av regnskapsmateriale
- TeappsXML
- Finvoice
- Svefaktura
- Journal standards
- National standards for chart of accounts
- EHF v.2.0.8
- SIE
- SBR code set
- XBRL Global Ledger
- GS1 standards
- BEAst Emmission
- ISO 20022 (Universal Financial Industry Message Scheme)
- e-receipts
- BEAst Label
- UBL (?)
- BEAst Supply NeC
- EANCOM
- NemKonto
- International Financial Reporting Standards (IFRS)
- XBRL GLy
- e-invoice PEPPOL BIS Billing 3.0
- GTIN-12 (UPC)
- Norwegian regulation "Forskrift om bokføring"
- OIOXML
- Standard Import Export (SIE)
- CEN eInvoicing Semantic Data Model
- Bokføringsloven
- Forskrift om bokføring
- Account statement
- ISO 20022 - Bank to customer statement v02. Camd.053.001.02
- UNSPC
- iXBRL
- Financial statements standards
- SAFT-T Cash register
- UBL (incl. Tepps, EHF)
- Berlin Group NextGenPSD2 has worked on a detailed 'Access to Account (XS2A) Framework'
- ICEPRO
- Directive 2013/34/EU on the annual financial statements, consolidated financial statements and related reports of certain types of undertakings
- Gartner redefinerer ERP - enterprise business capabiities og økosystem
- ESMA: The European Single Electronic Format is the electronic reporting format in which issuers on EU regulated markets shall prepare their annual financial reports from 1 January 2020.
- EU Directive on Business Secrets
- Driver for change / concerns
- Directive 2015/2366/EU on payment services in the internal market (PSD2)
- Digitisition of transaction information
- The MyData-movement
- Platform blir viktigere enn features
- WTO: Agreement on Trade-Related Aspects of Intellectual Property Rights (TRIPS)
- Det strategiske bildet er så oppside-orientert uavhengig av business case
- Kunden eier sin egen Roadmap
- Directive 2014/55/EU on electronic invoicing in public procurement
- Konflikten i næringen går på at man bestiller noe annet enn det man får
- Reduce cost
- The VAT Directive permits electronic invoices and also allows invoices to be 10 stored outside of national borders, provided that the invoices are immediately accessible to tax authorities.
- Reduce transaction risk
- GDPR
- Improved decision support
- Premisstilretteleggende arbeid
- NSG vision and goals
- A new digital infrastructure for automated exchange of business data
- Transaksjonsdatabase
- Avoid manual processes
- Selvkjørende bedrifter
- Driv
- FI: Our utimatum goal is to get rid of e-reciepts in 2021
- digitisation and automation
- Standardize content for financial information
- Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken
- By standardizing we will capture more quality and real-life data with less manual work
- The Nordic Region as the best integrated region in the world
- Antall fakturafeil reduseres
- Reduce administrative burdens
- extract the full value embedded in data
- Skatterevisjoner og kvalitetsarbeid på lavt/detaljert transaksjonsnivå
- Increased adoption of eInvoices
- Increase innovation
- API first
- Adferdsendring
- share and utilise data more efficiently
- Adoption of eReceipts
- Reduserer telefonsamtaler
- SME's should be confident that the data they put into their ERP-systems will be available to themselves, but not available to others unless they consent or they have a clear legal basis
- Audit
- Morselskap
- Exchange of goods or services
- Requires that all transaction data are available digitally and structured, that the Government ensures the relevant regulation is co-ordinated and clear, and that the systems incorporates the regulation and learn from earlier transactions
- Konsern
- The level of digitisation and automation whitin the different Nordic Countries should not lead to cross-border business becoming more difficult
- Underkonsern
- Annual Account
- Konsernregnskap
- Data should be collected from the systems controlled by the SME, not from the raw transactions [Abelia]
- Datterselskap
- SME's must be able to use the data in other ways, share it with whom they choose themselves, move to other ERP-vendors, buy add-ons from other vendors
- Regnskapsår(-periode)
- The recording of a Transaction in an Account in the Accounting Records using Debits and Credits
- Account
- Soliditetsansvar
- Konsolidering
- Konsernforhold
- Better credit evaluation
- Transaksjonsdatabase (på plass)
- Expected outcomes
- Better credit valuations
- Standardisere informasjonsflyten
- Protect user data
- When I buy and sell goods and services I don't need to make any special arrangements when my trade-partners are in another Nordic country
- Use clearly defined, global semantics
- The Government gives me feedback and assures me when everything is OK
- Harmonisere på grensesnitt
- API-first
- Built to evolve
- Principles and constraints
- Enforce data portability
- Complience by design
- formålsbegrensning
- dataminimering
- Build on open standards
- Open banking
- I am in control of all the transaction and financial data of my business
- If someone offers me a better deal or improved service, migrating to new service providers for services like book-keeping, inventory, reporting etc is just as easy as changing operator for my cell phone
- I rarely perform manual steps related to inventory, book-keeping, bank-transactions, VAT- and other government reporting etc, unless I choose to verify the proposals from my systems
- I never manually enter information that is already maintained digitally by the producers, vendors or the government [TOOP]
- dataportabilitet
- Favor imperfect existing standards over perfect custom standards
- Business Transaction Documents should be compatible with Peppol eDelivery network
- 1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics]
- Best practice for secure access with APIs
- Financial raw data must be available for lookup [variants 1-8] (copy)
- This is large and long term. Can you give any examples on the type of MVPs you think is possible to make?
- Er det ikke nok å prøve å løse dette i Norge? Hvorfor gjøre det vanskeligere ved å prøve å få det til i hele Norden?
- Seriøse aktørers møte med
- Story
- How is NSG collaborating with ERP-system vendors?
- 1.1.3. Data will be collected from qualified electronic financial documents [i.e. Orders must be digitally]
- What are the various representations of (annunal) accounts – sematnics (SAF-T, XBRL, Altinn)?
- Business Transaction Documents should implment document specifications compatible with Peppol BIS
- Arbeides det parallelt med lovverk knyttet til finansiering og forsikring? Nordisk samarbeid vil åpne for enklere bruk av de andre lands leverandører.
- Who will do the certification of ERP-sytems and how can it be done?
- 1.1.1 Data will be collected from qualified electronic financial documents [i.e. Invoices must be retrieved digitally]
- API or message access
- If so, who shall certify the accouting systems, and must is be verified for all countries?
- Financial reports must be aggregated over dimentions like products, clients, suppliers, countries, locations, qualities, quantities.
- Capture product information
- 1.3.1 documents are categorized with its own document type e.g. sales invoice, purchase invoice, receipt, bank account statement, bookkeeping entry, warehouse entry, cash sales etc.
- API must support XBRL GL taxonomy
- Er Smart Government feil navn? Burde det hete Smart Business eller Smart Society?
- Financial reports must be available for lookup [use case 6] (copy)
- Will there development of a seperate portal where the small businesses themselves without having an agreement with a costly ERP-vendoer?
- Ska det på sikt bli tale om et felles nordisk bedriftsregister som felles sentral nøkkel for sikker pålogging ?
- Varekoder, grupper for statistikk og innsats. Eksempel SKD: gatekjøkken med 100 flatskjermer
- Strong enforcement of data integrity
- Hvem tar kostnadene for oppetid og prosessorkraft for å tilgjengeliggjøre dataene via API-er?
- Standardized and detailed APIs for bookkeeping transactions creates an opportunity for extracting details and aggregated to business partners, e.g. Banks
- Tilgjengelighet - sikre at regnskapsmaterialet er tilgjengelig for autoriserte personer ved behov
- Is it possible to have a common way of structuring data so that the questions and answers can be standardized?
- Requirements on businesses to have a certified accouning system when established?
- Can we forsee standardized product information - there are requiremnts on VAT levels, but nothing similar when it comes to product information?
- 1.1.2 Data will be collected from qualified electronic financial documents [i.e. Bank account statement must be digitally]
- Discovery - (Dynamic) addressing for APIs (aka capability registry)
- Epic
- Kan dere bygge inn insitamenter for å fremme sirkulær økonomi?
- Financial reports must be available for lookup [use case 6]
- How does EU relate to the questions here?
- Need systems that can collect information auttomatic
- Hva blir altinn’s rolle inn mot Smart Government
- Prosjektet trodde i en initell fase på det å etablere en nasjonal, sentralisert datamodell, og har siden gått i retning av en mer distrbiuert modell med uthenting av data fra ERP systemene. Innebærer denne endringen vesentlige endriger i tidsplanen for implementering, altså for eksempel at implementeringsplanen fra fremskyndes
- What rights and duties have the difference actors to the information of the business ("data ownership")
- What can the business avoid sharing?
- What kind of queries/API-s shall be possible - REST, GraphQL, others?
- The information must be represented in a generic and system-independent way to record all of the details in any kind of ledger and bookkeeping
- Acccess to account
- På hvilken måde skal data flyttes mellem lande og internt ? Sikkerhed? Cyberangreb ??
- Data sharing controlled by the data originator
- Is the differences in standards accross the Nordics and sectors considered a challenge?
- Kan man forenkle ved å sikre at personopplysninger kontrolleres av personen (data-subjektet)?
- Hva du pålegges å ta vare på i bokføringen
- Hvordan legge til rette for dataminimering – forskjell på behov knyttet til ”kreditt basert på utestående fakturaer” og ”ettersyn”
- API must be able to declare a version (and format standard used?) for the taxonomy used
- Can SAF-T be used for extracting transactions? Can we build on this with small changes (in the direction of XBRL)?
- Holistic management on authorization: Unauthorized (open data), users consent (B2B), regualtive access (B2G)?
- Acting in real-time and up-front
- Has blockchain been evaluated?
- Addressing - The endpoint(s) of the organisation’s ERP-system must be known
- How can you ensure that you cover the needs of the small and medium enterprises?
- 1.3.2 all needed information should be collected from the actual documents
- Common solution (SBB) for authorization – for example Altinn Autorization in Norway?
- Financial raw data must be available for lookup [variants 1-8]
- Standard audit file - CashRegister (SAF-C)
- Standard audit file - Tax (SAF-T)
- How can the process with registration of the business be changed in requirering the business to have a certified accounting systems?
- 1.1.4. Data will be collected from qualified electronic financial documents [i.e. Receipts must be retrieved digitally]
- Do we have sufficient access to public reference data (Business Registry, Product codes, ... others)?
- Can we forsee a standardizaed logging on use/data sharing?
- Will we have sufficeint actors on board on (cloud) infrastructure in 2025 that makes services realistic ?
- Hvordan vil dere sikre at etater samordner seg slik at ikke næringslivet må forholde seg til flere ulike gode initiativ?
- Check the validity of e-Receipts and e-Invoices - to prevent fraud. Both fraud in creating false Invoices, and receipts - and also prevent using them more than once to verify expenses.
- Common representation according to XBRL GL - as a concept scheme?
- Do we have sufficient documents on the input side (e-invoices)? Do we have standardized e-ordres?
- Estonia, Brazil, (Finland)
- Revisorforeningen (NO)
- Business systems
- Lånekassen
- Sparebank 1
- Stakeholder
- Ability/means to react on information
- Self determination
- 0,6 mrd euro / year
- Control
- Information
- 4200 brukere
- 7 mrd euro / year
- Value
-
-
-
-
(Order processing - Released (purchase) order)
-
(Managing invoices - Customer invoice)
-
(Fullfillment i.e. delivery and receipt of goods and services - Released (purchase) order)
-
(Capture/receive/review customers' purchase order - Submitted order (purchase order))
-
(Catalogue of products and services - Catalog (NACE, ...))
-
(Invoice management - Invoice)
-
(Provide sales receipt - Receipt)
-
(Accepting Invoice - Purchase invoice/supplier invoice)
-
(Analysis to create added value to the transaction - Chart of accounts)
-
(Accounting service provider - Standard chart of accounts (code list))
-
(Order processing - Submitted order (purchase order))
-
(Receive receipt - Receipt)
-
(Cash sales reporting - Journal)
-
(Receive order confirmation - Fullfilled order (sales order))
-
(Fullfillment i.e. delivery and receipt of goods and services - Fullfilled order (sales order))
-
(Ledger interface - General Ledger)
-
(Create and send order - (Purchase) Order)
-
(Invoice Approval and Payment - Invoice)
-
(Sales (order handling) and Marketing function - Released (purchase) order)
-
(Create invoice - Invoice)
-
(Create order for service or product - (Purchase) Order)
-
(Sales (order handling) and Marketing function - Submitted order (purchase order))
-
(Shipping/delivery - Shipping confirmation)
-
(Recieve order - (Purchase) Order)
-
(Cash sales - Journal)
-
(Receive Shipping Confirmation - Shipping confirmation)
-
(Receive invoice - Customer invoice)
-
(Capture/receive/review customers' purchase order - Submitted order (purchase order))
-
(e-Invoce interface - e-invoice)
-
(Industry assosiation - SME trade partner)
-
(Release - Application Service)
-
(Accounting - Purchase ledger)
-
(Sales (order handling) and Marketing function - Managing invoices)
-
(Accounting - Sales ledger)
-
(Accounting - General ledger)
-
(Accountant organization - Acountant)
-
(Roadmap - Capability Increment)
-
(SME - Employee)
-
(Auditor organization - Auditor)
-
(SME - Bookkeeper)
-
(SME - Board)
-
(Industry assosiation - SME)
-
(Industry assosiation - SME business partner)
-
(Authorization/power of mandates SBB - 5.1 Provide and maintain confidentiality)
-
(Regulators - 4.2 Compliance confirmation services)
-
(SME - Tax filing)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Product catalog lookup)
-
(Fraud detection - Check VAT registration)
-
(Reporting and analytics - Deliver financial report to government)
-
(Bank - Bank transaction)
-
(Business systems - 2.2. Open accounting (Legal access to real time financial transactions in business systems))
-
(Users consent SBB - User consent for B2B sharing)
-
(ERP - Cash sales reporting)
-
(Information services provider - Benchmarking)
-
(Business systems - 2.2. Manage change and deviations (was: Correctness incl. error detection and correction))
-
(Information services provider - Marketing services)
-
(Standardisation organisations - 1.4 Standardisation of eReceipts)
-
(Inventory manager - Managing inventory)
-
(Visma - Business analytics)
-
(Adressing SBB - 2.2. Open accounting (Legal access to real time financial transactions in business systems))
-
(SME - Order processing)
-
(SME - Financial Management)
-
(Business systems - 3.4 High avaliability )
-
(Adressing SBB - 3.3 Adressing)
-
(Collaboration with value added services - Identifyuser (authentcation))
-
(Business Actor - Business Service)
-
(SME - Annual Reporting)
-
(ERP - Payment)
-
(ERP - Sales and order management)
-
(Information services provider - Marketing services)
-
(Industry assosiation - Provide political influence)
-
(Credit provider (bank) - Other business opportunities)
-
(SME - Report on specific keywords across invoices)
-
(Authentication SBB - 5.1 Provide and maintain confidentiality)
-
(SME - Store transaction)
-
(Fraud detection - Check seriousness)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Pay invoice)
-
(Business systems - Authentication)
-
(Authorization/power of mandates SBB - Authorisation and access control)
-
(Business systems - Standardized access (APIs))
-
(Born digital - Register company API)
-
(Credit provider (bank) - Dynamic financing)
-
(Bank - Dashboard and Progonosis)
-
(SME - Report summarizing receipts pertaining to specific products)
-
(Acountant - Finance and Accounting)
-
(Business systems - 2.3. Common representation of transactions (semantics))
-
(Collaboration with value added services - Access transactions)
-
(SME - VAT reporting)
-
(SME trade partner - Getting good trading terms by showing solvency)
-
(Auditor - Tax Auditing)
-
(Authentication SBB - Authentication)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Receive invoice)
-
(SME - Exchanging business documents)
-
(Ledger interface - Ledger details lookup)
-
(Business Role - Business Service)
-
(Reporting and analytics - Access data for analytics)
-
(Statistics agency - Statistics)
-
(Collaboration with value added services - Identify rights (authorization))
-
(Information services provider - Pricing statistics)
-
(SME - Inventory management)
-
(SME in financial sector - Periodic Financial reporting)
-
(Bookkeeper - Bookkeeping)
-
(Born digital - Register accounting system (SMP))
-
(Information services provider - Credit rating)
-
(SME - Sales (order handling) and Marketing function)
-
(Insurance agency - Insurance)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Receive order)
-
(ERP - Asset management)
-
(Investor - Investors evaluation)
-
(Infrastructure for document exchange SBB - 5.2 Keeping the data safe (integrity and ownership))
-
(SME - Report on sales or purchases for product groups)
-
(Credit Insurance agency - Insuring credit)
-
(SME - Stock management)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Send invoice)
-
(ERP - Invoice management)
-
(Fraud detection - Check business registration)
-
(Business systems - 1.3 Product information - avaliable)
-
(Business systems - 1.1 Adoption of digital business documents)
-
(Business Actor - Business Role)
-
(SME - Inventory management)
-
(Business systems - 7.2 Provide anonymised access to aggregated data)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Receive payment)
-
(Auditor - Financial service offering)
-
(e-Invoce interface - e-Invoice)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Create and send order)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Receive order confirmation)
-
(Business systems - 1.2 Adoption of digital product and service information)
-
(Visma - Accounting)
-
(SME in financial sector - Other reporting)
-
(SME - Portability)
-
(ERP - Product information management)
-
(Visma - Bookkeeping)
-
(Users consent SBB - 5.1 Provide and maintain confidentiality)
-
(Acountant - Making adjustments)
-
(SME - Report on the price levels of products)
-
(Analytics software - Data analysis)
-
(ERP - Accounting)
-
(Fraud detection - Validate bank account)
-
(Standardisation organisations - 2.3. Common representation of transactions (semantics))
-
(Board - Making adjustments)
-
(Sparebanken Vest - Bank)
-
(Fraud detection - Check known fraudent actors)
-
(SME - Tax Audit)
-
(SME - Cash sales)
-
(Regulators - 1.3 Product information - avaliable)
-
(Standardisation organisations - 1.1 Adoption of digital business documents)
-
(ERP - Inventory management)
-
(Cash register - Cash sales)
-
(Payment provider (Bank, Credit Card company or broker) - Customer to bank payment)
-
(Credit provider (bank) - Giving credit)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Send order confirmation)
-
(Reporting and analytics - Deliver non-financial report to government)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Send receipt from POS)
-
(Regulators - 1.2 Adoption of digital product and service information)
-
(Credit provider (bank) - Credit lending evaluation)
-
(Resource - Capability)
-
(Business systems - 5.1 Provide and maintain confidentiality)
-
(Infrastructure for document exchange SBB - Encryption)
-
(Bank - Paying)
-
(Resource (future environment) - Capability)
-
(Fraud detection - Integrity check of business document)
-
(Cash sales report - Cash sales report)
-
(SME - Custom reporting (on request for data capture by Statistics))
-
(Ledger interface - Ledger aggregation report)
-
(Vendor/Supplier (Seller) - Purchasing)
-
(Visma - Inventory Management)
-
(Business systems - User consent for B2B sharing)
-
(Regulators - 1.1 Adoption of digital business documents)
-
(SME - Summaries of invoices pertaining specific products)
-
(Credit provider (bank) - Credit Lending Evaluation)
-
(SME (copy) - Store transaction (copy))
-
(Business systems - 2.1 Provide technical access points to detailed transaction data)
-
(Business partners purchase-to-pay and order-to-cash (rulebook) - Receive receipt)
-
(Business systems - Business management)
-
(SME - Managing invoices)
-
(Collaboration with value added services - Access historical transactions)
-
(Tax authoritiy - Tax Audit)
-
(Business systems - Authorisation and access control)
-
(Big data anlytics provider - Data analysis)
-
(25 % av SME-er benytter skyløsninger for regnskap - SMEs)
-
(ISO 20022 camt 053 - Bank statement receiving service)
-
(OIOUBL v.2.02 - Catalogue Pricing Update)
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Invoicing)
-
(SSB er med - Statistisk sentralbyrå (NO))
-
(Entry - General Ledger)
-
(0,6 mrd euro / year - Public administrations)
-
(SMEs - Reduce transaction risk)
-
(Acccess to account - Directive 2015/2366/EU on payment services in the internal market (PSD2))
-
(OIOUBL v.2.02 - Catalogue Request)
-
(OIOUBL v.2.02 - (Purchase) Order)
-
(individual national systems are gradually being replaced by SEPA-based implementations of ISO 20022. - ISO 20022 (Universal Financial Industry Message Scheme))
-
(UBL - PEPPOL BIS 3)
-
(Stefan Ellstrøm (SE) - WP3: Information exchange)
-
(A new digital infrastructure for automated exchange of business data - Avoid manual processes)
-
(GDPR - The subjects have an interest in how information concerning themselves is handled)
-
(OIOUBL v.2.02 - Catalogue Deletion)
-
(The MyData-movement - The subjects have an interest in how information concerning themselves is handled)
-
(OIOUBL v.2.02 - Order Change)
-
related to
(Transaction - Business document)
-
(XBRL Global Ledger - )
-
(UBL (?) - )
-
belongs to
(Set of transactions - Company)
-
(Complience by design - Sikre kjeder)
-
(NSG vision and goals - Driver for change / concerns)
-
standardization
(e-invoice - Core invoice)
-
(Directive 2015/2366/EU on payment services in the internal market (PSD2) - Danish Saxo Bank, that opened up for their APIs in September 201510)
-
(Know your client/orgaization (KYC) - Audit)
-
(Need systems that can collect information auttomatic - BEAst (bygggbransjens elektroniske affãrstandard))
-
(Verdien av ferske data. Kanskje skal etterhvert lånet ditt betjenes fra nettbanken. - Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken)
-
(Better credit evaluation - Financial sector)
-
( - SIE)
-
(Accounting - Visma)
-
(DNB - Puls)
-
(Directive 2015/2366/EU on payment services in the internal market (PSD2) - Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken)
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Label)
-
(OIOUBL v.2.02 - Order Response Simple aka Order Acknowledgement, PO Response)
-
(The recording of a Transaction in an Account in the Accounting Records using Debits and Credits - Entry)
-
proved by
(Transaction - Proof of transaction)
-
(Support the vision of standardized APIs, but it is hard work, and will take time - Visma)
-
(EU Directive on Business Secrets - The subjects have an interest in how information concerning themselves is handled)
-
(NCC - BEAst Supply Material)
-
(Bits - Kontoopplysninger)
-
(GS1 standards - EANCOM)
-
(National standards for chart of accounts - Chart of accounts)
-
(Norsk bokføringsstandard NBS 1 Sikring av regnskapsmateriale - Tilgjengelighet - sikre at regnskapsmaterialet er tilgjengelig for autoriserte personer ved behov)
-
(Read entries - XBRL Global Ledger)
-
(UBL (incl. Tepps, EHF) - Purchasing management system)
-
(Audit panning and strategy - Audit)
-
(Prediction Machines (Book) - 3. Verdien av komplementære tjenester vil øke og verdian av subsitutter ofr prediksjon vil synke)
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Supply Material)
-
(Nordic API gateway - Banks)
-
(Reduce cost - SMEs)
-
(Sirius - Skatteetaten (NO))
-
(Stakeholder - Driver for change / concerns)
-
(Inventory management - Sales and order management)
-
reference a voucher
(Proof of transaction - Journal)
-
(dataportabilitet - GDPR)
-
(Puls - Banks)
-
(Roger Schjerva - IKT-norge (NO))
-
(Countries: Portugal, Nederland, Litauen, Frankrike, Spania, Luxemburg, EU - SAF-T (Financial))
-
(The subjects have an interest in how information concerning themselves is handled - I rarely perform manual steps related to inventory, book-keeping, bank-transactions, VAT- and other government reporting etc, unless I choose to verify the proposals from my systems)
-
(I am in control of all the transaction and financial data of my business - SME's must be able to use the data in other ways, share it with whom they choose themselves, move to other ERP-vendors, buy add-ons from other vendors)
-
(A new digital infrastructure for automated exchange of business data - share and utilise data more efficiently)
-
(Regnskap Norge (NO) - Regnskap norge er positive - og støtter - den overordnede målsetningen med konseptet Nordic Smart Government)
-
(3550 kNOK NO (0 kNOK own contribution + 3550 kNOK NI contribution) - WP3: Information exchange)
-
(Bank statement - )
-
( - e-receipts)
-
(Sales and order management - Sales ledger)
-
(UBL - OIOUBL v.2.02)
-
(What is needed? (DK?) - Visma)
-
(OIOUBL v.2.02 - Credit Note)
-
(OIOUBL v.2.02 - Specification Update)
-
(iXBRL - ESMA: The European Single Electronic Format is the electronic reporting format in which issuers on EU regulated markets shall prepare their annual financial reports from 1 January 2020.)
-
(Standard audit file - CashRegister (SAF-C) - Skatteetaten (NO))
-
(OIOUBL v.2.02 - Order Cancellation)
-
(formålsbegrensning - GDPR)
-
(Intervju med SSB - Statistisk sentralbyrå (NO))
-
(Payment - Purchase ledger)
-
(1.1.1 Compliance with CEN semantic model EN-16931 for invoices - High impact (for the invoice receiver), low cost due to public procurement already demands this. Finland may have more legacy than others.)
-
(API first - Visma)
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Supply Rental)
-
(SMEs - Better credit valuations)
-
manages
(GS1 - GS1 standards)
-
(NO: 766 kNOK (167 kNOK own contribution + 600 kNOK NI contribution) - WP1: Interoperability and governance)
-
(OIOUBL v.2.02 - Reminder)
-
listed in
(Entry - Journal)
-
(OIOUBL v.2.02 - Invoice)
-
(A new digital infrastructure for automated exchange of business data - extract the full value embedded in data)
-
is part of
(Transaction - Set of transactions)
-
(dataminimering - GDPR)
-
(Regnskap Norge (NO) - Sikkerhet)
-
(Account - General Ledger)
-
(SIE - )
-
(A new digital infrastructure for automated exchange of business data - digitisation and automation)
-
(Eilina Koskentalo (FI) - WP3: Information exchange)
-
(Deling av mikrodata - Statistisk sentralbyrå (NO))
-
(XBRL GLy - )
-
(Thomas Flank (SE) - WP2: Automated flow of data)
-
(Selvkjørende bedrifter - Tillit: Det er ca. 1/3 av ressurser brukt på administrasjon sammenliknet med en ameriansk bedift)
-
(Standard audit file - Tax (SAF-T) - Skatteetaten (NO))
-
( - Standard audit file - Tax (SAF-T))
-
(Sparebanken Vest - Buffer)
-
(OIOUBL v.2.02 - Payment transactions aka Statements of Account)
-
(Big data anlytics provider - Analytics software)
-
(Public administrations - Need to improve the use of existing data for improving public andministation and services)
-
(Bank transaction - ISO 20022 standard)
-
(Buffer - Banks)
-
(ERP vendor - ERP)
-
(Transaction standards - Business operations)
-
(OIOUBL v.2.02 - NemHandel)
-
(Largest cloud ERP-software vendor in Europe - Visma)
-
(OIOUBL v.2.02 - Application Response)
-
(Business registry - Business registry)
-
(516 kNOK FI cont. (167 kNOK own contribution + 350 kNOK NI contribution) - WP1: Interoperability and governance)
-
(Entry - Product or Service)
-
(OIOUBL v.2.02 - Catalogue Item)
-
(Analysis: Evaluate and asses the impact of evidence - Audit)
-
(National standards for chart of accounts - Standard chart of accounts (code list))
-
defined by
(Directive 2015/2366/EU on payment services in the internal market (PSD2) - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Store potensialer for forenklinger, men utfordringer - Revisorforeningen (NO))
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Supply NeC)
-
(Varekoder, grupper for statistikk og innsats. Eksempel SKD: gatekjøkken med 100 flatskjermer - Skatteetaten (NO))
-
(Steinar Skagemo (NO) - WP1: Interoperability and governance)
-
(Financial statements standards - )
-
(Adoption of eReceipts - 1.1 Adoption of digital business documents)
-
(DK: 2.367 kNOK (167 kNOK own contribution + 2.200 kNOK NI contribution) - WP1: Interoperability and governance)
-
(Machine-readable transaction-data is an asset - I never manually enter information that is already maintained digitally by the producers, vendors or the government [TOOP] )
-
(SIE - )
-
(Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken - 4200 brukere)
-
(Sikre kjeder - Skatteetaten (NO))
-
(3.017 kNOK SE cont. (167 kNOK own contribution + 2.850 kNOK NI contribution) - WP1: Interoperability and governance)
-
(Assessment - Capability)
-
(Sparebank 1 - Driv)
-
(Directive 2015/2366/EU on payment services in the internal market (PSD2) - Open banking)
-
(UBL - CEN BII profile for public procurement)
-
(OIOUBL v.2.02 - Order Response aka Order Acknowledgement, PO Response)
-
(e-invoice - )
-
(Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken - Lånekassen)
-
(UBL (one version) - Purchasing management system)
-
(The Nordic Region as the best integrated region in the world - When I buy and sell goods and services I don't need to make any special arrangements when my trade-partners are in another Nordic country)
-
(GS1 - Standardiseringsutvalget for Norsk Dagligvarebransje)
-
(Prediction Machines (Book) - 2. Prediksjoner vil anvedes i ehlt nye problemstilinger)
-
(Fieldwork: collect information and optain evidence - Audit)
-
replaces
(EDIFACT - ISO 20022 (Universal Financial Industry Message Scheme))
-
(BEAst (bygggbransjens elektroniske affãrstandard) - BEAst Emmission)
-
(Increased adoption of eInvoices - 1.1 Adoption of digital business documents)
-
(ISO 20022 standard - Kontoopplysninger)
-
(e-order - )
-
(Standard audit file - Tax (SAF-T) - )
-
(By standardizing we will capture more quality and real-life data with less manual work - e-invoice)
-
(XBRL Global Ledger - Update entries)
-
(Visma - Skjemaorienterte. Systemaenee er designet etter prosess for skjemaer. Brukerne forventer skjemaer. Adferdsendring. Eksempel Skatt og MVA)
-
(David Norheim (NO) - WP3: Information exchange)
-
(I am in control of all the transaction and financial data of my business - SME's should be confident that the data they put into their ERP-systems will be available to themselves, but not available to others unless they consent or they have a clear legal basis)
-
(I am in control of all the transaction and financial data of my business - Data should be collected from the systems controlled by the SME, not from the raw transactions [Abelia])
-
(Improved decision support - SMEs)
-
(Standard audit file - Tax (SAF-T) - )
-
(Adferdsendring - Skjemaorienterte. Systemaenee er designet etter prosess for skjemaer. Brukerne forventer skjemaer. Adferdsendring. Eksempel Skatt og MVA)
-
(Financial statements standards - )
-
(UBL (one version) - Sales management system / order portal)
-
(I rarely perform manual steps related to inventory, book-keeping, bank-transactions, VAT- and other government reporting etc, unless I choose to verify the proposals from my systems - Requires that all transaction data are available digitally and structured, that the Government ensures the relevant regulation is co-ordinated and clear, and that the systems incorporates the regulation and learn from earlier transactions)
-
(Financial statements standards - Tax Auditing)
-
(Missing good handling of Ordering system/purchase invoices - A purchasing system manages the entire acquisition process, from requisition, to purchase order, to product receipt, to payment. )
-
(Private actors - 7 mrd euro / year)
-
reference a voucher
(General Ledger - Proof of transaction)
-
(Svefaktura - UBL)
-
(Exchange of goods or services - Transaction)
-
filed on
(Entry - Account)
-
(The subjects have an interest in how information concerning themselves is handled - I am in control of all the transaction and financial data of my business)
-
(XBRL GLy - )
-
(XBRL-GL - Estonia, Brazil, (Finland))
-
(Transaction - )
-
(BEAst Supply Material - Virke)
-
(e-order - )
-
(Bokføringsloven - Forskrift om bokføring)
-
(Hans Christian Ellefsen - Regnskap Norge (NO))
-
(Kai Morten Hagen - Revisorforeningen (NO))
-
(Journal standards - )
-
(The subjects have an interest in how information concerning themselves is handled - If someone offers me a better deal or improved service, migrating to new service providers for services like book-keeping, inventory, reporting etc is just as easy as changing operator for my cell phone)
-
(Standard audit file - Tax (SAF-T) - )
-
(GS1 standards - GTIN-12 (UPC))
-
(When I buy and sell goods and services I don't need to make any special arrangements when my trade-partners are in another Nordic country - The level of digitisation and automation whitin the different Nordic Countries should not lead to cross-border business becoming more difficult)
-
(Digitisition of transaction information - Machine-readable transaction-data is an asset)
-
( - XBRL Global Ledger)
-
(XBRL Global Ledger - Create entries)
-
(Undisclosed information - WTO: Agreement on Trade-Related Aspects of Intellectual Property Rights (TRIPS) )
-
(Berlin Group NextGenPSD2 has worked on a detailed 'Access to Account (XS2A) Framework' - Lånekassen: Kundene vil bli vant med å se egne kontoer med innskudd og gjeld i den kanalen de foretreekker. Etterhvert vil de også forvente å finne Lånkassen der. Kunden er opptat av å ha oversikt over egen økonomi, og kunne tenke seg å se studielånet sitt i nettbanken)
-
reference
(Proof of transaction - Entry)
-
(Prediction Machines (Book) - 1. Økt anvendelse av prediksjoner i prosesser som allerede prediksjonsbasertee)
-
(SSB - Statistisk sentralbyrå (NO))
-
(Data is not exploited - Information brokers)
-
(OIOUBL v.2.02 - Catalogue)
-
(Course of Action - National Solution Building Blocks (SBBs) should provide authentication of a company)
-
(Course of Action - Business systems should have the ability to restrict access to their data, e.g. through an API-manager.)
-
(Iceland - ICEPRO)
-
(Invoice - price)
-
(5.1 Provide and maintain confidentiality - User consent for B2B sharing)
-
(Payment instructions - Credit transfer)
-
(Information delivery - Data discovery)
-
(K. Standardize content of business system transactional data (semantic interoperability) - 5.1.3 Provide the mapping between national selected transaction standard and the common reference data model for transactions)
-
(E. Adoption of structured product information - 1.2.6 Product catalogues should be used with standardized product codes to provide access to machine readable descriptions of product information that can be used thoughout the supply chain. Product codes must be mapped to general codes; UNSPC and Customs code.)
-
(Ecosystem - 6. Governance)
-
(High level technical questions - Common solution (SBB) for authorization – for example Altinn Autorization in Norway?)
-
(H. Integrity by not having to exchange documents - 1.3.4 Legal changes to remove the need to store and archive copies of vouchers)
-
(Norway - EANCOM)
-
(WP2 Other - Check the validity of e-Receipts and e-Invoices - to prevent fraud. Both fraud in creating false Invoices, and receipts - and also prevent using them more than once to verify expenses. )
-
(Ecosystem - Business management)
-
(1. Use of digital business documents - 1.3 Product information - avaliable)
-
(Procurement - Purchase planning)
-
(Customer Relationship Management (CRM) Function - Sale force management)
-
(Tendering (pre-award) - Tendering)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them)
-
(High level technical questions - Best practice for secure access with APIs)
-
(4. Compliance - 4.2 Compliance confirmation services)
-
(1. Use of digital business documents - 1.1 Adoption of eInvoices)
-
(Sweden - Standard Import Export (SIE))
-
(1. Use of digital business documents - 1.3 Adoption of eReceipts)
-
(High level semantic questions - What are the various representations of (annunal) accounts – sematnics (SAF-T, XBRL, Altinn)?)
-
(D. Adoption of eOrders, eCatalogs - 1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering))
-
(High level legal questions - Holistic management on authorization: Unauthorized (open data), users consent (B2B), regualtive access (B2G)? )
-
(WP1 User principles - I am in control of all the transaction and financial data of my business)
-
(Finance and Accounting - Account payables)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.6 Create incentives in when governments require payments e.g. extending the payment deadline for businesses that can receive an eInvoice)
-
(Invoice line - Line VAT information)
-
(Product information management - Enrich)
-
(Motivation (Documented needs and User principle document) - Principles and constraints)
-
(E. Adoption of structured product information - 1.2.4 Enforce the use of product ans service codes in the supply chain. )
-
(WP2 Common Nordic Rulebook - Capture product information)
-
(Busiiness document API - OrderAPI)
-
(High level legal questions - What can the business avoid sharing?)
-
((Purchase) Order - Cost center attribution)
-
(WP1 User principles - I never manually enter information that is already maintained digitally by the producers, vendors or the government [TOOP] )
-
(High level legal questions - What rights and duties have the difference actors to the information of the business ("data ownership"))
-
(Data governance - Handle life cycle of transactions (versions))
-
(Selling - Recieve order)
-
(WP1 Desired attributes - Strong enforcement of data integrity)
-
(High level semantic questions - Can we forsee standardized product information - there are requiremnts on VAT levels, but nothing similar when it comes to product information?)
-
(Government - Information exchange )
-
(Dokumentasjon av bokførte opplysninger - Dokumentasjon av andre regnskapsmessige disposisjoner)
-
(Financial accounting - General accounting)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Lønnsspesifikasjon)
-
(D. Adoption of eOrders, eCatalogs - 1.1.20 Implement in OpenPeppol BIS eCatalog for Business systems)
-
(Digital shoebox (reference implementation) - Business transactions)
-
(Public procurement - Call-off on established contracts)
-
(Inventory Management - Inventory count)
-
(5. Data protection - 5.3 Maintaining availability)
-
(e-Procurement - e-Notification)
-
(Customer Relationship Management (CRM) Function - Account and contact management)
-
(5. Data protection - 4.3 Maintain avaliability)
-
(Finance and Accounting - Billing)
-
(Public procurement - Fullfillment i.e. delivery and receipt of goods and services)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Andre spesifikasjoner)
-
(Business support and reguslations - Business and industry development)
-
(Procurement - Accounts Payables)
-
(Core invoice - Document level charges)
-
(Financial Management - Payment validation)
-
(Product information management - Publish)
-
(e-Procurement - e-Catalogue)
-
(Pliktig regnskapsrapportering - Årsregnskap)
-
(Customer Relationship Management (CRM) Function - Marketing)
-
(Quality capabilities - Encryption)
-
(Information exchange - Technology management)
-
(Financial accounting - Accounts payable)
-
(Inventory management - Stock utilization reporting)
-
(Course of Action - 4.1.1 National Solution Building Blocks (SBBs) should provide authorization by power of mandates )
-
(4. Compliance - 4.3 Common representation of businesses (semantics))
-
(High level legal questions - Requirements on businesses to have a certified accouning system when established?)
-
(J1. Enable standarized access to business systems transactional data (technical interoperability) - 2.1.2 Establish a (standardized) role based authorization service for the businesses to grant access to different parties to read/write data (B2B, …))
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.9 Making eInvoicing mandatory in the Nordics)
-
(Denmark - OIOUBL v.2.02)
-
(Data management - Data quality)
-
(Core invoice - Invoice line)
-
(Business support and reguslations - Business and industry regulation)
-
(Human Resources - Time management)
-
(Ecosystem - 1. Use of digital business documents)
-
(EU - CEN BII profile for public procurement)
-
(Sales (order handling) and Marketing function - Shipping/delivery)
-
(I. Trust services that enable and increase secure business - 1.3.7 Access to a service that checks the “seriousness” of a company, e.g. are taxes paid etc.)
-
(I. Trust services that enable and increase secure business - 1.3.8 Access to a service that checks that trading partners really exist before sending documents (is registered in business registries))
-
(Dokumentasjon av bokførte opplysninger - Betalingsdokumentasjon)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them)
-
(1. Use of digital business documents - 1.3 VAT automation)
-
(Procurement - Purchase)
-
(Quality capabilities - Standardized access (APIs))
-
(Ecosystem - 4. Compliance)
-
(Quality capabilities - 5.2 Keeping the data safe (integrity and ownership))
-
(Purchasing (post award) - Fullfillment i.e. delivery and receipt of goods and services)
-
(Capability area - Capability)
-
(Quality capabilities - Authentication)
-
(Financial accounting - Accounts recievable and revenue)
-
(C. Adoption of eReceipts - 1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x))
-
((Purchase) Order - Organizational info)
-
(Core invoice - Seller)
-
(C. Adoption of eReceipts - 1.1.10 Standardize the content of eReceipts)
-
(Other requirements- not put into documents - API must be able to declare a version (and format standard used?) for the taxonomy used)
-
(G. Integrity in the business document exchange - 1.3.1 Access to a digital business documents validation services that check that necessary contents are present and used codes etc. are correct)
-
(E. Adoption of structured product information - 1.2.2 Discover product information/codes and access services providing additional information about the product.)
-
(Human resource operations - Employee administration)
-
(WP1 Recommendation of standards - Business Transaction Documents should implment document specifications compatible with Peppol BIS)
-
(Ecosystem - Invoice - seller sends an invoice)
-
(Ecosystem - 7. Analytics)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Leverandørspesifikasjon)
-
(Inventory management - Stock transfer out)
-
(Ecosystem - Human resource operations)
-
(Procurement - Pay)
-
(5. Data protection - 5.2 Keeping the data safe (integrity and ownership))
-
(Receipt - company name)
-
(Core invoice - Sellers Tax representative party)
-
(High level technical questions - API or message access)
-
(Data security - 5.1 Provide and maintain confidentiality)
-
(High level semantic questions - Do we have sufficient documents on the input side (e-invoices)? Do we have standardized e-ordres? )
-
(High level organizational questions - How can the process with registration of the business be changed in requirering the business to have a certified accounting systems?)
-
(High level technical questions - Will we have sufficeint actors on board on (cloud) infrastructure in 2025 that makes services realistic ?)
-
(ISO 20022 standard - ISO 20022 (Universal Financial Industry Message Scheme))
-
(5.1 Provide and maintain confidentiality - User consent for B2B sharing)
-
(D. Adoption of eOrders, eCatalogs - 1.2.2 Discover product information/codes and access services providing additional information about the product.)
-
((Purchase) Order - Quantities of goods and services)
-
(Invoice - payment)
-
(Denmark - EANCOM)
-
(Core invoice - Preceeding invoice reference)
-
(Transaction processing - 1.2 Adoption of digital product and service information)
-
(Bundle (copy) - Business systems should provide mechanisms that ensure high availability of APIs (copy))
-
(Business management - 7.2 Provide anonymised access to aggregated data)
-
(High level semantic questions - Is it possible to have a common way of structuring data so that the questions and answers can be standardized? )
-
(OECD SAF - Standard audit file - Tax (SAF-T))
-
(Human resource operations - Time and attendance)
-
(2.Transaction availability - 2.3. Common representation of transactions (semantics))
-
(Data discovery - 3.3 Adressing)
-
(Core invoice - Payment instructions)
-
(Item information - Item attributes)
-
(Ecosystem - Asset management)
-
(Denmark - OIOXML)
-
(Purchasing (post award) - Contract management)
-
(Human Resources - Benefits administration)
-
(E. Adoption of structured product information - 1.2.3 The ordering systems must provide product codes.)
-
(Business architectur (Rule book document) - Business Service)
-
(D. Adoption of eOrders, eCatalogs - 1.1.19 Compliant with eCatalog BIS format )
-
(Business architectur (Rule book document) - Business Function)
-
(5.1 Provide and maintain confidentiality - Authentication)
-
(Core invoice - Additional supporting documents)
-
(Financial Management - Managing invoices)
-
(7. Analytics - 3.3 Access to data across businesses )
-
(ERP - Cash sales report)
-
(e-Procurement - e-Ordering)
-
(Quality capabilities - 3.4 High avaliability )
-
(Finland - XBRL-GL)
-
(Tendering (pre-award) - Call for tender)
-
(B. Increase SMEs use of digital business system - born digital - 4.1.1 Demand a certain group of companies to use digital accounting systems. E.g. remove the minimum capital requirement for limited companies, but demand a digital accounting system )
-
(Business architectur (Rule book document) - Business Role)
-
(Ecosystem - Product Catalogue management)
-
(E. Adoption of structured product information - 1.2.8 Standardize a common mandatory set of product and service information, and make this standard flexible enough that it may be extended with sector-specific information and/or information necessary for compliance)
-
(ISO 20022 standard - betalingsinstruksjoner (betalingsfiler) fra kunde til bank (pain 001))
-
(Ecosystem - 3. Reporting and analytics)
-
(Quality capabilities - User consent for B2B sharing)
-
(Financial Service providers - Accounts management)
-
(Inventory management - Receipt activities)
-
(Financial Management - Finance and Accounting)
-
(K. Standardize content of business system transactional data (semantic interoperability) - 5.1.2 Ensure a common semantics in supplemental information to the transaction (e.g. business activities, categorization, product information etc.) in order to make comparative analysis)
-
(F. VAT automation between businesses and business systems - 1.2.10 Enable to have enough information on cross-border level (code & rules))
-
(ICT Service Delivery - 3.4 High avaliability )
-
(e-Procurement - e-Fulfilment)
-
(High level legal questions - Can we forsee a standardizaed logging on use/data sharing? )
-
(Norway - Bits)
-
(Financial auditing - 2.1 Provide technical access points to detailed transaction data)
-
(Customer Relationship Management (CRM) Function - Forecasting and analytics)
-
(Receipt - date of supply)
-
(Sales (order handling) and Marketing function - Sales queries)
-
(Ecosystem - Procurement)
-
(Ecosystem - Sales)
-
(D. Adoption of eOrders, eCatalogs - 1.2.3 The ordering systems must provide product codes.)
-
(Financial operations - Financial reporting)
-
(Account information services - opening up APIs - Danish Saxo Bank, that opened up for their APIs in September 201510)
-
(Sales order processing - Order processing)
-
(C. Adoption of eReceipts - 1.1.15 Implement eReceipts for all PoS-systems (are able create them))
-
(Sales (order handling) and Marketing function - Order processing)
-
(3. Reporting and analytics - 3.3 Access to data across businesses )
-
(Financial Management - Payment finalizaion)
-
(Iceland - FUT)
-
(WP1 Architecture principles - Build on open standards)
-
(Finance and Accounting - Purchase order)
-
(WP2 Common Nordic Rulebook - The information must be represented in a generic and system-independent way to record all of the details in any kind of ledger and bookkeeping)
-
(Finance and Accounting - Sales order)
-
(ERP - Ledger interface)
-
(K. Standardize content of business system transactional data (semantic interoperability) - 5.1.1 Select a common standard as the core for the semantic representation of transactions)
-
(Finland - TeappsXML)
-
(Motivation (Documented needs and User principle document) - NSG vision and goals)
-
(Financial operations - Financial accounting)
-
(Sales (order handling) and Marketing function - Sales order processing)
-
(F. VAT automation between businesses and business systems - 1.2.12 Progress in line with the options and possibilities studied earlier eg. proceed towards the goal set by implementing.)
-
(Ecosystem - 2.Transaction availability)
-
(Quality capabilities - 3.3 Adressing)
-
(Business support and reguslations - Financial service regulations)
-
(WP2 Common Nordic Rulebook - 1.1.4. Data will be collected from qualified electronic financial documents [i.e. Receipts must be retrieved digitally])
-
(Course of Action - National Solution Building Blocks (SBBs) should provide authorization through user’s consent in B2B)
-
(B. Increase SMEs use of digital business system - born digital - 4.1.2 Making sure business system (accounting system) fulfill a set of requirements)
-
(Invoice - buyer)
-
(Norway - EHF v.2.0.8)
-
(Norway - Tilgjengelighet - sikre at regnskapsmaterialet er tilgjengelig for autoriserte personer ved behov)
-
(Core invoice - Buyer)
-
(Tendering (pre-award) - Award)
-
(Pliktig regnskapsrapportering - Omsetningsoppgave MVA)
-
(2.Transaction availability - 2.2. Open accounting (Legal access to real time financial transactions in business systems))
-
(Application architecture (Architecture assessment documents) - Application Component)
-
(Tendering (pre-award) - Contract)
-
(Sales (order handling) and Marketing function - Obtain payment)
-
(Justice administration - Privacy guideline monitoring)
-
(Financial Service providers - Risk management)
-
(WP2 Common Nordic Rulebook - 1.3.2 all needed information should be collected from the actual documents)
-
(Data quality - 2.2. Manage change and deviations (was: Correctness incl. error detection and correction))
-
(WP2 Common Nordic Rulebook - 1.1.2 Data will be collected from qualified electronic financial documents [i.e. Bank account statement must be digitally])
-
(Tendering (pre-award) - Notification)
-
(1. Use of digital business documents - 1.1 Adoption of digital business documents)
-
(High level legal questions - Hvordan legge til rette for dataminimering – forskjell på behov knyttet til ”kreditt basert på utestående fakturaer” og ”ettersyn” )
-
(Norway - Forskrift om bokføring)
-
(J1. Enable standarized access to business systems transactional data (technical interoperability) - 2.1.4 Provide mechanisms that ensure high availability of APIs)
-
(2.Transaction availability - 3.4 High avaliability )
-
(I. Trust services that enable and increase secure business - 1.3.9 Access to a service that provides a warning function related to well known "fraud companies" or the bank account number that is used could also be relevant.)
-
(Government - Justice administration)
-
(I. Trust services that enable and increase secure business - 1.3.10 Implement warning services for suspicious events (B2B))
-
(C. Adoption of eReceipts - 1.1.14 Mobile payment services sends eReceipts (B2B))
-
(Sweden - Svefaktura)
-
(5. Common interpretation - 5.3 Operational metadata on quality and life cycle)
-
(Other requirements- not put into documents - API must support XBRL GL taxonomy)
-
(Quality capabilities - Business systems)
-
(WP1 User principles - When I buy and sell goods and services I don't need to make any special arrangements when my trade-partners are in another Nordic country)
-
(High level semantic questions - Can SAF-T be used for extracting transactions? Can we build on this with small changes (in the direction of XBRL)? )
-
(Ecosystem - Mergers and acquisitions)
-
(J1. Enable standarized access to business systems transactional data (technical interoperability) - 2.1.5 Provided a service to find the actual lookup access points for a business (eAdressing))
-
(Norway - Norsk Standard Kontoplan NS 4102)
-
(7. Analytics - 7.2 Provide anonymised access to aggregated data)
-
(Product information management - Supply)
-
(3. Reporting and analytics - 3.4 Obtaining disclosure control while analysing data)
-
(B. Increase SMEs use of digital business system - born digital - 4.1.3 Enable registration of business directly from business systems (accounting system, banks or other) (“born digital”))
-
(5. Data protection - 5.1 Provide and maintain confidentiality)
-
(Finland - Tax Audit Pilot)
-
(Customer Relationship Management (CRM) Function - Maintain partner masterdata)
-
(Ecosystem - manage access to aggegated data for reporting, statistics and analytics)
-
(CEN/TC 440 - e-Procurement)
-
(D. Adoption of eOrders, eCatalogs - 1.2.1 Include and process product information/codes in the business documents)
-
(6. Governance - 7.3 EU Governance)
-
(Purchasing (post award) - Invoicing)
-
(Credit lending evaluation - Credit Lending Evaluation)
-
(Information exchange - ICT Service Design and Development)
-
(Public procurement - Preparation and publication of competition)
-
(WP1 Architecture principles - Use clearly defined, global semantics)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Bokføringsspesifikasjon)
-
(Purchasing (post award) - Payment)
-
(Core invoice - Invoice note)
-
(WP1 Desired attributes - Data sharing controlled by the data originator)
-
(6. Governance - 6.2 Nordic Governance)
-
(5.2 Keeping the data safe (integrity and ownership) - Encryption)
-
(Data security - 5.2 Keeping the data safe (integrity and ownership))
-
(J1. Enable standarized access to business systems transactional data (technical interoperability) - 2.1.3 implement a standardised format for transferring detailed bookkeeping data between systems (portability))
-
(Receipt - payment)
-
(7. Analytics - 3.4 Obtaining disclosure control while analysing data)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Merverdiavgiftspesifikasjon)
-
(Core invoice - Payee)
-
(Ecosystem - 3rd party sharing)
-
(C. Adoption of eReceipts - 1.1.16 Have an eReceipt follow the Credit/debit card transaction flow)
-
(1. Use of digital business documents - 1.2 Adoption of eOrders)
-
(ISO 20022 standard - kvitteringsfiler (returfiler) fra bank til kunde (pain 002 og pain 003).)
-
(Ecosystem - manage the detailed transactions and give access to transactions)
-
(Invoice line - Invoice line period)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Kundespesifikasjon)
-
(Pliktig regnskapsrapportering - A-meldingen lønn)
-
(5. Common interpretation - 4.3 Common representation of businesses (semantics))
-
(Sellers Tax representative party - Sellers Tax representative postal address)
-
(Norway - Norsk bokføringsstandard NBS 1 Sikring av regnskapsmateriale)
-
(Dokumentasjon av bokførte opplysninger - Kjøpsdokument)
-
(Procurement - Source)
-
(3. Reporting and analytics - 3.1 Financial reporting)
-
(Data management - Data security)
-
(WP1 Architecture principles - Built to evolve )
-
(Receipt - amount/price)
-
(WP1 Architecture principles - Enforce data portability)
-
(Human resource operations - Compensation and benefit)
-
(Bookkeeping - Bank transactions)
-
(Bundle (copy) - Consumers of data from business systems must be provided a service where businesses, by their organization number, to be mapped to lookup access points (end points). (copy))
-
(Financial Service providers - Customer credit ratings)
-
(5.1 Provide and maintain confidentiality - Authorisation and access control)
-
(High level semantic questions - Is the differences in standards accross the Nordics and sectors considered a challenge?)
-
(5.2 Keeping the data safe (integrity and ownership) - Inventory your data)
-
(Purchasing - Receive service or product)
-
(Transaction processing - 1.3 Product information - avaliable)
-
(Core invoice - Document totals )
-
(Digital shoebox (reference implementation) - Pre-storage)
-
(Transaction processing - 1.1 Adoption of digital business documents)
-
(WP2 Common Nordic Rulebook - 1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics])
-
(Motivation (Documented needs and User principle document) - Expected outcomes)
-
(5.2 Keeping the data safe (integrity and ownership) - Tracking / logging)
-
(4. Compliance - 4.1 Born digital)
-
(Busiiness document API - InvoiceAPI)
-
(Procurement - Fullfill)
-
(Business architectur (Rule book document) - Business Process)
-
(Justice administration - Assosications and corporate law)
-
(Core invoice - Document level allowences)
-
(Information exchange - Standardisation)
-
(Data management - Structured data management)
-
(J1. Enable standarized access to business systems transactional data (technical interoperability) - 2.1.1 Establish a standardised service, API, for accessing transactional data about a business)
-
(Denmark - NemHandel)
-
(Ecosystem - Order - buyer places an order )
-
(Customer Relationship Management (CRM) Function - Lead and Opportunity management)
-
((Purchase) Order - Vendor details)
-
(Finance and Accounting - General Ledger)
-
(Application architecture (Architecture assessment documents) - Application Service)
-
(ERP - e-Invoce interface)
-
(WP2 Common Nordic Rulebook - 1.1.3. Data will be collected from qualified electronic financial documents [i.e. Orders must be digitally])
-
(WP1 User principles - I rarely perform manual steps related to inventory, book-keeping, bank-transactions, VAT- and other government reporting etc, unless I choose to verify the proposals from my systems)
-
(High level technical questions - Discovery - (Dynamic) addressing for APIs (aka capability registry) )
-
(WP1 User principles - If someone offers me a better deal or improved service, migrating to new service providers for services like book-keeping, inventory, reporting etc is just as easy as changing operator for my cell phone)
-
(1. Use of digital business documents - 1.4 Standardisation of eReceipts)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.4 Communicate and promote the business case to the SMEs)
-
(2.Transaction availability - 3.3 Adressing)
-
(EU - CEN eInvoicing Semantic Data Model)
-
(Government - Economic and financial management)
-
(WP1 Recommendation of standards - Business Transaction Documents should be compatible with Peppol eDelivery network)
-
(Capabilities (This document) - Resource)
-
(Busiiness document API - BankStatementAPI)
-
(D. Adoption of eOrders, eCatalogs - 1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses)
-
(Ecosystem - Financial operations)
-
(Information exchange - Information delivery)
-
(E. Adoption of structured product information - 1.2.5 Enforce a best practice for use of product and service codes in eInvoicing.)
-
(Core invoice - VAT breakdown)
-
(Invoice line - Price details)
-
(Product information management - Translate)
-
(ISO 20022 standard - Kontoutskrift (camt.053))
-
(Dokumentasjon av bokførte opplysninger - Salgsdokument)
-
(Economic and financial management - Taxation services)
-
(Public procurement - Invoicing)
-
(Inventory management - Inventory Replenishment)
-
(Capabilities (This document) - Capability)
-
(Selling - Create invoice)
-
(Sales order processing - Fullfillment i.e. delivery and receipt of goods and services)
-
(Norway - Kontoopplysninger)
-
(Government - Business support and reguslations)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.1 Compliance with CEN semantic model EN-16931 for invoices)
-
(Pliktig regnskapsrapportering - Annen pliktig regnskapsrapportering)
-
(5. Data protection - 5.4 Provide traceability)
-
(C. Adoption of eReceipts - 1.1.13 Implement mapping and routing from national eReceipts systems to the OpenPeppol network)
-
(Structured data management - 2.3. Common representation of transactions (semantics))
-
(Procurement - Receive service or product)
-
(Standardisation - 1.4 Standardisation of eReceipts)
-
(High level semantic questions - Common representation according to XBRL GL - as a concept scheme? )
-
(Dokumentasjon av bokførte opplysninger - Annen dokumentasjon av bokførte opplysninger)
-
(High level technical questions - What kind of queries/API-s shall be possible - REST, GraphQL, others?)
-
(Procurement - Operational procurement)
-
(Public procurement - Establish contract)
-
(WP4 Capabilities needed of the reference implementation - Financial reports must be aggregated over dimentions like products, clients, suppliers, countries, locations, qualities, quantities.)
-
(Ecosystem - sending and recieving business documents)
-
(Human Resources - Employee)
-
(Purchasing - Receive receipt)
-
(1. Use of digital business documents - 1.2 Adoption of digital product and service information)
-
(Information exchange - Data management)
-
(Core invoice - Deliver to information)
-
(Human Resources - Recruitment and onboarding)
-
(2.Transaction availability - 2.1 Provide technical access points to detailed transaction data)
-
(Ecosystem - Reporting - to government)
-
(Financial Service providers - Factoring)
-
(Motivation (Documented needs and User principle document) - Driver for change / concerns)
-
(Deliver to information - Deliver to address)
-
(Finland - SBR code set)
-
(Public procurement - Verification of business needs and requirements)
-
(I. Trust services that enable and increase secure business - 1.3.6 Access to a service that checks for VAT-registration)
-
(WP1 Architecture principles - Protect user data)
-
(E. Adoption of structured product information - 1.2.1 Include and process product information/codes in the business documents)
-
(WP2 Common Nordic Rulebook - 1.1.1 Data will be collected from qualified electronic financial documents [i.e. Invoices must be retrieved digitally])
-
(WP4 Capabilities needed of the reference implementation - Financial raw data must be available for lookup [variants 1-8])
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.3 Market the eInvoice feature to their customers. E.g. recommend the sending of an eInvoice if the customer is able to receive it )
-
(Deliver to information - Delivery or invoice period)
-
(Public procurement - Submission and evalutation of tenders)
-
(Human Resources - Payroll)
-
(Data management - Reference and master data management)
-
(F. VAT automation between businesses and business systems - 1.2.9 Enable to have enough information on domestic level (codes & rules))
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.8 Buyer can demand an eInvoice)
-
(Ecosystem - Receipt - seller provides a receipt)
-
(Capabilities (This document) - Capability area)
-
(Ecosystem - Financial auditing)
-
(ISO 20022 standard - fullstendig oversikt over transaksjoner som er debitert konto (camt 054d))
-
(High level organizational questions - Do we have sufficient access to public reference data (Business Registry, Product codes, ... others)?)
-
(Invoice - line)
-
(Ecosystem - 5. Data protection)
-
(Finance and Accounting - Account receivables)
-
(e-Procurement - e-Tendering)
-
(Financial reports must be aggregated over dimentions like products, clients, suppliers, countries, locations, qualities, quantities. - Capture product information)
-
(F. VAT automation between businesses and business systems - 1.2.11 Study the possibilities to utilize eDocuments product information in VAT automation between business systems)
-
(Quality capabilities - 2.2. Manage change and deviations (was: Correctness incl. error detection and correction))
-
(WP2 Common Nordic Rulebook - 1.3.1 documents are categorized with its own document type e.g. sales invoice, purchase invoice, receipt, bank account statement, bookkeeping entry, warehouse entry, cash sales etc.)
-
(Course of Action - Business systems can encrypt the communication channels.)
-
(E. Adoption of structured product information - 1.2.7 Synchronize the processes regarding requiring product and service information to make sure product information is digital before encouraging and demanding it )
-
(Product information management - Classify)
-
(XBRL Reporting - XBRL Global Ledger Taxonomy)
-
(Sales - Customer relationship management)
-
(Financial operations - Transaction processing)
-
(Ecosystem - 5. Common interpretation)
-
(Norway - Bokføringsloven)
-
(Selling - Deliver service or product)
-
(Purchasing (post award) - Catalogue of products and services)
-
(Procurement - Purchase order creation)
-
(Capabilities (This document) - Course of Action)
-
(Invoice - seller)
-
(Purchasing - Invoice Approval and Payment)
-
(Tax Audit - Tax Auditing)
-
(Ecosystem - Bookkeeping - internal process)
-
(B. Increase SMEs use of digital business system - born digital - 4.1.4 Business registration process should be changed so that businesses are encouraged to be digital and enable registration in the OpenPeppol SMPs)
-
(Invoice - period)
-
(Data management - Data architecture and catalogueing)
-
(Tendering (pre-award) - Planning)
-
(ERP - Bookkeeping)
-
(CEN standard - Core invoice)
-
(G. Integrity in the business document exchange - 1.3.2 Insist that the digital business document stays entirely unchanged for both the originator and the receiver (meaning that exactly the same physical document must be found on both sides on request) in order to make sure that a voucher is only used once. This enables automated checks (based on hash calculations) )
-
(J2. Enable access to financial transactions in business systems (legal interoperability) - 2.2.1 Require a lookup service to be available (similar to PSD2 directive Account Information Service Provider (AISP) for banks) )
-
(K. Standardize content of business system transactional data (semantic interoperability) - 5.1.4 Base their delivery model on the common representations, and provide access to this as well as the national selected standard)
-
(Seller - Seller postal address)
-
(Finland - FI: Our utimatum goal is to get rid of e-reciepts in 2021)
-
(ISO 20022 standard - Innbetalinger (camt.054 credit))
-
(High level organizational questions - Who will do the certification of ERP-sytems and how can it be done?)
-
(I. Trust services that enable and increase secure business - 1.3.5 Access to a service that checks the validity of a bank account number against the company number)
-
(Epic - Story)
-
(Purchasing - Create order for service or product)
-
(Norway - SAF-T (Financial))
-
(Justice administration - Administrative law)
-
(3. Reporting and analytics - 3.2 Non-financial automated reports)
-
(Inventory management - Inventory control (tracking inventory transactions))
-
(Human Resources - Organization)
-
(Invoice line - Item information)
-
(Finland - Finvoice)
-
(Payment instructions - Payment card information)
-
(Finland - RTECO (Real time economy))
-
(Finance and Accounting - Stock/inventory)
-
(WP4 Capabilities needed of the reference implementation - Financial reports must be available for lookup [use case 6])
-
(WP1 Architecture principles - Favor imperfect existing standards over perfect custom standards)
-
(6. Governance - 6.1 National Governance)
-
(Motivation (Documented needs and User principle document) - Stakeholder)
-
(5.1 Provide and maintain confidentiality - Authentication)
-
(WP3 Take-aways from meetings with business system stakeholders v. 0.1 - Standardized and detailed APIs for bookkeeping transactions creates an opportunity for extracting details and aggregated to business partners, e.g. Banks)
-
(Buyer - Buyer contact)
-
(Buyer - Buyer postal address)
-
(Business architectur (Rule book document) - Product)
-
(5.1 Provide and maintain confidentiality - Authorisation and access control)
-
(Finance and Accounting - Bookkeeping)
-
(OECD SAF - Standard audit file - CashRegister (SAF-C))
-
(WP3 Take-aways from meetings with business system stakeholders v. 0.1 - Addressing - The endpoint(s) of the organisation’s ERP-system must be known)
-
recorded in
(Transaction - Entry)
-
(XBRL Reporting - XBRL Global Ledger)
-
(Quality capabilities - Authorisation and access control)
-
(Roadmap - Release)
-
(Human resource operations - Payroll)
-
(Dokumentasjon av bokførte opplysninger - Lønnsdokumentasjon)
-
(Government - Statistical production management)
-
(Data security - 5.1 Provide and maintain confidentiality)
-
(Journal - Cash register transaction)
-
(Procurement - Vendor management)
-
(Financial operations - Payroll reporting)
-
(Invoice line - Invoice allowences )
-
(Data quality - 4.2 Compliance confirmation services)
-
(A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement - 1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices) )
-
(C. Adoption of eReceipts - 1.1.12 Implement receiving eReceipts in Business systems)
-
(Spesifikasjoner av pliktig regnskapsrapportering - Kontospesifikasjon)
-
(Core invoice - Process control)
-
(Data management - Data governance)
-
(Financial Service providers - Payments)
-
(Seller - Seller contact)
-
(Financial Management - Payment reservation)
-
(Procurement - Purchasing (post award))
-
(Information exchange - ICT Service Delivery)
-
(Procurement - Tendering (pre-award))
-
(Pliktig regnskapsrapportering - Likningsoppgave)
-
(H. Integrity by not having to exchange documents - 1.3.3 Enforce a system where sales documents are not sent at all, but stored in one place and being referenced. Eliminates the challenges of having two different copies at each end)
-
(Taxation services - Tax insepctions and audit)
-
(WP1 User principles - The Government gives me feedback and assures me when everything is OK)
-
(Invoice line - Invoice charges)
-
(Sales order processing - Capture/receive/review customers' purchase order)
-
(Selling - Provide sales receipt)
-
(Pre-storage - Business transactions)
-
(Annual Reporting - Statistics agency)
-
(Preparation and publication of competition - Submission and evalutation of tenders)
-
(Deliver service or product - Create invoice)
-
(Invoicing - Payment)
-
(Receive service or product - Invoice Approval and Payment)
-
(Submission and evalutation of tenders - Establish contract)
-
(Call-off on established contracts - Fullfillment i.e. delivery and receipt of goods and services)
-
(Invoice Approval and Payment - Receive receipt)
-
(Establish contract - Call-off on established contracts)
-
(VAT reporting - Tax authoritiy)
-
(Capability - Course of Action)
-
(Verification of business needs and requirements - Preparation and publication of competition)
-
(Recieve order - Deliver service or product)
-
(Fullfillment i.e. delivery and receipt of goods and services - Invoicing)
-
(Periodic Financial reporting - Economic Investigation and prosecution)
-
(Tax Audit - Tax authoritiy)
-
(Create order for service or product - Receive service or product)
-
(Tax filing - Tax authoritiy)
-
(Custom reporting (on request for data capture by Statistics) - Statistics agency)
-
(Other reporting - Economic Investigation and prosecution)
-
(SME - Statistics)
-
(Annual Reporting - Accounting registry)
-
(Create invoice - Provide sales receipt)
-
(Insuring credit - SME)
-
supports
(Fiken - Adoption of eReceipts)
-
(Lack of quality decision data - Improved decision support)
-
supports
(Xledger - Increased adoption of eInvoices)
-
(Standard Account Plan - Norsk Standard Kontoplan NS 4102)
-
(Account - International Financial Reporting Standards (IFRS))
-
supports
(DNB - Increased adoption of eInvoices)
-
(Acountant - Accountants)
-
(Industry assosiation - Industry associations)
-
supports
(Fiken - Increased adoption of eInvoices)
-
(Standard Account Plan - SBR code set)
-
supports
(Visma - Increased adoption of eInvoices)
-
(Reduce administrative burdens - Administrative burdens too high)
-
(Directive 2014/55/EU on electronic invoicing in public procurement - e-invoice PEPPOL BIS Billing 3.0)
-
(By standardizing we will capture more quality and real-life data with less manual work - Directive 2014/55/EU on electronic invoicing in public procurement)
-
supports
(Power office - Increased adoption of eInvoices)
-
supports
(Zirius - Adoption of eReceipts)
-
supports
(Norwegian regulation "Forskrift om bokføring" - Adoption of eReceipts)
-
(Standardize content for financial information - Getting rid of the pdfs and paper)
-
supports
(DNB - Adoption of eReceipts)
-
(SME - SMEs)
-
(Public Adminstration - Public administrations)
-
(Getting rid of the pdfs and paper - Reduce cost)
-
supports
(Regnskaps Norge IKT-forum - Increased adoption of eInvoices)
-
(Standardize content for financial information - Lower businesses transaction cost by standardizing data formats)
-
(Administrative burdens too high - Reduce cost)
-
(Bookkeeping - 25 % av SME-er benytter skyløsninger for regnskap)
-
supports
(Microsoft Dynamics - Increased adoption of eInvoices)
-
(Lower businesses transaction cost by standardizing data formats - Reduce cost)
-
(Bank - Banks)
-
(Auditor - Auditors)
-
(Increase innovation - Data is not exploited)
-
(Business systems - 1.1.19 Compliant with eCatalog BIS format )
-
(Regulators - 1.2.11 Study the possibilities to utilize eDocuments product information in VAT automation between business systems)
-
(OpenPeppol - 1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x))
-
(Resource - Course of Action)
-
(Product - Capability)
-
(Business systems - E. Adoption of structured product information)
-
(XBRL-GL - XBRL Global Ledger)
-
(Product information management - Product catalog)
-
(Regulators - H. Integrity by not having to exchange documents)
-
(Regulators - A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement)
-
(Digital shoebox (reference implementation) - InvoiceAPI)
-
(Point of sales systems - C. Adoption of eReceipts)
-
(Receive order - 1.2 Adoption of digital product and service information)
-
(Transaction - XBRL Global Ledger)
-
(Authentication - Data sharing controlled by the data originator)
-
(Regulators - 1.1.9 Making eInvoicing mandatory in the Nordics)
-
(Payment reservation - Reserving payment)
-
(Receive receipt - 1.1 Adoption of digital business documents)
-
(5.1 Provide and maintain confidentiality - National Solution Building Blocks (SBBs) should provide authorization through user’s consent in B2B)
-
(Shipping/delivery - Receive order goods)
-
(SME - Users consent SBB)
-
(5.1 Provide and maintain confidentiality - National Solution Building Blocks (SBBs) should provide authentication of a company)
-
(Architecure Building Block (copy) - Bundle (copy))
-
(1.2 Adoption of digital product and service information - 1.3.1 documents are categorized with its own document type e.g. sales invoice, purchase invoice, receipt, bank account statement, bookkeeping entry, warehouse entry, cash sales etc.)
-
(2.1 Provide technical access points to detailed transaction data - 2.1.2 Establish a (standardized) role based authorization service for the businesses to grant access to different parties to read/write data (B2B, …))
-
(1.2 Adoption of digital product and service information - 1.2.1 Include and process product information/codes in the business documents)
-
(Business architectur (Rule book document) - Resource)
-
(Regulators - 1.1.13 Implement mapping and routing from national eReceipts systems to the OpenPeppol network)
-
(Register company API - 4. Compliance)
-
(Standardisation organisations - E. Adoption of structured product information)
-
(2.3. Common representation of transactions (semantics) - The information must be represented in a generic and system-independent way to record all of the details in any kind of ledger and bookkeeping)
-
(Business systems - 2.1.4 Provide mechanisms that ensure high availability of APIs)
-
(Business systems - 2.2.1 Require a lookup service to be available (similar to PSD2 directive Account Information Service Provider (AISP) for banks) )
-
(Digital shoebox (reference implementation) - Load bank statements)
-
(Credit lending evaluation - Giving credit)
-
(Create and send order - 1.1 Adoption of digital business documents)
-
(Exchanging business documents - 1.1 Adoption of digital business documents)
-
(Regulators - B. Increase SMEs use of digital business system - born digital)
-
(Send order confirmation - 1.2 Adoption of digital product and service information)
-
(2.2. Open accounting (Legal access to real time financial transactions in business systems) - Financial reports must be available for lookup [use case 6])
-
(1.1 Adoption of digital business documents - B. Increase SMEs use of digital business system - born digital)
-
(Standardisation organisations - 5.1.3 Provide the mapping between national selected transaction standard and the common reference data model for transactions)
-
(kvitteringsfiler (returfiler) fra bank til kunde (pain 002 og pain 003). - ISO 20022 (Universal Financial Industry Message Scheme))
-
(4.2 Compliance confirmation services - 1.3.9 Access to a service that provides a warning function related to well known "fraud companies" or the bank account number that is used could also be relevant.)
-
(Regulators - 1.2.9 Enable to have enough information on domestic level (codes & rules))
-
(Sales and order management - Price)
-
(Digital shoebox (reference implementation) - Read entries)
-
(Kontoutskrift (camt.053) - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Digital shoebox (reference implementation) - BankStatementAPI)
-
(Application Service - Capability Increment)
-
(5.1 Provide and maintain confidentiality - If someone offers me a better deal or improved service, migrating to new service providers for services like book-keeping, inventory, reporting etc is just as easy as changing operator for my cell phone)
-
(betalingsinstruksjoner (betalingsfiler) fra kunde til bank (pain 001) - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Acting in real-time and up-front - Complience by design)
-
(Business systems - J1. Enable standarized access to business systems transactional data (technical interoperability) )
-
(Purchasing - Purchasing)
-
(1.2 Adoption of digital product and service information - 1.2.2 Discover product information/codes and access services providing additional information about the product.)
-
(Standardisation organisations - 5.1.1 Select a common standard as the core for the semantic representation of transactions)
-
(The information must be represented in a generic and system-independent way to record all of the details in any kind of ledger and bookkeeping - Enforce data portability)
-
(Business systems - K. Standardize content of business system transactional data (semantic interoperability) )
-
(Architecure Building Block (copy) - Consumers of data from business systems must be provided a service where businesses, by their organization number, to be mapped to lookup access points (end points). (copy))
-
(5.1 Provide and maintain confidentiality - 4.1.1 National Solution Building Blocks (SBBs) should provide authorization by power of mandates )
-
(Innbetalinger (camt.054 credit) - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Product catalog providers - 1.2.6 Product catalogues should be used with standardized product codes to provide access to machine readable descriptions of product information that can be used thoughout the supply chain. Product codes must be mapped to general codes; UNSPC and Customs code.)
-
(Capabilities (This document) - Expected outcomes)
-
(fullstendig oversikt over transaksjoner som er debitert konto (camt 054d) - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Core invoice - CEN eInvoicing Semantic Data Model)
-
(Digital shoebox (reference implementation) - OrderAPI)
-
(Business systems - Business systems can encrypt the communication channels.)
-
(e-receipts - FI: Our utimatum goal is to get rid of e-reciepts in 2021)
-
(5.2 Keeping the data safe (integrity and ownership) - Business system provide solutions to ensure that the data is not altered without authorization )
-
(Business systems - 1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices) )
-
(1.2 Adoption of digital product and service information - 1.3.2 all needed information should be collected from the actual documents)
-
(Svefaktura - Svefaktura)
-
(Check known fraudent actors - 4.2 Compliance confirmation services)
-
(Authorisation and access control - Data sharing controlled by the data originator)
-
(e-invoice - e-invoice PEPPOL BIS Billing 3.0)
-
(Stock transfer out - Transfering out stock)
-
(Integrity check of business document - 4.2 Compliance confirmation services)
-
(Business systems - 1.1.12 Implement receiving eReceipts in Business systems)
-
(1.2 Adoption of digital product and service information - D. Adoption of eOrders, eCatalogs)
-
(2.3. Common representation of transactions (semantics) - 5.1.3 Provide the mapping between national selected transaction standard and the common reference data model for transactions)
-
(2.1 Provide technical access points to detailed transaction data - J1. Enable standarized access to business systems transactional data (technical interoperability) )
-
(Business systems - 1.2.1 Include and process product information/codes in the business documents)
-
(1.2 Adoption of digital product and service information - E. Adoption of structured product information)
-
(Regulators - 1.2.12 Progress in line with the options and possibilities studied earlier eg. proceed towards the goal set by implementing.)
-
(1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics] - Build on open standards)
-
(Business systems (copy) - Bundle (copy))
-
(3.4 High avaliability - Financial raw data must be available for lookup [variants 1-8])
-
(Inventory management - Inventory report)
-
(Finvoice - Finvoice)
-
(Application architecture (Architecture assessment documents) - Business Service)
-
(Create and send order - 1.2 Adoption of digital product and service information)
-
(Regulators - 4.1.1 Demand a certain group of companies to use digital accounting systems. E.g. remove the minimum capital requirement for limited companies, but demand a digital accounting system )
-
(Invoice management - e-Invoice)
-
(1.2 Adoption of digital product and service information - F. VAT automation between businesses and business systems)
-
(Data sharing controlled by the data originator - Protect user data)
-
(Invoice Approval and Payment - Paying)
-
(4.2 Compliance confirmation services - 1.3.2 Insist that the digital business document stays entirely unchanged for both the originator and the receiver (meaning that exactly the same physical document must be found on both sides on request) in order to make sure that a voucher is only used once. This enables automated checks (based on hash calculations) )
-
(4.2 Compliance confirmation services - 1.3.1 Access to a digital business documents validation services that check that necessary contents are present and used codes etc. are correct)
-
(OIOUBL - OIOUBL v.2.02)
-
(Standardisation organisations - 5.1.2 Ensure a common semantics in supplemental information to the transaction (e.g. business activities, categorization, product information etc.) in order to make comparative analysis)
-
(4.2 Compliance confirmation services - G. Integrity in the business document exchange)
-
(Business systems - 1.3.10 Implement warning services for suspicious events (B2B))
-
(Check seriousness - 4.2 Compliance confirmation services)
-
(Regulators - 1.2.10 Enable to have enough information on cross-border level (code & rules))
-
(Regulators - 4.1.4 Business registration process should be changed so that businesses are encouraged to be digital and enable registration in the OpenPeppol SMPs)
-
(Business systems - 2.1.1 Establish a standardised service, API, for accessing transactional data about a business)
-
(1.1 Adoption of digital business documents - 1.1.10 Standardize the content of eReceipts)
-
(4.2 Compliance confirmation services - 1.3.5 Access to a service that checks the validity of a bank account number against the company number)
-
(Product catalog providers - E. Adoption of structured product information)
-
(Receive order - 1.1 Adoption of digital business documents)
-
(3.3 Adressing - Addressing - The endpoint(s) of the organisation’s ERP-system must be known)
-
(Standardisation organisations - K. Standardize content of business system transactional data (semantic interoperability) )
-
(EHF - EHF v.2.0.8)
-
(2.3. Common representation of transactions (semantics) - 5.1.2 Ensure a common semantics in supplemental information to the transaction (e.g. business activities, categorization, product information etc.) in order to make comparative analysis)
-
(Roadmap - Epic)
-
(Business systems - 1.3.9 Access to a service that provides a warning function related to well known "fraud companies" or the bank account number that is used could also be relevant.)
-
(Business systems - 1.2.3 The ordering systems must provide product codes.)
-
(Product catalog providers - 1.2.2 Discover product information/codes and access services providing additional information about the product.)
-
(e-receipts - e-receipts)
-
(Receive invoice - 1.1 Adoption of digital business documents)
-
(Standardized access (APIs) - Standardized and detailed APIs for bookkeeping transactions creates an opportunity for extracting details and aggregated to business partners, e.g. Banks)
-
(Regulators - C. Adoption of eReceipts)
-
(RTECO (Real time economy) - FI: Our utimatum goal is to get rid of e-reciepts in 2021)
-
(Digital shoebox (reference implementation) - TransactionAPI)
-
(Purchasing - Standardize content for financial information)
-
(e-order - e-order)
-
(Regulators - F. VAT automation between businesses and business systems)
-
(4.2 Compliance confirmation services - 1.3.8 Access to a service that checks that trading partners really exist before sending documents (is registered in business registries))
-
(1.2 Adoption of digital product and service information - 1.2.6 Product catalogues should be used with standardized product codes to provide access to machine readable descriptions of product information that can be used thoughout the supply chain. Product codes must be mapped to general codes; UNSPC and Customs code.)
-
(Standardisation organisations - 1.1.10 Standardize the content of eReceipts)
-
(2.3. Common representation of transactions (semantics) - K. Standardize content of business system transactional data (semantic interoperability) )
-
(Regulators - G. Integrity in the business document exchange)
-
(Business registry - Retrieve business master data)
-
(Business Process - Business Service)
-
(Sales order processing - Receive order confirmation)
-
(Send invoice - 1.1 Adoption of digital business documents)
-
(1.1 Adoption of digital business documents - 4.1.1 Demand a certain group of companies to use digital accounting systems. E.g. remove the minimum capital requirement for limited companies, but demand a digital accounting system )
-
(Validate bank account - 4.2 Compliance confirmation services)
-
(Chart of accounts - National standards for chart of accounts)
-
(5.2 Keeping the data safe (integrity and ownership) - Business systems must ensure that the data is kept safe and not compromised so that business secrets isn ́t unwillingly shared with wrong parties.)
-
(1.1 Adoption of digital business documents - 1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices) )
-
(2.2. Open accounting (Legal access to real time financial transactions in business systems) - Financial raw data must be available for lookup [variants 1-8])
-
(5.1 Provide and maintain confidentiality - Data sharing controlled by the data originator)
-
(Business systems - Business systems must ensure that the data is kept safe and not compromised so that business secrets isn ́t unwillingly shared with wrong parties.)
-
(Architecure Building Block - Course of Action)
-
(4.2 Compliance confirmation services - I. Trust services that enable and increase secure business)
-
(Business systems - 1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses)
-
(Application Function - Application Service)
-
(Regulators - 1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them)
-
(General Ledger - General Ledger (no: hovedbok))
-
(Business Service - Capability)
-
(5.2 Keeping the data safe (integrity and ownership) - Business systems must recognize parts of information that could be considered as a business secret.)
-
(Release - Story)
-
(1.1 Adoption of digital business documents - 1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics])
-
(Business architectur (Rule book document) - Capability)
-
(Send order confirmation - 1.1 Adoption of digital business documents)
-
(Regulators - 1.2.7 Synchronize the processes regarding requiring product and service information to make sure product information is digital before encouraging and demanding it )
-
(SAF-T (Financial) - Standard audit file - Tax (SAF-T))
-
(Regulators - 1.2.4 Enforce the use of product ans service codes in the supply chain. )
-
(Regulators - 1.2.5 Enforce a best practice for use of product and service codes in eInvoicing.)
-
(Business systems - C. Adoption of eReceipts)
-
(1.1 Adoption of digital business documents - 1.1.2 Data will be collected from qualified electronic financial documents [i.e. Bank account statement must be digitally])
-
(Business systems - 1.1.20 Implement in OpenPeppol BIS eCatalog for Business systems)
-
(Expected outcomes - NSG vision and goals)
-
(Capability - Course of Action)
-
(Application Component - Application Service)
-
(Bank transactions - Bank transaction)
-
(Business systems - Business system provide solutions to ensure that the data is not altered without authorization )
-
(Secure chain approach - Complience by design)
-
(Payment validation - Validating payment)
-
(Business systems - Business systems should have the ability to restrict access to their data, e.g. through an API-manager.)
-
(Send receipt from POS - 1.1 Adoption of digital business documents)
-
(Check VAT registration - 4.2 Compliance confirmation services)
-
(Sales order processing - Create and send order)
-
(Shipping/delivery - Receive Shipping Confirmation)
-
(Standardisation organisations - 1.2.8 Standardize a common mandatory set of product and service information, and make this standard flexible enough that it may be extended with sector-specific information and/or information necessary for compliance)
-
(7.2 Provide anonymised access to aggregated data - Financial reports must be aggregated over dimentions like products, clients, suppliers, countries, locations, qualities, quantities.)
-
(Regulators - 1.1.4 Communicate and promote the business case to the SMEs)
-
(Access historical transactions - 2.2. Open accounting (Legal access to real time financial transactions in business systems))
-
(Principles and constraints - Expected outcomes)
-
(Regulators - 1.3.4 Legal changes to remove the need to store and archive copies of vouchers)
-
(Business registry - Update business master data)
-
(Sales and order management - Pipeline)
-
(Receive order confirmation - 1.1 Adoption of digital business documents)
-
(2.1 Provide technical access points to detailed transaction data - 2.1.1 Establish a standardised service, API, for accessing transactional data about a business)
-
(Business systems - 2.1.4 Provide mechanisms that ensure high availability of APIs)
-
(Architecure Building Block - National Solution Building Blocks (SBBs) should provide authentication of a company)
-
(1.2 Adoption of digital product and service information - 1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses)
-
(Business systems - J2. Enable access to financial transactions in business systems (legal interoperability))
-
(1.1 Adoption of digital business documents - 1.1.4. Data will be collected from qualified electronic financial documents [i.e. Receipts must be retrieved digitally])
-
(Encryption - Strong enforcement of data integrity)
-
(4.2 Compliance confirmation services - 1.3.10 Implement warning services for suspicious events (B2B))
-
(Adjustments - Making adjustments)
-
(Check business registration - 4.2 Compliance confirmation services)
-
(Digital shoebox (reference implementation) - Update entries)
-
(Business Registry - Business Core data API)
-
(Regulators - 1.1.6 Create incentives in when governments require payments e.g. extending the payment deadline for businesses that can receive an eInvoice)
-
(4.1 Born digital - B. Increase SMEs use of digital business system - born digital)
-
(5.1 Provide and maintain confidentiality - Business systems should have the ability to restrict access to their data, e.g. through an API-manager.)
-
(e-catalogues - CEN BII profile for public procurement)
-
(Business systems - 1.3.8 Access to a service that checks that trading partners really exist before sending documents (is registered in business registries))
-
(Sales and order management - Sales volume)
-
(1.1 Adoption of digital business documents - 1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x))
-
(Business systems - 1.3.1 Access to a digital business documents validation services that check that necessary contents are present and used codes etc. are correct)
-
(Bank transaction - ISO 20022 (Universal Financial Industry Message Scheme))
-
(Business document validation - Business document validation API)
-
(Business systems - 2.1.2 Establish a (standardized) role based authorization service for the businesses to grant access to different parties to read/write data (B2B, …))
-
(Architecure Building Block - 4.1.1 National Solution Building Blocks (SBBs) should provide authorization by power of mandates )
-
(2.1 Provide technical access points to detailed transaction data - Financial raw data must be available for lookup [variants 1-8])
-
(Business systems - G. Integrity in the business document exchange)
-
(Managing invoices - Receive invoice)
-
(2.3. Common representation of transactions (semantics) - 5.1.1 Select a common standard as the core for the semantic representation of transactions)
-
(Business systems - D. Adoption of eOrders, eCatalogs)
-
(2.1 Provide technical access points to detailed transaction data - 2.1.3 implement a standardised format for transferring detailed bookkeeping data between systems (portability))
-
(1.3 Product information - avaliable - Capture product information)
-
(Sales and order management - Revenue streams)
-
(Product - Business Service)
-
(1.2 Adoption of digital product and service information - 1.2.3 The ordering systems must provide product codes.)
-
(User consent for B2B sharing - Data sharing controlled by the data originator)
-
(Application Component - Resource (future environment))
-
(4.2 Compliance confirmation services - 1.3.3 Enforce a system where sales documents are not sent at all, but stored in one place and being referenced. Eliminates the challenges of having two different copies at each end)
-
(Regulators - 1.3.3 Enforce a system where sales documents are not sent at all, but stored in one place and being referenced. Eliminates the challenges of having two different copies at each end)
-
(Automatic reporting to government - Standard audit file - Tax (SAF-T))
-
(Inventory Management - Managing inventory)
-
(1.2 Adoption of digital product and service information - 1.2.4 Enforce the use of product ans service codes in the supply chain. )
-
(Business systems - 1.1.3 Market the eInvoice feature to their customers. E.g. recommend the sending of an eInvoice if the customer is able to receive it )
-
(Receive order confirmation - 1.2 Adoption of digital product and service information)
-
(Sales and order management - e-Procurement)
-
(Authorization SBB - Authorization/power of mandates SBB)
-
(4.2 Compliance confirmation services - Check the validity of e-Receipts and e-Invoices - to prevent fraud. Both fraud in creating false Invoices, and receipts - and also prevent using them more than once to verify expenses. )
-
(Automatic reporting to government - Reduce administrative burdens)
-
(Regulators - 1.3.6 Access to a service that checks for VAT-registration)
-
(Regulators - 1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them)
-
(Business systems - 2.1.3 implement a standardised format for transferring detailed bookkeeping data between systems (portability))
-
(Digital shoebox (reference implementation) - Create entries)
-
(Register accounting system (SMP) - 1.1 Adoption of digital business documents)
-
(OpenPeppol - C. Adoption of eReceipts)
-
(e-invoice - Finvoice)
-
(Regulators - I. Trust services that enable and increase secure business)
-
(1.1 Adoption of digital business documents - 1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them)
-
(Roadmap - Capability Increment)
-
(1.1 Adoption of digital business documents - A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement)
-
(1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics] - Use clearly defined, global semantics)
-
(Registration in OpenPeppol SMP - 4.1.2 Making sure business system (accounting system) fulfill a set of requirements)
-
(Business systems - 1.3.5 Access to a service that checks the validity of a bank account number against the company number)
-
(Regulators - 1.1.8 Buyer can demand an eInvoice)
-
(1.1 Adoption of digital business documents - 1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them)
-
(Bank statement - ISO 20022 camt 053)
-
(Register company API - 1.1 Adoption of digital business documents)
-
(Payment finalizaion - Finalizing payment)
-
(SAF-T (Financial) - Skatterevisjoner og kvalitetsarbeid på lavt/detaljert transaksjonsnivå)
-
(Cash sales reporting - Cash sales report)
-
(1.2 Adoption of digital product and service information - 1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering))
-
(2.2. Open accounting (Legal access to real time financial transactions in business systems) - Addressing - The endpoint(s) of the organisation’s ERP-system must be known)
-
(Business systems - 5.1.4 Base their delivery model on the common representations, and provide access to this as well as the national selected standard)
-
(Digital shoebox (reference implementation) - Load eOrders)
-
(Architecure Building Block - 2.1.5 Provided a service to find the actual lookup access points for a business (eAdressing))
-
(Business systems - I. Trust services that enable and increase secure business)
-
(3.3 Adressing - Financial raw data must be available for lookup [variants 1-8])
-
(Bank transaction - Standardize content for financial information)
-
(5.2 Keeping the data safe (integrity and ownership) - Strong enforcement of data integrity)
-
(Business systems - A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement)
-
(Access transactions - 2.2. Open accounting (Legal access to real time financial transactions in business systems))
-
(Regulators - E. Adoption of structured product information)
-
(Business Function - Capability)
-
(1.1 Adoption of digital business documents - 4.1.2 Making sure business system (accounting system) fulfill a set of requirements)
-
(1.1 Adoption of digital business documents - 1.1.1 Data will be collected from qualified electronic financial documents [i.e. Invoices must be retrieved digitally])
-
(1.2 Adoption of digital product and service information - 1.2.7 Synchronize the processes regarding requiring product and service information to make sure product information is digital before encouraging and demanding it )
-
(1.1 Adoption of digital business documents - 1.1.1 Compliance with CEN semantic model EN-16931 for invoices)
-
(Regulators - 1.3.5 Access to a service that checks the validity of a bank account number against the company number)
-
(1.1 Adoption of digital business documents - 1.1.3. Data will be collected from qualified electronic financial documents [i.e. Orders must be digitally])
-
(4.2 Compliance confirmation services - H. Integrity by not having to exchange documents)
-
(Business systems (copy) - Business systems should provide mechanisms that ensure high availability of APIs (copy))
-
(5.1 Provide and maintain confidentiality - Business systems can encrypt the communication channels.)
-
(Digital shoebox (reference implementation) - ReceiptAPI)
-
(Standardisation organisations - C. Adoption of eReceipts)
-
(Authorization SBB - Users consent SBB)
-
(Regulators - 1.3.8 Access to a service that checks that trading partners really exist before sending documents (is registered in business registries))
-
(Asset management - Asset report)
-
(5.1 Provide and maintain confidentiality - Course of Action)
-
(Business document validation - Validataion service)
-
(Point of sales systems - 1.1.14 Mobile payment services sends eReceipts (B2B))
-
(Regulators - 1.3.2 Insist that the digital business document stays entirely unchanged for both the originator and the receiver (meaning that exactly the same physical document must be found on both sides on request) in order to make sure that a voucher is only used once. This enables automated checks (based on hash calculations) )
-
(Point of sales systems - 1.1.15 Implement eReceipts for all PoS-systems (are able create them))
-
(Capabilities (This document) - Principles and constraints)
-
(Authorisation and access control - If someone offers me a better deal or improved service, migrating to new service providers for services like book-keeping, inventory, reporting etc is just as easy as changing operator for my cell phone)
-
(Accounting - Ledger aggregation report)
-
(1.2 Adoption of digital product and service information - 1.2.5 Enforce a best practice for use of product and service codes in eInvoicing.)
-
(Accounting - Ledger details lookup)
-
(Business systems - 1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering))
-
(Obtain payment - Receive payment)
-
(1.1 Adoption of digital business documents - C. Adoption of eReceipts)
-
(Regulators - 4.1.2 Making sure business system (accounting system) fulfill a set of requirements)
-
(Regulators - 4.1.3 Enable registration of business directly from business systems (accounting system, banks or other) (“born digital”))
-
(Digital shoebox (reference implementation) - Load eReceipts)
-
(Regulators - 1.3.7 Access to a service that checks the “seriousness” of a company, e.g. are taxes paid etc.)
-
(Register accounting system (SMP) - 4. Compliance)
-
(Business systems - Business systems must recognize parts of information that could be considered as a business secret.)
-
(1.4 Standardisation of eReceipts - 1.1.5 All the general fields of eOrders are defined and mapped according a chosen standard. [i.e. Orders must be standardized with clear semantics])
-
(Accounts Payables - Accepting Invoice)
-
(Business Process - Capability)
-
(e-invoice - Invoice)
-
(ERP - Business systems)
-
(Architecure Building Block - National Solution Building Blocks (SBBs) should provide authorization through user’s consent in B2B)
-
(Business systems - 1.1.1 Compliance with CEN semantic model EN-16931 for invoices)
-
(3.4 High avaliability - Financial reports must be available for lookup [use case 6])
-
(Ledger aggregation report - Media)
-
(Inventory management - Inventory management)
-
(Getting good trading terms by showing solvency - SME)
-
(Read entries - Reporting service: financial statement)
-
(Payment - Procurement)
-
(Dynamic financing - SME)
-
(Financial service offering - SME)
-
(Update entries - Tax, )
-
(Report on the price levels of products - SME)
-
(Sales and order management - Order processing)
-
(TransactionAPI - Portability)
-
(Syntetic invoice generator - Load eOrders)
-
(Access transactions - SME)
-
(Product - Business Actor)
-
(Customer to bank payment - Paying)
-
(Syntetic invoice generator - Load eReceipts)
-
(Read entries - Accounting service provider)
-
(e-Procurement - Procurement)
-
(Pipeline - Credit Analysis)
-
(TransactionAPI - Analytics)
-
(Retrieve business master data - Public Adminstration)
-
(TransactionAPI - Tracability of products)
-
(Pipeline - Data analysis)
-
(Retrieve business master data - SME service provider)
-
(Cash sales report - Data analysis)
-
(Cash sales - Cash sales)
-
(Receive Shipping Confirmation - Customer (Buyer))
-
(Data analysis - SME)
-
(Marketing services - SME)
-
(Vendor/Supplier (Seller) - Accepting Invoice)
-
(Giving credit - SME)
-
(Receive order confirmation - Customer (Buyer))
-
(Ledger aggregation report - Credit Analysis)
-
(SME - Dashboard and Progonosis)
-
(Credit lending evaluation - SME)
-
(Inventory management - Procurement)
-
(Paying - Customer (Buyer))
-
(Retrieve business master data - SME)
-
(Receive order - Vendor/Supplier (Seller))
-
(Validate bank account - Customer (Buyer))
-
(Receive invoice - Customer (Buyer))
-
(Credit Analysis - Credit Lending Evaluation)
-
(Application Service - Business Function)
-
(Ledger aggregation report - Accounting registry)
-
(Inventory report - Data analysis)
-
(Business Function - Business Process)
-
(Ledger aggregation report - Statistics agency)
-
(Register company API - SME)
-
(Product catalog - Data analysis)
-
(Asset report - Risk management)
-
(Revenue streams - Data analysis)
-
(Create and send order - Customer (Buyer))
-
(Syntetic invoice generator - Load bank statements)
-
(Access transactions - SME trade partner)
-
(TransactionAPI - Store transaction)
-
(Sales and order management - Sales (order handling) and Marketing function)
-
(TransactionAPI - Giving credit)
-
(Provide political influence - SME)
-
(Register accounting system (SMP) - SME)
-
(Tax Audit - SME)
-
(Data analysis - Information services provider)
-
(Credit rating - Credit Lending Evaluation)
-
(Insurance - SME)
-
(Report summarizing receipts pertaining to specific products - SME)
-
(Create entries (copy) - Store transaction (copy))
-
(Finance and Accounting - SME)
-
(Receive invoice - Customer (Buyer))
-
(Ledger details lookup - Economic Investigation and prosecution)
-
(Retrieve business master data - Media)
-
(Send order confirmation - Vendor/Supplier (Seller))
-
(Send receipt from POS - Vendor/Supplier (Seller))
-
(Access transactions - SME business partner)
-
(Report on specific keywords across invoices - SME)
-
(Asset management - SME)
-
(TransactionAPI - Statistics)
-
(Send invoice - Vendor/Supplier (Seller))
-
(Syntetic invoice generator - Purchasing management system)
-
(Summaries of invoices pertaining specific products - SME)
-
(Banking system - Bank statement receiving service)
-
(Investors evaluation - SME)
-
(Create entries - Store transaction)
-
(Receive order confirmation - Customer (Buyer))
-
(Ledger details lookup - Auditor)
-
(Sales and order management - SME)
-
(Risk management - Insurance agency)
-
(Price - Data analysis)
-
(Accounting - Finance and Accounting)
-
(Cash sales reporting - Cash sales)
-
(Invoice management - Managing invoices)
-
(Stock management - SME)
-
(Revenue streams - Credit Analysis)
-
(Dashboard and Progonosis - SME)
-
(TransactionAPI - Tax Audit)
-
(Access transactions - Tax authoritiy)
-
(Portability - SME)
-
(Accounting - Procurement)
-
(Sales volume - Credit Analysis)
-
(Update entries - Digital shoebox (reference implementation))
-
(Integrity check of business document - Customer (Buyer))
-
(Ledger details lookup - Tax authoritiy)
-
(Report on sales or purchases for product groups - SME)
-
(Integrity check of business document - Tax authoritiy)
-
(Check business registration - Customer (Buyer))
-
(e-Invoice - Procurement)
-
(Access transactions - Credit provider (bank))
-
(Ledger aggregation report - Data analysis)
-
(Update entries - Analysis to create added value to the transaction)
-
(Update entries - Business Registries)
-
(Sales volume - Data analysis)
-
(Update business master data - SME)
-
(Receive receipt - Customer (Buyer))
-
(Receive order goods - Customer (Buyer))
-
(Price - Credit Analysis)
-
(Retrieve business master data - SME business partner)
-
(TransactionAPI - Analysis to create added value to the transaction)
-
(SME in financial sector - SME)
-
(Catalogue Deletion - Business document)
-
(Information - Control)
-
(Regular business transactions - Business transactions)
-
(Order Response aka Order Acknowledgement, PO Response - Proof of transaction)
-
(Public procurement - Procurement)
-
(Payment transactions aka Statements of Account - Proof of transaction)
-
(Balance sheet accounts - Account)
-
(Reminder - Business document)
-
(Svefaktura - e-Invoce interface)
-
(ISO 20022 - Bank to customer statement v02. Camd.053.001.02 - Account statement)
-
(Specification Update - Business document)
-
(EHF v.2.0.8 - CEN BII profile for public procurement)
-
(Loans - Liabilites)
-
(Tax authoritiy - Public Adminstration)
-
(CEN BII profile for public procurement - e-invoice PEPPOL BIS Billing 3.0)
-
(Debit Note - Business document)
-
(e-invoice PEPPOL BIS Billing 3.0 - Transaction standards)
-
(Invoice - Proof of transaction)
-
(TeappsXML - e-invoice PEPPOL BIS Billing 3.0)
-
(Business registry - Public Adminstration)
-
(Self determination - Control)
-
(Capability Increment - Capability)
-
(Payment provider (Bank, Credit Card company or broker) - SME business partner)
-
( VAT Recveivable - Liabilites)
-
(Catalogue - Business document)
-
(Catalogue Pricing Update - Business document)
-
(IKT-norge (NO) - Industry associations)
-
(SME trade partner - SME)
-
(Abelia (NO) - Industry associations)
-
(Credit Note - Business document)
-
(EHF v.2.0.8 - UBL)
-
(VAT Payable - Liabilites)
-
(Saleries - Regular business transactions)
-
(Credit provider (bank) - Bank)
-
(Information services provider - SME service provider)
-
(Cash sales - Sales (order handling) and Marketing function)
-
(Depreciation - Less common business transactions)
-
(XBRL-GL - Cash sales report)
-
(Falske faktura, med kjent leverandør som "avsender" - False invoice)
-
(Account statement - Transaction standards)
-
(Vendor/Supplier (Seller) - SME trade partner)
-
(Media - Government, politicians and general public interest)
-
(Prepayments - Less common business transactions)
-
(Skatteetaten (NO) - Public administrations)
-
(Liabilites - Balance sheet accounts)
-
(Credit Insurance agency - Insurance agency)
-
(EDIFACT - e-Invoce interface)
-
(EHF - e-Invoce interface)
-
(Auditor - SME service provider)
-
(Debit Note - Proof of transaction)
-
(Assets - Balance sheet accounts)
-
(Payroll slip - Proof of transaction)
-
(stjeler bedriftspost og lager en identisk faktura med nytt kontonummer. - False invoice)
-
(Catalogue Item - Business document)
-
(Ministries - Government, politicians and general public interest)
-
(Accounts receivalbe - Assets)
-
(Payment transactions aka Statements of Account - Business document)
-
(Accounts payable - Liabilites)
-
(Loan interest - Less common business transactions)
-
(BEAst Invoicing - e-invoice PEPPOL BIS Billing 3.0)
-
(Investors - SME business partner)
-
(Income - Profit and loss statement accounts)
-
(Visma - ERP vendor)
-
(Order Response Simple aka Order Acknowledgement, PO Response - Proof of transaction)
-
(Faktura uten forutgående avtale eller bestilling - False invoice)
-
(Dynamic financing - Giving credit)
-
(Invoice - Business document)
-
(Politicians - Government, politicians and general public interest)
-
(Application Response - Business document)
-
(Expenses - Profit and loss statement accounts)
-
(ERP vendor - SME service provider)
-
(Stock exchange - SME service provider)
-
(Accruals - Less common business transactions)
-
(Insurance agency - SME business partner)
-
(IT infrastructure provider - SME service provider)
-
(Economic Investigation and prosecution - Public Adminstration)
-
(Acountant - SME service provider)
-
(Big data anlytics provider - SME service provider)
-
(Statistisk sentralbyrå (NO) - Public administrations)
-
(Finvoice - e-Invoce interface)
-
(Less common business transactions - Business transactions)
-
(Standard audit file - Tax (SAF-T) - Financial statements standards)
-
(XBRL Global Ledger - Financial statements standards)
-
(CEN eInvoicing Semantic Data Model - e-invoice PEPPOL BIS Billing 3.0)
-
(SME trade partner - SME business partner)
-
((Purchase) Order - Business document)
-
(XBRL-GL - Ledger interface)
-
(Paying bills - Regular business transactions)
-
(Catalogue Request - Business document)
-
(Order Change - Business document)
-
can be
(Proof of transaction - Business document)
-
(e-receipts - Transaction standards)
-
(Sales invoices - Invoice)
-
(Cash Memo - Proof of transaction)
-
(Accounting registry - Public Adminstration)
-
(Customer (Buyer) - SME trade partner)
-
(Sales - Regular business transactions)
-
(SERES - Ledger interface)
-
(Bank - SME business partner)
-
(Credit Note - Proof of transaction)
-
(Profit and loss statement accounts - Account)
-
(SAF-T (Financial) - Ledger interface)
-
(Order Cancellation - Business document)
-
(Receipt - Proof of transaction)
-
(OIOUBL - e-Invoce interface)
-
(Purchases - Regular business transactions)
-
(Statistics agency - Public Adminstration)
-
(Equity - Balance sheet accounts)
-
(Ability/means to react on information - Information)
-
(SAF-T Cash register - Cash sales report)
-
(Purchase invoices - Invoice)
-
(Capture/receive/review customers' purchase order - Validating payment)
-
(Payment clearing and settlement - Receive payment)
-
(Customer to bank payment - Payment clearing and settlement)
-
(Fullfillment i.e. delivery and receipt of goods and services - Transfering out stock)
-
(Managing invoices - Finalizing payment)
-
(Read entries - Auditing service provider)
-
(Reporting service: financial statement - Business Registries)
-
(Syntetic bank statement generator - Bank statement receiving service)
-
(Invoicing - merge fullfilment and invoice)
-
invoice
("Company Y" Sales management system / order portal - Purchasing management system)
-
(Reporting service: statistics - Statistics)
-
(Read entries - Tieto UI (?))
-
(Receive payment from bank - Obtain payment)
-
(Fullfillment i.e. delivery and receipt of goods and services - merge fullfilment and invoice)
-
(Internal financial reporting - External financial reporting)
-
(merge fullfilment and invoice - Finished)
-
(Read entries - Reporting service: tax)
-
(Split fullfilment and invoice - Invoicing)
-
(External financial reporting - Investment, lending and regulation)
-
(Bank statement receiving service - Create entries)
-
(Order processing or finished - Order processing)
-
(Purchasing management system - Syntetic bank statement generator)
-
(Change accounting vendor - SME)
-
(Fullfillment i.e. delivery and receipt of goods and services - Reserving payment)
-
(Reporting service: tax - Tax, )
-
(Order processing - Split fullfilment and invoice)
-
(Accounting service provider - Update entries)
-
(Sales management system / order portal - Create entries)
-
(Order processing or finished - Finished)
-
(Read entries - Reporting service: statistics)
-
(Purchasing management system - Banking system)
-
(Business operations - Internal financial reporting)
-
(Read entries - Reporting sevice "X")
-
(Purchasing management system - Create entries)
-
(Receive Purchase order - Capture/receive/review customers' purchase order)
-
(Reporting sevice "X" - B2B services, Banks, insurance)
-
(Capture/receive/review customers' purchase order - Order processing or finished)
-
(Split fullfilment and invoice - Fullfillment i.e. delivery and receipt of goods and services)
-
(Web Form - Reporter)
-
(Generate requested report - General Ledger)
-
(Generate requested report - Reporting)
-
(Bookkeeping system - Preview requested report)
-
(Bookkeeping system - Generate requested report)
-
(SME - Reporter)
-
(General Purpose National Building Block (Altinn) - Web Form)
-
(Preview requested report - Reporting)
-
(General Purpose National Building Block (Altinn) - Recieve Reports)
-
(Bookkeeping system - General Ledger)
-
(Reporting - Reporter)
-
(Web Form - General Purpose National Building Block (Altinn))
-
(Report - )
-
(Bookkeeping system - Reporting)
-
(Statistics Norway - Recieve Reports)
-
(Bookkeeping system - General Ledger)
-
(Bookkeeping system - Preview requested report)
-
(Make changes to requested report(???) - Reporting)
-
(Preview requested report - Reporting)
-
(Bookkeeping system - Make changes to requested report(???))
-
(Report - )
-
(Generate requested report - Reporting)
-
(Bookkeeping system - Transfer/Post requested report)
-
(Transfer/Post requested report - Reporting)
-
(Generate requested report - General Ledger)
-
(Reporting - Reporter)
-
(Transfer/Post requested report - General Purpose National Building Block (Altinn))
-
(Bookkeeping system - Reporting)
-
(Bookkeeping system - Generate requested report)
-
(Statistics Norway - Recieve Reports)
-
(General Purpose National Building Block (Altinn) - Recieve Reports)
-
(SME - Reporter)
-
(Bookkeeping system - SAF-T representation)
-
(Transfer/Post requested report - Reporting)
-
(General Ledger - SAF-T representation)
-
(Generate requested report - Reporting)
-
(Make changes to requested report(???) - Reporting)
-
(Generate requested report - Generate SAF-T)
-
(Bookkeeping system - Generate SAF-T)
-
(Generate SAF-T - General Ledger)
-
(Bookkeeping system - Transfer/Post requested report)
-
(Transfer/Post requested report - General Purpose National Building Block (Altinn))
-
(General Purpose National Building Block (Altinn) - Recieve Reports)
-
(SME - Reporter)
-
(Statistics Norway - Recieve Reports)
-
(Bookkeeping system - Make changes to requested report(???))
-
(Bookkeeping system - Reporting)
-
(Generate requested report - SAF-T representation)
-
(Preview requested report - Reporting)
-
(Report - )
-
(Bookkeeping system - Preview requested report)
-
(Bookkeeping system - Generate requested report)
-
(Bookkeeping system - General Ledger)
-
(Reporting - Reporter)
-
(Statistics Norway - Recieve Reports)
-
(Bookkeeping system - Reporting)
-
(Bookkeeping system - Generate SAF-T)
-
(Bookkeeping system - API for requesting a report (consent-based))
-
(Transfer/Post requested report - General Purpose National Building Block (Altinn))
-
(Bookkeeping system - General Ledger)
-
(General Ledger - SAF-T representation)
-
(Report - )
-
(Make changes to requested report(???) - Reporting)
-
(Bookkeeping system - Generate requested report)
-
(Generate requested report - Generate SAF-T)
-
(SME - Reporter)
-
(Bookkeeping system - Make changes to requested report(???))
-
(Reporting - Reporter)
-
(Generate requested report - SAF-T representation)
-
(Generate requested report - Reporting)
-
(General Purpose National Building Block (Altinn) - Recieve Reports)
-
(Bookkeeping system - API for machine readable instructions)
-
(Transfer/Post requested report - Reporting)
-
(Bookkeeping system - SAF-T representation)
-
(Bookkeeping system - Preview requested report)
-
(Bookkeeping system - Generic functionality for executing the standardised machine-readable instructions)
-
(Bookkeeping system - Transfer/Post requested report)
-
(Preview requested report - Reporting)
-
(Phase A. Exploring - A02 Business plan)
-
(Phase A. Exploring - A01 Business idea)
-
(Phase B. Establishing - B02. Gather capital)
-
(Phase B. Establishing - B08. Get necessary permits and licences)
-
(Phase B. Establishing - B03. Establish [Stifte])
-
(Phase B. Establishing - B09. Tax and insurance)
-
(Phase B. Establishing - B04. Secure Intellectual Property Rights)
-
(Phase B. Establishing - B05. Register)
-
(Phase B. Establishing - B06. Digital tools)
-
(Phase B. Establishing - B01. Gather information)
-
(Phase B. Establishing - B07. Launch)
-
(Phase C. Running and Developing - C16. Payment problems and [innkreving])
-
(Phase C. Running and Developing - C10. Changes in the organisation)
-
(Phase C. Running and Developing - C07. Employing)
-
(Phase C. Running and Developing - C05. Credit)
-
(Phase C. Running and Developing - C15. Controls [tilsyn])
-
(Phase C. Running and Developing - C02. [Leverandørstyring])
-
(Phase C. Running and Developing - C06. Need for extra capital)
-
(Phase C. Running and Developing - C12. Paying taxes (running and periodically))
-
(Phase C. Running and Developing - C13. End of year accounting)
-
(Phase C. Running and Developing - C11. Board and ownership)
-
(Phase C. Running and Developing - C09. Manage employees)
-
(Phase C. Running and Developing - C01. Buying and selling)
-
(Phase C. Running and Developing - C03. Service providing)
-
(Phase C. Running and Developing - C17. Advice on debts)
-
(Phase C. Running and Developing - C14. Government reporting (annual))
-
(Phase C. Running and Developing - C18. Downsizing)
-
(Phase C. Running and Developing - CXX. Government reporting (running))
-
(Phase D. Dissolving - D02. Bankrupcy)
-
(Phase D. Dissolving - D01. Voluntary dissolving)
-
(Phase D. Dissolving - D03. Forced dissolution)
-
(Phase C. Running and Developing - C04. Adjust excpected turnover, income and VAT)
-
(Phase C. Running and Developing - C08. Paying salary)
-
(Phase D. Dissolving - D04. Delete and/or dissolving)
-
(Phase C. Running and Developing - C19. Negotiation of debt and restructuring)
-
(Phase C. Running and Developing - CXX. B2B documentation and reporting)
-