Electronic pesticide records have three separate questions: what information describes the application, what format holds it, and when an initially non-electronic entry is transferred. Regulation 2023/564 addresses these in Articles 1, 2 and 3 and applies from 1 January 2026. The 2025 amendment adds a national option concerning electronic conversion for uses before 1 January 2027. The option is a power for Member States, not an automatic country-wide postponement written into the amendment. [1][2]
Read the content rule separately from the format rule
Article 1 requires professional users to provide the Annex information in the records referred to in Article 67 of Regulation 1107/2009. Article 2 requires those records to be kept electronically in a machine-readable format, referring to the definition in Directive 2019/1024. The content and format provisions are distinct obligations in the text. [1]
Use the application-fields guide to decide what your record needs to describe before choosing an office file or mobile workflow. The Annex separates surface treatments, closed-space treatments and treatment of seeds or reproductive material. A field-oriented table can therefore need different measurement headings when the operation concerns a facility or a batch. [1]
For an internal implementation review, make two lists. The first contains the information that must survive a handover: identifiers, date, rate, location, extent and crop or situation. The second describes how your chosen workflow preserves and retrieves those values. Assess both lists together. An attractive screen does not demonstrate that every required value remains present in the file a colleague receives.
Immediate recording and conversion are different events
Article 3 says each use must be recorded without undue delay. Where a record is not initially created in the prescribed electronic format, the baseline transfer period is no later than 30 days from the date of use. Member States may provide shorter periods for uses on their territory. The initial recording instruction is not replaced by the conversion period. [1]
Organise your own workflow around the distinction. Give the operator a way to describe the completed application promptly, and assign an identifiable person to any subsequent transcription. Keep the application date separate from the date on which the office receives a report or creates a workbook entry. Retain the underlying report so a discrepancy can be investigated without reconstructing the treatment from recollection.
| Stage | What the EU provision addresses | Practical control for your own file |
|---|---|---|
| Completed use | Record without undue delay | Associate the initial note with the actual application |
| Transfer from another initial format | Baseline 30-day conversion period | Identify the entry awaiting transcription and its responsible person |
| National timing choices | Shorter periods, limited longer periods, and the 2027 option | Keep a specific applicable national instruction with the policy it affects |
| Authority request | Prompt provision and an electronic-response rule | Retain the request, scope, receipt date and delivered copy |
| Contract service | Client access or copy without undue delay or restrictions | Agree the receiving contact and understandable location references |
The table separates the provisions rather than assigning a new Maltese deadline. The national choices and the authority-request mechanism have their own conditions in the cited text. [1][2]
What the 2027 amendment actually changes
Regulation 2025/2203 adds a paragraph to Article 3 of Regulation 2023/564. It permits Member States to allow that records for uses on their territory before 1 January 2027 are not transferred into the prescribed electronic format. The amendment identifies the use date and the transfer requirement; it does not replace Article 1 or delete the Annex. [2]
Keep that distinction explicit in a business decision. A general headline mentioning 2027 does not identify which rule was changed, which territorial decision applies, or which applications fall within its scope. For a policy file, record the issuing body, instrument title, relevant paragraph and dates associated with the instruction actually being used. Preserve the document with the workflow it informs.
This guide explains the verified EU provisions and their separate national options. A statement about a particular country’s exercise of an option needs that country’s instrument. The Malta hub connects the legal framework with the local authority and ARPA evidence routes. Use that framework when assigning the person responsible for tracking any applicable instruction.
The limited longer-period option has an outer date
For uses before 1 January 2030, Article 3 permits Member States to allow longer conversion periods than the baseline. All relevant records must nevertheless be available in the prescribed electronic format before 31 January of the year following the year of use. This is another national option and has different wording from the paragraph added in 2025. [1][2]
In your internal procedure, separate a source document that describes the ordinary baseline from a document authorising an exception. Label the affected operation period precisely. Avoid turning the final availability date into a general permission to delay the first record. The requirement to record each use without undue delay appears independently in Article 3. [1]
A working register of pending transcription can contain an event reference, application date, original-document location, transcription owner and completion status. These are editorial management suggestions, not additional statutory columns. They let an administrator locate an unconverted note and its supporting product or parcel information before preparing the structured copy.
Responding to an authority request
Article 4 requires the professional user to provide requested record information without undue delay. It also addresses an express request for the prescribed electronic format before the relevant conversion period has expired: the information is supplied before that period ends or within ten working days, whichever comes first. This request rule should be read together with the conversion provisions it names. [1]
Preserve the incoming request with the set of records selected in response. Identify the holdings, dates and applications it covers. For the office copy, make a manifest matching each attachment to its description and relevant period. Open the exported table and inspect the identifiers, measurement units and any category-specific fields. Keep the original records in their ordinary archive while retaining the response set separately.
Where a requested value is unclear, locate the reporter and the original event document. State the exact point that needs clarification. An unexplained replacement attachment is difficult for the next person to interpret, especially when several exports cover overlapping dates. Retain the correspondence that explains a revised row and identify which copy was delivered.
Contract sprayers must make the record available to the client
Article 4 expressly covers professional users acting under contractual arrangements for another natural or legal person. They must give the contracting person access to, or a copy of, the records without undue delay or restrictions. That provision concerns the record of the service performed, beyond the commercial booking or invoice. [1]
For an orderly handover, agree a receiving contact before the job. Explain the client’s parcel references and how the operator will identify a partly treated area. After completion, compare the report with the customer’s application register. Resolve mismatched names, units or dates through the person who carried out the work, and retain the resulting clarification beside the supplied report.
Keep contractor access arrangements understandable during staff changes. Identify who can retrieve the relevant season’s report and who owns unresolved enquiries. If a contractor changes software, obtain a usable copy of the historical records needed for your archive. This is a continuity recommendation for the business; the legal basis for the client’s access or copy is the Article 4 provision above. [1]
Retention is independent of software selection
Article 67(1) of Regulation 1107/2009 requires professional users to keep records of the plant protection products they use for at least three years. The same paragraph distinguishes producers, suppliers, distributors, importers and exporters, whose specified product records have a five-year minimum. Keep those roles separate when deciding which retention statement describes your activity. [3]
The professional-user record includes product name, time, dose, area and crop under Article 67; Regulation 2023/564 supplies the detailed content and format rules for those records. A change of phone or an annual workbook rollover does not describe a different legal category of use. Preserve the historical application evidence throughout the applicable record period. [3][1]
As an archive exercise, select an older application and retrieve its original entry, relevant product identity and location information. Check whether a different authorised colleague can locate and understand the same documents. Record a broken reference or unreadable attachment as a concrete retrieval problem, with an owner and a resolution, rather than treating the existence of a folder as proof that its contents are usable.
Evaluate a spreadsheet by its actual output
For a spreadsheet trial, begin with fictional data that is clearly labelled and contains no proposed pesticide recommendation. Include a surface entry, a closed-space entry and a seed-treatment entry so the different denominators and extents are visible. Those categories come from the Annex. Use the trial to assess your headings and handover process. [1]
Export the file in the format you intend to retain and inspect it separately from the editing screen. Look for truncated product names, lost leading zeroes in identifiers, rounded measurements, hidden columns and ambiguous date displays. Keep formulas distinguishable from the entered values on which they depend. These are practical data-review checks, not a certification of a particular application or file extension.
Write a small data dictionary explaining the columns and units. If a recipient imports the file into another system, compare the resulting rows with the original export. Check the first and last events, unusual characters and a partly treated location. Retain the test file and explain any deliberate transformation. A successful trial should demonstrate that the intended information remains interpretable outside the original editing context.
Keep evidence of product conditions connected
Article 55 requires proper use, including compliance with the conditions established in the authorisation and specified on the labelling. Electronic storage of an event does not supply those product-specific conditions. Keep the actual label or authorisation material identifiable in your archive and connect it to the recorded product. [3]
When a later harvest, access or buffer enquiry arises, start from that product document and the actual application chronology. Do not generate a universal interval from the name of a crop or from the presence of an app reminder. The Malta authority and label overview explains how to organise those documents without substituting a generic product description.
Keep scheme evidence distinguishable too. ARPA’s BiedjaCam booklet describes crop-plan management, registered parcels, aid applications, payments, notifications and geotagged photographs. These are functions of the published ARPA workflow. The BiedjaCam guide explains the crop-plan and eco-scheme context rather than treating every official app screen as an application-record export. [4]
Make the workflow resilient to ordinary changes
Prepare an internal responsibility note covering initial recording, transcription, review, retrieval and contractor enquiries. Name the role responsible for each step and the substitute who handles an absence. Include the directory location and naming convention used for the season. Explain the abbreviations used for parcels and facilities so a new administrator can identify a historical event.
During a software change, preserve a representative export before migration and compare it with the imported result. Count the selected events, then examine their substantive fields. A matching row count can coexist with a lost unit or changed identifier. Record which source dataset was migrated, which adjustments were intentional and which discrepancies remain under investigation.
For an archive handover, prepare a concise inventory of datasets, attachments and supporting dictionaries. Identify the business custodian and the authorised retrieval route. Keep access credentials within the business’s normal arrangements instead of embedding them in an application record. Explain how an older export is opened and how any compressed attachment is extracted before it is needed for a request.
Check character handling in a labelled transfer exercise
For an internal transfer exercise, create a clearly fictional dataset containing a Maltese parcel nickname with an accented character, an authorisation-style identifier stored as text, a fractional extent and an explanatory remark. Label the file as a demonstration and avoid real applicant identities or pesticide recommendations. Copy it through the intended export/import sequence, then compare the characters, identifier, decimal separator and remark in the receiving table.
Inspect whether punctuation remains attached to the correct value. Look for a misplaced delimiter, an unexpected line break inside a description or a blank that has been replaced with a zero. Document the interpretation of an empty field in the companion dictionary. These checks help you assess the intelligibility of your chosen exchange process; they do not create an officially prescribed serialization scheme.
Keep the demonstration apart from the operational dataset so fictional events cannot enter the season’s application history. Once the transfer method is understood, use a selected authorised copy of real records for the substantive comparison. Preserve the source filename, export time and any transformation note in the migration inventory. Resolve a mismatch through the originating document before accepting the transferred copy as your working archive.
Review the process against the actual event chain: use, initial record, structured copy, supporting documents, request and response. Each link should have an understandable reference. The ARPA inspection guide then shows how the application evidence relates to purchases, storage and the separate conditionality assessment. [5]