tripletex-email-receipt-to-pdf

Tripletex Email Receipt To PDF

Overview

Convert email-only receipts into clean PDF attachments for Tripletex. Use this when the original email body contains the receipt evidence, but forwarding the email alone is not enough for Bilagsmottak.

Guardrails

• Confirm the Tripletex company and e-bilag destination before sending the generated PDF. Resolve the e-bilag address from knowledge/companies.md; do not hardcode it.
• Use this only when the email body is the receipt/invoice evidence and there is no proper PDF/image attachment already showing it.
• Do not invent missing receipt facts. If a required value is absent, leave it blank or ask the user.
• Verify supplier, date, order/invoice/receipt number, currency, total, VAT/MVA, product/service, and payment method against the email body before generating the PDF.
• If the email has both a PDF invoice and a receipt-like body, prefer the original PDF unless it is clearly not the accounting document.
• Keep the original email message id and subject in the PDF metadata table for traceability.

Evidence Rules

A generated PDF is acceptable only when these checks pass:

• The email sender is plausible for the supplier or platform.
• The receipt date is close to the bank transaction date or period being booked.
• The amount and currency match the bank transaction or known payment amount.
• The product/service name identifies the purchase.
• The supplier/legal seller is visible or inferable from the email body.
• The generated PDF contains enough source fields for a human to audit it later.

For Tripletex import, put the most important fields on page 1:

• Supplier/legal seller.
• Supplier address/country when visible.
• Order, invoice, receipt, or reference number.
• Receipt/invoice date.
• Product/service.
• Total amount and currency.
• VAT/MVA amount or VAT statement.
• Payment method.
• Source email subject and message id.

Workflow

1. Read the candidate email message.
2. Check attachments:
   • If it has a real PDF/image invoice or receipt, forward/upload that original document instead.
   • If attachments are only terms, policies, HTML files, calendar files, or unrelated material, continue.
3. Extract receipt fields from the email body and compare them to the bank/Tripletex task.
4. Create a JSON input file for scripts/create_email_receipt_pdf.py.
5. Generate the PDF under the current working directory, preferably output/pdf/.
6. Render or otherwise inspect the PDF before sending. Confirm no key fields are clipped or missing.
7. Send the PDF as an attachment to the correct Tripletex e-bilag address with the email connector. Use Tripletex web upload only as a fallback when email/e-bilag delivery is unavailable or the user explicitly asks for web upload.
8. Record the sent email id, output PDF path, and matching evidence in knowledge/gmail-receipt-sources.md.
9. After Tripletex imports the email, verify the imported row and page count before booking. If the same evidence already exists as an older generated-only inbox row, delete or merge the old row only after confirming the new PDF row is complete.

Script

Use the bundled script (resolve the plugin root with ${CLAUDE_PLUGIN_ROOT}):

python3 "${CLAUDE_PLUGIN_ROOT}/skills/tripletex-email-receipt-to-pdf/scripts/create_email_receipt_pdf.py" \
  --input /path/to/receipt.json \
  --output output/pdf/receipt.pdf

Input JSON shape (placeholder values — replace with the exact values from the source email):

{
  "title": "<Platform> receipt",
  "source_email": {
    "from": "<Platform> <[email protected]>",
    "to": "<configured email account>",
    "received": "2026-03-16 00:28:44 CET",
    "subject": "<Your order receipt from 16 March 2026>",
    "message_id": "<email-message-id>"
  },
  "receipt": {
    "supplier": "<Legal seller name>",
    "supplier_address": "<Seller address, country>",
    "order_number": "<order/receipt number>",
    "receipt_date": "2026-03-16",
    "product": "<product/service name>",
    "payment_method": "<card or payment method>",
    "total": "1 599,00 kr",
    "vat": "319,80 kr"
  },
  "amount_lines": [
    ["<product/service name>", "1 599,00 kr"],
    ["Inkludert MVA", "319,80 kr"],
    ["Total belastet", "1 599,00 kr"]
  ],
  "original_excerpt": "Relevant plain-text excerpt from the email body.",
  "note": "Original email had no PDF receipt attachment."
}

Use exact field values from the source email. The script accepts extra receipt keys and prints them as rows, so include any relevant supplier-specific fields such as customer number, subscription period, invoice number, or payment reference.

Stop Conditions

Stop and ask the user if:

• The email body does not clearly show an accounting receipt or invoice.
• The amount, supplier, or date conflicts with the bank transaction.
• A PDF/image attachment exists but cannot be opened or verified.
• The email is only a payment notification and points to a portal where the actual invoice must be downloaded.
• The generated PDF would need manual interpretation rather than direct source-field transcription.

Continuous Improvement

After each real workflow:

• Add supplier-specific behavior to knowledge/gmail-receipt-sources.md or knowledge/vendors.md.
• Update this skill only when the reusable procedure changes.
• Record whether Tripletex successfully imported the generated PDF; if not, improve the PDF field layout or required metadata.
• Prefer documenting the sent email message id over browser-upload timing because it gives the next agent a concrete import trace.