# Import external data into Stripe

Automatically import and map external data from other sources with no-code connectors.

Use the [Stripe Dashboard](https://dashboard.stripe.com/data-management) to automatically upload data from other sources into Stripe. Under **Data Management**, you can:

- Connect your Apple App Store data to import subscriber data.
- View the processing status of your Import Sets.
- Get detailed information on file processing after completion.
- Download and resolve Import Set errors.

## Choose an import for your task 

Choose the business result before choosing a file format or connector. The destination determines whether an import affects accounting, tax reporting, or usage for billing. A one-time upload and a recurring connector are ways to deliver data, not interchangeable business operations.

| Your task | Destination and import path | Required identifiers and data | What changes | What doesn’t change | Verify the result |
| --- | --- | --- | --- | --- | --- |
| Recognize revenue from external sales | Revenue Recognition. Use [general import](https://docs.stripe.com/revenue-recognition/data-import.md#general-import) for CSV files, or a supported [Apple](https://docs.stripe.com/data/import-external-data/connectors/apple-app-store.md) or [Google Play](https://docs.stripe.com/data/import-external-data/connectors/google-play.md) connector. | For CSV imports, provide a source, transaction ID, booked date, recognition start and end dates, amount, and currency. Connectors use their source reports instead of this CSV format. | Adds external transactions to Revenue Recognition reports and recognizes revenue over their service periods. | Doesn’t collect a payment or create a Billing subscription. This isn’t a Stripe Tax import. | Check imported transactions and then [Revenue Recognition reports](https://docs.stripe.com/revenue-recognition/reports.md). For Apple, follow the [end-to-end example](https://docs.stripe.com/revenue-recognition/data-import/apple-app-store.md#import-to-revenue). |
| Correct an existing recognition schedule | Revenue Recognition [general import](https://docs.stripe.com/revenue-recognition/data-import.md#general-import). | Set **Source** to `Stripe` and use the existing transaction ID. For an invoice line, use the invoice ID and set **Split transaction ID** to the invoice line item ID. Supply the recognition dates to override. | Changes the transaction’s recognition schedule in Revenue Recognition. | Doesn’t change the underlying payment or invoice, or bill the customer again. Stripe ignores overrides on payments attached to invoices—target the invoice instead. | Check the imported transaction’s status and its schedule in the [Revenue Recognition audit view](https://docs.stripe.com/revenue-recognition/reports/audit-numbers.md). |
| Exclude a transaction from revenue | Revenue Recognition [exclusion import](https://docs.stripe.com/revenue-recognition/data-import.md#exclusion-import). | Use the invoice, invoice item, invoice line item, or standalone payment ID. For a payment attached to an invoice, use the invoice ID. | Excludes the transaction from revenue. The accounting treatment depends on whether and how it was paid. | Doesn’t refund cash already received or delete the original transaction. This isn’t an exclusion from Stripe Tax reporting. | Check the [exclusions list](https://docs.stripe.com/revenue-recognition/data-import/manage-imported-data.md#exclusions) and the resulting accounting entries. |
| Add a journal entry | Revenue Recognition [journal entry import](https://docs.stripe.com/revenue-recognition/data-import.md#journal-entry-import). | Provide an existing transaction ID in the same account and mode, an open accounting period date, debit and credit accounts, and settlement amount and currency. Use an invoice ID instead of its attached charge ID. | Adds manual debit and credit entries to Revenue Recognition reports. | Doesn’t collect or refund money, or change the underlying invoice. Use general import to change a recognition schedule instead. | Check the [journal entries list](https://docs.stripe.com/revenue-recognition/data-import/manage-imported-data.md#journal-entries) and the [Debits and credits report](https://docs.stripe.com/revenue-recognition/reports/debits-and-credits.md). |
| Include external sales in tax monitoring and reporting | [Stripe Tax transaction import](https://docs.stripe.com/tax/imports.md). | Include `provider`, `source_transaction_id`, and `line_item.id`, plus the required dates, addresses, currency, tax classification, and amounts in the Tax CSV format. Refunds and voids also require `liable_transaction_id`. | Includes external sales in tax obligation monitoring and reporting, using the tax amount you provide. | Doesn’t recalculate the imported tax amount, modify Stripe-processed transactions, or add revenue to Revenue Recognition. | Check import validation results, then [tax reports](https://docs.stripe.com/tax/reports.md) and [obligations monitoring](https://docs.stripe.com/tax/monitoring.md). Some reports and interfaces take up to 2 days after processing to reflect imports. |
| Record usage for billing | Billing meter events. [Upload usage in the Dashboard](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage-in-bulk-dashboard.md) or [import it from Amazon S3](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage-in-bulk.md) for an existing Billing Meters integration. | Configure a meter first. Include its event name, customer identifier, usage value, and timestamp in the selected format. For S3 imports, you can also supply a unique event `identifier`. | Records meter events that Stripe aggregates for usage-based billing. Usage can affect upcoming invoices according to your subscription and pricing configuration. | Doesn’t create a subscription or immediately collect a payment. It isn’t an external-sales import for accounting or Tax. | Check file status in Data management, then the meter event count, aggregated usage, and upcoming invoice. Aggregation is asynchronous. For new integrations, review the [usage recording options](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage.md). |

Use each product’s template and correction instructions. Don’t assume that re-uploading the same file replaces prior data or prevents duplicates across destinations. For example, [Stripe Tax uses transaction versions for corrections](https://docs.stripe.com/tax/imports.md#correcting-transactions), while [Revenue Recognition ignores duplicate exclusion IDs](https://docs.stripe.com/revenue-recognition/data-import.md#exclusion-import).

## Verify import and product processing 

Verify both milestones before treating an import as complete:

1. **Import result**: In Data management or the product’s import page, check processing status and record-level errors. Resolve any failed records.
2. **Business result**: Check the destination product’s output listed in the [Verify the result](https://docs.stripe.com/data/import-external-data.md#supported-use-cases) column of the import table. A successful file import doesn’t mean the product has finished processing the data.

For manual Revenue Recognition imports, reports typically update in 3–4 hours. Mobile app store imports have a different timeline—Stripe fetches Apple App Store data daily, and Revenue Recognition processing takes approximately 24 hours after connector import. Check the report’s data freshness timestamp before re-importing data that isn’t visible yet. See [Revenue Recognition data freshness](https://docs.stripe.com/revenue-recognition/data-freshness.md) for timing by data source and interface.

## Get started 

[Amazon S3](https://docs.stripe.com/data/import-external-data/connectors/s3.md): Automate recurring file imports from your Amazon S3 bucket to Stripe.

[Apple App Store®](https://docs.stripe.com/data/import-external-data/connectors/apple-app-store.md): Use the Apple App Store to Stripe to automate recurring file imports.

[Google Play Store](https://docs.stripe.com/data/import-external-data/connectors/google-play.md): Automate recurring file imports from Google Play Store to Stripe.

### Request access to ingesting data that isn’t currently supported.

Enter your email to request access.

```bash
curl https://docs.stripe.com/preview/register \
  -X POST \
  -H "Content-Type: application/json" \
  -H "Referer: https://docs.stripe.com/data/import-external-data" \
  -d '{"email": "EMAIL", "preview": "udap_ingestion_preview"}'
```
