Are both sources in TD SYNNEX StreamOne + PSA available?

Yes. Both sources are listed as available integrations. Exact record coverage depends on vendor plans, account configuration, permissions, and the billing model being reviewed.

Does BillingReconcile automatically change invoices?

No. The current workflow provides comparison context and evidence. Your team remains responsible for deciding and applying any change.

Does every difference indicate a billing error?

No. Timing, account structure, service mapping, lifecycle changes, agreement terms, and source freshness can all create legitimate differences.

Available integration pair

TD SYNNEX StreamOne + PSA Billing Reconciliation

BillingReconcile supports TD SYNNEX StreamOne + PSA as a review pair. MSP teams can compare StreamOne marketplace subscription and licence quantities beside PSA recurring billing while keeping account, service, timing, and agreement context visible before making a billing decision.

Book a Demo View Integrations

What the two systems contribute

A PSA or billing system and an operational source often describe the same client service from different perspectives. Reviewing both sides helps a team understand whether the proposed billed quantity still reflects the source evidence.

BillingReconcile keeps the comparison reviewable. It does not assume that every quantity difference is a billing error.

Data categories that may be compared

StreamOne customers, marketplace products, subscriptions, and licence quantities

PSA customers, recurring services, products, and billed quantities

Customer relationships across both systems

Marketplace-product and billed-service relationships

Common differences worth investigating

A StreamOne subscription quantity changed while the PSA billed quantity did not

A reduced product remains represented at the previous billed quantity

A StreamOne customer does not clearly correspond to the PSA customer

A marketplace product is associated with the wrong billed service

A review-first sequence

1
Connect both supported sources with appropriate authorization.
2
Confirm that the customer accounts correspond across the systems.
3
Confirm that the billed service represents the source product, device, or licence category.
4
Compare the billed quantity against the relevant source count for the review period.
5
Have an authorized person decide whether billing, mapping, or source data should change.

Read-only and human-review boundaries

The current BillingReconcile workflow is read-oriented and does not silently change invoices or connected-system records. Contract terms, billing policy, and exceptions remain under the MSP team's control.

Confirm connector scope

Available records vary by vendor plan, account configuration, granted permissions, and API changes. BillingReconcile confirms the data required for the agreed billing model during onboarding.