E-commerce
July 1, 2026
"The invoice has the wrong company name, accounting refuses payment." "I entered my personal address instead of the headquarters, can you correct it?" "Our ERP is blocking: billing address ≠ registered VAT address." Three tickets where customer support confuses delivery address correction and accounting re-invoicing with credit notes.
The e-commerce wrong address invoice customer support covers incorrect billing addresses on issued PDFs, accounting impacts (credit notes, re-invoicing), legal deadlines for correction, and B2B pro vs B2C personal cases, distinct from parcel address changes or untraceable invoices.
This guide #463 covers policy INVADDR-SUP, flow INVADDR-FLOW, and KPI invaddr. Completes gift/pro invoices (#254) and missing invoice (#359): here, customer support playbook for billing address correction, accounting credit notes, and special cases.
Summary
Why do invoices with incorrect addresses hold up accounting?
A wrong address invoice ticket occurs when the issued tax PDF does not match the expected accounting data: company name, registered office, VAT number, incorrect or obsolete billing checkout address.
Five typical billing address errors
Personal company name: first/last name instead of SAS
Registered office vs establishment: delivery address copied as billing
VAT address mismatch: intracommunity number linked to another entity
SIRET or Postal Code typo: automatic ERP rejection
Group entity: subsidiary vs billed holding company
Facturii reminds that a compliant invoice must include the full identity of the professional buyer, address and VAT number if applicable (Facturii, compliant invoice 2025). Shop Circle estimates that manual corrections post-issuance absorb 15 to 25% of finance time in light DTC B2B (Shop Circle, auto invoices 2026).
Angle #463 vs neighboring content
Pro invoice #254: issuing pro gift. #463 = post-issuance address correction.
Missing invoice #359: portal lookup. #463 = PDF received but billing data incorrect.
Delivery address #183: modify shipping. #463 = accounting billing, not package.
VAT #160: excl. tax incl. tax explanation. #463 = credit note reinvoicing workflow.
Adjacent future bot #464: intracommunity VAT. #463 = billing entity address.
Light DTC B2B Example
Pro equipment, 78 invaddr tickets/month, 44% shipping vs billing confusion. Without INVADDR-SUP: invaddr_correction_sla 4.2 days, client accounting rejections 31/month. After INVADDR-MAP + flow: invaddr_correction_sla 18 hours, invaddr_first_contact_resolution 82%, invaddr_csat 4.3/5.
Billing ≠ shipping
INVADDR-FLOW rule 1: correct delivery address does not correct invoice. Distinct billing reinvoicing.
Month-end accounting spike
Last 5 business days of the month: invaddr_erp_rejected P1 volume 2x. Pre-scale finance on-call and INV-ADDR-URGENT capacity.
How does INVADDR-SUP differ from #254, #359, and parcel address?
Invoice issuance, lookup missing, shipping change, and billing correction: four distinct CS processes.
Document → CS action matrix
#463 INVADDR-FLOW: correct billing, credit note, re-invoice
#254 INV-GIFT PRO: issue initial invoice
#359 INV-MISSING: find and resend existing PDF
#183 SHIP-ADDR: change parcel shipping address
#321 PROFORMA: document before payment
Four INVADDR-TYPE pathways
invaddr_pre_payment: invoice not yet validated by accounting, simple cancellation
invaddr_post_payment: paid, credit note + new invoice mandatory
invaddr_erp_submitted: already imported into client ERP, P1 urgency
invaddr_multi_entity: change of buyer's legal entity
Promise #463
Policy INVADDR-SUP, matrix INVADDR-MAP, 12 typologies invaddr_*, flow INVADDR-FLOW, macros INV-ADDR-*, KPI invaddr_*.
Key accounting impact
Invoice issued with billing error: no simple "PDF edit". Full credit note + corrective invoice numbered in legal sequence.
Invoice correction ops stack
Sufio or Order Printer Pro credit note, Shopify billing_address metafield, Gorgias tags invaddr_*, finance approval workflow, ERP export sync.
45-Minute agent training
Module 1: billing vs shipping verbatims. Module 2: live INVADDR-MAP branches. Module 3: macro INV-ADDR-AVOIR walkthrough. Quiz 85% before invaddr queue.
Which invaddr_* typologies should be mapped?
Twelve wrong address invoice typologies for consistent helpdesk routing.
Twelve invaddr scenarios
invaddr_company_name_wrong: incorrect company name
invaddr_billing_street_typo: incorrect street, ZIP, or city for billing
invaddr_shipping_as_billing: shipping address on invoice by mistake
invaddr_vat_address_mismatch: VAT does not match address
invaddr_siret_wrong: incorrect SIRET or SIREN
invaddr_entity_change: invoice another group subsidiary
invaddr_personal_to_pro: switch from personal to professional post-purchase
invaddr_po_address: purchase order address ≠ invoice address
invaddr_erp_rejected: customer's ERP rejected import
invaddr_duplicate_invoice: two invoices with different addresses for the same order
invaddr_intracom_country: billing country impacts VAT (link #464)
invaddr_gift_buyer_billing: gift invoice with wrong buyer entity
Helpdesk tags
invaddr, invaddr_correction, invaddr_avoir, invaddr_urgent, invoice_request cross-tag. Distinct ship_addr (#183), pro_invoice_correction (#254).
Prioritization
P1: invaddr_erp_rejected accounting deadline < 24 h. P2: invaddr_post_payment credit note pending. P3: invaddr_pre_payment simple void.
Mining invaddr verbatims
90-day export "correct invoice", "wrong billing address", "wrong company name", "credit note reinvoicing", "accounting rejects", "registered office address".
Intake data IA-1
order_id, invoice_number, caller_role buyer accountant third, billing_error_type, payment_status, erp_submitted Y/N, correct_billing_json requested.
Checkout prevention field
Separate billing address checkbox default expanded B2B SKU: reduce invaddr_shipping_as_billing at source.
How should the INVADDR-MAP matrix be structured?
The INVADDR-MAP matrix links error type, authorized accounting action, SLA, and required auth.
Lookup INVADDR-MAP fields
error_type → action: void | credit_note_re-invoice | amend_pre_send
payment_status gate: unpaid void OK, paid credit note mandatory
fields_correctable[]: company, street, city, zip, vat, siret
auth_level: email order match L1, finance approve L2 entity change
sla_hours: P1 4 h, P2 24 h, P3 48 h
finance_handoff: entity_change multi_entity always
Example INVADDR-MAP lines
invaddr_company_name_wrong + paid → credit note INV-001 + re-invoice INV-002 billing corrected, SLA 24 h.
invaddr_pre_payment + draft not sent → void regenerate, SLA 4 h agent alone.
invaddr_entity_change → finance approval mandatory, PO verify, SLA 48 h P1 if erp_rejected.
Non-editable fields post-issuance
Subtotal and Total amounts, original issuance date, sequence number: billing correction does not change product lines except for separate error #254.
Invoice App Sync
Sufio credit note API, link original invoice, new invoice references credit note number. Aligned CSV accounting export.
Auth before correction
Apply auth #122 L1 email order. Accountant third: email domain company match or buyer consent.
Invoice number chain audit
IA-8 log original_invoice, credit_note_number, corrected_invoice_number, timestamp, agent_id for quarterly finance audit.
How to write the INVADDR-SUP policy in eight rules?
The INVADDR-SUP invoice address correction policy governs credit notes, rebilling, and agent limits.
Eight INVADDR-SUP rules
Billing not shipping: invoice correction ≠ parcel address change #183
Avoir before reissue paid: paid invoice = total credit note then rebill, never edit PDF alone
Auth email order: requester = buyer's email or authorized accounting
Collect correct billing JSON: company name, address, VAT, SIRET before execution
Finance gate entity change: invaddr_entity_change mandatory finance approval
Reference original invoice: corrected invoice cites credit note and initial invoice numbers
No price change billing fix: address correction does not modify amounts except for separate VAT ticket
Confirm ERP resubmit: post-correction macro instructions for importing new PDF
Agent prohibitions
Resending the same PDF "corrected" manually without credit note sequence. Modifying amounts during address correction. Sending invoice with corrected shipping address to gift recipient.
Gift invoice billing
invaddr_gift_buyer_billing: correction on buyer email order entity, never shipping recipient. Align gift receipt #459.
DPO retention
Retain credit note and initial invoice for GDPR audit trail. Do not delete erroneous PDF, cancel via credit note.
Legal sequence France
Credit note mentions cancelled original invoice, corrected invoice has distinct sequential number, correction issue date. DPO validate Sufio template.
How to apply the INVADDR-FLOW flow in eight steps?
The INVADDR-FLOW IA-1 to IA-8 flow structures the processing of wrong address invoice tickets.
Eight steps IA-1 to IA-8
IA-1 Intake: order_id, invoice_number, invaddr_* classify, erp_submitted
IA-2 Auth: email order match or accountant authorized domain
IA-3 Diagnose: compare billing PDF vs correct data client provides
IA-4 INVADDR-MAP lookup: action void | avoir_refacture, sla, finance_gate
IA-5 Collect confirm: macro INV-ADDR-CONFIRM correct billing JSON signed off
IA-6 Execute: void draft | credit note Sufio | regenerate invoice
IA-7 Deliver: email PDF corrected + credit note to buyer email, ERP instructions
IA-8 Document: tags invaddr_*, invoice numbers chain, csat macro
IA-4 pre_payment branch
Invoice draft or not yet exported: void regenerate under 4 h, no credit note if never officially issued in accounting.
IA-4 post_payment branch
Credit note 100% lines, new invoice identical amounts new billing. Chain numbers in IA-8.
IA-4 erp_rejected P1 branch
Escalate to finance same day. Macro INV-ADDR-URGENT with new PDF + ERP re-import guide.
IA-6 entity_change
Finance validates PO entity match, VAT of new entity verified link #464 future. Agent holds until approved.
IA-3 shipping confusion
If client only needs parcel address: route to #183 SHIP-ADDR, not INVADDR.
IA-5 double confirm entity
For invaddr_entity_change: client confirms legal name + VAT + billing address twice in ticket before finance handoff to reduce typo cycle.
Which INV-ADDR-* macros and templates should be used?
Eight invoice address correction macros for consistent responses grounded in INVADDR-MAP.
INV-ADDR-CONFIRM (data collection)
"To correct your invoice #[X], please confirm: company name, registered billing address, postal code, city, country, VAT number, SIRET. Reply with the complete block to avoid a second loop."
INV-ADDR-AVOIR (post-payment)
"Credit note #[A] issued canceling invoice #[X]. New invoice #[Y] with corrected address attached. Please import #[Y] into your ERP. Credit note #[A] cancels #[X] in accounting."
INV-ADDR-VOID (accounting pre-submission)
"Invoice #[X] cancelled before accounting validation. New invoice #[Y] with corrected address is attached hereto. No credit note required."
INV-ADDR-SHIP-REDIRECT
"Your request concerns the package delivery address, not the billing address. I am redirecting you to delivery modification #[order]. The invoice remains on your buyer entity."
INV-ADDR-ERP-GUIDE
"ERP: cancel import of invoice #[X], import credit note #[A] then invoice #[Y]. Billing fields: [summary]. ERP support: [FAQ link if existing]."
INV-ADDR-URGENT P1
"Priority correction within 4 business hours. Documents sent to accounting@[client]. Numbers: credit note #[A], invoice #[Y]."
INV-ADDR-FINANCE-HOLD
"Legal entity change: finance validation required within 48 hours. PO #[PO] and VAT for new entity verified. Ticket escalated to finance-invaddr."
INV-ADDR-DENY-THIRD
"Invoice correction reserved for buyer or authorized accounting email domain @[company]. Please contact #[buyer email hint]."
INV-ADDR-CSAT follow-up
48 hours post corrected PDF delivery: "Did your ERP accept invoice #[Y]? Reply yes/no." Feeds invaddr_erp_resubmit_success KPI.
Which B2B, gift, and multi-currency use cases should be handled?
Special billing address cases require INVADDR-MAP extensions or handoff.
B2B payment terms
Net 30 invoice with wrong entity: correction before P1 due date. Link payment terms (#234). PO address mismatch verify PO entity.
Multi-devise order
Credit note reinvoice same currency original invoice. Link multi-devise (#452). Billing address country may affect VAT display not FX.
Gift buyer wrong company
Gift buyer enters personal details, wants company invoice for expense claim: invaddr_personal_to_pro post-payment credit note. PDF to buyer email only #254.
Proforma converted
Error on final invoice post-proforma: #321 conversion chain + INVADDR credit note.
Duplicate invoice same order
invaddr_duplicate_invoice : void incorrect duplicate, keep corrected chain documented IA-8.
Intracom country billing
Address country change may trigger VAT recalc : split ticket TVA #160 #464 if amounts change, not pure INVADDR.
Accountant third party
compta@client.fr requests : verify domain match company on invoice or buyer forward authorization.
Chargeback open
Payment dispute open : hold INVADDR correction until chargeback resolved finance gate.
Wire transfer pending
Bank transfer not yet matched : void proforma or draft invoice easier path before payment clears. Link bank transfer support if exists.
Which KPIs should be measured?
Invoice address correction KPIs link accounting SLAs, FCR, and process errors.
Eight key metrics
invaddr_ticket_rate: invaddr tickets / 100 finance tickets
invaddr_correction_sla: average hours for credit note + reinvoice delivered
invaddr_first_contact_resolution: corrected without recontact / tickets
invaddr_ship_confusion_rate: routed #183 / total invaddr
invaddr_avoir_chain_complete: credit note + reinvoice both sent / post_payment
invaddr_erp_resubmit_success: customer confirms import OK / P1
invaddr_finance_escalation_rate: entity_change handoffs / total
invaddr_csat: post-correction satisfaction
DTC B2B light Benchmark
invaddr_correction_sla < 24 h P2, < 4 h P1, invaddr_first_contact_resolution > 78 %, invaddr_avoir_chain_complete 100 %.
Finance-support Dashboard
Error type breakdown, SLA breach P1, ship vs billing misroute, repeat tickets same order.
Root cause checkout
Track invaddr_shipping_as_billing rate: feed reduce address errors checkout UX billing separate field.
Repeat ticket same order alert
Second invaddr ticket same order_id within 14 days: supervisor review IA-5 collect incomplete or ERP guide unclear.
Which invoice correction anti-patterns should be avoided?
Twelve bad address invoice anti-patterns to ban in CS and finance.
1. Edit PDF manually
Rule 2 credit note mandatory paid. No Photoshop PDF.
2. Confondre shipping correction
Rule 1 INV-ADDR-SHIP-REDIRECT #183.
3. Skip avoir post-payment
Double customer accounting if re-invoiced without cancellation.
4. Partial billing JSON
Rule 4 collect complete before IA-6.
5. Entity change sans finance
Rule 5 fraud risk VAT misuse.
6. Send corrected invoice to shipping address
Gift leak risk. Buyer email only.
7. Change amounts during address fix
Rule 7 split VAT ticket if needed.
8. No reference chain numbers
Rule 6 ERP reject repeat.
9. Third party no auth
INV-ADDR-DENY-THIRD accountant domain verify.
10. Delete original wrong invoice
Audit trail: credit note cancels, never delete.
11. Promise same-day sans finance capacity
INV-ADDR-URGENT only if finance SLA confirmed.
12. Resend missing invoice as correction
Route #359 if client never received, not invaddr.
13. Mix TVA correction in address ticket
If VAT amount changes with country: split invaddr billing fields only vs separate VAT ticket #160 avoid wrong credit note amounts.
How does Qstomy help with INVADDR tickets?
Qstomy on Shopify qualifies invaddr_* tickets upstream: distinguishes billing vs shipping, collects structured billing JSON, applies auth #122, routes INVADDR-MAP action, handsoff finance entity_change with complete payload.
Qstomy invaddr Capabilities
invaddr_intent_classifier: 12 typologies section 3
billing_vs_shipping_router: redirect #183 vs INVADDR
invaddr_map_lookup: void credit invoice sla finance_gate
billing_json_collector: structured confirm macro
finance_handoff_payload: order invoice chain ERP flag
Pipeline #463 #254 #359 future bot
#463 playbook agents correction. #254 initial issuance. #359 lookup. Documents bot (#255) automates resend post-correction.
DTC scenario figures
B2B light equipment, 78 invaddr tickets/month, 44% ship confusion baseline.
After INVADDR-SUP + Qstomy classify: invaddr_correction_sla 16 h, invaddr_first_contact_resolution 84%, invaddr_ship_confusion_rate -62%, invaddr_csat 4.4/5.
Explore customer support and request a demo.
Sync bot corpus
INVADDR-MAP JSON feed bot #255 intents invoice_correction_address future automate tier 1 collect.
Weekly invaddr QA sample
Review 10 closed invaddr tickets: credit invoice chain complete, no ship confusion, auth documented.
What is the checklist for deploying INVADDR-SUP?
Checklist INVADDR-SUP (12 steps)
Document INVADDR-MAP error_type action sla finance_gate
Draft policy INVADDR-SUP 8 rules
Configure 12 tags invaddr_* helpdesk
Create 8 macros INV-ADDR-* section 7
Train agents INVADDR-FLOW 45 min (IA-4 branches, have chain)
Workflow finance credit note Sufio test staging
Auth #122 + accountant domain allowlist
Route shipping confusion → #183 macro INV-ADDR-SHIP-REDIRECT
SLA P1 erp_rejected 4 h finance on-call
Dashboard KPI invaddr section 9
Checkout audit billing field separate shipping
Sync INVADDR-MAP → bot #255 corpus
In brief
#463 = billing address correction, not parcel address
Paid = credit note + re-invoice, never edit PDF
INVADDR-MAP: action by error_type payment_status
P1 erp_rejected: SLA 4 h
KPI invaddr_avoir_chain_complete: target 100%
FAQ
Is correcting shipping address enough?
No. Parcel #183. Invoice billing separate buyer entity INVADDR.
Can we modify the PDF directly?
No if issued in accounting. Credit note cancels, corrective re-invoice numbered.
Difference from #254?
#254 initial issuance gift pro. #463 post-issuance correction of billing address.
Can a third-party accountant request?
Yes if company domain matches or buyer L1 auth consent.
Subsidiary entity change?
Finance gate mandatory, PO VAT verify, SLA 48 h.
Go further
This week: publish INVADDR-MAP JSON, create macros INV-ADDR-AVOIR test credit note chain Sufio staging, train agents IA-4 branches 45 min, activate tag invaddr_erp_rejected P1, launch dashboard invaddr_correction_sla.
Share this guide #463 with finance and customer service: one macro INV-ADDR-SHIP-REDIRECT is worth ten parcel corrections handled as re-billing, a complete credit note chain is worth five client ERP rejections and repeat tickets in accounting.
Enzo
July 1, 2026
