Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically check for proceeds on bank account #1232

Closed
vohmar opened this issue Jun 19, 2019 · 3 comments · Fixed by #1260
Closed

Automatically check for proceeds on bank account #1232

vohmar opened this issue Jun 19, 2019 · 3 comments · Fixed by #1260
Assignees

Comments

@vohmar
Copy link
Contributor

vohmar commented Jun 19, 2019

Implement connection to LHV Connect service and enable automatic balance and incoming transfer checks to mark invoices paid by bank transfer (incl e-invoice standing order) as paid without human interaction.

connection details for LHV test Connect env are in Redmine

Tech spec: https://partners.lhv.ee/en/connect/

If possible rely on Debit Credit Notification service (alternatively there are automatic account statement and account report options).

@vohmar
Copy link
Contributor Author

vohmar commented Aug 23, 2019

test results @ staging - failed

  1. created payment in LHV test: rake dev:create_bank_transactions (success)
  2. created an invoice for a registrar with invoice nr 1, total sum 0.1 and regsitrar's ref nr 13
  3. run rake invoices:process_payments (Transactions processed: 0)

@vohmar vohmar assigned artur-intech and unassigned vohmar Aug 23, 2019
@vohmar
Copy link
Contributor Author

vohmar commented Aug 23, 2019

problem solved - registry iban was incorrect for lhv test to work

@artur-intech
Copy link
Contributor

And it was documented in internal Redmine.

artur-intech pushed a commit that referenced this issue Aug 26, 2019
teadur pushed a commit that referenced this issue Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants