What we've builtEnergy renovation
The bank request nobody sends anymore
Grant-advance bundles used to be assembled by hand and checked by hand. Now the platform builds them, sends them, polls the answer and moves on.
The setup
A dossier looked like it was with the bank. It had been for three weeks. It had never left. A consent file was missing, the send had failed quietly, and nobody had a way to know. That dossier is the reason this system exists.
What we did
The bundle is now assembled by the platform from the company's own storage and the e-signature service: identity papers, tax notice, quote, grant letter, signed consent and mandate. A database trigger fires the request the moment the back office validates the dossier. A scheduled job polls the bank's answer and walks the dossier through the seven states between pre-acceptance and payment. The state machine only moves forward, so a late or duplicated answer can never push a dossier backwards.
Then the bank's content firewall started rejecting files. Encrypted PDFs from certification bodies. PDFs with embedded scripts. Certified PDFs from notaries. We traced one rejection to an encrypted certificate whose streams our merger had copied as garbage. Every file is now normalised at send time: images converted, encryption removed, scripts stripped, signed documents passed through untouched, all pages of a slot merged so the bank never gets only the newest of three scans.
And the silent failure is gone. Any failed exchange posts to the operations channel within seconds, request and response attached. Test dossiers are flagged so they can never reach the bank.
What changed
No hands on the pipeline
Seven sub-states from pre-acceptance to payment, advanced automatically.
No silent failures
Seconds to notice, not weeks.
One written contract
Two apps, one database, one rule set for who moves a dossier and when, checked against the code line by line.