Reconciling statements imported through Yapily
When using Yapily, statement downloads and bank reconciliation follow the standard Continia Banking reconciliation process. Continia Banking imports Yapily statements directly and automatically matches them with posted bank account ledger entries. This article describes the import conditions and reconciliation behavior specific to Yapily, including handling for HSBC and for payments rejected within a batch.
For setup instructions, see Onboarding through Yapily.
Important:
- Only transactions with the status BOOKED that have not been previously imported are included.
- The Date and Amount Matching setting is automatically enabled on the bank account when it's set up with Yapily.
HSBC transaction import
HSBC delivers bank statement data through Yapily in two phases. A transaction may first arrive as provisional, with a later delivery replacing it with a final, confirmed version. For HSBC accounts, a transaction is only imported once it is:
- Settled - the transaction status is BOOKED. Pending or otherwise unsettled transactions are not imported.
- Final - the transaction is confirmed, not provisional. Provisional transactions are not imported; they're picked up automatically once HSBC confirms them.
- Not previously imported - each transaction has a unique identifier. If a transaction with the same identifier has already been imported, it's skipped to avoid duplicates.
As a result, you may notice a short delay between a transaction appearing in HSBC's own systems and it appearing in your Continia Banking bank statement lines.
Automatic handling of rejected payments in a batch
When a payment batch is sent through Yapily, the bank statement can include both the full batch amount and separate lines for any payments that were rejected by the bank. This means that the amount on the statement doesn't immediately reflect only the payments that were successfully processed, which can prevent automatic matching.
To address this, Continia Banking can automatically identify rejected payments, link each rejected statement line to its original payment, and merge the related lines before the matching process begins. As a result, the statement amount reflects only the payments that were successfully processed and can be matched automatically like any other transaction.
To enable automatic handling of rejected payments:
- Search () for and select Banking Import Setup.
- In the Yapily section, select the Populate Payment Information id checkbox.
- Additionally, select the Merge by Payment Information id checkbox.