PoS, PoC and SD: the three documents that run renewable fuel compliance
Anyone working in renewable fuel compliance runs into the Proof of Sustainability and affiliated documents within the first week. PoS, PoC and SD. They all travel with sustainable fuel, but they describe different things. And the difference matters.
This article explains each one, what it is for, and how they fit together in a compliance workflow.
Proof of Sustainability (PoS)
A Proof of Sustainability is a document issued under a recognised sustainability scheme. Think ISCC EU, REDcert, 2BSVS or similar. The PoS verifies the sustainability characteristics of a batch of renewable fuel.
A typical PoS contains:
- The scheme under which it was issued
- The feedstock type
- The volume covered
- The GHG saving compared to the fossil reference
- The origin of the raw material
- The certification body
- A batch or transaction reference
- A validity window
The PoS proves what the fuel is, from a sustainability standpoint. Without it, operators cannot claim the fuel as renewable for compliance purposes.
A quick example. A trader buys ISCC EU certified biofuel. The supplier issues a PoS with the delivery. The trader later sells the fuel onward. They then issue an outgoing PoS to the next customer, carrying the relevant attributes through. Sometimes with conversion, depending on scheme.
Proof of Compliance (PoC)
A Proof of Compliance is a different document. Where the PoS proves what the fuel is, the PoC proves how it was used for compliance.
The fuel supplier issues the PoC to the customer with the regulatory obligation. That customer is typically:
- A shipping company under FuelEU Maritime or EU ETS Maritime
- An aviation company under ReFuelEU Aviation
The PoC records that a specific volume of certified fuel was allocated to a specific obligation. The customer then uses that PoC to file their own claim with the relevant authority.
A PoC also links back to the underlying PoS. The PoC essentially says: “This fuel, with these sustainability characteristics, was supplied to you to meet obligation X.”
PoC is increasingly important in maritime. FuelEU Maritime obligations have moved from theoretical to operational. A shipping company cannot count a bio-bunker delivery toward compliance without a PoC linking the delivery back to the source PoS.
Self Declaration (SD) and Sustainability Declaration (SD)
The abbreviation SD is used for two related but distinct documents.
A Self Declaration is a statement issued by an actor in the supply chain. Usually a feedstock supplier. It declares that the material meets certain criteria. Self Declarations are common upstream, where they are often used by small, not necessarily certified, outfits that supply raw materials to a collector. It is only a declaration that confirms what a certain actor will send to a collector who does fall under a certification scheme.
A Sustainability Declaration is a more formal document. Depending on the scheme, it can be synonymous with PoS. Some schemes refer to the documentation travelling between actors as Sustainability Declarations. The full PoS then gets issued at specific points in the chain, usually at the point of final fuel placement.
So the same acronym covers two different things. In practice, the scheme rule set decides which document is needed at each step. It also decides when a Self Declaration is enough and when a full Sustainability Declaration or PoS is required.
How they fit together
A simplified UCO-based biodiesel chain shows how each document moves through the flow:
- A large restaurant providing UCO issues a Self Declaration to the processor. It declares the feedstock category, origin and any relevant characteristics.
- The processor (ISCC EU certified) validates the SD and processes the feedstock into biodiesel.
- The processor then issues a PoS to the trader who buys the biodiesel.
- The trader (also ISCC EU certified) sells the biodiesel to a fuel supplier. An outgoing PoS goes to that supplier, with the relevant attributes.
- The fuel supplier has a regulatory obligation, for example under ERE in the Netherlands. They deliver the fuel to a road customer and issue a PoC. The PoC links back to the source PoS.
- The road customer uses the PoC to report their compliance.
At each step, the documentation must line up. Volumes must match. Sustainability characteristics must carry through. Validity windows must align.
Why this matters operationally
The distinction between PoS, PoC and SD is not academic. Compliance and commercial teams feel the weight of these documents every day. And it shows up on the P&L, in the calendar, and in the audit report.
These documents are the licence to earn the green premium. A PoS is not just paperwork attached to a delivery. It is the document that allows the fuel to be sold as renewable in the first place. If the PoS is invalid, incomplete or misses key characteristics, the sale cannot be booked against the green premium.
The same goes for a PoC on a FuelEU Maritime delivery. Without a PoC, the shipping customer cannot file the claim and sees the premium they were willing to pay evaporate. Illustrating the importance of the document layer directly driving the margin.
Every incoming PoS is a chunk of a compliance officer’s week. One incoming PoS from a supplier takes 15 to 30 minutes to handle manually. Validating the fields against the contract, checking that the counterparty’s ISCC certificate is still valid, entering the sustainability characteristics into the mass balance, filing the PDF against the transaction, reconciling it against the invoice.
For a trader receiving 20 to 30 PoSses per month, that is close to a full working week. Not to mention the work that goes into the outgoing PoS and PoC generation still to come on top.
Partial allocations turn the mass balance into a moving target. An incoming PoS covering 5,000 MWh is almost never sold in one transaction. It gets split, allocated and drawn against over weeks or months, sometimes across quarter-end.
Tracking is complicated. How much remains on each PoS? Which sustainability characteristics still apply? Is the validity window still open at the moment of sale? This is one of the biggest daily headaches in the industry.
Every scheme and every registry wants outputs in its own format. ISCC EU expects one template. REDcert another. 2BSvs a third. And that is before national registries. Nabisy in Germany, HBE in the Netherlands, RTFO in the UK all have their own submission structure.
The same underlying transaction has to be re-formatted for each destination. Every reporting round is another cycle of reformatting the same data by hand.
Counterparty templates vary wildly. No two suppliers issue PoS in exactly the same layout. Some trader PoS templates are notoriously heavy and hard to parse. Smaller trading houses often send Excel-based PoS. Older ISCC templates still coexist with newer ones.
Reformatting incoming documents into a shape the mass balance can actually digest is a layer of overhead. It lives outside any scheme rulebook, taking up valuable time every week.
Audit friction shows up at the worst moment. An auditor asks: “Show me every outgoing PoS in Q2 that traces back to this specific batch of UCO.” The answer needs to be ready in minutes, not days.
If the answer needs assembling multiple spreadsheets, digging through email and cross-referencing files across drives, that reconstruction time is itself an audit finding. Even if the underlying data is fine.
Errors in one document propagate through the chain. Say the feedstock category on the upstream SD is wrong. That error flows into the PoS issued by the processor. Then into the outgoing PoS from the trader. And then into the PoC issued to the final compliance customer.
By the time it surfaces at audit, the error has compounded through multiple parties. And correcting it becomes materially harder.
Different roles retain different things. A trader holds incoming PoS records and issues outgoing PoS records. A bunker operator also issues PoCs for FuelEU Maritime deliveries. An upstream collector deals mostly in SDs. What needs to be kept, and for how long, varies by role and by scheme.
How FuelFWD handles this
FuelFWD is built around the operational reality above. Every pain point in the previous section points to a specific piece of platform functionality
Protecting the green premium. Incoming PoS gets validated against the underlying contract at the moment of ingestion. Certificate validity, feedstock eligibility, GHG values, volume tolerances and expiry dates all get checked automatically.
Outgoing PoS and PoC are then generated in the correct scheme format against the mass balance. The sustainability characteristics carry through, so the document layer that drives the premium is defensible before the sale is booked
Removing 15 to 30 minutes per PoS. Incoming PoS are read by a combined OCR and LLM extraction pipeline. Every field lands in a structured record in about one minute.
Every extracted field is reviewable side-by-side against the source PDF. The compliance officer confirms rather than retypes. The record is then automatically linked to the underlying purchase contract and gets cross-checked against the supplier invoice when it lands into the system
Remaining volume tracked per PoS, in real time. Each PoS record carries an initial, sold and remaining quantity. Partial sales, allocations across quarters and splits across multiple buyers all subtract from the remaining balance automatically.
At any moment, the mass balance shows exactly which PoSses still have quantity remaining, what their sustainability characteristics are, and whether they are still within their validity window
Registry-ready outputs per scheme. FuelFWD generates outputs in the exact format each recipient expects. ISCC EU PDFs. REDcert templates. 2BSvs formats. Nabisy CSV.
New formats can be added within a working day, preventing a new registry or new customer template from becoming a project
Template-agnostic ingestion. The platform parses custom PoS formats, smaller Dutch trading house Excel files, older and newer ISCC templates, homemade producer formats, and everything in between. All into the same clean record structure.
The counterparty variation that today costs hours of manual reformatting each week becomes irrelevant the moment it enters FuelFWD
Audit queries in minutes, not days. Every document is linked to the transaction, the counterparty, the storage location and the sustainability chain it belongs to.
When an auditor asks “show me every outgoing PoS in Q2 tied to this specific batch of UCO”, the export is one action. Every change to every record is logged with timestamp and user, making the audit trail queryable rather than reconstructable
Validation at every layer, not just at the top. Cross-checks run between SD, PoS, PoC and invoice at the moment of issue. Let’s say the feedstock category on the upstream SD does not match the PoS being generated, or the PoC volume does not reconcile with the source PoS. FuelFWD flags it before the document goes out. Errors get caught where they start, instead of surfacing three parties downstream
Role-based retention, aligned to the role. Different user roles see and manage different document types. A trader sees the PoS in and PoS out layer. A bunker operator also manages PoC issuance under FuelEU Maritime. An upstream collector primarily works with SDs.
Retention windows and access controls are configured per role and per scheme, ensuring that the right documents are held for the appropriate time period without manual policing.
The pattern that emerges is simple. FuelFWD validates at the moment of ingestion and at the moment of issuance, making the comparisons the auditor eventually runs come out clean. The documentation layer becomes an efficient and integral part of trade execution, and stops being the slow, error-prone collateral of sustainable fuel trading.
Common questions
Is a PoS the same as a Sustainability Declaration? Depending on the scheme, the terms may be used interchangeably. In ISCC EU, the formal output document for end-fuels is the Proof of Sustainability. In some other schemes, the term Sustainability Declaration is used. The fields are typically similar.
Does every delivery need a PoC? No. PoCs are needed when the customer has a regulatory obligation that requires documented compliance allocation. For pure commercial trades without a regulatory destination, only the PoS travels.
Can the same volume have multiple PoCs? A specific volume should not be allocated to multiple compliance obligations. The PoC documents a specific allocation. Double-counting is one of the most serious compliance failures.
What is the typical validity window for a PoS? Typically one year, with variations by scheme. The validity window applies to when the PoS can be used to support a claim, not to the underlying fuel.
The bigger picture
The documentation layer of renewable fuel compliance is more elaborate than it looks from the outside. PoS, PoC, SD, BDN for bunker deliveries and a stack of supporting records all sit alongside the physical fuel movement. Understanding these documents is the foundation of a clean audit trail.
The companies that handle these layers well run cleaner audits, they attract more demanding customers, and they scale faster. The ones that treat the documentation as paperwork tend to discover, mid-audit, that the paperwork was the product all along.