Requirements and compliance

Draupnir and Gungnir are the two products of FairyWare Order to Invoice. Every requirement below is built and verified: proven by a test or on an instance, and named in the requirements matrix. Requirements that are designed but not yet verified are not listed here; they are counted at the end. Planned capabilities are in the roadmap section and are not part of the current version.

PartDeliveredOf which key capabilities
Draupnir: subscriptions288
Gungnir: invoicing3712
Gungnir add-on: Pricing30
Gungnir add-on: ITFM147
Gungnir add-on: Time reporting101
Included in both products337
Licensing and delivery51
Total13036

Priority is the priority the requirement had when the product was designed: Must, Should or Could. A star (★) marks a key capability.

Draupnir: subscriptions

IDAreaRequirementPriority
SUB-001Model★ A subscription records what a customer has bought: offering (mandatory), billing account, optional contract, owner, item, host, quantity, dates and billing frequency.Must
SUB-004OrderingThere is one order form per offering and audience. All forms share one buyer block that offers the buyer types allowed for the offering’s order class (user or infrastructure).Must
SUB-005OrderingInfrastructure is ordered only on an existing contract. The form never creates a contract; it points to the contract request.Must
SUB-006OrderingAny user can order user items for another user, who becomes the owner.Should
SUB-008OrderingAn offering can limit the quantity per order.Could
SUB-009ApprovalEvery order is registered at once with status awaiting approval. The approver follows the owner type (contact person, manager, cost center manager, service owner). The contact person ordering needs no approval, and an offering can skip approval.Must
SUB-010ApprovalApprovers get a reminder after 3 days; after 5 days the approval moves to the offering’s support group.Must
SUB-011FulfilmentFulfilment runs by the offering’s method: system call, automated flow, manual task or none (sync only). A manual task records the delivered item and host.Must
SUB-012Fulfilment★ Billing starts on the later of the requested start date and the delivery date, so customers never pay before delivery. A seller can choose the requested date instead.Must
SUB-013FulfilmentFailed or stuck fulfilment is retried, shown in a work queue and escalated after 5 days. Hourly sweeps catch anything missed.Must
SUB-014Add-ons★ Add-on offerings (backup, rollback, setup fee) are bought on a parent subscription, start and end on their own, and end with the parent.Must
SUB-016Changes★ Support edits billing-relevant fields directly in the form. The change flow starts by itself, the row is locked while it runs, and every change is journalled. Controllers have Correct without fulfillment.Must
SUB-017ChangesOne validation routine runs for every source (form, file, flow, API). It blocks any change to an already billed period.Must
SUB-020CancellationA notice period per offering sets the cancellation date; billing runs to it. A cancellation can be withdrawn until its effective date. Mandatory subscriptions cannot be cancelled by users.Must
SUB-021Self-service★ Employee Center shows a user’s subscriptions, or those of a billing account or contract, with status, item, host and dates, and offers add-ons, cancel and offering actions. The cancel dialog shows the consequences first.Must
SUB-022Self-serviceUsers can be granted access to act for other companies; a company switcher appears for them.Should
SUB-023IntakeSubscriptions can be loaded from files of up to about 50,000 rows as sync rows that need no fulfilment, with the same validation as the form.Must
SUB-024IntakeThe same order event can never create two subscriptions (idempotent intake).Must
SUB-026Billing guardEach subscription keeps how far it has been billed and a readable list of billed periods, so it is never billed twice.Must
SUB-027VolumeA contract can hold about 200,000 subscriptions; lists are indexed, paged and filterable.Must
SUB-029One-time chargesAn offering can be set to bill an order as a one-time charge without a subscription, for items that need no history. The charge is created when the order is delivered and is never billed twice.Must
SUB-030Self-serviceCustomers see their recent one-time orders in Employee Center, latest first, with status and whether they have been billed.Should
SUB-031Ordering★ O2I follows the installation’s own request process: the subscription is registered when the request item is created, ended without billing when it is rejected or closed incomplete, and activated with the delivered item when it closes complete.Must
SUB-032Ordering★ O2I’s own approval and fulfilment task are optional per offering and seller, with a default per seller, for catalog items that have no process of their own.Must
SUB-033OrderingO2I writes a work note on the request item at each stage (created, approved, activated, failed, ended, blocked), switchable per seller and offering.Should
SUB-034Integration★ Installations can use four standard Flow Designer actions (Register order, Mark fulfilled, Mark failed, End subscription) and the same calls in a documented script API, in their own flows and scripts.Must
SUB-035OrderingA request item is never registered twice, even when several processes try at the same moment.Must
SUB-036OrderingA private (person) account is offered only when people order for themselves; web shop users without a company can order through the catalog on their own account.Should

Gungnir: invoicing

IDAreaRequirementPriority
INV-001Billing runA billing run belongs to one seller and bills everything due up to a cutoff date. Several runs per month are allowed, with one open draft per seller.Must
INV-002Billing run★ A draft is built early and refreshed as often as needed: incremental (changed sources only), scoped (one offering, account or subscription) or full. About 200,000 lines per run are processed in resumable batches.Must
INV-003Billing runChanges after the run’s snapshot are listed as warnings and never applied silently.Must
INV-004Billing runRuns can start automatically on a seller schedule (frequency, first cutoff, lead days, time of day), for example every second week.Must
INV-005ApprovalApproval is manual by default, or automatic at a set time a set number of working days after the cutoff when reconciliation passes.Should
INV-006Approval★ Open errors never block approval: the financial controller decides. Lines in error stay out and are billed in a later run.Must
INV-007ControlDouble billing is prevented by a billed-up-to date on every source plus a uniqueness rule on source and covered period.Must
INV-008ControlReconciliation proves that aggregated plus excluded equals all priced lines; a mismatch fails the run.Must
INV-009SpecificationEvery invoice line copies the values it used (price, cost centers, GL, names, tax). Approved lines are never changed.Must
INV-010SpecificationControllers edit or hold draft lines late in the period; refreshes keep manual work, and every change is journalled.Must
INV-011TransactionsOne-time transactions (charge, usage, credit, time) are loaded from files, TCM, true-up and native expense lines. Credits need no original.Must
INV-012TransactionsA transaction without an offering is allowed when it carries an earning cost center, GL, price and description.Must
INV-013Cost centers★ A row that arrives with only a cost center finds the customer account that claims it. An unclaimed cost center is billed as an internal sale with an information exception.Must
INV-014Cost centersThe ERP cost center of each line is resolved in a fixed order: the row’s own, the account override, the account’s rule, then the common debit cost center.Must
INV-015GLEach line gets its GL from the transaction override or the offering and service defaults; internal sales use the GL mapping, and the original GL is kept.Must
INV-016ExceptionsLines that cannot be built become exceptions (error, warning, info) that wait and are retried. Service owners and controllers fix them on the source through a catalog item.Must
INV-017ExceptionsOne open exception per source and reason; a controller can accept a warning with a note.Must
INV-018ERP★ The ERP deliverable has one row per debit and credit cost center and GL, per fiscal period and run, with a signed amount, and is marked when delivered.Must
INV-019ERPSelf-charges are excluded, and internal charges between two cost centers can be netted per seller.Should
INV-020Customer viewThe customer summary has one row per customer account. The invoice detail groups lines by customer account, owner, item and offering.Must
INV-021InvoicesA seller can create invoices: one per run and billing account (one seller, one customer), numbered at approval from the seller’s own series (or an external number), with a snapshot of customer and seller details. A negative invoice is a credit note.Must
INV-022InvoicesThe invoice covers the run’s period, gets its due date from the payment terms and is exported as Excel or CSV.Must
INV-023VAT★ When the seller switches VAT on, each line’s tax code is resolved by the rules (incoming code, account override, account code, offering, service, GL and country rules, seller default). Own-company buyers get no VAT.Must
INV-024VATThe invoice shows a VAT summary per tax code, rounded once per invoice and code. Prices and ERP files stay net.Must
INV-025ERP alignment★ After the ERP file is delivered, finance controllers align approved lines with what the ERP accepted (GL, cost center, customer account, billing account), in a workspace or by file. Amounts never change, and every change has a reason.Must
INV-026ERP alignmentAn aligned change follows through: the cost pool gets reversing and new entries, and an invoice that is not yet sent is recalculated.Must
INV-027Expense lines★ Native Cost Management expense lines can be billed without a subscription. Mapping rules choose which lines are taken and fill in what they lack, and changed source lines are flagged.Should
INV-028ProrationThe proration architecture is in place with the mode none as default: a period is billed in full.Should
INV-029PeriodsEach line has an accounting date and fiscal period. Lines for a closed period go to the earliest open period and are flagged late.Must
INV-030TimeBillable time from TCM becomes time transactions priced by Pricing, and the invoiced status is reported back to the time entry.Must
INV-032Marketplace★ A web shop owner can sell other vendors’ products in its own name: the buyer gets one invoice from the owner, whichever vendors’ products it holds.Must
INV-033Marketplace★ Each offering can name the vendor that supplies it. After each approved billing run every vendor gets a settlement of what was sold of its offerings, grouped by offering, minus a commission percentage.Must
INV-034MarketplaceSettlements are self-billing documents with an own number series per vendor, the vendor’s VAT and a snapshot of both parties’ details. Credits and returns flow into the next settlement.Should
INV-035MarketplaceSettlements are booked in the ERP file on the vendor’s own cost center, and the purchase is posted to the cost pool, so the margin per offering is visible.Should
INV-036Marketplace★ The vendor’s users see their own settlements and sales per offering in the portal, without seeing who bought.Should
INV-037Offerings★ An offering can be marked non-billable per seller (or by its status, through the adapter): its subscriptions are ordered, fulfilled and kept but never invoiced, and transactions on it are rejected with a reason.Must
INV-038Proration★ With the mode daily, a partial period is billed by its covered days: a subscription that starts or ends inside a period pays covered days / days in the period, and an end inside a period that is already billed gives a credit for the unused days. The mode is set per seller and can be overridden per billing frequency. One-time charges, transactions and time are never prorated.Should

Gungnir add-on: Pricing

IDAreaRequirementPriority
PRC-001Customer pricesAn agreed price per billing account (seller and customer) and offering replaces the list price, for everything that seller bills the customer. A price of 0 means free.Must
PRC-002DiscountsA flat percentage discount per billing account applies to list prices only, never to a fixed or customer price.Should
PRC-003ValidationCustomer prices and discounts cannot overlap in time for the same scope and must belong to the account’s seller.Must

Gungnir add-on: ITFM

IDAreaRequirementPriority
ITF-001Cost pool★ Actuals, budgets and forecasts are entries in one cost pool per seller, cost center and fiscal period, on shared dimensions (service, offering, GL, component type, TBM), so variance is a direct comparison.Must
ITF-002ActualsApproved billing runs post actuals automatically and idempotently, one entry per invoice line, with a sweep for anything missed.Must
ITF-003Actuals★ Internal sales also post the cost on the buyer’s cost center, so both sides see their true cost.Must
ITF-004ActualsBilled lines are spread over the months they cover in proportion to the days; future months count as committed.Must
ITF-005ActualsPosted entries are immutable; corrections are reversing entries, and closed periods are never changed.Must
ITF-006Transfer priceA transfer price percentage is added to consultant hours billed to external customers, in budget and actuals, by one shared calculation.Must
ITF-007BudgetBudgets are versions with revisions; controllers lock versions, and the current budget is the highest locked revision.Must
ITF-008Budget★ Budgets are built from components per month (labour hours × standard or own rate, vendor, software, income), per cost center and service or offering. Budget entries are generated, never typed.Must
ITF-009Forecast★ A forecast version is made each month after close. Open months start from the average of the last three closed months, and committed amounts are a floor.Must
ITF-010Vendor cost★ Vendor costs are uploaded with covered months, matched by vendor (and GL) to versioned mappings and distributed by fixed percentages, equal split, billed amount or quantity, or budget share, after a preview.Must
ITF-011True-up★ Group billing is trued up to actual cost over closed periods: credits or extra charges per account in proportion to what each was billed. A seller can allow credits only, and a run can be withdrawn while unbilled.Must
ITF-012TimeInternal (non-billable) time is posted as cost directly at timecard approval, optionally allocated to the offering’s cost center.Must
ITF-013AccessAll service owners of a seller see its budgets; the owner, delegate and controllers edit.Must
ITF-014Variance★ A variance report compares actuals with the current budget and forecast per seller and fiscal year, by cost center, service or offering: year to date and full year, income and cost separately, with a breakdown by component type and month and a CSV export.Must

Gungnir add-on: Time reporting

IDAreaRequirementPriority
TCM-001ResourcesEach person has a resource profile per seller (manager, delegate, employee or consultant) and a cost rate with validity dates visible only to the seller’s finance controllers.Must
TCM-002TimecardsTime is reported per person and week (Monday weeks) in hours, in a weekly grid with a comment per cell.Must
TCM-003TimecardsEvery entry names an offering (only offerings open for time reporting), an optional project node and, for billable time, a billing account.Must
TCM-004ProjectsProjects have up to five levels (the project, and up to four levels below it, such as phase and type of work); a billing account on the project makes its time billable by default.Should
TCM-005ApprovalManagers approve timecards, and a rejection carries a comment. Approved cards never change; late time goes on a supplementary card.Must
TCM-006CorrectionsA correction adds reversing entries: the transaction is cancelled if unbilled, or credited if billed.Must
TCM-007Integration★ Time can be reported from any task and through a REST API, with the same validation as the form.Should
TCM-008ValidationClosed periods block new time (controllers can override); a person reports at most 24 hours per day.Must
TCM-009RatesCost rates are read through the adapter, so existing rate tables (HR or Cost Management labour rate cards) can be used; O2I keeps its own rate table for installations without one.Should
TCM-010HistoryEvery time entry keeps the person’s cost center, department and company as on the work date, with their names, frozen at approval for historical verification.Must

Included in both products

IDAreaRequirementPriority
COR-001Sellers★ Several sellers (legal entities) can use one instance. Every business record belongs to one seller, and users see only the data of the sellers they work for.Must
COR-003SellersThe seller record holds everything needed to issue an invoice: legal name, address, registration and VAT number, bank details and a footer text.Should
COR-004SellersOptional behaviour is switched on per seller with safe defaults: automatic approval, run schedule, invoices, VAT, proration, ERP netting and ERP alignment.Must
COR-012Billing accountsAn account’s cost center can be overridden for chosen services or offerings (with an optional tax code), so an ERP that derives VAT from the cost center receives the right one.Must
COR-013Billing accountsA billing account is found by contract number, or by seller plus customer number, in forms, files and integrations.Must
COR-014Contracts★ The platform’s own contract is used. A contract is owned by one seller and belongs to one customer; the system adds only the billing account, and reads the customer account (the PO number), parties, validity and state from the platform’s own fields through the adapter.Must
COR-015ContractsA contract can be ordered on only when it has a billing account, a company and an active contact person.Must
COR-017Reference dataSmall reference data (sellers, billing frequencies, fiscal periods, GL accounts, payment terms, tax codes and rules, offering settings and more) is kept in one table, validated per type and seeded by the demo data.Should
COR-019GLGL accounts are kept per seller with category, type (income, expense, netting) and TBM cost pool. A GL in use is never deleted, only made inactive.Must
COR-021Reference dataPayment terms hold days, basis (invoice date or end of month) and the text printed on the invoice.Must
COR-022Reference dataBilling frequencies are data (week, month, year or once, interval, alignment, timing), so new periods need no code.Must
COR-023TBM★ TBM cost pools and towers are loaded as data; every GL rolls up to a TBM cost pool and every offering or service to a tower. Tags are copied onto every line when it is created.Should
COR-024Offering settings★ Offering and service settings are kept without adding columns to the platform’s offering and service tables, opened through an O2I settings link on their forms.Must
COR-026PricingOffering prices are kept per billing frequency with validity dates. A price change is a new row, and overlapping rows are blocked.Must
COR-027PricingOne pricing service resolves every price in a fixed order: fixed price on the subscription, customer price (add-on), internal price, then list price minus discount.Must
COR-028PricingOwn-company buyers can have internal prices per seller, offering and billing frequency, with validity dates; without one they pay the list price. Group companies and external customers pay the list price.Must
COR-029PricingA missing price is an exception, never zero. A test price lookup when a subscription is saved flags the problem before the billing run.Must
COR-030PricingUnit prices keep four decimals; each line is rounded to two decimals by one shared routine.Must
COR-031PricingThe order form shows a read-only price estimate with its source.Should
COR-032UploadsFiles are uploaded as batches with row counts and status. Every rejected row is logged with a reason and does not stop the rest. The original file is kept for 3 months.Must
COR-033UploadsA file that was already loaded is detected by its fingerprint and blocked, unless a controller uses Upload anyway.Must
COR-034UploadsA whole batch can be withdrawn while its rows are not billed or posted.Must
COR-035UploadsFiles are Excel or CSV with fixed column names and business keys (never internal ids). Every row has an external reference, and each upload type has a downloadable template.Must
COR-036UploadsAn Update existing option lets a re-uploaded row update the existing one until it is billed; otherwise a known key is rejected as a duplicate.Should
COR-037UploadsA file row gets its seller from its contract, from a seller column, from the seller chosen at upload, or from the default seller. One file holds one seller.Must
COR-039VAT★ Tax rules choose the tax code by offering, service or GL account, for a specific customer country or for any country.Must
COR-040Adapter★ Everything that differs between instances is isolated in one adapter. A default adapter works on a plain instance, and a self check shows which extension points are active.Must
COR-043AccessCustomers see only their own company’s approved data. Prices and invoice amounts need the role customer invoice viewer, and internal fields (cost centers, GL, cost) are always hidden.Must
COR-044RetentionRetention is set per seller and table group: invoicing data 3 months after approval, ITFM entries for the current and previous fiscal year. Purging can require an export first.Must
COR-049SellersA default seller can be set, so an installation with one seller never has to choose a seller in forms, files or integrations.Should
COR-050Offering settings★ An offering can be sold by several sellers: shared settings are kept once per offering, and each seller sets its own cost centers, GL, internal price and groups.Must
COR-052AccessPeople who order can see the billing accounts they may order on (their company’s accounts and their own private account), with name and customer reference only, so the order form works without an O2I role.Must
COR-053AdministrationOne property sets how much every O2I app writes to the system log (error, warning, info, debug; default warning). Errors are always logged; business records such as history, row logs and work notes are not affected.Should

Licensing and delivery

IDAreaRequirementPriority
PRD-001LicensingA signed licence key unlocks modules and limits and is verified offline.Must
PRD-002Licensing★ A 14-day trial runs without a key. After expiry the system becomes read-only; data is never deleted and reading is never blocked.Must
PRD-003LicensingNew releases are delivered only within the update entitlement.Must
PRD-009LicensingIn read-only mode a customer can still end and cancel subscriptions and withdraw batches, so what is billed can always be reduced; everything else that creates or bills is refused.Must
PRD-010LicensingLicence limits (sellers, active subscriptions, resources) refuse only creating more; existing records keep working and are billed.Must

Roadmap

Planned, not in the current version. Order and timing are not committed.

IDProductPlanned capability
RM-001DraupnirMinimum term and automatic renewal of subscriptions.
RM-002DraupnirFuture-dated changes (a change that takes effect on a chosen later date).
RM-003DraupnirNotice ending at the end of the billing period, as a seller option.
RM-004DraupnirAmount limits for automatic order approval.
RM-005Gungnir (Pricing)Volume price tiers with their own screens (the data model is already prepared).
RM-006Gungnir (Pricing)Discounts scoped to chosen offerings or services.
RM-007GungnirGross prices (including VAT) in the web shop.
RM-008GungnirInvoices as Word or PDF documents.
RM-009GungnirDirect ERP integration (version 1 delivers the ERP table).
RM-011GungnirOne-off override on a billing exception.
RM-012GungnirIntercompany GL mapping and an intercompany ERP treatment.
RM-013Gungnir (ITFM)Aggregated posting of actuals per run as an alternative to one entry per line.
RM-014Gungnir (ITFM)An explicit cost share for true-up scopes that mix group and external billing.
RM-015Gungnir (ITFM)Transfer price in the budget as a share of hours instead of all or nothing.
RM-016DraupnirLabels per seller for the three specification text fields.
RM-017GungnirMarketplace commission per offering, as a fixed fee per order or as a markup, and a separate commission invoice.
RM-018GungnirPayout file for vendor settlements.

Not yet verified

36 further requirements are designed and mostly built, but their proof is not yet recorded. They are added to this sheet as their proofs are recorded.