The applicant requests the advance or payout
A link after signing. They upload the evidence your rules require, and your team checks when judgement is needed. Four-eyes happens before booking, then amortization is updated when a payout is approved.
Evidence, then payout
Payout steps are where evidence, rules, and customer messages meet. The applicant submits what the programme needs. Your rules decide pass or fail. Your team only acts when judgement is needed.
- The applicant requests it
- Advances or final payouts without calling or emailing your team.
- Evidence against your rules
- Documents are checked with rule-driven logic and ML-assisted extraction.
- Four-eyes before booking
- Each payout must pass a structured review before it is booked.
- Payout documents
- Updated amortization tables, confirmations, and booking documents are created when the step passes.
- Messages at each step
- The applicant is told what happened at each payout step.
Frequently asked questions
- Who can request an advance or payout?
- The applicant starts from a link sent after contract signing and reservation. They select Advance or Payout and upload the required documents.
- What if the applicant loses the payout link?
- A handler can resend the link to the registered email from the case.
- Which documents are required before payout?
- That depends on your programme rules. Common examples: invoices, proof of payment, installation confirmations, technical documents, subsidy proofs.
- Is everything fully automated?
- Most steps are automated. A person appears for document validation, judgement, and the four-eyes check before booking.
- Do you create updated amortization tables automatically?
- Yes. An approved payout produces an updated amortization table and the matching customer message.
