1b.app
Link copied -

Tightened 2 extra payments from private

Here is an extract in the CRM on the card
https://vzutik.crm-onebox.com/admin/shop/finance/?contractorid=&accountid%5B... =&filternobalance=&filteruserid=&filterdirection=0&filterdocumentid=&filtercode=&filterbankdetail=&filter_custom_nalozhka1=&ok=%D0%A4%D0%B8%D0%BB%D1%8C%D1%82%D1%80%D0%BE%D0%B2% D0%B0%D1%82%D1%8C
Highlighted in the carousel square - correct

and those 2 payments that are at the top - they are not in private, that is, physically such payments did not exist. Why did it happen ? There is also a payment code. Can you check what private api gave? To understand on whose side the mistake is and do something about it.
Since it takes a lot of time to look for extra payments, and this is already 2-3 times a month
Original question is available on version: ru

Answers:

Good afternoon. Boxing physically cannot create a payment, come up with a name for it, add an amount from the ceiling and add someone's full name. That is, if you see a payment in the box, someone created it. In this case, most likely it was created by the payment import action (payments have codes, in my opinion, payments with handles cannot be created with codes). If an action created a payment, then it received information about it at a certain moment when it was launched. Now this payment may no longer be in the search results, but this does not mean that it was not there at the time of its creation (5 days ago, for example). In order to prove to the private that he is paying extra payments (if this is true), you need to put logs and record each request and response from the private. If you are good at programming, you can do it yourself on a separate server and request a list of payments every hour. If not, we can do it in 2 hours of revision. Those. we will put the logs, wait for you to show the extra payment and give you the request that we sent and the response that we received with information about this payment.
31.05.2022, 11:51
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment