The Union Database, and what it asks of your supply chain

The database record of a custody transfer between registered operators, the digital handover mirroring the physical one, the chain assembling link by link. Transactions are the database's native tense.

Correction procedures exist with counterparties and administrators, the audit trail preserving the original, the appeal being part of the design. The database forgives with paperwork.

Imported consignments enter the chain at the first Union operator, the external origin documented, the internal custody digital from arrival. The border is the database's front door.

Operator familiarity with the interface and the timing rules, an afternoon's training preventing a quarter's confusion, the systems simpler than the rumours. The database is a tool, not a trial.

The records feed scheme verification, the digital trail backing the paper one, auditors reading both. The database is the audit's second opinion.

Each economic operator bears its own registration and transaction costs, modest next to a single compliance cargo's value, and non-negotiable in any case. The fee is trivia, the gap is the risk.

Through the system's correction workflows with the counterparties involved, an audit trail of fixes rather than silent edits. Corrections are normal, invisibility is not.

The database and the scheme documents interlock, with UDB registration and transaction records backing the paper trail, not erasing it. Digital is the second set of books, the scheme remains the first.

Each registered operator books its leg, the chain assembling transaction by transaction across borders, which is why every counterparty's registration matters before the cargo moves. One unregistered link stalls the whole string.

Through a phased rollout: operator registration came first, then transaction reporting, with liquid biofuel chains leading. The obligations have also been arriving country by country through national RED III implementations, Spain first in written law, with Real Decreto 611/2026 in force from 1 January 2027, Germany following its April 2026 adoption. Where your chain stands today is a question for the current timeline and your certification body, not for last year's.

Increasingly no for compliance material: the database is becoming the record of who held what, and counterparties ask for your UDB position the way they used to ask for a certificate. Registering early is cheap, discovering the gap mid-deal is not.

It is the European system for recording biofuel consignments and their transfers, introduced under the Renewable Energy Directive so that a volume claimed in one member state cannot also be claimed in another. It records data about consignments that your scheme certification supports; it does not certify anything itself.

No. The scheme certifies the operator and the chain of custody; the database records the resulting consignment data so it can be matched across borders. You need both, and the database generally asks for information you should already hold if your certification is in order.

Ask your certification body what applies to your role, your member state and your product, because that answer is specific and it changes. Then do the part that helps regardless: reconcile quantities, categories and counterparty names across the declaration, bill of lading and invoice for a few recent consignments, and fix whatever does not line up. Data that survives being matched against someone else's is the whole game.

The registration and reporting detail has been phased in and differs by member state and fuel type, so confirm your own position with your certification body rather than reading it off a page. What holds in every version is that each transfer has to reconcile: quantities consistent across documents, feedstock described the same way from collection to refinery gate, the greenhouse gas figure carried with its calculation basis, and the counterparty identity matching between declaration, contract and invoice.

Economic operators in the chain, collectors, processors, traders, fuel suppliers, but the mechanics matter more than the label. You do not apply from scratch: once you are certified, your voluntary scheme submits the certificate data and the UDB registers you automatically. What is left is yours to do: the UDB sends an onboarding link to the main contact person named on the certificate, that person clicks it and completes the onboarding in the UDB (the EU Login app is required for authentication), and you then verify every detail recorded about you, roles, sites, certificate scope, because the data in the UDB is the operator's responsibility even though the scheme created the record. Certified but never seen a link? Do not assume you are exempt; assume the link went to a stale main contact and ask your scheme where it went.

The obligation exists at EU level through Article 31a of the Renewable Energy Directive, but enforcement arrives country by country. Spain is first in written law: Real Decreto 611/2026 (in force 1 January 2027) obliges the whole chain, certified origin points included, to report in the framework of the Union Database, with dual reporting to the Spanish SICCRE system until both are interconnected, so December 2026 is the readiness window for anyone selling into Spain. Germany's RED III transposition landed only in 2026 and Nabisy remains operative in the transition. For any destination, the question to put to your certification body is whether the buyer's authority already refuses volumes without a UDB trail.

Data that does not reconcile. A rounding difference between the declaration and the bill of lading, a feedstock described one way at collection and another at delivery, or a greenhouse gas figure passed on without its basis. All of these survive fine in a paper chain and fail the moment two records are matched against each other.

National registries still do the national booking, Nabisy for the German market, and the UDB is the EU-wide layer they are being connected to. Spain shows what that transition looks like: under Real Decreto 611/2026 its operators report in both the national system and the UDB until the two are fully interconnected. What has not changed is that the national authority still needs proof it can book, and that proof still starts with your certification and your documents.

That is the intent, and cross-border matching does close a gap that document-based proof left open. It is not a complete answer on its own, data entered consistently can still describe something that never happened, which is why audit and physical verification still matter. But double counting across member states gets considerably harder, and that is worth something to everyone trading this material honestly.