Overview

The Invoice Simulator is a tool that allows you to simulate the generation of an invoice.

The simulator can have two different use cases:

• Billing Debug: You can use the simulator to debug the billing configuration and see how the invoice is generated depending on the Billable Element Context.
• Customer Service: You can use the simulator to simulate invoice and provide information to the customer directly or through an agent. This is useful when the customer has questions about the invoice or when you want to provide an estimation of the invoice before it’s generated.

How to access the simulator

To access the simulator you need to navigate to the Invoice Simulator tab in the Wattyo Billing app.

//TODO CHANGE IMAGE

Context Manager

The context manager is the main component of the simulator. It allows you to define the context of the invoice that you want to simulate. Here you can define the Billable Element you want to invoice both selecting one or creating one virtually from scratch.

Additionally you can define the following information:

• Terms: the billable element terms to be used in the calculation.
• Usages: the usages to be used in the calculation.

Invoice Simulation

Once you have defined the context you can click on the Simulate button to generate the invoice. The invoice will be generated and shown in the Invoice Simulation section.

Note that the invoices are never stored in the database, they are only generated in memory and shown in the simulator.

Once the simulation have been generated you will be able to see the following information:

• Applied Rules: the rules that have been applied to the invoice.
• Discardd Rules: the rules that have been discarded and the reason for it.
• Concepts: The different generated Billable Concepts with its quantity, price and taxes and the rule/s that generate it. In case more than one rule generates the same concept you will see all the rules that generate it in a Tree format.
• Performance: The performance of the simulation in terms of time. This is useful in case you need to debug performance issues in the billing process.