This optional layer has been designed to offer the capability to split one invoice into multiple invoices to be dispatched to different entities.
As an example, this can be used to answer a customer accounting requirement to have separate invoices for capital and operating expenditures for example. Another scenario is when one customer company want different business entities to be invoiced separately for different items.
The split in multiple invoices can be based on various criteria such as the offer, an accounting code or any other customer references.
Once all the necessary information required per invoice has been generated, we prepare the invoice content itself covering four main sections:
The content and presentation of the details is fully customizable, every customer have their own specific way of showing that information. In Telco or any business billing many various events, there are different options to aggregate them per day, per conference, per destination at the customer leisure with the focus to keep them easy to read for the end customer.
The output of the invoicing layer is a JSON document which contains both the content of the invoice to generate as well as the related input for the ledger to ensure consistency.
We’re almost at the end of our journey !
The output from the invoicing layer is then organized as per a predefined template and used to generate a pdf with the proper look & feel of the company.
This predefined template will vary depending on the invoicing company or even the type of offer, there is no limitation in the number of templates BillingLabs can manage.
Steady, ready, POST !
The invoice document is now ready to go ! We can post them on a directory, a sharepoint folder, a SFTP server or any other form of secured repository where it can be distributed from.
We can also send it via email or any other way including specific country relative system such as Chorus PRO in France for public affair invoicing.
