Guide
This guide walks through a practical client reconciliation workflow in BillingReconcile. It is meant to help your team move from fresh synced data to a clear understanding of billing discrepancies and what to do next.
Start by making sure the integrations relevant to the client are healthy and recently synced. If data is stale or a sync failed, later results may be misleading.
Review Integrations StatusCheck that the integration-side client is correctly linked to the right PSA-side client. If the client is unmapped or mapped incorrectly, fix that first before spending time investigating discrepancies.
Pay special attention to AI-suggested matches and confirm they are accurate for the organization you are reviewing.
Review Client MappingConfirm that the PSA services or billing items for this client are being compared against the right usage source. If service mapping is incomplete or too broad, the discrepancy view may not reflect your intended billing model.
Review Service ManagementOnce setup looks sound, move into Billing & Invoices and locate the client in the reconciled invoices table. Review the seat count, service count, discrepancy count, discrepancy amount, and billing cycle information.
If you are triaging a busy workspace, start with the clients that show the highest absolute discrepancy amount.
Open Billing & InvoicesOpen the client detail view to inspect how the result was calculated. Look at which billing services were mapped to which integrations, the invoiced quantity, the system count, the unit rate, and the estimated or calculated values behind the discrepancy.
Use the integrations, seats, and services tabs to confirm whether the issue is caused by sync freshness, client mapping, service mapping, or a real billing gap.
Once you understand the issue, decide what follow-up is appropriate. Some discrepancies are setup-related and should be fixed through mapping. Others point to real billing gaps and may require an adjustment or PSA follow-up workflow.
By the end of a client reconciliation review, your team should understand whether the discrepancy is caused by stale data, mapping setup, or a real billing issue. That clarity is what makes the next action meaningful instead of reactive.