← BillabexCONTENT HISTORY
WHAT CHANGED
Update to Billabex
Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Billabex and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Import an invoice document into Billabex for payment follow-up, creating the customer account first when it does not exist yet. Use when the user shares an invoice PDF or image, or asks to add, upload or import an invoice.",
"included_files": [],
"name": "import-invoice",
"skill_md_contents": "---\nname: import-invoice\ndescription: Import an invoice document into Billabex for payment follow-up, creating the customer account first when it does not exist yet. Use when the user shares an invoice PDF or image, or asks to add, upload or import an invoice.\n---\n\n# Import Invoice\n\n1. Resolve the organization if needed. Read the invoice and extract its number, issue date, due date, currency, total amount including tax, tax amount, any amount already paid, and the customer: legal name, SIREN or SIRET, VAT number and billing address. Never guess a missing value: ask for it.\n2. Find the customer with the `query` parameter of `list-accounts`, trying the legal name and then a shorter distinctive part of it. When candidates appear, compare their SIREN, VAT number or address with `get-account`. Ask the user to choose when several remain plausible.\n3. When no account matches, propose to create one from the invoice: legal name, SIREN, VAT number, billing address and the invoice currency. Call `create-account` only after the user confirms these values. If the organization syncs invoices from a billing tool, say that the customer may simply not be synced yet, and let the user decide.\n4. Check for a duplicate with `list-invoices` for that account, filtering `number` equal to the invoice number. If the invoice already exists, show it and stop: never change its number to get around the duplicate.\n5. Summarize the customer and invoice values, then generate one UUID `importId` and keep it with exactly the same values for every retry.\n6. Call `create-invoice-from-file` with the native ChatGPT attachment. Never invent a download URL or ask for base64. If the file cannot be transferred or the download fails, call `prepare-invoice-upload` with the SAME `importId` and values, then give the user the link exactly as returned, in full: the link expires after 15 minutes and preparing it does not create the invoice. Report success only once the import result or `get-invoice` confirms the invoice.\n7. Check that the customer has a contact with an email address using `list-contacts`. Without one, Billabex cannot follow up: offer to add one with `create-contact`, using only a name, email and language the user provides.\n8. Confirm the import in business terms, without technical identifiers.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}SHA-256 of public snapshot: 828d76617a12470a1ccd1297c5bc937a4bdbd02d687e65091dbe121a27a2019d