Please enable JavaScript to view this site.

Made in EU
Visma.net Financials Forums

Navigation: Catalog: VismaNet > Schemas > Schema: ExpenseReceipt > Tables

ExpenseReceipts: Visma.net Financials Expense Receipts

Get a range of Expense Receipts, a filter needs to be specified. ScreenId=EP301020

Catalog: VismaNet

Schema: ExpenseReceipt

Label: Expense Receipts

Retrieve: true

Insert: true

Update: false

Delete: false

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function ExpenseReceipts. 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

Default Value

Documentation

claimedBy

 

☐

 

Identifies the employee from the document

customer

 

☐

 

Identifies the customer from the document

date

 

☐

 

The date of the document

dateCondition

 

☐

 

 

inventory

 

☐

 

Identifies the inventory item from the document

invoiceable

 

☐

 

If the document is invoiceable

project

 

☐

 

Identifies the project from the document

projectTask

 

☐

 

Filter on Task ID.

status

 

☐

 

The status of the document. (Values: Open, Pending, Approved, Rejected, Released)

 

Columns of Table Function

The columns of the table function ExpenseReceipts 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.

Name

Data Type

Label

Required

Documentation

branch_name

varchar2

Branch Name

☐

Click the magnifier. > The name.

branch_number

varchar2

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

varchar2

 

☐

Address 1 > The first line of the customer's/supplier's/company's/employee's contact address.

claimedBy_address_addressLine2

varchar2

 

☐

Address 2 > The second line of the address.

claimedBy_address_addressLine3

varchar2

 

☐

Address 3 > The third line of the address.

claimedBy_address_city

varchar2

 

☐

City > The city.

claimedBy_address_country_errorInfo

varchar2

 

☐

 

claimedBy_address_country_id

varchar2

 

☐

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

varchar2

 

☐

Mandatory field: Country name* > The complete name of the country.

claimedBy_address_county_id

varchar2

 

☐

Click the magnifier > The identifier

claimedBy_address_county_name

varchar2

 

☐

Click the magnifier > The displayed name

claimedBy_address_postalCode

varchar2

 

☐

Postcode > The postcode.

claimedBy_branch_name

varchar2

 

☐

Click the magnifier. > The name.

claimedBy_branch_number

varchar2

 

☐

Click the magnifier. > The identifier.

claimedBy_calendarID

varchar2

 

☐

 

claimedBy_contact_attention

varchar2

 

☐

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

varchar2

 

☐

Email > The email address of the customer/supplier/company as a business entity.

claimedBy_contact_employeeContact

varchar2

 

☐

Employee contact > The link to the contact record associated with the employee.

claimedBy_contact_fax

varchar2

 

☐

Fax > The fax number.

claimedBy_contact_firstName

varchar2

 

☐

First name > The first name of the employee.

claimedBy_contact_lastName

varchar2

 

☐

Mandatory field: Last name* > The last name of the employee.

claimedBy_contact_midName

varchar2

 

☐

Middle name > The middle name of the employee.

claimedBy_contact_name

varchar2

 

☐

Name > The legal name of to appear on the documents.

claimedBy_contact_phone1

varchar2

 

☐

Phone 1 > The default phone number.

claimedBy_contact_phone2

varchar2

 

☐

Phone 2 > An additional phone number.

claimedBy_contact_phone3

varchar2

 

☐

Phone 3 > An additional phone number of the employee.

claimedBy_contact_title

varchar2

 

☐

Title > The courtesy title to be used for the employee.

claimedBy_contact_web

varchar2

 

☐

Web > The website of the company, if one exists.

claimedBy_department

varchar2

 

☐

Mandatory field: General information tab > Employee section > Department* > The department the employee works for.

claimedBy_employeeClass_description

varchar2

 

☐

Click on the magnifier. > The description.

claimedBy_employeeClass_id

varchar2

 

☐

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

varchar2

 

☐

 

claimedBy_employeeName

varchar2

 

☐

The top part > Employee name > The name of this employee.

claimedBy_employeeNumber

varchar2

 

☐

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

varchar2

 

☐

 

claimedBy_lastModifiedDateTime

datetime

 

☐

 

claimedBy_metadata_maxPageSize

int64

 

☐

 

claimedBy_metadata_totalCount

int64

 

☐

 

claimedBy_status

varchar2

 

☐

Mandatory field: The top part > Status > The status of the employee. The following options are available: Active, On hold, Hold payments, Inactive, One-time.

claimedBy_timeStamp

blob

 

☐

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)

COMPANY_CODE

varchar2(30)

Company Code

☑

Partition code, segmenting the data.

COMPANY_NAME

varchar2(240)

Company Name

☑

Name of the partition.

currency_description

varchar2

Currency Description

☐

Click on the magnifier. > The description.

currency_id

varchar2

Currency ID

☐

Click on the magnifier. > The identifier.

customer_name

varchar2

Customer Name

☐

Click the magnifier. > The name.

customer_number

varchar2

Customer Number

☐

 

date

datetime

Date

☐

Both tabs > Date > The date of the expense receipt.

description

varchar2

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

varchar2

Expense Account Description

☐

Name of item/description

expenseAccount_number

varchar2

Expense Account Number

☐

Number of item

expenseAccount_type

varchar2

Expense Account Type

☐

 

expenseClaim_description

varchar2

Expense Claim Description

☐

Name of item/description

expenseClaim_number

varchar2

Expense Claim Number

☐

Number of item

expenseSub_active

char

 

☐

 

expenseSub_description

varchar2

 

☐

Click on the magnifier. > The description.

expenseSub_id

varchar2

 

☐

Click on the magnifier. > The identifier.

image_id

guid

Image ID

☐

The ID of the attachment

image_name

varchar2

Image Name

☐

The name of the attachment.

image_revision

int32

Image Revision

☐

The version of the attachment.

internalId

int32

Internal ID

☐

 

inventory_description

varchar2

Inventory Description

☐

Name of item/description

inventory_number

varchar2

Inventory Number

☐

Number of item

invoiceable

char

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

varchar2

Location Description

☐

Click on the magnifier. > The description.

location_id

varchar2

Location ID

☐

Click on the magnifier. > The identifier.

project_description

varchar2

Project Description

☐

Click on the magnifier. > The description.

project_id

varchar2

Project ID

☐

Click on the magnifier. > The identifier.

project_internalId

int32

 

☐

The internal identifier.

projectTask_description

varchar2

Project Task Description

☐

Click on the magnifier. > The description.

projectTask_id

varchar2

Project Task ID

☐

Click on the magnifier. > The identifier.

projectTask_internalId

int32

 

☐

The internal 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

varchar2

Receipt ID

☐

The top part > Employee > The identifier of the employee whose expense receipts you want to manage.

refNbr

varchar2

Reference Number

☐

Both tabs > Ref. no. > The reference number, which usually matches the number of the original receipt.

salesAccount_description

varchar2

Sales Account Description

☐

Name of item/description

salesAccount_number

varchar2

Sales Account Number

☐

Number of item

salesAccount_type

varchar2

Sales Account Type

☐

 

salesSub_active

char

 

☐

 

salesSub_description

varchar2

 

☐

Click on the magnifier. > The description.

salesSub_id

varchar2

 

☐

Click on the magnifier. > The identifier.

status

varchar2

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

varchar2

 

☐

Name of item/description

taxCategory_number

varchar2

 

☐

Number of item

taxTotal

double

Tax Total

☐

The top part > VAT total > The total amount of VAT or taxes calculated for the expense receipt.

timeStamp

blob

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)

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

varchar2

Unit of Measure

☐

Receipt details tab > Expense details section > UoM > The unit of measure of the expense item.

 

X

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.

  
Disclaimer