Connect Daftra to CII & UBL by InvoiceXML

Both apps 61Daftra 47CII & UBL by InvoiceXML 14

• Trigger
  Client Created

  Triggers when a new client is added to your Daftra account.

• Trigger
  Client Updated

  Triggers when a client is added or updated in Daftra.

• Trigger
  Estimate Updated

  Triggers when an estimate (quote) is created or updated in Daftra.

• Trigger
  Invoice Created

  Triggers when a new invoice (or debit note) is created in Daftra.

• Trigger
  Invoice Updated

  Triggers when an invoice or debit note is created or updated in Daftra.

• Trigger
  Journal Created

  Triggers when a new journal entry is created in Daftra.

• Trigger
  Journal Updated

  Triggers when a journal entry is created or updated in Daftra.

• Trigger
  Product Created

  Triggers when a new product is added in Daftra.

• Trigger
  Product Updated

  Triggers when a product is added or updated in Daftra.

• Action
  Add Client

  Creates a new client in Daftra and returns its id and client number.

• Action
  Add credit note

  Creates a credit note for a client in Daftra, optionally against a source invoice, with line items.

• Action
  Add Estimate

  Creates a new estimate (quote) for a client in Daftra, with optional line items.

• Action
  Add Expense

  Creates an expense in Daftra with its amount, date, vendor, category and optional taxes, account splits and cost-center allocations.

• Action
  Add Invoice

  Creates a sales invoice for a client in Daftra, with optional line items and payments, and returns the new invoice's id.

• Action
  Add Invoice Payment

  Records a payment against an existing Daftra invoice and returns the new payment's id.

• Action
  Add Journal

  Creates a manual double-entry journal entry with its debit and credit lines. Total debits must equal total credits.

• Action
  Add Product

  Creates a new product, service or bundle in Daftra and returns its id.

• Action
  Add Refund Receipt

  Creates a refund receipt against an existing invoice in Daftra, with optional refunded line items and refund payments.

• Action
  Add Supplier

  Creates a new supplier in Daftra and returns its id.

• Action
  Delete Client

  Deletes a client from Daftra. The client must have no invoices, payments or other related records.

• Action
  Delete credit note

  Deletes a credit note in Daftra by its ID.

• Action
  Delete Estimate

  Deletes an estimate (quote) in Daftra. Estimates already converted to an invoice or sales order cannot be deleted.

• Action
  Delete Expense

  Deletes an expense in Daftra, along with its related accounting journal and attachments.

• Action
  Delete Invoice

  Deletes a sales invoice in Daftra by its ID.

• Action
  Delete Invoice Payment

  Deletes an invoice payment, re-adjusting the related invoice's paid total and the client's balance.

• Action
  Delete Product

  Deletes a product, service or bundle in Daftra by its ID.

• Action
  Delete Refund Receipt

  Deletes a refund receipt in Daftra by its ID.

• Action
  Delete Supplier

  Deletes a supplier from Daftra. Suppliers referenced by purchase orders, expenses or other transactions cannot be deleted.

• Action
  Edit Client

  Updates an existing client in Daftra. Only the fields you fill in are changed.

• Action
  Edit Estimate

  Updates an existing estimate (quote) in Daftra, changing its client, date, currency, notes or line items.

• Action
  Edit Expense

  Updates an existing expense in Daftra. Only the fields you fill in are changed.

• Action
  Edit Invoice

  Updates an existing standard invoice in Daftra, including its header details, line items, payments and custom fields.

• Action
  Edit Invoice Payment

  Updates an existing invoice payment in Daftra. Only the fields you fill in are changed.

• Action
  Edit Journal

  Updates an existing journal entry in Daftra, replacing its debit and credit lines.

• Action
  Edit Product

  Updates an existing product, service or bundle in Daftra. Only the fields you fill in are changed.

• Action
  Edit Refund Receipt

  Updates an existing refund receipt in Daftra — its date, currency, store, notes or line items.

• Action
  Edit Supplier

  Updates an existing supplier's business name, contact details, addresses and other details.

• Action
  Get client

  Returns a single Daftra client by id, with its contact details, addresses, balances and custom field values.

• Action
  Get Expense

  Returns a single expense by its id, including amount, taxes, totals, vendor, category, date and status.

• Action
  Get invoice

  Returns a single standard invoice by ID, with its line items, payments, taxes, client and custom fields.

• Action
  Get Purchase Order

  Returns a single purchase order by its ID, including its line items, supplier, taxes, payments and custom fields.

• Action
  Get Refund Receipt

  Returns a single refund receipt by ID, including its line items, payments, taxes, custom fields and client.

• Action
  List clients

  Returns a list of clients in your Daftra account, optionally filtered by keyword or assigned staff member.

• Action
  List estimates

  Returns the account's estimates (quotes), most recent first, optionally filtered by client, number, status, amount, dates and more.

• Action
  List invoices

  Returns a page of your Daftra invoices and debit notes, most recent first, optionally filtered by client, status, dates, amounts and more.

• Action
  List products

  Returns a page of products and services in your Daftra account, optionally filtered by keyword, category, supplier, brand, stock status, barcode or product code.

• Action
  Update credit note

  Updates an existing credit note in Daftra — its client, date, currency, store, notes or line items.

• Action
  Convert CII to UBL

  Translates a UN/CEFACT CII invoice XML into a standards-compliant UBL 2.1 XML document, enabling interoperability between systems that use different e-invoice formats.

• Action
  Convert UBL to CII

  Transforms a UBL 2.1 invoice XML into a UN/CEFACT CII XML document, bridging compatibility between PEPPOL-based systems and CII-native accounting platforms.

• Action
  Create CII Invoice

  Produces a UN/CEFACT Cross-Industry Invoice (CII) XML document from structured billing data, ready for submission through any EN16931-compliant e-invoicing channel.

• Action
  Create UBL Invoice

  Generates a standards-compliant UBL 2.1 XML invoice from structured billing data including seller, buyer, line items, and payment details.

• Action
  Extract Invoice Attachments

  Download an e-invoice's embedded attachments as a ZIP.

• Action
  Extract Invoice JSON

  Parses a PDF invoice into machine-readable JSON, reading embedded CII or UBL XML when available and applying AI-based extraction as a fallback for unstructured PDFs.

• Action
  Extract Invoice XML

  Pull the CII or UBL XML out of an e-invoice PDF.

• Action
  Parse Invoice JSON

  AI-parse any PDF invoice — messy, scanned, or handwritten — into structured JSON.

• Action
  Render CII to PDF

  Produce a human-readable PDF from a CII e-invoice.

• Action
  Render UBL to PDF

  Produce a human-readable PDF from a UBL e-invoice.

• Action
  Transform PDF to CII

  Reads an existing PDF invoice and produces a UN/CEFACT CII XML document using AI-powered data extraction. Ideal for digitising paper-based or scanned invoices into a structured CII format. Note: AI can make mistakes; review output before sending.

• Action
  Transform PDF to UBL

  Reads an existing PDF invoice and produces a UBL 2.1 XML document using AI-powered data extraction. Useful for onboarding legacy invoices into structured e-invoicing workflows. Note: AI can make mistakes; review output before sending.

• Action
  Validate CII Invoice

  Verifies a UN/CEFACT CII invoice XML against EN16931 semantic rules and XSD schema, returning a detailed compliance report including any rule failures or data inconsistencies.

• Action
  Validate UBL Invoice

  Checks a UBL 2.1 invoice XML against EN16931 business rules and schema constraints, returning a structured validation report with any rule violations or structural errors.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.