Add the payments section
This actually should be the “payments and receivables” section, however
this is quite a mouthful; a “receivable” is a payment made **to** you,
therefore “payments” is ok.
In fact, there is still no receivables in there, as they should be in
a separate relation, to constraint them to invoices instead of expenses.
It will be done in a separate commit.
Since this section will be, in a sense, sort of simplified accounting,
i needed to introduce the “payment account” concept. There is no way,
yet, for users to add them, because i have to revamp the “tax details”
section, but this commit started to grow too big already.
The same reasoning for the attachment payment slips as PDF to payment:
something i have to add, but not yet in this commit.
2024-08-10 02:34:07 +00:00
|
|
|
{{ define "title" -}}
|
|
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.PaymentForm*/ -}}
|
|
|
|
|
{{( pgettext "New Payment" "title" )}}
|
|
|
|
|
{{- end }}
|
|
|
|
|
|
|
|
|
|
{{ define "breadcrumbs" -}}
|
|
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.PaymentForm*/ -}}
|
|
|
|
|
<nav data-hx-target="main" data-hx-boost="true">
|
|
|
|
|
<p>
|
|
|
|
|
<a href="{{ companyURI "/" }}">{{( pgettext "Home" "title" )}}</a> /
|
|
|
|
|
<a href="{{ companyURI "/payments"}}">{{( pgettext "Payments" "title" )}}</a> /
|
|
|
|
|
<a>{{( pgettext "New Payment" "title" )}}</a>
|
|
|
|
|
</p>
|
|
|
|
|
</nav>
|
|
|
|
|
{{- end }}
|
|
|
|
|
|
|
|
|
|
{{ define "content" }}
|
|
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.PaymentForm*/ -}}
|
|
|
|
|
<section data-hx-target="main">
|
|
|
|
|
<h2>{{ template "title" . }}</h2>
|
|
|
|
|
<form method="POST" action="{{ companyURI "/payments" }}"
|
2024-08-11 22:08:18 +00:00
|
|
|
enctype="multipart/form-data"
|
Add the payments section
This actually should be the “payments and receivables” section, however
this is quite a mouthful; a “receivable” is a payment made **to** you,
therefore “payments” is ok.
In fact, there is still no receivables in there, as they should be in
a separate relation, to constraint them to invoices instead of expenses.
It will be done in a separate commit.
Since this section will be, in a sense, sort of simplified accounting,
i needed to introduce the “payment account” concept. There is no way,
yet, for users to add them, because i have to revamp the “tax details”
section, but this commit started to grow too big already.
The same reasoning for the attachment payment slips as PDF to payment:
something i have to add, but not yet in this commit.
2024-08-10 02:34:07 +00:00
|
|
|
data-hx-swap="innerHTML show:false"
|
|
|
|
|
data-hx-boost="true">
|
|
|
|
|
{{ csrfToken }}
|
|
|
|
|
|
|
|
|
|
{{ template "select-field" .PaymentAccount }}
|
|
|
|
|
{{ template "input-field" .Description }}
|
|
|
|
|
{{ template "input-field" .PaymentDate }}
|
|
|
|
|
{{ template "input-field" .Amount }}
|
|
|
|
|
{{ template "tags-field" .Tags }}
|
2024-08-11 22:08:18 +00:00
|
|
|
{{ template "file-field" .File }}
|
Add the payments section
This actually should be the “payments and receivables” section, however
this is quite a mouthful; a “receivable” is a payment made **to** you,
therefore “payments” is ok.
In fact, there is still no receivables in there, as they should be in
a separate relation, to constraint them to invoices instead of expenses.
It will be done in a separate commit.
Since this section will be, in a sense, sort of simplified accounting,
i needed to introduce the “payment account” concept. There is no way,
yet, for users to add them, because i have to revamp the “tax details”
section, but this commit started to grow too big already.
The same reasoning for the attachment payment slips as PDF to payment:
something i have to add, but not yet in this commit.
2024-08-10 02:34:07 +00:00
|
|
|
|
|
|
|
|
<footer>
|
|
|
|
|
<button class="primary" type="submit">{{( pgettext "Save" "action" )}}</button>
|
|
|
|
|
</footer>
|
|
|
|
|
</form>
|
|
|
|
|
</section>
|
|
|
|
|
{{- end }}
|
