Why a Rendered Invoice Can Still Fail Send

An invoice PDF can exist and still not be an invoice package. That sentence shaped the send path. The easy implementation would render the invoice, store the PDF, try to build the XML, and log a warning if the compliance layer failed. The client still gets a document. The API still returns success. The business can "fix it later." That is exactly the failure I did not want. Klevar Docs treats e-invoicing as part of finalization, not as decoration after rendering. For an invoice that routes to Fa