Read the linked expense journal
From detail, choose 1 Journal Transaction when available and authorised. The page checks that the route's journal ID matches the expense's linked journal before displaying it.
What to inspect
| Value | Review purpose |
|---|---|
| Journal ID/number | Trace exact accounting record, distinct from expense ID |
| Status | Journal state, separate from expense and payment |
| Posting date | Currently built from expense date |
| Reference type/ID/number | Expense linkage |
| Business unit | Owning scope used for journal |
| Transaction/base currency and rate | Detect current GBP/rate-1 implementation limits |
| Debit/credit lines | Selected expense account and payable account |
| Totals | Balanced recognition amount, normally full expense total |
Procedure
- Confirm the expense and journal IDs and Paid By path.
- Inspect date, unit, description, currencies and exchange rate.
- Verify selected debit account and expected payable account.
- Compare debit/credit totals to the full expense amount.
- For employee-paid records, use PAY/payment-count navigation only when the expense state permits it and payment-view authority exists.
There is one shared initial expense journal relationship for employee reimbursement, with additional relationship rows for later partial payments. A journal-only placeholder row does not count as a payment. The page can show zero payments after a read failure; retry before concluding none exist.
Recognition versus settlement
The journal recognises spending and a liability. Its POSTED state does not prove a reimbursement or supplier bank transfer has settled. The reviewed payment lifecycle does not itself demonstrate a dedicated expense-payable clearing entry; accounting reconciliation remains necessary.
Reset to Draft and Confirm controls change the journal's own state under separate permissions. They are not a correction wizard that updates the expense amount, approval, payment counters and all relationships. Read Journal actions before using them.
If the detail link is absent, check journal permission, posting outcome and loading errors. Do not post again just because a failed read cleared the journal display. Use the exact record ID and support evidence to resolve uncertainty.