Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: account > Tables

journal

Journal

Catalog: Odoo

Schema: account

Documentation:

Populate factory part for account.journal.

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 journal are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

account_control_ids

string

 

☐

 

account_online_account_id_label

string

 

☐

 

account_online_account_id

string

 

☐

 

account_online_link_id_label

string

 

☐

 

account_online_link_id

string

 

☐

 

account_online_link_state

string

State

☐

 

active

boolean

Active

☐

Set active to false to hide the Journal without removing it.

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

 

☐

 

alias_domain

string

Alias domain

☐

 

alias_id_label

string

 

☐

Send one separate email for each invoice.Any file extension will be accepted.Only PDF and XML files will be interpreted by Odoo

alias_id

string

 

☐

Send one separate email for each invoice.Any file extension will be accepted.Only PDF and XML files will be interpreted by Odoo

alias_name

string

Alias Name

☐

It creates draft invoices and bills by sending an email.

available_payment_method_ids

string

 

☐

 

bank_acc_number

string

Account Number

☐

 

bank_account_id_label

string

 

☐

 

bank_account_id

string

 

☐

 

bank_id_label

string

 

☐

 

bank_id

string

 

☐

 

bank_statements_source

string

Bank Feeds

☐

Defines how the bank statements will be registered

code

string

Short Code

☑

Shorter name used for display. The journal entries of this journal will also be named using this prefix by default.

color

int32

Color Index

☐

 

company_id_label

string

 

☐

Company related to this journal

company_id

string

 

☐

Company related to this journal

company_partner_id_label

string

 

☐

 

company_partner_id

string

 

☐

 

compatible_edi_ids

string

 

☐

EDI format that support moves in this journal

country_code

string

Country Code

☐

The ISO country code in two chars. You can use this field for quick search.

create_date

datetime

Created on

☐

 

create_uid_label

string

 

☐

 

create_uid

string

 

☐

 

currency_id_label

string

 

☐

The currency used to enter statement

currency_id

string

 

☐

The currency used to enter statement

default_account_id_label

string

 

☐

 

default_account_id

string

 

☐

 

default_account_type

string

Default Account Type

☐

 

display_name

string

Display Name

☐

 

edi_format_ids

string

 

☐

Send XML/EDI invoices

entries_count

int32

Entries Count

☐

 

expiring_synchronization_date

datetime

Expiring Synchronization Date

☐

Date when the consent for this connection expires

expiring_synchronization_due_day

int32

Expiring Synchronization Due Day

☐

 

has_message

boolean

Has Message

☐

 

has_sepa_ct_payment_method

boolean

Has Sepa Ct Payment Method

☐

 

has_sequence_holes

boolean

Has Sequence Holes

☐

 

id

int32

ID

☐

 

inbound_payment_method_line_ids

string

 

☐

Manual: Get paid by any method outside of Odoo.Payment Providers: Each payment provider has its own Payment Method. Request a transaction on/to a card thanks to a payment token saved by the partner when buying or subscribing online.Batch Deposit: Collect several customer checks at once generating and submitting a batch deposit to your bank. Module account_batch_payment is necessary.SEPA Direct Debit: Get paid in the SEPA zone thanks to a mandate your partner will have granted to you. Module account_sepa is necessary.

invoice_reference_model

string

Communication Standard

☑

You can choose different models for each type of reference. The default one is the Odoo reference.

invoice_reference_type

string

Communication Type

☑

You can set here the default communication that will appear on customer invoices, once validated, to help the customer to refer to that particular invoice when making the payment.

journal_group_ids

string

 

☐

 

json_activity_data

string

Json Activity Data

☐

 

kanban_dashboard_graph

string

Kanban Dashboard Graph

☐

 

kanban_dashboard

string

Kanban Dashboard

☐

 

loss_account_id_label

string

 

☐

Used to register a loss when the ending balance of a cash register differs from what the system computes

loss_account_id

string

 

☐

Used to register a loss when the ending balance of a cash register differs from what the system computes

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

Journal Name

☑

 

next_link_synchronization

datetime

Online Link Next synchronization

☐

 

outbound_payment_method_line_ids

string

 

☐

Manual: Pay by any method outside of Odoo.Check: Pay bills by check and print it from Odoo.SEPA Credit Transfer: Pay in the SEPA zone by submitting a SEPA Credit Transfer file to your bank. Module account_sepa is necessary.

payment_sequence

boolean

Dedicated Payment Sequence

☐

Check this box if you don't want to share the same sequence on payments and bank transactions posted on this journal

pos_payment_method_ids

string

 

☐

 

profit_account_id_label

string

 

☐

Used to register a profit when the ending balance of a cash register differs from what the system computes

profit_account_id

string

 

☐

Used to register a profit when the ending balance of a cash register differs from what the system computes

refund_sequence

boolean

Dedicated Credit Note Sequence

☐

Check this box if you don't want to share the same sequence for invoices and credit notes made from this journal

restrict_mode_hash_table

boolean

Lock Posted Entries with Hash

☐

If ticked, the accounting entry or invoice receives a hash as soon as it is posted and cannot be modified anymore.

sale_activity_note

string

Activity Summary

☐

 

sale_activity_type_id_label

string

 

☐

Activity will be automatically scheduled on payment due date, improving collection process.

sale_activity_type_id

string

 

☐

Activity will be automatically scheduled on payment due date, improving collection process.

sale_activity_user_id_label

string

 

☐

Leave empty to assign the Salesperson of the invoice.

sale_activity_user_id

string

 

☐

Leave empty to assign the Salesperson of the invoice.

secure_sequence_id_label

string

 

☐

Sequence to use to ensure the securisation of data

secure_sequence_id

string

 

☐

Sequence to use to ensure the securisation of data

selected_payment_method_codes

string

Selected Payment Method Codes

☐

 

sepa_pain_version

string

SEPA Pain Version

☐

SEPA may be a generic format, some countries differ from the SEPA recommendations made by the EPC (European Payment Council) and thus the XML created need some tweaking.

sequence_override_regex

string

Sequence Override Regex

☐

Technical field used to enforce complex sequence composition that the system would normally misunderstand.This is a regex that can include all the following capture groups: prefix1, year, prefix2, month, prefix3, seq, suffix.The prefix* groups are the separators between the year, month and the actual increasing sequence number (seq).e.g: ^(?P<prefix1>.*?)(?P<year>\d{4})(?P<prefix2>\D*?)(?P<month>\d{2})(?P<prefix3>\D+?)(?P<seq>\d+)(?P<suffix>\D*?)$

sequence

int32

Sequence

☐

Used to order Journals in the dashboard view

show_on_dashboard

boolean

Show journal on dashboard

☐

Whether this journal should be displayed on the dashboard or not

suspense_account_id_label

string

 

☐

Bank statements transactions will be posted on the suspense account until the final reconciliation allowing finding the right account.

suspense_account_id

string

 

☐

Bank statements transactions will be posted on the suspense account until the final reconciliation allowing finding the right account.

type

string

Type

☑

Select 'Sale' for customer invoices journals.Select 'Purchase' for vendor bills journals.Select 'Cash' or 'Bank' for journals that are used in customer or vendor payments.Select 'General' for miscellaneous operations journals.

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