cvr.dev · company data
cvr.dev integration: automatic CVR lookup in your app
A cvr.dev integration means that when someone types a CVR in your system, you fetch name, address, status and any cessation — before you create a directory card. It is the cheapest integration you can build, measured in errors you avoid. A wrong company name on an invoice costs more than the lookup. You look up name, address lines, status and industry code if you use it for onboarding. Signing rules only if you actually have a compliance need. It should sit as autocomplete on the CVR field, not as a “look up” button people forget. The chain: cvr.dev → customer card with you → debtor in e-conomic or Dinero. Three steps, one truth about CVR.
Public CVR data also exists directly from the Danish Business Authority. cvr.dev is a developer-friendly layer. Pick what your team can keep running. See pricing.
CVR
37 57 64 76
Ceptiv ApS
Lyngbyvej 83A · 2100 · Aktiv
What you look up in a cvr.dev integration
- Name and address lines
- Status (active, ceased, in bankruptcy)
- Industry code if you use it for onboarding
- Signing rules — only if you actually have a compliance need
Where it should sit in the UI
Not as a “look up” button people forget. As autocomplete on the CVR field. They type 8 digits, the rest fills in.
cvr.dev
Name, address and status are fetched while the field is filled.
Customer card
Your system creates or matches. No duplicate on the same CVR.
Debtor
The same CVR lands in e-conomic or Dinero.
May we cache CVR data? Yes, for a short period. Companies change address. Cache without a TTL gives wrong invoices in 18 months. Company data is public. Mixed with contact persons and emails it is personal data. Keep the fields apart.
8
digits, then the rest fills in
1
truth about CVR across app and books
cvr.dev is often integration no. 1 in an SME package, because it pays for itself immediately. Small: DKK 18,000 + DKK 600/month, or as the second in Medium together with MobilePay or e-conomic. See pricing.
Take the latest invoice with the wrong company name. That is the business case. The rest is autocomplete. Quote within 24 hours.
FAQ: cvr.dev integration
May we cache CVR data?
Yes, for a short period. Companies change address. Cache without a TTL gives wrong invoices in 18 months.
Is it personal data?
Company data is public. Mixed with contact persons and emails it is personal data. Keep the fields apart.
Why not call the Business Authority directly?
You may. cvr.dev is a developer-friendly layer. Pick what your team can keep running.
Should ceased companies be selectable?
Show status clearly. Block creation, or require a deliberate confirm. Quietly creating a ceased CVR is the expensive mistake.
Does cvr.dev belong in the Small package?
Yes. It is often integration no. 1, because it pays for itself immediately — fewer duplicates, fewer wrong invoices.