Ordway

Ordway distinguishes a fixed subscription from consumption charges and fees based on transaction value. Those components can be combined on an invoice, with formulas and usage detail available to explain the calculation.

For a prepaid offer, its usage tools track credit consumption, replenishment, expiry and rollover rules. They can also compare actual usage with a contract's minimum commitment. The billing rules should make clear whether unused credits carry forward and what happens when the allowance is exhausted.

The invoice-generation step is called a Billing Run. Open Menu > Operations > Billing Runs > Add Billing Run. Set the Target Date for charges eligible to be billed and the Invoice Date that should appear on the document. Choose the charge types and any customer filters, then review the processing options before saving.

Draft runs allow review before finalization. Posted runs and invoices cannot simply be deleted. Only one billing run can execute at a time, although a run filtered to one subscription can use immediate processing when that feature is enabled. Grouping customers by billing cycle or geography helps organize the work.

After invoicing, accounts-receivable tools show balances by age, send reminders for overdue or failed payments and match receipts to invoices. Customers can use a portal to check balances and download past invoices. Payment links and automatic collection depend on the selected payment configuration.

Ordway sells a configured subscription service. Its commercial guide describes fixed subscription fees scaled to the value processed, with a proposal based on product scope, volume and implementation. It says this is not a percentage deduction from every billed sale.

The platform works from orders and contracts into billing and revenue reporting. Full sales quoting and the general ledger remain separate systems, connected through integrations or programming interfaces (APIs). Ordway also states that it is not the merchant of record; the seller's payment and tax arrangements still matter.

Bring representative contracts, usage files and accounting requirements to the demo. Those inputs determine how the billing rules and connections need to be configured.