Payment methods
A payment method stores how money moves for a counterparty: a bank account, card, wallet, or other instrument. Invunion uses these records, including IBAN or provider identifiers, as matching signals. You can import and export payment methods, and transaction intake can create or resolve them automatically.
Browse documentation
What you see in Payment methods
The Payment methods section lists the payment instruments known to your tenant. Typical fields include:
- a code and name;
- type (for example bank account, credit card, PayPal, Wero, Twint, or other);
- currency;
- IBAN and BIC when applicable;
- bank name and other identifiers;
- status (active, inactive, or error);
- the linked counterparty when one is set.
Some records are catalogue entries you manage yourself. Others are created or updated when bank connections and transaction imports resolve identifiers. Technical bank-connector rows for connected accounts are different from the catalogue instruments you associate with customers.
Default System
Every tenant has a Default System payment method with code SYS-PM-001, attached to the Default System counterparty (SYS-CPT-001).
Transactions that cannot be linked to an existing payment method fall back to this record. Keep it in place; it is part of the tenant bootstrap and should not be treated as a normal instrument you delete or overwrite.
Created during transaction intake
When bank transactions are synchronized or imported, Invunion can create or resolve a payment method automatically from identifiers such as an IBAN or a known provider pattern. Creating a counterparty can also create a default payment method for that party, so there is a place to attach later banking identifiers.
Import and export
From Payment methods you can:
- Import payment methods from a file to create or load instruments in bulk.
- Export the current list of payment methods (for example as CSV) for review, backup, or use in another tool.
Merge
Use Merge when several payment methods represent the same instrument (for example duplicate IBANs created by imports).
You choose a target payment method that keeps the history. The other methods in the group are absorbed into it:
- their transactions are reassigned to the target;
- missing IBAN, BIC, identifier, or counterparty details on the target can be filled from the sources;
- the absorbed payment methods are then deleted.
Invunion can suggest probable duplicates. You can also add methods to the merge group manually or start from a multi-row selection.
Default payment methods cannot be absorbed as sources; keep them as the target instead. Technical bank-connector rows cannot be merged from this screen.
Limits to keep in mind
- A payment method alone does not confirm that a payment belongs to a specific invoice.
- Aggregator rails (for example some payment-provider patterns) may serve many counterparties, so the payment method is not always owned by a single party.
- Missing or conflicting identifiers reduce matching strength and may leave a case for review.
- Disconnecting a bank connection does not delete transactions already imported, and catalogue payment methods remain until you change them.
Next step
Continue with Transactions to see how bank lines arrive and use these instruments, or return to Counterparties if you still need to create the customer record first.
Updated
Was this article helpful?
Feedback helps us improve the next version of this guide.