Invoice Status vs Accounting Entry: Why Payment Does Not Determine Accrual
Mandatory e-invoicing introduces invoice status fields — acceptance, rejection, payment — as a mechanism for traceability and late payment control. They are a valuable tool. But there is a technical and accounting risk that Position Paper No. 3/2026 by Economistas Contables EC-CGE identifies with precision: if those status fields are not managed correctly in the software, they can indirectly push businesses towards recording income and expenses at the moment of actual cash receipt or payment, rather than at the point of accrual. For advisors, accountants and economists, understanding this distinction is essential.
The accrual principle does not change with e-invoicing
The accrual principle is the governing criterion for accounting recognition under Spain's General Accounting Plan (Plan General Contable, PGC). Income and expenses are recognised in the period in which they arise, regardless of when cash is received or paid. This principle has not been modified by RD 238/2026, nor could it be: it belongs to the accounting framework, not to the invoicing framework.
However, the introduction of invoice status fields into the operational flow of businesses creates a new tension. When invoicing software automatically records the status "paid" and that event triggers an accounting entry, the result can be cash-basis recognition rather than accrual — especially in small and medium-sized businesses without robust internal accounting controls.
EC-CGE warns of this explicitly in its Position Paper No. 3/2026: there is a risk that certain technological automatisms may indirectly and involuntarily induce criteria closer to cash-basis accounting, especially in small and medium-sized enterprises.
What are invoice status fields and what are they for?
RD 238/2026 establishes that issuers and recipients of electronic invoices must report the following invoice status fields to the AEAT within a maximum of 4 calendar days of each event occurring:
- Acceptance or rejection of the invoice by the recipient.
- Full payment of the invoice.
The purpose of these status fields is twofold: to combat commercial late payments (the AEAT can cross-reference declared payment dates with actual ones) and to improve traceability of the economic cycle of each transaction.
What invoice status fields do not do — and this is the core of the issue — is determine when an operation must be recognised in accounting terms. They are informational data about the administrative and cash-flow cycle of the invoice, not about the underlying economic event that gives rise to it.
The legal definition of "effective payment date" and its accounting implications
Article 10 of RD 238/2026 introduces a precise definition of "effective payment date" that has direct accounting consequences and deserves specific attention.
The regulation defines the effective payment date as the moment when the supplier actually receives payment for the goods or services. It expressly excludes from that definition the mere making available of a financial mechanism to advance receipt — such as confirming or factoring arrangements.
This has two important practical implications:
First: there can be a difference of several days between the date on which the customer executes the bank transfer and the date on which the funds are actually credited to the supplier's account. The effective payment date for the purposes of RD 238/2026 is the latter, not the former. Software that records the status "paid" at the moment the transfer is sent is being imprecise relative to the regulation's own legal definition.
Second: the effective payment date — even in its most precise definition — remains irrelevant for the accounting recognition of income or expense. A sale is recognised when the goods are delivered or the service is rendered; a purchase, when it is received. The subsequent receipt or payment is a cash flow event that affects the debtor or creditor account, not the recognition of income or expense.
EC-CGE underlines precisely this: the invoice status fields have an informational and monitoring character and in no case condition the moment of accounting recognition.
The real risk for SMEs: when automation replaces accounting judgement
The risk is not theoretical. In practice, many management systems and ERP solutions for SMEs are designed to simplify operations: when an invoice arrives and is marked as "paid", the system may automatically generate the accounting entries for the transaction. If that process is not correctly configured, the result is accounting that reflects when cash is paid, not when the obligation is incurred.
The consequences can be significant:
- Mismatches in the profit and loss account: income accrued in December but received in January appears in the wrong financial year.
- Errors in taxable profit calculation: the corporate tax base can be distorted.
- Unreliable financial information: monthly or quarterly closes do not reflect the economic reality of the period.
- Risk in audits and reviews: the absence of correct accrual adjustments is one of the most frequently identified errors in SME accounting reviews.
EC-CGE frames this in terms of internal control: this risk must be avoided through correct system configuration and adequate accounting training.
What responsible invoicing software must do
A technically sound invoicing software designed with the accountant and advisor in mind cannot limit itself to recording and transmitting invoice status fields. It must design its interface and its automated processes in a way that does not induce — or allow — confusion between the administrative cycle of the invoice and the accounting cycle.
Best practices in software design for this context include:
1. Informational text in the UI alongside invoice status fields. When a user marks an invoice as "accepted" or "paid", the system should display a clear notice: this status is reported to the AEAT for the purposes of the RD 238/2026 obligation, but does not automatically generate or modify the accounting entry. Accounting recognition must follow the accrual principle under the PGC.
2. Explicit separation between the invoice status module and the accounting module. Status fields are fiscal and administrative information flows. The accounting entry is an independent flow governed by PGC criteria. The software must not merge these flows without the user being fully aware.
3. Alerts about the "effective payment date". When a payment is recorded, the system should remind the user that the effective payment date under RD 238/2026 is the date funds are credited to the supplier's account, not the date the transfer order is issued.
4. Explicit configuration of accrual rules. The software must allow the advisor or accountant to define accrual and periodification rules without the invoice status automation overriding or interfering with them.
InvoSeal and the accounting perspective of compliance
Most e-invoicing solutions on the market are designed from a purely technological perspective: transmitting the right data in the right format to the AEAT. That is necessary, but insufficient when the end user is an advisor, a certified accountant or a company with internal accounting functions.
InvoSeal is built with awareness of this risk. The invoice status fields it generates and reports under RD 238/2026 are clearly differentiated from the accounting cycle. The interface design includes contextual notices reminding the user of the distinction between the effective payment date (legal definition under Art. 10 RD 238/2026) and the moment of accounting recognition under the PGC.
This approach is aligned with the recommendations of EC-CGE Position Paper No. 3/2026 and with the perspective upheld by the Consejo General de Economistas: e-invoicing must be integrated into the company's financial information system, not substitute accounting judgement.
See our technical documentation on VeriFactu and the accounting cycle to understand how InvoSeal implements these principles in practice.
Frequently asked questions: invoice status and accounting
Does the "paid" status of an electronic invoice automatically generate the accounting entry?
It should not, although some poorly configured systems do. The "paid" status is informational data reported to the AEAT for late payment monitoring purposes. The accounting entry for cash receipt must be recorded in accordance with the PGC, independently of the invoice status in the electronic system.
When is income recognised in accounting terms if the electronic invoice is accepted but not yet paid?
Income is recognised when the goods are delivered or the service is rendered, in accordance with the accrual principle. The recipient's acceptance of the invoice does not affect that moment. The invoice may be accepted and the income already recognised beforehand, or recognised after acceptance: the invoice status is not the determining factor.
What is the difference between the "effective payment date" under RD 238/2026 and the payment date in accounting?
The effective payment date under RD 238/2026 (Art. 10) is the date on which the supplier actually receives the funds. In accounting, the derecognition of the liability (removal of the creditor) may coincide with that moment, but the expense recognition already occurred at the point of accrual, regardless of when payment is made.
Does confirming or factoring change the effective payment date?
Not for the purposes of RD 238/2026. The regulation expressly excludes from the definition of effective payment date the mere making available of a financial mechanism to advance receipt. The effective payment date remains the moment the supplier actually receives the funds.
What should advisors review before their clients implement B2B e-invoicing?
EC-CGE recommends reviewing the entire accounting circuit of the invoice before implementation: from issuance or receipt through to the accounting close. In particular, verifying that the software's automated processes do not confuse invoice status with the point of accrual, and that accrual periodification is correctly configured.
Conclusion: technology serving accounting judgement, not replacing it
Mandatory e-invoicing is an opportunity to improve the quality of financial information. But that improvement only materialises if the software implementing it respects fundamental accounting principles, rather than replacing them with administrative automatisms.
Invoice status fields are valuable data. The effective payment date is a precise legal definition. And accrual is the accounting principle that continues to govern the recognition of income and expenses. All three exist on separate planes and must be kept separate.
For advisors and certified accountants accompanying their clients through this transition, correct software configuration and administrative team training are tasks as important as the choice of invoicing platform itself.