Navigation: Catalog: Teamleader > Schemas > Schema: V2 > Tables

InvoiceById: Teamleader Focus Invoice by ID

Catalog: Teamleader

Schema: V2

Primary Keys: id

Label: Invoice by ID

This is a read-only table function. The Teamleader Focus API may not support changing the data or the Invantive UniversalSQL driver for Teamleader Focus does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Teamleader Focus API.

Parameters of Table Function

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

Columns of Table Function

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

Name	Data Type	Label	Required	Documentation
c_ookpernotaris	char		☐
created_at	datetime	Created at	☑
currency	varchar2	Currency	☐
deal_id	varchar2	Deal ID	☐
deal_type	varchar2	Deal Type	☐
department_id	varchar2	Department ID	☐
department_type	varchar2	Department Type	☐
due_on	datetime	Due on	☐
expected_payment_method	varchar2	Expected Payment Method	☐
file_id	varchar2	File ID	☐
file_type	varchar2	File Type	☐
id	varchar2	ID	☑
invoice_date	datetime	Invoice Date	☐
invoice_number	varchar2	Invoice Number	☐	Unique number of the invoice, including year.
invoicee_customer_id	varchar2	Invoicee Customer ID	☑
invoicee_customer_type	varchar2	Invoicee Customer Type	☑
invoicee_for_attention_of_contact_id	varchar2	Invoice for Attention of Contact ID	☐
invoicee_for_attention_of_contact_type	varchar2	Invoice for Attention of Contact Type	☐
invoicee_for_attention_of_name	varchar2	Invoice for Attention of Name	☐
invoicee_name	varchar2	Invoicee Name	☑
invoicee_vat_number	varchar2	Invoicee VAT Number	☐
note	varchar2	Note	☐
on_hold_since	datetime	On Hold Since	☐
paid_at	datetime	Paid at	☐
paid	char	Paid	☑
payment_reference	varchar2	Payment Reference	☐
payment_term_days	decimal	Payment Term (days)	☐
payment_term_type	varchar2	Payment Term Type	☐
project_id	varchar2	Project ID	☐
purchase_order_number	varchar2	Purchase Order Number	☐
sent	char	Sent	☑
status	varchar2	Status	☑
total_due_amount	decimal	Total Due Amount	☐
total_due_currency	varchar2	Currency of Total Due Amount	☐
total_payable_amount	decimal	Total Payable Amount	☐
total_payable_currency	varchar2	Currency of Total Payable Amount	☐
total_tax_exclusive_amount	decimal	Total Amount excluding Taxes	☐
total_tax_exclusive_currency	varchar2	Currency of Total Amount excluding Taxes	☐
total_tax_inclusive_amount	decimal	Total Amount including Taxes	☐
total_tax_inclusive_currency	varchar2	Currency of Total Amount including Taxes	☐
updated_at	datetime	Updated At	☑

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.

Teamleader Focus API Data Model

InvoiceById: Teamleader Focus Invoice by ID

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information