Product · Billing

Flight completion and billing

Turn approved flight records into charge calculations and draft invoices using the organisation’s configured Hobbs, tacho, block or airborne-time rules, landing fees and VAT.

Repulion flight invoice overview
Operational billingFlight invoices remain tied to the underlying flight record.
Configurable time basisHobbs, tacho, block or airborne time.
Review before invoicingSubmitted values stay visible before financial processing.
Operational charges includedLanding fees, VAT and organisation-specific charging rules.

The flight record stays at the centre.

A completed flight already contains most of the information needed for billing. Repulion carries the completed flight record through review and invoicing. Office staff work from the approved operational data.

01 · COMPLETECapture the flight

Operational values, landings, people and remarks are submitted with the completed flight.

02 · REVIEWCheck the record

Authorised staff can confirm or correct the values before they become financial data.

03 · CALCULATEApply your rules

The organisation’s configured time basis, fees and VAT determine the charge.

04 · INVOICEPrepare the invoice

A draft invoice is created for final review, download, print or onward accounting.

Flight completion

Capture the information while the flight is still fresh.

Pilots and instructors complete the operational record once. The billing workflow starts from that record, including the time values and charges that matter to your organisation.

  • Start and end values stay together with the flight.
  • Landings, people on board and operational remarks remain part of the same record.
  • Instructional flights can keep the lesson context alongside completion.
Repulion flight completion form
Flight completion · operational data is captured before billing begins.

Review

Give the office a proper review step.

A submitted flight is not forced straight into an invoice. Authorised staff can compare the submitted record with the operational values, make a justified correction when needed and approve the flight for billing.

  • Submitted and reviewed values stay visible in one place.
  • Corrections can be documented and retained with the record.
  • Billing starts from an approved operational record.
Repulion submitted flight record review
Record review · operational values can be checked before approval.

Charging rules

Use the billing basis your operation actually uses.

Different organisations charge aircraft differently. Repulion keeps those charging rules in the operational workflow so each invoice reflects the aircraft, flight and organisation configuration.

Time calculationHobbs, tacho, block or airborne-time charging, according to the organisation’s configuration.
Additional chargesLanding fees and other configured operational charges can be carried into the calculation.
Tax handlingVAT can be applied to the relevant invoice lines using the organisation’s configured rules.
Review statusDrafts remain reviewable before they are treated as final financial documents.
Accounting connectivityPrepared records can move into the connected finance workflow without rebuilding the flight by hand.

Invoice output

Produce an invoice people can actually check.

The finished invoice keeps the charged activity readable: who was billed, what was charged, which unit price was used, VAT and the final total. The finance team can review it without tracing figures through several systems.

  • Clear invoice lines derived from approved flight activity.
  • PDF and print output for normal office workflows.
  • Invoice status remains visible from the billing overview.
Repulion generated draft invoice
Draft invoice · a readable financial document generated from the approved flight.

See billing with your own aircraft and rules.

We can walk through the path from flight completion to invoice review using the way your organisation currently charges flying.

Réserver une démo