Fetch transactions with the Bridge

With Omoplata Bridge you fetch the transactions of your bank account directly from your computer - without downloading a bank statement and uploading it to Omoplata. The fetched transactions are passed on to Omoplata automatically; there, payments are matched and returned direct debits are recognised. You can start in Omoplata or right in the Bridge.

Two ways to the same fetch

In both cases you fetch the transactions in the Bridge, and afterwards they appear in Omoplata by themselves.

1. Fetch from Omoplata

1. In Omoplata, open Finance > Bank transactions.
2. Click Fetch transactions at the top. If your club has several bank accounts, the button also carries the name of the account.
3. Omoplata reports Request sent and shortly afterwards Open in the Bridge. The Bridge comes to the front on your computer and shows the account, with a note saying who asked for the transactions in Omoplata.
4. Click Fetch transactions in the Bridge. If your bank asks for an approval, confirm it with your TAN method.
5. The Bridge reports how many new transactions were sent to Omoplata - or Up to date if there are no new ones.

Omoplata reloads the list of bank transactions by itself and reports New bank statements were imported.

2. What Omoplata does with the transactions

As soon as the transactions have been passed on, Omoplata works through them by itself - just as with an uploaded bank statement:

• Incoming payments are matched to the right invoices. Whatever cannot be matched unambiguously is listed under Needs review.
• Returned direct debits are recognised by Omoplata from the end-to-end ID of the original direct debit and processed automatically.

An example: Jana has sent a file with ten direct debits. Two of them come back - one for insufficient funds, one because the account was closed. After the fetch the following happens without any further action:

1. Both returned direct debits are listed under Bank transactions, each with the bank's reason.
2. Under SEPA Files the file shows 2 returned and the outstanding amount.
3. The two affected invoices are set to Pending retry - they wait for the next collection. The other eight stay untouched.
4. The affected members automatically receive an email, and a processing fee, if one is configured, is added to the invoice.

Collect again

1. Under Finance > SEPA Files, click Create Bank Submission.
2. Open the Retries tab. It lists the returned invoices with the last error, for example Insufficient funds in the account.
3. Select what should be collected again and create the file.
4. Send it as usual - see Send direct debits with the Bridge.

Sort out beforehand what can be sorted out: with a closed account the member first needs new bank details. More on this under Handle failed payments.

Fetch directly in the Bridge

You do not have to open Omoplata.

1. Click Bank statements in the Bridge. Each of your club's bank accounts is listed there with its latest transactions and the time of the last import.
2. Click Fetch transactions next to the account.

New transactions are passed on to Omoplata immediately and processed there as if you had started in Omoplata: payments are matched, returned direct debits are created.

When something does not go smoothly

• Fetched, but not sent yet: Omoplata could not be reached at that moment. The transactions are kept encrypted on your computer; with Send again you pass them on afterwards.
• The bank rejects the fetch: The Bridge shows what the bank's message means. If you changed your username or PIN, click Log in at the bank again under Settings › Bank connections › Change.
• A transaction is missing: Banks only deliver transactions once they are booked. Fetch again later - nothing is imported twice.

Next steps

• Send direct debits with the Bridge - send SEPA files to the bank directly from your computer.
• Handle failed payments - returned direct debits, collecting again and dunning.
• Process SEPA direct debits - the whole collection cycle.