Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Odoo API Data Model

Navigation: Schema: account > Tables

batch_payment

Batch Payment

Catalog: Odoo

Schema: account

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

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

Table Columns

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

Name

Data Type

Label

Required

Documentation

activity_calendar_event_id_label

string

 

☐

 

activity_calendar_event_id

string

 

☐

 

activity_date_deadline

datetime

Next Activity Deadline

☐

 

activity_exception_decoration

string

Activity Exception Decoration

☐

Type of the exception activity on record.

activity_exception_icon

string

Icon

☐

Icon to indicate an exception activity.

activity_ids

string

 

☐

 

activity_state

string

Activity State

☐

Status based on activitiesOverdue: Due date is already passedToday: Activity date is todayPlanned: Future activities.

activity_summary

string

Next Activity Summary

☐

 

activity_type_icon

string

Activity Type Icon

☐

Font awesome icon e.g. fa-tasks

activity_type_id_label

string

 

☐

 

activity_type_id

string

 

☐

 

activity_user_id_label

string

 

☐

 

activity_user_id

string

 

☐

 

amount_residual_currency

decimal

Amount Residual Currency

☐

 

amount_residual

decimal

Amount Residual

☐

 

amount

decimal

Amount

☐

 

available_payment_method_ids

string

 

☐

 

batch_type

string

Batch Type

☑

 

company_currency_id_label

string

 

☐

 

company_currency_id

string

 

☐

 

create_date

datetime

Created on

☐

 

create_uid_label

string

 

☐

 

create_uid

string

 

☐

 

currency_id_label

string

 

☐

 

currency_id

string

 

☐

 

date

datetime

Date

☑

 

display_name

string

Display Name

☐

 

export_file_create_date

datetime

Generation Date

☐

Creation date of the related export file.

export_file

byte[]

File

☐

Export file related to this batch

export_filename

string

File Name

☐

Name of the export file generated for this batch

file_generation_enabled

boolean

File Generation Enabled

☐

Whether or not this batch payment should display the 'Generate File' button instead of 'Print' in form view.

has_message

boolean

Has Message

☐

 

id

int32

ID

☐

 

journal_id_label

string

 

☐

 

journal_id

string

 

☐

 

message_attachment_count

int32

Attachment Count

☐

 

message_follower_ids

string

 

☐

 

message_has_error_counter

int32

Number of errors

☐

Number of messages with delivery error

message_has_error

boolean

Message Delivery error

☐

If checked, some messages have a delivery error.

message_has_sms_error

boolean

SMS Delivery error

☐

If checked, some messages have a delivery error.

message_ids

string

 

☐

 

message_is_follower

boolean

Is Follower

☐

 

message_main_attachment_id_label

string

 

☐

 

message_main_attachment_id

string

 

☐

 

message_needaction_counter

int32

Number of Actions

☐

Number of messages which requires an action

message_needaction

boolean

Action Needed

☐

If checked, new messages require your attention.

message_partner_ids

string

 

☐

 

my_activity_date_deadline

datetime

My Activity Deadline

☐

 

name

string

Reference

☑

 

payment_ids

string

 

☐

 

payment_method_code

string

Code

☐

 

payment_method_id_label

string

 

☐

The payment method used by the payments in this batch.

payment_method_id

string

 

☐

The payment method used by the payments in this batch.

sct_batch_booking

boolean

SCT Batch Booking

☐

Request batch booking from the bank for the related bank statements.

sct_generic

boolean

Sct Generic

☐

Technical feature used during the file creation. A SEPA message is said to be 'generic' if it cannot be considered as a standard european credit transfer. That is if the bank journal is not in €, a transaction is not in € or a payee is not identified by an IBAN account number.

state

string

State

☐

 

website_message_ids

string

 

☐

Website communication history

write_date

datetime

Last Updated on

☐

 

write_uid_label

string

 

☐

 

write_uid

string

 

☐

 

 

01-03-2023 15:29 Version 22.1.135-BETA+3826

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