PROCESS RITE · CONTRACTOR PAYMENT GUIDE
Contractor Monthly Minimum Fee Review: Eligible Charges and Shortfalls
Read the account’s monthly minimum definition, identify eligible charges and reproduce the shortfall calculation. Compare complete costs across quiet and busy months before deciding what to change.
In this guide
- Start with the contracting business’s actual collection records
- Keep the job ledger in control of the balance
- Distinguish a monthly minimum from a fixed monthly service fee
- Calculate a fictional shortfall with an explicit definition
- Identify which charges count toward the threshold
- Review quiet and busy periods separately
- Confirm first-month and closure treatment
- Check multiple locations and accounts on their own scope
- Evaluate an alternative with no stated minimum fairly
- Ask for a precise explanation or correction
- Maintain a minimum-fee control sheet
- Who should approve the review?
- Prepare the review without exposing private records
- Sources and review scope
- Related guides for your business
- Keep an acceptance checklist
- Discuss the configuration you actually need
Start with the contracting business’s actual collection records
A contracting business can have uneven collection while work continues across job stages. Use the actual eligible-charge period rather than the value of jobs under contract. A future invoice or expected deposit does not establish that the account threshold has been met this month.
Model a quiet collection period and a month with several approved stage payments. Preserve separate equipment, invoice software and account costs. Before requesting suspension or closure, confirm how open invoices and historical correction access will be handled through the relevant providers.
Keep the job ledger in control of the balance
The job or invoicing application should identify the agreed work, approved changes, payments and remaining balance. A payment receipt alone may not show whether the correct invoice was updated. Record which system owns the balance and how a field collection reaches it. If the update is manual, name the person who completes it and the check that prevents a second collection request.
Use an approved change order in the demonstration. A field employee should not invent a higher payment amount merely because the customer mentions additional work. Confirm how the authorised amount reaches the invoice and how the customer sees the revised balance. Payment permission, job approval and accounting access are separate responsibilities.
Separate a deposit from earned work and progress billing in the records used by your bookkeeper. For an illustrative job, an initial collection reduces the amount still to collect but does not by itself establish revenue recognition or contractual completion. Have the business’s advisers approve accounting treatment and the wording of any payment schedule.
Test a field connection failure after the customer attempts payment. The employee and office should find authoritative transaction status before retrying. A successful charge with a failed invoice posting requires a record correction; a confirmed failed transaction may require another supported attempt. An unresolved result needs investigation rather than a second invoice or an improvised charge.
For closeout, retain the job, invoice, payment and settlement references. The date a job is completed may differ from the date a customer pays and from the bank deposit date. Keep those timelines visible. Avoid sending private customer records, full card details or bank credentials through an ordinary support enquiry.
Distinguish a monthly minimum from a fixed monthly service fee
Read the agreement’s definition before interpreting the statement. A monthly minimum may describe a threshold against specified eligible charges, while a fixed service fee may be billed independently. Similar wording on a dashboard is not enough to establish whether the two amounts are interchangeable or both apply.
Obtain the account-specific amount, period and list of eligible categories. Ask how the shortfall is calculated and whether the displayed line is the minimum itself, an additional shortfall or another fee. Keep the provider’s written explanation with the schedule in effect for the month.
Do not assume sales volume is the qualifying amount. A minimum based on eligible processing charges answers a different question from a minimum required sales volume. Identify the exact basis and units before using a calculation or comparing another provider’s proposal.
Calculate a fictional shortfall with an explicit definition
Suppose a fictional agreement defines a $25 minimum against a specified set of eligible charges. If those charges total $17, the illustrative shortfall is $8, giving $25 across the eligible charges and shortfall together. This assumes that exact structure; it is not a universal rule for every provider.
If the eligible charges are $31 under the same fictional structure, the additional shortfall is zero. It would be incorrect to add another $25 merely because the minimum appears in the agreement. Equally, an excluded monthly software fee would not automatically reduce the shortfall.
Write the assumed formula and eligible categories beside the example. Compare the statement’s actual presentation with the provider’s explanation before concluding that an amount was charged twice. A correct arithmetic result on the wrong eligibility definition still produces an unreliable billing conclusion.
Identify which charges count toward the threshold
List the statement categories and mark each as eligible, excluded or awaiting confirmation. Ask about percentage charges, per-item amounts and separately billed services individually. Do not treat the total statement expense as the qualifying amount unless the actual terms say so.
Keep a source reference for each decision. A provider response should identify the applicable category and period, rather than offering only a general assurance that the minimum is normal. Where the answer changes an earlier interpretation, retain the corrected worksheet so the next reviewer does not repeat the same error.
Calculate the eligible total once, excluding duplicated summary and detailed amounts. Then apply the documented minimum calculation. Keep other charges in the complete-cost comparison even when they do not count toward this particular threshold.
Review quiet and busy periods separately
Choose representative periods from the business’s actual operating cycle. Keep the same eligibility definition while showing how different activity affects the minimum calculation. A quiet month can expose a shortfall that is absent in a busy month, without implying that either statement is necessarily incorrect.
Use fictional planning figures when future activity is uncertain and label them clearly. Show the eligible charges, potential shortfall and other costs separately for each scenario. Do not promise that next month’s sales will remove a charge or justify spending more merely to reach a threshold.
Compare an annual view only after the individual periods are understood. A single busy month should not stand in for a seasonal business’s full year. Retain uncertainty in the model rather than choosing a favourable period that makes one proposal appear cheaper.
Confirm first-month and closure treatment
Ask how the agreement treats activation, partial billing periods, account changes and closure. Do not assume a minimum is prorated, waived or stopped by inactivity. Record the provider’s confirmed rule and any dated amendment or cancellation acknowledgement relevant to the period.
Distinguish an unused device from a closed merchant account or cancelled software subscription. These may involve separate services and obligations. Have the responsible owner verify the status of each before interpreting a continuing charge or submitting a commercial change request.
Keep the final statement and any later adjustment under review until the agreed treatment is visible. A request to close an account is not itself evidence that every related service has ended. Obtain confirmation through the relevant providers without sharing credentials or sensitive bank records in general enquiries.
Check multiple locations and accounts on their own scope
Identify whether the minimum applies per merchant account, location or another documented scope. A business with several routes should not pool eligible charges merely because the same owner receives the statements. Confirm the actual aggregation rule before combining amounts.
Build one row per applicable scope with its threshold, eligible charges and resulting calculation. Retain separate service costs and any shared items. If the provider allows a combined treatment, obtain the written basis and effective date rather than assuming the billing system automatically recognises common ownership.
Use the location and channel references consistently in the operating review. Consolidation can affect more than cost, including reporting and account configuration. Do not move activity between accounts to influence a minimum without the providers’ approval of the business arrangement and collection methods.
Evaluate an alternative with no stated minimum fairly
A proposal without a monthly minimum can still include transaction, software, equipment or other service charges. Compare the same collection routes, realistic volumes and required features. Keep an unanswered fee field unresolved rather than treating a missing quote item as free.
Model quiet and busy periods under both written structures. Show one-time costs separately and include any obligations associated with changing services. The useful result is a complete supported comparison, not a general claim that one pricing model is always better.
Ask the proposer to confirm any conditional waiver and its duration. A promotional exception is different from a permanent account term. Record what happens after the stated period and who must authorise the final proposal before staff or customers rely on the new setup.
Ask for a precise explanation or correction
Provide the period, exact line, agreed minimum and your eligible-charge calculation through the verified support route. Explain which categories you included and ask which provision determines any difference. This gives the provider a question it can answer with a definition or calculation.
Distinguish a confirmed billing correction from a request to negotiate future terms. Both can be useful, but they should not be recorded as the same outcome. A change in future pricing does not explain a past amount unless the provider explicitly addresses that period.
Retain the case reference, effective date and expected next action. Verify a promised credit or change on the relevant later statement. Close the review when the billing evidence supports the conclusion, while preserving any separate commercial decision about whether to continue the service.
Maintain a minimum-fee control sheet
Record the applicable scope, threshold, eligible categories, source schedule, period, calculation and billed shortfall. Add other periodic charges in a separate column so the complete cost remains visible. Retain any excluded items with the explanation for excluding them from this calculation.
Have another authorised reviewer reproduce a quiet month’s result and a busy month’s result. They should be able to explain why the eligible total differs from total statement expense and why the shortfall changes. If the definition remains unclear, leave the conclusion open and request clarification.
Review the sheet after a dated pricing or configuration change. A worksheet built for the old scope may no longer apply. Keep the earlier version for historical questions rather than overwriting the assumptions that explain previous statements.
Who should approve the review?
Have the office reconciliation owner confirm the operational references and the financial owner confirm the statement calculation. Ask the provider to explain the applicable terms. Keep unresolved items and any accepted commercial change separate, with a named owner and an effective date. Use a non-sensitive summary for an initial enquiry rather than attaching customer or bank records.
Prepare the review without exposing private records
Summarise the business, current software, payment channels, locations and the specific job invoice problem you want resolved. Include a non-sensitive example and the outcome you expected. That gives a review more direction than a general request for better rates or a new device. List existing components you want to retain so proposals account for them.
Process Rite helps organise the payment requirements, provider questions and written comparison. Availability, integration, account approval, implementation and service terms need confirmation in the applicable proposal and provider agreement. Hardware, software, applications and processing charges should remain identifiable. Request a custom proposal based on the configuration and channels your business actually needs.
Use the website enquiry for the summary, then arrange document sharing after contact. Do not submit payment credentials, bank logins, passwords or private customer records. Include your town and preferred callback time so the conversation starts with the right context. Consultations and any site work are arranged directly. Confirm the responsible support contact and available service hours in the proposal.
Sources and review scope
Documentation reviewed October 17, 2026. Provider documentation supports product-specific facts; it does not confirm another provider’s terms or the suitability of an individual configuration. These operating examples are proposed checks, not reports of hands-on product testing. Worked amounts and records are fictional.
PAYARC: example provider change form showing separately identified fee fields
Related guides for your business
Contractor deposits and field payments
Contractor invoice links and online collections
Contractor collection and office handoff
Keep an acceptance checklist
- The minimum amount and eligible charge categories are documented.
- The comparison period and shortfall calculation are reproduced.
- Other periodic and transaction charges remain visible.
- Seasonal and multi-account effects are compared on consistent assumptions.
Discuss the configuration you actually need
Tell Process Rite your business type, town, current software and the specific question to review. Start with a non-sensitive summary and arrange document sharing after contact. Do not submit payment credentials, bank logins or private customer records.
Equipment, software, applications and implementation are separately quoted. Availability, integration, approval, pricing and service terms need confirmation in the applicable proposal and provider agreement. A review does not guarantee savings, approval, legal compliance or a dispute outcome.
Request a free payments review · Review the complete cost · Find the right support route
Request a Focused Payments Review
Tell us your current software, business type and the workflow you want to improve. Arrange document sharing after contact.
