Skip to main content
Skip table of contents

Fields in a Payment Check transaction

In the header of the transaction the following data is visible:

image-20240801-140551.png

It will mentioned the payment date, amount, number of invoices, batch id etc.

In the detail lines the following data is visible:

image-20240801-140558.png

In the details information can be found if the payment line matches an invoice. There are several checks in here;

Payment line details

  • Bank # matched: the imported bank account number ( = Bnk# import) matches the bank account number known as default in the Onventis application ( = Bnk# WFW).

    • If not checked, the bank account number known as default in the application does not match the bank account number in the payment file or the bank account number is not validated.

  • Bnk# import: the imported bank account number from the payment (proposal).

  • Bnk# WFW: The bank account number set as default in the application.

  • Bnk# in OCR-data: It is an additional check if our regular OCR recognized the bank account number. It does not block the field ‘line approved’ from being checked if this is the only unchecked checkbox.

    • If not checked, the bank account number as recognized by our OCR does not match the bank account number as received from the financial system.

  • No bank # change active: If there is no active change approval open for this bank account number, the box is checked.

    • If not checked, an open change approval for this bank account number (from payment (proposal) is found. Look up the change approval and have it approved following regular procedure.

  • Bank # status: Only a ‘valid’ bank account number cannot blocked the Payment Check. (The line will be approved, but the process itself will mention that a bank account number needs signing)

  • Amount matched: Amount imported ( = Amt imported) matches the amount in Onventis ( = Amt WFW)

    • If not checked, the amount in the payment (proposal) differs from the invoice amount in the invoice in our application.

  • Amount imported: the amount imported from the payment (proposal).

  • Amount WFW: the invoice amount as mentioned in the invoice in the application.

  • Suppl code import: the imported supplier code.

  • Currency Imported: the currency for the payment line as mentioned in the payment (proposal)

  • Currency WFW: the currency for the payment as mentioned in the invoice in the application.

  • Matching transaction found: In the Onventis application a link could be made between payment line and transaction.

    • If not checked, the transaction could not be found based on transaction number.

  • EntrNmbr imported: The entry number imported from the financial system.

  • TranId WFW: this is the record ID (Tran ID) of the matched invoice.

  • Matching transaction approved: An indication is given if the linked transaction is fully approved.

    • If not checked, the transaction is not fully approved (yet).

  • No double payment: only if the payment is not already done, it will not block the Payment Check.

    • If not checked, this invoice is registered in our application as already paid. (fields Amount Paid, Payment Date and Payment processed in section “financial” in invoice. Visible via Archive)

  • Line approved: If all checks are ‘ok’, the line is approved.

    • If not checked, one or more of the earlier mentioned required checkboxes are not checked. After changing the reasons why a certain payment line could not be ‘approved’, re-import the payment (proposal). (For some financial systems, this would mean that a the payment should be proved again.)

  • Supplier: the linked supplier is mentioned

  • Last Approver: the last person who approved the invoice.

Via the ‘i’ in front of the payment line the user can navigate quickly to the linked transaction (it will be opened in a separate tab in the browser).

Please be aware that customizations might be applicable to your application, only the default feature is described in this manual. Please contact your application manager for additional information.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.