Skip to content

Update 15.07.2026

The AbaNinja release on July 15, 2026, introduced new features in addition to various improvements:

  • Dunning Settings
  • Dunning Fees
  • Postpone Dunning Date
  • SamurAI AI Assistant - Confirmation

Dunning

In addition to the redesign of the page for basic dunning settings under “Settings - Invoices - Dunning,” several other useful new features were introduced. You can now define default dunning settings for all addresses.

  • Reminders enabled by default
  • Reminder fees enabled by default
  • Automatic sending of reminders enabled by default

By default, these basic settings apply to all addresses. However, the settings can be overridden individually for each address.

This enhancement allows for the easy activation of the dunning system, as well as the new reminder fees and automated sending, for the entire address database.

Late fees

The new late fees are available from the Pro Subscription, can be individually defined and overridden per reminder level and per address, and are booked as an additional amount directly on the reminder invoices. The use is currently only possible with the new invoice mask.

The features of late fees in detail

Availability and activation

The late fee function is available from the Pro Subscription.

In the settings for the reminder system, you first define which reminder levels (payment reminder, 1st reminder, 2nd reminder, etc.) are active and when they are triggered. Newly, there is an additional setting with which you can generally activate late fees and enter an amount per reminder level.

Late fees per level (reminder level)

For each reminder level, you can define a fixed late fee amount, e.g. CHF 0.-- for the payment reminder, CHF 10.-- for the 1st reminder, CHF 20.-- for the 2nd reminder, etc.

Important: A higher reminder level may not have a lower amount than the previous level. This way, your reminder process remains logical and legally consistent.

Overriding per address

In addition to the general settings, you can enter your own reminder settings per address in the General tab (manual/automatic). This logic is now supplemented by late fees. So you can, for example, manage dunning fees individually for specific customers by activating or deactivating them per address, or by applying the account settings, without changing the global defaults.

Triggering of late fees on invoices

When a reminder level is triggered, AbaNinja creates a new reminder document for each reminder/late fee. The defined fee amount appears as an additional position/amount on this document and is automatically booked. A reminder at a higher level replaces the previous reminder level. This means that already charged late fees from the previous level are transferred to the new reminder level so that the fees do not double, but are correctly continued.

QR reference and payment receipts

All reminder documents for the same invoice retain the same QR reference. This allows incoming payments to be automatically correctly allocated: first the open invoice amount and then any late fees are offset, without you having to manually assign the payment.

New invoice mask as a prerequisite

The new late fees can only be used in combination with the new invoice mask (new entry view for invoices).

Account assignment for late fees

With the new account assignment for late fees, you can define on which accounting account the charged late fees should be booked. By default, AbaNinja uses the accounting account 3094 for late fees. If necessary, this assignment can be individually adjusted.

Manual override of late fees directly on the invoice

Once an invoice has reached the status "Sent", there is also the possibility to manually override the late fees directly on the invoice. This allows you to adjust the suggested late fee amount for a single invoice again individually, without changing the general settings in the reminder system. This option is particularly suitable for individual customer agreements or special situations where deviations from the stored standard values are desired.

Benefits

  • Less manual effort: Late fees are automatically calculated and posted per stage – you don’t have to create separate invoices for fees.
  • Transparent debt collection process: Clear amounts per stage and the rule that higher stages cannot be cheaper ensure a transparent process for your customers.
  • Automatic payment allocation: Identical QR reference ensures that incoming payments including late fees are automatically assigned to the correct invoice and stage.
  • Flexible customer treatment: Overrides per address allow you to treat regular customers more leniently without changing your general debt collection rules.

Tips and hints

  • First check your existing debt collection stages (texts, deadlines, automatic/manual triggering) in the settings and then add late fees sensibly per stage.
  • Start with moderate fee amounts and adjust them based on practical experience so that your debt collection is perceived as fair.
  • Use the option to individually adjust or deactivate late fees for sensitive addresses (e.g. long-term customers).
  • Test the process with an internal test address: Create an invoice, let it become due, trigger the debt collection stages and simulate the payment flow with a QR invoice to check the bookings and documents.
  • Check the account assignments from the start to ensure the bookings are correct. When using the predefined account plans, the account 3094 "Inkassospesen" is automatically used.

Adjust due date

With the new feature Adjust due date, you can manually adjust the date for the next reminder directly on an invoice. This allows you to maintain control over the reminder timing in special cases without having to change your general reminder settings or automation. To use these features, the billing system and automatic invoice reminders must be enabled on the address.

AI Assistant SamurAI - Confirmation

SamurAI automatically performs numerous tasks, such as recording invoices or products. The AI agent now asks more often before something is definitively executed. This ensures that sensitive processes do not simply "happen on their own," but can always be confirmed by a person.