[DEMO] hr-expense trip suite — sales-rep budget + approvals walk

DEMO_trip_suite.md

@@ -0,0 +1,43 @@
+# HR Expense — Trip suite demo (SMB sales-rep walk)
+
+This branch stacks the optional **Trip** layer over the base hr-expense flow so it
+can be installed + evaluated as one unit:
+
+- `hr_expense_trip` — the optional Trip container (groups expense lines; approval
+  workflow draft → request → approve → collect receipts → done; trip PDF).
+- `hr_expense_advance_clearing` + `hr_expense_advance_clearing_trip` — a **trip
+  advance = the budget** (cash issued for the trip, cleared against actual spend).
+- `hr_expense_payment` + `hr_expense_payment_trip` — **reimburse the whole trip
+  in one payment**.
+
+The Trip is **opt-in**: nothing changes about the plain per-expense flow unless a
+trip is used.
+
+## Scenario — a sales rep on the road
+
+**Without a trip (base flow):** the rep files each expense individually (flight,
+hotel, dinner). Each is approved and reimbursed on its own; there is no budget and
+no grouping — fine for the occasional expense, noisy for a multi-day trip.
+
+**With a trip:** the rep's manager opens a **Trip** ("Q1 East Coast Sales Tour"),
+issues a **$2,000 advance** as the trip budget, and approves the trip. The rep
+collects receipts against the trip; **Apply Advance** clears them against the
+budget (Advance Remaining tracks what's left), and **Pay Trip** reimburses any
+balance in one payment. One approval, one budget, one settlement.
+
+| Need | Base | Trip |
+|---|---|---|
+| Group a multi-day trip's expenses | — | trip.expense_ids |
+| Budget | — | advance ( $ issued up front ) |
+| Approval | per expense | one trip approval workflow |
+| Reimburse | per expense | one payment (Pay Trip) |
+| Document | per expense | trip PDF report |
+
+## Screenshots
+- Trip with advance budget + Apply Advance ([advance demo](https://storage.googleapis.com/ledo-pr-assets/hr-expense/pr-3/advance-clearing-trip.png)).
+- Trip form + batched expenses + state machine ([trip foundation](https://storage.googleapis.com/ledo-pr-assets/hr-expense/pr-1/01-buffer-form-flow-index.png) — see hr-expense#1 for the trip walk).
+
+## Eval
+Open this branch's runboat build (admin/admin) and follow the scenario above.
+Note: in 19.0, expense posting routes through `hr.expense.post.wizard`, so for the
+**Pay Trip** step do *Create Bill* → confirm the post wizard → **Pay Trip**.

hr_expense_advance_clearing/README.rst

@@ -0,0 +1,187 @@
+.. image:: https://odoo-community.org/readme-banner-image
+   :target: https://odoo-community.org/get-involved?utm_source=readme
+   :alt: Odoo Community Association
+
+=============================
+Employee Advance and Clearing
+=============================
+
+.. 
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! This file is generated by oca-gen-addon-readme !!
+   !! changes will be overwritten.                   !!
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! source digest: sha256:3399d5032631e32709c5c3793d190f99f145eee5605de1181d2698efad056214
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
+    :target: https://odoo-community.org/page/development-status
+    :alt: Beta
+.. |badge2| image:: https://img.shields.io/badge/license-AGPL--3-blue.png
+    :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
+    :alt: License: AGPL-3
+.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fhr--expense-lightgray.png?logo=github
+    :target: https://github.com/OCA/hr-expense/tree/19.0/hr_expense_advance_clearing
+    :alt: OCA/hr-expense
+.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
+    :target: https://translation.odoo-community.org/projects/hr-expense-19-0/hr-expense-19-0-hr_expense_advance_clearing
+    :alt: Translate me on Weblate
+.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
+    :target: https://runboat.odoo-community.org/builds?repo=OCA/hr-expense&target_branch=19.0
+    :alt: Try me on Runboat
+
+|badge1| |badge2| |badge3| |badge4| |badge5|
+
+Lets the company pay an "advance" to an employee, then later reconcile
+that advance against the actual expenses incurred.
+
+In Odoo 19.0 the workflow is per-expense (the 18.0 advance-sheet vs
+clearing-sheet pair is gone with ``hr.expense.sheet``):
+
+- An **advance expense** has ``expense_type='advance'``, uses the
+  ``Employee Advance`` product, no taxes. Paid to the employee via the
+  standard ``action_pay``.
+- A **clearing expense** is a regular ``hr.expense`` with
+  ``clearing_advance_id`` set to the advance. On posting, its receivable
+  line auto-reconciles against the advance's receivable line.
+- The advance's ``clearing_residual`` tracks the unreconciled balance.
+  When it hits zero, the advance is fully cleared.
+
+Three scenarios remain:
+
+- ``clearing_total = advance`` — fully reconciled, advance is closed.
+- ``clearing_total > advance`` — Register Payment on the clearing
+  expense's difference (the wizard understands the ``expense_clearing``
+  context).
+- ``clearing_total < advance`` — use **Return Advance** on the advance
+  expense to refund the residual back to the company.
+
+19.0 note: ``hr_expense_trip`` (when available) is the natural clearing
+scope — a "Clear Trip" button on the trip would call
+``action_clear_advance`` on the trip's ``expense_ids``. Trip integration
+lives in the trip module, not here.
+
+**Table of contents**
+
+.. contents::
+   :local:
+
+Configuration
+=============
+
+This module will create a new product "Employee Advance" automatically.
+You will need to setup the Expense Account of this product to your
+Employee Advance account manually.
+
+- Open Product window and search for "Employee Advance"
+- On Accounting tab, select appropriate employee advance account from
+  your chart of account
+
+Note:
+
+- You will need the "Show Full Accounting Features" to see accounting
+  data
+- Employee Advance account code, if not already exists, you can create
+  one. Use type = Current Asset and check Allow Reconciliation.
+
+Usage
+=====
+
+First-time setup: open product **Employee Advance** (auto-created on
+install) and set its expense account to your "Employee Advance"
+current-asset account with ``Allow Reconciliation``.
+
+**Create an Employee Advance**
+
+1. Expenses → My Expenses, click New.
+2. Set ``Expense Type`` to **Advance** (Employee Advance product +
+   own_account auto-fill).
+3. Optionally set ``Clearing Product`` — it's the default product for
+   clearing expense lines that reference this advance.
+4. Set the amount, Save.
+5. Submit → Approve → Post → Register Payment. The advance is paid to
+   the employee.
+
+**Clear the Advance with a regular expense**
+
+1. Expenses → My Expenses, New (or pick an existing draft).
+2. Leave ``Expense Type`` as **Expense** and set ``Clearing Advance`` to
+   the advance you want to clear against. The ``Advance Remaining``
+   smart field shows what's left of the advance.
+3. Submit → Approve → Post. On post, the clearing expense's receivable
+   line auto-reconciles against the advance's receivable line.
+
+What happens at post time:
+
+- ``clearing_total ≤ advance_residual`` → fully covered. No further
+  payment needed; the advance's residual updates.
+- ``clearing_total > advance_residual`` → the excess remains on the
+  clearing expense's move. Register Payment for the difference.
+
+**Return unused advance**
+
+1. Open the paid advance with ``clearing_residual > 0``.
+2. Click **Return Advance** (header button). The Register Payment wizard
+   opens pre-filled with the residual.
+3. Confirm. The advance is now fully closed; ``clearing_residual = 0``.
+
+**Trip integration** (when ``hr_expense_trip`` is installed)
+
+A trip's ``expense_ids`` can include both an advance and the regular
+expenses paid out of it. The trip module wires a "Clear Trip" button
+that calls ``action_clear_advance`` on the trip's regular expenses with
+the trip's advance as the target. This module does not depend on
+``hr_expense_trip``; the integration is one-way from the trip side.
+
+Bug Tracker
+===========
+
+Bugs are tracked on `GitHub Issues <https://github.com/OCA/hr-expense/issues>`_.
+In case of trouble, please check there if your issue has already been reported.
+If you spotted it first, help us to smash it by providing a detailed and welcomed
+`feedback <https://github.com/OCA/hr-expense/issues/new?body=module:%20hr_expense_advance_clearing%0Aversion:%2019.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
+
+Do not contact contributors directly about support or help with technical issues.
+
+Credits
+=======
+
+Authors
+-------
+
+* Ecosoft
+
+Contributors
+------------
+
+- Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
+- Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
+- Saran Lim. <saranl@ecosoft.co.th>
+
+Maintainers
+-----------
+
+This module is maintained by the OCA.
+
+.. image:: https://odoo-community.org/logo.png
+   :alt: Odoo Community Association
+   :target: https://odoo-community.org
+
+OCA, or the Odoo Community Association, is a nonprofit organization whose
+mission is to support the collaborative development of Odoo features and
+promote its widespread use.
+
+.. |maintainer-kittiu| image:: https://github.com/kittiu.png?size=40px
+    :target: https://github.com/kittiu
+    :alt: kittiu
+.. |maintainer-dnplkndll| image:: https://github.com/dnplkndll.png?size=40px
+    :target: https://github.com/dnplkndll
+    :alt: dnplkndll
+
+Current `maintainers <https://odoo-community.org/page/maintainer-role>`__:
+
+|maintainer-kittiu| |maintainer-dnplkndll| 
+
+This module is part of the `OCA/hr-expense <https://github.com/OCA/hr-expense/tree/19.0/hr_expense_advance_clearing>`_ project on GitHub.
+
+You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

hr_expense_advance_clearing/__init__.py

@@ -0,0 +1,4 @@
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+from . import models
+from . import wizard

hr_expense_advance_clearing/__manifest__.py

@@ -0,0 +1,22 @@
+# Copyright 2019 Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
+# Copyright 2026 Ledo <https://ledoweb.com>
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+{
+    "name": "Employee Advance and Clearing",
+    "version": "19.0.1.0.0",
+    "category": "Human Resources",
+    "author": "Ecosoft, Odoo Community Association (OCA)",
+    "license": "AGPL-3",
+    "website": "https://github.com/OCA/hr-expense",
+    "depends": ["hr_expense"],
+    "data": [
+        "data/advance_product.xml",
+        "views/account_payment_view.xml",
+        "views/hr_expense_views.xml",
+        "views/hr_employee_views.xml",
+        "views/hr_employee_public_views.xml",
+    ],
+    "installable": True,
+    "maintainers": ["kittiu", "dnplkndll"],
+}

hr_expense_advance_clearing/data/advance_product.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<odoo noupdate="1">
+    <record id="product_emp_advance" model="product.product">
+        <field name="name">Employee Advance</field>
+        <field name="default_code" />
+        <field name="type">service</field>
+        <field name="sale_ok" eval="False" />
+        <field name="purchase_ok" eval="False" />
+        <!-- 19.0: advance is itself an hr.expense, so the product must be
+             expensable (was False in 18.0 because advance lived on the
+             sheet, not the expense). -->
+        <field name="can_be_expensed" eval="True" />
+        <field name="supplier_taxes_id" eval="False" />
+        <field name="taxes_id" eval="False" />
+    </record>
+</odoo>