Define phases
Add phase
Click + New phase. Fill:
- Name: e.g. “Requirements analysis”, “MVP development”, “Go-live”
- Description: phase objectives
- Start / expected end date
- Invoiceable amount: % or absolute value of budget
- Predecessors: other phases that must close first
Phase statuses
| Status | Meaning |
|---|---|
| Planned | Phase created, not started |
| In progress | Active |
| Completed | Team declares done |
| Pending signature | Sent to customer for approval |
| Signed | Customer signed the SAL |
| Invoiced | Invoice issued for this phase |
Close a phase
Declare completion
PM clicks Mark as completed. Arya asks for a short note and attaches closure documents (report, deliverables).
Send to customer
Send for signature → Arya generates a SAL PDF with description, amount, deliverable checklist. The customer receives a public link to sign it digitally.
Customer signs
Qualified electronic signature (QES) via SPID or certificate. On signing, the phase moves to
Signed.Issue invoice
Click Generate SAL invoice. Arya creates the e-invoice with the phase amount, ready for SDI submission. See E-invoicing.
SAL variants
You can add variants (mid-project changes that modify amounts or deliverables):- New variant → specify changes → customer signs → budget updated
SAL report
Project page → SAL report: visual timeline of phases with status, planned vs actual dates, invoiced vs remaining.Frequently asked questions
Can I invoice without a signed SAL?
Can I invoice without a signed SAL?
Technically yes, but Arya’s flow blocks invoice generation if the phase isn’t signed. Force with
⋯ → Early invoice (Admin role required).What if the customer rejects the SAL?
What if the customer rejects the SAL?
Phase returns to
Completed. You can renegotiate deliverables, add a variant, and resubmit for signature.Can I have parallel phases?
Can I have parallel phases?
Yes, if there are no predecessor dependencies. Arya shows them in parallel on the timeline.