Shrisun (solar) — Document automation

Shrisun Solar Solutions install rooftop solar. Every installation generates a stack of statutory paperwork for India's Rooftop Solar Programme and for net metering with the state distribution company — a work completion report, a programme agreement, a commissioning report, a net metering connection agreement, an application to the meter testing lab, and an invoice. Six documents. The same customer details appear across most of them, in different places, in different layouts, and every one has to match a fixed government proforma or it comes back.

The installer now fills one form and gets all six.

The part that makes this a product rather than a template fill is the dependency map. The system knows which fields feed which documents: the customer's name, consumer number and address are on all six; the sanction number, installed capacity, warranty, year of manufacture, charge controller and identity number appear only on the work completion report; module make, model and wattage feed two documents; inverter capacity feeds three. Because that map exists, the interface can tell somebody exactly which fields are still missing for the documents they have actually selected — and nothing else. Nobody is asked for information they do not need.

The generation itself is around three and a half thousand lines of hand-written layout code drawing in millimetres on A4, because these are printed forms with fixed positions, not web pages. The generator measures the content it has been given and, when a page would overflow, scales everything by the same ratio — cell heights, font sizes, line spacing, padding and the signature images together — so the proportions hold rather than the layout breaking. Column widths were rebalanced against the longest real address so that long entries wrap to fewer lines. Cell padding is tuned to look balanced rather than to be numerically equal, because the top of a letterform is not where the box begins. That is the difference between producing a PDF and producing one a regulator accepts.

Signatures, vendor stamps and identity documents are uploaded and cropped in the browser and placed at fixed dimensions in the output.

Because those files contain identity numbers and signatures, generated documents expire automatically after thirty days, with a warning a week before and an expiry badge on every file in the admin view. The cleanup that enforces this had to be rebuilt mid-project: the scheduled job was deleting storage records directly from the database, which the platform blocks at runtime by design. It now runs through a proper storage function invoked on a schedule, authenticated with a secret held in a vault rather than sitting in the job definition where anyone with database access could read it.

Access is not open. People request it, an administrator grants it, and every generated file is logged.