
BureauRelay reads selected QuickBooks Online customer accounts, invoices, payments, credits and refunds through OAuth 2.0. Dated source evidence anchors payment history and preserves continuous delinquency until an evidenced cure. Full inventories, independent customer balances and change-data recovery checks precede reporting acceptance. Files then follow the customer's configured bureau routes and delivery approvals. QuickBooks Desktop continues through manual CSV or Excel import.
An authenticated request verifies access to the authorized QuickBooks company realm. Signed notifications invalidate readiness and request a source refresh; full inventory and CDC recovery run under durable request budgets. Independent balances and dated history must reconcile before the ordinary API generates a validated file. Source sync, file validation, transport receipt and verified bureau response are separate checkpoints.
QuickBooksMap approved customer credit accounts with their actual terms, invoices and allocation evidence.
Authorize QuickBooks Online without sending accounting passwords to BureauRelay. Sandbox and production access stay separate.
Preserve history by calendar month and retain corrections in their original periods.
Paying one invoice does not reset an account's delinquency while other overdue obligations remain.
Verify signed QuickBooks notifications and refresh complete inventories before issuing new reporting readiness.
After an exceeded CDC window or saturated response, review current inventory, deleted accounts and affected periods before establishing a new baseline.
BureauRelay maps these fields from QuickBooks to Metro 2 format automatically.
Use OAuth 2.0 in the intended Test or Live environment with the accounting scope. Reconnecting must retain the same company realm.
Select immutable customer IDs and approve credit terms, reporting identity, historical evidence and source balances.
Discover and import a complete inventory, reconcile balances and test history across periods through the ordinary reporting API.
Accept the mapping and reporting scope. Enable the configured schedule and delivery route under existing customer approvals.
QuickBooks Online uses OAuth 2.0 REST API access. QuickBooks Desktop uses the existing manual CSV or Excel import workflow.
Yes. The accepted mapping defines the supported account relationship and product, with invoice due dates, allocations and dated history as evidence. A customer name or invoice alone does not establish reporting eligibility.
Reporting remains held while an administrator reviews complete current inventory, account dispositions and affected historical periods. Acceptance establishes a new CDC baseline; a subsequent successful scan is required.
Full scans default to hourly, configurable from 15 to 1440 minutes. Verified notifications can request earlier refreshes. Provider limits and source volume govern job completion.
No. Mapping acceptance, file validation, customer reporting approval and the configured bureau delivery route are separate steps.

Report customer payment data from Xero to credit bureaus via OAuth 2.0 REST API with HMAC-SHA256 webhooks.

Report customer accounts from FreshBooks to credit bureaus via OAuth 2.0 REST API.

Report customer credit accounts from Sage Intacct or Sage 50 to credit bureaus via REST API or XML Web Services.