The standard models, billed automatically.
Billing software for SOC contracts priced per endpoint, per user, by retainer, by package or by incident response hours, each billed automatically the way the contract is written.
What makes it hard.
- 01
Every contract bills differently
Contracts differ in which number they bill on, and how.
- 02
Hour blocks to track
Each client’s incident response hours run down through the year.
- 03
Minimums and true-ups
Committed numbers and true-ups have to be applied on time.
What you get.
The right numbers, every time
Each contract billed on what it names.
Minimums and true-ups applied
Applied automatically, as the contract says.
Hour blocks tracked
Incident response hours tracked, and hours over the block billed.
Retainers and packages
Billed correctly, every month.
Nothing goes out until you say so.
Nothing goes out without you
Every invoice waits for your approval.
Every change on record
A full history of every change.
Each client kept apart
Every client’s data kept separate.
Only what billing needs
SOC Tally only uses the information it needs for billing.
Questions we get asked.
Can we bill on the month’s peak instead of the average?
Yes. Each contract says which count it bills on, and SOC Tally uses that one.
How are minimums and true-ups handled?
Minimums are applied every month, and true-ups when the contract says they’re due. Both happen automatically.
Can prices rise each year?
Yes. Set the yearly rise in the contract, and the new prices apply from the date it says.
How are incident response hours tracked?
Each client’s block runs down as hours are used, and hours over the block are billed.
Other ways in.
Simplify next month’s SOC billing.
Join the waitlist, and we’ll show you SOC Tally on contracts like yours.