Counterparties
A counterparty is the customer or other organisation associated with invoices and bank activity. Invunion stores identity, roles, references, and free-form metadata so matching can use more than a bank-provided name. You can import and export counterparties, and invoice import can create them automatically when needed.
Browse documentation
What you see in Counterparties
The Counterparties section lists the third parties known to your tenant. Typical fields include:
- a display name and original name;
- an account code;
- category (for example individual, professional, or governmental);
- roles such as client, supplier, payer, partner, internal, or employee;
- contact and address details when you store them;
- status (for example up to date, disputed, or blocked);
- metadata: free-form key/value data at customer level for anything important that is not covered by a standard field.
A single counterparty can hold more than one role. For current reconciliation, customer (client) records are the most important, because Invunion focuses on customer payments against issued invoices and customer refunds against issued credit notes.
Default System
Every tenant has a Default System counterparty with account code SYS-CPT-001.
Payment methods or invoices that cannot be linked to an existing counterparty fall back to this record. Keep it in place; it is part of the tenant bootstrap and should not be treated as a normal customer you delete or overwrite.
Created during invoice import
When you import issued invoices, Invunion can create a counterparty automatically for the customer on each imported invoice when no matching counterparty already exists. You do not have to pre-create every customer before loading invoices.
Import and export
From Counterparties you can:
- Import customers from a file to create or load counterparties in bulk.
- Export the current list of counterparties (for example as CSV) for review, backup, or use in another tool.
Limits to keep in mind
- A bank description that looks like a customer name is not proof of identity on its own.
- Aggregator payment rails (for example some payment-provider patterns) may serve many counterparties, so the payment method is not always owned by a single party.
- Supplier invoices and general outgoing expenses are outside the current reconciliation scope, even if a counterparty record exists.
Next step
Continue with Payment methods to see how banking identifiers attach to a counterparty, or open Issued invoices if you are loading customer documents next.
Updated
Was this article helpful?
Feedback helps us improve the next version of this guide.