Satellite-Capacity Contract Accounting Architect — Orbital Networks

The mandate

Customer agreements combine reserved transponder capacity, managed throughput, gateway access, hosted-payload commitments and launch-dependent minimum payments. Commercial teams track contract signatures, programme teams track orbital milestones and Network Operations measures availability, while Billing applies separate activation and credit rules. A launch delay, partial payload acceptance and insurance notice exposed that contract assets, deferred income, customer remedies and recovery expectations could not be reconciled by satellite and beam.

The six-month deliverable is a contract-to-ledger architecture spanning reservation deposits, take-or-pay commitments, launch windows, in-orbit testing, service commencement, steerable capacity, usage bands, availability credits, restoration, hosted-payload consideration, insurer proceeds, termination and replacement capacity. It must distinguish legal entitlement, operational evidence, billing event, cash, accounting conclusion and forecast economics while preserving qualified Accounting and Legal judgement.

Milestone one at week four accepts the contract-family, satellite and balance inventory. Week ten approves event maps, evidence hierarchies and judgement ownership. Week eighteen rehearses delayed launch, partial payload acceptance and regional service degradation. Week twenty-six accepts calculation specifications, contract-to-ledger bridges, exception controls, training cases and a sequenced implementation backlog. Fee release follows documented client acceptance at each milestone.

Acceptance requires Commercial Finance, Programmes, Network Operations and Revenue Accounting to reproduce eight unseen customer contracts from executed terms through milestone evidence, invoice, cash and ledger; explain one insurance-related recovery without netting unlike rights; and resolve twelve launch, capacity and service events within agreed tolerance. External Audit may test evidence availability but does not pre-approve the architecture or accounting outcomes.

The client will provide executed contracts and amendments, satellite programme baselines, launch and in-orbit test records, beam-capacity allocations, network availability data, service-credit claims, invoices, cash receipts, insurance notices, ledgers, accounting papers and named owners. The consultant will not certify spacecraft readiness, accept payloads, interpret law, promise capacity, settle claims, negotiate customers, post entries, operate billing or issue assurance.

Why this is external work

Commercial teams read promises, engineers establish technical state, operators measure delivered service and Accounting determines recognition, but each uses a different event vocabulary and level of granularity. An independent architect can make those boundaries traceable across satellite, beam and customer without becoming mission authority, contract counsel, claim adjuster or production accountant.

What you will own

• Catalogue reservation, launch, acceptance, availability, throughput, hosted-payload, credit, termination and replacement-capacity clauses by contract and satellite.
• Trace launch evidence, in-orbit testing, beam allocation, measured service and customer acceptance into billing, cash and ledger events.
• Define source and judgement hierarchies for commencement, variable consideration, service credit, contract modification and insurance recovery.
• Design close controls for delayed launch, partial payload, capacity reassignment, outage, disputed measurement and retroactive customer remedy.
• Rehearse a launch slip, incomplete hosted-payload acceptance and multi-region degradation from technical fact through financial consequence.
• Establish satellite-to-contract lineage, exception ageing, override evidence, counsel escalation and accountable accounting-policy decisions.
• Deliver event maps, calculation specifications, balance bridges, control catalogue, training cases and a prioritised systems backlog.

Candidate qualifications

• Directed contract or revenue-accounting architecture for satellite, telecommunications, aerospace or similarly milestone-dependent infrastructure services.
• Reconciled commercial promises, technical acceptance, measured availability, billing, cash and ledger evidence across long-duration customer agreements.
• Governed launch delay, partial acceptance, service credits, variable usage, contract modification and termination through controlled financial closes.
• Distinguished customer remedy, insurance right, forecast recovery and recognised accounting amount without inappropriate netting or premature certainty.
• Built operating evidence jointly with programme engineers, network operators, Commercial, Legal, Insurance, Treasury and external audit.
• Transferred reproducible controls through unseen launch and degradation cases rather than leaving consultant-owned calculations or interpretation.

Non-negotiables

• The named architect must lead all Toulouse design councils, four file residencies and three event walkthroughs during six months.
• Will disclose relationships with satellite operators, launch providers, insurers, customers, regulators, auditors and network-equipment suppliers.
• Brings milestone-to-service contract-accounting implementation in technically complex infrastructure; general subscription accounting alone is insufficient.
• Will not certify spacecraft, accept payloads, interpret contracts legally, promise capacity, settle claims, post entries or issue assurance.

1. 49 words maximum. Describe a contract balance that changed after launch, acceptance or availability evidence was rebuilt.
2. 49 words maximum. Which partial-payload or service-degradation case would best test the target architecture?
3. 49 words maximum. What commercial and technical records must the client provide before milestone one?