1.3 KiB
1.3 KiB
Repository Maintenance Rules
Expense synchronization
Whenever a document is added or changed and it confirms an actual booked or paid expense, update expenses.md in the same change.
- Add or update exactly one ledger row per real expense. Do not duplicate an expense merely because it appears in both a booking file, PDF, email, or itinerary.
- Do not add shortlist prices, rejected options, refundable deposits, estimated optional fees, or TBC amounts as expenses.
- Record the payer exactly. If it is not clear who paid, ask the user before updating the ledger; do not infer the payer.
- Preserve the source currency in the ledger. For shared-cost settlement, use the USD amount recorded in Tricount.
- The accounting couples are KTVT (KT + VT) and LKMS (LK + MS). Shared expenses are split 50/50 between them unless a source clearly identifies an expense as couple-only.
- Couple-only expenses stay in the ledger for completeness but do not affect the cross-couple settlement.
- Ignore discrepancies below US$1 when they plausibly result from currency conversion or rounding.
- After every ledger-row change, recompute the net balance and update the single settlement sentence in
expenses.md. Show only the final result in the form: “KTVT owes LKMS US$X.XX.” (or the reverse).