Blog

What happens if the AEAT is unavailable when you issue an invoice?

An AEAT outage does not require invoicing to stop. Learn how issuance, retries and pending VERI*FACTU registration records should work.

How to correct an invoice after it has been issued

An issued invoice should not be edited or deleted. Learn when to use a credit note, replacement or cancellation and how FiscalRail preserves the history.

FiscalRail Ruby SDK Released

VERI*FACTU and B2B e-invoicing are not the same thing

VERI*FACTU governs invoicing systems and fiscal records; B2B e-invoicing governs structured exchange between businesses. Here is how they fit together.

Introducing payment instructions

Add validated bank-transfer details to invoices by default or per invoice, without changing past documents.

Introducing customer-specific invoice prefixes

Use customer-specific invoice prefixes to keep invoice numbers sequential per customer, while preserving FiscalRail's durable issuance workflow.

Why FiscalRail asks for an AEAT power

Why FiscalRail uses the AEAT's IZ860 power for VERI*FACTU instead of storing client certificates or relying on social collaboration.

Introducing FiscalRail

FiscalRail is a focused invoicing API for the common 80%: immutable invoices, atomic numbering, free Test accounts, and Spanish support.