Spain's Immediate Supply of Information sits in most project plans under a heading it does not belong in. It is not an invoicing mandate. Nothing in it changes the document you send your customer: that document can remain a paper original, a PDF attached to an email, or a structured file, and the obligation is identical in each case.
What the regime does is take the records that would have gone into your VAT registers and require them to be submitted to the tax administration within a short window of the invoice being issued or, for purchases, recorded. The registers are then assembled at the administration's electronic office from what you have sent. You still keep your own accounting. You no longer keep the statutory registers as a private artefact produced only when somebody asks for it.
That is a reporting obligation rather than an invoicing one, and the general shape of the distinction is set out in clearing a document versus reporting data about it. In Spain the distinction is not academic, because both obligations exist, they come from different laws, and they catch different populations.
The four registers, not the invoice
The regime covers the statutory VAT registers: invoices issued, invoices received, capital goods, and certain intra-Community transactions. Each submission is a record about an invoice — who the counterparty is, how the document was numbered, when it was issued, what the taxable base and tax amounts were, which treatment keys apply, and, for purchases, when you booked it and how much you intend to deduct.
A record is not the invoice. There is no line detail, no unit price, no item identifier, no attachment. Where a structured invoice carries coded information about what was sold, the record carries a free-text description of the operation. A machine can total it. A machine cannot tell from it what was bought.
A window measured in working days
The deadline is counted in working days from a triggering event, not in weeks from the end of a period. The exact count and the excluded days are fixed in the VAT regulation as amended and published in the official gazette; read them there rather than in a vendor summary, because they have been changed since the regime began.
The triggering event differs by register, and that is the part most often misread. For invoices you issue, the clock starts at issue. For invoices you receive, it starts when you record the document in your books — you choose that date, but not indefinitely, because the record still has to land inside the settlement period in which the deduction is taken. Slow booking does not buy time; it buys a compressed queue at the end of the period.
Outbound records come from a system you own, on a schedule you set. Inbound records depend on a supplier's document reaching somebody who books it, and on that person booking it promptly. An accounts payable backlog that used to be invisible until the return was prepared now surfaces as records submitted late, one at a time, each carrying a date.
An error is no longer something you fix before filing
Under a periodic return, everything inside the period is provisional. You post, you correct, you post again, and only the state of the ledger at the moment of filing is asserted to anybody. The month is a buffer, and most finance functions use it as one whether or not they would describe it that way.
Continuous reporting removes the buffer. A record that goes in wrong has been asserted. Correcting it means submitting a further record that supersedes the first, and the administration's copy keeps both. None of that is punitive — the mechanism exists for correction — but it changes what a mistake is.
Each submitted record also comes back with a state of its own: accepted, accepted with errors, or rejected. The middle case is the expensive one. The record is in, the batch looks successful, and the defect stays invisible until somebody reads the responses instead of counting the records sent.
What the regime collects, and what it does not
Setting the two side by side shows that neither is a subset of the other.
| Information | Immediate Supply record | Structured invoicing mandate |
|---|---|---|
| Counterparty identity | Tax identification number and name | Full party details, including postal and electronic addresses |
| Invoice identification | Series, number, issue date, transaction date | The same, carried inside the document itself |
| Amounts | Taxable base, rate and tax amount per breakdown | The same, plus line amounts that must sum to them |
| What was sold | A free-text description of the operation | Every line: item, quantity, unit price, allowances and charges |
| Item and unit coding | Not collected | Coded units of measure and item identifiers |
| Commercial references | Not collected | Payment instructions, order and contract references |
| The document | Not submitted | The submission is the document |
| Treatment keys | National transaction and special-regime keys | Tax category codes and exemption reasons from European lists |
| Your ledger position | Recording date and deductible amount for purchases | Not part of an invoice at all |
Read the last row first. The reporting record carries information that no invoice contains — when you booked the document and how much of the tax you are claiming — because it is a statement about your ledger rather than about the transaction. A project that treats the reporting feed as a by-product of the invoicing feed therefore produces something structurally short of what is required, and finds out late.
The administration's copy, and how it differs from an audit file
The difference from audit-file style reporting is not really the data — much of it is the same fields — but who holds it and when. An audit file is an extract you produce for a period, usually on request. Here the administration holds a running set of registers built from your submissions, and alongside them a set built from everybody else's submissions about you. Your supplier's record of a sale to you exists in that data whether or not you have booked the purchase, within days of the invoice being issued.
Reconciliation as a standing process
The difference between your registers and the administration's copy is a live figure at all times, and there is no filing date at which it gets settled and forgotten. Most of what that surfaces is neither fraud nor error. It is timing: a supplier issues in one period and you book in the next, a credit note lands against a different series, a self-billing arrangement produces a record from one side and not the other. Each is defensible and none clears itself, so somebody has to look. The general problem of matching reported data against your own books is the same everywhere; the Spanish version arrives more often.
Two obligations, two laws
None of the above is the Spanish business-to-business invoicing obligation. That comes from separate legislation and concerns the form of the document itself — a structured invoice between businesses and professionals, with reporting of what happens to it. Its scope and phasing are covered in the Spanish business-to-business invoicing obligation.
Two things follow. Being inside the reporting regime tells you nothing about your position under the invoicing obligation, because the populations are defined on different criteria. And complying with one does not discharge the other: an invoice issued as a structured document still generates a register record with a deadline of its own.
What decides whether this works
The question is not which software you buy. It is whether the reporting record is generated by the same process that creates the accounting entry, or by a separate extraction running afterwards.
If it is the same process, a correction to the ledger is a correction to the record and the two cannot drift. If it is a separate extraction, they will drift, and the drift is invisible from inside your own systems because both sides of your internal check are drawn from the same place. You find it when the administration's aggregate disagrees with yours.
The regime does not ask you to invoice differently. It asks you to be right within days rather than within weeks, in a data set you have never had to defend field by field, against a copy held by somebody who also holds your counterparties' version of it. No document format solves that.
