# Use commit and uncommit

Source: https://developer.avalara.com/products/communications/integration-guides/communications-integration/iyd8924845980836/

Guide: Communications

# Use commit and uncommit

Understand how to use commit and uncommit processes to manage transaction groups and compliance reporting.

The commit process groups transactions by a Document Code (`doc`) and indicates if the transaction group should be included in compliance reporting (`cmmt`).

-   Group the transactions by invoice.
-   Use a unique Document Code (`doc`) for each group of transactions (for example, a GUID).
-   Use a metadata field, such as Invoice Number Reference (`invn`), to create an association between a Document Code and an invoice. This gives you the flexibility to uncommit Document Codes throughout the calendar month, effectively removing these transactions from your committed reports. It also helps reconcile data between your internal billing system and Avalara.
-   Don’t send a Document Code (`doc`) for transactions not intended to be committed, such as quotes. Leave this field empty.
-   Use the Commit endpoint to commit or uncommit a Document Code once the transaction has been submitted. You **can’t** change the commit status of a Document Code through the `CalculateTaxes` API.
-   All committed transactions are locked at the end of the calendar month and can’t be uncommitted or changed. Submit an adjustment to reclaim taxes in future filing periods.