> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data and Analytics

> Export DualEntry's accounting data into PostgreSQL, Redshift, or Snowflake for analytics, reporting, and downstream business intelligence.

Data and Analytics covers warehouse data flows in both directions: exporting DualEntry's accounting data into a warehouse for analytics and BI, and ingesting analytics records from a warehouse back into DualEntry.

* **[Analytics Ingestion](./analytics-ingestion)**: ingest analytics records from your enterprise data warehouse into DualEntry. Today this supports usage records for usage-based revenue recognition only.
* **[PostgreSQL](./postgresql)**: export DualEntry's accounting data into a PostgreSQL (or Redshift) database for analytics and downstream BI.
* **[Power BI](./power-bi)**: export ledger data into a PostgreSQL, Snowflake, or SQL Server database, then point Power BI at that database.
* **[Snowflake](./snowflake)**: push DualEntry's accounting data into Snowflake (or another warehouse) for analytics.

The export connectors each register a destination, validate connectivity, and store credentials in AWS Secrets Manager before the export pipeline runs. Analytics ingestion reuses that same secure credential handling for reading from a warehouse rather than writing to one. Power BI is the one that trips people up: DualEntry does not push into Power BI, so connecting it means choosing one of the databases above as the destination and pointing Power BI at that.

Return to [Integrations](../index) for the full connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.