Start with one reporting period
Before you compare sales and accounting records, agree a reporting cutoff, one legal entity or business unit, and one currency. Mixing different periods or currencies can manufacture discrepancies. Capture when every export was taken and whether it includes archived, refunded, or voided records.
Check 1 — Confirm record identity
Collect the minimum agreed fields: a durable deal or project identifier, invoice identifier, customer identifier where appropriate, dates, amount, currency, status, and payment allocation ID. Never match only on a person's name when trustworthy IDs are available.
Check 2 — Agree what "won" means
Your CRM's closed-won date may not be the billing trigger. Compare contracts, deposit terms, milestones, acceptance criteria and retainer cycles before treating an uninvoiced opportunity as an exception.
Check 3 — Match billing to deliverables
For each scoped engagement, map expected billing events to invoices. Partial invoices, credit notes, tax treatment, recognized adjustments and cancellations need explicit handling. Keep the underlying source row linked in every flagged item.
Check 4 — Reconcile payments by allocation
One bank payment might settle multiple invoices; one invoice might be paid in installments. Prefer invoice-payment allocation records over guessing from transaction amount and date. Reconcile unapplied cash without assuming it is available revenue.
Check 5 — Apply cutoffs consistently
An invoice created after your cutoff does not necessarily represent a missed invoice. Likewise a payment posted after the reporting period can explain an apparently outstanding balance. Classify these separately from unexplained mismatches.
Check 6 — Rank questions rather than claims
Make an exception register with four useful fields: what appears different, the exact source records involved, the business owner who can confirm it, and the next evidence request. An exception is a question, not a collectible dollar amount.
Check 7 — Confirm privacy and authority
Deal, invoice and payment exports may contain personal data or commercially confidential information. Identify an authorized sender and recipient, define purpose and retention, limit fields, and agree secure transport before real exports are transferred. Do not send raw records in a website inquiry.
Check 8 — Test one resolution path
Pick a small validated exception and document the root cause and process correction. Possible fixes include common record IDs, invoicing checklists, approval deadlines or clearer handoffs. Do not automatically edit accounting or payment systems.
What a useful result looks like
A good review produces a traceable list of exceptions and non-exceptions, a source mapping, ranked validation questions, and a clear owner for each next action. It should also disclose unmatched inputs, ambiguous IDs and the limits of the review.
Ask Praximere
Praximere's proposed Revenue X-Ray is an export-first, fixed-scope pilot. Inquiry discussions are available; paid work and client-file intake require final terms and operating readiness. You can request a fit discussion without attaching confidential financial records.