Automatically rename invoices, receipts, and tax documents based on content

Rename this file based on the visible contents of the document.
The file is likely an invoice, receipt, tax document, bank/account statement, vendor bill, purchase order, fiscal document, or downloaded portal PDF.
Create a concise, safe macOS filename using the most reliable fields found in the document.

General rules:
- Use only information that is visible or strongly supported by the document.
- Do not guess missing fields.
- Do not include personal tax IDs, full account numbers, full card numbers, addresses, phone numbers, or other sensitive identifiers in the filename.
- Use hyphens inside field values and underscores between major filename parts.
- Remove or replace unsafe filename characters, including / \ : * ? " < > | and line breaks.
- Keep the filename readable and under 140 characters when possible.
- Use Title-Case or clear abbreviated labels for vendors and document types.
- Preserve the original file extension.

Date rules:
- Prefer the document issue date, receipt date, transaction date, or statement period.
- Format exact dates as YYYY-MM-DD.
- Format monthly statement periods as YYYY-MM.
- Format tax years as YYYY.
- If multiple dates appear, choose the date most relevant to the document type:
  - invoice: invoice issue date
  - receipt: purchase or transaction date
  - statement: statement period
  - tax document: tax year
  - purchase order/vendor bill: document issue date

Vendor/issuer rules:
- Use the vendor, issuer, merchant, institution, or payee name.
- Clean common suffix noise when it is not needed, such as Inc., LLC, Ltd., GmbH, invoice portal text, or payment processor boilerplate.
- If the vendor is unclear, use Unknown-Vendor.

Amount and currency rules:
- Include the total amount when clearly visible and useful.
- Format amounts as 123.45-USD, 89.00-EUR, 420.00-BRL, etc.
- Use the currency shown in the document.
- If currency is missing but the symbol is clear, infer only common symbols such as $, €, or £.
- If amount is unclear, omit it.

Document number rules:
- For invoices, include the invoice number when visible as INV-{number}.
- For receipts, include a receipt number only if clearly labeled and useful.
- For purchase orders, include PO-{number}.
- For vendor bills, include Bill-{number} or INV-{number}, depending on the label.
- For statements, use the statement period instead of a document number.
- For tax documents, use the form type and tax year.

Document type rules:
- Use one of these document type labels when appropriate:
  Invoice, Receipt, Statement, Tax-Form, Tax-Support, Vendor-Bill, Purchase-Order, Credit-Note, VAT-Invoice, Factura, NF
- If the exact type is unclear, use Document.

Preferred filename patterns:
- Invoice: {date}_{vendor}_INV-{invoiceNumber}_{amount}-{currency}
- Receipt: {date}_{vendor}_Receipt_{amount}-{currency}_{category}
- Tax document: {taxYear}_{formType}_{issuer}
- Statement: {period}_{institutionOrAccount}_Statement
- Vendor bill / PO: {date}_{vendor}_PO-{poNumber}_Bill-{billNumber}_{amount}-{currency}
- International fiscal document: {date}_{vendor}_{documentType}-{documentNumber}_{amount}-{currency}

Category rules for receipts:
- If a broad category is obvious, append one of:
  Travel, Meals, Software, Office, Shipping, Marketing, Utilities, Hardware, Professional-Services, Other
- If no category is obvious, omit the category.

Fallback rules:
- If only a date and vendor are reliable, use: {date}_{vendor}_{documentType}
- If only a vendor and document type are reliable, use: {vendor}_{documentType}
- If almost nothing is readable, use: Needs-Review_{originalBaseName}

Return only the filename, with no explanation.