P2P Dash
Sign In Sign Up

Import guide

Everything about getting platform exports into P2P Dash: which file to download, what the import modes do, and what to do when rows are not recognised.

✓ Step by step ✓ Import modes explained ✓ The usual mistakes

See the import in action

Watch the video walkthrough by die-p2p-macher.de to see how importing works in P2P Dash.

P2PDash 2026 - eine umfangreiche Anleitung by die-p2p-macher.de

Quick Start

1

Export from Platform

Download transaction export (Update mode handles incomplete data)

2

Select Platform

Choose your platform before uploading

3

Upload & Import

Drag files and start the import process

Important: Understanding Current Day Data

Current day data is often incomplete because platforms process transactions throughout the day. Here's what you need to know:

  • • Current day transactions may be incomplete or pending
  • • Morning exports might miss afternoon transactions
  • • Platform timing can affect transaction completeness

Good News: Update mode fixes incomplete data on the next import. If today's rows were incomplete, import a later export that covers the same day: for each date the version with more transactions wins.

Best Practices:
• Conservative: Export up to yesterday only
• Convenient: Export including today, then the next time you import, make sure to overlap - Update mode will handle the rest

File Format Requirements

Important: Export the Transaction List

Many platforms offer different types of exports. You need the complete transaction history, not loan summaries or portfolio overviews.

✅ What to export (Transaction List):

  • • All deposits and withdrawals
  • • Interest payments received
  • • Investment transactions (loan purchases)
  • • Principal repayments
  • • Fees and taxes
  • • Bonuses and cashback
  • • Any other transaction-level activities

❌ Don't export these:

  • • Current loan portfolio summaries
  • • Active investment overviews
  • • Account balance reports
  • • Aggregated monthly/yearly summaries

Tip: Look for exports named "Transaction History", "Account Statement", "Transaction List", or similar. These contain the individual transaction records we need.

Supported Formats

CSV Files (.csv)

Comma, semicolon, or tab delimited

Excel Files (.xlsx, .xls)

Multiple sheets supported

Language Requirements

English exports required

Other languages not supported yet

Why English Exports Are Required

Currently, our import system only supports English exports for most platforms. Using other languages will result in import failures:

  • • Import Detection: Non-English files won't be recognized by our system
  • • Column Mapping: Our algorithms expect English column headers
  • • Transaction Types: We currently only recognize English transaction categories
  • • Future Support: More languages will follow as we add them platform by platform.

How to export in English: Most platforms allow you to switch the interface language before exporting. Look for language settings in your account preferences, switch to English, then download your export.

Generic Import Template

Flexible Import Solution

Can't find your platform or need to add missing transactions? Our Generic Import Template provides a standardized format for manual or unsupported-platform data. It must contain only three columns: date, type, and amount. Nothing else.

✅ Perfect For:

  • • Unsupported P2P platforms
  • • Adding missing transactions to existing data
  • • Manual transaction entry
  • • Combining data from multiple sources
  • • Custom transaction tracking

🔧 How It Works:

  • 1. Copy our standardized template
  • 2. Fill in your transaction data
  • 3. Export as CSV or Excel
  • 4. Import using any platform or "Generic"
  • 5. Enjoy standardized processing

📊 Template Features:

Our template includes all supported transaction types with clear examples and formatting guidelines:

Supported Types: Interest, Principal Repayment, Investment, Deposit, Withdrawal, Fee, Tax, Bonus, Default Loss, Internal Transfer
Access Template Make a copy to edit

Usage Tips

  • • Platform Selection: Use "Generic" platform type for unknown platforms, or select any supported platform for the template
  • • Date Format: Use YYYY-MM-DD format for consistent processing
  • • Amount Values: Usually use positive numbers - transaction type determines the direction. Use negative values only for corrections or reversals
  • • Mixing Data: Use Combine mode when importing multiple files together, or Accumulate mode when adding to existing data

Important Notes

  • • Exactly Three Columns: Your file must contain only the date, type, and amount columns. This keeps generic imports from accidentally matching a real platform export, which always has extra columns, and importing it under the wrong platform. If your file has extra columns, remove them before importing as Generic, or choose the specific platform it came from.
  • • Data Quality: Ensure accuracy when manually entering data
  • • No Duplicates: Avoid importing the same transactions multiple times
  • • Backup: Keep copies of your template files for future reference
  • • Validation: Review the analysis before importing to catch any issues

Step-by-Step Import Process

1

Navigate to Your Platform

Import functionality is available on each individual platform page. You'll automatically be importing data for that specific platform, ensuring our system uses the correct processing strategy.

Why this matters: Each platform has unique file formats and column structures. Platform-specific imports prevent mismatched data processing and ensure accuracy.

2

File Upload & Analysis

Drag and drop your files or click to browse. Our system immediately analyzes each file to show:

  • Platform compatibility verification
  • Date range of transactions
  • Total number of records found
  • Count of successfully normalized transactions

Real-time feedback: You'll see all this information before importing, allowing you to verify everything looks correct.

3

Import Execution

Once you're satisfied with the file analysis, click "Import Files" to begin processing. The system will:

Data Processing:

  • • Convert to standardized format
  • • Aggregate into daily timeseries
  • • Validate transaction types

Quality Assurance:

  • • Check for duplicates
  • • Save unhandled records
  • • Update your dashboard

Multiple files: You can queue multiple files and they'll be processed in sequence automatically.

Understanding Import Modes

How Import Modes Work

Four modes decide what happens when a new file overlaps with data you already imported. Update is the default and right for almost everyone; the others cover special cases.

Update (Recommended)

  • Imports files one by one sequentially
  • Uses transaction count as quality indicator
  • Keeps the most complete data for each date
  • Right for regular updates and re-imports

For each date, the system compares transaction counts and keeps the version with more transactions (more complete data). Equal counts favor the newest import.

Combine

  • Merges all queued files together first
  • Then deduplicates like Update mode
  • Track multiple accounts as one
  • Values are summed for overlapping dates

Use this when you have multiple accounts on the same platform that you want to track as one (e.g., two Bondora Go & Grow accounts). Transactions are summed first, then deduplicated like Update mode.

Accumulate

  • Adds new data on top of existing data
  • No deduplication or quality comparison
  • Values are summed for overlapping dates
  • Use with caution to avoid double-counting

Use this only when you're certain the data is truly additive and non-overlapping. Can double-count if same data imported twice.

Replace

  • Completely replaces existing data within the imported date range
  • Data outside the imported range is preserved
  • No merging or quality comparison: new data wins entirely
  • Use with caution: existing data in the range is permanently overwritten

Use this when you need precise control over a specific time period. Ideal for correcting errors or re-importing a date range with updated data from the platform.

Practical Examples

✅ Update: Regular Monthly Import

You imported January data last month, now importing February data:

Existing: Jan 1-31 | New import: Feb 1-28 → Result: Complete Jan 1 - Feb 28 data

✅ Update: Fixing Incomplete Data

You imported incomplete current day data, then later import complete data - Update mode automatically fixes it:

First import: Feb 15 (3 transactions) | Second import: Feb 15 (8 transactions) → Result: Feb 15 with 8 transactions (the more complete data wins)

✅ Combine: Multiple Account Exports

You have two Bondora Go & Grow accounts you want to track as one:

Account A: Feb 1-28 | Account B: Feb 1-28 → Result: Both accounts merged and imported together

✅ Update: Historical Data Import

Adding older historical data to existing account:

Existing: Jun 1 - Dec 31 | New import: Jan 1 - May 31 → Result: Complete year-long data

✅ Replace: Correcting a Specific Period

You noticed incorrect data for March and re-exported that period from the platform:

Existing: Jan 1 - Jun 30 | Replace import: Mar 1-31 → Result: Jan-Feb preserved, March replaced, Apr-Jun preserved

Troubleshooting Common Issues

"No strategy found for platform" Error

This means the file format doesn't match the expected structure for this platform.

  • Verify you're on the correct platform page
  • Check if you're using English exports (required for most platforms)
  • Ensure you're exporting the transaction list, not loan summaries or portfolio reports
  • Look for "Transaction History", "Account Statement", or similar export options
  • Try switching the platform interface to English before exporting

High Number of Unhandled Records

Unhandled records are transaction types the import doesn't know yet.

  • They are saved without a link to your account so support can be added
  • We regularly add support for new transaction types
  • Your import will still proceed with recognized transactions
  • You may need to re-import once we add support

Keep your original export files. Once the missing type is added, you re-import them.

Missing Recent Transactions

This was a common problem with the old deduplication, which marked partial days as complete. Update mode replaces them.

  • <strong>Old system:</strong> Partial data would be marked as "complete" and skipped in future imports
  • <strong>New system:</strong> Update mode compares transaction counts and chooses the more complete data
  • <strong>Result:</strong> Incomplete data gets automatically replaced by complete data

Fix: Import a later export that covers the same days in Update mode (the default). For each date the version with more transactions is kept.

Best Practices for Reliable Imports

Do These Things

  • • Export data up to yesterday only
  • • Use English language exports (required for most platforms)
  • • Navigate to the correct platform page for importing
  • • Keep original export files for potential re-imports
  • • Review file analysis before importing
  • • Import regularly to maintain current data

Avoid These Mistakes

  • • Including current day in exports
  • • Uploading files to the wrong platform page
  • • Using Accumulate mode for regular updates (use Update instead)
  • • Ignoring unhandled record warnings
  • • Deleting original export files
  • • Importing files with mixed platforms

Ready to import?

Create an account, open the platform page, upload the export. The first numbers are there a few minutes later.

Create free account

Free to use • No platform login needed • First import in minutes