Navigation: Schema: account > Tables

reconcile_model

Preset to create journal entries during a invoices and payments matching

Catalog: Odoo

Schema: account

Documentation:

Populate factory part for account.reconcile.model.

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

Name	Data Type	Label	Required	Documentation
active	boolean	Active	☐
allow_payment_tolerance	boolean	Payment Tolerance	☐	Difference accepted in case of underpayment.
auto_reconcile	boolean	Auto-validate	☐	Validate the statement line automatically (reconciliation based on your rule).
company_id_label	string		☐
company_id	string		☐
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
decimal_separator	string	Decimal Separator	☐	Every character that is nor a digit nor this separator will be removed from the matching string
display_name	string	Display Name	☐
has_message	boolean	Has Message	☐
id	int32	ID	☐
line_ids	string		☐
match_amount_max	decimal	Amount Max Parameter	☐
match_amount_min	decimal	Amount Min Parameter	☐
match_amount	string	Amount Condition	☐	The reconciliation model will only be applied when the amount being lower than, greater than or between specified amount(s).
match_journal_ids	string		☐	The reconciliation model will only be available from the selected journals.
match_label_param	string	Label Parameter	☐
match_label	string	Label	☐	The reconciliation model will only be applied when the label:* Contains: The proposition label must contains this string (case insensitive).* Not Contains: Negation of "Contains".* Match Regex: Define your own regular expression.
match_nature	string	Amount Type	☑	The reconciliation model will only be applied to the selected transaction type:* Amount Received: Only applied when receiving an amount.* Amount Paid: Only applied when paying an amount.* Amount Paid/Received: Applied in both cases.
match_note_param	string	Note Parameter	☐
match_note	string	Note	☐	The reconciliation model will only be applied when the note:* Contains: The proposition note must contains this string (case insensitive).* Not Contains: Negation of "Contains".* Match Regex: Define your own regular expression.
match_partner_category_ids	string		☐	The reconciliation model will only be applied to the selected customer/vendor categories.
match_partner_ids	string		☐	The reconciliation model will only be applied to the selected customers/vendors.
match_partner	boolean	Partner is Set	☐	The reconciliation model will only be applied when a customer/vendor is set.
match_same_currency	boolean	Same Currency	☐	Restrict to propositions having the same currency as the statement line.
match_text_location_label	boolean	Match Text Location Label	☐	Search in the Statement's Label to find the Invoice/Payment's reference
match_text_location_note	boolean	Match Text Location Note	☐	Search in the Statement's Note to find the Invoice/Payment's reference
match_text_location_reference	boolean	Match Text Location Reference	☐	Search in the Statement's Reference to find the Invoice/Payment's reference
match_transaction_type_param	string	Transaction Type Parameter	☐
match_transaction_type	string	Transaction Type	☐	The reconciliation model will only be applied when the transaction type:* Contains: The proposition transaction type must contains this string (case insensitive).* Not Contains: Negation of "Contains".* Match Regex: Define your own regular expression.
matching_order	string	Matching Order	☑
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		☐
name	string	Name	☑
number_entries	int32	Number of entries related to this model	☐
partner_mapping_line_ids	string		☐	The mapping uses regular expressions.- To Match the text at the beginning of the line (in label or notes), simply fill in your text.- To Match the text anywhere (in label or notes), put your text between .e.g: .N°48748 abc123.*
past_months_limit	int32	Search Months Limit	☐	Number of months in the past to consider entries from when applying this model.
payment_tolerance_param	decimal	Gap	☐	The sum of total residual amount propositions matches the statement line amount under this amount/percentage.
payment_tolerance_type	string	Payment Tolerance Type	☑	The sum of total residual amount propositions and the statement line amount allowed gap type.
rule_type	string	Type	☑
sequence	int32	Sequence	☑
show_decimal_separator	boolean	Show Decimal Separator	☐
to_check	boolean	To Check	☐	This matching rule is used when the user is not certain of all the information of the counterpart.
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

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.

Odoo API Data Model

reconcile_model

Table Columns

Important Safety and Usage Information