1999 · Historical account
Miracle becomes a working tool for AeroMar
In 1999, AeroMar received a non-exclusive licence for Miracle. Behind this entry in the company’s history was practical application development: I.V.A.’s own platform was used to build IMS — Invoice-Mutual Settlement.
The work began well before an invoice was printed. Goods and services had to be recorded against a customer and an accounting period, with the right currency and individual terms. A payment could be an advance or settle only part of a debt. The software needed to preserve the connection between a service, its invoice and a particular payment.
IMS was built on Miracle16 as a set of interacting applications. Some maintained customer, bank and currency records; others created documents and performed calculations; a third group presented the resulting information. The component approach took a tangible form: individual applications contributed to a shared process using related data.
Transitions between stages received particular attention. Service records were included in an invoice, and the same amount was not to be billed again in another invoice. Final printing locked the invoice against further changes. Tax invoices and the sales ledger followed the selected accounting policy. The design also provided for preparing data for the SunSystems accounting system.
Calculation rules went beyond a single universal formula. Customers could have different currencies, accounting periods and markups; configurable algorithms calculated additional amounts. The user guide specifically explained that the enterprise’s specialists could modify an algorithm. This reflected an important part of Miracle’s purpose: an application should accommodate the particular practices of its customer.
One small detail of daily use also survives: a flashing indicator in an application window. It informed the user that another operator had changed the data and prompted a refresh of the display. This simple signal reveals a practical collaboration problem: several people worked with shared information, and changes needed to be made visible.
For I.V.A., licensing was part of putting its own technology to practical use. Miracle provided the foundation for a customer settlements system, expressing its capabilities through connected documents, processing rules and user actions. This episode shows how developing a programming environment and solving an enterprise’s problem could support each other.