Need to pay a fine, fee, or bill? Use the link on your notice or your agency’s website.

Information for people making a payment

Revenue distribution

Revenue distribution does not move money. Each agency account receives one deposit. Distribution applies your allocation policy to the settled payments in that deposit and produces the journal entries and recipient reports finance staff use to post it by fund and to remit state and other shares from the agency’s own bank account.

Allocation policies

Define recipients, scope, calculation order, holds, and schedules. Review the result before activation and keep the version that was used.

Recipient directory

Each recipient record holds the recipient type, remittance details, contacts, general ledger segments, statutory references, and approval status.

Policy scope

Finance staff select eligible transactions by payment type, location, portal, reference, date, amount, or other conditions.

Ordered rules

Rules apply fixed amounts, percentages, conditions, and remainders in a defined order. Court technology fees, victim services surcharges, and state remittances are common examples.

Settlement holds

Hold periods and eligibility rules by payment method determine when a transaction enters a distribution run.

Schedules

Policies run manually or on an agency-defined schedule. The next and previous run are shown.

Recipient reports

Each recipient’s contacts receive a PDF summary and CSV detail for the batch.

Simulation and approval

Finance staff see the output of a policy before it runs and retain the exact version used afterward.

  • Interactive simulator with amount, fee, and remainder tracing
  • Validation of rules, schedules, recipients, and policy overlap
  • Activation sign-off and approval controls
  • Dry runs with recipient totals before a batch is created
  • Policy versions, change history, pause, resume, archive, and duplicate
Allocation preview$100.00 fine
General fund60%$60.00
Court technology fund25%$25.00
Victim servicesRemainder$15.00

Batches and reports

1. Run

Execute a validated policy for an eligible transaction period.

2. Calculate

Apply the ordered rules and keep the trace for each transaction.

3. Lock

Create a batch with control totals, the policy version, hashes, and exclusions.

4. Report

Produce recipient summaries, transaction detail, notifications, and journal-entry exports.

Exceptions and permissions

Exception queue

Staff filter open items, review the source transaction or run, resolve with a note, dismiss when appropriate, or run again.

Allocation trace

The trace shows which policy, rule, basis, amount, and running remainder produced each recipient allocation.

Permissions

Viewing, configuration, approval, and execution are separate privileges for finance, administration, and audit roles.

Batch exports

Each batch exports allocation, transaction, recipient, and journal-entry CSV files for the general ledger.

Recipient reports

Finance staff generate a print-ready PDF summary and CSV detail for each recipient in a batch.

Audit history

One record keeps policy changes, activations, runs, resolutions, user actions, and timestamps.

Payout and distribution questions

All questions and answers

Evaluate the platform with your own payment types