Client Mapping

Client Mapping helps connect integration-side client records to the correct PSA-side client. This is one of the most important setup steps because accurate client mapping makes the rest of reconciliation much more reliable.

What you’ll see

The page is split between unmapped clients and mapped clients so you can quickly identify records that still need review.

Unmapped clients are integration-side records that have not yet been linked to the correct PSA-side client. Mapped clients are records that BillingReconcile believes are already associated correctly across systems.

AI-assisted matching

During sync, BillingReconcile suggests likely client matches during sync to speed up setup.

These suggestions are meant to speed up setup, not replace review. It is still important to confirm that mapped clients are correct before relying on downstream discrepancy results.

Common actions

Merge an unmapped client into the correct PSA-side client.
Map one integration-side client to another client when records refer to the same organization.
Unlink an integration from a client if the match was incorrect or has changed over time.
Review mapped clients to catch false positives before they affect reconciliation.

Seats and services tabs

Each client also includes supporting views that help you validate the mapping. The seats tab shows devices or usage-side records pulled from integrations.

The services tab shows the agreements, additions, items, or services coming from the PSA that the client is being billed for. Reviewing both sides together helps confirm that the mapping makes sense before you move to discrepancy review.

Why this step matters

Incorrect client mapping can make later discrepancies look larger, smaller, or simply wrong. That is why most organizations review Client Mapping right after their first sync and before spending much time in Billing & Invoices.

Continue to Billing & Invoices