Automating Expense Reports in Odoo 19:
OCR, Approval Workflows & Accounting

Expense Reports Are Where Finance Automation Goes to Die

Every company has the same story. Sales reps collect paper receipts in their wallets for three weeks, then dump a stack of crumpled paper on the finance team's desk the day before month-end close. The finance team manually enters each line, chases managers for approvals via email, and then re-keys everything into the accounting system. The process takes days, errors are constant, and nobody is happy.

Odoo 19's Expenses module changes this completely. Receipts are scanned with OCR that extracts amounts, dates, and vendors automatically. Approval workflows route expense reports to the right manager based on department and amount thresholds. Approved expenses post journal entries directly into your chart of accounts—no manual re-entry. And billable expenses can be re-invoiced to customers with a single click.

This guide walks through every layer of expense automation in Odoo 19: how to configure expense categories, how OCR receipt scanning works, how to build multi-level approval workflows, how journal entries are generated, how to re-invoice expenses to customers, and how employees submit expenses from their phones.

Configuring Expense Categories and Products for Clean Reporting

Before any receipt hits the system, you need a well-structured set of expense categories. In Odoo, every expense line is linked to an expense product—a special product type that maps to a specific GL account. Getting this structure right determines whether your P&L breakdown is useful or whether everything lands in a generic "Employee Expenses" bucket.

Creating Expense Products

Navigate to Expenses > Configuration > Expense Products. Each product represents a category of spend:

# Creating expense products via code (e.g., data migration)
expense_product = env['product.product'].create({
    'name': 'Hotel Accommodation',
    'type': 'service',
    'can_be_expensed': True,
    'property_account_expense_id': env.ref(
        'l10n_generic_coa.1_a620100'
    ).id,
    'supplier_taxes_id': [(6, 0, [tax_20_purchase.id])],
    'expense_policy': 'cost',       # 'cost' or 'sales_price'
    'default_code': 'EXP-HOTEL',
    'list_price': 0.0,
    'standard_price': 0.0,
})

Setting Up Mileage Allowances

Mileage expenses require a special configuration. Instead of a receipt amount, employees enter the number of kilometers driven, and Odoo calculates the reimbursement using a per-km rate:

<odoo>
  <record id="expense_product_mileage" model="product.product">
    <field name="name">Mileage Reimbursement</field>
    <field name="type">service</field>
    <field name="can_be_expensed">True</field>
    <field name="uom_id" ref="uom.product_uom_km"/>
    <field name="uom_po_id" ref="uom.product_uom_km"/>
    <field name="standard_price">0.67</field>
    <!-- EUR 0.67/km - adjust per local tax authority rates -->
    <field name="property_account_expense_id"
           ref="l10n_generic_coa.1_a625100"/>
  </record>
</odoo>

Building Multi-Level Expense Approval Workflows in Odoo 19

Small companies can get by with a single manager approval. But once you have multiple departments, spending tiers, or compliance requirements, you need a multi-level approval workflow. Odoo 19 supports this through a combination of expense report approval rules, department-based routing, and activity-based escalation.

The Default Approval Flow

Out of the box, Odoo routes expense reports through this sequence:

Adding Amount-Based Approval Tiers

For companies that require director-level approval above a certain threshold, you can extend the expense model with a custom approval step:

from odoo import api, fields, models


class HrExpenseSheet(models.Model):
    _inherit = "hr.expense.sheet"

    x_requires_director_approval = fields.Boolean(
        string="Requires Director Approval",
        compute="_compute_requires_director",
        store=True,
    )
    x_director_approved = fields.Boolean(
        string="Director Approved",
        tracking=True,
    )
    x_director_id = fields.Many2one(
        "res.users",
        string="Approving Director",
        tracking=True,
    )

    @api.depends("total_amount")
    def _compute_requires_director(self):
        threshold = float(
            self.env["ir.config_parameter"].sudo().get_param(
                "expense.director_approval_threshold", "5000.0"
            )
        )
        for sheet in self:
            sheet.x_requires_director_approval = (
                sheet.total_amount > threshold
            )

    def action_approve_director(self):
        """Called by the director approval button."""
        self.ensure_one()
        self.write({
            "x_director_approved": True,
            "x_director_id": self.env.uid,
        })
        # Trigger the standard manager approval next
        self.action_approve_expense_sheets()

Department-Based Routing with Activities

def action_submit_sheet(self):
    """Override submit to route to the correct approver."""
    res = super().action_submit_sheet()
    for sheet in self:
        approver = sheet.employee_id.department_id.manager_id.user_id
        if not approver:
            approver = sheet.employee_id.parent_id.user_id
        if approver:
            sheet.activity_schedule(
                "hr_expense.mail_act_expense_approval",
                user_id=approver.id,
                note=f"Expense report {{sheet.name}} "
                     f"({{sheet.total_amount}} "
                     f"{{sheet.currency_id.symbol}}) "
                     f"requires your approval.",
            )
    return res

Re-Invoicing Expenses to Customers: Billing Travel and Project Costs

Consulting firms, agencies, and professional services companies regularly bill travel and project expenses back to clients. Odoo handles this through the re-invoice policy on expense products, linked to analytic accounts tied to sales orders.

The Re-Invoicing Flow

• Step 1: Set the expense product's Re-Invoice Policy to "At cost" or "At sales price."
• Step 2: When creating the expense, the employee selects the Analytic Account linked to the customer's sales order.
• Step 3: After the expense report is approved and posted, the expense lines appear as "Expenses to Re-Invoice" on the linked sales order.
• Step 4: When you create the next invoice from the sales order, these expense lines are automatically included.

# Employee creates an expense linked to a customer project
expense = env['hr.expense'].create({
    'name': 'Flight to Paris - Acme Corp project',
    'product_id': flight_product.id,
    'total_amount_currency': 450.00,
    'employee_id': employee.id,
    'analytic_distribution': {
        str(acme_analytic_account.id): 100.0,
    },
    # The analytic account must be linked to a sales order
    # for re-invoicing to work.
})

# After approval + posting, check the sales order:
# sale_order.expense_ids will include this expense
# sale_order._create_invoices() will add it to the invoice

Mobile Expense Submission: From Receipt Photo to Posted Entry in 60 Seconds

The mobile experience is where expense automation delivers the most visible ROI. Employees no longer collect receipts for weeks—they photograph each receipt immediately after the transaction. The Odoo mobile app (iOS and Android) provides a streamlined expense submission flow:

• Open the Odoo app — Navigate to Expenses and tap the "Scan" button.
• Photograph the receipt — The app uses the phone's camera. OCR processes the image immediately.
• Review pre-filled fields — Amount, date, vendor, and currency are auto-populated. The employee selects the expense category and adds notes.
• Submit — The expense is added to a draft expense report. The employee can submit the report immediately or batch multiple expenses.
• Manager notification — The manager receives a push notification and can approve directly from the mobile app.

# Recommended mobile-friendly settings:
#
# 1. Expenses > Settings > Digitization = "Digitize automatically"
#    (Employees don't need to trigger OCR manually)
#
# 2. Set default expense products per department:
#    HR > Departments > [Dept] > Expense Products
#    This reduces the number of taps on mobile.
#
# 3. Enable push notifications for approvers:
#    Settings > Discuss > Push Notifications = Enabled
#    Managers get instant alerts for pending approvals.
#
# 4. Consider allowing "single expense" submission
#    (vs. grouped reports) for real-time processing:
#    Settings > Expenses > Expense Report Grouping = "None"

3 Expense Automation Mistakes That Create Accounting Headaches

Optimization Metadata