Billing engine

Overview

The billing engine turns each location's parkers, rate codes, and activity into monthly invoices. It is designed to handle the cases legacy parking AR systems make you work around — mid-month changes, employer/parker splits, per-location tax — so a full cycle runs in minutes instead of days.

Rate codes

A rate code defines what a parker is charged and how. Rate codes belong to a location and capture the base monthly amount, any tax treatment, and the GL accounts charges post to. Assign a rate code to a parker's agreement and the engine uses it every cycle.

• Define base amounts per location and per parker type.
• Map each rate code to revenue and receivable GL accounts.
• Report on rate-code usage live, without waiting for month-end.

Proration

When a parker starts, stops, or changes rate mid-month, the engine prorates the charge for the days the agreement was active. You set the proration basis per location; the engine applies it consistently and shows the calculation on the invoice line.

Charge splitting

Corporate accounts often split a parker's charge between an employer and the employee — for example, the employer pays 60% and the parker pays 40%. Configure the split on the account, and the engine generates the right invoice to each party automatically, keeping the receivable balances separate.

Late fees, adjustments & tax

Late fees apply per your location's policy when an invoice ages past due. Adjustments let you credit or add to a balance with a reason that lands in the audit log. Tax is applied per location and rate code, so multi-jurisdiction portfolios stay correct.

Running a billing cycle

Billing runs follow a preview-then-post flow so nothing is a surprise:

1. Preview — generate the run for a location and period. The engine shows every invoice it will create and flags exceptions (missing rate codes, ended agreements, unusual amounts).
2. Review exceptions — resolve flagged items, or let the Collections and audit agents surface anything that looks off as approval-gated proposals.
3. Post — commit the run. Invoices are issued, GL entries post, and parkers with auto-pay are queued for collection.