Card Transaction Sync Error: “Account is required”

Overview

You may encounter the following error when syncing card transactions to FENXT:

Card Transaction Syncing Fail with Error: “Account is required.”

This error means that Blackbaud rejected the transaction because a required General Ledger (GL) account was not provided or could not be validated.

Why this happens

Blackbaud requires every card transaction to be associated with a valid GL account. If an account is missing, inactive, or inaccessible, Blackbaud will not allow the transaction to sync.

Common reasons this error occurs include:

• No GL account was assigned to the transaction
• No default account is configured for card transactions
• The referenced account is inactive or archived in Blackbaud
• The referenced account does not exist in Blackbaud - common if a user has added an Account through Ramp instead of using the Refresh Data within the Ramp for FE syncing console.
• The User attempting the sync does not have permission to access the account
• Account security is enabled in Blackbaud and the account is restricted

Resolving the Issue

Follow the steps below to identify and fix the issue.

Step 1: Confirm the transaction has an assigned account

• Ensure the transaction(s) is coded with a valid GL account before syncing.
• If your workflow allows uncoded transactions, confirm a default or clearing account is configured.

Step 2: Verify the account exists and is active in Blackbaud

In Blackbaud Financial Edge:

• Confirm the account:
  • Exists
  • Is active
  • Is not expired or archived

If it does not exist within FENXT, add the code to FENXT, complete the Refresh Data and then attempt to resync.

Step 3: Check API user permissions

If account security is enabled in Blackbaud:

• Confirm the User has access to the account
• The account must be visible and usable by the integration user

Even if the account exists, Blackbaud will reject it if the API user cannot access it.

Step 4: Review default account settings

If accounts are expected to auto-populate, verify defaults are configured for:

• Card transactions
• Vendors
• Projects or classes (if applicable)
• Integration-level settings

Step 5: Retry the sync

Once the account issue is resolved:

• Retry syncing the transaction
• Confirm the transaction posts successfully in Blackbaud

Additional Notes and Considerations

• Blackbaud’s API does not allow transactions without an account, even if they appear uncoded in the UI.
• Card transactions often require at least one distribution line, which must include:
  • Account
  • Amount

Still need help?

If you continue to see this error after completing the steps above, please contact support and include:

• The transaction ID
• The intended GL account
• Confirmation that the account is active and accessible