Overview
To check an answering service invoice, match the usage period first, identify what the agreement counts as billable time, apply its rounding rule to each billable event, and then subtract the included allowance. A phone system's total call duration may measure something different from the service's billed minutes. Reconcile those definitions before treating a difference as an error.
Separate the invoice date from the usage dates
Collect the invoice, the agreement or plan terms that applied during the disputed period, and the service's itemized usage report. Record the beginning and end of the usage period and the report's time zone. Confirm whether the boundary includes or excludes a call at the exact cutoff.
One invoice can combine an advance plan charge with earlier usage charges. Ruby's billing article dated February 9, 2026 describes that arrangement. Comparing its entire invoice with only the new month's call log would mix periods. Ask your own provider to identify the dates covered by each line item.
Find the event that starts and stops the meter
For context, the current Ruby article describes one-minute rounding and includes after-call information entry in receptionist time. PATLive's FAQ describes an initial full minute followed by six-second increments. These examples show why raw durations are not interchangeable with billed usage; neither establishes the terms of an AnSer account.
- Ask whether time starts when the receiving service answers or at another event, and whether hold time counts.
- Identify whether time after a transfer is excluded and whether completing a message after the caller disconnects is included.
- Check how outbound attempts, separate transfer legs, short calls, and excluded call types appear in the usage report.
- Confirm the minimum charge and rounding increment for each event. Use the terms effective for this account and period, not an older search result or another provider's rule.
Apply the rule to the itemized events
Use the actual eligible events in the usage report. For a per-event rule, apply the account's documented minimum and rounding increment to each event before adding the billed durations. Rounding the combined raw duration once can produce a different total and does not reproduce a per-event rule.
Keep the raw duration, excluded time, any additional billable components, and calculated billed duration in separate columns. If the agreement does not explain how the minimum and increment interact, request a provider calculation for an actual event before applying an assumed formula to the whole period.
Reconcile the allowance separately from the money
Once billed usage agrees, match it to the included allowance for that same period. Under a simple included-minutes plan, usage above the allowance is multiplied by the applicable overage rate. Confirm whether an allowance is shared across lines and whether tiered rates, plan changes, or credits affect the calculation before applying that model to your invoice.
Keep taxes, setup charges, optional services, credits, and other adjustments on separate lines. An invoice total divided by a per-minute rate is not a reliable way to reconstruct usage when the invoice includes other charges. Do not assume unused minutes carry into a later period.
Send a discrepancy that someone can reproduce
- Record the invoice identifier, usage period, and the specific call or event IDs that do not reconcile.
- Show the reported duration, applicable rule, your expected billed duration, and the billed value for each example.
- Ask for clarification when the report omits a billable component; an unexplained difference is not yet a confirmed overcharge.
- Share only the information needed through the provider's approved support channel. A billing inquiry usually does not need the caller's message or a recording.
- Keep the provider's explanation and any adjustment reference with the reconciliation so the next period can use the corrected interpretation.
