What are outgoing bank payments?
The "Outgoing bank payments" screen is an outbox of all payment files generated for suppliers. You do not create new payments directly from here — the payments are created on the Purchase invoice screen via the "Generate payment" button. Once a payment is created, it is shown in this overview, and from here you can export it to the bank, regenerate the file, download the payment file's content and view accounting vouchers.
The screen gives an overview of all outgoing payments across organizational units and provides access to the underlying invoices, credit notes and posting vouchers.
How to access the screen
Open Financial and navigate to Accounting, then Outgoing bank payments.
If you cannot see the menu item, you probably do not have permission for it. Contact support.
Relationship with the Purchase invoice screen
Payments are not created from this screen. The flow starts on the Purchase invoice screen, where you select one or more invoices and click Generate payment. The system thereby creates a payment batch and the payment file is associated with the batch. The resulting payment is then shown in the overview here, where you can process, export and follow up on it. Payments are collected in runs (batches). One run becomes one payment file, so payments for different departments or different bank formats each get their own run.
The overview and multi-selection
The overview shows all generated payments in a table view. In addition to clicking a row to focus it, you can select multiple rows using the checkbox in the first column on each row. Multi-selection is used for batch actions, e.g. regenerating or exporting payment files for several runs at once.
Actions
Regenerate payment file
Active when exactly one payment is focused (clicked) in the list. Regenerates the bank payment file for that run via the agent. Use this action if the original file has been lost or needs to be restored for checking.
Regenerate payment file for selected runs
Active when at least one row is selected via checkbox or focused in the list. Regenerates the bank payment file for all selected runs in one operation. Used when you want to regenerate files for several payments at the same time.
Export all unexported payments
Active only when there are payments in the overview that have not yet been exported to the bank. Exports all unexported payments as one bank file via the agent and subsequently marks them as exported. The action is dimmed if all payments have already been exported.
Export selected unexported payments
Active under the same condition as above — there must be unexported payments. Exports only the selected (marked) payments rather than all. Used when you want more granular control over which payments are sent to the bank this time.
Download
Active when at least one row is selected or focused. Downloads the content of the selected payments as a file (CSV, or XML for ISO 20022 (Bankdata)) locally on your computer. After download the system asks: Mark as exported? — if you answer Yes, the payments are registered as exported in the system and the "Exported on" column is updated.
Content
Active only when the focused payment has an associated payment file with content. Opens the Content dialog, which shows the raw XML or text representation of the bank payment file. Used to verify or troubleshoot the file content, e.g. before uploading to the bank.
Refresh
Reloads the overview with the latest data from the system.
The More menu
In the top right there is a More button (three dots or similar) that gives access to four additional actions:
View vouchers is visible and active when the focused payment has associated accounting vouchers. Opens the Voucher summary dialog, which shows the accounting vouchers associated with the payment.
Purchase invoices is visible and active when the focused payment has associated purchase invoices. Opens the Purchase invoices popup, which shows a list of the purchase invoices and credit notes included in the selected payment.
Re-post is exclusively visible to administrator users and active only when the selected payments are already posted (i.e. the posting status is different from "None"). Used to re-post selected payments. This action changes the posting and should only be used with care.
Regenerate in another bank format is active when at least one payment is selected. Used if a payment must be sent to the bank in a different format than the one it was created in (e.g. from a CSV format to ISO 20022 (Bankdata)). The selected payments must belong to one organizational unit - otherwise "Select payments from one organizational unit to regenerate them in another bank format" is shown. Sapera asks you to choose the bank setup to use (see Bank setup) and then creates the file again in the new format.
The system asks for confirmation when it matters: If the run contains more payments than the ones you have selected, you are told that all payments in the run will be regenerated in the new format ("Batch {0} has {1} payments. All of them will be regenerated in the new bank format."). If one or more of the payments have already been exported, the date is shown ("This payment was already exported on ...") together with the question "Send again in the new bank format?", so you do not accidentally send the same payment to the bank twice.
Dialogs and popups
The Content dialog
Opened via the button Content and shows the raw text representation of the bank payment file — typically XML format — in a modal window with pre-formatted text. The dialog is for viewing only and allows you to inspect the exact file content that has been sent or will be sent to the bank.
Purchase invoices popup
Opened via More → Purchase invoices and shows a list of the purchase invoices and credit notes included in the selected payment. Useful for verifying which invoices are covered by a given payment.
Voucher summary dialog
Opened via More → View vouchers and shows the accounting vouchers associated with the payment. Useful when checking and reconciling the posting for a payment.
The filter options
Each column in the overview supports filtering, which is activated directly in the column header:
Run is filtered with a numeric range (from–to), so you can limit it to a specific range of batch IDs.
Supplier is filtered via a supplier lookup, where you search for and select the supplier.
Account from and Account to are filtered with free text on registration number, account number and IBAN.
Created on is filtered with a date range (from–to date).
Invoices is filtered with free text on the invoice ID.
Exported on is filtered with a dropdown with three choices: None (shows all), Yes (only exported) and No (only not exported).
Org. unit is filtered via organizational unit (store/department).
Description of fields
Run: The batch ID (sequence number) for the payment run the payment belongs to. Payment files are generated in batches — this field identifies which batch a given payment belongs to. Sortable; the default sort is descending, so the most recent runs are shown at the top.
Supplier: Name of the supplier the payment is directed to.
Account from: The sending bank account in the format registration number + account number. This is typically the company's own bank account, from which the payment is drawn. If an IBAN is specified on the bank setup, it is shown after the reg. no./account no., separated by a slash.
Account to: The receiving account in the format registration number + account number. This is typically the supplier's bank account. If the supplier is paid via IBAN, the IBAN is shown instead (several IBANs are separated by commas).
Amount: The total payment amount, currency-formatted.
Created on: The date and time (including seconds) when the payment was created in the system.
Invoices: A comma-separated list of the invoice IDs (purchase invoices, manual entries and credit notes) included in the payment.
Exported on: The date the payment was exported to the bank. An empty field means the payment has not yet been exported.
Export format: The bank format the payment file was created in, e.g. Danske Bank, ERH, Jyske, SDC or ISO 20022 (Bankdata).
Org. unit: The organizational unit (store or department) the payment belongs to.
If you have any questions, you are welcome to contact support.
IBAN and ISO 20022 (foreign payments)
Outgoing bank payments support IBAN account numbers with BIC/SWIFT, so you can create payments to foreign suppliers. This uses the bank format ISO 20022 (Bankdata), which is set up on the bank setup (see Bank setup) with IBAN, BIC / SWIFT and optionally Account currency. For each payment, the format requires a valid IBAN and BIC on the purchase invoice, as well as the name and address (postal district and country) of the supplier and of the organizational unit. If anything is missing, an error message is shown and the payment is not created.
If the file cannot be saved: If the agent cannot write the payment file (e.g. because it is not connected), you are notified and the payments still appear as not exported.
Want to know more?
Read more in these related articles:
Outgoing payments
Setup of outgoing payments in Sapera: whether the bank payment file (CSV) should be generated immediately, and whether export lines should be grouped.
Bank setup
How to create and edit bank accounts for outgoing payments in Sapera, including bank format, reg. number, account number, folder and journal.
Payout
This article covers how to create a payout in Pos, including selecting a payment option, entering the amount, offset account, description and attaching a receipt.

