In the Space and SmallSat industry, milestones are everywhere. Design reviews, engineering gates, test campaigns, payload integration, launch windows, customer acceptance, and post-launch support can all become key points in a contract. They are useful. They help teams measure progress. They often trigger invoices.

But here is the accounting catch: a milestone is not automatically revenue. That may sound like a small distinction, but for SmallSat companies managing complex contracts, government funding, customer-specific deliverables, and long development timelines, it can become a major financial reporting issue. Finance teams need to get back to the core question: when has control of the promised goods or services actually transferred to the customer?

Billing and Revenue Are Not Always on the Same Path
Many aerospace and SmallSat contracts are structured around milestones because that is how the work is managed. A customer may agree to pay when a preliminary design review is completed, when hardware passes environmental testing, when integration is complete, or when a satellite reaches a certain post-launch operating period. Those billing events are important for cash flow. They may even be the right way to manage the contract operationally. But they do not automatically answer the revenue-recognition question. Under ASC 606, revenue is recognized based on the transfer of promised goods or services to the customer. The standard uses a five-step model that looks at the contract, performance obligations, transaction price, allocation of that price, and when each obligation is satisfied.
In plain English: just because you can send an invoice does not always mean you have earned the revenue for financial reporting purposes.

Where SmallSat Contracts Get Tricky
SmallSat companies often operate in a unique mix of engineering services, manufacturing, government contracting, mission support, and advanced technology development. That creates several accounting questions:
–Is the company delivering one combined mission solution, or several distinct goods and services?
–Does a design review represent a separate performance obligation, or is it simply one step toward delivering the final spacecraft, payload, subsystem, or mission service?
–Should revenue be recognized over time as work progresses, or at a point in time when control transfers?
–How should contract modifications, change orders, launch delays, rework, performance incentives, or customer acceptance terms be handled?

The milestone schedule may show when cash comes in, but the accounting team still needs to determine what has been promised, what has been delivered, and what support exists for the revenue-recognition treatment.
That is where finance teams may need a little help from their ERP system.

Government Contracts Add Another Layer
For companies working with government or quasi-government customers, the challenge may go beyond GAAP. FAR Part 31 includes cost principles used for pricing and determining reimbursable costs when a contract requires it. FAR 31.201-2 says a cost must meet several tests to be allowable, including reasonableness, allocability, applicable CAS or GAAP standards, contract terms, and any stated limitations. FAR 31.203 also brings discipline to indirect-cost allocation.

That means many SmallSat finance teams are managing two related but different issues:
–First, they need to recognize revenue correctly under ASC 606.
–Second, they need to track direct costs, indirect costs, allowable costs, and allocation logic in a way that can support pricing, reimbursement, audits, and customer questions.

In other words, you need a clean revenue-recognition process and a clean cost-accounting foundation. If those are not connected, reporting can become a long and winding road of spreadsheets, emails, and manual explanations.

A 2026 CAS Watch Item
There is also a timely compliance development worth watching. On March 20, 2026, the Cost Accounting Standards Board published a proposed rule that would increase certain CAS monetary thresholds, including increasing the full CAS coverage and disclosure statement threshold from $50 million to $100 million. As of this writing, that proposal is not final, so companies should not assume the relief applies today. But it is still important. It shows that CAS thresholds and compliance obligations continue to evolve. For emerging space contractors, the takeaway is not, “We can ignore this.” The better takeaway is, “We should build accounting processes that can scale before compliance becomes urgent.” That is especially true for companies pursuing larger awards, federal work, defense-related programs, or contracts with cost-reimbursement features.

How ERP Helps Keep the Story Straight
This is where an ERP system can make a meaningful difference. A well-structured ERP should help finance teams separate billing from revenue recognition, track project costs at the right level of detail, maintain contract and change-order history, and support reporting by project, customer, contract line, task, or cost pool.

For SmallSat companies, that may include:
–Tracking contract milestones separately from revenue-recognition events.
–Capturing labor, materials, subcontractors, travel, testing, and other project costs by contract or work breakdown structure.
–Maintaining visibility into indirect cost pools and allocation bases.
–Supporting deferred revenue when billings happen before revenue is earned.
–Keeping change orders and contract modifications tied to the original contract record.
–Providing reporting that helps controllers explain the difference between bookings, billings, backlog, revenue, and cash.

Acumatica can be a strong fit for this type of environment because its Project Accounting capabilities support project cost tracking, billing rules, and project-based reporting. When paired with contract management and deferred revenue functionality, Acumatica can help companies manage the timing differences between invoicing, cash receipts, project progress, and revenue recognition. The key is not simply turning on software. The key is designing the system around how contracts are written, how costs are accumulated, and how revenue is recognized.

The Practical Takeaway
For SmallSat and space-industry finance leaders, the lesson is simple: Milestones may drive invoices, but they do not automatically determine revenue.
A signed milestone schedule is a great operational tool. It may also be a great cash-flow tool. But revenue recognition still requires careful analysis of performance obligations, transfer of control, transaction price, variable consideration, and contract changes.
Companies that get ahead of this will be in a better position to support audits, investor reporting, government-customer requirements, and future growth. Companies that wait may eventually find themselves trying to reconstruct contract history from spreadsheets, emails, and billing notes. And in an industry where timing, documentation, and mission readiness all matter, that is one accounting black hole worth avoiding. Here comes the sun is a much better financial reporting strategy.

Need Help Reviewing Your Contract and Revenue Process?
Polaris Business Solutions helps project-based and contract-driven companies evaluate how their ERP system supports billing, revenue recognition, project accounting, and compliance reporting. If your team is managing milestone-heavy contracts, deferred revenue, government contract requirements, or complex project costing, Polaris can help you assess whether your current system is ready for the next stage of growth.