Navigation: Schema: ExpenseReceipt > Tables

ExpenseReceiptByNumber: Visma.net Financials Expense Receipt by Number

Get a specific ExpenseReceipt

Catalog: VismaNet

Schema: ExpenseReceipt

Label: Expense Receipt by Number

The data in this table is partitioned per value of the COMPANY_CODE column.

This is a read-only table function. 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.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function ExpenseReceiptByNumber. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name	Data Type	Required	Documentation
COMPANY_CODE	string	☐	Partition to retrieve data from.
erp-api-background	string	☐	If a URL value is provided, then API endpoint will be queued and executed in background. When the execution of the background operation is finished, the system will POST the response to the specified URL. The endpoint itself responds in this case with a 202-Accepted status and a reference to a state document for the background operation.
receiptNumber	string	☑	Identifies the ExpenseReceipt

Columns of Table Function

The columns of the table function ExpenseReceiptByNumber are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
branch_name	string	Branch Name	☐	Click the magnifier. > The name.
branch_number	string	Branch Number	☐	Click the magnifier. > The identifier.
claimAmount	double	Claim Amount	☐	Receipt details tab > Expense details section > Expense claim > The expense claim with which the expense receipt is associated.
claimedBy_address_addressId	int32		☐
claimedBy_address_addressLine1	string		☐	Address 1 > The first line of the customer's/supplier's/company's/employee's contact address.
claimedBy_address_addressLine2	string		☐	Address 2 > The second line of the address.
claimedBy_address_addressLine3	string		☐	Address 3 > The third line of the address.
claimedBy_address_city	string		☐	City > The city.
claimedBy_address_country_errorInfo	string		☐
claimedBy_address_country_id	string		☐	Mandatory field: Country ID* > The unique two-letter country ID according to international standard ISO 3166.
claimedBy_address_country_metadata_maxPageSize	int64		☐
claimedBy_address_country_metadata_totalCount	int64		☐
claimedBy_address_country_name	string		☐	Mandatory field: Country name* > The complete name of the country.
claimedBy_address_county_id	string		☐	Click the magnifier > The identifier
claimedBy_address_county_name	string		☐	Click the magnifier > The displayed name
claimedBy_address_postalCode	string		☐	Postcode > The postcode.
claimedBy_branch_name	string		☐	Click the magnifier. > The name.
claimedBy_branch_number	string		☐	Click the magnifier. > The identifier.
claimedBy_calendarID	string		☐
claimedBy_contact_attention	string		☐	Attention > The attention line as it is used in your customer's/supplier's/company's business letters. The intention of this line is to direct the letter to the right person if the letter is not addressed to any specific person.
claimedBy_contact_contactId	int32		☐
claimedBy_contact_email	string		☐	Email > The email address of the customer/supplier/company as a business entity.
claimedBy_contact_employeeContact	string		☐	Employee contact > The link to the contact record associated with the employee.
claimedBy_contact_fax	string		☐	Fax > The fax number.
claimedBy_contact_firstName	string		☐	First name > The first name of the employee.
claimedBy_contact_lastName	string		☐	Mandatory field: Last name* > The last name of the employee.
claimedBy_contact_midName	string		☐	Middle name > The middle name of the employee.
claimedBy_contact_name	string		☐	Name > The legal name of to appear on the documents.
claimedBy_contact_phone1	string		☐	Phone 1 > The default phone number.
claimedBy_contact_phone2	string		☐	Phone 2 > An additional phone number.
claimedBy_contact_phone3	string		☐	Phone 3 > An additional phone number of the employee.
claimedBy_contact_title	string		☐	Title > The courtesy title to be used for the employee.
claimedBy_contact_web	string		☐	Web > The website of the company, if one exists.
claimedBy_department	string		☐	Mandatory field: General information tab > Employee section > Department* > The department the employee works for.
claimedBy_employeeClass_description	string		☐	Click on the magnifier. > The description.
claimedBy_employeeClass_id	string		☐	Click on the magnifier. > The identifier.
claimedBy_employeeId	int32		☐	Mandatory field: The top part > Employee ID* > The unique identifier, which is assigned to the employee in accordance with the configuration of the EMPLOYEE segmented key.
claimedBy_employeeLogin	string		☐
claimedBy_employeeName	string		☐	The top part > Employee name > The name of this employee.
claimedBy_employeeNumber	string		☐	General information tab > Employee settings section > Employee ref. no. > A reference number for the employee.
claimedBy_employeeUserId	guid		☐	Employee internal user ID. This is the ID of the user linked to the employee
claimedBy_errorInfo	string		☐
claimedBy_lastModifiedDateTime	datetime		☐
claimedBy_metadata_maxPageSize	int64		☐
claimedBy_metadata_totalCount	int64		☐
claimedBy_status	string		☐	Mandatory field: The top part > Status > The status of the employee. The following options are available: Active, On hold, Hold payments, Inactive, One-time.
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
currency_description	string	Currency Description	☐	Click on the magnifier. > The description.
currency_id	string	Currency ID	☐	Click on the magnifier. > The identifier.
customer_name	string	Customer Name	☐	Click the magnifier. > The name.
customer_number	string	Customer Number	☐
date	datetime	Date	☐	Both tabs > Date > The date of the expense receipt.
description	string	Description	☐	Open the receiptMandatory field: Receipt details tab > Expense details section > Description* > The expense description, which is displayed as a link.
employeePart	double		☐	Receipt details tab > Expense details section > Employee part > The part of the total amount that will not be paid back to the employee.
expenseAccount_description	string	Expense Account Description	☐	Name of item/description
expenseAccount_number	string	Expense Account Number	☐	Number of item
expenseAccount_type	string	Expense Account Type	☐
expenseClaim_description	string	Expense Claim Description	☐	Name of item/description
expenseClaim_number	string	Expense Claim Number	☐	Number of item
expenseSub_description	string		☐	Click on the magnifier. > The description.
expenseSub_id	string		☐	Click on the magnifier. > The identifier.
image_id	guid	Image ID	☐	The ID of the attachment
image_name	string	Image Name	☐	The name of the attachment.
image_revision	int32	Image Revision	☐	The version of the attachment.
internalId	int32	Internal ID	☐
inventory_description	string	Inventory Description	☐	Name of item/description
inventory_number	string	Inventory Number	☐	Number of item
invoiceable	boolean	Invoiceable	☐	Receipt details tab > Financial details section > Invoiceable > A check box that indicates (if selected) that the customer should be invoiced for the claim amount.
location_description	string	Location Description	☐	Click on the magnifier. > The description.
location_id	string	Location ID	☐	Click on the magnifier. > The identifier.
project_description	string	Project Description	☐	Click on the magnifier. > The description.
project_id	string	Project ID	☐	Click on the magnifier. > The identifier.
projectTask_description	string	Project Task Description	☐	Click on the magnifier. > The description.
projectTask_id	string	Project Task ID	☐	Click on the magnifier. > The identifier.
quantity	double	Quantity	☐	Receipt details tab > Expense details section > Quantity > The quantity of the expense item that the employee purchased according to the receipt.
receiptId	string	Receipt ID	☐	The top part > Employee > The identifier of the employee whose expense receipts you want to manage.
refNbr	string	Reference Number	☐	Both tabs > Ref. no. > The reference number, which usually matches the number of the original receipt.
salesAccount_description	string		☐	Name of item/description
salesAccount_number	string		☐	Number of item
salesAccount_type	string		☐
salesSub_description	string		☐	Click on the magnifier. > The description.
salesSub_id	string		☐	Click on the magnifier. > The identifier.
status	string	Status	☐	Receipt details tab > Expense details section > Expense claim status > The current status of the associated expense claim, which can be one of the following options: On hold, Pending apporval, Approved, Rejected, Released.
taxCategory_description	string		☐	Name of item/description
taxCategory_number	string		☐	Number of item
taxTotal	double	Tax Total	☐	The top part > VAT total > The total amount of VAT or taxes calculated for the expense receipt.
totalAmount	double	Total Amount	☐	Receipt details tab > Expense details section > Amount > The total amount of the receipt (for VAT-inclusive taxes), or the total amount before taxes (for VAT-exclusive taxes).
unitCost	double	Unit Cost	☐	Receipt details tab > Expense details section > Unit cost > The cost of one unit of the expense item.
uom	string	Unit of Measure	☐	Receipt details tab > Expense details section > UoM > The unit of measure of the expense item.

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

ExpenseReceiptByNumber: Visma.net Financials Expense Receipt by Number

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information