Month-to-month and usage-based contracts
Not every contract is a fixed term with one price. Some bill monthly, some by usage, and June only had one shape to put a contract in. Those contracts showed the wrong cost, sometimes zero, so your spend numbers were off and you couldn’t plan a budget off them.
Now you record each contract in its real shape, log payments against it, and see spend in that contract’s own terms.
Contract types
Create a contract as fixed-term, recurring with a monthly price, or usage-based.
Payments and spend
Record payments against a contract. Spend shows in the contract’s own terms: a monthly amount for recurring contracts, the committed total for fixed-term contracts. Spend to date fills in base charges automatically.
From chat
Ask June to create a contract or record a payment.
Improvements
- Peripherals Added monitors, keyboards, mice, docks, headsets and headphones as asset types.
- Peripherals Added a lean detail page and a type filter in the assets list.
- Chat Can now create peripherals (monitors, keyboards and similar) from a catalog product from chat.
- Chat Can now add or update catalog products from chat.
Fixes
- Dates Fixed hire, leave, contract, purchase and warranty dates showing one day early for US users.
- Dates Fixed date pickers saving a day early east of UTC.
- Employees Fixed the employee Assets tab missing assets when the email capitalization differed.
- Okta Fixed apps staying “Unmanaged (SSO)” after the person’s Okta assignment or group access was removed.
- Contracts Fixed the link-to-application popover in the contracts table not opening.