The accept button on offer pages sent to customers is pretty confusing when IN is set to German.

While not completely false, “zustimmen“ is clearly the wrong word to use here (it's rather equivalent to “agree”). The button should rather say “Angebot annehmen”. (Please note that using only the verb “Annehmen” would very likely still cause the very same confusion!)

Why does this happen?

I'm always frustrated when I'm trying to use endpoints. Need to do back and forth between codebase and postman.
Is it possible to share a postman collection in json before having the documentation please ?
Thank you!

I think we should have specific documents (invoices, rent notices, letters...) according to the country where the landlord leases properties.
Then we should translate and adapt template documents to the legal rules of each countries.
The number and type of documents can vary. So the menu should be adapted too.

Similar to #798 (Activities) or #545 (Tags) we need to build generic feature Notes & Comments.

For each type of record (e.g. Contacts, Organizations, Employees, Invoices, etc), we should be able to add some notes which will be displayed in like timeline style (i.e. it's a list of notes, most recent notes at the top, oldest at bottom of the list). Note: it is possible that some entities already

For ZF2 we need a new official sample file, this time in english
How you can help:
Download the blanko 506 .odt file as documented, open in libreoffice, translate to english, adjust the dates and export to PDF.
copy the source code for the file generated in the tests (the factur-x file with 506 in it's name) to a new test, update the invoice date to today, translate the positions and by all m

• Features
• Limitations
• Installing
• Getting started
• Some tips, like ways to use other command line tools to e.g. render a range of invoices.

Like

set temp_file (mktemp) && head -n 10 (invoices config get path_invoices) >> $temp_file
invoices render $temp_file

The editing button on individual entries have a hover effect which expands beyond the given width and enables horizontal scrolling.

Make sure if user click on button with year to filter invoices the button is highlighted.

I suggest you to raise moyasar custom exception (for payment requests) instead of base exceptions. It's a really good mechanism for separating user exception and moyasar exceptions. More details about this can be found at python doc.