> For the complete documentation index, see [llms.txt](https://docs.openstamanager.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openstamanager.com/2.9.7/guide/esempi/fatturazione-elettronica/fattura-pa.md).

# Split payment e reverse charge

Guida alle operazioni in split payment e reverse charge con OpenSTAManager

{% hint style="info" %}
La pubblica amministrazione richiede **Split payment** o **Reverse charge**. Come gestire questi due parametri in **OpenSTAManager**?
{% endhint %}

## Split payment

Creando una fattura di vendita è possibile abilitare lo **split payment** spuntando la casella sotto indicata.

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/HoMmGZTnurR1ml9PAlS4/SplitPayment.png)

Così facendo nella tabella **Righe** il **Totale** sarà comprensivo di **IVA,** mentre il **Netto a pagare** sarà **IVA esclusa** perché l'imposta relativa alla transizione sarà a carico della pubblica amministrazione.

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/TWRQnkUr78WBB58Xmqzx/RigheSplitPayment.png)

Si dovrà inoltre cliccare su Attributi avanzati e andare a inserire l'IdDocumento e a valorizzare almeno uno dei due campi CodiceCUP e CodiceCIG.

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/wYqZH4bat0vA8aymmU3i/immagine.png)

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/5iYnvcXPd4rQsBMTkZaL/immagine.png)

##  Reverse charge

Il riferimento normativo del ***reverse charge*** IVA in Italia è rappresentato dall'*articolo 17*, commi 5 e 6. Il reverse charge è applicabile quindi andando a selezionare l'aliquota IVA corretta nel momento di creazione di una riga:

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/IFInnfSYts5RN0GRVLSI/N6.png)

Il risultato ottenuto sarà il seguente:

![](https://content.gitbook.com/content/DmQzkOGDOL4JJFhduzJ3/blobs/JOfIFaPHLRhliq7YZa6B/RigheN6.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openstamanager.com/2.9.7/guide/esempi/fatturazione-elettronica/fattura-pa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.