> ## Documentation Index > Fetch the complete documentation index at: https://docs.guito.pt/llms.txt > Use this file to discover all available pages before exploring further. # Bank synchronisation > Set up automatic open-banking sync, manage connections, renew an expired authorisation, or stop syncing an account. Once you connect your bank, guito keeps your accounts and transactions up to date on its own, through open banking. Access is always read-only. guito reads your account balances, your transaction history, and the account holder name and IBAN, but can never move money or touch your funds. You authorise access in your own bank's portal, with your usual credentials, which guito never sees or stores. ## Set up automatic sync For the connection step by step, see [Connect your bank](/en/getting-started/connect-your-bank). Automatic open-banking sync is part of the [Plus plan](/en/account/plans-and-pricing) and is included in the 14-day free trial. On the Free plan you can add your accounts by hand and import transactions from a bank statement. Once an account is connected: * Transactions sync automatically. * Each transaction arrives already named, categorised, and matched to a merchant. * Each account's balance tracks what the bank records on your statement. You don't have to clean up after the bank. If the same transaction arrives more than once, guito shows it only once. Genuine repeat purchases, such as two identical top-ups on the same day, stay as distinct transactions. Each transaction is dated by its booking date, the day the bank recorded it; a separate value date, when the bank sends one, is shown for reference only and never feeds into balances or totals. For how those dates drive your balances, see [how balances work](/en/concepts/how-balances-work). ## How often your data updates Each account refreshes about three times a day while you're using guito, so roughly every 8 hours. If you go a while without opening the app, your accounts refresh less often, but never less than once a day, and they return to the normal rhythm as soon as you come back. Whenever you open guito, it requests a refresh for your accounts if the last one was more than 8 hours ago. You can also refresh whenever you want: on **Connections**, use **Refresh now** in the **⋯** menu on the bank's row to refresh every account on that connection, or open a single account and use the same button on its connection card to refresh just that one. If your bank won't accept more requests that day, we tell you what time the next refresh becomes available. The data isn't real-time. Banks cap how many times a day we may fetch each account (usually 4), so it's normal for a few hours to pass between refreshes, and for a transaction you make right now to show up later. The balance and transactions you see are always the ones your bank reported at the last refresh. ### The first import Until the first import of a newly connected account finishes, the **Activity** section on the Summary shows where it stands: * **Importing and categorising**: the import is running and your transactions will show up shortly. * **Waiting for your bank**: the bank won't take more requests that day (for example, because the same account was refreshed several times). We show the time we'll try again from, and the import carries on by itself. * **The import didn't finish**: something went wrong on the bank's side. We'll try again on our own at the next update. * **We couldn't import your transactions**: the bank connection needs renewing. Use **See connection** and follow [Renew the authorisation](#renew-the-authorisation). ## Manage connections The **Connections** page (sidebar, **Tools** section) gathers all your automatic connections in one place. From here you renew an expired connection or reconnect one that has an error. At the top, the **N connections need you** panel shows only the connections where you have something to do: a connection with an error, an authorisation that has expired or expires within 7 days, or one that hasn't synced for more than 2 days (4 days for a broker, which syncs on its own on weekdays, and 7 days for Edenred, which asks for a code by email on every refresh). Each says why and has the button that fixes it: **Reconnect** for a connection with an error or an expired one, **Re-authorise** for an authorisation about to expire, **Refresh now** for a bank that has stopped syncing and **Update key** for a broker that has, in case the key was revoked. When there's nothing to do, you just see **Everything syncing**. Brokers connected **by email** show up here too: in the panel while a step is still yours (adding the address, confirming in Gmail or setting up your forwarding filter) and, after that, under **Connected**, with the last email received or **Waiting for the first email**. The other connections sit under **Connected**, each with its last sync and, for banks, the days left before the authorisation expires. The other actions (refresh, renew authorisation, disconnect) are in each row's **⋯** menu. If you have two connections to the same bank, the first account's name tells them apart. Connections you disconnected are under **See old connections**. ### Renew the authorisation By open-banking rules, the authorisation you give guito to read your accounts expires periodically (typically every 90 days, though some banks allow longer) and needs to be renewed. When that happens, the account shows a notice asking you to reconnect. You also get email reminders: in the last week before the authorisation expires and, if you let it expire, about 3 and 14 days after. You can turn them off with **Expiring bank connections** in your [email notifications](/en/account/email-notifications); the notice on the account still appears. On the **Connections** page, the expired connection appears in the **N connections need you** panel. Click **Reconnect**. You go through your bank's portal again to authorise access, just like the first connection. Renewing the authorisation does not erase your history. Transactions already synced remain, and automatic sync resumes as soon as the connection is renewed. Transactions you recorded by hand while the connection was expired or suspended aren't imported again, and an account you disconnected on purpose stays manual. ### Stop syncing an account An expired or suspended connection (for example, at the end of the free trial) keeps its accounts automatic and paused, with their history kept. Nothing changes until you decide what to do: * **Reconnect** authorises access again and resumes syncing. If the connection was suspended at the end of a plan, you need the Plus plan to reconnect it: on the Free plan, **Reconnect** shows what the Plus plan includes, and your accounts and history stay saved. * **Disconnect** turns the account manual, so you keep it by hand from then on. From the account's options menu, you can save the current balance as the starting point for the transactions you'll record. From a connection's **⋯** menu on the **Connections** page, it does the same for every account at that bank. ### Limit on connection attempts To avoid repeated requests to your bank, you can make up to 30 connection attempts in any 30-day period. Attempts you didn't finish count too, as do reconnections of expired or suspended connections. You need to wait 2 minutes between two attempts at the same bank. Renewing the authorisation of a connection that is still active doesn't count toward this limit, but it has its own small limit at each bank. ## Related pages The first open-banking connection, step by step. How guito calculates and presents your account balances. How guito identifies and handles transfers between your accounts. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.