Technical information

This page provides technical details for d‑basics Collector and explains the differences between the on-premises and SaaS (Collector Online) versions.

Technical Specifications

The table below outlines the system requirements and technical details for both deployment options—on-premises (d‑basics Collector v2) and SaaS (Collector Online)

	d‑basics Collector v2	Collector Online
Deployment option	On-premises	SaaS (Online)
Available for	On-premises and online accounting software	online accounting software only
Is Collector software installation required?	Yes	No
Data processing location	Computer environment client	d‑basics datacenter environment (Europe)
Minimum computer specifications	Modern workstation or server meeting current system requirements.	n/a
Can the software run on a virtual machine?	Yes	n/a
System availability (on-premises)	Always available / running 24/7	n/a
Processor requirements	Minimum 8-core processor or higher	n/a
Memory requirements	Minimum 16 GB RAM or higher	n/a
Disk space requirements	Minimum 2GB of free disk space (depends on amount of data processed)	Subject to a fair use policy; no local disk space required.
Supported operating system	Current Windows workstation or server OS	n/a
Required type of database access	Read access to database of accounting software	Read access to database of accounting software

Additional software

d‑basics Collector connects to your accounting software database to retrieve data.

For on-premises installations, you may need to install extra components (such as an ODBC driver) to enable this connection. For Collector Online, certain features in your accounting software may need to be activated to allow API access.

These steps are typically handled by your system administrator, and any related costs are the client’s responsibility. If needed, the d‑basics Service Desk is happy to guide your system administrator through arranging, installing, and configuring additional software or features.

Installation

The d‑basics Service Desk will schedule an appointment for installing and configuring the software. During this appointment, a remote desktop connection will be used to assist with the installation and configuration process.

On-premises installation

To ensure a smooth on-premises installation of the Collector software, please prepare the following:

Computer readiness: The computer where the software will be installed must be available and meet system requirements.
Additional components: If extra software is required (e.g., ODBC driver) or functionality needs to be activated or configured in the accounting software, this should be completed before the appointment.
Database access: If a dedicated user account is required to connect to the accounting database, it must be created beforehand with read permissions for the relevant data.
System administrator presence: The system administrator should be available during installation and have admin rights within the environment where d‑basics Collector will be installed.
Finance department support: A finance team member with access to the accounting software should be available to verify imported data, assist with code mapping, and help set filters.
Authentication details: Credentials required for uploading data to the recipient must be ready.

Implementation Collector Online

For a smooth implementation of Collector Online, please ensure:

Accounting software setup: Any required functionality in the online accounting software should be activated before the appointment.
API access: If a separate user account is needed for API access to the accounting package, it must be created beforehand with read permissions for the relevant data.
System administrator presence: The system administrator should be available during installation and have admin rights within the online accounting software.
Finance department support: A finance team member should be available to verify imported data, assist with code mapping, and help set filters.
Authentication details: Credentials required for uploading data to the recipient must be ready.

Application manager

After installation and configuration are complete, a scheduled task will automatically trigger data extraction and upload at fixed intervals.

Because this process runs in the background, there is a risk that issues go unnoticed—such as stopped uploads or incomplete data extraction due to tasks like code mapping. To prevent this, the client should assign an Application Manager to monitor the software and ensure smooth operation.

To ensure that d‑basics Collector keeps running smoothly, the client should assign an Application Manager that keeps an eye on the software.

Key responsibilities include:

Verifying that uploads occur according to schedule
Checking that data is processed correctly
Ensuring no unmapped codes prevent successful data extraction
Confirming that credentials for accessing accounting software or uploading files remain valid (especially if passwords change periodically)

d‑basics Service Desk

If the Application Manager encounters an issue that cannot be resolved, the d‑basics Service Desk is available to assist.

Notifications

If d‑basics Collector cannot complete a data extraction task, a notification is sent to the email address linked to the user account running the software.

If the Application Manager uses a different email address, add it to the notification recipient list.

Important: d‑basics Collector cannot send notifications if the software is not running. The Application Manager should also confirm that the recipient is receiving data files as expected.