---
title: "JournalTransactionAttachmentsByPeriodOrDateV2 (Visma.net Financials)"
description: "Journal Transaction Attachments by Period or Date"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.JournalTransactionV2.JournalTransactionAttachmentsByPeriodOrDateV2
original: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.JournalTransactionV2.JournalTransactionAttachmentsByPeriodOrDateV2
updated: 2026-11-01T17:49:50Z
license: https://documentation.invantive.eu/en/
---

# JournalTransactionAttachmentsByPeriodOrDateV2: Visma.net Financials Journal Transaction Attachments by Period or Date

`read only` `REST`

- Catalog: `VismaNet`
- Schema: `JournalTransactionV2`
- Label: Journal Transaction Attachments by Period or Date

Get a range of Journal Transactions - ScreenId=GL301000. 
On this particular endpoint, pagesize and totalcount denotes number of journaltransaction lines. 
When using pagination, the transactions for one specific batch can be split into several responses. 
Please use a page size lower or equal to the allowed max page size which is returned under metadata. 
If pagesize is greater than the max page size, it will be limited to max page size.
Data for Journal Transaction

Can only retrieve data.

## Summary

Data for Journal Transaction

## API Source

- Endpoint: `/v2/journaltransaction`
- Operation: `get /v2/journaltransaction`

## Performance Characteristics

| Characteristic | Value |
|---|---:|
| Average access latency (ms) | 155 |
| Full scan rows per minute | 29,100 |
| Point query rows per minute | 387 |

The result can be cached on the client.

## Parameters

| Name | Data Type | Required | Default | Documentation |
|---|---|:---:|---|---|
| `branch` | `` | [ ] |  | Branch to query data for. |
| `expandAttachments` | `` | [ ] |  | If true, includes all attachments for batch. Default is false. |
| `lastModifiedDateTime` | `` | [ ] |  | This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present. Mandatory if 'PeriodId' is not provided.   Accepted format: * ```yyyy-MM-dd``` * ```yyyy-MM-dd HH:mm:ss``` * ```yyyy-MM-dd HH:mm:ss.FFF``` * ```yyyy-MM-ddTHH:mm:ss``` * ```yyyy-MM-ddTHH:mm:ss.FFF``` |
| `module` | `` | [ ] |  | Module to query data for. Allowed values: GL, AP, AR, CM, CA, IN, DR, FA, PM |
| `periodId` | `` | [ ] |  | Financial Period to query data for. Mandatory if 'LastModifiedDateTime' not provided. Format: YYYYPP |
| `status` | `` | [ ] |  | Journal transaction status to query data for. Available statuses : Hold, Balanced, Unposted, Posted, Voided, Scheduled, Unreleased. (Values: Hold, Balanced, Unposted, Posted, Voided, Scheduled, Unreleased) |

## Table Columns

The columns of the table `JournalTransactionAttachmentsByPeriodOrDateV2` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `COMPANY_CODE` | `varchar2(30)` | Company Code | [x] | writable | Partition code, segmenting the data. |
| `COMPANY_NAME` | `varchar2(240)` | Company Name | [x] | writable | Name of the partition. |
| `autoReversing` | `char` | itgen_vnet_autoreversing | [ ] | filters on the platform, writable, `::ancestor.autoReversing` | The top part &gt; Automatic reversing &gt; A check box that indicates (if selected) that the batch is auto-reversing. |
| `batchNumber` | `varchar2` | Batch Number | [ ] | filters on the platform, writable, `::ancestor.batchNumber` | The top part &gt; Batch number &gt; The unique ID of the batch, which is generated by the numbering sequence assigned to batches in the GL102000 window. |
| `branch` | `varchar2` | Branch | [ ] | filters on the platform, writable, `::ancestor.branch` | The top part &gt; Branch &gt;  The branch to which this batch is related. This field is available if your company is set up with branches. |
| `controlTotal` | `double` | Total for Control | [ ] | filters on the platform, writable, `::ancestor.controlTotal` | The top part &gt; Control total &gt; The control total of the batch, which is used for batch status validation. |
| `controlTotalInCurrency` | `double` | itgen_vnet_controltotalincurrency | [ ] | filters on the platform, writable, `::ancestor.controlTotalInCurrency` | Background calculation giving you the Control total in your default currency. This field is applicable if the amount is given in another currency than your default. |
| `createVatTransaction` | `char` | itgen_vnet_createvattransaction | [ ] | filters on the platform, writable, `::ancestor.createVatTransaction` | The top part &gt; Create VAT transactions &gt; A check box that indicates (if selected) that a VAT-related transaction can be created manually; select this check box when you begin to create the transaction. |
| `creditTotal` | `double` | itgen_vnet_credittotal | [ ] | filters on the platform, writable, `::ancestor.creditTotal` | The top part &gt; Credit total &gt; The total of transaction credit amounts for the batch; the value is calculated automatically. |
| `creditTotalInCurrency` | `double` | itgen_vnet_credittotalincurrency | [ ] | filters on the platform, writable, `::ancestor.creditTotalInCurrency` | Background calculation giving you the Credit total in your default currency. This field is applicable if the amount is given in a another currency than your default. |
| `currencyId` | `varchar2` | Currency ID | [ ] | filters on the platform, writable, `::ancestor.currencyId` | The top part &gt; Currency &gt; The currency used for all the journal transactions in the selected batch. |
| `debitTotal` | `double` | Debit Total | [ ] | filters on the platform, writable, `::ancestor.debitTotal` | The top part &gt; Debit total &gt; The total of transaction debit amounts for the batch; the value is calculated automatically. |
| `debitTotalInCurrency` | `double` | itgen_vnet_debittotalincurrency | [ ] | filters on the platform, writable, `::ancestor.debitTotalInCurrency` | Background calculation giving you the Debit total in your default currency. This field is applicable if the amount is given in another currency than your default. |
| `description` | `varchar2` | Description | [ ] | filters on the platform, writable, `::ancestor.description` | The top part &gt; Description &gt; A description of the batch. |
| `errorInfo` | `varchar2` | Error Message | [ ] | filters on the platform, writable, `::ancestor.errorInfo` |  |
| `exchangeRate` | `double` | Exchange Rate | [ ] | filters on the platform, writable, `::ancestor.exchangeRate` | Ingformation collected from the system to calculate currency amount. |
| `financialPeriod` | `varchar2` | Financial Period | [ ] | filters on the platform, writable, `::ancestor.financialPeriod` | Mandatory field: The top part Post period* &gt; The financial period to which the transactions should be posted. Format YYYYMM. |
| `hold` | `char` | Hold | [ ] | filters on the platform, writable, `::ancestor.hold` | The top part &gt; Hold &gt; A check box that indicates (if selected) that the batch has the On hold status and cannot be released or posted. You can clear the check box only if the batch has total debits equal to total credits. |
| `id` | `guid` | ID | [ ] | writable, `id` | The ID of the attachment |
| `lastModifiedDateTime` | `datetime` | Last Modified | [ ] | filters on the platform, writable, `::ancestor.lastModifiedDateTime` | System generated information. |
| `ledger` | `varchar2` | Ledger | [ ] | filters on the platform, writable, `::ancestor.ledger` | Mandatory field: The top part &gt; Ledger* &gt; The unique ID of the ledger to which batch transactions are posted. By default, it is the default posting ledger specified for the branch in the GL101010 window, but another posting ledger can be selected. |
| `ledgerDescription` | `varchar2` | Ledger Description | [ ] | filters on the platform, writable, `::ancestor.ledgerDescription` | Mandatory field: The top part &gt; Ledger* &gt; Click the magnifier &gt; The description of the ledger to which batch transactions are posted. By default, it is the default posting ledger specified for the branch in the GL101010 window, but another posting ledger can be selected. |
| `metadata_maxPageSize` | `int64` | Metadata Max Pagesize | [ ] | filters on the platform, writable, `::ancestor.metadata.maxPageSize` |  |
| `metadata_totalCount` | `int64` | Total Count | [ ] | filters on the platform, writable, `::ancestor.metadata.totalCount` |  |
| `module` | `varchar2` | Module | [ ] | filters on the platform, writable, `::ancestor.module` | The top part &gt; Workspace &gt; The workspace where the batch originates. New batches can be created only for General ledger. |
| `name` | `varchar2` | Name | [ ] | writable, `name` | The name of the attachment. |
| `originalBatchNumber` | `varchar2` | itgen_vnet_originalbatchnumber | [ ] | filters on the platform, writable, `::ancestor.originalBatchNumber` | The top part &gt; Orig. batch number &gt; For a scheduled or auto-reversing batch, the reference number of the batch used as a template. |
| `postPeriod` | `varchar2` | Post Period | [ ] | filters on the platform, writable, `::ancestor.postPeriod` | Mandatory field: The top part &gt; Post period* &gt; The financial period to which the transactions recorded in the document should be posted. Format MMYYYY. |
| `reversingEntry` | `char` | itgen_vnet_reversingentry | [ ] | filters on the platform, writable, `::ancestor.reversingEntry` | The top part &gt; Reversing entry &gt; A check box that indicates (if selected) that the batch is a reversing batch. The Orig.batch number field displays the ID of the batch that was reversed by this batch. |
| `revision` | `int32` | Revision | [ ] | writable, `revision` | The version of the attachment. |
| `skipVatAmountValidation` | `char` | itgen_vnet_skipvatamountvalidation | [ ] | filters on the platform, writable, `::ancestor.skipVatAmountValidation` | The top part &gt; Skip VAT amount validation &gt; A check box that (if selected) causes automatic validation of a VAT-related transaction that you create manually to be skipped. |
| `status` | `varchar2` | Status | [ ] | filters on the platform, writable, `::ancestor.status` | The top part &gt; Status &gt; The current status of the batch. The status defines what processing can be applied to the batch. The following options are available: On hold, Balanced, Scheduled, Unposted, Posted, Void. |
| `timeStamp` | `blob` | Timestamp | [ ] | filters on the platform, writable, `::ancestor.timeStamp` | Identifier that represents a specific version of the resource. It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers) |
| `transactionCode` | `varchar2` | itgen_vnet_transactioncode | [ ] | filters on the platform, writable, `::ancestor.transactionCode` |  |
| `transactionCodeDescription` | `varchar2` | itgen_vnet_transactioncodedescription | [ ] | filters on the platform, writable, `::ancestor.transactionCodeDescription` | The Table part &gt; Transaction description &gt; A description of the transaction or any comments relevant to the transaction. |
| `transactionDate` | `datetime` | itgen_vnet_transactiondate | [ ] | filters on the platform, writable, `::ancestor.transactionDate` | Mandatory field: The top part &gt; Transaction date* &gt; The date when the batch was created, which relates to the transaction dates of the journal entries. |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Visma.net Financials](/en/release-notes/drivers?driver=visma-net-financials)

