How Accounting Firms Can Manage Client Billing Inside Payroll Relief

Payroll processing creates two financial workflows at once.

The obvious one is the client’s payroll: wages, taxes, direct deposits, and other liabilities.

The second is the accounting firm’s own revenue for providing the payroll service.

Payroll Relief supports that second workflow directly. Current IRIS documentation says firms can configure payroll-processing and compliance charges for individual employer clients and, when properly authorized, automatically debit those fees from the employer’s bank account through ACH.

For an accounting firm building a scalable payroll practice, this turns billing from an after-the-fact administrative task into part of the payroll operating model.

Client Billing Requires Authorization First

Automatic billing should not begin simply because an employer’s bank account is already used for another electronic payroll service.

IRIS documentation specifically requires the accounting firm to confirm that the employer has authorized automatic payroll-processing charges. Payroll Relief provides an Employer Billing Authorization form that the firm can retain as evidence of that consent.

That creates an important distinction:

Employer payroll funding authorization concerns money used for payroll and related liabilities.

Payroll-service billing authorization concerns money the accounting firm charges for its own services.

Even when the same bank account is involved, those are separate purposes.

A well-controlled client file should preserve the billing authorization alongside the service agreement and fee schedule rather than relying on the fact that ACH billing happens to be enabled in the software.

The Firm’s Receiving Bank Account Is a Global Setting

Before automatic client billing can operate, the accounting firm must enter the bank account that will receive its processing fees.

IRIS states that the bank information maintained on the Firm Bank tab applies globally to employer processing charges.

That makes a firm-bank change much more significant than a single-client configuration change.

If the firm changes banks, the update potentially affects fee receipts across its entire payroll portfolio.

A useful internal control therefore treats changes to the firm’s billing bank information as privileged administration.

The firm should know:

• who requested the change;
• who entered it;
• who independently verified it;
• when the new account became effective;
• whether the first subsequent credits were reconciled.

The need for those reviews is an operational recommendation, but it follows from the global scope of the setting.

Flat Monthly Fee or Fee Per Payroll?

Payroll Relief supports more than one billing model.

Current IRIS documentation describes options including a flat monthly fee and a fee per payroll, with additional configurable charges for payroll and compliance activity.

These models fit different service arrangements.

Flat Monthly Billing

A fixed monthly amount can work well when the firm’s service includes predictable recurring support and the client values a stable bill.

The accounting firm absorbs some variation in processing volume in exchange for predictable revenue.

Fee Per Payroll

Per-payroll pricing tracks processing activity more directly.

It can be appropriate when clients have different pay frequencies or when additional payroll runs materially increase the firm’s workload.

The important point is not which model is universally better.

It is making sure the system configuration matches the client’s signed commercial terms.

Approval Can Create the Billing Event

IRIS explains that payroll-processing charges are tied to payroll activity and that fees can be calculated when payroll is approved rather than merely when a pay date arrives.

That linkage creates an operational consequence.

An unnecessary Additional Payroll or mistakenly approved payroll can affect both payroll records and client billing.

The review process therefore needs to consider whether an unusual payroll should generate a charge under the firm’s agreement.

A correction payroll may be technically legitimate while still requiring the firm to decide whether the related processing fee should be passed to the client.

Software calculation and commercial judgment are not always the same thing.

Payroll Relief Can Bill More Than a Base Fee

The Processing Charges configuration supports several fee components.

Current documentation includes base payroll charges, per-check charges, additional payroll-processing charges, and compliance-related charges.

This allows firms to reflect a more nuanced pricing model.

For example, a client with five employees and weekly payroll may create a different workload from a client with 200 employees running semi-monthly payroll.

However, detailed billing models also create greater reconciliation complexity.

The firm should be able to explain an invoice without opening several configuration screens and reverse-engineering the calculation.

Automatic Billing Has Its Own Transaction Cost

IRIS’s current Processing Charges documentation states that a processing fee is charged for each bank transaction used in the billing process.

That means billing frequency can affect the firm’s own economics.

Frequent individual debits may produce different transaction costs from consolidated monthly billing.

For a large client portfolio, small transaction-level costs can become material when multiplied across hundreds of employers and twelve months.

Pricing decisions should therefore consider both client simplicity and the firm’s transaction costs.

Funds Do Not Arrive Instantly

Current IRIS documentation says client processing charges credited through this billing mechanism reach the firm’s account after the defined banking-day settlement period; the documentation currently describes credits occurring five banking days after the debit.

A firm should not treat a charge appearing as billed as identical to cash already received.

Its revenue reconciliation can distinguish:

incurred

pending

debited

credited

exception

That is especially important around month-end.

Use the Processing Fee View as a Receivables Control

Payroll Relief allows firms to review pending and billed processing charges by employer and date range.

That view can support a simple recurring control.

At least periodically, compare:

fees expected under the firm’s pricing arrangement;

fees created by payroll activity;

amounts marked billed;

amounts actually received in the firm’s bank account.

A difference may indicate a configuration issue, failed ACH activity, client account problem, waived charge, or timing difference.

Without reconciliation, automated billing can create the illusion that receivables no longer require management.

Practice Relief Adds a Different Billing Model

Payroll Relief also has an integration path with Practice Relief for firms that want more detailed time and activity billing.

IRIS documentation says payroll activities can be linked to task and expense codes in Practice Relief. When Standard or Additional payrolls are approved, the integration can create associated task and expense activity that can later support itemized client invoices.

This is conceptually different from simple automated Payroll Relief processing charges.

The firm has two possible approaches:

transaction-based payroll billing inside the payroll service;

or

practice-management billing based on tasks, expenses, and broader client work.

Some firms may use one model consistently. Others may combine them for different service tiers.

Standardize Pricing Before Automating It

Automation magnifies configuration.

If 100 clients have inconsistent fee settings, automated billing simply processes those inconsistencies faster.

A firm scaling Payroll Relief should therefore maintain a pricing matrix defining:

• service tier;
• payroll frequency;
• base fee;
• per-check or per-employee fee where used;
• Additional Payroll treatment;
• quarterly compliance fee;
• year-end W-2 or 1099 treatment;
• special service charges;
• automatic ACH billing status;
• effective date of pricing;
• authorization evidence.

The software should implement the commercial policy rather than become the only place that policy exists.

Pricing Changes Need an Effective Date

Client fees evolve.

A firm may increase monthly pricing, change from per-payroll to subscription billing, or introduce a new compliance fee.

The change should have:

a communicated effective date;

appropriate client authorization where necessary;

updated Payroll Relief configuration;

verification after the first billing cycle.

Without an effective date, it becomes difficult to answer whether an older payroll should have used the old or new pricing.

Billing Exceptions Belong in the Practice Queue

Most billing will be routine.

Exceptions deserve attention.

Examples include:

client billing authorization missing;

bank debit failure;

unexpected fee amount;

duplicate charge;

client dispute;

firm bank-account change;

waived fee not reflected;

new client accidentally left without billing configuration.

These exceptions should have owners just like rejected tax filings or payroll funding failures.

Client Billing Should Reconcile to the Service Agreement

Payroll Relief can calculate and move a processing charge.

It cannot determine whether the accounting firm’s commercial agreement was fair, correctly communicated, or appropriately amended.

The strongest billing process therefore connects three layers:

client agreement → Payroll Relief fee configuration → bank reconciliation

When those three agree, automated billing saves substantial administrative work.

When they do not, automation can make a pricing mistake repeat every pay cycle.