[{"data":1,"prerenderedAt":1124},["ShallowReactive",2],{"blog-posts-en":3},[4,269,521,696,880],{"id":5,"title":6,"body":7,"category":255,"country":256,"description":257,"extension":258,"featured":259,"meta":260,"navigation":261,"path":262,"primaryKeyword":263,"pubDate":264,"published":259,"readingTime":265,"seo":266,"stat":263,"statCaption":263,"stem":267,"translationKey":263,"verifiedDate":264,"__hash__":268},"blogEn\u002Fblog\u002Fdoes-a-generated-pdf-hold-up.md","Does a generated PDF hold up as evidence?",{"type":8,"value":9,"toc":244},"minimark",[10,14,17,20,25,33,36,43,47,50,61,67,73,77,80,83,117,120,123,127,130,137,144,150,153,157,164,167,170,177,181,184,211,214,218,221,224,227,230],[11,12,13],"p",{},"Somebody disputes a delivery note. The customer says the damage was already there. You have a PDF, generated automatically, with a signature drawn on a phone at the depot.",[11,15,16],{},"Does it hold up?",[11,18,19],{},"Usually yes, and considerably less strongly than the people who generated it assume. The reasons are worth understanding before you need them rather than after.",[21,22,24],"h2",{"id":23},"the-good-news-first","The good news first",[11,26,27,28,32],{},"A document is not inadmissible because it was produced by software. In the EU, eIDAS is explicit that an electronic signature cannot be denied legal effect ",[29,30,31],"strong",{},"solely"," because it is electronic or because it fails to meet the requirements of a qualified signature. Comparable principles apply in most other jurisdictions with modern evidence rules.",[11,34,35],{},"So the naive fear, that automating document production somehow makes the output count for less, is unfounded. A generated PDF is a document like any other.",[11,37,38,39,42],{},"The real question was never admissibility. It is ",[29,40,41],{},"weight",": how much work your document does once it is in front of someone who has to decide.",[21,44,46],{"id":45},"what-actually-decides-weight","What actually decides weight",[11,48,49],{},"Three things, roughly in order of how often they matter.",[11,51,52,55,56,60],{},[29,53,54],{},"Can you attribute it to a person?"," This is where most disputes live. Not \"was this document altered\" but \"was that actually them, and did they understand what they were agreeing to\". A drawn signature on a phone, with no identity check anywhere in the process, is evidence that ",[57,58,59],"em",{},"somebody"," signed. Tying it to a named individual depends entirely on the surrounding record.",[11,62,63,66],{},[29,64,65],{},"Can you show it has not changed?"," Easier to answer, and the part most tooling covers. A cryptographic seal or signature over the document's hash makes any later edit detectable. Without one, you are relying on your own file storage and your own word.",[11,68,69,72],{},[29,70,71],{},"Can you show where it came from?"," The question people forget until they need it. Was this generated from the order record it references, or typed into a template by hand? A document can be entirely unaltered and still have been wrong from the moment it was created. Integrity protection does not catch that; it fixes the contents in place without saying anything about whether they were right.",[21,74,76],{"id":75},"the-audit-trail-is-doing-more-work-than-you-think","The audit trail is doing more work than you think",[11,78,79],{},"For a signature with no identity verification behind it, the audit trail is not a nice extra. It is most of your case.",[11,81,82],{},"What is worth capturing, and what a dispute actually turns on:",[84,85,86,93,99,105,111],"ul",{},[87,88,89,92],"li",{},[29,90,91],{},"Who"," the link was sent to, and by what channel",[87,94,95,98],{},[29,96,97],{},"When"," each step happened: sent, opened, filled, submitted",[87,100,101,104],{},[29,102,103],{},"What"," was on screen at the moment of signing, meaning the exact document version",[87,106,107,110],{},[29,108,109],{},"From where",", meaning IP address and device, imperfect but corroborating",[87,112,113,116],{},[29,114,115],{},"What changed afterwards",", ideally nothing, and provably so",[11,118,119],{},"None of that is exotic, and most systems capture some of it. The failure mode is capturing it in a form that is not exportable, or overwriting it, or keeping it only for ninety days.",[11,121,122],{},"A practical test: could you produce, today, a complete history of one specific document from eighteen months ago, in a form somebody outside your company could read? If not, your audit trail is a log rather than evidence.",[21,124,126],{"id":125},"the-three-levels-briefly","The three levels, briefly",[11,128,129],{},"European law grades electronic signatures by how much verified identity sits behind them, and the level maps directly onto the attribution question above.",[11,131,132,133,136],{},"A ",[29,134,135],{},"simple"," signature (SES) is a signature with no certificate and no required identity check. Admissible, and you carry the burden of proving who signed.",[11,138,139,140,143],{},"An ",[29,141,142],{},"advanced"," signature (AES) authenticates the signer, binds the signature uniquely to them, and makes later changes detectable. This is the level that turns the attribution question from an argument into a record, and it is where most commercial documents should be.",[11,145,132,146,149],{},[29,147,148],{},"qualified"," signature (QES) adds a certificate issued by a trust service provider on the EU trusted list, after that provider has verified the person's identity. It carries the same legal effect as a handwritten signature across the EU, and the burden of proof reverses onto whoever disputes it.",[11,151,152],{},"Moving from simple to advanced is engineering work. Moving to qualified means paying a third party to identify every signer. That is why the middle level is where most of the value sits.",[21,154,156],{"id":155},"what-a-seal-adds-that-a-signature-does-not","What a seal adds that a signature does not",[11,158,159,160,163],{},"A signature says a person agreed. A ",[29,161,162],{},"seal"," says an organisation issued this.",[11,165,166],{},"Because a seal belongs to the organisation rather than an individual, it needs nobody's participation, and can therefore be applied automatically at the moment a document is generated. That is exactly when the useful context still exists: the source record, the template version, the timestamp.",[11,168,169],{},"For the disputed delivery note, a seal applied at generation lets you demonstrate that the document came out of your system, referencing that job, at that time, and has not changed since. The signature question is separate, and both need answering.",[11,171,172,173,176],{},"Note the honest limit: a seal is ",[29,174,175],{},"tamper evident",", not tamper proof. It does not prevent editing. It makes editing detectable, which is the useful property, but it is not the same claim.",[21,178,180],{"id":179},"four-things-to-keep","Four things to keep",[11,182,183],{},"Independently of what tooling you buy:",[185,186,187,193,199,205],"ol",{},[87,188,189,192],{},[29,190,191],{},"The document as issued",", byte for byte, not a regenerated copy. A regenerated PDF is a new document that happens to look the same.",[87,194,195,198],{},[29,196,197],{},"The full timeline",", exportable, in a format a third party can read.",[87,200,201,204],{},[29,202,203],{},"The link between document and source record",", so you can show what it was made from.",[87,206,207,210],{},[29,208,209],{},"Whatever identity evidence you have",", however weak, because weak evidence that exists beats strong evidence you did not capture.",[11,212,213],{},"Most organisations have the first and some of the second. The third is the one that quietly does not exist, and it is the one that is impossible to reconstruct after the fact.",[21,215,217],{"id":216},"where-docspawn-fits","Where docspawn fits",[11,219,220],{},"docspawn generates documents from your data and keeps everything collected in a filterable library with saved views, versions and an audit trail, so the record outlives the document rather than being buried in a PDF in somebody's inbox.",[11,222,223],{},"Against the four things worth keeping above: you can seal any document it generates with a qualified electronic seal and a qualified timestamp, applied as the document is produced. On a sealed document that covers the second and third items directly. You can show it has not changed, and you can show which record and template produced it, without relying on your own file storage or your own word. Sealing is an option per document, so it is worth turning on for the documents most likely to be disputed rather than treating it as a blanket setting.",[11,225,226],{},"The first and fourth are still yours to get right, and the fourth is where we are deliberately unimpressive: signatures docspawn collects are simple electronic signatures with no identity check, and advanced level is on the roadmap. The seal does not help here, because it proves who issued the document rather than who signed it. For the disputed delivery note, that means a sealed one answers the origin question cleanly, and the attribution question only as well as your audit trail allows. Which is a good argument for turning sealing on before the dispute rather than after it.",[11,228,229],{},"We would rather tell you which half is solved than let a seal imply the other one is.",[11,231,232,233,238,239,243],{},"Also worth reading: ",[234,235,237],"a",{"href":236},"\u002Fblog\u002Fprovenance-vs-integrity","Provenance and integrity: two different things a document can prove"," and ",[234,240,242],{"href":241},"\u002Fblog\u002Feidas-signature-levels","SES, AES and QES: the three eIDAS levels",".",{"title":245,"searchDepth":246,"depth":246,"links":247},"",2,[248,249,250,251,252,253,254],{"id":23,"depth":246,"text":24},{"id":45,"depth":246,"text":46},{"id":75,"depth":246,"text":76},{"id":125,"depth":246,"text":126},{"id":155,"depth":246,"text":156},{"id":179,"depth":246,"text":180},{"id":216,"depth":246,"text":217},"trust","global","Usually yes, and less strongly than people assume. What actually decides whether a document survives a dispute, what an audit trail is worth, and the four things to keep.","md",false,{},true,"\u002Fblog\u002Fdoes-a-generated-pdf-hold-up",null,"2026-07-27",7,{"title":6,"description":257},"blog\u002Fdoes-a-generated-pdf-hold-up","oMGmQ5J0VEFUkLvX2B5P_dV6fD3xsvn_1_Lv3LH1dY0",{"id":270,"title":271,"body":272,"category":255,"country":513,"description":514,"extension":258,"featured":259,"meta":515,"navigation":261,"path":241,"primaryKeyword":516,"pubDate":264,"published":259,"readingTime":517,"seo":518,"stat":263,"statCaption":263,"stem":519,"translationKey":263,"verifiedDate":264,"__hash__":520},"blogEn\u002Fblog\u002Feidas-signature-levels.md","SES, AES and QES: the three eIDAS levels and which one you actually need",{"type":8,"value":273,"toc":501},[274,277,280,284,360,365,368,374,377,380,384,387,390,393,396,400,403,410,413,419,423,426,432,438,441,445,452,455,458,462,468,474,476,483,490,493],[11,275,276],{},"Every electronic signature in the European Union sits at one of three levels. They are not marketing tiers invented by vendors. They are defined in eIDAS, the regulation governing electronic identification and trust services, and the level determines what happens when someone disputes the signature.",[11,278,279],{},"Most people buying signature software never find out which level they are getting. That is the problem this article is meant to solve.",[21,281,283],{"id":282},"the-three-levels","The three levels",[285,286,287,305],"table",{},[288,289,290],"thead",{},[291,292,293,296,299,302],"tr",{},[294,295],"th",{},[294,297,298],{},"Requires",[294,300,301],{},"In a dispute",[294,303,304],{},"Typical use",[306,307,308,326,343],"tbody",{},[291,309,310,317,320,323],{},[311,312,313,316],"td",{},[29,314,315],{},"SES"," simple",[311,318,319],{},"A signature and, in practice, an audit trail. No certificate.",[311,321,322],{},"Admissible. You prove who signed.",[311,324,325],{},"Internal approvals, low-value consent.",[291,327,328,334,337,340],{},[311,329,330,333],{},[29,331,332],{},"AES"," advanced",[311,335,336],{},"Signer authenticated, signature uniquely linked to them, later changes detectable.",[311,338,339],{},"Strong. Hard to repudiate credibly.",[311,341,342],{},"Most commercial agreements.",[291,344,345,351,354,357],{},[311,346,347,350],{},[29,348,349],{},"QES"," qualified",[311,352,353],{},"All of AES, plus a qualified certificate from a provider on the EU trusted list and a key in certified hardware.",[311,355,356],{},"Equal to handwriting EU-wide. They prove it is wrong.",[311,358,359],{},"Where law specifically demands it.",[361,362,364],"h3",{"id":363},"ses-the-default-and-it-is-weaker-than-it-looks","SES: the default, and it is weaker than it looks",[11,366,367],{},"A simple electronic signature is the baseline. eIDAS defines it broadly enough that a typed name, a drawn squiggle, or a clicked \"I agree\" all qualify. There is no certificate and no identity check required by the definition.",[11,369,370,371,373],{},"The critical thing about SES is not that it is worthless. eIDAS explicitly says a signature cannot be denied legal effect ",[29,372,31],{}," because it is electronic or because it does not meet the requirements of a qualified signature. An SES is admissible.",[11,375,376],{},"What SES does not do is help you when the other side says \"that was not me\". You are left proving it yourself from whatever surrounding evidence you kept: the email trail, the IP address, the timestamps, the behaviour. If you kept a good audit trail, that is often enough. If you kept nothing, you have a signature that cannot be attributed to anybody.",[11,378,379],{},"Most electronic signatures in daily commercial use are SES. That is fine for most of what they are used for.",[361,381,383],{"id":382},"aes-the-level-worth-aiming-at","AES: the level worth aiming at",[11,385,386],{},"An advanced electronic signature has to satisfy four requirements. It must be uniquely linked to the signatory, capable of identifying them, created using data the signatory can use under their sole control, and linked to the signed data such that any later change is detectable.",[11,388,389],{},"Read those carefully and notice what is absent: nothing says a third party has to vouch for the identity. You can meet the AES bar with your own infrastructure, provided you actually authenticate the signer and actually bind the signature to the document.",[11,391,392],{},"That is why AES is the level most products should be aiming at, and the level most business contracts genuinely need. It moves you from \"we think this was them\" to \"this was cryptographically bound to an authenticated session, and the document has not changed since\". In practice, that ends most disputes before they become disputes.",[11,394,395],{},"The cost of getting from SES to AES is engineering work, not a supplier contract. That is the single most useful fact in this article.",[361,397,399],{"id":398},"qes-the-top-level-and-the-narrowest-need","QES: the top level, and the narrowest need",[11,401,402],{},"A qualified electronic signature is an advanced signature created by a qualified signature creation device and based on a qualified certificate. The certificate is issued by a qualified trust service provider listed on an official EU trusted list, after that provider has verified the individual's identity, and the private key lives in certified hardware.",[11,404,405,406,409],{},"The legal payoff is specific and large: a QES has the ",[29,407,408],{},"equivalent legal effect of a handwritten signature"," across the EU, and other member states must recognise a QES issued in any member state. The burden of proof reverses. The person disputing it has to prove it is invalid.",[11,411,412],{},"The cost is also specific. Every signer must be identified by the trust service provider, which is a per-person cost and a real step in the user's journey. Pricing is quote-based and rises with identification method.",[11,414,415,418],{},[29,416,417],{},"Who genuinely needs QES?"," Certain real estate transactions, notarial acts, some public-sector filings, and specific employment and credit contracts in countries including Germany, Spain, Italy and France. The list is narrower than vendors imply, it is national rather than EU-wide, and it changes. If someone tells you your ordinary B2B service agreement requires QES, ask them which national provision they are relying on.",[21,420,422],{"id":421},"how-to-work-out-which-level-you-need","How to work out which level you need",[11,424,425],{},"Two questions, in this order.",[11,427,428,431],{},[29,429,430],{},"One: is there a legal requirement?"," For a specific document type, in a specific country, is there a rule that says this must be a qualified signature or notarised? If yes, the answer is decided for you and no amount of engineering substitutes for it. If no, move on.",[11,433,434,437],{},[29,435,436],{},"Two: what is your actual risk?"," How much money is on the line, how likely is the counterparty to dispute it, and what evidence would you want in front of a judge? For a delivery note signed by a driver, an audit trail is proportionate. For a fifty thousand euro equipment lease, you probably want the signer authenticated.",[11,439,440],{},"Notice that the second question is about evidence, not compliance. Most of the time you are not satisfying a rule, you are deciding how much proof to buy.",[21,442,444],{"id":443},"the-seal-which-is-not-on-this-ladder","The seal, which is not on this ladder",[11,446,447,448,451],{},"One thing that confuses this picture: eIDAS also defines electronic ",[29,449,450],{},"seals",", which run through the same simple, advanced and qualified grading but do a different job.",[11,453,454],{},"A signature is given by a person and carries intent. A seal is issued by an organisation and carries origin. Because a seal has no human to wait for, it can be applied automatically, at the moment a document is generated, which is something no signature can do at any level.",[11,456,457],{},"That means the two are not alternatives. A document can carry an organisation's seal proving where it came from, and a person's signature proving they agreed to it, and each answers a question the other cannot.",[21,459,461],{"id":460},"two-phrases-to-distrust","Two phrases to distrust",[11,463,464,467],{},[29,465,466],{},"\"eIDAS compliant.\""," All three levels are eIDAS compliant, so the phrase is equally true of the weakest option on the market and the strongest. It is technically accurate and informationally empty. Always ask which level.",[11,469,470,473],{},[29,471,472],{},"\"Certified signature.\""," This has no definition in eIDAS. The levels are simple, advanced and qualified. A term outside the regulation's vocabulary cannot be checked against it.",[21,475,217],{"id":216},[11,477,478,479,482],{},"docspawn generates documents from your data and collects signatures on them. Those signatures are ",[29,480,481],{},"simple electronic signatures",": a link, a name given on a phone, and an audit trail of who filled what and when. There is no identity verification in that flow today, and advanced level is on the roadmap.",[11,484,485,486,489],{},"Separately, and this is the part that is live: you can seal any document docspawn generates with a ",[29,487,488],{},"qualified electronic seal"," and a qualified timestamp, applied as the document is produced. Sealing is an option you turn on, not something applied to everything. And it is a seal, not a signature: it proves the document was issued by docspawn's system, from that record, at that moment, and has not changed since. It says nothing about who signed it.",[11,491,492],{},"We are stating the current signature level plainly, and refusing to let the seal blur it, because the point of this article is that vendors should. If a supplier cannot tell you which of the three levels you are buying, that is the answer.",[11,494,232,495,238,499,243],{},[234,496,498],{"href":497},"\u002Fblog\u002Fwhat-is-an-electronic-seal","What is an electronic seal, and how is it different from a signature?",[234,500,6],{"href":262},{"title":245,"searchDepth":246,"depth":246,"links":502},[503,509,510,511,512],{"id":282,"depth":246,"text":283,"children":504},[505,507,508],{"id":363,"depth":506,"text":364},3,{"id":382,"depth":506,"text":383},{"id":398,"depth":506,"text":399},{"id":421,"depth":246,"text":422},{"id":443,"depth":246,"text":444},{"id":460,"depth":246,"text":461},{"id":216,"depth":246,"text":217},"eu","European law grades electronic signatures by how much verified identity sits behind them. What each level requires, what it is worth in a dispute, and why most contracts do not need the top one.",{},"eidas electronic signature",8,{"title":271,"description":514},"blog\u002Feidas-signature-levels","-Zk7dfy1yonsriL4fNp8lNFma6vtUP_tspBVFkkq-4U",{"id":522,"title":237,"body":523,"category":255,"country":256,"description":690,"extension":258,"featured":259,"meta":691,"navigation":261,"path":236,"primaryKeyword":263,"pubDate":264,"published":259,"readingTime":692,"seo":693,"stat":263,"statCaption":263,"stem":694,"translationKey":263,"verifiedDate":264,"__hash__":695},"blogEn\u002Fblog\u002Fprovenance-vs-integrity.md",{"type":8,"value":524,"toc":682},[525,528,534,540,543,547,550,553,556,559,562,566,572,575,578,585,592,595,599,605,611,614,617,621,624,631,634,637,640,644,647,652,655,658,661,663,666,669,676],[11,526,527],{},"There are two different claims a document can make about itself, and they get treated as one thing constantly.",[11,529,530,533],{},[29,531,532],{},"Integrity",": this file has not changed since it was sealed.",[11,535,536,539],{},[29,537,538],{},"Provenance",": this file was produced from this data, by this system, at this moment.",[11,541,542],{},"Integrity is the one everybody sells. Provenance is the one that answers the question people actually have.",[21,544,546],{"id":545},"the-distinction-concretely","The distinction, concretely",[11,548,549],{},"Imagine an invoice arrives and someone says the total is wrong.",[11,551,552],{},"An integrity guarantee answers: has this PDF been altered since it was signed? That is a real and useful answer. It rules out one specific kind of fraud, the after-the-fact edit.",[11,554,555],{},"It does not answer: was this total ever correct? Did it come from the order record it claims to reference? Which price list was applied? Was this generated from the system of record, or typed by hand into a template by someone who then signed it?",[11,557,558],{},"A perfectly intact document can be perfectly wrong. Integrity says nothing about whether the contents were right when they were fixed in place. It only says they have not moved since.",[11,560,561],{},"Provenance is the claim that covers that gap. It ties the document back to the thing it was made from.",[21,563,565],{"id":564},"why-the-distinction-is-structural-not-competitive","Why the distinction is structural, not competitive",[11,567,568,569,243],{},"Here is the part that is easy to miss: the difference between these two claims is not a feature gap. It is a consequence of ",[29,570,571],{},"where each system sits in the workflow",[11,573,574],{},"Think about what a signing platform receives. A finished PDF. Somebody uploaded a file.",[11,576,577],{},"By the time that file exists, the interesting metadata is already gone. The record it was built from, the template version, the field values, the identity of whoever triggered generation, the moment it was produced: none of that is inside the PDF. It was discarded when the document was rendered. The platform is not withholding it or failing to expose it. It never had it.",[11,579,580,581,584],{},"So the strongest honest claim available to any tool that receives a finished document is ",[29,582,583],{},"\"this file has not changed since I first saw it.\""," Not because the engineering is lacking, but because that is genuinely the extent of what it witnessed.",[11,586,587,588,591],{},"The system that ",[29,589,590],{},"generates"," the document is in a completely different position. At the moment of generation, and only at that moment, all of those things exist together in one place: the source record, the template version, the resolved field values, the timestamp, the user. That is the only point in the lifecycle where a document can be bound to its origin, because it is the only point where its origin is still present.",[11,593,594],{},"Miss that moment and it cannot be recovered later. Not by a better signing platform, not by a better PDF library, not by anyone.",[21,596,598],{"id":597},"what-this-looks-like-in-practice","What this looks like in practice",[11,600,601,602],{},"A document with integrity protection carries, in effect: ",[57,603,604],{},"a hash, and a mark saying this hash was correct when I saw it.",[11,606,607,608],{},"A document with provenance carries something closer to: ",[57,609,610],{},"this was generated from record 4471, using template version 12, on 3 March at 14:22, by this system, and here is a mark proving all of that and proving the contents have not changed since.",[11,612,613],{},"The second contains the first. Provenance is not an alternative to integrity, it is integrity plus the context that makes integrity meaningful.",[11,615,616],{},"The mechanism for asserting it is not exotic. An electronic seal covers a hash of the document, and the metadata bound into the sealed payload rides along with it. The hard part was never the cryptography. The hard part is being present at the moment of creation, which is a matter of what your product is, not how good your crypto is.",[21,618,620],{"id":619},"why-this-is-becoming-urgent","Why this is becoming urgent",[11,622,623],{},"For most of the history of business documents, producing a convincing-looking document took effort. Not much effort, but enough that volume was self-limiting.",[11,625,626,627,630],{},"That constraint is gone. Generating a plausible invoice, report or certificate now costs approximately nothing, and generating a plausible ",[29,628,629],{},"fake"," one costs exactly the same, because they are the same operation. The skill floor that used to make forgery rare has collapsed.",[11,632,633],{},"The consequence is that a document's appearance has stopped being evidence of anything. A well-formatted PDF with a company logo used to carry weak but real signal. It now carries none.",[11,635,636],{},"What is left with value is proof of origin: the ability of a document to demonstrate where it came from, rather than merely looking like it came from somewhere. That is why this distinction is worth understanding now rather than in five years.",[11,638,639],{},"Regulators are circling the same problem from a different angle. The EU AI Act's transparency obligations, which begin applying in August 2026, require marking of AI-generated content, and commentary on the final rules has noted that no current marking technology meets all of the required properties. Watermarks can be stripped. A cryptographic seal cannot be stripped without breaking, which is a meaningfully different property.",[21,641,643],{"id":642},"what-to-ask-a-vendor","What to ask a vendor",[11,645,646],{},"One question separates the two claims cleanly:",[11,648,649],{},[29,650,651],{},"\"At what point in the process does your proof get applied, and what does it know at that point?\"",[11,653,654],{},"If the answer is \"when the document is uploaded to us\", you are buying integrity. That may be exactly what you need, and it is worth having.",[11,656,657],{},"If the answer is \"at generation, and it knows which record and template produced it\", you are buying provenance.",[11,659,660],{},"Both are legitimate products. They are just answers to different questions, and the pricing pages rarely make that clear.",[21,662,217],{"id":216},[11,664,665],{},"docspawn sits at the generation end. It holds the source record, the template version and the timestamp at the moment a document comes into existence, which is the position provenance requires.",[11,667,668],{},"That position is usable. Turn sealing on for a document and it gets a qualified electronic seal and a qualified timestamp, applied as it is produced, which is the only moment when the record, the template version and the timestamp all still exist together. It is an option per document rather than something applied to everything, and that is the right shape: provenance is worth paying for on the documents that will be argued about, not on all of them.",[11,670,671,672,675],{},"The honest limit, because this article is about being precise: the seal covers ",[29,673,674],{},"origin and integrity",", not identity. It proves the document came from this system, from that record, at that time, and has not changed since. Who signed it is a different question with a different answer, and docspawn collects simple electronic signatures with no identity check today. A seal is not a signature, and it does not upgrade one.",[11,677,232,678,238,680,243],{},[234,679,498],{"href":497},[234,681,6],{"href":262},{"title":245,"searchDepth":246,"depth":246,"links":683},[684,685,686,687,688,689],{"id":545,"depth":246,"text":546},{"id":564,"depth":246,"text":565},{"id":597,"depth":246,"text":598},{"id":619,"depth":246,"text":620},{"id":642,"depth":246,"text":643},{"id":216,"depth":246,"text":217},"Integrity says a file has not changed since someone saw it. Provenance says where it came from. Only the system that produced the document can attest to the second, and the reason is structural.",{},6,{"title":237,"description":690},"blog\u002Fprovenance-vs-integrity","i8f-f6ALMUfXidnP6L-ddYKbFy8pxB0SoAuHChVM8gk",{"id":697,"title":498,"body":698,"category":255,"country":513,"description":874,"extension":258,"featured":259,"meta":875,"navigation":261,"path":497,"primaryKeyword":876,"pubDate":264,"published":259,"readingTime":265,"seo":877,"stat":263,"statCaption":263,"stem":878,"translationKey":263,"verifiedDate":264,"__hash__":879},"blogEn\u002Fblog\u002Fwhat-is-an-electronic-seal.md",{"type":8,"value":699,"toc":865},[700,707,710,714,724,727,730,734,737,740,747,750,754,759,762,765,768,772,775,778,785,791,798,802,805,808,815,818,822,828,831,834,841,843,846,849,852,859],[11,701,702,703,706],{},"An electronic seal is a cryptographic mark that says ",[29,704,705],{},"an organisation issued this document",". It is defined in EU law, it is not the same thing as an electronic signature, and the difference is not a technicality. It changes what the mark can be used for and when it can be applied.",[11,708,709],{},"The short version: a signature is given by a person, a seal is issued by a legal entity. Everything else follows from that.",[21,711,713],{"id":712},"the-definition-and-why-it-is-worded-that-way","The definition, and why it is worded that way",[11,715,716,717,719,720,723],{},"eIDAS, the EU regulation that governs electronic trust services, defines an electronic seal as data attached to other data to ensure the latter's ",[29,718,674],{},". The signature definition is deliberately different: a signature is data used by a signatory ",[29,721,722],{},"to sign",", which is to say, to express intent.",[11,725,726],{},"That is the whole distinction in the legislation's own vocabulary. A signature carries an act of will: a human being read something and agreed to it. A seal carries an attribution: this came from us, and it has not changed since.",[11,728,729],{},"A useful analogy is the paper world. A director's handwritten signature at the bottom of a contract is a signature. The company stamp pressed into the letterhead is a seal. Nobody confuses the two on paper, and nobody would accept a rubber stamp as evidence that a specific person agreed to a specific clause. The electronic versions keep exactly that division of labour.",[21,731,733],{"id":732},"why-a-seal-can-be-automatic-and-a-signature-cannot","Why a seal can be automatic and a signature cannot",[11,735,736],{},"This is the practical consequence, and it is the reason seals matter for anyone generating documents at volume.",[11,738,739],{},"A signature has to be collected. Someone has to be shown the document, has to understand it, and has to choose to sign. You can make that fast and pleasant, but you cannot make it happen without them, and you certainly cannot do it on their behalf.",[11,741,742,743,746],{},"A seal has no such requirement. It belongs to the organisation, the organisation holds the key, and the organisation alone decides which of its documents get sealed. There is no second party to wait for. That means a seal can be applied ",[29,744,745],{},"at the moment a document is generated",", as part of producing it, rather than as a separate step afterwards.",[11,748,749],{},"If you produce two hundred delivery notes on a Tuesday morning, sealing all two hundred is a configuration decision. Getting two hundred signatures is a project.",[21,751,753],{"id":752},"the-qualified-level","The qualified level",[11,755,756,757,243],{},"eIDAS grades seals the same way it grades signatures: simple, advanced, and qualified. The word that matters is ",[29,758,148],{},[11,760,761],{},"A qualified electronic seal is created using a qualified certificate for electronic seals, issued by a qualified trust service provider that appears on an official EU trusted list, with the private key held in certified hardware. That last constraint is why a qualified seal is not something you can produce with a self-signed certificate and a script.",[11,763,764],{},"What qualification buys you is a legal presumption. Under eIDAS, a qualified electronic seal enjoys a presumption of the integrity of the data and of the correctness of the origin of that data. In plain terms: the burden of proof moves. Someone disputing a qualified-sealed document has to show it is wrong, rather than you having to show it is right.",[11,766,767],{},"An unqualified seal still carries cryptographic weight. It just does not carry that presumption, so you are back to arguing about your own key management.",[21,769,771],{"id":770},"tamper-evident-not-tamper-proof","Tamper evident, not tamper proof",[11,773,774],{},"This distinction gets flattened in marketing copy constantly, so it is worth being precise.",[11,776,777],{},"A seal does not stop anyone editing a document. Nothing does. A PDF sitting on someone's laptop can be opened and altered like any other file.",[11,779,780,781,784],{},"What a seal does is make the alteration ",[29,782,783],{},"detectable",". The seal covers a cryptographic hash of the document's contents. Change a digit in a total, move a decimal point, replace a photograph, and the hash no longer matches, so the seal fails validation. Anyone who checks sees a broken seal rather than a clean one.",[11,786,787,788,790],{},"That is the correct claim: ",[29,789,175],{},". If you see a vendor writing \"tamper proof\" or \"unforgeable\", they are describing something that does not exist.",[11,792,793,794,797],{},"Pairing the seal with a ",[29,795,796],{},"qualified timestamp"," adds the other half of the story. The seal says what the document contained; the timestamp says when it demonstrably existed in that state, attested by a third party rather than by your own server clock. Together they answer \"what\" and \"when\", which is most of what a dispute turns on.",[21,799,801],{"id":800},"where-seals-are-already-routine","Where seals are already routine",[11,803,804],{},"Seals are not speculative technology waiting for adoption. They are load-bearing in European e-invoicing today.",[11,806,807],{},"Italy has required structured, cryptographically signed electronic invoices through its Sistema di Interscambio since 2019. Spain's Verifactu regime requires a qualified electronic signature on invoicing records that are not filed directly with the tax authority, phasing in during 2027. France, Germany and Poland are phasing in their own e-invoicing mandates between 2026 and 2028.",[11,809,810,811,814],{},"One important caveat, because it cuts against the obvious sales pitch: ",[29,812,813],{},"no general rule requires an ordinary business to seal its own documents."," Poland's KSeF is the clearest counterexample. It puts authenticity guarantees at the platform layer and explicitly does not require a per-invoice seal. Anyone telling you the law forces you to seal your paperwork is overstating it, and the counterexample is one search away.",[11,816,817],{},"The honest version is that mandates in this space are training a continent to expect documents that can prove things about themselves, without any single mandate covering the general case.",[21,819,821],{"id":820},"the-vocabulary-trap","The vocabulary trap",[11,823,824,825],{},"If you take one practical thing from this article, take this: ",[29,826,827],{},"\"eIDAS compliant\" on its own means nothing.",[11,829,830],{},"A simple electronic signature is eIDAS compliant. So is an advanced one. So is a qualified seal. The regulation defines all of them, so the phrase is equally true of the weakest and the strongest option on the market, while sounding like it describes the strongest.",[11,832,833],{},"Similarly, \"certified signature\" has no definition in eIDAS at all. The levels are simple, advanced and qualified. A term outside that vocabulary cannot be checked, which is usually why it gets used.",[11,835,836,837,840],{},"When you are evaluating anything in this space, the only useful question is: ",[29,838,839],{},"which level, exactly?"," A vendor who can answer that immediately is telling you something. A vendor who reaches for \"compliant\" or \"certified\" is telling you something too.",[21,842,217],{"id":216},[11,844,845],{},"You can seal any document docspawn generates. Turn sealing on and the document gets a qualified electronic seal and a qualified timestamp, applied as it is produced rather than added afterwards. That is the whole argument of this article put into practice: because docspawn is the thing producing the document, the seal can be bound to the record it came from, the template version used, and the moment it was produced. A tool that receives a finished PDF never had any of that, because it was discarded before the file arrived.",[11,847,848],{},"Sealing is an option rather than something applied to everything, which is the right shape for it. Most documents in most businesses do not need to prove their origin to anybody. The ones that do tend to know who they are: the condition report that will be argued about, the certificate somebody will present to a third party, the invoice that has to survive an audit.",[11,850,851],{},"Signatures are a separate question, and worth keeping separate. docspawn collects simple electronic signatures: a link, a name given on a phone, and an audit trail of who filled what and when. There is no identity check in that flow, which is why the product says so plainly on the form itself. Advanced level is on the roadmap.",[11,853,854,855,858],{},"The seal does not change that. It proves who ",[29,856,857],{},"issued"," the document, not who signed it. A sealed document carrying a simple signature is exactly that, and anyone telling you a seal upgrades a signature has the two concepts confused.",[11,860,232,861,238,863,243],{},[234,862,242],{"href":241},[234,864,237],{"href":236},{"title":245,"searchDepth":246,"depth":246,"links":866},[867,868,869,870,871,872,873],{"id":712,"depth":246,"text":713},{"id":732,"depth":246,"text":733},{"id":752,"depth":246,"text":753},{"id":770,"depth":246,"text":771},{"id":800,"depth":246,"text":801},{"id":820,"depth":246,"text":821},{"id":216,"depth":246,"text":217},"An electronic seal is issued by an organisation, not given by a person. What eIDAS says it is, what the qualified level adds, and why a seal can be applied automatically where a signature cannot.",{},"what is an electronic seal",{"title":498,"description":874},"blog\u002Fwhat-is-an-electronic-seal","xql4YB1_vXKI2j0fXcyra8KcnPmxsQ2w-BY2GL_tYEo",{"id":881,"title":882,"body":883,"category":1116,"country":256,"description":1117,"extension":258,"featured":259,"meta":1118,"navigation":261,"path":1119,"primaryKeyword":1120,"pubDate":264,"published":261,"readingTime":265,"seo":1121,"stat":263,"statCaption":263,"stem":1122,"translationKey":263,"verifiedDate":264,"__hash__":1123},"blogEn\u002Fblog\u002Fwhat-is-document-generation.md","What is document generation?",{"type":8,"value":884,"toc":1108},[885,888,891,894,898,901,908,914,920,926,930,933,939,945,951,957,960,964,967,973,976,982,1000,1003,1007,1010,1016,1022,1028,1034,1038,1041,1083,1086,1089,1091,1094,1097,1100],[11,886,887],{},"Document generation is the practice of producing a finished document by merging structured data into a fixed layout, automatically, so that nobody retypes anything.",[11,889,890],{},"That is the whole idea. You have data somewhere: a spreadsheet row, a CRM record, a form submission, the output of a script. You have a document that has to look a particular way: an inspection report, a delivery note, a contract, a certificate. Document generation is the machinery between the two.",[11,892,893],{},"The reason it has a name at all is that the naive version does not scale. Copying a template, filling in the blanks by hand and exporting a PDF works fine for the first document and roughly the twentieth time it starts costing real hours. Document generation is what you reach for when that stops being acceptable.",[21,895,897],{"id":896},"what-document-generation-is-not","What document generation is not",[11,899,900],{},"The term gets used loosely, so it helps to draw the borders.",[11,902,903,904,907],{},"It is ",[29,905,906],{},"not document editing",". A word processor is where a human writes prose. Document generation assumes the prose is already decided and only the data changes.",[11,909,903,910,913],{},[29,911,912],{},"not e-signature",". Signing is what can happen to a document after it exists. Generation is how it comes to exist. The two are often bought together, which is why they get confused.",[11,915,903,916,919],{},[29,917,918],{},"not form building",". A form builder collects data. That is one input to document generation, not the thing itself. A form builder that emails you a summary of the responses has not generated your document, it has shown you the answers.",[11,921,903,922,925],{},[29,923,924],{},"not a PDF filler",". Filling a fillable PDF by hand is a manual act with a nicer interface. It becomes generation when the filling happens from a data source, without a person doing it.",[21,927,929],{"id":928},"the-four-pieces","The four pieces",[11,931,932],{},"Every document generation setup, no matter who sells it, is made of the same four parts. If you are evaluating tools, work out which of the four each one actually covers, because most cover two or three.",[11,934,935,938],{},[29,936,937],{},"1. The template."," The fixed layout, with holes in it where data goes. This is where the biggest differences between tools live, and the next section is entirely about it.",[11,940,941,944],{},[29,942,943],{},"2. The data source."," Where the values come from. A spreadsheet, a database, a CRM, a form submission, an API call, a person on a phone in a car park.",[11,946,947,950],{},[29,948,949],{},"3. The generation engine."," The thing that takes template plus data and returns a document. This is the part everyone means when they say \"document generation\", and it is the part that is mostly a solved problem.",[11,952,953,956],{},[29,954,955],{},"4. Delivery."," Getting the finished document to whoever needs it: emailed to a customer, filed in a system, attached to a record, handed to the next step in a workflow.",[11,958,959],{},"The fourth one is the one that quietly gets dropped. A tool that generates a beautiful PDF and leaves it in a folder has solved three quarters of the problem and left you with the quarter that involves a human doing the same thing every day.",[21,961,963],{"id":962},"templates-rebuild-or-bring-your-own","Templates: rebuild, or bring your own",[11,965,966],{},"There are two philosophies, and the choice constrains everything downstream.",[11,968,969,972],{},[29,970,971],{},"Rebuild it in their editor."," The tool gives you a template builder and you recreate your document inside it. This is the common approach because it makes the tool's job easy: it controls the layout format, so it can guarantee the output.",[11,974,975],{},"The cost lands on you. If your document is a plain letter, rebuilding takes ten minutes and nobody minds. If it is a three page inspection report with a checkbox grid, embedded photos, a signature block and a table that grows, rebuilding is a project. And every time the real document changes, you do it again.",[11,977,978,981],{},[29,979,980],{},"Bring your own file."," The tool works from the PDF you already use, and you tell it where the fields are. Nothing gets rebuilt, so nothing drifts from the document your business actually issues.",[11,983,984,985,988,989,992,993,999],{},"This is where PDF form technology matters. A PDF can carry interactive form fields, and there have historically been two competing ways to do it. ",[29,986,987],{},"AcroForms"," were introduced in the PDF 1.2 specification and are present in every later version. ",[29,990,991],{},"XFA",", an XML based alternative, arrived in PDF 1.5, was never compatible with AcroForms, and was deprecated from the format in PDF 2.0. Most PDF software does not handle XFA content at all. (",[234,994,998],{"href":995,"rel":996},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPDF",[997],"nofollow","Wikipedia: PDF, interactive forms",")",[11,1001,1002],{},"The practical consequence: AcroForm fields are the interoperable way to describe \"this box holds the customer name\", and a bring-your-own-file approach depends on being able to find and address those fields. Where they do not exist yet, they have to be added, which is the tedious part, and increasingly the part that gets detected automatically rather than drawn by hand.",[21,1004,1006],{"id":1005},"where-these-setups-break","Where these setups break",[11,1008,1009],{},"Four failure modes account for most of the disappointment.",[11,1011,1012,1015],{},[29,1013,1014],{},"The document is more complex than the tool assumed."," Tables that grow with the data, checkbox grids, conditional pages that appear only sometimes, photos captured in the field with annotations on them. Tools built for the letter-shaped document degrade badly here, and you usually discover this after choosing one.",[11,1017,1018,1021],{},[29,1019,1020],{},"It needs a developer, permanently."," Plenty of excellent generation engines are libraries and APIs. They are the right answer if you have engineers and want programmatic control. They are the wrong answer if the person who needs to change the wording of a clause is in operations, because every change becomes a ticket.",[11,1023,1024,1027],{},[29,1025,1026],{},"It stops before delivery."," See the fourth piece above. Generation without distribution leaves a human in the loop doing the least interesting job in the company.",[11,1029,1030,1033],{},[29,1031,1032],{},"The data goes nowhere."," The document gets made and sent, and the values inside it are gone, buried in a PDF in an inbox. Six months later somebody asks how many inspections failed on the same fault and the only way to answer is to open files one at a time. The data collected during generation is often more valuable than the document, and it is routinely thrown away.",[21,1035,1037],{"id":1036},"do-you-actually-need-it","Do you actually need it?",[11,1039,1040],{},"Two variables decide: how many documents, and how complex each one is.",[285,1042,1043,1055],{},[288,1044,1045],{},[291,1046,1047,1049,1052],{},[294,1048],{},[294,1050,1051],{},"Simple document",[294,1053,1054],{},"Complex document",[306,1056,1057,1070],{},[291,1058,1059,1064,1067],{},[311,1060,1061],{},[29,1062,1063],{},"Low volume",[311,1065,1066],{},"Do it by hand. Genuinely.",[311,1068,1069],{},"Do it by hand, carefully.",[291,1071,1072,1077,1080],{},[311,1073,1074],{},[29,1075,1076],{},"High volume",[311,1078,1079],{},"Almost any generation tool works. Pick on price and delivery.",[311,1081,1082],{},"This is the case that needs real evaluation.",[11,1084,1085],{},"The bottom right cell is where most of the frustration lives, because it is where the general purpose tools stop fitting and the specialist ones start needing developers.",[11,1087,1088],{},"One useful signal: if somebody in your organisation has a folder of near-identical documents named after customers, and opens the most recent one to make the next one, you have an unautomated document generation process. It just has a person in the middle of it.",[21,1090,217],{"id":216},[11,1092,1093],{},"docspawn takes the bring-your-own-file side of the template question. You upload the complex PDF you already use, AI detects the fillable fields so they do not have to be drawn by hand, and the output keeps the pixel-accurate fidelity of your original file, including tables, checkbox grids, annotated photos, signatures and multi-page layouts.",[11,1095,1096],{},"On the other three pieces: data can be captured from anyone through web, mobile or voice, including public links that let third parties upload PDFs and IDs without an account. Conditional logic decides what gets generated and what gets appended. A spreadsheet becomes a batch of documents in one run. The finished document is sent, rather than left in a folder. And everything collected stays in a filterable library with saved views, versions and an audit trail, so the data outlives the document.",[11,1098,1099],{},"An MCP server and an API, so that a CLI, n8n, Zapier or an AI agent can hand over data and get a finished document back, are on the roadmap and not yet released.",[11,1101,1102,1103,1107],{},"If that maps onto the problem you actually have, ",[234,1104,1106],{"href":1105},"#book-demo","book a demo"," and we will walk through your document rather than a sample one.",{"title":245,"searchDepth":246,"depth":246,"links":1109},[1110,1111,1112,1113,1114,1115],{"id":896,"depth":246,"text":897},{"id":928,"depth":246,"text":929},{"id":962,"depth":246,"text":963},{"id":1005,"depth":246,"text":1006},{"id":1036,"depth":246,"text":1037},{"id":216,"depth":246,"text":217},"automation","Document generation turns structured data into a finished document with nobody retyping it. What it covers, the four pieces it needs, and where it breaks.",{},"\u002Fblog\u002Fwhat-is-document-generation","what is document generation",{"title":882,"description":1117},"blog\u002Fwhat-is-document-generation","k_IJCGtIspj5ou1oYkwQd9Oug-JZV2kqZemDA548HYc",1785171669562]