Reconciliation

Tie billing, ERP/GL, tax engine, preparer, and filed-return totals together before signoff.

  • Sales, purchasing, and combined reconciliation in one approval queue
  • Source ownership, system-of-record anchor, deltas, materiality, and exception taxonomy
  • Fail-closed signoff plus marketplace and collected-versus-remitted controls

How the work moves through ITMS

Reconciliation is the cross-system tie-out workspace for tax teams working across customer-owned, third-party, and Prophit-managed systems. It supports programs where Prophit.ai is the tax engine, the preparer, both, or the reconciliation layer.

One module covers sales, purchasing, and combined oversight. Runs preserve source snapshots, ownership, materiality, exceptions, adjustments, evidence, and approval history across internal pre-compliance and external pre-filing stages.

Inputs
  • Source-system totals and counts from billing, payment, ERP/GL, AP, tax engine, preparer, and filed returns
  • Period, state scope, filing deadline, basis, materiality, ownership, and system-of-record selection
  • Manual or detected exceptions, adjustments, documents, notes, links, and exports
  • Marketplace responsibility evidence and remittance-ledger entries where those controls are used
Operational outputs
  • Matched percentage, unreconciled amount, exception counts, and pending approvals
  • Source comparison matrix and exception-category rollups
  • Prepared, reviewed, approved, rejected, reopened, and filed history
  • A documented handoff from internal source tie-out to preparer and filed-return reconciliation

A two-stage tie-out with an explicit approval trail

Reconcile internal systems before data goes to a preparer, then reconcile what was sent with what the preparer processed and the authority ultimately received.

  1. 01

    Create the run and scope

    Choose sales, purchasing, or combined domain; internal pre-compliance or external pre-filing stage; tax or taxable basis; period, states, deadline, owner, and materiality.

  2. 02

    Snapshot every participating source

    Record billing, payment, ERP/GL, AP, tax-engine, preparer, or filed-return totals as manual, imported, computed, or connector snapshots, with customer, third-party, or Prophit ownership.

  3. 03

    Choose the system of record

    Mark the anchor source and compare every other source’s gross, taxable, tax, transaction-count, and headline amount against it.

  4. 04

    Detect and triage variances

    Generate source-delta candidates idempotently and classify missing records, tax/rate, jurisdiction, timing, non-taxable exclusions, rounding, GL mapping, or preparer adjustments.

  5. 05

    Explain, adjust, and attach evidence

    Assign exceptions; move them through open, investigating, explained, adjusted, accepted, or resolved states; record adjustments; and attach documents, notes, links, or exports.

  6. 06

    Review, approve, and tie to filing

    Submit, review, approve, reject, reopen, and mark filed through a recorded event trail. Material open exceptions and applicable remittance blockers prevent unsafe signoff.

What your team can operate

Cross-system source comparison

Model the systems as they actually exist, including ownership boundaries.

  • Billing, payment, ERP/GL, AP/purchasing, tax engine, preparer, and filed-return source roles
  • Customer, third-party, and Prophit ownership badges
  • Manual, import, computed, and connector snapshot methods
  • System-of-record anchor with per-source delta, match rate, and unreconciled amount

Exception and resolution ledger

Make every difference classifiable, owned, and explainable.

  • Nine explicit exception categories across missing data, tax, jurisdiction, timing, exclusions, rounding, mapping, and preparer changes
  • Dollar and percentage materiality thresholds
  • Assignee, jurisdiction, reference, description, and status on each variance
  • Adjustment records, evidence items, category rollups, and append-only activity history

Operational signoff controls

Connect a balanced tie-out to filing through recorded preparation, review, and approval states.

  • Draft, in-review, approved, rejected, reopened, and filed run states
  • Prepared, reviewed, and approved attribution and timestamps
  • Pending approvals, next filing deadline, domain rollups, and exception KPIs
  • Marketplace reconciliation exceptions and collected-versus-remitted ledger panels

What stays explicit

Works across ownership boundaries

The module stores each source snapshot with ownership and method. Third-party and preparer totals remain identified as supplied values unless a configured computation is available.

Material exceptions block signoff

Approve and mark-filed actions are withheld and rejected while a material exception remains open or investigating.

Remittance can fail closed

For scoped external pre-filing runs, overlapping open collected-versus-remitted exceptions can block the filed transition until resolved.

Custom Enterprise reconciliation

Reconciliation is an entitlement-gated custom Enterprise module. Source adapters, computed totals, preparer connections, marketplace controls, and remittance integrations depend on your systems and implementation scope.

Ready to plan the next step?

Show us which systems own billing, GL, tax calculation, preparation, and filing so we can map the right reconciliation stages and controls.