Credits and billing
What does not consume credits
The list of what you can do without watching the balance, which is longer than people think.
Almost all documentation about credits explains what gets charged. The side effect is that many people end up using the platform with the handbrake on: not searching just in case, not opening a file just in case, not showing something to a colleague just in case. The opposite list is worth having.
What does not consume
| Action | Comment |
|---|---|
| Logging in, browsing and consulting | Opening files, viewing documents and checking history |
| Searching your documents | Content search is not a charged action |
| A third party supplying or signing | Whoever receives the request pays nothing: consumption is on the sender |
| Downloading a report already generated | Generating it counts; downloading it again does not |
| Receiving the daily digest | Sending is not counted; what counts is generating it |
| An agent thinking | Its actions count; the internal processing does not |
Important
The third row is worth saying out loud when you work with small suppliers. It is their first question — "is this going to cost me anything?" — and the answer is no: they enter by their link, upload theirs or sign, and need no account, no licence and no balance.
What does consume, in short
It is an easy pattern to remember: you are charged when the platform does something for you outward or with AI. Looking at what is already inside, no.
Watch out
The nuance that confuses anyone reading the credit policy: it lists concepts that are not being charged today. **The source of truth is your consumption breakdown, not the price list**: if a concept does not appear in the month's breakdown, you were not charged for it, whatever the table says. And if it ever started being charged, it would show up there.
What to tell the team
- 1
Search without fear
The cost of not finding something is far higher than any search.
- 2
Do not resend out of habit
There it does count: every resend is a new send, and it is usually avoidable by checking the status.
- 3
And run trials on a real case
Repeating the same send twenty times to demo it does consume.
Worth knowing
If someone on your team avoids using the platform "to save credits", that costs more than the spend it avoids: the documentation ends up outside, in an inbox, and that is where it gets lost.
›Does checking history cost anything?
No. Consulting what is already stored is not a charged action.
›What if a supplier uploads ten documents?
What is counted is the request you sent, not each file they supply.
›How do I know exactly what I was charged for?
The breakdown: it shows action, date and area. It answers any doubt in this article.
A real case
The situation
A team avoids searching and opening files "to save credits".
What you do
- Checks the breakdown and sees consulting is not a charged action
What you get
They stop working with the handbrake on and the month's consumption does not change.
The situation
The team avoids consulting in case it consumes.
What you do
- Checks which activities do not consume
What you get
Usage stops being held back out of caution.
The situation
People search local folders rather than looking here.
What you do
- Confirms that searching does not consume
What you get
Work returns to where the information is.
The situation
Inviting a colleague is avoided for fear of cost.
What you do
- Checks what depends on licence and what on usage
What you get
The team comes in without surprises.
The situation
Documents are downloaded to avoid reopening them.
What you do
- Confirms which actions are free
What you get
Information stops being duplicated outside.
The situation
Decisions are taken without knowing what is free.
What you do
- Checks the list before deciding
What you get
The decision uses the fact.
This article answers
- what is free on the platform
- does viewing documents use credits
- does the signer pay anything
- does downloading a report consume