Before You Start
User Rights: You need to be an admin in order to import transactions on a bank account.
Bank Accounts: Transactions are imported per bank account.
Include All Transactions: Ensure your import file contains all transactions for each day, even those already in Agicap. The system will filter out duplicates automatically.
Step 0: Find the Bank Account 🏦
To start, you will have to access to the Banks & Integrations page and find the connected bank account where you want to import the transactions. Once you found the bank account:
Move the cursor over the bank name,
Click on the three dots appearing next to it,
Choose 'Import Transactions'.
Step 1: Select the File to Import 📁
Your import file must include both the booking date and the value date for each transaction.
These dates are usually available in bank statements or exports.
Including both dates allows precise synchronization of transactions.
You can use the provided template to format your file correctly. You can download the template directly from the Step 1 window.
Step 2: Choose the Type of Import 🔄
You have two options:
Exhaustive Import (✅ Recommended):
Your file contains all transactions for the selected date range.
Ensures that your bank account reflects the exact transactions.
Partial Import:
Your file contains some transactions for the selected date range.
Not recommended due to potential inconsistencies.
Step 3: Map the File's Columns (Optional) 🗺️
If your file doesn't match the provided template, you can map your file's columns to the expected transaction fields.
This ensures that each transaction field corresponds to the correct column in your file.
Step 4: Processing the Bank File ⚙️
Validation: Each transaction is analysed for completeness and correct formatting.
Transactions with missing or invalid fields (e.g., amount, date) are rejected.
Transaction Matching:
The system automatically chooses to use either the booking date or the value date for comparison.
Transactions are compared based on date and amount.
Matched Transactions: If an imported transaction matches an existing one, it is ignored.
New Transactions: Imported transactions not matching any existing ones are imported.
Obsolete Transactions: Existing transactions not matching any imported ones are deleted.
Step 5: Validate and Complete the Import ✅
Review the summary of:
Transactions to import
Transactions to ignore
Rejected transactions
Choose how you want transactions to be displayed:
By booking date
By value date
Click Validate to finalise the import.
💡 Tips
Always Use Exhaustive Imports: To maintain consistency and avoid duplicates.
Include All Daily Transactions: Even if they already exist in Agicap.
Check File Formatting: Ensure your import file follows the provided template or properly map the columns.
Display Preferences: After importing, you can choose to display transactions by booking date or value date.
Q&A ❓
What happens if I import duplicate transactions?
The system automatically detects and ignores duplicate transactions based on date and amount, ensuring no duplicates are added.
Can I choose which transactions to delete during an exhaustive import?
During an exhaustive import, the system automatically deletes existing transactions that don't match any in your import file. You cannot manually select transactions to delete. To avoid losing valuable data, ensure your import file includes all relevant transactions.
What if my bank file doesn't include booking date or value date?
Both dates are crucial for precise synchronisation. If your file lacks one of these dates, you may encounter issues with transaction comparison and synchronisation limits. Make sure your import file includes both dates for each transaction.