Payment orders — system description

Overview

Payment order basket: an invoice is added with a row action of the Invoices list (with source and target account, amount, value date); items not tied to an invoice (wages, tax, other) can also be added. From the selected items a giro file (HCT XML or Erste Electra .HUF) is generated per client into the document centre, together with an outgoing draft transaction that the bank import recognises from the reference.

Data model

Table names carry the installation's own prefix in the database.

Process

1. Adding an invoice: amount = outstanding amount minus the unreleased retention; target account from the document, otherwise the partner's active default account in the currency; source is the client's default account; value date is the due date.
2. Item without invoice: title, amount, target account, remittance information.
3. Bulk value date: for the selected items the invoice due date or a fixed date.
4. Third-party reimbursement: payee_kind = third, title reimburse, amount defaults to gross, note with the payment method's name; the cash and card restriction deliberately does not apply here. Invoice, payee name and account are required; customer invoices are refused.
5. Generation: selected items grouped by batch key (client + debit account + currency + value date); netting per partner (credit note as a negative item, a partner with non-positive net is left out) or one transfer per invoice according to the client setting; a unique batch reference with client identifier and timestamp; HCT XML or Electra .HUF (HUF only); filing by the client's storage rule (document, otherwise invoice); batch header written, items set to status 1 and linked to the batch; an outgoing draft transaction through the idempotent batch handler of the finance/transaction model.
6. Delete: the selected, still open items are physically deleted.

Rules and validation

• Adding an invoice is refused for: cash, card or deduction payment method; an already settled invoice (absolute outstanding at most 0.5); an open item for the same invoice; a customer invoice with a positive amount (only an overpayment refund is allowed); zero amount; missing target account (with the partner's name); missing source account.
• Only items with status 0 can be changed.
• Generation errors: an item of a cash or card invoice, Electra in a currency other than HUF, a partner without a target account, a missing storage rule.
• Saving the merge mode fails with a message if the settings table migration has not run.

Permissions

• Layer 1: saving the merge mode and generating also require modify permission.
• Layer 2: list (also the page), edit (add, edit, value date, merge mode), reimburse, export, delete, debug.
• Layer 3: at every endpoint the client must be one of the user's permitted companies (filtered in the model query); reimbursement filters on the invoice's client.

Related processes

Finalising the bank import matches the bank debit with the generated batch and marks the invoice as settled by bank.

Known limitations

• The payee account helper of the reimbursement returns the bank account of the given company without a content scope check.