Skip to main content
GullySystem
Automotive

Invoice Management for Electric scooter dealers

Reconcile the actual scooter seller’s bill with the accepted package and the original collection of booking money.

Finance & Accounting

Does this function belong in your operation?

For dealers issuing their own invoices or retaining another seller’s invoice reference for local fulfilment.

Accepted supply or an agreed advance becomes billable by the entity authorised to issue that charge.

Confirm whether the dealer is the seller or is fulfilling a sale invoiced by another entity before preparing a customer bill. Reconcile the original online token, later payments and supplied package without duplicating the manufacturer's charge. Optional accessories and battery-provider obligations need their own supported treatment. Keep correction and refund decisions traceable. A paid invoice does not establish registration approval, technical readiness, service-plan activation or completion of every accessory line.

Bring the records the workflow depends on.

  • Actual invoicing entity, purchaser and accepted variant package
  • Original booking collection, verified allocation and later receipt references
  • Actual billable equipment, optional lines and accountant-approved treatment

Outputs to check

  • Dealer invoice or correctly linked external-seller document
  • Single verified booking-credit allocation
  • Outstanding balance and separate optional-provider references

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. Confirm who issues the bill

    Identify the contractual seller for the scooter and each optional item. Where another entity invoices the vehicle, retain its reference rather than creating duplicate dealer revenue.

  2. 2. Match the package

    Check the accepted variant, supplied equipment and authorised changes. Refer missing or disputed accessory lines to the agreed billing terms.

  3. 3. Verify the booking credit

    Trace the original collector and confirmed allocation. A customer screenshot and an imported booking must not create two credits for the same money.

  4. 4. Issue or link the authorised document

    Create only the dealer’s actual charge using approved numbering and accounting settings, or retain the external seller’s invoice reference. Keep separate battery-provider documents identifiable.

  5. 5. Reconcile and correct

    Apply verified receipts and authorised adjustments. Preserve the original invoice and booking trail when a purchaser change, cancellation or missing accessory needs review.

Who uses the module, and who approves?

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

Retail billing owner

Checks seller identity and avoids duplicate vehicle billing.

Counter account coordinator

Resolves purchaser and package differences with the actual seller.

Accounts reviewer

Verifies booking credit, settlement evidence and authorised corrections.

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.

Brand collected the token

Confirm the permitted allocation and settlement reference before crediting the dealer’s customer account.

Manufacturer already invoiced the scooter

Link the document and identify only genuinely separate dealer charges.

Purchaser changes after documents are issued

Follow the actual seller and accountant’s correction process without rewriting the original payment history.

Battery plan is billed by another provider

Keep its agreement and bill outside dealer revenue unless the actual contract and accounting treatment require otherwise.

A cancellation has an approved refund

Link the seller decision to the original collection and authorised payee. Keep credit approval, payment instruction and confirmed return-of-money evidence separate; a credit note alone does not prove the buyer received funds.

Can this work independently?

Billing can use approved entered supply lines and external document references. Actual money collection and allocations require verification. Accounts determines tax, refund and document treatment; payment execution, registration and optional-service activation are distinct processes with separate authority. An authorised credit or refund decision is separate from payment execution and confirmed returned-money evidence.

Systems and records it connects with

  • Accepted retail order and actual supply evidence.
  • Manufacturer invoice or booking-settlement reference where applicable.
  • Verified receipts, authorised corrections and separate provider documents.

Configure, test and introduce the workflow.

  • Compare a dealer-invoiced sale with fulfilment invoiced by another entity.
  • Test duplicated token evidence and an unresolved accessory line.
  • Reconcile a purchaser correction without erasing the original seller and payment records.

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.

  • The bill identifies the actual seller and purchaser.
  • Each verified booking amount is credited only once.
  • Payment does not imply registration approval or complete accessory and service delivery.
Electric scooter dealers

How the business operates.

A scooter buyer books through a brand website, a family member pays the token, and the local counter is asked to deliver a different colour with another battery option. The dealer needs the original reference and the accepted revision before treating those requests as one settled sale. This scope covers new electric-scooter retail through the business's actual manufacturer or retail-partner arrangements. It follows rider questions, variant and pack choices, physical scooter and accessory custody, the correct selling entity and handover. Removable packs or a separate battery plan are recorded only for models actually supplied that way. The proposed workflow does not run a battery-swapping network or claim installed GullySystem capability.

Counter enquiries and test rides

Keep the intended rider, purchaser and person making contact distinct. Record which model the rider tried and questions needing a product specialist. A family enquiry or online token does not settle the owner details, permitted road use or final package.

Variant and package confirmation

Identify the scooter variant, colour, supplied pack configuration and charger. Retain accessory and optional service-plan choices separately. When a model offers a battery usage arrangement, record the actual provider terms rather than presenting it as an ordinary included battery.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Brand booking reference, collection channel and verified payment evidence
  • Intended rider, purchaser, payer and authorised recipient
  • Variant, colour, pack configuration and accepted revision
  • Battery-plan provider and agreement reference where applicable

Operational bottlenecks to check

The online booker is not the purchaser

A relative’s contact appears on the booking while another person is meant to own the scooter. Resolve the correct identities through the actual seller’s process before billing; do not overwrite the payment trail.

Same colour, different pack or charger

The counter substitutes a visually similar scooter or charger and loses the accepted specification. Preserve variant and equipment references and obtain the relevant technical and buyer decisions.

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. Connect the counter enquiry

    Find the original brand booking or earlier visit without merging different riders or purchases. Confirm the contact’s role and record the question still preventing a decision.

  2. 2. Record the model experience

    Identify the test scooter and feedback. Refer compatibility, technical or permitted-use questions to the appropriate authority rather than promising that another variant behaves identically.

  3. 3. Agree the exact package

    Record colour, variant, supplied battery arrangement, charger and selected extras. Retain any new revision and the purchaser’s decision before allocation.

  4. 4. Match physical items

    Check the actual scooter and included equipment against the accepted package. Record an absent charger, missing pack reference or held unit separately; a carton count alone cannot prove a complete customer supply.

  5. 5. Complete the retail handoff

    Check the selling entity and applicable external responses. Record the actual recipient and supplied items, preserving outstanding optional accessories or account queries under the agreed terms.

  6. 6. Reconcile money and follow-up

    Match the original booking collection and later receipts without crediting the same token twice. Send unresolved charging, warranty or account questions to their actual provider with the accepted package reference.

Industry reports to connect with

  • Enquiries awaiting rider, purchaser or original-booking clarification
  • Variant or battery-plan revisions awaiting purchaser acceptance
  • Scooters held, available or allocated by actual identity
  • Incomplete charger, pack or accessory supply by order

Questions before implementation.

When should electric scooter dealers consider invoice management?

For dealers issuing their own invoices or retaining another seller’s invoice reference for local fulfilment. Accepted supply or an agreed advance becomes billable by the entity authorised to issue that charge.

What should we bring to the requirements discussion?

Bring anonymised examples of Actual invoicing entity, purchaser and accepted variant package; Original booking collection, verified allocation and later receipt references; Actual billable equipment, optional lines and accountant-approved treatment. 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. Reconcile the actual scooter seller’s bill with the accepted package and the original collection of booking money. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The invoice does not grant subsidy eligibility, registration, warranty acceptance or permission to use a vehicle. Refund outcomes depend on the actual agreement and authorised decision.

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. The bill identifies the actual seller and purchaser. 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