Payment methods, bank details, and manual payment registration

Historical retrospective - September–October 2025 This article was written afterwards and describes the feature as it worked during the stated period.

A card charge moves money through the payment provider. A bank transfer happens outside the gateway and can later be registered manually on an invoice with an outstanding balance. Bank details on the invoice are not card details or gateway setup. A manual entry for a smaller amount leaves the invoice partially paid; it is paid only when the balance is covered. Registration documents payment in Alunta but does not move money in the bank. See the current guide (Markdown file, AI agent-friendly)

Example and answers

Example: A customer transfers DKK 700 for a DKK 1,000 invoice. Register only DKK 700; the invoice remains partially paid until the rest arrives. Bank details on the PDF do not change the card payment method.

If the amount cannot be registered, check that the invoice has a balance and is not a credit note.

Register only received amounts

Open the invoice payment action, check the outstanding balance, and enter the amount actually received in the bank. Use the transfer’s received date according to the team’s reconciliation practice. If the customer pays in two parts, register two payments; the status becomes paid only when the balance is covered.

A manual payment does not create a bank transfer or start a gateway. Do not use it for an authorization, a promised payment, or a collection still pending with a provider. Credit notes have their own document flow.

Reconcile after registration

After registering a bank payment, reopen the invoice and check remainder, payment date, and activity. If the customer paid the wrong amount, do not use manual registration to hide the difference. Register what was received and follow the team’s normal reconciliation for the rest or a credit.

Manual payment is useful when no gateway is involved. If the customer also has a pending card collection, resolve it first so you do not register a bank payment and later receive a card payment as well.

FAQ and boundaries

A manual payment is a record, not a new collection. It cannot reserve money, reactivate a subscription, or force an invoice to paid without money actually received. If the bank amount differs from the invoice, keep the actual payment and handle the remainder as a partial payment, credit, or other agreed reconciliation.

Support scenario

If the customer transfers an amount different from the invoice balance, document the difference in later reconciliation. Do not use a manual payment to make a customer appear paid before money is received. The same applies while an online payment is pending.

Check after the action

Use this check during follow-up: note what was visible before the action, perform only the selected action, and check the document or mandate afterwards. Read a status again before informing the customer if it changes later. The retrospective describes the documented milestone; the current guide and interface determine today’s steps. Examples use fictional customers, amounts, and dates.

If the result differs

If the result does not match expectations, keep the visible status and investigate the relevant prerequisite instead of repeating the action blindly. Check currency, date, customer, payment method, and whether the document was already sent or booked. When answering a customer, distinguish what the system recorded from what the bank or recipient has not yet confirmed.