PROCESS RITE · PRACTICAL OPERATING GUIDE
Contractor Merchant Services Onboarding: A Controlled First Invoice
Prepare the account, invoice references and office-to-field handoff before asking customers to use a new payment route.
In this guide: Define which business and work the account covers · Build references around the job · Separate access and responsibilities · Rehearse a staged job · Review the customer-facing request · Launch with a short first-cycle review · An onboarding ownership matrix
Define which business and work the account covers
Describe the services, ordinary job values, billing stages and collection channels accurately during onboarding. Provide requested information through the provider’s approved route. Do not use another business’s account or assume a change in activity is automatically covered.
Assign an office owner for application questions, account access and provider communications. Confirm what remains subject to approval and what evidence the provider requires. An application submission is not confirmation that collection can begin, and a demo account is not a production account.
Build references around the job
Choose a stable job number and an invoice numbering approach before importing balances. A customer may have several projects or several invoices on one project. The payment reference should distinguish the specific obligation being collected.
Decide where the office records deposits, progress collections and final balances. Identify whether the accounting application, project software or another ledger is authoritative. The field employee should be able to identify an invoice without editing the entire customer account.
Separate access and responsibilities
Give field staff only the collection functions their role needs. Keep invoice corrections, refunds and administrative settings under appropriate supervision. Confirm how a departed employee’s access is removed through the supported account process.
Write who answers a customer’s payment question and who contacts the provider about an uncertain result. A salesperson, bookkeeper and technician may all participate, but one person should own each unresolved issue. Include the handoff when the office is closed.
Rehearse a staged job
Use a fictional $2,000 job with a $500 deposit and a later $1,500 balance, before any other applicable amounts. Verify that both payments remain connected to the job and that the second request does not ask for the original full value again.
Now add an approved change order through the business’s normal documentation process. Check how the revised amount reaches the invoice and payment request. An informal text from the field should not silently change the amount the customer is asked to pay without an authorized invoice update.
Review the customer-facing request
Make the business identity, invoice reference and purpose clear. Send payment requests only through the approved workflow and avoid asking customers to email card information. Review the hosted payment page or device path on the kinds of phones customers actually use.
Ask how a customer can obtain a receipt and how the office sees a confirmed result. Do not treat a screenshot of a bank notification as the office’s payment ledger. Resolve uncertain results using the provider’s record before issuing another collection request.
Launch with a short first-cycle review
Start with a limited, supervised set of legitimate invoices rather than migrating every open balance on day one. Compare each collection with the invoice and relevant settlement record. Keep unresolved legacy balances separate so the office does not lose track during the transition.
After the first complete billing cycle, review fees, customer questions and manual corrections against the accepted proposal and workflow. Preserve the account support route and export procedure. The onboarding plan is complete when the office can explain an invoice from request through payment and correction.
An onboarding ownership matrix
List account application, job references, payment-request wording, employee access, invoice allocation, settlement review and first-statement review. Give each one an owner, required input and acceptance evidence. Separate the provider’s approval from the contractor’s own readiness to send a payment request.
Use the first supervised invoice to validate this matrix. The field employee identifies the job, the customer receives the correct request, the office locates the confirmed result and the bookkeeper records the appropriate balance. Note any step that depends on manually forwarding a message.
Does submitted paperwork mean the account is ready? Wait for the provider’s actual confirmation and required setup. Can legacy balances move without a review? Reconcile the opening balances and preserve old references. Who handles a customer’s disputed invoice amount? The contractor’s authorized office process must address the invoice question; technical payment support does not decide the scope of work or project acceptance.
Reference: Clover® device configuration documentation. Reviewed October 17, 2026. The exercises above are proposed operating checks using fictional records, not claims of hands-on testing of every product. Confirm the actual plan, application, account and written proposal.
Continue: POS workflow for contractors · Support routes · Request a free payments review
Request a Focused Payments Review
Tell us your current software, business type and the workflow you want to improve. Arrange document sharing after contact.
