Linking receivables

In the Bling × Koncili integration, the link between order and receivable is 100% automatic — a job runs on its own, once a day, at 01:00 (Brasília time), with no team action.

How it works — the discovery chain

Bling links an accounts receivable to an Invoice (NF-e), not directly to a sale — in practice, every receivable comes from an invoice. The job follows this chain on its own:

1

Open receivable

The job lists the receivables not yet written off in Bling.

2

Resolve the invoice

From the receivable, it finds the Invoice (NF-e) and the originating sale.

3

Resolve the order number

From the sale, it obtains the marketplace order number.

4

Match the Koncili order

It compares against the already-imported order code — avoiding matching orders from different accounts with the same number.

5

Store the link

Done, when the reconciliation is sent, Koncili already knows which receivable to write off.

Rules

Never loses, always retries

The receivable stays "open" in Bling until written off — so it reappears in every daily sweep. A failure (authentication, unavailability) only delays the link, never loses it.

Import start date

When you set the integration's start date, the job fetches from Bling the accounts receivable issued from that date that are still open.

For example, suppose Koncili was hired to reconcile from 2026-07-01 — only orders issued from that date onward are imported into Koncili.

That is why it is important to set this start date correctly, preventing the job from querying orders in Bling that predate when Koncili began reconciling. Those orders will never be available in Koncili and, therefore, cannot be reconciled.

Besides generating unnecessary queries, this can impact the process's performance — especially on accounts with a large volume of orders, resulting in thousands of queries to Bling.

One day per query, with a safety margin

Each query to Bling covers only one day. Koncili stores the last date processed by the job and, on every new run, uses a safety margin of 3 days, by default, to reprocess the previous days. This way, it can identify orders that became available in Koncili after the receivable was issued in Bling.

Safety net — if the job did not link in time

On-the-spot resolution at write-off time

At the moment of the write-off, if the receivable still has no link, Koncili tries to create the link immediately, searching for the matching order in Bling. If the order is found, the link is created before the write-off is sent. If the order is still not located, the write-off fails, returning a document not found error.