Overview

The Ramp integration connects your Ramp corporate spend platform to Accounting Seed, automatically syncing card transactions, bills, and employee reimbursements as accounting records in Salesforce. This article walks you through the one-time setup: creating a Ramp developer app, entering credentials in Salesforce, establishing the accounting connection, configuring sync settings and default GL accounts, and scheduling the sync pipelines. Ramp supports only one active accounting connection at a time, so if your Ramp account is currently connected to another accounting integration, do not proceed. Contact Accounting Seed Support for the migration path before establishing the connection.

In this article:

• Prerequisites
• Step 1: Set up 3 GL Accounts
• Step 2: Create a Developer App in Ramp
• Step 3: Enter Credentials in Salesforce
• Step 4: Test the Connection
• Step 5: Establish the Accounting Connection
• Step 6: Set up Custom Fields (GLAVs) & Sync Values to Ramp
• Step 7: Review Default Ramp Sync Settings
• Step 8: Assign Default GL Accounts
• Step 9: Schedule the Sync Pipelines

Prerequisites

1. In Ramp, ensure you have admin access to your Ramp dashboard, specifically the Company > Developer area at app.ramp.com.
2. In Salesforce:
   1. Ensure your org is on the Spring '26 release of Financial Suite with version 3.392 or later (this is the minimum release version required). To find which version you're currently on, review this article.
   2. Install the ASRamp managed package; install links are available on the Product Installation Links article for sandbox and production orgs.
   3. Ensure these Remote Site Settings are active: https://api.ramp.com (production) or https://demo-api.ramp.com (sandbox).
   4. Assign the Ramp Admin permission set to the user performing setup. This grants access to the Ramp Home tab and the integration fields added to Accounting Seed objects.

Step 1: Set up 3 GL Accounts

You will need three GL Accounts designated for the integration before transactional pipelines can run. You will assign them in Step 8, but make sure you have these GL Accounts ready:

GL Account	Required?	Purpose	Expected Type
Ramp Card Clearing	Required for card transactions	Credit side of every card transaction Journal Entry. Represents the outstanding balance owed to Ramp. Nets to zero when the card statement is paid via bank reconciliation.	Balance Sheet (Liability)
Ramp Bill Payment Bank	Required for bill and reimbursement payments	Bank or cash account credited when a paid bill or reimbursement posts a Cash Disbursement.	Balance Sheet (Assets, Bank/cash) Ensure "Bank/Credit Card Account" is checked.
Ramp Suspense	Optional	Fallback expense account for transaction or bill lines with no GL coding in Ramp. Without it, uncoded lines fail instead of posting.	Expense

Step 2: Create a Developer App in Ramp

The integration authenticates with Ramp's API using OAuth 2.0 client credentials. In this step, you create a developer app in Ramp, grant it the scopes the integration requires, and then copy the Client ID and Client Secret.

1. As a Ramp admin, log in to your Ramp account and navigate to Company > Developer.
2. Click Start Building.
3. Enter a name for the app, for example, Accounting Seed Integration, and accept the Terms. Click Create app.
4. When prompted enter the MFA code.  Then under My Apps click the Accounting Seed Integration app (or what you named it in the previous step).
5. Under Grant Types, click Add New Grant Type and select Client Credentials.
6. Important: Copy the Client ID and Client Secret and store them securely. The Client Secret is displayed in full only at creation time.
7. Under Scopes, click Configure Allowed Scopes and select all of the following then click Set after selecting the above scopes.

Scope	Used For
accounting:read	Reading the accounting connection and chart-of-accounts data in Ramp
accounting:write	Pushing GL Accounts and custom fields into Ramp
bills:read	Reading bills and bill payments for sync
bills:write	Updating bill sync state
reimbursements:read	Reading employee reimbursements for sync
reimbursements:write	Updating reimbursement sync state
transactions:read	Reading Ramp card transactions for sync
vendors:read	Reading Ramp vendor records
vendors:write	Linking and syncing vendors

Step 3: Enter Credentials in Salesforce

1. In Salesforce, navigate to Ramp Home (App Launcher > Ramp Home). Here, you'll see Finish Setup wizard at the top.
2. Click the 'Connect to Ramp' step OR the Configure button (top right).
3. In the Setup and Configuration window's Authorization tab, enter the fields as listed below:

Field	What to Enter
Developer Name	An API name with no spaces (for example, Acme_Corp). This value cannot be changed after the record is saved.
Label	A display label (for example, Acme Corp Ramp Credential).
Client ID	The Client ID copied from your Ramp developer app.
Client Secret	The Client Secret copied from your Ramp developer app.
Token URL	For production: leave the default: https://api.ramp.com/developer/v1/token For a sandbox: https://demo-api.ramp.com/developer/v1/token
API Base URL	For production: leave the default: https://api.ramp.com For a sandbox: https://demo-api.ramp.com
Scopes	Paste this scope string: transactions:read accounting:write accounting:read vendors:read reimbursements:read reimbursements:write bills:read bills:write vendors:write
Active	Select this checkbox.

4. Click Save Configuration. A confirmation message with a Deployment Job ID displays. Do not click Done yet.
5. Wait a few seconds, then refresh the page. The credential saves through an asynchronous process and is live within seconds. Do not click Done yet.

Important: Exactly one credential record may be marked Active at a time. The package includes an empty, inactive record named Default. Leave this record untouched.

If you see "No active Ramp credential found" or "Multiple active Ramp credentials found," review your records under Setup > Custom Metadata Types > Ramp Credential and ensure only one record has Active selected.

Step 4: Test the Connection

1. If you're not on Ramp Home, click the Configure button.
2. On the Setup and Configuration window's Authorization tab, click Test Connection.
3. On success, the message "Connection successful! API responded with status 200." displays, indicating that the credential, scopes, and network path are all working as required.

If the test fails, see Ramp Integration Troubleshooting (coming soon).

Step 5: Establish the Accounting Connection

Important:

• Ramp supports only one active accounting connection at a time. If your Ramp account is currently connected to another accounting integration, do not proceed. Contact Accounting Seed Support for the migration path before establishing the connection.
• Never use Ramp's manual Export button once the accounting connection is established. The Export button marks items as synced inside Ramp without sending them to Accounting Seed, causing those records to be permanently skipped by the integration.

To establish the connection:

1. If you're not on Ramp Home, click the Configure button.
2. On the Setup and Configuration window's Authorization tab, click Establish Accounting Connection.
3. On success, the Connection ID displays and the Accounting Connection Status (at the bottom) changes to Connected to Accounting Seed.

This step:

• Registers Accounting Seed as the accounting provider on your Ramp account.
• Automatically creates four GL Account Variable custom fields in Ramp (GL Account Variable 1–4).

Step 6: Set up Custom Fields (GLAVs) & Sync Values to Ramp

In this step you will create the four field "containers" for GL Account Variables 1–4. They are represented in Ramp as custom fields.

Note: The Custom Fields tab requires a saved credential. If you haven't completed Step 2 yet, the tab shows "Configure your authorization credentials first to access custom field management."

1. From Ramp Home > click the Configure button > Setup & configuration window > select the Custom Fields tab.
2. Review the Custom Fields in Ramp section:
   1. If it shows the 4 GL Variables mapped to their respective Ramp custom fields, this was done automatically when you clicked Establish Accounting Connection; skip to step 3.
   2. If this section is empty, click Create Accounting Fields. On success you'll see "Custom field(s) updated successfully." This can be re-run as existing fields are not duplicated.
3. Optional: Rename a field: the Name and Display Name columns are editable inline. Double-click a cell, change the value, and click Save in the table footer.

   1. 

4. Optional: Delete a field: use the row action menu > Delete. You'll be asked to confirm: "Are you sure you want to delete the custom field… This cannot be undone."
   1. Important: When you delete a custom field, your cardholders can no longer select values for it on new transactions. Only delete a field if you are certain it should not be part of your coding surface. If you delete one accidentally, restore the standard setup by running Create Accounting Fields again and re-sync the variable values.
   2. 
5. Once your edits to the Custom Fields in Ramp section are complete, click Sync Accounting Variables to Ramp. This kicks off the sync.
6. Click Done.

You can check this job's progress by going to Ramp Home > Sync Pipelines > Master Data tab. Scroll down to Recent sync runs and check the status in the Accounting Variables card:

Admins can monitor progress under Setup > Apex Jobs > RampFieldOptionsSyncBatch.

Step 7: Review Default Ramp Sync Settings

When you complete Step 6, the system automatically updates your Ramp Sync Settings.  Sync behavior is controlled by a single custom metadata record: Ramp Sync Settings > "Default". 

1. To review the default settings, navigate to Setup > Custom Metadata Types.
2. Next to Ramp Sync Settings, click Manage Records. 
3. Click the label Default and you should see fields and values similar to the screenshot below.  
   1. If you don't see some of the fields, you can add them. To do this manually, go to Setup > Custom Metadata Types > click "Ramp Sync Settings" > scroll down to Page Layouts and click Edit.  Add the missing fields and sections and click Save. 
   2. 
4. Compare the field values to those in the table below.  Note: Make your updates before running any sync pipelines.

Field	What It Does	Default Value
Default Ledger	The Accounting Seed ledger that receives all Ramp activity: Journal Entries, Payables, and Cash Disbursements. Enter the ledger's External Id (preferred) or Name.	Name of default Ledger
Default JE Status	The Posting Status applied to Journal Entries created by the card transaction pipeline. Use In Process to hold entries for review before posting.	In Process
Sync Grouping	This is how card transactions are grouped into Journal Entries. Set this to: Daily to create one Journal Entry per transaction date Accounting Period to create one JE per period.	Daily
Send Sync Acknowledgement to Ramp	Tells Ramp that a record has been successfully synced and clears it from Ramp's ready-to-sync queue.  Production: You must enable this setting before going live. Sandbox: Leave unchecked for testing mode (records import into Accounting Seed but Ramp is never notified, so the same records are pulled again on every sync run).	Unchecked
Vendor Match Requires Payment History	When selected, inbound vendor name-matching only considers Accounts that already have at least one Cash Disbursement. Reduces false matches in orgs with many similarly named Accounts.	Unchecked
Enable Reference Lookup	This is optional and can be set up through the UI - see Ramp Reference Lookup for Matching & Defaulting
Reference Key Template	This is optional and can be set up through the UI - see Ramp Reference Lookup for Matching & Defaulting

5. To make updates, click Default, then click Edit.
6. Make your updates then click Save. Note that changes take effect on the next sync run with no deployment or restart required.

 

Step 8: Assign Default GL Accounts

The Ramp package ships with three user-defined GL Account Defaults that must be populated on the Default GL Accounts page. These accounts determine where card charges, bill payments, and uncoded spend post in Accounting Seed.

1. Navigate to Accounting Home > Setup > Configurations > Default GL Accounts.  Click the pencil icon to edit.
2. Select the same ledger you set as the Default Ledger in Step 6.
3. Assign the GL Accounts created earlier to the respective fields:
   1. Ramp Card Clearing
   2. Ramp Bill Payment Bank
   3. Ramp Suspense
4. Click Save.

Note:

• Default GL Accounts are per ledger. If you change the Default Ledger in Sync Settings later, assign these defaults on the new ledger as well.
• If a required account is not configured:
  • Ramp Card Clearing missing: Card transaction sync fails with an error directing you to assign the account.
  • Ramp Bill Payment Bank missing: Bills and reimbursements create Payables, but the payment phase is skipped until the account is assigned.
  • Ramp Suspense missing: Uncoded transaction lines fail rather than posting to a holding account.

Step 9: Schedule the Sync Pipelines

The Ramp integration includes six sync pipelines: three for master data (GL Accounts, Accounting Variables, Vendors) and three for transactional data (Card Transactions, Bills, Reimbursements). Each is scheduled independently from its card on the Ramp Home tab.

1. On Ramp Home, find the Sync Pipelines section.
2. Select the Master Data tab.
   1. Click Sync Now on the GL Accounts, Accounting Variables, and Vendors cards to send this information to Ramp immediately. This is a prerequisite for the transactional sync.
   2. We recommend scheduling these three pipelines to run once a day so that changes to these records are automatically picked up and sent to Ramp. On the GL Accounts pipeline card, click Schedule, select a frequency (see the table below), and click Save Schedule. The pipeline card displays the active schedule and next run time.

   3. 

   4. Repeat for the Accounting Variables and Vendors cards.

Frequency	When It Runs
Hourly	Every hour, on the hour
Every 6 Hours	At 12 AM, 6 AM, 12 PM, and 6 PM
Daily	Once per day at the hour you select
Weekdays	Monday through Friday at the hour you select

3. Before running the transactional pipelines, ensure that card transactions and reimbursements are coded and marked ready to sync in Ramp's Accounting tab. A card transaction can't be marked ready until it has cleared; bills become ready once approved or paid in Ramp.
4. Click the Transactions tab and set the schedule for each of the three pipeline cards (Card Transactions, Bills, and Reimbursements) to run once a day or more, depending on your business needs.

   1. 

To remove a schedule, click Clear on the scheduler panel. To run a pipeline immediately regardless of its schedule, click Sync Now on any pipeline card.

Note: Pipelines run independently with no required order. You can mix cadences, for example running master data pipelines once daily and transactional pipelines more frequently.

 

Optional next step: Configure Reference Lookup
After completing initial setup, you can configure Reference Lookup, an optional feature that automatically applies GL Account, Vendor, GL Account Variables, Project, and other coding defaults to card transaction Journal Entry Lines during sync, based on a lookup table you maintain. See Reference Lookup for Matching & Defaulting.

 

Related Articles:

• Ramp Integration Overview 
• Run & Monitor Ramp Sync Pipelines
• Ramp Reference Lookup for Matching & Defaulting
• Ramp Integration Troubleshooting 
• Ramp Integration Developer API Documentation 

---

Return to top