{
 "categories": [
  "payroll",
  "hr",
  "legacy-software"
 ],
 "deployment": "desktop",
 "evidence": [
  {
   "date": "2026-08-16",
   "fact": "homepage",
   "note": "Visma's retained product page identifies Visma L\u00f8nn and states that payroll can no longer be run from it from 2024.",
   "source": "https://www.vismasoftware.no/visma-lonn",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "platforms",
   "note": "The vendor's version 11 documentation describes an installed Visma L\u00f8nn application with client-side menus, setup, and upgrade requirements.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "license",
   "note": "The vendor manual says the software is licensed under a usage and maintenance agreement and may only be used on licensed machines.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.api.exists",
   "note": "Visma documents a narrow Sync engine integration between Visma L\u00f8nn and Visma.net Time and Absence.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.api.kinds[0]",
   "note": "The integration is a product-specific synchronization mechanism that must be activated through a Visma partner.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.api.coverage",
   "note": "The documented coverage is limited to selected Visma.net services, including payroll-code synchronization and importing approved hours into a payroll run.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.data_access.export[0]",
   "note": "Visma documents an in-product Flytt til Payroll action that exports current payroll-system data into its managed migration process.",
   "source": "https://www.vismasoftware.no/artikler/bytte-fra-visma-lonn-til-det-skybaserte-lonnssystemet-payroll",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.data_access.import[0]",
   "note": "The vendor documents importing approved Visma.net Time entries into a Visma L\u00f8nn payroll run through Sync engine.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "modalities.data_access.import[1]",
   "note": "Visma's Calendar guide documents CSV export and subsequent import into Visma L\u00f8nn, with unique identifiers used to avoid duplicate hours.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/547db4365b91487c98fa07f0eddc4640.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "verdict.scores.api",
   "note": "The proprietary synchronization path belongs to a product that can no longer run payroll and whose vendor-supported outcome is migration, placing it at the stale and severely restricted end of the API scale.",
   "source": "https://www.vismasoftware.no/visma-lonn",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as Visma's retained first-party lifecycle statement for Visma L\u00f8nn.",
   "source": "https://www.vismasoftware.no/visma-lonn",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as Visma's first-party migration procedure from Visma L\u00f8nn to Payroll.",
   "source": "https://www.vismasoftware.no/artikler/bytte-fra-visma-lonn-til-det-skybaserte-lonnssystemet-payroll",
   "tier": "declared"
  },
  {
   "date": "2026-08-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as retained vendor documentation for Visma L\u00f8nn version 11 and its Sync engine path.",
   "source": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-08-16",
  "volatility": "low",
  "watch": [
   {
    "type": "lifecycle",
    "url": "https://www.vismasoftware.no/visma-lonn"
   },
   {
    "type": "migration",
    "url": "https://www.vismasoftware.no/artikler/bytte-fra-visma-lonn-til-det-skybaserte-lonnssystemet-payroll"
   },
   {
    "type": "docs",
    "url": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf"
   }
  ]
 },
 "homepage": "https://www.vismasoftware.no/visma-lonn",
 "id": "visma-lonn",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": "https://community.visma.com/legacyfs/online/mdn_images/f0e5d479bc7c44f692e2d3cd0c58a86e.pdf",
   "exists": "partial",
   "kinds": [
    "proprietary-sync"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "payroll-migration"
   ],
   "import": [
    "visma-net-sync",
    "csv"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Visma L\u00f8nn is an end-of-life Windows payroll product that may hold sensitive employee and financial data; UI automation remains unassessed.",
   "ui_stack": [
    "windows-client"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Visma L\u00f8nn",
 "platforms": [
  "windows"
 ],
 "related": {
  "alternatives": [
   "visma-payroll",
   "tripletex",
   "poweroffice-go"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "eol",
 "vendor": "Visma Software",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 1,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 1,
   "rpa": null
  },
  "summary": "Visma L\u00f8nn is end of life: Visma states that payroll can no longer be run from the product from 2024 and directs customers to its cloud Payroll replacement. Historical vendor documentation describes narrow product-specific machinery: a Sync engine exchanged selected data with Visma.net services, approved hours could be imported into a payroll run, and Calendar data could be moved through CSV. Visma also provided an in-product migration action that exported base data for its managed move to Payroll. These paths can help extract or transfer legacy data, but they are stale and restricted, not a supported general automation platform. No current public SDK, CLI, webhook, or MCP path was established; unknown fields remain unknown rather than being converted into absence. The supported outcome is migration to Payroll. UI and computer-use paths remain unassessed.\n"
 }
}