Xero Uses Two Types Of Bank Feed Yodlee And

Xero’s bank feed functionality is the engine that powers its automated reconciliation, transforming the tedious task of manual data entry into a seamless, near-real-time process. At its core, a bank feed securely imports your financial transactions directly from your bank or financial institution into Xero, matching them against your records with remarkable accuracy. On the flip side, Xero utilizes two distinct technological architectures to achieve this: the legacy Yodlee feed and the modern direct bank feed (often powered by Open Banking standards in regions like the UK and EU). Understanding the critical differences between these two feed types is essential for any Xero user, as it impacts security, reliability, data freshness, and the long-term stability of your accounting workflow.

The Legacy Approach: Understanding the Yodlee Feed

The Yodlee feed represents the older, third-party aggregation model. On the flip side, xero partners with Yodlee, a financial data aggregation platform, to connect to your bank. Yodlee then uses these credentials to log into your bank’s website on your behalf, a process often called "screen scraping.Here’s how it fundamentally works: when you set up a Yodlee feed, you provide your online banking login credentials (username and password) directly to Yodlee’s secure system. " It navigates the online banking interface, extracts your transaction data, and transmits it to Xero.

Key Characteristics of a Yodlee Feed:

• Third-Party Mediation: Your data passes through Yodlee’s servers before reaching Xero. This adds an extra layer but also an extra potential point of failure.
• Credential-Based: You must share your bank login details with a third party (Yodlee), which, while encrypted and secure by industry standards, is a less direct method than modern API connections.
• Feed Frequency: Transactions are typically imported in batches, often once or twice a day. You do not get true real-time updates.
• Bank Coverage: Historically, Yodlee’s strength was its vast network, supporting thousands of financial institutions worldwide, including many smaller banks and credit unions that did not have their own API connections. This made it a universal solution.
• Vulnerability to Changes: Because it mimics a human user logging in, any change to your bank’s website layout, login process (like multi-factor authentication updates), or security protocols can instantly break the feed. Yodlee must then update its "scraping" logic, causing downtime until fixed.
• Phasing Out: Due to the global shift towards Open Banking and more secure API-based connections, Xero is actively decommissioning Yodlee feeds in many regions, particularly where Open Banking regulations are in force (e.g., the UK, Europe, Australia). New setups for supported banks in these areas are almost exclusively direct feeds.

The Modern Standard: The Direct Bank Feed (Open Banking API)

The direct bank feed is the present and future of Xero’s connectivity. This leads to it operates on a direct, permission-based connection between your bank and Xero, leveraging secure Application Programming Interfaces (APIs). In regions with Open Banking regulations (PSD2 in Europe, Open Banking in the UK), these APIs are mandated by law, ensuring standardized, secure data sharing.

Continue exploring with our guides on x2 + 13x + 36 and How to Write an Equation of a Line That Is Parallel (The Simple Method Students Are Raving About).

Here’s how it works: During setup, you are redirected from Xero to your bank’s own secure login page. Which means this permission is managed via an OAuth token, which Xero uses to request data from the bank’s API. You then explicitly grant Xero permission to access your transaction data for a specified period (e., 90 days, 1 year). You authenticate directly with your bank (often using your usual login plus a one-time passcode for two-factor authentication). On top of that, g. No bank credentials are ever shared with Xero or any third-party aggregator.

Key Characteristics of a Direct Feed:

• Direct Connection: Data flows straight from your bank’s system to Xero. This eliminates the middleman, enhancing security and reliability.
• Token-Based Authentication: Uses secure, revocable tokens instead of static passwords. You can revoke Xero’s access anytime from your online banking settings.
• Real-Time or Near-Real-Time: Many direct feeds update automatically every few hours, with some offering near-instantaneous imports. This provides a more current view of your cash position.
• Superior Security: Compliant with the highest banking security standards and Open Banking regulations. It is the most secure method of data transfer.
• Stability: Since it uses a formal, documented API, the connection is far less likely to break due to cosmetic website changes. Updates are managed by the bank and Xero at the API level.
• Regulatory Driven: Its adoption is accelerating globally due to regulatory pushes for customer data rights and secure innovation in financial services.

Side-by-Side Comparison: Yodlee vs. Direct Feed

| Feature | Yodlee Feed | **Direct Bank Feed (Open