Automatic payment matching, which you trigger in the app with a button, can also be invoked via REST API — for both bank and cash register.
Running it
PUT /c/{firma}/banka/automaticke-parovani
The response is <success>true</success>. The call can be repeated — documents that are already matched won't be matched again.
Limiting with a filter
For larger companies, it's worth running matching on only a subset of payments — the filter is inserted into the address before the action name:
PUT /c/{firma}/banka/{filtr}/automaticke-parovani
PUT /c/{firma}/banka/(datVyst%3E='2020-03-01')/automaticke-parovani
PUT /c/{firma}/banka/(datVyst = NOW())/automaticke-parovani
💡 The filter significantly reduces run time — without it, Flexi goes through all payments in the records. Characters in the filter must be encoded, otherwise the request will fail.
Matching parameters
Behavior is controlled by the following parameters:
Parameter | Values |
|
|
|
|
| How large a difference between the payment and the document should be ignored. Default is |
|
|
Example with all parameters:
PUT /c/{firma}/banka/automaticke-parovani?mod=jenVar&obdobi=aktualni&ignorovat-rozdil-castka=1.5&zauctovat-rozdil=true
⚠️ An invalid value for the mod or obdobi parameter results in the 400 error. This differs from a parameter that ABRA Flexi doesn't recognize at all — such a parameter is silently ignored and matching proceeds with the default settings.