"No active Ramp credential found" error

No Ramp Credential custom metadata record has Is Active selected.

Navigate to Setup > Custom Metadata Types > Ramp Credential. Open your credential record, select Is Active, and save.

"Multiple active Ramp credentials found" error

More than one Ramp Credential record has Is Active selected.

Navigate to Setup > Custom Metadata Types > Ramp Credential. Deselect Is Active on all records except the one you want to use.

Saving credentials returns "Client ID, Client Secret, and Scopes are required"

One or more required fields on the Authorization tab are blank.

Complete all required fields: Client ID, Client Secret, and Scopes. Click Save Configuration.

Test Connection returns "OAuth request failed with status 401"

The Client ID or Client Secret is incorrect, or the Ramp developer app does not have the Client Credentials grant type enabled.

Verify the credentials in Ramp under Company > Developer > Applications. Confirm Client Credentials is listed as a grant type. Re-copy the values into Salesforce and test again.

Test Connection returns "Connection established but API returned status 403"

The Ramp app token was issued but is missing one or more required OAuth scopes.

Add the missing scope to the app in Ramp under Company > Developer > Applications. Then click Clear Token Cache on the Authorization tab and click Test Connection again.

You saved updated credentials but the connection still behaves like the previous ones

The previous OAuth token is cached and may remain active for up to 48 hours.

Click Clear Token Cache on the Authorization tab, then click Test Connection to force a new token request.

The credential form shows old values immediately after saving

Credential records save asynchronously.

Wait a few seconds, then refresh the page.

The Custom Fields tab shows "Configure your authorization credentials first"

No credential record has been saved yet.

Complete the Authorization tab (enter credentials and click Save Credentials), then return to the Custom Fields tab.

The Custom Fields tab shows "No custom fields found in Ramp"

GL Account Variable custom fields have not been created in Ramp for this accounting connection.

Click Create Accounting Fields on the Custom Fields tab, then click Refresh.

GL Account Variable values appear in the Custom Fields tab but not as options in Ramp after syncing

The variable sync batch job may still be running, or the custom fields did not exist in Ramp when the sync ran.

Check the job status under Setup > Environments > Jobs > Apex Jobs. Once the fields exist and any running job completes, run Sync Accounting Variables to Ramp again.

Accounting Variables sync reports "No Ramp field ID found" error

GL Account Variable custom fields do not exist in Ramp for this accounting connection.

Click Create Accounting Fields on the Custom Fields tab in the Ramp setup app, then re-run the Accounting Variables sync.

A sync pipeline shows a Pending count that never decreases

Records were added since the last run, or a previous sync stopped partway through.

Click Sync Now on the pipeline card. If the count still does not decrease, open the latest Automated Job Results record under Accounting Home > Accounting > Automated Job Results and review the Notes field for per-record errors.

A renamed GL Account still shows the old name in Ramp

GL Account name changes after initial creation are not pushed to Ramp. This is current product behavior.

Edit the account name directly in Ramp. GL Account renames do not flow through the integration after the initial sync.

Duplicate GL Accounts, Vendors, or Accounting Variable options appear in Ramp

Records were created manually in Ramp and also synced from Accounting Seed.

Treat Accounting Seed as the source of truth for master data. Remove the duplicates that were created directly in Ramp.

Sync returns "No active GL Accounts found to sync" error

No GL Accounts in Accounting Seed have the Active field selected.

Activate the GL Accounts you want to sync in Accounting Seed, then re-run the pipeline.

A Ramp transaction does not appear in Salesforce after running the sync

The transaction is not ready in Ramp: it may not be cleared, may not be coded to a GL Account, or may not be marked ready to sync in Ramp's Accounting tab.

In Ramp, open the transaction, code it to the appropriate GL Account, and confirm it is marked as ready for accounting export. Then re-run the sync.

Sync returns "No Accounting Period in Accounting Seed covers date [date]" error

The transaction's accounting date falls in a period that is closed or does not exist in Accounting Seed.

Open the Accounting Period that covers the transaction date, or update the transaction's accounting date in Ramp. Then re-run the sync.

Sync returns "Could not resolve a GL Account for transaction" error

The transaction line has no GL Account coded in Ramp, and no Ramp Suspense GL Account is configured as a fallback.

Code the transaction in Ramp, or assign a Ramp Suspense GL Account under Accounting Home > Setup > Configurations > Default GL Accounts. The suspense account is used only when a line has no coding.

Sync returns "No active Salesforce User matches the employee email [email]" for a reimbursement

The Ramp employee's email address does not match any active Salesforce User record.

Update the Salesforce User's email to match the email registered in Ramp (or update the email in Ramp to match Salesforce), then re-run the sync.

The same records import again on every sync run

Send Sync Acknowledgement to Ramp is not enabled on the Ramp Sync Settings record.

Navigate to Accounting Home > Setup > Ramp Sync Settings. Open the Default record and select Send Sync Acknowledgement to Ramp. Important: Enable this setting only when you are ready for production use. Once enabled, records are marked as acknowledged and will not re-import. Any records already stuck in Pending must be re-synced after enabling this setting.

Records remain in Pending status after syncing

The sync acknowledgement call did not complete, or the setting was enabled after records were already in Pending.

Re-run the affected pipeline. Check the latest Automated Job Results record under Accounting Home > Accounting > Automated Job Results and review the Notes field for errors.

A bill synced to Accounting Seed but no Cash Disbursement or payment records were created

The Ramp Bill Payment Bank GL Account is not configured, the bill has not been paid in Ramp, or the payment date's Accounting Period is closed.

Assign a Ramp Bill Payment Bank GL Account under Accounting Home > Setup > Configurations > Default GL Accounts. If the bill is paid, confirm the payment date's Accounting Period is open. Payment records post to the period of the payment date in Ramp, not the bill date, so ensure the correct period is open. Payment records are created in a separate sync pass and appear on the next run.

A Journal Entry line shows a merchant name but no linked vendor Account

Card transactions do not auto-create vendor Accounts. No existing Account in Accounting Seed matched the merchant name.

Create an Account in Accounting Seed for the merchant or identify the correct existing Account, then re-run the transaction sync. You can also update the Journal Entry line manually. Linking vendor Accounts to transaction lines improves reporting accuracy. For more information, see Run & Monitor Ramp Sync Pipelines.

Sync returns "Default_Ledger__c is not configured" error

The Default Ledger field is blank on the Ramp Sync Settings record.

Navigate to Accounting Home > Setup > Ramp Sync Settings. Open the Default record and set a value in the Default Ledger field.

Sync returns "No Ledger with External Id or Name '[value]' was found" error

The value entered in Default Ledger does not match any existing Ledger's name or External ID exactly.

Open your Ledger records in Accounting Seed and confirm the exact External ID or Name. Update the Ramp Sync Settings record to match exactly.

Sync returns "Multiple Ledgers are named '[name]'" error

Two or more Ledger records share the same name.

Assign a unique External ID to the intended Ledger, then set that External ID as the Default Ledger value on the Ramp Sync Settings record.

Sync returns "No 'Ramp Card Clearing' GL Account is configured" error

The Ramp Card Clearing GL Account default is not assigned on the sync Ledger.

Navigate to Accounting Home > Setup > Configurations > Default GL Accounts for the sync Ledger. Assign the Ramp Card Clearing GL Account. For setup details, see Ramp Integration One-time Setup.

Bills and reimbursements create Payable records but no Cash Disbursement records

The Ramp Bill Payment Bank GL Account default is not assigned on the sync Ledger.

Navigate to Accounting Home > Setup > Configurations > Default GL Accounts for the sync Ledger. Assign the Ramp Bill Payment Bank GL Account. Payment records are created on the next sync run.

A schedule change does not take effect

The previous scheduled Apex job is still referenced.

Reopen the scheduling panel under Accounting Home > Setup > Ramp Sync Settings > Scheduling tab, then click Save to replace the job reference.

Reference Lookup is enabled but no defaults are applied to card transaction Journal Entry Lines

The Reference Key Template is blank, or no Ramp Lookup Reference record's Reference field matches the key computed for the transaction.

On the Reference Lookup tab, confirm the Reference Key Template field is populated. Then open the Ramp Lookup Reference tab and confirm at least one record's Reference field matches the key that would be computed for the transaction (the key is case-insensitive). If no record matches, add one. For setup details, see Reference Lookup for Matching & Defaulting.

A matching Ramp Lookup Reference record exists but the GL Account on the Journal Entry Line is not being replaced

The Override checkbox is not selected on the Ramp Lookup Reference record. Without Override, Reference Lookup fills only empty fields and does not replace an existing GL Account.

Open the Ramp Lookup Reference record and select Override. Because every card transaction expense line always carries a GL Account (from Ramp coding or the Ramp Suspense default), Override must be selected for the GL Account to be replaced. Re-run the card transaction sync.

The card-clearing Journal Entry Line does not reflect the defaults from a Ramp Lookup Reference record

This is expected behavior. Reference Lookup applies defaults only to expense (debit) lines. The card-clearing line is never modified.

No action required. The card-clearing line is intentionally excluded from Reference Lookup to preserve the clearing account balance.

The computed Reference Key contains a stray hyphen or is partially empty (for example, "Starbucks--Coffee")

One of the {token} placeholders in the Reference Key Template resolved to an empty string for this transaction. The integration substitutes a hyphen (-) for any token with no value.

Review the Reference Key Template on the Reference Lookup tab and remove or replace tokens that are frequently empty. Check the raw transaction data in Ramp to confirm which fields are populated for the affected transaction type. Update your Ramp Lookup Reference records to match the keys that are actually being produced.

Changes saved on the Reference Lookup tab do not seem to take effect on the next sync

Reference Lookup settings deploy via a background Queueable job, the same way as the Authorization tab. The new settings are not active until the job completes.

Wait a few seconds after saving, then check Setup > Environments > Jobs > Apex Jobs to confirm the deployment job has finished. Once complete, run the card transaction sync again.