If your B2B operation invoices customers in more than one country, your tooling decisions get expensive fast. This guide covers the operational shape of multi-country invoicing, the compliance requirements per market, and the three failure modes that cost mid-market companies six figures a year.
The fiscal entity model
The most important architectural decision is to separate your tenant from your fiscal entities. One business operation can own multiple legal entities — a Mexican SA de CV, a Delaware LLC, a Spanish SL — each with its own tax authority credentials, sequence numbering and local format. Each invoice is bound to the issuing entity, not to a generic "company".
Per-country compliance reality
- Mexico — CFDI 4.0. Government-stamped via PAC. RFC + CSD + fiscal regime + payment complement. Stamping latency under 5 seconds; failure rate near zero when the customer data is clean.
- Spain — Facturae / VeriFactu. Digital signature with timestamp. VeriFactu mandatory from 2026 for most B2B operations.
- Brazil — NF-e / NFS-e. NF-e for products, NFS-e for services, the latter handled per municipality. A1 digital certificate, state and municipal registrations.
- United States. No government stamping. State-level sales tax presets if you sell goods or specific services.
- Canada. GST/HST + provincial tax handling.
FX — the trap nobody talks about
If you invoice in USD from your Mexican entity, the FX rate stamped on the invoice is the only legally defensible rate for that document. Today's FX is not relevant; the rate at the moment of issue is. Most generic invoicing tools don't snapshot this — they recompute every time the report runs, breaking your historical revenue numbers. This single behavior tips operators toward fiscal-grade tooling.
The three failure modes
- One entity invoicing multiple countries. Works until your Mexican customer demands CFDI and you're issuing from your Delaware LLC. You scramble; you lose 2 months while you incorporate; the customer churns.
- Tax engine bolted on as a service. Generic SaaS handles "international taxes" by routing through Avalara or similar. Works for sales tax. Fails for CFDI/Facturae stamping which requires real-time authority calls.
- Reporting that consolidates badly. Each entity's books are clean. The consolidated view across entities recomputes FX, produces unstable numbers, your CFO loses trust. The fix: consolidate at the rate stamped on each document, not at today's rate.
The shape of "right"
One tenant. Multiple fiscal entities. Each entity carries its own credentials, format, sequence. Customer record points to a default issuing entity. Invoice generation picks the right format based on customer + entity. Consolidation rolls up at stamped FX. Audit trail preserved per document.
OMB Cloud's Billing module is built on exactly this model. The Invoices module handles the per-country formats natively.