Skip to main content

Processing and reconciling bank files

To support account reconciliation, FinDock can read and interpret standard bank files, transforming them into Inbound Report records or Transaction and Transaction Set records for matching.

Depending on the file type, incoming records are matched automatically on ProcessingHub or processed and matched through Guided Matching. This helps speed up reconciliation and eliminate the need for manual intervention.

Supported file types for reconciliation

The table below presents the file types supported by FinDock for reconciliation.

FileNameProcessor - MethodSalesforce RecordAuto-Matched By
ADDACSAutomated Direct Debit Amendment and Cancellation ServiceFinDock - Bacs Direct DebitInbound ReportGuided Matching
ARUDDAutomated Return of Unpaid Direct DebitsFinDock - Bacs Direct DebitInbound ReportGuided Matching
AUDDISAutomated Direct Debit ServiceFinDock - Bacs Direct DebitInbound ReportGuided Matching
Autogiro Mandate AdviceMandate AdviceFinDock - Autogiro direct debitInbound ReportGuided Matching
Autogiro Payment SpecificationPayment SpecificationFinDock - Autogiro direct debitInbound ReportGuided Matching
BGMaxFinDock - Bankgiro ReceivablesTransaction Set and TransactionGuided Matching
Bollettino ReportBollettino ReportFinDock - SEDAInbound ReportGuided Matching
C72Cuaderno 72FinDock - SEPA (Spain)Inbound ReportProcessingHub
Camt.053Bank to Customer StatementFinDock - Autogiro, AvtaleGiro, CH-DD, LSV+, SEPATransaction Set and TransactionProcessingHub
Camt.054*Bank to Customer Debit Credit NotificationFinDock - CH-DD, LSV+, SEPATransaction Set and TransactionProcessingHub
CODACoded Statement of AccountFinDock - SEPA (Belgium)Transaction Set and TransactionGuided Matching
DDICDirect Debit Indemnity ClaimFinDock - Bacs Direct DebitInbound ReportGuided Matching
Input ReportInput ReportFinDock - Bacs Direct DebitInbound ReportGuided Matching
MT 940Message Type 940FinDock - N/ATransaction Set and TransactionProcessingHub
N43Norma 43FinDock - SEPA (Spain)Transaction Set and TransactionProcessingHub
OCROCR GiroFinDock - AvtaleGiro, Giro, etc. (Norway)Inbound Report and Transaction SetGuided Matching
Pain.002Customer Payment Status ReportFinDock - SEPA, SEPA CBIInbound ReportProcessingHub
PlusGirotFinDock - Bankgiro ReceivablesTransaction Set and TransactionGuided Matching

(*) Supported versions: camt.054.001.02, camt.054.001.04

BIC support for MT 940

Extracting information from MT 940 files requires specific parsing rules for specific banks. The rules are applied based on the bank's BIC. For further information, please refer to our MT 940 article.

Upload a bank file for processing

The first step in the reconciliation process is to upload the bank file to Salesforce. This triggers the automated processing in FinDock.

Uploading is done through Chatter, so your ProcessingHub configuration must include a file exchange setup. The file name must not contain empty whitespaces.

caution

Attach only one file per post. Attaching multiple files to a single post may cause errors.

To upload a bank file:

  1. Open the Chatter Group for file exchanges. Chatter Group for payment files
  2. Share a new post and attach the file. Adding text to the post is allowed, but not required.
  3. Click Share to post the file.

The status of the uploaded file can be tracked by taking a look at the auto-generated comments on the post from ProcessingHub or by using ProcessingHub Manager.

Camt.053 and camt.054 with images

In the Swiss market, camt.053 and camt.054 files from PostFinance, the financial services unit of Swiss Post, may include images of ESR (Einzahlungsschein mit Referenznummer) payment slips. The files and images come from the bank in a zip file. When FinDock processes files with images, the images are attached to the corresponding records in Salesforce.

The original images are in TIFF format, so you cannot preview them in Salesforce. However, on the target level, you can change the file format to PNG to preview the file in Salesforce. A very common use case for previewing during the Guided Review process.

To change the CAMT image file format for previewing:

  1. Launch the FinDock app and click Setup.
  2. Click on the ProcessingHub tile to open the ProcessingHub settings.
  3. Click the Target tab.
  4. In the list of targets, click the arrow icon to the right of your SEPA target and select Settings.
  5. For Payslip option field, enter png (or both) and click Save.

Automatic matching on ProcessingHub

ProcessingHub fetches an uploaded file and starts processing it automatically. For file types (excluding CODA and OCR) transformed into Transaction Set and Transaction records, FinDock automatically matches entries based on the End-to-End Id or payment reference (Final Payment Reference on Installment).

File-based reconciliation

When FinDock finds an installment, FinDock handles the incoming record based on ProcessingHub settings explained in the following sections. Once the processing is completed, the results are pushed to Salesforce. Unmatched records can be further processed via Guided Matching.

Other file types, such as CODA, OCR and those transformed to Inbound Report records, are put to Guided Matching for automatic matching.

Default automatic matching on ProcessingHub

For inbound payment data matched on ProcessingHub, additional criteria determine what action FinDock takes, as outlined in the table below.

Entry*Installment Record TypeAdditional Criteria when References are MatchedRecord Status after ProcessingInstallment Status after ProcessingInstallment Amount Open after ProcessingPayments after Processing
CreditReceivableRecord Amount = Installment Amount OpenMatchedCollected0New payment with Record Amount
CreditReceivableRecord Amount < Installment Amount OpenMatchedPartially PaidInstallment Amount Open - Record AmountNew payment with Record Amount
CreditReceivableRecord Amount > Installment Amount OpenMatchedCollectedInstallment Amount Open - Record AmountNew payment with Record Amount
DebitReceivableRecord Amount = Installment Amount & Installment Status = Collected or RejectedMatchedReversedInstallment AmountNew payment with -1 * Record Amount
DebitReceivableOtherNo MatchN/AN/AN/A
CreditPayableRecord Amount = Installment AmountMatchedReversedInstallment Amount Open + Record AmountNew payment with Record Amount
DebitPayableRecord Amount = Installment Amount OpenMatchedPaid0New payment with -1 * Record Amount
DebitPayableRecord Amount < Installment Amount OpenNo MatchN/AN/AN/A

(*) Entry refers to the bank account transaction - credit is money coming into the account, and debit is money leaving the account.

Transaction amount > Installment amount

If the transaction amount is greater than the installment amount, FinDock takes into account the Overpaid Installment Handling setting. This setting has three options:

  • Manual Review: the transaction is marked for manual review and not processed any further
  • Book all on current: FinDock books the total amount against the current installment, creating one payment for the amount of the installment and a second payment for the remainder
  • Book remainder on next: FinDock creates a payment for the amount of the installment, marks it as collected, and moves to the next installment based on the Multiple Installment Handling setting, creates a payment for the amount of the next installment, marks it collected, and so forth. This continues until the transaction amount is fully booked or there are no more Installments. If there are no more installments and the transaction amount is not yet fully booked, the entire operation is rolled back, and the transaction is marked for guided review.

Transaction amount < Installment amount

If the transaction amount is less than the installment amount, FinDock takes into account the Underpaid Installment Handling setting. This setting has two options:

  • Partially Paid (default): If the transaction has a smaller amount than the installment, FinDock creates a payment for the amount of the transaction and it marks the installment as ‘Partially paid’ rather than Collected.’
  • Manual Review: When the option ‘Manual Review’ is chosen, the transactions are not matched automatically, but rather added to Manual Review.

Multiple installments

If the Payment Reference or End to End Id on the transaction matches multiple installments, the automatic matching flow depends on the Multiple Installment Handling setting. This setting has three options:

  • Manual Review: any transaction that matches multiple installments is marked for manual review
  • Oldest Due Date: FinDock selects the oldest (based on due date) open installment and uses that to match the transaction using the Basic Flow for Debit Transactions (see below).
  • Most recent Due Date: FinDock selects the installment with the most recent due date (which might be in the future) and uses that to match the transaction using the Basic Flow for Debit Transactions.

Batch transaction

If FinDock is unable to locate an installment for the transaction, but it can find a FinDock file record where the group identifier field matches the Payment Reference or End to End Id, FinDock treats the transaction as a batch payment.

If the total amount of the installments connected to the file record matches the amount of the transaction, all the installment are marked as collected and Payment records are created. If the total amount differs or if no installment or file record is found, FinDock marks the transaction for manual review. For more information, see batch reconciliation.

Transaction sub-elements with charges

If a transaction contains transaction sub-elements, these are matched if the parent transaction is matched.

Matching for transaction sub-elements means:

  • A new installment with RecordType ‘Payable’ is created with status ‘Paid’
  • A new payment with a negative amount for the charge is created under the installment.

When transaction sub-element record is set to Matched, the installment and the transaction sub-element are related via a lookup on the installment, allowing you to create comprehensive reports to detail the charged amount per bank. The transaction sub-element contains the originating party. Usually this is provided in the form of a BIC for the charging bank.