A collection batch groups together several outstanding amounts owed by customers so they can be submitted to the bank in a single file.
For example, we can prepare a collection batch with the monthly mooring invoices for several customers and generate the file we will use to request payment.
Creating the collection batch or generating the file does not mean that the money has already been collected. We must then process it with the bank and check the result.
Go to:
TREASURY → COLLECTION BATCHES
From the list, we can view the description, date, total amount, and status of each collection batch. We can also filter by status and open a batch to review its invoices.
The Collection Batches feature must be enabled for the company. The actions available also depend on the user's permissions.
Before generating the file, we will review our company's and customers' information.
We will need to select the company and bank account we will use to manage collections.
The account must include the relevant details, such as its account number and the creditor identifier. This identifier makes it possible to identify the company requesting direct debit collections.
If these fields are incomplete, the remittance may prompt you to enter them.
The file is generated using each customer's default payment method. We will check that it includes:
Bank account or IBAN.
Relevant bank details.
Direct debit mandate reference.
Date the mandate was signed.
We must have the customer's authorization to collect payments by direct debit.
We will go to Treasury → Remittances.
We will click +.
We will complete the description and date.
We will select the company and bank account.
We will complete any missing bank details.
We will click Create.
The remittance will be created with the status Pending. We can then add the invoices.
This is the name we will use to identify the remittance.
For example: Mooring fee collections — October 2026.
This is the scheduled date for processing the collections, which will be included when the file is generated.
Determines which company the remittance belongs to and which invoices we can add.
We will select the bank account associated with that company.
Once the remittance has been created, we will see the invoices available to add.
The list includes sales invoices for the selected company with outstanding amounts. It does not include drafts or rejected or voided invoices.
To add an invoice:
Find the invoice.
Click the + button in its row.
The invoice will appear among those included in the remittance.
Review the amount added.
When you add it, StarNapp suggests the outstanding amount of the invoice, which may be less than its total if part of it has already been collected.
We’ll repeat the process with the other invoices.
Including an invoice in a pending collection batch identifies what we want to collect. It does not yet confirm that the payment has been collected.
While the collection batch is Pending, we can change the amount allocated to an invoice.
For example, if an invoice has €1,000 outstanding and we want to collect only €400 by direct debit:
We’ll add the invoice.
We’ll change its amount in the collection batch to €400.
We’ll check the total for the collection batch.
The amount must be positive and must not exceed the outstanding amount on that invoice.
If that €400 is collected and confirmed, €600 will remain outstanding on the invoice.
While the batch is Pending, we can use the option to remove the invoice from its row.
This action removes its amount from the batch and updates the total. It does not delete the original invoice.
Before generating the file, we will check that it includes only the invoices we want to submit for collection.
When the batch is ready:
We will check the date, bank account, and customer details.
We will check the invoices and their amounts.
We will open the batch options menu.
We will click Generate (xml).
StarNapp will generate the bank file and change the batch status to Processing.
The file contains the information needed to request collections. When there are several invoices for the same customer, generation groups their amounts by customer.
Generate (xml) prepares the file; it does not automatically send it to the bank or confirm that customers have paid.
Once generated, we will submit the file through our bank's remittance service, following its procedure.
We will check whether the bank accepts the file and the outcome of the collections.
If we modify the remittance after generating a file, the previous file is not updated automatically. We must make sure to submit the version that matches the final data.
Once we have confirmed that the collections have been made, we can record their confirmation in StarNapp.
The status Confirmed indicates that the transaction is considered complete. The associated amounts will be taken into account in the payment status of the invoices.
If you cover the entire outstanding balance, the invoice will be paid.
If you cover only part of it, it will be partially paid.
We will not confirm the entire batch if any of the collections have failed or been returned. In that case, we will review the affected transactions before reflecting the result.
Status
Meaning
Pending | We are preparing the batch. We can add or remove invoices and adjust their amounts. |
Processing | The batch is being processed. StarNapp uses this status when generating the XML; it does not, by itself, confirm that the bank has received it. |
Confirmed | The payment has been recorded as completed in StarNapp. |
The ability to change the status may be limited by permissions or by the source of the operation.
The Delete option is available in the menu when the batch is Pending and the user has permission to do so.
Deleting it in StarNapp does not cancel a file that we have already submitted to the bank. If we have sent it, we will also need to check its status with the bank.
We want to collect payment for the monthly invoices of three customers:
Customer A: €300.
Customer B: €450.
Customer C: €250.
The process will be:
We create the payment batch “October direct debits”.
We select the company, account, and due date.
We add the three invoices.
We check that the total is €1,000.
We click Generate (xml). The payment batch changes to Processing.
We submit the file to the bank.
We check the result of the collections.
If they have all been processed successfully, we mark the payment batch as Confirmed.
If these amounts cover the entire outstanding balance of each invoice, all three will be marked as paid.
The remittances described here group together customer invoice collections.
We will review the bank details and mandates before generating the file.
We will check the outstanding amount of each invoice.
Adding an invoice, generating the XML, and confirming the collection are different steps.
The Processing status does not prove that the bank has accepted the file.
We will confirm only the amounts actually collected.
When reviewing Treasury transactions later, we will avoid recording the same collection twice.
