Ramp Checking Account Bank Feeds

What are bank feeds?

A bank feed is a complete record of the financial activity for one or more accounts, presented in a format that can be easily ingested by many other software platforms. For instance, Ramp now publishes a bank feed that contains all your Ramp Checking Account transactions: that bank feed can be consumed by many accounting providers, giving you a complete record of your Ramp Checking Account activity in your accounting provider—without you need to upload any CSV files yourself. This speeds up reconciliation, improves accuracy, and gives you clear visibility into your cash position across accounts.

Who can use this?

We offer direct bank feeds integration for Ramp Checking Accounts for the accounting providers QuickBooks Online, QuickBooks Desktop, Sage Intacct, Acumatica, Zoho Books, and Xero. These bank feeds connect through Plaid or Intuit, depending on the accounting provider. By establishing this connection with your accounting software, you can view all transaction data from your Ramp Checking Accounts.

Support for NetSuite is coming soon. Note, Ramp Investment Account activities are not available through bank feeds today. The direct bank feeds integration is only available for Ramp Checking Account(s) and it does not cover activities such as individual card transactions.

Where can I enable bank feeds?

You don’t need to enable anything in the Ramp app. Generally, ERPs will have a Bank Feeds feature to enable, and you can set up the connection from the Banking or Cash Management page.

You can find specific instructions for QuickBooks Online + Desktop, Sage Intacct, Acumatica and Zoho Books below. Video walkthroughs: QuickBooks Online, QuickBooks Desktop, Sage, Acumatica, Zoho Books (Zoho Help Center article)

For Xero, use Xero's bank feed setup flow and select Ramp through Plaid.

Why should you use a bank feed?

Connecting Bank feeds in accounting software automatically imports transaction data, offering several benefits:

• Simplifies reconciliation. By connecting bank feeds, many accounting software solutions will automatically match the bank feed data to your ledger records, allowing you to confirm the accuracy of your books. This allows you to easily reconcile your ledger against the bank statement by confirming that final balances match exactly and that each transaction on one side matches one or more transactions on the other side.
• Saves time by eliminating the need to download statements or manually input transaction data.
• Improves accuracy since bank statement data flows directly from your Ramp Checking Account. This guards against accidental data entry errors.
• Protects against fraud. Even if transactions are omitted from the ledger, bank feeds will expose all activity in your Ramp Checking Account.
• Regular syncs keep your books current.

How to use it?

When using bank feeds for reconciliation, the goal is to match transactions from your bank to existing ERP records. The general flow looks like this:

• From the Accounting > Banking page in Ramp, sync your financial activity into your ERP’s general ledger.
• In your ERP, the bank feed imports recent activity from your connected bank accounts. These items appear as unmatched transactions in your bank reconciliation module.
• The ERP attempts to automatically match imported transactions to records you previously synced from Ramp, based on criteria such as date, amount, and transaction type.
• When a match is found, the ERP will either automatically mark the record as cleared or present the match for you to confirm. If no match is found, you can choose to create a new transaction manually from the bank feed.

It’s important to note that bank feeds do not post directly to your general ledger. Instead, they bring in transactions that must first be matched, reviewed, or approved before they affect your books.

How to avoid duplication?

• Turn off auto-creation of new transactions: Some ERPs allow you to automatically create new entries for unmatched bank feed items. This can lead to duplication if those transactions already exist (e.g., synced from Ramp). Disable this option and review unmatched items manually.
• Rely on matching: Use your ERP’s reconciliation or transaction matching features to clear existing records rather than posting new ones.

How does the direct bank feed differ from the Ramp accounting sync flow?

The accounting sync flow creates new accounting records in your ledger, while the bank feed provides a bank / statement view for matching and verifying those records exist. This is why it's important to disable auto-creation of transactions from bank feeds, otherwise you may duplicate the transactions already synced from Ramp.

Ramp Accounting Sync

• Pushes transaction data from Ramp directly into your ERP's general ledger as journal entries or native objects
• Controlled from within Ramp's Accounting > Banking page

Direct Bank Feed

• Imports raw bank statement data into your ERP's bank reconciliation module through Plaid or other direct integrations
• Does not post directly to your general ledger
• Transactions must first be matched, reviewed, or approved
• Appears as unmatched transactions that need to be reconciled against existing ledger records
• Used primarily for reconciliation to confirm accuracy of your books

Frequently asked questions

Does this replace the need to sync from Ramp Accounting > Banking?

No, this shouldn't replace the need to sync transactions under Accounting. Ramp Checking Account transactions under Accounting will continue to show up as they represent the ledger / book side. The direct bank feed integration represents the bank side and simplifies reconciliation. By connecting bank feeds, many accounting software solutions will automatically match the bank feed data to your ledger / book side records, allowing you to confirm the accuracy of your books. This allows you to easily reconcile your ledger against the bank statement by confirming that final balances match exactly and that each transaction on one side matches one or more transactions on the other side.

To avoid duplication, turn off auto-creation of new transactions as some ERPs automatically create new entries for unmatched bank feed items. This can lead to duplication if those transactions already exist (e.g., synced from Ramp). Disable this option and manually review unmatched items. Also, use your ERP’s reconciliation or transaction matching features to clear existing records rather than posting new ones.

What happens to the transactions recorded for Banking under Accounting in Ramp? Would they continue to show up there with the bank feed connection enabled?

The transactions recorded for Banking remain in the Accounting section of Ramp since those represent records on the "book" side, even if you had set up the direct bank feed connection.

How can I get rid of older transactions there without sending them to my ERP / needing to categorize them?

You can remove any transactions you do not wish to sync over by exporting them all, selecting "Export as" and choose the "Download CSV" option. See this Help Center article for more information.