Yes. Krokul CRM integrates with PrivatBank through the bank API for business (Autoclient). With a token the client issues, Krokul reads the account statement, finds the company by the payer EDRPOU code and turns the open expected payment into an actual one. The accountant only sorts out the unmatched receipts.
Several times an hour, Krokul reads /api/statements/transactions/interim and takes incoming transactions with TRANTYPE C. By the payer EDRPOU code in AUT_CNTR_CRF, it finds the company, and by the SUM amount and the OSND purpose, it picks the open expected payment of that company deal. The plan becomes an actual payment dated DAT_OD, and the deal feed shows which bank payment brought the money.
The bank advises identifying a payment by the REF and REFN pair. Krokul stores this pair as the external key of the payment and checks it before every write, so reading the same statement again creates no second payment.
If the payer EDRPOU code is not found among companies or the amount matches no plan, the transaction goes to the «Unmatched receipts» list. The accountant picks the deal by hand, and Krokul remembers the EDRPOU code for that company, so the next payment from the same payer lands on its own.
When the client has paid part of the invoice, Krokul records an actual payment for the SUM of the transaction and keeps the rest of the plan open. The manager sees on the deal card how much is still due.
Each actual payment from the statement fires the Krokul webhook payment.received, and when receipts cover the deal invoice in full, Krokul sends invoice.paid once. An accounting program or a team chat can listen to these events.
| PrivatBank | Direction | Krokul | When |
|---|---|---|---|
| Statement transaction (TRANTYPE C): SUM, OSND, DAT_OD | PrivatBank → Krokul | Actual deal payment | Krokul polls /api/statements/transactions/interim on a schedule |
| Payer EDRPOU code AUT_CNTR_CRF | PrivatBank → Krokul | Deal company | While the transaction is matched |
| REF and REFN pair | PrivatBank → Krokul | External key of the payment | After the payment is recorded |
| Transaction with no match | PrivatBank → Krokul | «Unmatched receipts» list | When no company or plan is found |
Final statement (/final) | PrivatBank → Krokul | Check of the payments for the previous day | Once a day |
payment/api-readList with openPlans: true.payment/api-create with the deal cardUuid, and store the REF and REFN pair on the payment through externalRef/api-set, so a repeated read gives no second payment.payment.received and invoice.paid, so accounting or a team chat gets the event. Each delivery carries the x-crm-signature header, which you check with your secret.Only read the statement through the Autoclient API with the token you issued. Krokul creates no payments, and a deleted token stops the statement reads.
A few minutes after the transaction appears in the bank interim statement. Krokul polls the statement on a schedule and keeps to the bank advice of at most one request per second.
Krokul puts it in «Unmatched receipts». The accountant picks the deal by hand, and Krokul remembers the payer for next time.
Yes. In the payment register, the accountant marks the expected payments seen in the statement and records them with the «Actuals from statement» button.
Krokul works with PrivatBank only through the bank API and within the rights of the token the client issued. It reads the statement and creates no payments. The bank sends no events about new transactions and advises at most one request per second, so Krokul polls the statement on a schedule.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
PrivatBank and Privat24 are trademarks of their owner. Krokul is not affiliated with PrivatBank.