# Reimbursement Reference

Primary fact source: `docs/报销发票附件规则.md`.

## Checks Before Editing

- PC and mobile must have the same business capability.
- Ordinary users should see "添加发票", not "绑定整单", "不绑定明细", "发票池", or "ERP 同步".
- Invoice constraints belong on the server; frontend restrictions are only convenience.
- Attachments are supporting materials and must not enter invoice OCR or invoice dedup.

## Backend Hotspots

- `server/src/routes/invoicePool.js`
- `server/src/routes/invoicePool/read.js`
- `server/src/jobs/ocrJob.js`
- `server/src/services/invoiceGovernance.js`
- `server/src/routes/reimbursements.js`
- `server/prisma/schema.prisma`

## Frontend Hotspots

- `client/src/pages/ReimbursementDetailPage.tsx`
- `client/src/pages/MobileReimbursementDetailPage.tsx`
- `client/src/pages/InvoicePoolPage.tsx`
- `client/src/api/invoicePool.ts`
- `client/src/api/reimbursements.ts`

## Minimum Tests

- Invoice upload/dedup tests.
- OCR job duplicate handling tests.
- Reimbursement invoice bind/unbind tests.
- Attachment upload/download/delete tests.
- PC and mobile Playwright flow.