A representative Spanish leasing operation financed distributed solar systems, battery storage, and commercial EV charging equipment. Each project arrived as a pack: supplier quotation, invoice, technical datasheet, installation certificate, and sometimes a grid-connection document.
Operations staff created the asset register manually. They copied equipment counts, capacities, serial ranges, installation addresses, and financial totals from several PDFs. Missing certificates were often discovered late, delaying activation of the lease.
Why completeness mattered as much as extraction
The team needed to know both what each document contained and whether the complete pack had arrived. The automation therefore classified files first, extracted structured data second, and applied a checklist based on asset type.
Creating a structured asset pack
Files entered through a project portal and were grouped by project ID. ConvertToData extracted the commercial and technical values. The integration created separate but linked objects for the finance case, physical assets, site, and source documents.
Validation rules checked that invoice totals reconciled, installed capacity matched the approved quotation, required certificates were present, and serial-number counts agreed with equipment quantities. The system did not activate a lease when mandatory evidence was missing.
Example JSON sent to the asset register
{
"projectId": "ES-GREEN-2026-0319",
"documentType": "installation_invoice",
"site": {
"region": "Valencia",
"country": "ES"
},
"assets": [
{"type": "solar_array", "capacityKWp": 120},
{"type": "battery_storage", "capacityKWh": 215}
],
"commercial": {
"equipment": 168400.00,
"installation": 21600.00,
"total": 190000.00,
"currency": "EUR"
},
"packComplete": true
}
Illustrative improvement in pack readiness
The representative process shortened asset setup from an illustrative 26 minutes to 6 minutes for complete standard packs. More importantly, missing technical evidence was detected at intake rather than at lease activation.
Design principles for renewable asset finance
Technical and commercial data should remain linked but not be flattened into one ambiguous table. Preserve units, keep source-document references, and validate project-level totals separately from individual asset values.
This pattern supports lessors that finance complex equipment bundles and need a reliable asset register for operations, insurance, servicing, and end-of-lease decisions.
