---
title: "ProjectTransactions (Visma.net Financials)"
description: "Project Transactions"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.ProjectTransaction.ProjectTransactions
original: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.ProjectTransaction.ProjectTransactions
updated: 2026-11-01T17:49:50Z
license: https://documentation.invantive.eu/en/
---

# ProjectTransactions: Visma.net Financials Project Transactions

`insert` `update` `REST`

- Catalog: `VismaNet`
- Schema: `ProjectTransaction`
- Primary Keys: `refNbr`
- Label: Project Transactions

Get a range of Project transaction documents - ScreenId=PM304000
Data for Project transactions

Can retrieve data and change data using `insert` and `update`.

## Summary

Data for Project transactions

## API Source

- Endpoint: `/v1/projecttransaction`
- Operation: `get /v1/projecttransaction`

## 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 |
|---|---|:---:|---|---|
| `billable` | `` | [ ] |  | Filter invoiceable project tasks. |
| `branch` | `` | [ ] |  | Filter on branch for the project transation. |
| `createdDateTime` | `` | [ ] |  | This value, generated by the system, indicates the creation date and time. Use it to retrieve all records that have been created since that time, up to the present.  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```  _Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__. |
| `createdDateTimeCondition` | `` | [ ] |  | This value represents the condition to be applied when retrieving records.  Accepted values (without the single quotes): * '&gt;' for greater than * '&lt;' for less than * '&gt;=' for greater than or equal * '&lt;=' for less than or equal  _Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__. |
| `date` | `` | [ ] |  | Filter on the registration date for the project transaction. |
| `expandNote` | `` | [ ] |  | Expands project transaction notes |
| `fromPeriod` | `` | [ ] |  | Mandatory. Start date for the task. |
| `greaterThanValue` | `` | [ ] |  | Greater than value. The item which is the object for this, varies from API to API. |
| `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.  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```  _Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__. |
| `lastModifiedDateTimeCondition` | `` | [ ] |  | This value represents the condition to be applied when retrieving records.  Accepted values (without the single quotes): * '&gt;' for greater than * '&lt;' for less than * '&gt;=' for greater than or equal * '&lt;=' for less than or equal  _Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__. |
| `module` | `` | [ ] |  | Select to filter on module; e.g. AR, AP, IN etc. (Values: ModuleGL, ModuleAP, ModuleAR, ModuleCA, ModuleCM, ModuleIN, ModuleSO, ModulePO, ModuleDR, ModuleFA, ModuleEP, ModulePM, ModuleTX, ModuleCR) |
| `project` | `` | [ ] |  | Filter on project ID. |
| `projectTask` | `` | [ ] |  | Filter on Task ID. |
| `status` | `` | [ ] |  | The status of the document. (Values: Hold, Balanced, Released) |
| `toPeriod` | `` | [ ] |  | Mandatory. End date for the task. |

## Table Columns

The columns of the table `ProjectTransactions` 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. |
| `description` | `varchar2` | Description | [ ] | filters on the platform, writable, `description` | The top part &gt; Description &gt; The description provided for the transaction. |
| `errorInfo` | `varchar2` | Error Message | [ ] | filters on the platform, writable, `errorInfo` |  |
| `metadata_maxPageSize` | `int64` | Metadata Max Pagesize | [ ] | filters on the platform, writable, `metadata.maxPageSize` |  |
| `metadata_totalCount` | `int64` | Total Count | [ ] | filters on the platform, writable, `metadata.totalCount` |  |
| `module` | `varchar2` | Module | [ ] | filters on the platform, writable, `module` | The top part &gt; Module &gt; The module you create the transactions in. |
| `note` | `varchar2` | Note | [ ] | filters on the platform, writable, `note` |  |
| `origDocNbr` | `varchar2` | Original Document Number | [ ] | filters on the platform, writable, `origDocNbr` | The top part &gt; Orig. doc. no. &gt; The reference number of the underlying document for the transaction. |
| `origDocType` | `varchar2` | Original Document Type | [ ] | filters on the platform, writable, `origDocType` | The top part &gt; Orig. doc. no. &gt; The type of the document the transaction is based on. It has one of the following values: Allocation, Time card, Case, Expense claim, Allocation reversal, Reversal, Credit note. |
| `refNbr` | `varchar2` | Reference Number | [ ] | filters on the platform, writable, `refNbr` | The top part &gt; Ref. no. &gt; The reference number of the transaction. |
| `status` | `varchar2` | Status | [ ] | filters on the platform, writable, `status` | The top part &gt; Status &gt; The status of the transaction. The following statuses are possible: Balanced, Released. |
| `timeStamp` | `blob` | Timestamp | [ ] | filters on the platform, writable, `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) |



## 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)

