As organisations prepare for the mandatory Digital Battery Passport requirements from 18 February 2027, collecting the required information is only the first step. Before data is published, organisations need confidence that it is accurate, complete, consistent and supported by appropriate evidence.
Under Article 77 of Regulation (EU) 2023/1542, the economic operator placing the battery on the market is responsible for ensuring that the information in the Battery Passport is accurate, complete and up to date. The regulation also requires Battery Passport information to be interoperable, structured, machine-readable and based on open standards.
For compliance, IT, sustainability and quality teams, this raises a practical question:
"How can Battery Passport data be checked before it reaches the published Passport?"
A structured validation process can help identify missing information, inconsistencies and unsupported claims before they become compliance or operational problems.
Start with the Required Data
Validation begins with knowing what information actually needs to be provided.
The European Commission's updated guidance, published in August 2026, brings together 71 Battery Passport data points and identifies their applicability to electric vehicles (EVs), light means of transport (LMT), and industrial batteries over 2 kWh. It distinguishes between information that is mandatory, optional, conditionally applicable or not required as of February 2027.
Organisations can use this as the foundation for a validation matrix.
For each applicable data field, teams should identify:
Required field → Data source → Responsible owner → Validation rule → Supporting evidence → Approval status
This creates a clear connection between the information entering the Battery Passport and the process used to verify it.
BASE's Battery Passport Data Attribute Longlist v1.3 can also provide a useful starting point for mapping data attributes and understanding how different information categories relate to Battery Passport implementation.
Check Data for Completeness
The first validation question is simple: is anything missing?
A Battery Passport may contain information from multiple departments, systems and supply chain partners. A technical specification could come from an engineering system, production information from a manufacturing system, and sustainability information from a separate reporting process.
Automated completeness checks can identify missing mandatory fields before publication.
For example, a validation workflow could prevent a Passport from progressing to publication if a required identifier, manufacturer detail or applicable performance indicator has not been provided.
This is particularly useful when organisations manage large numbers of battery models or individual battery records. Manual checking becomes increasingly difficult as the volume of information grows.
Validate Format, Units and Values
A field can be complete and still be wrong.
Data validation should therefore check whether information follows the expected format, measurement unit and value range.
Consider a battery capacity field. A system should know whether the value is expected in watt-hours or kilowatt-hours and flag values that fall outside an expected range.
Similar rules can be applied to dates, identifiers, numerical values, classifications and other structured information.
Where applicable, validation should also check that related fields make logical sense. A battery's reported characteristics should not contradict information elsewhere in the Passport.
These checks can catch simple errors early, before they reach downstream systems or external stakeholders.
Check Data Against its Source
Automated validation rules are useful, but they cannot answer every question about data quality.
Organisations should also be able to establish where each important value came from.
For example, if a Battery Passport contains a performance indicator, the validation process should identify the relevant measurement, test result, calculation methodology or source record supporting it.
This creates a chain such as:
Data Attribute → Source → Calculation or Measurement → Evidence → Validation → Publication
Such traceability becomes particularly important for sustainability, performance and lifecycle information where values may be calculated or derived from several underlying datasets.
BASE's article on Battery Passport Audit Trails and Evidence Management explores how organisations can strengthen provenance and demonstrate data integrity throughout the Battery Passport lifecycle.
Cross-Check Data from Different Systems
Battery Passport information rarely exists in one place.
ERP, MES, PLM, laboratory, BMS and sustainability systems may all contribute information. Validation should therefore include checks between connected systems where the same information appears in multiple locations.
For example, the battery identifier recorded in a production system should correspond with the identifier associated with the Battery Passport. Product characteristics should also remain consistent between relevant engineering and Passport records.
APIs and automated integrations can reduce manual transcription, while validation rules can flag discrepancies between systems.
This is one reason why Battery Passport implementation should be considered as part of an organisation's wider data architecture rather than as a standalone database project.
Validate Changes Before They are Published
Battery Passport data can evolve throughout the battery lifecycle.
Information may need to be updated following changes in ownership, use, repair, repurposing or other lifecycle events. The regulation requires the information to remain accurate, complete and up to date.
Organisations should therefore apply validation whenever relevant information changes, rather than validating the Passport only once during its initial creation.
A useful workflow is:
Update → Validate → Review → Approve → Publish
Where a change fails validation, the system should identify the affected field and return it to the appropriate data owner for correction.
Maintaining a history of important changes also makes it easier to investigate discrepancies later.
Apply Human Review Where it Matters
Not every validation process should be fully automated.
Automated checks are highly effective for completeness, formatting, consistency and predefined thresholds. Human review remains valuable for information that requires interpretation or professional judgement.
A compliance or sustainability specialist may need to review a particular environmental claim. An engineering expert may need to assess an unusual performance value. A quality team may need to investigate conflicting production records.
The objective is to combine automated validation with clearly defined human approval rather than relying exclusively on either approach.
Control Who Can Approve Publication
Validation and publication should also be connected to appropriate permissions.
A person who enters data does not necessarily need authority to approve it for publication. Organisations can establish role-based workflows in which data owners maintain information, quality or compliance teams review relevant fields, and authorised users approve the final record.
This creates accountability around the publication process and reduces the risk of unauthorised changes.
The Batteries Regulation also requires appropriate controls over access to introduce, modify and update Battery Passport information, alongside requirements for authentication, reliability and integrity.
Keep Evidence With the Data
A validation result is stronger when it can be supported by evidence.
Organisations should consider linking relevant Battery Passport attributes to their underlying source documents, measurements, calculations or system records. The exact evidence will depend on the data field and its source.
For compliance and quality teams, this creates a much stronger position when information needs to be reviewed internally or requested by an authority.
It also makes future corrections easier. If a source value changes, organisations can identify which Battery Passport records depend on it and determine whether they need to be revalidated.
How BASE Can Help with Validating Battery Passport Data
The BASE project is developing, validating and implementing a working Digital Battery Passport service designed to support transparent, secure and cost-efficient data management across the battery value chain. Its approach includes data authenticity verification, traceability, interoperability and privacy by design.
Data validation is closely connected to these objectives. A trustworthy Battery Passport needs mechanisms that can help establish whether information is complete, consistent, traceable and reliable before it is shared.
BASE's demonstration activities are also focused on validating the transparency, accuracy and reliability of battery indicator estimation methods while synchronising Digital Battery Passport data with realistic product development and lifecycle processes.
For organisations preparing their own implementation, BASE's resources on Battery Passport data attributes, DIN DKE SPEC 99100 and JTC 24 standards can help connect regulatory requirements with practical data structures and interoperability considerations.
Building a Reliable Pre-Publication Process
Battery Passport validation should be treated as a controlled process rather than a final manual check.
A practical approach is to validate information at several stages: when data enters the system, when it is changed, when it is combined with information from other sources and immediately before publication.
The essential questions are straightforward:
"Is the data complete? Is it correctly formatted? Is it consistent with other records? Can its source be verified? Has the appropriate person reviewed it?"
By building these checks into the Battery Passport workflow, organisations can improve data quality while creating a stronger foundation for regulatory compliance, lifecycle traceability and trusted information sharing.
The BASE project has received funding from the Horizon Europe Framework Programme (HORIZON) Research and Innovation Actions under grant agreement No. 101157200.
References & Resources
European Union - Regulation (EU) 2023/1542: https://eur-lex.europa.eu/eli/reg/2023/1542/2025-07-31/eng
European Commission - Guidance To Support Preparations For The Digital Batteries Passport: https://single-market-economy.ec.europa.eu/news/guidance-support-preparations-digital-batteries-passport-2026-08-21_en
European Commission - Digital Product Passport For Batteries: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport/batteries_en
BASE - Article 77 Explained: Building A Compliant Digital Battery Passport Data Model: https://base-batterypassport.com/blog/regulations-4/article-77-explained-building-a-compliant-digital-battery-passport-data-model-111
BASE - How To Implement A Digital Battery Passport: A Step-By-Step Guide: https://base-batterypassport.com/blog/regulations-4/how-to-implement-a-digital-battery-passport-132