Building a DICO integration
Appfront builds integrations with DICO, the messaging standard of Ketenstandaard Bouw en Techniek. With DICO, contractors, installers, wholesalers and manufacturers exchange quotes, orders, order confirmations, delivery notes and invoices. We make sure your own system creates and reads those messages, if your software cannot: orders to suppliers, confirmations and delivery notes coming back, and invoices that are automatically matched to the order.
What is a DICO integration?
DICO is the messaging standard for the construction and installation sector, managed by Ketenstandaard Bouw en Techniek. With DICO, parties in the chain exchange electronic messages: from quote request and quote to order, order confirmation, delivery note and invoice. Much business software for the construction industry supports DICO, and Ketenstandaard offers certification for messages that comply with the standard.
If you use your own system or a package without DICO, you miss out on that exchange. Orders go to the wholesaler by email or phone, an order confirmation with a different delivery time goes unnoticed, and a delivery note is signed off on site and retyped at the office. The invoice arrives as a PDF, and anyone checking that what was invoiced was also ordered and delivered has to lay three documents side by side.
We build custom because the integration has to fit your system and your partners: which messages you exchange, with which wholesalers and manufacturers, how articles are coded in your system, and through which channel your partners receive messages. We work out exactly what the standard prescribes from the Ketenstandaard documentation; we make sure your system works with it. We usually start with the partner with the most messages, and add the others afterwards.
Messages from your system
Orders and other messages in line with DICO from your own system, and received messages imported.
Order, delivery and invoice
Delivery notes and invoices linked to the order, with differences flagged for review.
Checked per message
A check before sending, and a log per message with its status.
How we build your DICO integration
We start with your messages: which ones you exchange, with which partners, which system you use, and where retyping happens now.
Your messages, wholesalers and manufacturers, article coding and system.
Messages in line with DICO from your system, and received messages imported.
Delivery notes and invoices linked to the order, and a check for differences.
Testing with real partners, going live per partner, and maintenance for new versions.
What a DICO integration actually does
The components below feature in almost every DICO integration. Which ones you need depends on your partners.
Orders
Orders to suppliers in line with DICO.
Confirmations
Order confirmations with delivery times and deviations.
Delivery notes
Delivery notes linked to the order.
Invoices
Invoices imported and linked to the order and delivery.
Validation
Differences between order, delivery and invoice.
Log
Status and result per message.
Who we build a DICO integration for
The integration is intended for construction companies without DICO in their own system.
Contractors
Many orders from wholesalers. Orders and invoices are the core.
Installers
Materials per project. Linking the delivery note to the project matters most.
Wholesalers and manufacturers
Messages with customers. What you need is the ability to receive orders.
Software suppliers
DICO in your own product. The standard is the core.
Technology and integrations
This page is about DICO messages in construction. For a construction package with DICO, see our page on a BouwWorks integration; for UBL messages outside construction, our page on a UBL integration; and for estimates, our page on construction work estimates. You can read about our approach on building software.
Why Appfront for your DICO integration?
An invoice that isn't checked against the order and delivery note also pays for what wasn't delivered. That's what we build on: messages from your own system, order, delivery and invoice linked together, and a check per message.
No retyping
Orders, delivery notes and invoices go digital.
Differences spotted
Anything that differs between order and invoice stands out.
Chain connected
Partners receive messages in the standard they know.
Security and privacy in a DICO integration
The integration processes orders, prices and invoices from you and your partners. Access credentials for channels are stored encrypted and used only by the integration.
The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and a log of every message.
Frequently asked questions about a DICO integration
Questions that construction companies and wholesalers ask before getting started.
DICO is the messaging standard for the construction and installation sector, managed by Ketenstandaard Bouw en Techniek. Parties use it to exchange quotes, orders, order confirmations, delivery notes and invoices.
UBL is an international standard for business documents across all sectors. DICO is tailored to the construction and installation sector, with agreements on articles and processes in that chain. UBL has its own page.
The messages you exchange with your partners, such as quote request, quote, order, order confirmation, delivery note and invoice. We usually start with the message that involves the most retyping, often the invoice or the order.
Yes. An invoice is matched to the order and the delivery note, and differences in quantities or prices are flagged for review. That way you only pay for what was ordered and delivered. A partial delivery or a follow-up delivery stays linked to the same order, so you can track the status of every order.
The articles in your system are matched to the codes used in the messages. Where that cannot be done one to one, the integration records a mapping, so a message lands on the right articles. A new article that does not have a mapping yet is queued for you to match once.
Ketenstandaard offers a certification for DICO messages. Whether and when you apply for it is up to you; the integration adheres to the standard, so certification is possible.
Companies with their own system or a package without DICO support, and software vendors who want to support DICO in their product. If you use a package that already supports DICO, a custom integration is often not needed.
Orders and invoices according to the construction standard?
Tell us which messages you exchange, with which partners and which system you use. We will show you what the integration looks like.