Product Update: A New and Improved Bank Integration Experience is Here

We’ve upgrading Bank Integration in Aplos to make it easier to connect your bank accounts, review incoming transactions, and keep your accounting records up to date.

Bank Integration has always been designed to reduce manual entry by helping you bring bank and credit card transactions directly into Aplos. With this update, the bank connection experience and the transaction review workflow have been modernized for improved usability.

Note: The new bank integration will appear in customer accounts on a rolling basis over the course of three weeks. If you do not see the new Bank Integration in your account, stay tuned!

See our video overview here

Why we upgraded Bank Integration

We know that keeping your books current depends on accurate, reliable bank transaction data. For many organizations, bank feeds are one of the most important ways to reduce manual data entry, stay on top of reconciliation, and avoid duplicate work.

The previous Bank Integration experience helped customers import transactions, but it also had limitations related to transaction matching, payee names, and connections. The new experience resolves these issues and provides a stronger foundation for future improvements. It is designed to help you spend less time manually entering and checking transactions, while still keeping you in control of what gets imported into your accounting registers.

What’s new in the upgraded experience

You will see a more modern workflow for connecting institutions, mapping bank accounts to Aplos registers, reviewing transactions, and importing them into your books. The experience is designed to make it clearer what needs your attention and easier to move through your transaction list with confidence.

Some of the key improvements include:

• A modernized Bank Integration workflow for connecting banks, managing institutions, and reviewing transactions.
• Smarter transaction matching to help identify possible matches between incoming bank transactions and transactions already entered in your register.
• Clean payee names to help reduce duplicate or messy contact records caused by bank-provided transaction descriptions.
• Support for check numbers, helping with transaction review and matching when check information is available.
• Multi-account connection, so you can select multiple eligible accounts from the same bank during a single connection flow.
• Clear connection health visibility, making it easier to understand when a bank connection needs attention.
• A more guided import process, including clearer required fields before transactions are imported.
• Canadian bank support through Plaid, giving Aplos a better path for supporting Canadian institutions where available.

Transactions still do not post automatically. You remain in control of what gets imported into Aplos. Bank transactions are made available for review, and you choose which transactions to import, match, hide, or manage.

What this means for existing Bank Integration users

If your organization already uses Bank Integration, you will need to reconnect your bank account(s). Please note that Plaid is now the only way to connect your bank to Aplos through Bank Integration.

This one-time reconnect step is required because Bank Integration has been rebuilt on a new technical foundation. Existing bank connections cannot be carried over as-is, so customers with active connections will need to re-link their banks through the new experience.

After reconnecting, Aplos will pull in the transaction data available from your bank. Depending on your financial institution, you may see recent transaction history appear for review. In some cases, this may include transactions you have already imported into Aplos. You should review your transaction list carefully and only import the transactions you need.

Because the amount of historical data available can vary by bank, some customers may see more transaction history than others. Plaid may support up to 24 months of history in some cases, but many banks provide a shorter window, such as around 90 days.

Any transactions you have already imported into Aplos will remain in Aplos. Reconnecting your bank will not remove previously imported transactions from your registers.

Our move from Finicity to Plaid

As part of this upgrade, Aplos is moving to a single provider model with Plaid. This means Finicity is being retired as a Bank Integration provider, and Plaid will be the bank connection provider going forward.

We are making this change so we can provide a more reliable connection experience and continue improving Bank Integration faster. Maintaining two providers adds complexity to product development, testing, troubleshooting, and support. By focusing on one provider, we can invest more deeply in the quality and consistency of the Bank Integration experience.

Most banks are supported by Plaid, and most customers should be able to reconnect successfully in the new experience. However, support can vary by financial institution. If your bank was previously connected through Finicity, you will need to reconnect using Plaid after the update becomes available.

If your bank is not currently supported by Plaid, you can continue using file or manual import as an alternative way to bring transactions into Aplos.

You can check whether your financial institution is available through Plaid here: https://plaid.com/docs/institutions/

How transaction matching works

The upgraded Bank Integration experience can suggest matches between incoming bank transactions and transactions that already exist in your Aplos register. This is especially helpful when you have already entered a transaction manually and want to confirm it against the bank transaction instead of creating a duplicate.

Matching works best when the register transaction exists before the bank transaction arrives. When a bank transaction comes into Aplos, the system checks it against existing register activity and may suggest a match if it finds a strong candidate. You can then review the suggested match and decide whether to confirm it.

It is important to know that matching does not automatically re-check every unmatched bank transaction after the fact. If a bank transaction arrives first and you later create the matching register transaction manually, the system may not connect those two transactions automatically. In that situation, review carefully and dismiss or hide the bank transaction if needed to avoid creating a duplicate.

For the smoothest workflow, we recommend reviewing and importing or matching transactions from Bank Integration first when possible.

How to get started with the new Bank Integration experience

To use the new Bank Integration experience, go to Fund Accounting → Transactions → Bank Integration in Aplos.

If you are connecting a bank for the first time, you will be guided through the setup process. If you previously used Bank Integration, you will need to reconnect your bank account in the new experience.

To connect or reconnect your bank:

1. Open Bank Integration in Aplos.
2. Choose the option to add or link a bank.
3. Search for your financial institution in the secure Plaid connection window.
4. Enter your online banking credentials through Plaid.
5. Complete any multi-factor authentication required by your bank.
6. Select the accounts you want to connect.
7. Map each connected bank account to the correct Aplos register.
8. Review your available transactions and import only the transactions you want to bring into Aplos.

When mapping accounts, the source is the real bank or credit card account, such as a checking account ending in a specific set of digits. The target is the Aplos register where those transactions should be imported. Mapping each account correctly helps keep your books accurate.

The first time you connect or reconnect, it may take a short time for transactions to appear. If the connection succeeds but transactions do not show immediately, give the system a moment to finish loading the available transaction data.

What to expect after reconnecting

After you reconnect, your transaction list may include recent transactions from your bank. Depending on your bank’s available history, this may include older transactions, newer transactions, or transactions that overlap with activity you have already recorded in Aplos.

Before importing, review your transactions carefully. You can choose what to import, match, or skip. Nothing is automatically posted to your register without your action.

If you see transactions that you have already entered or imported, do not import them again. Use the available review options to avoid creating duplicates.

If your bank connection needs attention

Banks may occasionally require you to re-authorize your connection. If this happens, you may see an update or reconnect prompt in Bank Integration. Follow the prompt to re-enter your credentials through Plaid and refresh the connection.

If your bank is not available through Plaid, or if you cannot successfully connect, file/manual import remains available as an alternative way to bring transactions into Aplos.

A better foundation for bank transaction workflows

This Bank Integration update is an important step toward a more reliable and efficient transaction workflow in Aplos. The new experience is designed to make bank connections easier to manage, transaction review clearer, and import decisions more confident.

For existing Bank Integration users, the main action is to reconnect your bank account once the new experience is available. For customers who have not used Bank Integration before, this is a great time to try it and reduce manual transaction entry in your accounting workflow.

To get started, log in to Aplos and visit Bank Integration. Then, follow the prompts to connect or reconnect your bank.