The New Duty to Report Invoice Status (Accepted, Rejected, Paid) Within Four Days — And Why They Aren't Quite Business Days

Everyone reporting on Spain's mandatory B2B e-invoicing repeats the same line: recipients will have to report invoice status within four days. Almost nobody reads the actual wording, and the actual wording matters. Royal Decree 238/2026, published in the BOE on 31 March 2026, says the information must be sent within four calendar days, excluding Saturdays, Sundays and national holidays. That is not the same as four business days. If your regional or local holiday falls inside the window — the Comunidad de Madrid on 2 May, a local patron saint's day, a regional festivity in the Basque Country or Andalusia — the clock keeps running while your office is closed.

The second thing nobody puts in writing: this is not one message per invoice. It is at least two mandatory status events per invoice — acceptance or rejection, and then full effective payment — separated by weeks or months. A firm that receives 150 supplier invoices a month is looking at roughly 300 mandatory status events a month, about 15 every working day, each with its own independent four-day deadline. That is not a monthly batch job. It is a permanent open register.

Try it right now — free, no signup →

This article is about the counting, the volume and the process. Not about the political calendar.

What exactly you have to report

Under RD 238/2026, the recipient of an invoice must report two statuses, and may voluntarily report three more.

Mandatory:

Commercial acceptance or rejection of the invoice, with its date.
Full effective payment of the invoice, with its date.

Voluntary:

Partial commercial acceptance or rejection.
Partial payment, stating the amount paid and the date.
Assignment of the invoice to a third party for collection or payment (factoring, confirming).

Two details from the text that change how you work:

Acceptance is presumed. If you neither reject the invoice nor receive a corrective one, the invoice is taken as accepted. So the status you truly have to be fast about is rejection — a disputed invoice you let sit for five days is an accepted invoice.

Payment means funds received by the supplier. The effective payment date is the date the supplier actually receives the money, not the date you launched the transfer or authorised the remittance. If you release a SEPA batch on a Thursday and it lands on Monday, your four-day clock starts on Monday, not Thursday — and you need to know that Monday happened.

Statuses go both to the issuer and to the public solution, whatever channel the invoice originally travelled through.

How the four days are actually counted

Take a concrete case. A supplier's invoice is paid and the funds reach their account on Thursday 30 April 2026. You count from the day the status occurs:

Friday 1 May: national holiday, does not count.
Saturday and Sunday: do not count.
Monday 4 May: day 1.
Tuesday 5, Wednesday 6, Thursday 7 May: days 2, 3 and 4.

Deadline: Thursday 7 May. Now change one thing — you are in Madrid, where 2 May is a regional holiday. It falls on a Saturday that year, so nothing changes. But move the same case to a year where 2 May is a Tuesday: the office is shut, and the regulation still counts it. That is the trap. Build your process around national holidays only, and treat your own regional calendar as lost time, not as extra time.

The practical consequence: a status event that happens on a Friday afternoon gives you until roughly the middle of the following week. There is no version of this where a person catches up on Fridays with a folder of paperwork.

Do the math for your own business

Before deciding anything, put your own numbers in:

Supplier invoices received per month. Count them for real, including the ones that arrive by email as PDFs, by WhatsApp from a contractor, or on paper.
Multiply by two. That is your floor of mandatory status events: one acceptance/rejection, one payment.
Divide by 21 (working days in an average month) to get your daily rhythm.
Add the lag. With Spain's average payment period at 80.5 days and only 30.4% of amounts paid on time or early, according to CEPYME's late-payment observatory for Q4 2025, the payment status of a January invoice is reported around April. The two events for the same invoice are almost never in the same quarter.

A property manager with 300 invoices a month: 600 events, roughly 29 per working day, with acceptance and payment permanently out of sync. A small gestoría handling accounts payable for 20 clients: multiply your clients' volumes, and remember each client has its own deadlines.

Step 4 is the one people skip, and it is the one that breaks manual processes. You cannot report the payment of an invoice you did not record properly three months ago.

When this hits you

The Royal Decree entered into force in April 2026, but it is not enforceable yet. The deadlines run from the ministerial order that sets the technical detail — a draft went to public consultation between 17 April and 8 May 2026, proposing entry into force on 1 October 2026. From that date:

12 months for businesses with turnover above €8 million.
24 months for everyone else.

If the draft date holds, that lands around October 2027 and October 2028. There is one more concession: individual entrepreneurs and income-attribution entities with turnover of €8 million or less get an extra 12 months for the status reporting obligation specifically — it is voluntary for them until then. And during the first year of each wave, structured invoices must be accompanied by a readable PDF unless the recipient expressly agrees otherwise.

Ley 18/2022 sets fines of up to €10,000 for infringements in this area, so the cost of getting the process wrong is not purely operational.

The real bottleneck isn't the reporting — it's the capture

Sending a status message is the easy part; your invoicing platform will do it. The hard part is knowing, within four days, that something happened. Two facts have to exist inside your systems on time:

That invoice X was reviewed and either accepted or objected to.
That invoice X was matched to a specific bank movement on a specific date.

Most small firms today fail both. Invoices arrive as PDFs in a shared mailbox or as photos from a site foreman; someone types them into the accounting system at the end of the month; bank reconciliation happens later still. That workflow produces the right numbers for the VAT return and the wrong timing for status reporting.

A process that survives the four-day rule looks like this:

Capture on arrival, not at month end. Whatever the channel — email, WhatsApp, paper — the invoice becomes structured data the same day: supplier tax ID, invoice number, date, base, VAT, total, due date. This is exactly what our guide on preparing supplier invoices before handing them to your accountant covers, and the discipline it describes stops being good hygiene and starts being a legal deadline.
Deduplicate immediately. A duplicate that reaches the ledger now produces a duplicated status report too. The techniques in catching duplicate invoices before you book them apply straight to this.
Route approval with a hard date. Whoever authorises the expense has a working window measured in days, not weeks. Set your internal SLA at two days so the legal four never binds.
Reconcile payments weekly at minimum. Value dates at the supplier's bank, not your issue date. This is the step that most often causes late payment-status reports.
Push the data out. Your extracted invoice data has to reach the system that emits the statuses — accounting software, ERP or invoicing platform. If it does not travel automatically, someone will retype it, and retyping is where the four days evaporate. Sending invoice data to Excel or your ERP via API is the cheap version of this.

Four mistakes with a real consequence

Treating status reporting as an accounting task. It is an accounts payable task with a legal clock. Accounting closes monthly; this closes every four days.

Assuming your regional holidays extend the deadline. They do not, as written. A firm in a region with several local holidays can silently lose two of its four days.

Using the transfer order date as the payment date. The regulation points to the date the supplier receives the funds. Report the order date and your payment status carries a date the supplier's own records contradict.

Sitting on a disputed invoice. Silence equals acceptance. If a contractor's invoice has the wrong quantities, the rejection has to go out inside the window; after that you are arguing about an invoice you have already accepted, and you need a corrective one.

How this connects to Verifactu

They are separate systems with separate timelines. Verifactu is about how invoicing software records and reports what you issue; RD 238/2026 is about the structured invoice travelling between businesses and the statuses of what you receive. Firms often confuse the two and assume that complying with one covers the other. It does not — our breakdown of what Verifactu actually means for the way you handle invoices explains the difference.

What to do in the next twelve months

You do not need to buy anything today. You need to close the gap between an invoice arriving and its data existing:

Measure how many days pass, on average, between an invoice reaching you and it being recorded. If it is more than four, you already know what has to change.
Pick one arrival channel and make it structured end to end.
Ask your accounting or ERP provider a single specific question: will you emit and receive invoice statuses, and on what date will that be available?

The firms that will handle October 2027 calmly are not the ones with the best software. They are the ones where an invoice becomes data the day it arrives.

If you want to see how far a document is from being usable data, take one of your supplier invoices and try it free — no signup.