← BillabexCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Billabex
Snapshot Sep 30, 2026 · 22:57 UTC · version 2.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "enrich-customer-records",
"description": "Add customer contacts, invoices, or credit notes to Billabex from complete user-provided data and documents. Use for enriching an account, adding a debtor contact, importing a missing invoice, or recording a credit note.",
"included_files": [],
"skill_md_contents": "---\nname: enrich-customer-records\ndescription: Add customer contacts, invoices, or credit notes to Billabex from complete user-provided data and documents. Use for enriching an account, adding a debtor contact, importing a missing invoice, or recording a credit note.\n---\n\n# Enrich Customer Records\n\n1. Resolve the organization if needed and identify exactly one customer with `list-accounts`.\n2. Check existing data with `list-contacts`, `list-invoices`, or `list-credit-notes` to prevent obvious duplicates.\n3. For a contact, require the exact full name and two-letter language code. Use `create-contact` only after the user confirms the account and values.\n4. For an invoice, require its document, number, issue date, due date, total amount, tax amount, paid amount, and customer account. Use `create-invoice` only when all required data is available.\n5. For a credit note, require its document reference, number, issue date, total amount, tax amount, refunded amount, and customer account. Use `create-credit-note` only when the document is accessible to the tool.\n6. Never guess missing financial data, dates, language, currency, customer, or document references. Summarize the created record without exposing technical identifiers.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Use natural business vocabulary and avoid internal terminology.\n"
}SHA-256: dd0aadea42a64f76e9b533b81d480eb29acc7af43339fc5e01cc7872a021e5bf