> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/getting-started/tars/approve-changes.md). # Approve changes TARS suggests Review the changes TARS suggests on cards in the chat, then approve or reject each one. TARS can suggest changes to your transactions, but it changes nothing until you approve them. Each suggestion is a card under TARS's reply in the TARS chat ([Ask TARS](/getting-started/tars.md)). Anyone who can use TARS can approve or reject the cards it makes for them. {% hint style="info" %} If your company has the newer change card, each card shows **Production:** under its title. {% endhint %} ## What TARS can change * Code transaction line items to budget categories. * Write or change line-item descriptions. * Add, replace or clear a transaction's notes. * File a receipt or invoice you attached in the chat as a new transaction. * With the newer card, attach a file from the chat to a transaction that already exists. For any other change, TARS tells you what to change and where in the app. An approved change runs as you, with your permissions, so TARS can't change anything you couldn't change yourself, and only on transactions you can see ([Manage transactions](/transactions/transactions.md)). ## Approve or reject a change These steps are for a card without **Production:**. While TARS writes it, its reply shows **Preparing action...**. 1. Check the card's title and its list of changes, which shows up to 8 and counts the rest, such as **+4 more**. 2. Select **Approve** to make the change, or **Reject** to drop it. After **Approve**, the card shows **Executing action...**, then **✓ Approved** and **Action executed successfully**. After **Reject**, it shows **✗ Rejected** and **Action was not executed**. Each card works once, for 5 minutes. A card already used or older than that shows **Unavailable** and **Already approved or expired**, so ask TARS again. {% hint style="warning" %} If a change fails, a message shows **Failed to approve:** and the card shows **✗ Rejected**. A card that codes several transactions saves them one at a time, so check which ones saved before you ask TARS again. {% endhint %} ## Approve or reject on the newer card TARS says what it found, then puts every change you asked for on one card. **Production:** names the production the change is in. 1. If the card has more than one transaction, untick any you want to leave out. **Select all** and **Clear** tick or untick them all. 2. Select **Approve** to save the ticked changes, or **Reject** to drop the whole card. Neither works while TARS is replying. After **Approve**, the card shows **Saving…**, then a count such as **Saved 2 of 3**, and a badge on each transaction, such as **Saved**, **Left out** or **Failed:** with the reason. **Changed since — not saved** means someone changed the transaction after TARS made the card, so it was left alone. For **May have saved: check it in RollCredits**, check the transaction before you ask again. TARS then says what was saved. After **Reject**, the card shows **Rejected**. The card shows **Expired — ask TARS again** after 30 minutes, and **Replaced by your newer message** if you send a message instead of answering it. ## What a card shows for each change A card's title says what the change does. Its list names each transaction by its vendor, its invoice or receipt number if it has one, and its total, with each field's value before and after. **None** means the field is empty. * **Coding:** each line item shows by number, with its description if it has one, such as **Line 2: Lumber budget code**. A transaction with no line items gets one for its full amount, so it needs an amount first. The newer card can instead split the amount evenly across several, such as **$32.10 · 4101 - Location Fees**. To code transactions yourself, see [Code transactions](/transactions/transactions/code-transactions.md). * **Descriptions:** **Line 1 description** and so on. On a transaction with no line items, approving creates one for each description, splits the amount evenly and leaves them uncoded. * **Notes:** the title starts with **Update the notes on** or **Clear the notes on**. **Notes** shows the whole current and new text, so check that nothing you want to keep is lost. ## File an attached receipt or invoice 1. Attach the receipt or invoice in the TARS chat. 2. Ask TARS to file, record or add it. 3. Check the card, then select **Approve**. The card's list starts with **New receipt transaction** or **New invoice transaction**, with the file name under **File**. With several files in the chat, the name says which one, such as **(file 2 of 3 attached in this chat)**. RollCredits then adds the file as an upload on the Transactions page and reads the vendor, date and amount from it ([Add receipts, invoices and estimates](/transactions/transactions/add-transactions.md)). TARS files only receipts and invoices, never a W-9 or any other document. ## Attach a file to a transaction that already exists {% hint style="info" %} If your company has the newer change card, TARS can also attach a chat file to a transaction already in RollCredits, such as a card charge missing its receipt. {% endhint %} 1. Attach the file in the TARS chat and ask TARS to attach it. "Can you attach this?" is enough: TARS finds the transaction and says which one. 2. Check the card, then select **Approve**. The title starts with **Attach**, or **Replace the file on** when the transaction has a file. **File** shows the current file, or **None**, and the new one. If **No file to upload?** is ticked on the transaction, **No file needed** goes from **Yes** to **No**. * The new file replaces any file the transaction has. When it had none, RollCredits reads the new file and suggests line items, filling in only blank fields. --- # 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://knowledge.rollcredits.io/getting-started/tars/approve-changes.md?ask=&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.