Settlement Flow and Order Resolution
The settlement and order resolution process represents the full integration lifecycle between Koncili and the ERP:
- Koncili identifies reconciled orders and exposes them via API.
- The ERP polls for available entries/financial titles.
- The ERP processes the data, records the payment, and updates the ledger.
- The ERP sends a confirmation back to Koncili.
- Koncili updates the reconciliation status accordingly.
Workflow Stages
- Polling Pending Entries in Koncili
- The ERP consumes the Financial Integration API endpoint to retrieve titles available for reconciliation (marked as CONCILIED).
- ERP Processing
- The ERP processes the data, applying its internal logic, and records the settlement in the financial/tax modules.
- ERP Confirmation to Koncili
- After recording the event, the ERP notifies Koncili of the final status:
- RESOLVED (transaction reconciled and settled).
- IIf the event is not resolved, the ERP must flag it as "read" via the endpoint to maintain synchronization.
- After recording the event, the ERP notifies Koncili of the final status:
Reconciliation Availability
🕒 When is a reconciliation ready for polling?
Reconciliations are only exposed via the API once Koncili completes the full processing of the Settlement Spreadsheet (PDR - Planilha de Repasse).
This ensures the ERP always receives validated, consistent, and reliable data.
The data becomes available after the following lifecycle is successfully completed:
- PDR Receipt – The marketplace provides the settlement spreadsheet.
- Full Load – The PDR is fully loaded into the Koncili platform.
- Validation – System applies structural (format, integrity) and financial (values, consistency) business rules.
- Data Matching – Financial entries are cross-referenced with existing orders in the database.
- Reconciliation Generation – Koncili initializes records as OPEN; once the analysis is finalized, the status transitions to FINALIZED.
Settlement ENTRIES only become available for lookup at the Financial Integration API endpoint after the reconciliation reaches the Finalized status.
Order and Entry Examples
🛒 Order Example
An order represents the original transaction performed on a marketplace. Below is a simplified breakdown:
| Field | Value | Description |
|---|---|---|
| orderId | PED-12345 | Unique order identifier within Koncili |
| marketplace | Amazon | Sales channel |
| data | 2025-09-10 | Sale date |
| client | João da Silva | Buyer name |
| grossAmount | 100.00 | Gross sale amount (before deductions) |
💰 Financial Entries for an Order
Each order may have associated financial entries representing debits and credits.
| releaseId | Type | Value | Balance Impact | Description |
|---|---|---|---|---|
| REL-1 | SALE | 100.00 | Inflow | Gross sale amount remitted by the marketplace |
| REL-2 | COMISSION | -10.00 | Outflow | Marketplace commission fee |
| REL-3 | SHIP | 20.00 | Inflow | Shipping fee paid by customer and remitted to seller |
📊 Reconciliation Summary
| Field | Value | Description |
|---|---|---|
| orderId | PED-12345 | Unique order identifier within Koncili |
| marketplace | Amazon | Sales channel |
| data | 2025-09-10 | Sale date |
| client | João da Silva | Buyer name |
| grossAmount | 100.00 | Gross sale amount (before deductions) |
In the example above, order PED-12345 consists of:
- Inflows: R$ 100.00 (SALE) + R$ 20.00 (SHIP)
- Outflows: R$ 10.00 (COMISSION)
➡️ Net Reconciled Balance: R$ 110.00
Occasionally, settlement discrepancies may occur—such as cancellations, returns, or commission variances. In these scenarios, the reconciliation will not reach the Finalized status until the entries are fully analyzed, ensuring that only consistent data is transmitted to the ERP.