P4 Software
/
activoHQ English
The Journal Batches screen shows the record of every journal entry activoHQ generates automatically from fixed asset events (depreciation, disposals, revaluations and impairments). Each batch groups the debit and credit lines for one Accounting event and can be uploaded to cifraHQ, the integrated Accounting system. The accountant or the system administrator mainly uses this screen to check, upload and monitor the status of pending batches.
Accounting > Journal Batches
URL: /Accounting/journal-batches
| Term | Meaning |
|---|---|
| Journal batch | The set of journal entries (debits and credits) generated automatically by a fixed asset event. |
| Journal line | Each individual row of the entry, tied to a GL account code, with its debit or credit amount. |
| Batch status | Where the batch sits in the upload cycle: pending, sent, confirmed or failed. |
| Event type | The event that produced the batch: depreciation, disposal, revaluation or impairment. Acquisition and transfer also appear as event types in the lists, but no process creates batches for them today. |
| cifraHQ | The external Accounting system the batch is uploaded to for final recording. |
| Dry run | When the company has no cifraHQ endpoint configured, the upload is simulated: the batch moves to Sent but cifraHQ never receives it. |
Clicking a batch's Event link opens its own detail screen, with everything in one place (/Accounting/journal-batches/<id>):
An Out of balance batch means the debits do not equal the credits; review it before sending it to Accounting.
If the company has no cifraHQ endpoint configured (per your account's Settings), the system runs a dry run: the batch moves to Sent but cifraHQ does not receive it. Upload Pending and Retry only handle batches in Pending or Failed status, so a batch marked Sent by a dry run is not sent to cifraHQ later. Configure and test the endpoint before you upload batches you want delivered.
| Field | Type | Required | Description | Validation |
|---|---|---|---|---|
| Event | Text link | - | The Accounting event type that produced the batch. Possible values: Asset Acquisition, Depreciation, Disposal, Revaluation, Impairment, Transfer. Clicking it opens the batch's detail screen. | Read-only. |
| Posted Date | Date | - | The date the Accounting event was recorded. Format: month day, year (for example, Jun 01, 2025). | Read-only. |
| Status | Badge | - | The batch's current status in the upload cycle: Pending, Sent, Confirmed, Failed. | Read-only. |
| Total Debit | Numeric | - | The sum of every debit in the batch, in the company's currency. Two decimals. | Read-only. |
| Total Credit | Numeric | - | The sum of every credit in the batch, in the company's currency. Two decimals. | Read-only. |
| Actions | Button | - | Shows the Retry button only when the batch's status is Failed. This column cannot be sorted or filtered. | Read-only. |
| Field | Type | Required | Description | Validation |
|---|---|---|---|---|
| Account | Text | - | The GL account code this line affects (for example 1-2-001). | Read-only. |
| Description | Text | - | A description of the line's purpose (for example, the depreciation period and asset model, or the code of a disposed asset). | Read-only. |
| Debit | Numeric | - | The amount debited on this line. Two decimals; zero when the line is a credit. | Read-only. |
| Credit | Numeric | - | The amount credited on this line. Two decimals; zero when the line is a debit. | Read-only. |
Available to users with access to the Accounting module, as configured by your administrator.
Journal batches are generated automatically when a depreciation run or another Accounting event (a disposal, a revaluation and so on) is processed. Batches cannot be created by hand on this screen. If the table is empty, the system shows: "Post a depreciation run to generate journal batches."
If your account has access to several Companies, switching company in the top selector refreshes the batch list automatically to show only the selected company's batches.
| Symptom | Likely cause | Resolution |
|---|---|---|
| The table is empty | No Depreciation runs or other Accounting events have been processed. | Run a depreciation run under Accounting > Depreciation runs and come back to this screen. |
| A batch changed to Sent after clicking Upload Pending, but cifraHQ shows nothing | The company has no cifraHQ endpoint configured, so the upload was a dry run. | Set the endpoint under Settings > Integration before uploading batches you want delivered. A batch already marked Sent is not uploaded again from this screen; contact P4 Software support. |
| A batch moved to Failed after clicking Upload Pending | cifraHQ rejected the request or a network error occurred. | Read the message in the batch's upload history, fix the cause and click Retry. |
| The Retry button does not appear in the Actions column | The batch's status is not Failed; the button only shows for failed batches. | Confirm the batch's status in the Status column. |
| Total Debit and Total Credit do not match | It may point to a problem in how the entry was generated. | Review the batch's journal lines by clicking the Event column link, and check with your accountant. |
| The notification shows "0 batch(es) uploaded" after clicking Upload Pending | There were no Pending batches at the time of the action. | Check the statuses in the table; every batch may already have been sent or confirmed. |
Was this page helpful?