How to Set Up and Manage the Aplos Integration

Aplos helps nonprofit organisations manage accounting, funds, contributions, and reporting. The Raisely → Aplos integration sends Raisely fundraising activity into Aplos so finance teams can keep donation and fund accounting records aligned.

How the integration works

When connected, Raisely sends supported fundraising transaction data to Aplos. Aplos then uses the integration configuration set by the organisation to determine how that activity should be recorded.

This integration is especially important for organisations that use Raisely Designations and Aplos Purposes. Designations in Raisely represent donor intent or fundraising allocation, while Purposes in Aplos are used for fund accounting. During setup, your team maps Raisely Designations to Aplos Purposes so donations are recorded in the correct accounting context.

Before you begin

Make sure you have the following before connecting the integration:

• An active Raisely organisation
• An active Aplos account
• Permission to manage integrations in Aplos
• An understanding of which Raisely Designations should map to which Aplos Purposes
• Raisely campaigns using the same currency as your Aplos accounting currency

⚠️ Note: The integration does not perform currency conversion. If a Raisely campaign uses a different currency than the organisation's accounting currency in Aplos, amounts may be imported as-is and interpreted in the Aplos currency context.

Connecting Raisely to Aplos

The integration is connected and managed from Aplos, not from Raisely.

1. Log in to Aplos.
2. Go to the Partners area.
3. Find Raisely.
4. Select the option to link or connect your Raisely account.
5. Review the requested permissions.
6. Follow the prompts to authenticate with Raisely.
7. Complete the setup steps in Aplos.

Setup steps in Aplos

After authenticating, Aplos will guide you through the following setup steps.

Step 1: Select a Default Purpose

Aplos requires a Default Purpose as part of the integration configuration. This is a required setup field. However, new or unmapped Raisely Designations are not automatically mapped to the Default Purpose — if a Designation is unmapped, affected imports may fail or queue until it is mapped.

Step 2: Map Raisely Designations to Aplos Purposes

Map each Raisely Designation to the correct Aplos Purpose. This tells Aplos how to record fundraising activity for fund accounting. For example, a Raisely Designation such as "Building Fund" may map to an Aplos Purpose with the same or similar name.

If your Raisely organisation does not have Designations enabled, the setup flow may guide you through enabling or creating Designations as part of the Aplos setup experience.

Step 3: Configure accounting accounts

For each payment provider account (such as Stripe or PayPal), select the relevant asset and expense accounts. This helps Aplos record provider-specific activity correctly.

Step 4: Review and start the integration

Review the summary of your selected configuration. Once everything looks correct, start the integration from Aplos.

Managing the integration after setup

After setup, all configuration is managed in Aplos. From the integration configuration page you can:

• Review and edit your current Designation-to-Purpose mappings
• Review and edit provider account mappings
• Refresh available Purposes, Designations, or account information
• Disconnect the integration

What data syncs

Designations and Purposes

Raisely Designations and Aplos Purposes are central to the integration:

• Raisely Designations represent donor intent or fundraising allocation.
• Aplos Purposes represent accounting allocation.
• The integration uses the mapping between the two to determine how donations are recorded.

Fees, tips, and financial amounts

Raisely and payment providers may represent fees differently depending on the pricing model or payment method.

• Raisely data is used for fundraising context: donor intent, campaign attribution, Designation metadata, donation comments, and transaction references.
• Payment provider data (e.g. Stripe) is used for settlement-level financial truth: gateway fees, net amounts, payouts, and refunds.

⚠️ Note: Where discrepancies exist between Raisely and the payment provider, Aplos should use the payment provider as the financial source of truth.

Multi-currency limitations

The integration does not perform currency conversion. For best results, Raisely campaigns should use the same currency as your Aplos accounting currency.

If a Raisely campaign uses a different currency, Aplos may receive the amount as-is and interpret it within the Aplos organisation's accounting currency — for example, a donation of 100 AUD could appear as 100 in an organisation configured for CAD.

Failed or blocked imports

Imports may fail or be blocked if required configuration is missing. Common causes include:

• A Raisely Designation has not been mapped to an Aplos Purpose
• A new provider account has not been mapped in Aplos
• The Default Purpose has been deleted or is no longer valid
• A currency mismatch or unsupported setup requires review
• Required transaction data is missing or inconsistent

To resolve: review the Raisely integration configuration in Aplos, fix the missing mapping or setup issue, and retry the affected items if retry is available.

Disconnecting the integration

The integration should be disconnected from Aplos. Once disconnected, Raisely and Aplos will stop syncing new activity. You may need to reconnect and complete setup again before syncing can resume.

Troubleshooting