Abacus setup has three parts: an Abacus administrator prepares the reports and service users, an organization administrator configures the connection in Didyma, and each client is linked to the correct Abacus mandant. Complete all three parts before using a direct import.

Before you start

You need access to Abacus User Management (Q981), AbaReport (Q948), and the Service Manager on the server running Abacus. Ask your Abacus administrator for the approved connection values and credentials. Do not guess a host, report path, client secret, or user account.

Decide whether the connection must only import data or may also post data back to Abacus. Use read-only access unless posting is an intentional part of the approved workflow.

1. Install the Didyma AbaReport package

  1. Open AbaReport (Q948).
  2. Open Extra > Import/Export > Reports importieren….
  3. Select the Didyma reports package (.avz) supplied by Didyma.
  4. Confirm the import.

Keep the package version aligned with the version supported by Didyma. If you do not have the package, contact Didyma support rather than using an unverified copy.

2. Create the Abacus users

Open User Management (Q981) and create a user category named Didyma. Grant the category the approved program policy and mandant access, then activate it with the lightning-bolt action. Follow least-privilege rules: access to every mandant is only appropriate when Didyma is intended to serve every mandant.

REST user for imports

  1. In the Didyma category, add a Service Benutzer.
  2. Name it DidymaREST.
  3. Under Schnittstellen-Zugriff, grant AbaReport and Systemmanagement.
  4. Save the generated Client-ID and Client-Schlüssel in an approved password manager.
  5. Under application access, assign the AbaR (AbaReport) licence. AbaView is not sufficient; the DataScience Edition is required.

SOAP user for posting

Create this user only if Didyma will post approved bookings back to Abacus.

  1. In the Didyma category, create a user named DidymaSOAP and use the same full name.
  2. Clear Passwort mit der nächsten Anmeldung ändern.
  3. Generate a strong password in an approved password manager and enter it twice.
  4. Assign the required FiBu licence.

3. Enable the web services

On the server running Abacus, open Service Manager and review these settings with the Abacus administrator:

  1. Configure AbaConnect.WebService.Users for the relevant web-service group and add DidymaSOAP to the AbaConnect property.
  2. Set abaengine.soap to true.
  3. Set abaengine.soap.reports to true.
  4. Set abaengine.soap.views to true.

Service Manager changes affect the Abacus environment. Apply them through the organization's normal change process and confirm whether a service restart is required.

4. Configure Abacus in Didyma

An organization administrator should then:

  1. Open Settings.
  2. Go to Accounting Software.
  3. Select Configure Abacus.
  4. Enter the Abacus Host / Base URL and Reports Root supplied for the environment.
  5. Choose the access mode: REST-API + AbaConnect or REST-API.
  6. Configure the source used for Ledger entries, Balances, Account names, and Posting.
  7. Enter the REST client ID and client secret.
  8. Select Test REST-API.
  9. Enter a known Mandant and test report access.
  10. For the hybrid access mode, enter the AbaConnect username and password and select Test AbaConnect.
  11. Save the configuration after the required tests succeed.

The source choices available for each operation depend on the access mode. They can include AbaReport, REST API, AbaConnect, Skip, or Off. Choose the source that matches the services enabled by the Abacus administrator. In particular, leave Posting off when the connection is intended only for imports.

Restrict sensitive mandants

The organization configuration can block mandants so that only organization administrators can link them to a Didyma client. Use this when a mandant must remain available in Didyma but non-admins must not be able to create a link to it.

This control is separate from client visibility. If a mandant does not need to be available through Didyma at all, restrict the Abacus users used by Didyma at the Abacus level instead. See Restrict access to Abacus mandants and Manage client permissions.

After the organization connection is saved:

  1. Open the client and go to Client Info.
  2. Open Integrations.
  3. Select Add Link, then Abacus.
  4. Enter the client’s Abacus Mandant.
  5. Review the operation settings for this client.
  6. Enable Read-only to allow imports while blocking posting.
  7. Save the link.

You can also start from a financial statement’s Import step and choose Add Abacus mandant. Confirm the mandant against the Abacus master data; linking the wrong one can bring another entity’s accounting data into the engagement.

Import into a financial statement

Open the statement’s Import step and choose Abacus. Didyma retrieves the available current- and prior-period data according to the organization and client settings.

If direct access is not available, use an Abacus file export: provide the balance-sheet and income-statement data covering both years and, when transaction data is needed, one F15 journal export for each fiscal year. See Import financial data.

Troubleshooting

  • If Abacus is not offered for the client, confirm that both the organization configuration and client mandant link exist.
  • If the report test fails, confirm that the Didyma report package is installed and that DidymaREST has AbaReport access, the correct licence, and access to the tested mandant.
  • If the REST test fails, recheck the base URL, client ID, secret, network access, and permissions with the Abacus administrator.
  • If report access fails, recheck Reports Root, the tested mandant, and the selected operation sources.
  • If AbaConnect fails, confirm that the hybrid access mode is selected and the AbaConnect credentials are valid.
  • If posting is blocked, check Read-only and the configured Posting source before changing anything; the block may be intentional.

Never broaden credentials or posting permissions merely to make a test pass. Resolve the required access with the Abacus administrator.