Financeiro Inteligente
Native integration · Read-only (pull) · Syncs automatically every 60 min (configurable) + on demand
Financeiro Inteligente is Kobana's financial management product, with receivables and a people registry. Connected to Dunning, it feeds the collection rule with open receivables — the customers and charges enter your collection operation automatically.
Prerequisites
- A Financeiro Inteligente account with people and receivables.
- An access token for the Financeiro Inteligente API.
How to connect
:::note No dedicated panel screen (yet)
Today only the Kobana Gateway has a ready connect screen in the panel. For this ERP, the connection is made through the API (/api/v1/integrations/... routes) — the steps below describe the authorization flow; the equivalent self-service screen in the panel is on the roadmap.
:::
Financeiro Inteligente uses a static key — you paste a token, with no redirect.
- In the Financeiro Inteligente panel, copy the access token.
- In Dunning, open Settings → Integrations and choose Financeiro Inteligente.
- Paste the access token and select the environment (
productionorsandbox). - Click Connect. Dunning validates the token with a test call; an invalid token is rejected before saving.
- The first sync runs right after connecting; the following ones happen automatically.
Field mapping (source → Dunning)
| Financeiro Inteligente field | Dunning field |
|---|---|
| Receivable | Charge |
amount | Original amount |
nominal_amount | Current amount |
ticket_amount (settled at the bank) | Amount paid |
due_date | Due date |
document_date / created_at | Issue date |
payment_date | Payment date |
document_number / document | Document number |
description (+ installment no.) | Description |
payment_method_kind (bank_billet→boleto, pix→pix, credit_card, ted→transfer…) | Payment method |
Status pending | pending (or overdue if past due) |
Status received | paid (settlement + exit from the collection rule) |
Status cancelled | cancelled |
| Person (customer) | Person in the portfolio |
document_number, name, legal_name | Document, name, legal name |
emails, phones | Person's emails and phones |
Pull-only
The Financeiro Inteligente API does not expose webhooks, so the integration is read-only via pull: Dunning fetches the receivables on the automatic sync (every 60 min by default) and on the manual sync, via the sync button. Each run is idempotent — reprocessing does not duplicate charges. A paid receivable settles the charge and removes it from the collection rule; a cancelled one exits for good. Charges already final locally (paid or cancelled) do not have their amounts overwritten by the source.
What it does not do / limitations
- Does not issue receivables. Creation stays in Financeiro Inteligente.
- Does not write back. It is pull-only: settling or cancelling in Dunning does not change the source receivable.
- No real time. Without webhooks, payments and cancellations appear at most on the next sync cycle.
Disconnecting or reconfiguring
Redo the setup to change the token. To rotate credentials, generate a new token in the source panel and paste it into Dunning; the old one stops being used.
Troubleshooting
- The sync is out of date. Check the interval (default 60 min) and click Sync now.
- A paid receivable did not settle. Since there is no webhook, settlement depends on the next pull — force it with Sync now or wait for the cycle.
- A customer did not appear. The people sync runs alongside the receivables sync; a person with no charge is created when their first receivable is synced.
- A charge appears duplicated. Dunning deduplicates by
externalId(finance:receivable:{id}); a real duplicate only occurs if the same charge comes from another source. - The connection dropped / invalid token. Generate a new token in the panel and reconnect.
Security
The access token is encrypted at rest and is never returned by the API. Every call to the Financeiro Inteligente API is recorded in the integration log, so you can audit what came in and diagnose sync failures.