Once your bank is connected, the Bank Integration screen becomes your hub for reviewing, coding, and importing transactions into your Aplos registers — and for hiding the ones that don't belong there. This guide covers both.

Before you can import, you'll need a connected bank. If you haven't set one up yet, start with Bank Integration: Connecting Your Bank.

Getting to your transactions

Go to Fund Accounting → Transactions → Bank Integration, then click Review Transactions on the account you want to work.

Choose the account you want to review. Once you're in, you can switch between your other connected accounts without leaving the review screen.

Reviewing and coding transactions

Work the queue using the tabs at the top:

• All Transactions — view every transaction at any stage.
• Suggested Matches — possible duplicates or transactions that already exist in your register.
• Ready to Import — transactions that have all required fields filled out but haven't been imported yet.
• Needs Input — transactions that still need required fields filled out. Fill these in using the in-line typeaheads without leaving the tab.
• History — all hidden or matched transactions.

For each transaction, set:

• Payee — Aplos auto-populates the payee from the bank data. If it's a new name, importing creates a new contact; if it's an existing contact, type the name to select and confirm the correct record.
• Account and Fund — choose the income or expense account and the fund to code the transaction to. As you code recurring payees, the system learns the pattern and starts pre-filling the account and fund for you.

Always link a transaction to an existing contact when one exists. Raw bank descriptors are often unique, so importing them as-is can spawn duplicate contacts and clutter your contact list.

Splitting a transaction

To allocate one bank transaction across multiple accounts, funds, or tags, click the plus sign (+) to add a split. You can enter split lines as amounts, percentages, or simple math expressions, and Aplos validates that the splits balance to the transaction total before it's ready to import.

Importing

Once required fields are filled, the Import button becomes enabled.

• Import individually — click Import on a single transaction line.
• Import in bulk — from the Ready to Import tab, use the one-click bulk import to bring in the whole tab at once (there's a safe maximum per request). If any rows fail, the partial failures are surfaced so you can retry them.

Imported transactions post to the target register. If you delete an imported transaction from the register later, it returns to the Bank Integration list.

The first pull can take a minute or two. You can leave the screen and come back — data keeps loading in the background.

Matching to existing register entries

If an incoming bank transaction corresponds to something already in your register, Aplos suggests a match and runs a duplicate check (it flags transactions with the same amount within five days before or after). You can:

• Accept the match to link the bank transaction to the existing entry instead of creating a new one.
• Import as new to dismiss a bad suggestion and bring it in as a fresh register transaction without leaving the card.

You can also open Search Transactions to manually look for an existing entry that matches.

Hiding transactions

Not every transaction the feed pulls in should be imported. Hiding moves a transaction off your pending list so it doesn't clutter the screen or get imported by mistake.

When to hide instead of import

Some transactions are better recorded through their own Aplos workflow so tracking and reports stay correct. Hide the bank entry and enter it in the proper place:

• Donations / contributions — Hide these. Record them on the Contribution Deposits page instead. Bank Integration only writes to your accounting registers, so importing a donation here would skip donor tracking and contribution statements.
• Bills (AP) or invoices (AR) — if the payment or receipt is tied to something in Accounts Payable or Accounts Receivable, hide the bank entry and process it through the AP/AR module. You can't link an imported bank transaction to an existing payable or receivable.
• Printed checks — if you print checks from Aplos, they're already recorded. Hide the matching bank entries to avoid duplicates.
• Internal transfers — when money moves between your own accounts (for example savings ↔ checking), import the transfer from one account only and hide it on the other. Pick a rule (for example, always import transfers from checking) and stick to it.
• Credit card payments — a payment appears on both the checking and the credit card account. Import from one side and hide the other. For paying a card balance, the Pay Bill option in the Credit Card Register handles fund splitting more cleanly.

Retrieving hidden transactions

Accidentally hid something? You can bring it back:

1. Click History
2. Toggle to Hidden
3. Click Search to display all previously hidden transactions.
4. Select the item and unhide it.