Navigation: Schema: Views > Views

JournalTransactions

Catalog: VismaNet

Schema: Views

This is a read-only view. The Visma.net Financials API may not support changing the data or the Invantive SQL driver for Visma.net Financials does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Visma.net Financials API.

View Columns

The columns of the view JournalTransactions are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
autoReversing	boolean		☐	The top part > Automatic reversing > A check box that indicates (if selected) that the batch is auto-reversing.
batchNumber	string	Batch Number	☐	The top part > Batch number > The unique ID of the batch, which is generated by the numbering sequence assigned to batches in the GL102000 window.
branch	string	Branch	☐	The top part > Branch > The branch to which this batch is related. This field is available if your company is set up with branches.
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
controlTotal	double	Total for Control	☐	The top part > Control total > The control total of the batch, which is used for batch status validation.
controlTotalInCurrency	double		☐	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	boolean		☐	The top part > Create VAT transactions > 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		☐	The top part > Credit total > The total of transaction credit amounts for the batch; the value is calculated automatically.
creditTotalInCurrency	double		☐	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	string	Currency ID	☐	The top part > Currency > The currency used for all the journal transactions in the selected batch.
debitTotal	double	Debit Total	☐	The top part > Debit total > The total of transaction debit amounts for the batch; the value is calculated automatically.
debitTotalInCurrency	double		☐	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	string	Description	☐	The top part > Description > A description of the batch.
errorInfo	string	Error Message	☐
exchangeRate	double	Exchange Rate	☐	Ingformation collected from the system to calculate currency amount.
financialPeriod	string	Period	☐	The table > Period > The period no and the year.
financialYear	int32	Year	☐	Mandatory field: The top part > Financial year* > The financial year.
hold	boolean	Hold	☐	The top part > Hold > 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.
lastModifiedDateTime	datetime	Last Modified	☐	System generated information.
ledger	string	Ledger	☐	Mandatory field: The top part > Ledger* > 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	string	Ledger Description	☐	Mandatory field: The top part > Ledger* > Click the magnifier > 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_totalCount	int64	Total Count	☐
module	string	Module	☐	The top part > Workspace > The workspace where the batch originates. New batches can be created only for General ledger.
originalBatchNumber	string		☐	The top part > Orig. batch number > For a scheduled or auto-reversing batch, the reference number of the batch used as a template.
postPeriod	string	Post Period	☐	Mandatory field: The top part > Post period* > The financial period to which the transactions recorded in the document should be posted. Format MMYYYY.
reversingEntry	boolean		☐	The top part > Reversing entry > 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.
skipVatAmountValidation	boolean		☐	The top part > Skip VAT amount validation > A check box that (if selected) causes automatic validation of a VAT-related transaction that you create manually to be skipped.
status	string	Status	☐	The top part > Status > 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.
transactionCode	string		☐
transactionCodeDescription	string		☐	The Table part > Transaction description > A description of the transaction or any comments relevant to the transaction.
transactionDate	datetime		☐	Mandatory field: The top part > Transaction date* > The date when the batch was created, which relates to the transaction dates of the journal entries.

22-12-2022 21:03 Version 22.1.101-BETA+3681

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Visma.net Financials API Data Model Visma.net Financials Forums

JournalTransactions

View Columns

Important Safety and Usage Information