When should you import transactions?
The import feature is ideal when you need to record multiple transactions at once, for example:
After a fundraising event with many cash or check donations
To integrate a transaction history from another tool
To centralize a large volume of offline memberships
💡 To record a single transaction, use the manual entry method instead.
✅ Before you start
Make sure you have:
The Fundraising module activated on your workspace (how to activate the Donation & Membership module)
Your campaigns and donation products already configured in Qomon — it is not possible to create new ones during the import (how to create your products and campaign codes)
A properly structured CSV file (see the templates at the bottom of this article)
The following cases are not yet supported:
Third-party payer
Couple membership
A donation made alongside a membership, for the same person
These cases can be handled via the Qomon public API: Explore the Qomon API.
🚀 How to launch a transaction import
1. From your Qomon workspace, go to the "Fundraising" tab
2. Click "Import transactions"
3. Choose the import type:
Transactions only
Contact records and Transactions (mixed import)
4. Select your CSV file
5. Check the column mapping (you can enable AI-powered automatic column detection), then launch the import
📋 Required fields for transactions
For the import to run, each transaction row must contain at minimum:
Field | Requirement | Notes |
Amount | Required | In euros, numeric format |
Transaction date | Required | DD/MM/YYYY format recommended |
Payment method | Required | Must match the values configured in Qomon |
Campaign code | Optional | Must already exist in Qomon |
Contact ID | Required for transaction-only imports. Recommended for mixed imports (contacts & transaction data). | Enables better duplicate matching |
⚠️ Important: Transaction-related values in your file (campaign codes, payment methods, etc.) must exactly match what is configured in your workspace. No automatic product creation is possible during the import.
👤 Managing contacts during the import
If a contact already exists in your database, Qomon automatically matches them via their unique Qomon identifier (Qomon ID).
If a contact does not yet exist, they will be automatically created from the information in the file (last name, first name, email, etc.).
For complex cases (third-party payers, advanced data relationships), the CSV import is not suitable — use the Qomon API instead.
🔍 Understanding import results
Once the import is complete, Qomon displays a summary with separate indicators for contacts and transactions:
Successfully imported rows
Rows with errors, with the exact line and issue identified
You can correct your file directly and relaunch the import without contacting support.
Common errors:
Missing or incorrectly formatted amount
Missing date or unrecognized date format
Payment method or campaign code not matching an existing value in Qomon
📎 Template to download
File import templates are available to help you get started:
💡 You can have both contacts and transactions data in your file if you wish to import both transactions and contacts information into your Qomon Database.
Simply make sure your file is properly formatted.
If you have any questions, feel free to contact us at: [email protected]