Stripe VAT in Portugal: setup without surprises
Best practices to configure VAT, map tax codes, and avoid compliance issues in InvoiceXpress documents created from Stripe payments.
Where tax data comes from
LusoInvoice reads fiscal data from Stripe (tax rates, Stripe Tax, and default rates) and maps it into InvoiceXpress issuance context.
When explicit tax data is missing on a payment, the LusoInvoice default VAT setting acts as an operational fallback.
Recommended VAT mapping strategy
Define rules by product category and keep Stripe pricing logic aligned with InvoiceXpress tax configuration. Consistency reduces document mismatches.
Use exemption codes only when legally applicable, and document internal criteria for audit readiness.
- Set a default VAT rate for edge cases.
- Review exemption codes before going live.
- Validate behavior for tax-inclusive and tax-exclusive prices.
Common errors and prevention
Most issues originate from incomplete payment data, wrong document sequence selection, or inconsistent tax mapping rules.
A monthly sample review of issued documents helps detect deviations early and maintain control.
- Avoid tax-rule changes without impact validation.
- Monitor voided documents to identify recurring issues.
- Review logs whenever Stripe totals and invoice totals diverge.
Quick FAQ
Does LusoInvoice calculate VAT independently?
No. It uses Stripe tax data and applies the configured mapping for issuance in InvoiceXpress.
Can different customers use different tax settings?
Yes, as long as Stripe payment data is complete and InvoiceXpress rules are aligned with your scenarios.