Payments management is something Togai has natively so that the post-invoicing processing and receivables can be managed in a single platform. This also provides the ability to give credit limits and trigger alerts if those limits are breached.

This section is not related to payment processing via payment gateways like Stripe or Adyen. That is explained under the integrations tab

How are payments recorded within Togai?

There are 2 ways of recording a payment in Togai -

Mark as paid

This means every DUE invoice or an order has an option to be marked as Paid. This can be initiated or automatically using payment gateway triggers.

Recording a payment entry

Payments can also be recorded separately for every account or account group. Here, you can provide all the transaction details and payment instrument to keep track of the payment entries as a ledger balance.


The 2nd option mentioned above (recording a payment entry) is treated as a wallet. The main properties of a wallet are the ability to hold a balance and then be able to add to it or remove from it in the form of transactions as it happens in a ledger.

You can use this feature to model a pre-paid/advance wallet for your customers who can fund this and hold an advance amount. This amount can be kept in the wallet itself or utilized to net-off against pending DUE invoices or added as a new credit entry that does not expire to the customer’s account.

If you net-off a wallet balance against an ongoing invoice, then value of the ongoing invoice will be placed in ‘Hold’ in the wallet with only the balance available for utilization. This amount will update automatically as the invoice gets refreshed based on consumption.
When netting off against an invoice, you can also choose which invoice to net off the wallet balance against.
To model advance payments we suggest using wallet. To model marketing promotions we suggest credits. To model minimum commitments at a rate card level, we suggest credit grant rate card in the price plan.

Wallet flows

Wallet flow

  1. Customer makes payment as advance
  2. This is recorded as a wallet balance (can also be automatically triggered from a payment gateway flow)
  3. This can be assigned to an ongoing or due or partially paid invoice

If the invoice unpaid value > wallet balance, then the overage amount alone is pushed to the payment gateway, if such a flow is enabled. If invoice unpaid value < wallet balance, then that is netted off and remaining amount lies in the wallet itself.

The default behaviour of a wallet is netting off the invoices as they become due.