E-commerce
June 29, 2026
"Send me my invoice." The bot responds with a generic link to the contact page. The customer insists. The agent searches for the PDF in Sufio for 8 minutes. A competitor had promised an intra-community VAT-free invoice via chat: accounting dispute three weeks later. Post-purchase chatbot documents are a high-ROI, high-tax-risk use case.
Fin estimates that payment-related inquiries (invoice, status, dispute) represent a growing segment once WISMO is automated (Fin, ecommerce 2026). Tactas recommends supervised automation: auto lookup and re-sending, VAT corrections and refunds behind human approval (Tactas, ecommerce AI 2026).
This guide #255 covers the AI chatbot for invoices and order documents. Complements invoice requests (#254) (human workflows): here, which bot intents, which guardrails, which API integrations.
Summary
Why is automating post-purchase documents in a bot sensitive?
An e-commerce invoice bot handles tax data, PII, and gift confidentiality. An error costs more than a failed WISMO.
Three specific risks
Document leak: PDF sent to the gift recipient or a third party
Tax hallucination: bot promises VAT exemption or unauthorized refund
Non-compliant document: Shopify confirmation presented as a legal invoice
Opportunity if structured
Shop Circle: automated PDF link in confirmation email reduces "where is my invoice" tickets by 40-60% (Shop Circle, auto invoices 2026). The bot complements this self-service for re-sending, status, and collecting missing professional details.
Home DTC Example
Home decor brand, 180 invoice tickets/month. Generic bot without lookup: deflection 12%, 1 incident/month of sending invoice to wrong email. Document bot with double auth + Sufio link: deflection 61%, qualified finance escalations −44%, recipient incidents 0 over 9 months.
How does it differ from the neighboring invoice and bot guides?
Five document contents, five levels of automation.
Human invoice requests (#254)
Invoice (#254): INV-* macros, agent workflows. #255: mirror bot intents + technical guardrails.
VAT questions (#160)
VAT (#160): explanation of incl. VAT/excl. VAT, EU VAT. #255: document action (PDF link, SIRET collection), not tax class.
WISMO / returns bot
Shared order lookup, but different intents: BFCM bot (#252) and return prequalification (#138) do not handle company name or PO corrections.
Authentication (#122)
Auth (#122): general rules. #255: email + order number binding before any PDF link.
Multichannel duplicates (#256)
Multichannel duplicates (#256): merging email, chat, social tickets. #255 generalizes the ticket already open on same intent logic beyond documents.
Which bot document intents should be prioritized?
Eight document bot intents by ROI and increasing risk.
Tier 1: auto without write (live week 1)
invoice_resend: resend existing PDF linkorder_confirmation_copy: confirmation email vs invoice, redirectinvoice_where: customer account + spam, not yet issuedpacking_slip_policy: packing slip vs invoice
Tier 2: collection + handoff (week 3-4)
gift_invoice_buyer: buyer PDF onlypro_invoice_collect: missing SIRET, VAT, company nameinvoice_po_add: PO collection → finance ticket
Tier 3: immediate human/finance escalation
invoice_vat_correction: incl. tax → excl. tax, VAT refundinvoice_credit_note: credit note, corrected invoice
End note: invoices and Stripe billing cover a payment aspect, not FR tax compliance (End, Stripe billing). The bot forwards, it does not re-issue without a connected accounting app.
How to authenticate before any document submission?
The invoice auth bot follows the same principle as secure WISMO: mandatory double identification.
4-step auth flow
Request email + order number (both required for PDF link)
Query Shopify: email = order billing email
If mismatch: polite refusal + macro INV-REFUSE-01 (#254), no guessing
If match: continue intent, log auth OK
Alhena: email as binding key, order number alone is insufficient (Alhena, secure lookup 2026).
Minimal exposed fields
Bot confirms: invoice number, date, total amount including tax, PDF link. Masked: full shipping address, last 4 digits of credit card, third-party email. Align auth (#122).
Logged-in session
Customer logged into Shopify account: skip double entry if session email = order email. Always confirm order number if there are multiple recent orders.
Third-party accountant
Intent invoice_third_party: auto-refusal, collect buyer email + written authorization → human handoff.
How do I configure the gift invoice flow in the bot?
The gift invoice bot scenario inherits from rules #254 with code safeguards.
Gift detection
Flags: shipping_address ≠ billing_address, tag gift, line property gift message, explicit intent "I gave". See gift (#205).
Flow gift_invoice_buyer
Buyer email authentication + order no.
Verify paid, no chargeback
Retrieve PDF URL from billing app (Sufio, Order Printer Pro)
Send link only to authenticated email (not shipping)
Message: "Invoice sent to [email]. The recipient does not receive a tax document."
Bot restrictions
Sending PDF to the delivery address "so that the recipient can print it". Modifying amounts or VAT upon chat request. See anti-overpromising (#209).
Christmas Peak
Sync corpus with macros INV-GIFT-01 (#254). Volume ×3 Nov-Jan: prioritize tier 1 intent before VAT corrections.
How do I configure the professional invoice flow in a bot?
The pro invoice bot scenario collects data but does not validate taxation on its own.
Flow pro_invoice_collect
Auth + order lookup
Read billing fields: company, VAT number present?
If complete + PDF exists: resend link + mention reverse charge if VIES tag is OK
If incomplete: collect company name, address, SIRET/VAT (FR/BE/DE regex validated format)
Create finance ticket tagged
pro_invoice_collectwith structured formBot: "File forwarded to accounting, PDF within 48 business hours."
Pro collection bot messages
"To issue your corporate invoice, I need: exact company name (copy-paste from registration document), billing address, VAT number. Please reply in this chat, and I will forward this to our accounting department." If client sends invalid VAT: "Expected format: FR + 11 digits. Please check your number on your official company documents."
PO and Net terms
Intent invoice_po_add: collect PO → handoff. Net terms and due date: refer to payment terms (#234), bot does not modify due date.
Static VAT Corpus
Bot quotes policy #160: "exemption subject to VIES validation at checkout". Without VIES trace in order → escalate invoice_vat_correction, no promise of tax-exempt price.
Which API integrations and live document sources?
The documents bot stack reads PDF URLs, not a static corpus.
Shopify Orders API
Fields: order name, email, billing, shipping, tags, PO metafields, financial_status, company, tax_lines. Basic auth and routing for gift vs pro.
Invoicing App
Sufio / Facturii / Regulo: PDF URL by order_id
Order Printer Pro: dynamic email link + API
APITemplate: PDF generation via order/paid webhook if custom
APITemplate: invoices from structured order data via API (APITemplate, ecommerce docs).
Shopify Customer Account
Intent invoice_where: bot returns link /account/orders/[id] if PDF is hosted there. Reduces "I can't find it" tickets.
Cron Sync and Latency
Webhook order/paid → index order_id + invoice_url + invoice_number in bot cache. App issuance latency (5-30 min): bot message "invoice being generated, email within 1 hour or check back here". Digiqt recommends idempotency keys on document actions to avoid double sending (Digiqt, chatbots payments 2026).
Dynamic Macro Variables
Bot injects: {{invoice_number}}, {{invoice_url}}, {{order_name}}, {{billing_company}}. Never generate a fabricated URL: if cache is empty, escalate or show a waiting message.
What safeguards and trust routing should be applied?
The document bot guardrails separate read-only lookup and fiscal write.
Autonomy matrix
Auto: return auth OK PDF link, explanation confirmation vs invoice
Collect + ticket: missing pro data, PO, accounting email
Immediate escalation: VAT correction, credit note, amount > €2,000, non-auth third party
Block: PDF request to shipping, order number only
Confidence threshold
If invoice intent + confidence < 85% or hybrid question ("invoice and VAT refund"): handoff with transcript. See anti-hallucination.
Witness and litigation
Witness.ai cites Moffatt v. Air Canada: organization held liable for bot-invented policy (Witness, ecommerce agents 2026). Document bot: never promise VAT refund or unscripted fiscal timeline.
Audit log
Log: order_id, intent, auth result, link sent yes/no, escalation. Monthly review of 20 conversations via bot audit.
How to structure the finance and agent handoff?
The invoice bot handoff prevents finance from starting from scratch.
Mandatory handoff package
Intent + confidence score
Order #, email auth, paid status
Gift or pro flag
Current vs. requested billing fields (diff)
Existing invoice number if PDF is already issued
Customer verbatim (VAT correction, PO, accounting@)
Bot → finance SLA
Ticket automatically created in Gorgias side panel. P1 if customer accounting deadline < 24 hours. Bot message before handoff: "An accounting advisor is taking over, case #[ref], response time 48 business hours."
Agent training
30 min: read bot handoff, do not ask for email + order number again, when to use the INV-CORRECT macro vs what the bot has already collected. Train bot team.
Which bot document anti-patterns should be avoided?
Six invoice bot errors cost more than no bot at all.
Generating invoices without an accounting app
Invented PDF or renamed confirmation. Fix: app-only link.
Authentication via order number alone
Order enumeration risk. Fix: email + order number mandatory.
Sending invoice to gift shipping address
Fix: hard block if shipping ≠ billing + gift intent.
Promising VAT corrections in chat
Fix: financial escalation, "pending accounting validation" corpus.
Static, out-of-sync tax corpus
Bot quotes outdated reverse charge clause. Fix: sync policy #160 + VAT app.
100% automated from Day 1
Tactic: deploy tier 1 read-only for 2 weeks, measure, then pro collection. Pilot 10% of invoice traffic before going 100%.
How does Qstomy automate invoices and documents?
Qstomy processes tier 1-2 document intents with Shopify auth and billing app PDF URL sync.
Bot document features
Dual auth email + order binding
invoice_resend: live Sufio/OPP link
gift_invoice_buyer: shipping block
pro_invoice_collect: finance handoff sheet
Confidence routing: VAT → escalation
Audit trail: sent link log
Quantified DTC scenario
Pro-light brand, 220 invoice tickets/month, 35% Dec peak. Static bot alone: deflection 14%, human AHT 9 min. Qstomy 6 intents + Sufio sync + auth: deflection 58%, human AHT 4 min, "not received" repeat tickets −51%, finance escalations with complete files 89%, PDF leak incidents 0.
Explore Shopify integration, AI customer support, request a demo.
Which playbooks can be deployed in 4 weeks?
Week 1: stack + PDF index
Live billing app. Webhook order/paid → cache invoice_url. Test 10 B2C, French pro, and BE intracommunal orders.
Week 2: tier 1 intents
Live invoice_resend, invoice_where, order_confirmation_copy. Dual auth mandatory. QA 15 test conversations.
Week 3: gift + pro collect
gift_invoice_buyer, pro_invoice_collect, invoice_po_add. Align macros #254.
Week 4: guardrails + escalation
VAT/credit_note routing → finance. Audit 20 logs. Train agents on handoff section 9.
Playbook test 12 scenarios
Resend OK, spam, auth fail, gift shipping block, pro missing fields, PO add, VAT correction escalation, third-party refusal, PDF not yet generated, logged-in account, multi-order, hybrid invoice+return.
Useful links
Automating invoices with a bot is not about replacing your accountant with an LLM. It is about sending the right PDF to the right email, collecting what is missing, and escalating everything related to VAT before an agent tries to improvise. Properly framed, administrative post-purchase becomes silent; poorly framed, it becomes a tax risk.
Enzo
June 29, 2026
