> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-tailored-solution-integration/gumu-sage-intacct-avalara-integration/use-case.md).

# Use Case

In case if Sales Invoice or Sales Credit Memo is further updated; corresponding Avalara transactions will be adjusted and the recalculated Tax will be back updated in Sage Intacct.

For instance,

* Add Sales Invoice with 1 line Item in Sage Intacct and post it. After posting synced Sales Invoice will be added in Avalara, then the calculated Tax from Avalara will be back updated in Sage Intacct.

![](/files/-MdLdqprBn_J1gYeBLSe)

![](/files/-MdLds6IA87EvSvcZbZS)

* Edit the above added Invoice and add one more Line Item or edit the existing line item.

![](/files/-MdLdtrBdswqzGWd63Qo)

* Click on Post button. It will again synchronize to Avalara and Tax will be recalculated which will be back updated in Sage Intacct.

![](/files/-MdLdxdQLguWiReLrgj_)

Deleting Sales transactions from Sage Intacct that are already synced cannot be erased in Avalara through this Integration process. Instead, User would need to manually delete the corresponding transactions from Avalara as and if needed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.greytrix.com/gumu-tailored-solution-integration/gumu-sage-intacct-avalara-integration/use-case.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.