{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/banking-data.sync-ledger/",
    "json": "https://www.anchorterminal.com/niches/banking-data.sync-ledger/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/banking-data.sync-ledger/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/banking-data.sync-ledger/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 12 | 16 | 26 | 14 |\n\n## What counts as done\n\nEvery booked transaction in the window arrives once, with a stable id, amount, date and payee, and pending items are marked as pending; a repeat sync adds only new or changed items through a cursor or date window.\n\nMeasured, for our own tests: the synced balance equals the bank's booked balance after one sync.\n\nHow agents ask for it: sync my bank transactions into my budget; pull last month's transactions into the spreadsheet; import my bank feed every night; backfill a year of history\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **MX Platform API (MX Technologies, Inc.)**: List transactions filters by from_updated_at and to_updated_at for delta sync, pages up to 1,000 records, carries status and a stable guid, and extend_history reaches 24 months where the institution allows; ranges are capped at six months per call.\n- **Powens (Powens SAS)**: Transactions list filters by last_update for changes since the last sync, marks pending items with coming, keeps removed ones with a deleted timestamp, and pages up to 1,000 with explicit pagination.\n- **Tink (Tink AB)**: /data/v2/transactions filters by bookedDateGte, bookedDateLte, statusIn and accountIdIn, pages by token at up to 100, and each transaction has an id, providerTransactionId and BOOKED or PENDING status; account-transactions:modified webhooks give the changed date range.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Akoya (Akoya LLC)**: Transactions take startTime and endTime (default 15 days), offset and limit, and carry status (AUTHORIZATION, MEMO, PENDING, POSTED). There is no cursor or change feed, and acc-14 reports duplicates and missing transactions from Chase via Akoya.\n- **BankMCP (noskillish (open-source project))**: get_transactions takes from/to and follows continuation; ids are entry_reference or a stable fingerprint (issue 10) with booked or pending status. Open issue 18: a bank 429 marks the consent EXPIRED, so repeat syncs can send the person to re-login.\n- **Basiq (Basiq Pty Ltd)**: Transactions filter by transaction.postDate and status (pending or posted), page at 500, and posted ids survive a refresh. Pending transactions get new ids on every refresh, and CDR connections carry no running balance.\n- **Belvo (Belvo Tecnologias Ltda.)**: Recurrent links refresh weekly by default and fire new_transactions_available and transactions_deleted webhooks; transactions filter by value_date and accounting_date ranges. Brazil Open Finance POST retrievals count against monthly per-CPF limits, and refresh-rate changes are priced by sales.\n- **Enable Banking (Enable Banking Oy)**: Transactions take date_from, date_to and continuation_key, with BOOK or PDNG status; entry_reference is immutable but transaction_id may change on refetch. Background reads hit the banks' four-a-day cap (wait 6 hours), and acc-18 saw a Revolut transaction skipped silently.\n- **Flinks (Flinks Technology Inc.)**: /GetAccountsDetail returns Days90 or Days365 of transactions with TransactionId, Date, Debit, Credit and Description, but in one unpaginated payload with no cursor; nightly refresh works only where the bank needs no MFA, and the docs say to plan for partial coverage.\n- **GoCardless Bank Account Data (GoCardless Ltd)**: Transactions come split into booked and pending with date_from and date_to and a last_updated field, but transactionId is optional and bank-set. Accounts show reissued ids duplicating every row (acc-17), unusable pending items (acc-20) and a 4-a-day cap stalling backfill (acc-27).\n- **Plaid (Plaid Inc.)**: /transactions/sync returns added, modified and removed through a cursor, with pending items replaced via pending_transaction_id. History defaults to 90 days unless days_requested is set (acc-32), refreshes bill per call on top of per-Item fees (acc-31), and Chase duplicates are reported (acc-14).\n- **Salt Edge Account Information (Salt Edge Limited)**: Transactions list by account with from_id paging, posted or pending status, a duplicated flag and possible_duplicate in extra. Pending items are removed on every refresh and may return with new ids, and acc-26 hit 403 on connect-session creation for Firefly III.\n- **TrueLayer (TrueLayer Limited)**: Settled and pending transactions are separate endpoints with from and to dates; normalised_provider_transaction_id is stable across requests and running_balance is returned. No cursor, X-PSU-IP is needed to pass the 4-a-day cap, and a 365-day Santander backfill got 403 access_denied (acc-33).\n- **Yapily (Yapily Ltd)**: Transactions take from, before, limit, sort, offset and cursor, with BOOKED or PENDING status and a transaction hash where the bank gives no id. Background reads are capped at four a day, and history past 90 days is often only available in the first five minutes.\n- **Yodlee Core API (Yodlee, Inc.)**: GET /transactions takes fromDate and toDate (30-day default, two years at most) with skip and top paging; each transaction has a unique id and status (POSTED, PENDING and others). There is no cursor, and change detection needs DATA_UPDATES webhooks or /dataExtracts/events in 60-minute windows.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Teller (Teller, Inc.)**: Docs not fetched (robots.txt bars Anthropic agents). acc-36 syncs Chase statements to a sheet, but one 2024 account doesn't establish ids, pending handling or a sync window.\n\n## What stops agents finishing\n\n- bank reissues transaction ids so duplicates arrive\n- four unattended reads a day per account under PSD2\n- a backfill window the bank refuses with 403, read as lost consent\n- per-refresh billing on top of per-connection fees\n\n## Around it\n\nBefore: banking-data.connect-consent. After: spreadsheets.append-rows, accounting.import-bank-feed, personal-finance.categorise.\n\n## Where this comes from\n\nWeight 26 of 100 in Bank data \u0026 open banking: 14 of 41 accounts, the most common job: Actual Budget, Firefly III, Sure, Leggen and spreadsheet syncs on HN and GitHub\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/banking-data.sync-ledger.json, or the MCP tool get_use_case with id banking-data.sync-ledger. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Keep a budget or ledger in step with the bank",
        "url": ""
      }
    ],
    "description": "Keep a budget or ledger in step with the bank: 3 companies fully do it, 12 with a limit, 16 carry the tag. Every listing in Bank data \u0026 open banking with the reason and a source.",
    "facts": null,
    "h1": "Keep a budget or ledger in step with the bank",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/banking-data.sync-ledger/",
    "published": "",
    "section": "agents",
    "title": "Keep a budget or ledger in step with the bank | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/banking-data.sync-ledger/"
  },
  "tokens": {
    "markdown": 1850,
    "slim": 380
  },
  "version": 1
}
