GuideMarch 13, 2026

IFRS vs Local GAAP:
Dual Reporting Standards in Odoo 19

INTRODUCTION

When One Set of Books Isn't Enough

If your company operates across borders, you've almost certainly been asked to produce financial statements under two different accounting frameworks. Your local regulator demands GAAP-compliant filings. Your parent company or investors want IFRS-consolidated numbers. Your auditors expect a clean reconciliation between the two. And your finance team is stuck maintaining parallel spreadsheets that drift apart every quarter.

The differences between IFRS and local GAAP aren't cosmetic. They affect revenue recognition timing, lease capitalization, inventory valuation methods, goodwill amortization, and deferred tax calculations. A transaction that hits your P&L this quarter under US GAAP might be deferred to next quarter under IFRS 15. A lease that's off-balance-sheet under local rules must be capitalized under IFRS 16.

Odoo 19's accounting module can handle dual-standard reporting—but only if you configure it correctly from the start. This guide walks you through: how to design a multi-GAAP chart of accounts, configure journals for dual-standard posting, create IFRS adjusting entries, generate compliant financial statements under both standards, and maintain a clean audit trail throughout.

Key Differences Between IFRS and Local GAAP That Affect Your Odoo Configuration

Before touching Odoo, you need clarity on which differences actually matter for your business. Not every IFRS/GAAP divergence creates a reporting difference. Focus on the ones that change the numbers on your financial statements:

Area	IFRS Treatment	US GAAP Treatment	Odoo Impact
Revenue Recognition	IFRS 15 — 5-step model, performance obligations	ASC 606 — similar 5-step model but different guidance on variable consideration	Separate revenue journals or analytic tags per standard
Leases	IFRS 16 — all leases capitalized (single model)	ASC 842 — operating vs finance lease distinction retained	Different asset/liability accounts for IFRS lease entries
Inventory Valuation	LIFO prohibited under IFRS	LIFO permitted and widely used for tax benefits	Separate inventory valuation accounts or adjusting entries
Goodwill	Impairment-only model (no amortization)	Amortized over useful life (up to 10 years for private companies)	Different depreciation schedules per reporting standard
Development Costs	Capitalized when criteria met (IAS 38)	Expensed as incurred (except software under ASC 350-40)	IFRS adjusting entries to capitalize development costs
Deferred Tax	Balance sheet approach (IAS 12)	Similar but different exceptions for initial recognition	Separate deferred tax computation accounts

Start With a Gap Analysis

Map every IFRS/GAAP difference to your specific transactions before configuring anything. Most mid-size companies find that only 3-5 differences actually generate material adjustments. Configuring for differences that don't affect your business adds complexity without value.

Designing a Multi-GAAP Chart of Accounts in Odoo 19

The chart of accounts is the foundation of dual reporting. There are two architectural approaches, and the one you choose determines how much ongoing effort the finance team faces every month.

Approach A: Single CoA with IFRS Adjustment Accounts

Use your local GAAP chart of accounts as the primary structure. Add a dedicated account group for IFRS adjustments. Day-to-day transactions post under local GAAP. At period-end, the finance team creates adjusting journal entries that reclassify or revalue items to IFRS. This is the recommended approach for most companies because it keeps the daily workflow simple.

# account_code, account_name, account_type, group
1000,Cash and Cash Equivalents,asset_cash,Current Assets
1200,Accounts Receivable,asset_receivable,Current Assets
1500,Inventory (GAAP - LIFO),asset_current,Current Assets
1510,Inventory IFRS Adjustment (LIFO to FIFO),asset_current,IFRS Adjustments
1700,Right-of-Use Assets (IFRS 16),asset_non_current,IFRS Adjustments
2100,Accounts Payable,liability_payable,Current Liabilities
2500,Lease Liability - Current (IFRS 16),liability_current,IFRS Adjustments
2510,Lease Liability - Non-Current (IFRS 16),liability_non_current,IFRS Adjustments
3000,Retained Earnings,equity,Equity
6000,Operating Lease Expense (GAAP),expense,Operating Expenses
6010,Depreciation - ROU Assets (IFRS),expense,IFRS Adjustments
6020,Interest - Lease Liability (IFRS),expense,IFRS Adjustments
7000,Development Costs Expensed (GAAP),expense,Operating Expenses
7010,Capitalized Development Costs (IFRS),asset_non_current,IFRS Adjustments

Approach B: Parallel Charts of Accounts with Company Mapping

Create two separate companies in Odoo—one operating under local GAAP, one under IFRS. Use inter-company transaction rules to mirror entries. This approach provides complete separation but doubles the transaction volume and requires inter-company reconciliation:

# In Odoo 19 shell: create the IFRS reporting company
env = api.Environment(cr, SUPERUSER_ID, {})

ifrs_company = env['res.company'].create({
    'name': 'Acme Corp (IFRS Reporting)',
    'currency_id': env.ref('base.USD').id,
    'chart_template': 'generic_coa',  # Will be customized
    'fiscalyear_last_month': '12',
    'fiscalyear_last_day': 31,
})

# Map the IFRS CoA accounts
# Each local GAAP account maps to an IFRS equivalent
account_mapping = {
    '1500': '1500-IFRS',  # Inventory: LIFO -> FIFO
    '6000': '6010',       # Operating lease -> ROU depreciation
    '7000': '7010',       # Dev costs expensed -> capitalized
}

Setting Up Account Tags for Reporting Segregation

Regardless of which approach you choose, account tags are essential for filtering financial reports by standard. Odoo 19's reporting engine can filter by tags, giving you GAAP-only or IFRS-only views from a single trial balance:

<odoo>
  <data noupdate="1">
    <!-- Reporting standard tags -->
    <record id="tag_local_gaap" model="account.account.tag">
      <field name="name">Local GAAP</field>
      <field name="applicability">accounts</field>
      <field name="color">4</field>
    </record>

    <record id="tag_ifrs" model="account.account.tag">
      <field name="name">IFRS</field>
      <field name="applicability">accounts</field>
      <field name="color">10</field>
    </record>

    <record id="tag_both_standards" model="account.account.tag">
      <field name="name">Both Standards</field>
      <field name="applicability">accounts</field>
      <field name="color">2</field>
    </record>
  </data>
</odoo>

Approach A Wins for 90% of Cases

Unless you have regulatory requirements mandating a fully separate ledger (common in banking and insurance), Approach A with adjustment accounts is simpler, cheaper to maintain, and easier to audit. The parallel company approach doubles your chart of accounts, doubles your journal entries, and requires constant inter-company reconciliation that nobody wants to own.

Configuring Journals for Dual-Standard Posting in Odoo 19

Journals are the traffic controllers of your accounting system. For dual reporting, you need dedicated journals that separate IFRS adjustments from day-to-day local GAAP entries. This separation is what makes your audit trail clean and your period-end close predictable.

Creating the IFRS Adjustment Journal

# Create dedicated IFRS adjustment journals
ifrs_journal = env['account.journal'].create({
    'name': 'IFRS Adjustments',
    'code': 'IFRS',
    'type': 'general',
    'company_id': company.id,
    'sequence_id': env['ir.sequence'].create({
        'name': 'IFRS Adjustment Sequence',
        'prefix': 'IFRS/%(year)s/',
        'padding': 4,
        'company_id': company.id,
    }).id,
})

# Lease-specific IFRS journal
ifrs_lease_journal = env['account.journal'].create({
    'name': 'IFRS 16 - Leases',
    'code': 'IF16',
    'type': 'general',
    'company_id': company.id,
})

# Revenue adjustment journal (IFRS 15)
ifrs_revenue_journal = env['account.journal'].create({
    'name': 'IFRS 15 - Revenue',
    'code': 'IF15',
    'type': 'general',
    'company_id': company.id,
})

Journal Access Rights and Segregation

IFRS adjustment journals should be restricted to senior accountants or the reporting team. Day-to-day users posting invoices and payments should never accidentally post to the IFRS journal. Odoo 19 handles this through journal-level access groups:

<odoo>
  <data noupdate="1">
    <!-- Only IFRS Reporting group can post to IFRS journals -->
    <record id="rule_ifrs_journal_access" model="ir.rule">
      <field name="name">IFRS Journal: Reporting Team Only</field>
      <field name="model_id" ref="account.model_account_move"/>
      <field name="domain_force">[
        '|',
        ('journal_id.code', 'not like', 'IF%'),
        ('journal_id.code', '=', False)
      ]</field>
      <field name="groups"
             eval="[(4, ref('account.group_account_user'))]"/>
    </record>

    <!-- IFRS Reporting team can access all journals -->
    <record id="rule_ifrs_journal_full_access" model="ir.rule">
      <field name="name">IFRS Journal: Full Access</field>
      <field name="model_id" ref="account.model_account_move"/>
      <field name="domain_force">[(1, '=', 1)]</field>
      <field name="groups"
             eval="[(4, ref('account.group_account_manager'))]"/>
    </record>
  </data>
</odoo>

Analytic Accounts for Cross-Standard Tracking

Use analytic accounts to tag every journal entry with its reporting standard. This lets you run profit-and-loss reports filtered by GAAP or IFRS without needing separate journals for every transaction type:

# Create an analytic plan for reporting standards
analytic_plan = env['account.analytic.plan'].create({
    'name': 'Reporting Standard',
    'company_id': company.id,
})

gaap_analytic = env['account.analytic.account'].create({
    'name': 'Local GAAP',
    'plan_id': analytic_plan.id,
    'code': 'GAAP',
})

ifrs_analytic = env['account.analytic.account'].create({
    'name': 'IFRS',
    'plan_id': analytic_plan.id,
    'code': 'IFRS',
})

Naming Convention Matters

Prefix all IFRS journal codes with IF (e.g., IFRS, IF16, IF15). This makes filtering trivial in reports and record rules. It also means anyone looking at a journal entry can instantly tell whether it's a local GAAP transaction or an IFRS adjustment—no decoding required.

Creating IFRS Adjusting Entries: Leases, Revenue, and Development Costs

Adjusting entries are where the dual-reporting magic happens. These entries exist only in the IFRS journals and transform your local GAAP trial balance into an IFRS-compliant one. Here are the three most common adjustment patterns.

IFRS 16 Lease Capitalization

Under local GAAP, an operating lease is simply a monthly rent expense. Under IFRS 16, you must recognize a right-of-use asset and a corresponding lease liability on the balance sheet. The monthly expense splits into depreciation and interest:

# Example: 3-year office lease, $5,000/month, 5% discount rate
# Present value of lease payments = $167,220

# Initial recognition entry (posted to IFRS journal)
lease_entry = env['account.move'].create({
    'journal_id': ifrs_lease_journal.id,
    'date': '2026-01-01',
    'ref': 'IFRS16 - Office Lease Initial Recognition',
    'line_ids': [
        (0, 0, {
            'account_id': rou_asset_account.id,     # 1700
            'debit': 167220.00,
            'name': 'Right-of-Use Asset - Office Lease',
        }),
        (0, 0, {
            'account_id': lease_liability_lt.id,     # 2510
            'credit': 132540.00,
            'name': 'Lease Liability - Non-Current',
        }),
        (0, 0, {
            'account_id': lease_liability_st.id,     # 2500
            'credit': 34680.00,
            'name': 'Lease Liability - Current (Year 1)',
        }),
    ],
})
lease_entry.action_post()

# Monthly IFRS adjustment (reverses GAAP lease expense,
# replaces with depreciation + interest)
monthly_adj = env['account.move'].create({
    'journal_id': ifrs_lease_journal.id,
    'date': '2026-01-31',
    'ref': 'IFRS16 - Monthly Lease Adjustment Jan 2026',
    'line_ids': [
        # Reverse the GAAP operating lease expense
        (0, 0, {
            'account_id': gaap_lease_expense.id,     # 6000
            'credit': 5000.00,
            'name': 'Reverse GAAP lease expense',
        }),
        # Record IFRS depreciation (straight-line over 36 months)
        (0, 0, {
            'account_id': ifrs_depreciation.id,      # 6010
            'debit': 4645.00,
            'name': 'ROU Asset Depreciation',
        }),
        # Record IFRS interest on lease liability
        (0, 0, {
            'account_id': ifrs_interest.id,          # 6020
            'debit': 697.63,
            'name': 'Interest on Lease Liability',
        }),
        # Reduce lease liability
        (0, 0, {
            'account_id': lease_liability_st.id,     # 2500
            'debit': 4302.37,
            'name': 'Lease liability payment',
        }),
        # Offset entry
        (0, 0, {
            'account_id': rou_asset_account.id,      # 1700
            'credit': 4645.00,
            'name': 'ROU Asset accumulated depreciation',
        }),
    ],
})

Development Cost Capitalization (IAS 38)

Under most local GAAP frameworks, R&D costs are expensed immediately. IFRS requires capitalization of development costs once six criteria are met (technical feasibility, intention to complete, ability to use/sell, probable future economic benefits, availability of resources, and reliable cost measurement):

# Quarterly IFRS adjustment: capitalize eligible dev costs
dev_cost_adj = env['account.move'].create({
    'journal_id': ifrs_journal.id,
    'date': '2026-03-31',
    'ref': 'IAS38 - Q1 2026 Development Cost Capitalization',
    'line_ids': [
        # Reverse GAAP expense for eligible development costs
        (0, 0, {
            'account_id': gaap_dev_expense.id,       # 7000
            'credit': 85000.00,
            'name': 'Reverse GAAP dev expense (eligible portion)',
        }),
        # Capitalize as intangible asset under IFRS
        (0, 0, {
            'account_id': ifrs_capitalized_dev.id,   # 7010
            'debit': 85000.00,
            'name': 'Capitalized development costs (IAS 38)',
        }),
    ],
})

Inventory Valuation Adjustment (LIFO to FIFO)

If your local GAAP uses LIFO for inventory valuation (common in the US for tax benefits), IFRS requires a switch to FIFO or weighted average. The adjustment is the LIFO reserve:

# The LIFO reserve represents the difference between
# LIFO and FIFO inventory valuation
lifo_reserve = 42000.00  # From your inventory subledger

inventory_adj = env['account.move'].create({
    'journal_id': ifrs_journal.id,
    'date': '2026-03-31',
    'ref': 'IFRS - Q1 2026 Inventory LIFO Reserve Adjustment',
    'line_ids': [
        (0, 0, {
            'account_id': ifrs_inventory_adj.id,     # 1510
            'debit': lifo_reserve,
            'name': 'Inventory IFRS adjustment (LIFO to FIFO)',
        }),
        (0, 0, {
            'account_id': cogs_account.id,
            'credit': lifo_reserve,
            'name': 'COGS adjustment for FIFO valuation',
        }),
    ],
})

Automate Recurring Adjustments

Use Odoo's recurring journal entries feature for adjustments that follow a predictable pattern (like IFRS 16 monthly depreciation). Go to Accounting → Miscellaneous → Journal Entries, create the entry, then set it as a recurring template. This eliminates manual entry errors and ensures your IFRS adjustments post on schedule every period.

Generating Financial Statements Under Both Standards in Odoo 19

With your chart of accounts tagged and IFRS adjustments posted to dedicated journals, generating statements under either standard becomes a matter of filtering. Odoo 19's financial reporting engine supports this through journal filters and account tag filters.

Local GAAP Statements (Exclude IFRS Journals)

# Generate trial balance excluding IFRS adjustment journals
gaap_options = {
    'date': {
        'date_from': '2026-01-01',
        'date_to': '2026-03-31',
        'filter': 'custom',
    },
    # Exclude all journals starting with 'IF'
    'journals': [
        j.id for j in env['account.journal'].search([
            ('code', 'not like', 'IF%'),
            ('company_id', '=', company.id),
        ])
    ],
    'unfolded_lines': [],
    'comparison': {'filter': 'no_comparison'},
}

# Access via Accounting > Reporting > Trial Balance
# Then apply the journal filter in the UI

IFRS Statements (Include All Journals)

The IFRS financial statements include all journal entries—both the local GAAP transactions and the IFRS adjustments. Since IFRS adjustments are additive (they transform GAAP numbers into IFRS numbers), you simply run the report without any journal exclusions:

# IFRS trial balance = ALL journals (GAAP + IFRS adjustments)
ifrs_options = {
    'date': {
        'date_from': '2026-01-01',
        'date_to': '2026-03-31',
        'filter': 'custom',
    },
    # Include all journals - no filter
    'journals': [
        j.id for j in env['account.journal'].search([
            ('company_id', '=', company.id),
        ])
    ],
}

# The IFRS numbers = GAAP numbers + IFRS adjustment entries
# This is why Approach A works: the adjustments are additive

Building a Reconciliation Report

Auditors will want a bridge between your GAAP and IFRS numbers. This reconciliation report shows the GAAP balance, each category of IFRS adjustment, and the resulting IFRS balance. Build this as a custom Odoo report:

# Custom report: GAAP to IFRS Reconciliation
class GaapIfrsReconciliation(models.AbstractModel):
    _name = 'report.dual_reporting.gaap_ifrs_recon'
    _description = 'GAAP to IFRS Reconciliation Report'
    _inherit = 'account.report'

    def _get_report_data(self, options):
        """Build the GAAP-to-IFRS bridge."""
        company = self.env.company
        date_from = options['date']['date_from']
        date_to = options['date']['date_to']

        # 1. Get GAAP balances (exclude IF% journals)
        gaap_lines = self.env['account.move.line'].search([
            ('date', '>=', date_from),
            ('date', '<=', date_to),
            ('journal_id.code', 'not like', 'IF%'),
            ('company_id', '=', company.id),
            ('parent_state', '=', 'posted'),
        ])

        # 2. Get IFRS adjustments only
        ifrs_adj_lines = self.env['account.move.line'].search([
            ('date', '>=', date_from),
            ('date', '<=', date_to),
            ('journal_id.code', 'like', 'IF%'),
            ('company_id', '=', company.id),
            ('parent_state', '=', 'posted'),
        ])

        # 3. Group IFRS adjustments by journal for the bridge
        adjustments_by_journal = {}
        for line in ifrs_adj_lines:
            jrnl = line.journal_id.name
            if jrnl not in adjustments_by_journal:
                adjustments_by_journal[jrnl] = 0.0
            adjustments_by_journal[jrnl] += line.balance

        return {
            'gaap_total': sum(gaap_lines.mapped('balance')),
            'adjustments': adjustments_by_journal,
            'ifrs_total': sum(gaap_lines.mapped('balance'))
                        + sum(ifrs_adj_lines.mapped('balance')),
        }

Saved Filters Are Your Friend

Create saved filter presets in Odoo's reporting interface for "GAAP Only" and "IFRS Complete." Train your finance team to use these presets instead of manually selecting journals each time. One wrong journal selection produces incorrect statements—and nobody catches it until audit.

Maintaining a Clean Audit Trail for Dual-Standard Reporting

Auditors reviewing dual-standard financials need to trace every IFRS adjustment back to its source. A clean audit trail means every adjusting entry has a clear reference, a documented rationale, and a link to the supporting calculation. Odoo 19 provides the tools, but you need to configure them deliberately.

Structured Reference Numbers

Every IFRS adjusting entry should follow a reference convention that identifies the standard, the period, and the adjustment category:

# Reference format: [STANDARD]-[PERIOD]-[CATEGORY]-[SEQ]
# Examples:
IFRS16-2026Q1-LEASE-001    # Lease capitalization, Q1 2026
IAS38-2026Q1-DEVCAP-001    # Development cost capitalization
IFRS-2026Q1-INVADJ-001     # Inventory valuation adjustment
IFRS15-2026M03-REVADJ-001  # Revenue recognition adjustment, March

Enabling Odoo's Lock Dates for Period Control

Dual reporting requires strict period control. You cannot have someone posting a Q1 IFRS adjustment after the Q1 IFRS statements have been issued. Odoo 19 supports two lock date levels:

# Set lock dates after period-end close
company.write({
    # Non-advisers cannot post before this date
    'period_lock_date': '2026-03-31',
    # Even advisers cannot post before this date
    'fiscalyear_lock_date': '2025-12-31',
    # Tax-related lock (prevents tax report changes)
    'tax_lock_date': '2026-03-31',
})

# Recommended close sequence:
# 1. Post all GAAP transactions for the period
# 2. Run GAAP trial balance and review
# 3. Post all IFRS adjusting entries
# 4. Run IFRS trial balance and reconciliation
# 5. Set period lock date
# 6. Generate final statements under both standards

Attachment-Based Documentation

Attach supporting calculations to each IFRS adjusting entry. Odoo's chatter system on account.move supports file attachments and internal notes. For lease calculations, attach the amortization schedule. For inventory adjustments, attach the LIFO reserve computation. This makes the auditor's job straightforward and reduces your audit fees:

# Attach supporting calculation to the IFRS entry
import base64

with open('/path/to/lease_amortization_q1_2026.xlsx', 'rb') as f:
    file_data = base64.b64encode(f.read())

env['ir.attachment'].create({
    'name': 'IFRS16_Lease_Amortization_Q1_2026.xlsx',
    'type': 'binary',
    'datas': file_data,
    'res_model': 'account.move',
    'res_id': lease_entry.id,
    'mimetype': 'application/vnd.openxmlformats-'
                'officedocument.spreadsheetml.sheet',
})

# Add an internal note explaining the adjustment
lease_entry.message_post(
    body='IFRS 16 lease capitalization for office lease '
         'at 123 Main St. PV calculated at 5% discount rate. '
         'See attached amortization schedule.',
    message_type='comment',
    subtype_xmlid='mail.mt_note',
)

Audit-Ready Checklist

Before closing each period, verify: (1) every IFRS journal entry has a structured reference, (2) every adjustment has an attached supporting calculation, (3) the GAAP-to-IFRS reconciliation report balances, and (4) the period lock date is set. Automating this checklist as an Odoo activity template saves 2-3 hours per close cycle.

3 Dual-Reporting Mistakes That Create Audit Findings

A team member posts an IFRS 16 lease adjustment to the general miscellaneous journal instead of the dedicated IFRS journal. The entry is correct in amount but invisible to your journal-based filtering. Your GAAP statements now include an IFRS-only adjustment, and your IFRS statements show the correct total but the reconciliation report doesn't tie out. This error typically surfaces during audit—when it's expensive to fix.

Our Fix

Use Odoo's record rules (shown in the journal configuration section) to prevent non-IFRS users from posting to IF-prefixed journals. Create a dedicated "IFRS Reporting" user group. Pair this with a monthly reconciliation check that compares the sum of all IFRS journal entries against the GAAP-to-IFRS bridge total.

IFRS adjustments for items like inventory valuation are cumulative, not incremental. If your Q1 LIFO reserve was $42,000 and Q2 is $38,000, you don't post a $38,000 entry in Q2—you need to reverse the Q1 entry and post the new Q2 balance. Forgetting the reversal doubles your IFRS adjustment and inflates your IFRS balance sheet. This is the most common dual-reporting error we see.

Our Fix

Use Odoo's auto-reversal feature on IFRS adjusting entries. When creating the entry, enable "Reverse Entry" and set the reversal date to the first day of the next period. This ensures every period starts clean, and you only need to post the current period's correct IFRS balance—not worry about what was posted before.

The CFO pulls the IFRS balance sheet on the 5th of the month. The IFRS team hasn't finished posting lease adjustments (they're due on the 7th). The CFO now has an incomplete IFRS balance sheet that looks final because it includes some adjustments but not all. Decisions get made on wrong numbers. The corrected version arrives two days later and contradicts what was presented to the board.

Our Fix

Implement a close calendar with status tracking. Use Odoo's activity scheduling to assign IFRS adjustment tasks with deadlines. Add a custom field on the accounting period (or use a simple spreadsheet) that tracks: "GAAP Close Complete," "IFRS Adjustments Complete," "Reconciliation Verified," "Statements Released." No IFRS report should be distributed until the status is "Statements Released."

BUSINESS ROI

What Proper Dual Reporting Saves Your Organization

Dual reporting isn't a compliance checkbox—it's an operational capability that directly affects audit costs, investor confidence, and finance team productivity:

40-60%Reduction in Close Time

Automated IFRS adjustments and saved report filters eliminate the manual spreadsheet reconciliation that adds 3-5 days to every period close.

$15-25KAnnual Audit Fee Savings

A clean audit trail with structured references and attached calculations reduces auditor hours. Fewer questions, fewer requests, lower fees.

ZeroRestatement Risk

Systematic dual reporting with reconciliation controls eliminates the manual errors that lead to restatements—the most expensive accounting failure.

For a mid-size company with $50M revenue, a restatement costs an average of $2.1M in direct costs (audit fees, legal, remediation) plus immeasurable damage to investor confidence. Proper dual-reporting infrastructure in Odoo is a one-time $30-50K investment that eliminates this risk entirely.

SEO NOTES

Optimization Metadata

Meta Desc

Complete guide to configuring IFRS and local GAAP dual reporting in Odoo 19. Multi-GAAP chart of accounts, IFRS adjusting entries, journal configuration, and audit trail best practices.

H2 Keywords

1. "Key Differences Between IFRS and Local GAAP That Affect Your Odoo Configuration"
2. "Designing a Multi-GAAP Chart of Accounts in Odoo 19"
3. "Creating IFRS Adjusting Entries: Leases, Revenue, and Development Costs"
4. "3 Dual-Reporting Mistakes That Create Audit Findings"