A practical starting point for your financial data

No. PipeLedger includes ERP extraction, accounting transformations, and a managed financial data warehouse. We maintain the pipeline and deliver approved data to your AI agents and reporting tools. Your team reviews accounting classifications and controls access, without having to assemble and operate the data infrastructure.

Compare building with buying

PipeLedger consolidates QuickBooks Online companies and NetSuite subsidiaries in one financial warehouse. Source accounts map to a common GAAP-aligned reporting taxonomy, and every published General Ledger line carries a Reporting Legal Entity ID. Income Statements and Balance Sheets can cover one Legal Entity or all authorized entities on a consistent reporting currency and accounting-book basis, with access-controlled drilldown to supporting records. Source identities remain available when records for the same legal company are combined across systems.

Group reporting

Yes. Source accounts retain their native numbers and names while mapping into a common five-level reporting hierarchy with GAAP-aligned classifications and configurable categories. Your controller reviews classifications, with ambiguous mappings prioritized by materiality and changes recorded for audit. Account 4000 in one company and 40100 in another can roll into the same revenue line when they represent the same activity, while retaining their separate identities for drilldown.

Account classification and normalization

Your controller tags dedicated intercompany accounts. Use is_intercompany in pl_query or exclude_intercompany in pl_report to exclude them from queries, Income Statements, Balance Sheets, Cash Flow Statements, and eligible Metrics Reports. The selection also applies to comparison periods and drilldowns, supporting questions such as revenue excluding sales to group companies. Untagged related-party transactions are not automatically identified; PipeLedger does not match intercompany pairs or post elimination journals. An excluded Balance Sheet is identified as a partial ledger and may not balance.

Intercompany handling

PipeLedger publishes datasets after the required financial checks and publication approval. A person approves publication unless automatic approval has been authorized. Report and query responses identify their source publication and provide source-recency evidence. The pl_data_quality tool reports readiness and flagged checks; pl_audit records publication approvals and their actors in an append-only audit trail. Publication age describes the available data, not whether month-end close is complete in your ERP.

Data readiness and evidence · Publication audit trail

Yes. Access can cover the whole organization, selected Legal Entities, or rows limited by business, geographic, or functional segment, project, or other supported filters. Clearance separately controls account amounts and detail; identity policy determines whether customer, vendor, employee, and project identities appear as original values or stable tokens. These controls apply across MCP, REST, and CLI; direct BI follows the organization’s BI delivery policy. The pl_whoami tool explains the connection’s access and whether its ledger view is complete or limited.

Identity, scope, and access

Yes. PipeLedger produces an indirect-method Cash Flow Statement from account classifications, balance changes, and supporting transaction evidence. Framework and industry defaults establish cash-flow treatment, which your controller can review and override per account or, for eligible cases, per transaction. Reports identify their reconciliation status and provide drilldown to supporting cash-flow components and authorized evidence. A direct-method preview is also available with its coverage limits identified.

Financial statements and drilldown

Yes. We recommend an Analytics Hub linked dataset in your own Google Cloud project for Power BI, Tableau, Looker Studio, and other tools that connect to BigQuery. PipeLedger also offers BI service-account credentials for direct BigQuery connections and a hosted Looker Studio connection if you do not run Google Cloud. For clients with Databricks, delivery into their AWS or Azure environment can be arranged on request. Delivery covers your organization’s configured sources, with BI access and identity-privacy settings agreed for the connection.

BI delivery options

Yes. PipeLedger consolidates connected entities into one financial warehouse with a common account taxonomy and business dimensions. Approved mappings bring records for the same legal company under one Reporting Legal Entity ID, while preserving their source references.

Combining financial sources

Extraction reaches as far back as records are available through the source APIs. Manual historical backfill is also available on request.

QuickBooks history · NetSuite history

QuickBooks Desktop historical imports are supported on request. The live connector supports QuickBooks Online; there is no live QuickBooks Desktop connector.

QuickBooks source coverage

No. PipeLedger does not write back to any connected ERP or initiate payments. Our approach to secure autonomous finance separates the agent coordinating the work from specialist agents authorized to act in an ERP or payment system. PipeLedger provides governed financial data and classification tools. Agents using PipeLedger receive no ERP credentials or tools for posting transactions or initiating payments.