Skip to main content
GullySystem
Automotive

Invoice Management for Wheel alignment centres

Bill the accepted alignment assessment or actual completed work without treating every machine check as an adjustment.

Finance & Accounting

Does this function belong in your operation?

Use when the centre needs to connect check-only outcomes, adjustments, related services and account work to their agreed payer. Invoicing is distinct from the technical findings and vehicle handback.

An accepted assessment, completed service or other agreed charge becomes billable under the visit’s terms.

Bill the chargeable check or work actually completed against the accepted scope. Keep a check-only visit distinct from a completed adjustment, and preserve the payer agreed for a referred vehicle. Repeated visits need an explicit billing decision instead of an automatic charge or credit. Receipt allocation, refund execution, technical outcome and vehicle handback remain separate records.

Bring the records the workflow depends on.

  • Visit identity and actual work statement
  • Accepted price revision and check-only charging terms
  • Customer or referring-account debtor details
  • Authorised credits, advances and prior invoice references
  • Numbering and accountant-confirmed tax settings

Outputs to check

  • Issued bills linked to check or adjustment visits
  • Unbilled accepted work and disputed-addition list
  • Customer balances after confirmed receipt allocation
  • Credits and refund decisions linked to payment outcomes

Follow the invoice management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the actual charge

    Read the visit outcome and accepted terms. Distinguish assessment performed, adjustment completed, separately scoped balancing and work not done.

  2. 2. Confirm payer and amounts

    Check the customer account and any referring-garage agreement. Compare lines with the accepted revision and retain the basis for an authorised change.

  3. 3. Review and issue

    Resolve duplicate visit references and disputed additions before issue. Preserve the issued document under the configured numbering rules.

  4. 4. Allocate confirmed payments

    Match received amounts and accepted advance allocations to the bill. A message saying payment was sent is not a confirmed receipt.

  5. 5. Resolve later adjustments

    Record the authorised credit or refund decision without replacing the bill. Keep refund instruction and confirmed payment execution separate, and link a repeat visit to its own charge decision.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Billing assistant

Builds lines from the completed visit and accepted prices; does not bill from every proposed recommendation.

Service adviser

Explains differences between accepted scope and actual work, preserving the customer’s decision.

Account approver

Authorises commercial corrections and referral-account arrangements within assigned limits.

Payment reconciler

Checks actual receipts, allocations and refund outcomes against their external evidence.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

No adjustment was performed

Apply the accepted assessment terms. Do not use a completed-alignment charge solely because a measurement sheet exists.

Repeat visit requests a free service

Record the commercial review and technical visit separately. Neither a free repeat nor a new charge follows automatically from a returning complaint.

Referring garage disputes the debtor

Check the commissioning agreement before changing the account. Vehicle delivery by a garage does not establish that garage as the payer.

Partial payment or refund

Keep the unpaid balance or pending refund visible until actual amounts are confirmed. Approval alone does not settle either record.

Can this work independently?

Invoicing can use entered accepted lines without a sales-order or stock module. Job cards and estimates supply the service basis. Accounting, receipt collection and refund execution remain separate handoffs. The accountant confirms document and tax requirements; technical staff determine the work outcome.

Systems and records it connects with

  • Job record: actual check, adjustment and unresolved findings.
  • Accepted estimate: rates, scope revisions and payer agreement.
  • Receipts and accounting: confirmed allocations and remaining balance.
  • Credit and refund records: authorisation, instruction and actual payment outcome.

Configure, test and introduce the workflow.

  • Reconcile check-only, completed and referred visits against their original terms.
  • Test a fleet-account payer dispute and a repeated complaint with a pending charge decision.
  • Check partial payments, a duplicate visit bill and a refund awaiting execution before adopting the billing flow.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Each billed service is supported by actual work and accepted charging terms.
  • A proposed but declined service remains outside the bill.
  • Repeat visits and credits retain their original references.
  • Settlement status depends on confirmed allocations, not job closure.
Wheel alignment centres

How the business operates.

A driver brings a steering-pull complaint; the desk has a booking, but the bay needs the vehicle identity and the earlier readings. Alignment-centre software should connect the accepted check, machine record, technician findings and customer decision. A measurement is not permission to adjust or replace anything. This scope covers fixed-site centres handling vehicles within their declared equipment and staff capability. Balancing, tyre supply, suspension repair and specialist electronic calibration remain separately scoped work. The workflows below are requirements examples to adapt with the centre, not evidence of an installed system.

Reception and referral intake

Record the complaint in the customer’s words, vehicle details, referring garage and paying account. A referral does not tell the desk who can authorise extra work. Keep the person bringing the vehicle distinct from the person accepting the bill.

Alignment bay

Attach the relevant initial measurement and the vehicle specification reference selected by the qualified technician. Preserve the machine identity and the observed condition that limits work. The technician decides whether assessment, adjustment or referral is appropriate.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Vehicle identity, complaint and referring-party record
  • Accepted check or adjustment estimate and revision history
  • Machine and specification-reference record for the visit
  • Initial and subsequent readings with visit identity and technician

Operational bottlenecks to check

A coloured result becomes a repair order

The desk needs a clear boundary between a machine result, a technical recommendation and accepted paid work. A result alone does not explain every steering complaint.

A repeat visit loses its earlier evidence

Link the new visit to the earlier job while retaining its own date, complaint and readings. A changed condition or new tyre work must not be mistaken for the same measurement event.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Accept the visit

    Confirm the vehicle type and the requested check against the centre’s declared capability. Record who commissions the work and the account to charge before treating a garage referral as an accepted job.

  2. 2. Establish the measurement context

    The technician records the vehicle reference and relevant observations. Keep a quick-check result distinct from a completed alignment record. Missing or conflicting identity details require review before evidence is attached to the job.

  3. 3. Present the findings and scope

    Retain the proposed work and its price revision. A worn component or unavailable technical reference can lead to a limited assessment or outside referral. Customer consent does not replace the technician’s decision about proceeding.

  4. 4. Record what was actually done

    Link work entries and subsequent readings to the same visit. A check-only visit stays check-only. If additional work is accepted, record its revision and who authorised it; do not overwrite the original complaint.

  5. 5. Review, explain and reconcile

    The responsible technician records the outcome and unresolved findings. Hand the relevant evidence to the permitted customer contact. Send actual chargeable lines to accounts and release bay capacity only when physical use has ended.

Industry reports to connect with

  • Checks completed without adjustment, with stated outcomes
  • Jobs awaiting customer decisions or outside repair
  • Initial and subsequent readings missing a matching visit reference
  • Bay occupation and equipment-block exceptions

Questions before implementation.

When should wheel alignment centres consider invoice management?

Use when the centre needs to connect check-only outcomes, adjustments, related services and account work to their agreed payer. Invoicing is distinct from the technical findings and vehicle handback. An accepted assessment, completed service or other agreed charge becomes billable under the visit’s terms.

What should we bring to the requirements discussion?

Bring anonymised examples of Visit identity and actual work statement; Accepted price revision and check-only charging terms; Customer or referring-account debtor details; Authorised credits, advances and prior invoice references; Numbering and accountant-confirmed tax settings. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Bill the accepted alignment assessment or actual completed work without treating every machine check as an adjustment. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A bill does not prove correction of a steering fault, technical release, receipt of money or completion of a refund.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Each billed service is supported by actual work and accepted charging terms. Use this check when reviewing the first working version.

Talk to us

Discuss invoice management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements