# Client adjustments · minimum UI for review

15 October 2026 · ODI-1438

## The flow

**Paid Invoice → Record adjustment → amount + handling choice → Save adjustment.**

The same action is available in the paid Invoice's Journey row menu. There are no new service-row actions and no duplicate services list. Inside the form, optionally select a billed service. It can be canceled, completed, verified or confirmed. Add a date and short reason, such as a service complaint or an agreed cancellation amount.

- **Money returned:** record a refund already made outside Odia. No payment is sent.
- **Keep as credit:** make the amount available to that contact, in the same currency.
- **Apply credit:** on a later Invoice, use all or part of an available note. Show Invoice total, applied credit and amount to pay separately.

## Minimum screens

| Location | Change |
|---|---|
| Journey → Invoices | One menu action on a paid Invoice. |
| Source Invoice | One compact Client adjustments section with the action and dated records. |
| Shared dialog | Handling choice, optional service, amount, date and reason. |
| Contact → Overview | Available client credit and its note history. |
| Later Invoice → Payment | Available/applied credit, its reference and Apply credit. History is collapsed here; no View credit note shortcut or separate history card. |
| Record detail | Source, reason, optional service, history and Void record action. |
| Journey → Revenue and Analytics | No new panels or adjustment calculations in this review. |

## Completed-service example

The boat tour happened and remains Completed. A complaint leads to an agreed €200 adjustment. Record €200 as returned, or keep €200 as credit. The saved record links back to the tour. Applying €150 credit to a later €3,000 Invoice leaves €2,850 to pay and €50 available credit. A second application can use the remaining €50. None of these actions cancels the tour.

## Corrections and limits

Failure keeps the draft and retry saves once. Remove applied credit to restore its balance. Void a mistaken refund or unused credit without deleting its history. Used credit cannot be voided until its applications are removed. Canceling the receiving Invoice returns its applied credit. Shared source/service caps cover both outcomes; wrong contact, currency and amounts are guarded in the simulation.

## What this does not decide

Recording does not silently alter the existing Include / Exclude treatment. Journey sales, costs, margins, commissions and Analytics retain their existing behavior in this prototype. Their eventual adjustment mapping is required before implementation and is deliberately not represented as an agreed calculation here. Formal tax-document layouts, supplier recoveries and payment execution are outside scope.

This is a reviewable UI proposal, not a production feature or approved financial architecture. See verification-report.md for current checks and limits.