Prerequisites
Before you configure usage drawdown, confirm the following:- Revenue recognition is enabled for your organization.
- The obligation’s Recognition Method is Usage, and its item has a deferral account. DualEntry pre-fills the method from the item’s Default Revenue Recognition Method, and you can change it on the obligation. See Where usage and drawdown settings live.
- You know the committed prepaid quantity and rate, or the flat or tiered usage pricing that DualEntry should apply before it draws the pool.
- You are creating or editing a contract that does not already require a change order or auto-renewal on the drawdown obligation. Those actions are unavailable after prepaid drawdown is in use.
Where usage and drawdown settings live
Usage is a recognition method you select on the contract form’s Performance Obligations step, and prepaid drawdown is a billing mode you select on its Invoicing step. Neither appears on the Recognition step, and there is no separate “Drawdown” recognition method or field. The table below lists each setting a prepaid usage obligation needs and where to find it on the contract form.
The Frequency options on the Recognition and Invoicing steps are the same list: One Time, Daily, Weekly, Monthly, Quarterly, Semi-Annually, and Annually. They set cadence, not the recognition method, so Usage never appears in them.
Obligations in a ramp group don’t show Recognition Method and can’t use Usage, so model prepaid usage on an obligation outside the ramp group.
Configure prepaid drawdown on an obligation
Set billing mode to Prepaid drawdown on the usage obligation so DualEntry invoices the committed pool instead of billing each usage row.- Open Accounting > Revenue Recognition > Contracts and create a contract, or open an existing draft contract.
- Add a performance obligation and select the item.
- In the obligation’s Revenue Recognition section, confirm Recognition Method is Usage. If the item’s default method is something else, select Usage here.
- Enter the committed quantity and contract rate when the obligation uses a flat rate.
- When the obligation uses graduated, volume, or block pricing, configure the usage pricing model and tier scope on the obligation instead of a single contract rate. See Usage Pricing: Flat and Tiered Models.
- Choose Next. On the Invoicing step, select the obligation, then under Billing mode, select Prepaid drawdown.
- Set the prepaid invoice timing: Frequency, Interval, and First Invoice Date / Last Invoice Date. For a one-time funding invoice, set Invoice Date instead of a date range.
- Save the obligation, then activate the contract when the terms are complete.
billing_mode as drawdown on the usage obligation. The obligation response then includes prepaid_invoiced, prepaid_recognized, and prepaid_remaining.
Record usage against the prepaid pool
Record usage the same way you do on other usage obligations. DualEntry prices the row, then draws the priced amount from prepaid remaining. Choose one intake path:- On the contract: open the active contract and choose Update Usage.
- From a file: import usage from CSV, or use Import Multi-Contract Usage when you are loading many contracts at once.
- Through the API: post usage to
/public/v2/contracts/{contract_id}/usage/bulk-upsert/.
- Enter the usage date and quantity. DualEntry maps the row to the usage obligation.
- Save the usage. DualEntry applies the obligation’s pricing model, reduces prepaid remaining, and creates the recognition for the priced amount.
Top up the prepaid pool
A top-up adds prepaid funds to the same usage obligation when remaining credits are too low for the next usage, or when the customer buys more capacity.- Open the contract that already has a prepaid drawdown usage obligation.
- Add a top-up for the additional prepaid amount.
- Save the top-up. DualEntry creates another funding invoice, credits the same deferral account, and increases prepaid invoiced and prepaid remaining.
Track prepaid invoiced, recognized, and remaining
The contract overview keeps prepaid invoiced, prepaid recognized, and prepaid remaining tied together so you can see how much of the pool is still deferred. After each funding invoice, usage row, top-up, refund, or termination, confirm this identity:- Prepaid invoiced equals prepaid recognized plus prepaid remaining.
- Prepaid recognized is never greater than prepaid invoiced.
- Prepaid remaining is never negative.
prepaid_invoiced, prepaid_recognized, and prepaid_remaining. Use them when you reconcile the deferral account to the contract.
The prepaid remaining balance rolls into the standard revenue reports as deferred revenue until usage draws it down. For the deferred revenue rollforward, invoice waterfall, and contract-level schedules, see Reporting.
If the term ends and prepaid remaining is still greater than zero, DualEntry does not recognize that unused balance as breakage on its own. Record additional usage if the customer still consumes against the package, or terminate the contract and choose accelerated recognition or cancel remaining schedules.
Troubleshooting
These are the usual blockers when you can’t find the drawdown settings, or when a prepaid drawdown obligation will not fund, consume, or close the way you expect.- There is no Drawdown or Usage option on the Recognition step. That step sets recognition cadence only. Select Usage under Recognition Method on the Performance Obligations step, then select Prepaid drawdown under Billing mode on the Invoicing step.
- Billing mode is missing from the Invoicing step. Recognition Method is not Usage, or Exclude Invoice is on. Set the method on the Performance Obligations step and turn Exclude Invoice off.
- Usage is rejected for insufficient funds. The priced usage amount is greater than prepaid remaining. Add a top-up that covers the shortfall, then record the usage again. DualEntry does not invoice the excess automatically.
- Quantity, rate, or discount will not save. A funding invoice already exists. Add capacity with a top-up instead of editing the original obligation amounts.
- Billing mode will not leave Prepaid drawdown. Invoice lines still exist against the obligation. DualEntry keeps the obligation on drawdown while those lines remain.
- Add Change Order is missing. That action is unavailable on any contract that has a prepaid drawdown usage obligation. Top up the pool, or terminate and replace the contract.
- Unused prepaid funds are still in deferred revenue after the end date. DualEntry does not auto-recognize breakage. Consume the remainder or terminate the contract so the remaining prepaid balance is accelerated or reversed.
- The obligation header shows a larger amount than the prepaid invoice. Usage form totals can still show a pricing estimate such as quantity times rate times invoice periods. Actual recognition follows recorded usage against the prepaid pool, not that header estimate.
Next steps
- Review the pool math and journal entries in How Usage Drawdown Works.
- Configure the pricing model in Usage Pricing: Flat and Tiered Models.
- Upload usage across contracts with Import Multi-Contract Usage.
- Close unused prepaid balances in Change Orders, Terminations, and Renewals.
- See how usage recognition fits ASC 606 and IFRS 15 in DualEntry.