> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arya.so/llms.txt
> Use this file to discover all available pages before exploring further.

# SAL phases

> Organise the project in phases, request customer sign-off, invoice on progress.

**SAL** (*Stato Avanzamento Lavori*) is the standard Italian approach to invoicing multi-phase projects. Arya includes a full SAL flow: phase definition → execution → customer signature → invoicing.

<Frame>
  <img src="https://mintcdn.com/agevole/cM9eEPJE8FVhTNOb/images/progetti/en/sal-phases.svg?fit=max&auto=format&n=cM9eEPJE8FVhTNOb&q=85&s=56c403d0b2f5dae351c22505376d37ba" alt="SAL tab with phase list, status and amounts" width="1200" height="720" data-path="images/progetti/en/sal-phases.svg" />
</Frame>

## Define phases

<Steps>
  <Step title="Open SAL tab">
    Project page → **SAL** tab.
  </Step>

  <Step title="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
  </Step>

  <Step title="Reorder">
    Drag-and-drop. Sum of amounts cannot exceed total budget.
  </Step>
</Steps>

## 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

<Steps>
  <Step title="Declare completion">
    PM clicks **Mark as completed**. Arya asks for a short note and attaches closure documents (report, deliverables).
  </Step>

  <Step title="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.

    <Frame>
      <img src="https://mintcdn.com/agevole/cM9eEPJE8FVhTNOb/images/progetti/en/sal-signature.svg?fit=max&auto=format&n=cM9eEPJE8FVhTNOb&q=85&s=5ff19677a827f91d5fc7887ea7a29098" alt="Customer-side SAL signature page" width="1200" height="720" data-path="images/progetti/en/sal-signature.svg" />
    </Frame>
  </Step>

  <Step title="Customer signs">
    Qualified electronic signature (QES) via SPID or certificate. On signing, the phase moves to `Signed`.
  </Step>

  <Step title="Issue invoice">
    Click **Generate SAL invoice**. Arya creates the e-invoice with the phase amount, ready for SDI submission. See [E-invoicing](/en/finance/e-invoicing-sdi).
  </Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="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).
  </Accordion>

  <Accordion title="What if the customer rejects the SAL?">
    Phase returns to `Completed`. You can renegotiate deliverables, add a variant, and resubmit for signature.
  </Accordion>

  <Accordion title="Can I have parallel phases?">
    Yes, if there are no predecessor dependencies. Arya shows them in parallel on the timeline.
  </Accordion>
</AccordionGroup>