Scopevisio API Integration Research

Date: 2026-04-29 Product: Scopevisio Cloud ERP (by Scopevisio AG, Bonn, Germany) Purpose: Evaluate Scopevisio's API capabilities for Orcha integration

1. Summary -- Capability Matrix

Overall assessment: Scopevisio has a comprehensive REST API ("OpenScope") with strong read AND write support across accounting, contacts, invoices, dimensions, and postings. The API is a direct integration path -- no iPaaS middleware exists for Scopevisio. The main gaps are: no webhook/event system (requires polling) and no programmatic approval workflow management.

2. API Landscape

API Layers

There is only one API layer -- the OpenScope REST API covers all modules. No separate admin API, no legacy API versions to worry about.

Authentication

Key Technical Details

• Max response size: 5,000 entries per request
• Date format: dd.MM.yyyy
• Pagination: Supported on most search endpoints via field filtering
• Rate limits: Not publicly documented

API Coverage by Module

3. Write Capability Verification

Confidence: HIGH -- Write operations are extensively documented in the Swagger spec.

Confirmed Write Endpoints (from Swagger spec)

Important: POST endpoints that are actually READ operations

Several POST endpoints in Scopevisio use POST for search/filter operations (sending query payloads):

• POST /contacts -- Search contacts (READ)
• POST /incominginvoices -- Search incoming invoices (READ)
• POST /outgoinginvoices -- Search outgoing invoices (READ)
• POST /debitoraccounts -- Search debtor accounts (READ)
• POST /dimensions -- Search dimensions (READ)

These are clearly read operations despite using POST.

4. iPaaS & Middleware Findings

Key finding: No iPaaS platform has a Scopevisio connector. This means:

1. Direct API integration is the only programmatic path
2. This is actually positive for Orcha -- no middleman needed, full control over the integration
3. The API is well-documented enough to integrate directly

5. Alternative Channels

DATEV Interface

• Direction: Bidirectional (import and export)
• Data types: Invoices, receipts, cash sheets, posting records
• API endpoint: POST /datevpostings/new for programmatic DATEV-format import, POST /datevexport for export
• Also available via UI for manual transfers to/from tax advisors
• Relevance for Orcha: The DATEV posting import endpoint is a viable programmatic write path for posting records

CSV Import

• Direction: Inbound (import only)
• Data types: G/L accounts, subledger accounts (debtors/creditors), posting records
• Method: UI-based only (drag & drop or file picker in web interface)
• Encoding: ISO-8859-15 recommended
• Limitations: Not programmatically accessible -- requires manual user action
• Relevance for Orcha: Fallback only; the REST API covers all CSV-importable data types

Email Import

• Endpoint: POST /incomingmail/new -- import incoming emails programmatically
• Relevance: Could be used to push invoice documents as email attachments

Webhooks / Event Notifications

• Status: NOT AVAILABLE
• Workaround: Polling via search endpoints (e.g., POST /incominginvoices with date/status filters)

Unified APIs

• Chift: Scopevisio not listed as connector
• Merge, Finch, Rutter: Not applicable (Scopevisio is German-market focused)

6. Licensing & Access Requirements

API Included in Base Subscription

YES -- API access is included. According to the pricing page:

"Wartung, Updates, API inklusive" (Maintenance, updates, API included)

The OpenScope REST API is part of every Scopevisio subscription. No separate API module purchase required.

Pricing Structure

What the Customer Needs

1. Active Scopevisio subscription with at least:
   • Organisation module (included in all plans)
   • Finanzen module (required for accounting, invoices, postings, dimensions)
   • DMS/ECM module (included in all plans)
2. User credentials for API authentication (OAuth 2.0 bearer token)
3. No additional API license or module purchase required

Admin Setup Checklist

1. Customer has active Scopevisio subscription with Finanzen module
2. Customer provides API user credentials (or creates a dedicated API user)
3. OAuth token generation verified against Scopevisio token endpoint
4. Verify which dimensions (cost centers, profit centers) are configured in their instance
5. Verify chart of accounts structure (SKR03/SKR04 or custom)

Ongoing Costs

• No per-API-call charges documented
• Standard user license costs only
• No rate limit overage fees documented

7. Orcha-Specific Deep Dive

Core Need 1: Sync Reference Data Inbound (Read)

Goal: Read the customer's chart of accounts, suppliers, cost centers to validate against.

Assessment: Full read access to all reference data Orcha needs. Up to 10 dimension categories supported (Kostenstellen, Kostentraeger, Profit Center, etc.).

Core Need 2: Write Reference Data (Cost Centers, Accounts)

Goal: Create/update cost centers, GL accounts, debtor/creditor accounts.

Assessment: Full write access for all reference data types. Dimensions can be created and updated programmatically.

Core Need 3: Push Documents (Incoming Invoices)

Goal: Push extracted invoices into Scopevisio.

Assessment: Strong write capability for incoming invoices. The POST /incominginvoice/new endpoint is the primary integration point. File attachment directly to invoices needs endpoint verification (teamwork file links exist for retrieval; upload path may go through contact or email import).

Core Need 4: Manage Approvals

Goal: Trigger, approve, or reject documents programmatically.

Assessment: Approval workflow is NOT exposed via the API. Scopevisio has a multi-level approval process (Freigabeprozess) for incoming invoices in the UI, with configurable mandatory fields per stage (cost centers, project assignments). However, this workflow cannot be triggered, advanced, or managed via the API. Documents pushed via API would enter the workflow at whatever stage the customer's configuration dictates.

Core Need 5: Track Document Lifecycle (Status Read-Back)

Goal: Poll or receive events for document status changes.

Assessment: Status tracking is available via polling. No webhook/event system exists. Orcha would need to implement periodic polling (e.g., every 5-15 minutes) against the search endpoints with date/status filters to track document lifecycle changes.

Orcha Integration Capability Summary

8. Recommended Path Forward

Architecture: Direct REST API Integration

Recommended approach: Direct integration via the OpenScope REST API.

Rationale:

• No iPaaS connectors exist -- direct API is the only option
• The API is comprehensive with full read/write support
• API is included in the base subscription (no extra cost for the customer)
• Well-documented via Swagger/OpenAPI spec
• OAuth 2.0 authentication is standard

Cost/Complexity Assessment

Phased Integration Plan

Phase 1 -- Reference Data Sync (Foundation)

• Read customer's chart of accounts (GL, debtor, creditor accounts)
• Read dimensions (cost centers, profit centers, etc.) and their entries
• Read contacts/suppliers
• Build local validation cache for Orcha's extraction pipeline

Phase 2 -- Document Push (Core Value)

• Push extracted incoming invoices via POST /incominginvoice/new
• Set responsible contact via PUT /incominginvoice/{id}/responsiblecontact
• Push posting records via POST /datevpostings/new or /postings/correction
• Test file attachment paths (contact file upload or email import)

Phase 3 -- Lifecycle Tracking

• Implement polling loop against POST /incominginvoices with date/status filters
• Track invoice status transitions (imported -> in verification -> approved -> posted)
• Frequency: every 5-15 minutes recommended

Phase 4 -- Reference Data Write-Back (Optional)

• Create new dimension entries (cost centers) from Orcha
• Create new contacts/suppliers
• Create debtor/creditor accounts for new contacts

Key Limitations to Communicate to Customers

1. No approval management: Invoices pushed via API will enter the customer's approval workflow, but Orcha cannot approve/reject/advance them programmatically
2. No real-time events: No webhooks -- Orcha must poll for status changes
3. Incoming invoice updates: Can only update invoices before they enter verification
4. File attachments: Direct attachment to invoices may require going through contact file upload or email import rather than a dedicated invoice attachment endpoint

9. Sources

Official Documentation

• Scopevisio REST API Swagger UI
• Scopevisio OpenAPI Spec (swagger.json)
• Scopevisio Help Center -- API
• OpenScope Overview
• OpenScope REST API Page
• Scopevisio Pricing

Help Articles

• CSV Import of G/L and Subledger Accounts
• DATEV Interface
• Accounting Software with API
• OpenScope API Explained
• Incoming Invoices Help

Community / GitHub

• owahlen/scopevisio -- Python: Extract accounting data via API
• yrrgarten/scopevisio-helper -- Python helper scripts
• CompuMaster.Scopevisio.OpenApi -- .NET client library (NuGet)
• Scopevisio GitHub Org

Third-Party Reviews

• Scopevisio on GetApp
• Scopevisio on Capterra
• Scopevisio on Software Advice

iPaaS / Unified APIs Checked (No Connector Found)

• Celigo Integration Marketplace
• Zapier Apps
• Make.com Integrations
• Chift Unified Accounting API