tripletex-create-supplier

Tripletex Create Supplier

Overview

Use this skill to create or improve a Tripletex supplier/leverandør record based on evidence from an invoice, receipt, or voucher page. Prefer the dedicated customer/supplier page over the small modal overlay from voucher registration, because the dedicated page exposes the full supplier profile and reduces the risk of missing language, currency, country, organization/VAT number, or bank details.

Guardrails

• Use the in-app Browser when working from an open Tripletex tab.
• Confirm the visible company before creating or editing a supplier.
• Treat supplier creation/editing as a persistent accounting data change. Ask for user approval before saving unless the user has explicitly authorized the exact creation/update.
• Do not click voucher-level Opprett, Bokfør, or similar booking actions from this skill unless the user separately approves voucher booking.
• If supplier identity is unclear, stop and summarize the competing evidence.
• Do not invent organization numbers, VAT numbers, country, currency, or bank details. Use what is visible in the PDF/invoice or ask the user.
• After each real supplier workflow, update this skill if the reusable procedure changed. Update local knowledge/ files when the learning is supplier-specific or historical.

Evidence To Extract

Read the invoice/PDF and capture:

• Supplier legal name.
• Supplier address and country.
• Supplier email and website when shown.
• Organization number, VAT number, or foreign registration number when shown.
• Invoice currency.
• Invoice language signals.
• Payment details: bank name, account/IBAN/BBAN, routing number, SWIFT/BIC, payment reference.

For foreign suppliers, set:

• Language: usually Engelsk.
• Currency: usually USD or EUR, based on the invoice currency.
• Country: the supplier country from the invoice.
• Org/VAT number: include the foreign organization/VAT/registration number when the invoice provides one.

For Norwegian organization numbers, use the official Brønnøysund register lookup and verify the resolved data.

Workflow

1. Search for an existing supplier first by exact supplier name and by organization/VAT number when available.
2. If no suitable supplier exists, open the dedicated Tripletex customer/supplier page for creating a new supplier instead of using the voucher modal overlay.
3. Set customer/supplier type to Leverandør.
4. Fill core identity:
   • Name.
   • Organization/VAT/registration number when available.
   • Country.
   • Language.
   • Currency.
   • Email and website when available.
5. Fill postal and physical address from the invoice. If only one address is shown, use it consistently where Tripletex requires address fields.
6. Fill bank/payment details from the invoice:
   • IBAN or account/BBAN.
   • SWIFT/BIC.
   • Routing number or bank name only if Tripletex has a suitable field.
   • Payment reference only on the voucher/payment, not as a supplier identity field unless Tripletex explicitly asks for it.
7. Before saving, compare the supplier form against the PDF evidence and summarize any blanks.
8. Save only after approval or explicit authorization.
9. Return to the voucher and verify the supplier field is set to the new supplier.

Stop Conditions

Stop and ask when:

• The PDF does not clearly identify the supplier.
• The invoice currency is not clear.
• The supplier country is unclear.
• A foreign org/VAT number is present but it is unclear which Tripletex field should store it.
• Multiple existing suppliers could match.
• Bank details differ from an existing supplier record.

Reporting

Report:

• Supplier name and Tripletex supplier number when visible.
• Company where it was created.
• Key fields filled: language, currency, country, org/VAT number, email, address, and bank details.
• Any fields intentionally left blank and why.
• Confirmation that no voucher booking was performed, unless separately authorized.

Continuous Improvement

At the end of each workflow:

• Add reusable process corrections here.
• Add supplier-specific facts to knowledge/vendors.md.
• Add examples of ambiguous supplier creation to a local knowledge file rather than expanding this skill into a history log.