> For the complete documentation index, see [llms.txt](https://tribalfs.gitbook.io/accountant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tribalfs.gitbook.io/accountant/sync-and-sharing/sync-across-devices.md).

# Sync across devices

Keep your phones and tablets in step through your own Google Drive.

**What you'll do:** turn on sync, so the same ledger is on all your devices, and keep a copy in your own Google Drive.

## How it works

* Sync may need [Premium](/accountant/getting-started/premium.md).
* Sync uses **your own Google Drive**. We don't run a server and never receive your ledger.
* Accountant can see only the files it creates or that you open with it, not the rest of your Drive.
* Each device keeps its copy in an **Accountant sync** folder in your Drive. Attachments go in the `.accountant_dont_delete` folder. Don't move or delete these files yourself; the app manages them.
* Devices sync when you open the app, after you change something, and when you pull down on the **Transactions** list. There's no background sync on a timer.

## Turn on sync

1. Open **Settings › Sync across devices** and turn on the switch.
2. Choose your Google account and allow access to Google Drive.
3. If this device already has records and your Drive already has a synced ledger, you'll see **This device already has records**. Choose:
   * **Use the cloud copy:** this device's records are replaced by the ones in Drive. A copy of this device's ledger is saved first, and you can restore it with **Settings › Undo last import** until it syncs.
   * **Keep and combine:** this device's records are added to the synced ledger. This is only possible if both use the same reporting currency.
4. Wait for the first sync to finish.

Repeat on each device, signed in to the **same Google account**.

{% hint style="warning" %}
**Sample data isn't synced.** If demo data is on the device, you'll be asked to **Remove sample data** before syncing starts.
{% endhint %}

## Sync settings

Once sync is on, these appear under **Sync across devices**:

| Setting                  | What it does                                                                                                                                             |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sync over Wi-Fi only** | Don't use mobile data for sync.                                                                                                                          |
| **Device ID**            | A name for this device, such as *Ana's phone*. It's shown in **Synced devices** and to people you share a ledger with, so make it recognizable.          |
| **Synced devices**       | Other devices syncing this ledger, and when each last synced. Tap one to **Remove** it. Its copy in Drive is deleted, but records already combined stay. |
| **Shared ledger**        | Share this ledger with someone who uses another Google account. See [Shared ledger](/accountant/sync-and-sharing/shared-ledger.md).                      |

Tap **Sync across devices** itself to **Change Google account**.

## If two devices change the same record

If two devices change the **same record** before syncing, the most recent change wins for that record. Changes to different records never overwrite each other.

## New phone or reinstall

Install Accountant, turn on **Sync across devices** with the same Google account, and choose **Use the cloud copy**. Your ledger comes back.

## Turning sync off

Turning **Sync across devices** off pauses syncing on this device. Your records stay on the device, and your Drive keeps the last uploaded copy.

## Troubleshooting

| You see                                                  | What to do                                                                         |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| *Sync paused. Tap to give access to Google Drive again.* | Tap it and sign in again.                                                          |
| *Sync paused: …*                                         | Check your connection. The reason is shown after the colon.                        |
| *Couldn't check Google Drive.*                           | Check your connection and try again.                                               |
| A device shows *Hasn't synced in over 90 days*           | Open the app on that device, or remove it from **Synced devices**.                 |
| A device shows *Not combined: …*                         | Usually the devices have different app versions. Update Accountant on all of them. |


---

# 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://tribalfs.gitbook.io/accountant/sync-and-sharing/sync-across-devices.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.