P4 Software
/
activoHQ English
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.
Side menu: Settings > Integration
Direct URL: /Settings/integration
| 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. |
https://cifrahq.example/api/journals).| 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. |
| 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. |
Available to users with access to the Settings module, as configured by your administrator.
/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.| 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. |
Was this page helpful?