Orkesta’s reconciliation engine automatically matches processed payments against bank statement entries and imported ERP records, flagging any discrepancies for manual review. This reduces the time spent on end-of-period close and gives your finance team a clear audit trail for every transaction.Documentation Index
Fetch the complete documentation index at: https://docs.orkesta.com.tr/llms.txt
Use this file to discover all available pages before exploring further.
How reconciliation works
Reconciliation runs in three phases: 1. Import Bank statement files are ingested into Orkesta automatically via the bank connector integration, or uploaded manually in MT940 or CSV format. ERP records can be imported via the ERP connector or uploaded as a CSV export from your accounting system. 2. Match Orkesta compares each statement entry against processed payments using amount, value date, and thereference field. Each potential match receives a confidence score:
| Score | Meaning |
|---|---|
| Exact | Amount, date, and reference all match precisely. Approved automatically. |
| Fuzzy | Two of three criteria match (e.g., amount and date match but reference differs). Requires manual approval. |
| Unmatched | No suitable payment found for this statement entry. Appears in the reconciliation queue for investigation. |
Starting a reconciliation run
Select the account and statement period
Choose the account you want to reconcile and set the statement start and end dates.
Click Run reconciliation
Orkesta imports the latest statement data (if using a bank connector) and starts the matching process. Large periods may take a few seconds to process.
Review matched and unmatched items
The results table shows three sections: Exact matches (auto-approved), Fuzzy matches (needs review), and Unmatched (needs investigation). Filter by section to focus your review.
Approve matches or assign manual mappings
For each fuzzy-matched item, confirm or reject the suggested match. For unmatched items, search for the correct payment and assign it manually, or mark the item as an exception with a note.
Exporting reconciliation results
Export the full reconciliation results from the results page using the Export button. Orkesta supports two formats:| Format | Contents |
|---|---|
| CSV | All matched, fuzzy, and unmatched items with amounts, dates, references, and match scores. Suitable for import into accounting systems. |
| Formatted reconciliation report with summary totals and exception list. Suitable for audit files and sign-off. |
Via API
Retrieve reconciliation results programmatically using theGET /reconciliation endpoint.
Automatic reconciliation accuracy improves when you populate the
reference field consistently in every payment. Exact matches require a reference that aligns with the statement entry — without a reference, Orkesta falls back to amount and date matching, which increases fuzzy and unmatched rates.