Sări la conținut
    Back to blog
    May 6, 2026 5 min read Stefan

    From spreadsheet to official document: NIR, PV, and Borderou generated automatically

    How the data from a waste collection becomes official paperwork — NIR, PV, Annexes, Borderou — without manual copying into Word or Excel.

    #vanagreen
    #reciclare
    #documente
    #nir

    For any recycling operator, the moment a batch of waste enters inventory has to produce the paperwork that proves it — NIR (Notă de Recepție și Constatare de Diferențe, the Romanian goods-receipt-and-discrepancy note), PV (Proces Verbal, a handover protocol), the Annexes required under HG 856/2002 or HG 1061/2008 (Romanian government decisions regulating waste transport documentation), and Borderou for individuals selling waste as private persons. Until recently, at most small and mid-size operators, the real workflow looked like this: collection data was written down once on paper or in a weighing spreadsheet, then someone retyped it manually into a Word template to produce the official document. The same information, entered twice, with two chances to get it wrong.

    VanaGreen removes the second step. Documents aren't filled in — they're generated.

    What automatic generation means in practice

    When a collection is finalized in the app, an internal event triggers rendering of the matching documents, with no extra action from the operator. The rule depends on the type of source:

    • Individual (private person) — generates a Borderou and a payment order (one PDF, two legally distinct documents).
    • Company or institution — generates NIR and an incoming PV; if the waste has a WEEE code (household appliances, electronics), also Annex 2 or Annex 3, depending on the waste's HG classification code.
    • Pre-collections — always generate a PV plus empty Annex 2 and Annex 3, ready to be filled in when the collection is finalized.

    Generation is asynchronous and never blocks anything — if PDF rendering hits a technical issue, finalizing the collection still succeeds; the document can be regenerated later, keeping the same number, series, and issue date as the first generation. That's a meaningful legal distinction: a regenerated document isn't a new document, it's the same record, just re-rendered.

    Why correct numbering matters

    An official document isn't just correct text — it needs a legal sequence number, with no gaps and no duplicates, that holds up even when two operators at the same location finalize collections at the same instant. VanaGreen allocates numbers through a database-level locking mechanism, so the sequences — NIR, incoming PV, outgoing PV, Borderou — stay correct no matter how many operators are working concurrently. Each tenant configures its four numbering flows separately, with its own prefix where needed.

    For an operator with multiple locations, or several people entering data at once during peak hours, this eliminates a whole class of errors that manual spreadsheets couldn't prevent: duplicate numbers, skipped sequences, documents "accidentally" rewritten with a different number.

    One PDF, not five open windows

    For collections from companies, where several documents can be generated at once (PV, Annex 2, Annex 3, NIR, Borderou, payment order), the app automatically combines them into a single PDF — a "bundle" — generated once the last document in the set is finalized. The operator no longer downloads each document separately to print or email to a partner; they get one complete file, ready to archive or send.

    In practical terms, that cuts out a step that in the manual version meant opening 3-5 different Word files, checking that they all matched the same collection, and merging them into one PDF with some external tool.

    What you don't see, but matters at an audit

    Document rendering runs through an isolated PDF engine that isn't allowed to make any external network request while generating a document — a security measure that prevents a compromised template from leaking data or being used as an attack entry point. It's not something an operator ever sees, but it's part of why you can trust that the generated document contains exactly the data from the collection, nothing more, nothing leaked elsewhere.

    The result for the operator

    A batch of waste enters the system once — weighing, source, HG code, quantity. From that moment, the official document exists, correctly numbered, with no retyping, no risk of someone mistyping a figure from Excel into Word. For an operator processing dozens of intakes a day, the difference doesn't show up in a single document — it shows up in the hours saved every month and in the absence of errors that only surface during an ANPM (Romanian National Environmental Protection Agency) audit or an end-of-month reconciliation.

    Want to discuss how this applies to your process?

    Schedule a technical audit

    Related articles