Required documents in the flow
The applicant uploads what the programme needs. Completeness is checked, and retention follows the programme.
Nobody wants to chase the documents
Most delay is a missing or mismatched document. The applicant supplies what the programme needs in the flow, and completeness is checked before payout waits on email.
- Asked at the right step
- The applicant is told which document is needed, when it is needed.
- Completeness checked
- Rule-driven checks plus ML-assisted extraction. A person confirms when judgement is needed.
- Evidence on the decision
- Each decision points at the proof that supports it.
- Retention by programme
- Programme-specific retention and deletion in a vault.
Frequently asked questions
- What kinds of documents can be collected?
- Invoices, installation proofs, technical specifications, subsidy declarations, contractor confirmations, photos, inspection reports, and other types your programme requires.
- How are documents validated?
- Rule-driven checks, ML-assisted extraction, and a person when the rule does not decide.
- Do you support versioning or updates?
- Yes. Updated uploads keep the validation context so the record stays complete.
- How is retention and deletion handled?
- Documents sit in a vault with programme-specific retention and deletion rules, including GDPR.
