Bank payment matrix (auto-computed)

The grid at the top of the Ledger tab is read-only. Each cell aggregates three sources that share the same (bank, pay_date):

  card_payments       (bank × pay_day)
+ interest_payments  (bank × pay_day)
+ cash_flows(is_auto=1)  (bank × matched pay_dates)

A cell turns black only when every contributing row is confirmed. To change a cell, edit the underlying rows in the detail sections — never the matrix itself.

A typical cycle day (stepper)

1. Add detail rows. In the relevant section below, add card payments, interest rows, or auto-transfer cash flows. Pay day / date range decides which matrix column each row lands in.
2. Enter cash-flow date ranges for auto transfers. For recurring transfers, set is_auto=1 and put a date range like 27일 or 27-05일 in date_range. money matches it to one or more pay_dates and folds the amount into the matrix cell.
3. Read the matrix. Each (bank, pay_date) cell is the sum of card + interest + auto cash flows for that bucket. The cell goes black only when all rows in the bucket are confirmed.
4. Confirm. Press ✓ on each red row (or "섹션 전체 확인") to lock it. The cell flips to black once every contributing row is confirmed.

Detail sections

• Card payments (카드 결제) — monthly per-card totals. Pay day drives which matrix column the row lands in.
• Interest (이자) — monthly interest. The loan column links the entry to a loan in the Loans tab; once linked, the rate snapshot is captured automatically.
• Manual spending (수동지출) — one-off expenses. Not in the matrix cells; shown as separate virtual rows below the matrix, grouped by pay_date. A virtual row goes black only when all its items are confirmed.
• Cash flow (현금흐름) — in/out by purpose (income, savings, transfer, etc.). Auto-transfer rows (is_auto=1) with a date_range are added to the matching matrix cells. Manual rows (is_auto=0) are record-only and do not affect the matrix.
• Auto transfers (자동이체) — global recurring transfer templates, reference only.
• Shinhan rate check (신한 우대금리) — see below.
• Notes (비고) — free-text month memo.

Reading a red cell backwards

When a matrix cell stays red, click it to see the contributing rows. Each row shows its own confirm state. Confirm all of them — the cell turns black automatically.

Manual spending virtual rows

Manual spending items are aggregated by pay_date and rendered as extra rows beneath the bank matrix, not inside it. Items without a pay_date are excluded from the virtual row (and therefore from the cycle total). Edit individual items in the Manual spending detail section to change their pay_date.

Shinhan preferred-rate window

Shinhan Bank offers a preferred rate when the 3-month rolling card spend stays above ₩500,000. money computes two windows:

• 차월 (prior window) = months M−3, M−2, M−1
• 차차월 (current window) = months M−2, M−1, M

M−2 and M−1 are shared between the two windows, so you only enter them once. Enter values in the 차차월 row (M−2, M−1, M all editable); 차월 reuses M−2 and M−1 and only needs its unique M−3 cell entered. Missing months count as ₩0 but remain distinct from an explicit ₩0. The result uses both the current and confirmed totals to show met, provisionally met, provisionally unmet, or unmet status.

Search

The search box at the top of the Ledger tab searches across all months (not just the selected one). Results render inline below.

Accounts tab (admin only)

Manage the reference list of bank accounts and cards used across the Ledger. Each account has a label, bank name, account number, and optional card name. In the Ledger's detail sections, the account picker (▼ button next to the bank/account/card fields) lets you autofill all three fields at once from this list. Add new accounts inline via the picker's "+ 새 계좌" button — no need to visit this tab first.

Card details tab (admin only) — per-transaction breakdown

Each card-payment row in the Ledger matrix is the sum of all card_transactions in that (month × card × bank) group. The Card details tab is where you enter individual transactions: date, card, store, amount, installment months.

Batch input — click "일괄 입력" to paste straight from a card statement. Each line is pipe-separated: YYYY-MM-DD|card|store|amount|installment_months|note(optional). Blank lines and # comments are ignored. All-or-nothing rollback on parse failure.

📷 Receipt upload — click the 📷 button on any row to attach a receipt photo. First time asks you to sign in with Google (drive.file scope only — app can only touch files it creates). The photo uploads to your Google Drive → "영수증" folder (counts against your 15 GB quota, not the service account's). A calendar event is auto-created in the "영수증" Google Calendar with the Drive link dropped into the description.

📎 Receipt link — the 📎 button opens a picker that searches the "영수증" calendar's events. Click an event to link it to the row; click 📎 again to view the breakdown (parsed from the event description). Use the unlink icon to disconnect it (the calendar event itself is preserved — it's user-owned).

Cases

• Paste a monthly statement → "일괄 입력" → paste lines like 2026-07-03|신한|카페|4500|1| → "저장". If any line fails to parse, the entire batch rolls back so the month stays consistent.
• Attach a paper receipt after the fact → find the row → 📷 → first time, sign in with Google → photo uploads to your Drive "영수증" folder and a calendar event is created automatically.
• Link an existing calendar receipt → 📎 → search the "영수증" calendar → pick the event → row links to it. Open 📎 again to see the parsed breakdown.

Jeremy tab (net worth tracking)

Tracks what young owes jeremy. Two directions:

• in (자산) — jem hands cash to young, reducing young's debt.
• out (부채) — young uses a card (the quick form at the top is the fastest way to log this).

Two status axes (review · reflected)

Each entry shows two independent axes:

• Review state — admin-entered entries are "reviewed"; jem-entered entries are "pending review".
• Reflected state — if the date hasn't arrived yet: "scheduled · excluded"; once it has: "reflected". A pending-review entry stays "pending review · excluded" even after the date arrives.

The totals (cumulative reflected assets/liabilities/net) sum only entries that are both reviewed and whose date has arrived as of the "as of" cutoff shown at the top. The review-comment field no longer auto-fills with "추정치"; it shows only comments you write yourself.

The board at the bottom is a shared memo board for young and jeremy. Use it for notes and image attachments related to Jeremy entries or follow-up discussion.

Cases

• young uses a card → out. Use the quick-entry form at the top of the Jeremy tab: pick a card, amount, optional note. Submit. The row shows red (pending review) until an admin marks it reviewed.
• jem hands cash to young → in. Open the Jeremy tab, choose direction in, enter the amount jem gave, and save. young's debt balance drops by that amount.
• Share a receipt or contract photo → scroll to the memo board, attach the image, and add a short caption. young and jeremy both see it; comments are preserved as a thread.

Fertility tab (calendar)

Period and fertility-window tracking. Click any day to log:

• Period (start/end) — drives the cycle prediction.
• Sex — record only. Pick 섹스만, 섹스+오랄, or 섹스+기타 when creating. After creation you can toggle 오랄/기타 independently. None of these flags affect the fertility probability calculation.

Day cells are color-coded by predicted fertility (high / medium / low). The banner at the top highlights the current phase. ⚠ Statistical estimate only — not medical guidance.

Cases

• Period starts → click the first day of bleeding, choose 생리 시작. Current-cycle ranges need at least four starts and are withheld when interval changes or tracking gaps require review.
• Period ends → click the last day, choose 생리 종료. Days between start and end are shaded as period days.
• Record sex → click the day, pick 섹스만, 섹스+오랄, or 섹스+기타. The fertility probability is computed from the period dates only — these flags do not change the prediction.

Loans tab (admin only)

Each loan has a full rate change history. For each rate entry you record the bank's spread and any preference components (우대금리). The final_rate auto-computes as spread − Σ preferences; override the field directly if you know the precise value. Linking a loan from the Interest section of the Ledger captures the rate-at-time-of-payment.

Loan contract memos capture each loan's terms (principal, rate, counterparty, dates). Every edit creates a snapshot, and each contract has a comments board for text notes and image attachments.

Cases

• Rate change this month → open the loan → add a new rate row with the bank's new spread + each 우대금리 component. The final_rate auto-computes; override it directly if you know the precise value.
• Capture the rate at interest payment time → in the Ledger's Interest section, pick this loan in the loan column. The current rate row is snapshotted onto the interest payment automatically.
• Update loan contract terms → open the contract memo → edit principal/counterparty/dates → save. A snapshot is preserved each time, so the full history is recoverable.

Status tab (admin only)

• Health — DB path/size/journal mode + table row counts.
• Backups — manual "지금 백업" + restore (overwrites current DB; confirm dialog).
• Audit log — every write is recorded; filter by action or actor.

Settings tab (admin only)

Manage user accounts (admin / observer), reset passwords, and edit each observer's allowed_tabs — the granular list of tabs that observer can open after login.

Profile household ledger

Admins can switch between My profile, Jeremy profile, and All. Jeremy users are server-isolated to their own profile. Personal and shared expenses remain on the profile that recorded them.

Only a Jeremy personal expense may be marked as paid with young's card. It creates a linked Jeremy debt row whose financial fields remain managed here.

Cases

• Bulk import → paste pipe text or JSON, validate and edit each row, then explicitly select rows for an atomic commit.
• Jeremy settlement → Jeremy-created links wait for admin confirmation; admin-created links are confirmed immediately.