In brief: Electronic reporting is complete after confirmed acceptance, not after submission. Two receipts, version history and a continuity process turn a technical action into a controlled evidence trail.
What the two receipts prove
According to STS guidance dated 10 March 2026, the first receipt is sent within two hours after the document is received, or during the first two hours of the next operating day when submission occurs after the operating day ends. If the first receipt does not arrive within the prescribed time, the document is treated as not received by the authority.
The second receipt confirms acceptance or rejection and states the reason. When the second receipt confirms acceptance, the acceptance date and time are those recorded in the first receipt. Both receipts therefore belong in the control register; a submission screenshot is insufficient.
Building an evidence trail
For each filing, retain the form, reporting period, file version, signer, submission date and time, both receipts, final status and action owner. Store the files together under a stable name so the accepted package can be reconstructed months later.
When several versions of the same document are submitted after corrections, the official guidance treats the last correctly prepared document sent before the deadline and accepted by the authority as the original. The register must therefore distinguish drafts, rejected versions and the final accepted filing.
Handling a technical failure
On 27 October 2026, the STS announced that maintenance had ended and services were operating normally, while specifically referring to paragraph 42¹.10 of the Tax Code. The official STS notice is useful evidence about system status, but it does not replace checking the particular filing and its receipts.
The Tax Code addresses failures officially recognised by the administrator, methodologist, an STS portal notice or a court decision. The text of Article 42¹ should not be treated as automatic relief for every local error. Retain attempt times, software messages, receipts and official notices, then assess the specific facts professionally.
Where automation and AI help
Automation can compare the filing calendar with statuses, flag a missing first or second receipt, highlight rejected documents and prevent a task from being marked complete without acceptance evidence. It should not create uncontrolled duplicate submissions through automatic retries.
AI can explain an error message, group recurring rejection causes or draft an internal checklist, but a person must validate the form, period, details, signature and final status. FinanceOne can organise the reporting calendar, evidence register and exception controls.
A stable reporting-cycle plan
Plan backwards from the final deadline and set internal dates earlier than statutory ones. Every reminder should point to a document, owner and escalation rule.
Five working days before internal close, produce the exception list. Rerun controls after corrections and freeze the approved data version. AI may draft variance explanations, while the accountant verifies figures and conclusions.
What to measure
- On-time document delivery
- Corrections after review
- Period-close duration
- Overdue tasks
Practical checklist
- ✓ Assign an owner to every form and period
- ✓ Retain the submitted file and signer details
- ✓ Monitor arrival of the first receipt
- ✓ Review the second receipt and any rejection reason
- ✓ Identify the final accepted version among repeat submissions
- ✓ Record attempt time, error text and official outage notices
- ✓ Do not assume every local error is an officially recognised STS failure
- ✓ Close the task only after retaining acceptance evidence
FinanceOne perspective
Electronic reporting is complete after confirmed acceptance, not after submission. Two receipts, version history and a continuity process turn a technical action into a controlled evidence trail.
To apply this approach in your business, begin with a review of the current process. Our reporting services service can help establish a reliable foundation for further automation.
Reporting servicesThis article is informational and does not replace individual accounting, tax or legal advice. Rules and business circumstances may change.
