Skip to content
P4 Software P4 Software / activoHQ English

Add these docs to Claude

Ask Claude questions about these docs. Claude reads the published pages and links you back to them. Copy this address:

https://p4-software.opendocs.page/mcp

In claude.ai or Claude Desktop: open Settings, then Connectors, choose Add custom connector and paste the address.

In Claude Code, run:

claude mcp add --transport http docs https://p4-software.opendocs.page/mcp

cifraHQ integration

cifraHQ integration

Overview

This screen connects activoHQ to the cifraHQ Accounting system so the journal entries generated by fixed Assets (depreciation, disposals, revaluations and impairments) can be sent to it. The account administrator configures the endpoint, the company code and the authentication key here; once saved, the Journal batches you upload from Accounting > Journal batches are posted to cifraHQ's general ledger. Uploading is done by hand with Upload Pending or Retry; nothing is sent in the background. If the endpoint is left unconfigured, the system runs in dry-run mode with no external calls.


How to get there

Side menu: Settings > Integration

Direct URL: /Settings/integration


Key concepts

Term Meaning
Endpoint The URL of the cifraHQ service that receives the journal entries (for example https://cifrahq.example/api/journals).
Cifra Company Code The company's identifier inside cifraHQ. It must match the code configured in cifraHQ exactly.
API Key The secret credential activoHQ sends on every request to authenticate against cifraHQ.
Dry-run mode When Endpoint URL is blank, the upload processes run internally with no call to cifraHQ at all, and the batches are marked Sent. A batch marked Sent is not uploaded again later, so use this mode with test data only.
GL account map The table that records, for each Accounting event type, the matching account code in cifraHQ. Validate uses it to check that every event type with pending batches is covered; the account codes on the journal lines themselves come from each asset model. It is managed on the GL Account Map screen.
Journal batch A set of journal entries in Pending status that have not yet been sent to cifraHQ.
Accounting event type (GlEvent) The Accounting movement's category: Asset Acquisition, Depreciation, Disposal, Revaluation, Impairment or Transfer. Batches are created today only for Depreciation, Disposal, Revaluation and Impairment.

How to use it

Configure the cifraHQ connection

  1. In the side menu, click Settings and then Integration.
  2. In the Posting target (this company) section, complete all three fields:
    • Endpoint URL - enter the full address of the cifraHQ API (for example https://cifrahq.example/api/journals).
    • Cifra Company Code - enter the company code exactly as it is registered in cifraHQ.
    • API Key - enter the API key supplied by cifraHQ. The value is masked like a password.
  3. Click Save. The button reads Saving... while it processes; when it finishes, the notification "Integration Settings saved" appears.

Test the connection

  1. Save the Settings first, then click Test connection. The test uses the saved Settings, not what is typed in the fields.
  2. activoHQ sends a test request to the configured endpoint.
    • If the connection succeeds, you see a success notification with the HTTP status code cifraHQ returned (for example HTTP 200).
    • If the endpoint is blank, activoHQ replies that dry-run mode is active (not an error).
    • If there is a network or authentication error, an error notification appears with the detail.

Validate the account map Coverage

  1. Click Validate.
  2. activoHQ checks two conditions:
    • If the endpoint is blank, it shows a Warning saying the system will run in dry-run mode.
    • For each Accounting event type with pending batches that has no active entry on the GL Account Map, it shows an Error.
  3. The Validation panel appears below the form:
    • If there are no problems: "No issues - ready to post."
    • If there are problems: a list of items with their severity (Warning or Error) and the descriptive message.
  4. Fix the problems flagged (configure the endpoint, or complete the account map) and click Validate again to confirm.

Running in dry-run mode

  • Leave Endpoint URL blank to run the uploads in dry-run mode (with no cifraHQ call). The screen states this: Leave the endpoint blank to run uploads in dry-run mode (no cifraHQ call).
  • In this mode, every posting process runs locally without sending any external data. Uploading in this mode marks the batches Sent, and a batch marked Sent is not uploaded again later, so use it only during implementation or testing with test data.

Fields

Field Type Required Description Validation
Endpoint URL Text field No The URL of the cifraHQ API that will receive the entries. Left blank, the system runs in dry-run mode. No format validation on screen; it is checked by Test connection.
Cifra Company Code Text field Yes (for an active integration) The code identifying the company inside cifraHQ. Not validated on screen; it must match the record in cifraHQ.
API Key Password field Yes (for an active integration) The authentication credential issued by cifraHQ. The value is masked in this field. No length validation on screen; it is checked by Test connection.

Buttons

Button Action
Save Saves all three fields in your account's Settings. It is disabled while processing.
Test connection Sends a test request to the configured endpoint and shows the result in a notification.
Validate Runs the pre-upload checks and shows the Validation panel with any problems found.

Permissions

Available to users with access to the Settings module, as configured by your administrator.


Notes

  • GL account map: Validate Reports an error for every Accounting event type that has pending batches but no active record on the GL Account Map screen (/master/gl-account-map); see GL account map (cifraHQ). The upload itself does not depend on the map. The available Accounting events are: Asset Acquisition, Depreciation, Disposal, Revaluation, Impairment and Transfer.
  • Dry-run mode: leaving the endpoint blank is a valid option during roll-out. Nothing is sent to cifraHQ. If you upload batches in this mode they are marked Sent and are not uploaded again later, so fill in and test the endpoint before uploading batches you want delivered.
  • Scope: the Settings apply only to the active company selected in your session. If your account manages several Companies, repeat the process for each one.

Troubleshooting

Symptom Likely cause Resolution
The Test connection notification shows an authentication error (401 / 403). The API Key is wrong or has expired. Ask the cifraHQ administrator for a new API key, update the field and click Save.
The Test connection notification shows a network or timeout error. The Endpoint URL is wrong, or cifraHQ is unavailable. Verify the URL with the cifraHQ team and make sure the service is up.
The Validation panel shows errors like "No GL account map for Depreciation". No active account map exists for that event type. Open the GL Account Map screen and add or activate the record matching the event named.
The Validation panel shows the warning "No cifraHQ endpoint configured - uploads run in dry-run mode". The Endpoint URL field is blank. Enter the cifraHQ endpoint URL and click Save.
Clicking Save shows an error notification. A communication error with the activoHQ server. Reload the page and try again. If the problem persists, contact technical support.

Related

Was this page helpful?