QuickBooks Online
OAuth connection, period review, supported change monitoring, source snapshots, and approval-controlled corrections for eligible accounting records.
Connected systems bring tenant-scoped transaction evidence into Prophit.ai. Each provider exposes only the modes its implemented adapter supports; a Period Review connector is never presented as real-time or write-back capable.
Open Sales Tax Compliance, choose Data Sources, and select Set up an integration. QuickBooks Online and Stripe expose their implemented connection workflows. SAP S/4HANA Cloud, Oracle Fusion Cloud, and Oracle NetSuite expose read-only Period Review setup using the customer tenant base URL and a least-privilege provider identity. Workday uses a customer-defined report mapping.
The platform stores connector credentials in the encrypted credential vault and never returns plaintext through list or detail APIs. Every connection belongs to one organization and location. Verification performs a bounded provider read before the connection becomes active; a failed verification remains visible with an error state instead of being called connected.
For a Period Review, choose a start and end date. Prophit.ai queues an idempotent sync, bounds provider pagination and record volume, retains the original provider payload as a scoped evidence snapshot, normalizes header and line facts, and records the run metrics and any provider-safe error message.
SAP uses the S/4HANA Cloud Billing Document OData collection. Oracle Fusion Cloud uses the Receivables Invoices REST resource with invoice lines expanded. NetSuite uses the REST Record Service, requires OAuth 2.0 and an explicit SuiteTax confirmation, and retrieves each invoice with subresources expanded. Provider endpoint paths and synchronization limits have safe defaults and can be configured for the tenant contract.
A connector catalogue is useful only when its operating mode is truthful. Prophit.ai separates available read-only period review from tenant-specific real-time calculation and write-back work, so buyers know which system owns each action.
ERP tax evidence is high-volume and sensitive. Organization and location isolation, encrypted credentials, bounded pagination, source snapshots, deterministic normalization, and non-mutating defaults make the integration reviewable in production.
Connected-system setup lives in Sales Tax Compliance → Data Sources. Imported transactions enter the same calculation, variance, nexus, and return-preparation workflows as Upload Center data. Headless real-time tax calculation uses API Access rather than these read-only ERP adapters.
OAuth connection, period review, supported change monitoring, source snapshots, and approval-controlled corrections for eligible accounting records.
Billing imports and supported event monitoring, with explicit profiles for billing, payments, marketplace, settlement, and tax-engine workflows.
Available read-only Billing Document header and item Period Review through the official OData API. Provider write-back is not enabled.
Available read-only Receivables invoice and line Period Review through the official Financials REST API. Provider write-back is not enabled.
Available read-only invoice and item-line Period Review through REST Record Service. OAuth 2.0 and SuiteTax are required; provider write-back is not enabled.
Available mapped report ingestion for customer and supplier document facts. Workday-side mutation requires a separately authorized Extend or Orchestrate implementation.