Skip to main content
How to understand your billing history?

Using Geekbot means that you are able to check what you pay at any time and keep track, simple and efficient.

Panos Mavrikos avatar
Written by Panos Mavrikos
Updated over 10 months ago

Geekbot tries to make billing crystal clear. If you need more information about payments made to Geekbot, you can find everything you need to know by going to your billing history.

Here, you'll find details relating to:

  • Everything you've ever been billed for

  • Every charge, refund, or deduction made to your account

  • How many credits are currently on your account

Billing History.png

...now, let's break it down and take a closer look 🧐

Credits

At the top of the page, you'll notice your credit count. Credits reflect the money you've paid: for every $1, we add 1 credit to your account.

Dates

The date is pretty self-explanatory; it's the date when an event in your billing history happened.

Events

In the Events column, you can see the events that occurred on each date, which will be one of the following:

  • Switching participant events: show every time you added someone to (or removed someone from) a workflow.

  • Subscription events: show every subscription renewal, or failure to renew, as well as changes to a monthly or annual plan.

  • Transactions events: reflect all charges made to your credit card, so you can refer back to events and record every transaction.

  • Credit allocation events: show when credits were added to (or removed from) your account β€” every time you add or remove participants, credits are either added to or deducted from your credit balance.

Actions

Actions relate to credits and payments. They help you keep track of the transactions made at every event. For example, every time your monthly subscription renews, a charge is made to your credit card with the charge showing as an action.

Balance

Finally, you have the balance column. Here, you can always see your current credit balance and the changes resulting from each event.

Did this answer your question?