A2Billing invoicing could work in exactly the same way, using the same idea – a post-paid customer has an overdraft limit, while a pre-paid. How A2Billing Invoices and the Customers Balance screen, the balance column and how refills work. asterisk 2 billing platform. Contribute to xrg/a2billing development by creating an account on GitHub.

Author: Faudal Grogor
Country: Djibouti
Language: English (Spanish)
Genre: Career
Published (Last): 28 January 2017
Pages: 323
PDF File Size: 6.73 Mb
ePub File Size: 7.9 Mb
ISBN: 926-2-31967-174-4
Downloads: 2577
Price: Free* [*Free Regsitration Required]
Uploader: Kazirn

Users browsing this forum: Google [Bot] and 0 guests. Mon Dec 31, A2Billing invoicing – proposed work flow. Tue Jan 19, 6: Dear all We need your input. I’ve been giving some thought to the process of invoicing, and I believe that I have come up with a relatively simple logic of how it should work.

Introduction The general principle is that invoicing works exactly like a bank statement that you get every month. It shows debits, and credits, with a value carried a2bllling from the last statement.

A2Billing invoicing could work in exactly the same way, using the same idea – a post-paid customer has an overdraft limit, while a pre-paid customer does not. There are two approaches to invoicing in accounting. Send an invoice, and when it a2hilling paid, mark it as paid. Send an invoice every month, with the balance carried a2billinv from previous invoices. Thus the latest invoice replaces all previous invoices. In my opinion, Option 1 is suitable for selling phones, or consultancy, e.

The process Each customer has a balance available to them — this is a net value — excluding taxes, and a credit limit, which is also a net value. The amount of balance available will either be the value of money given to you by the customer, or it will be w2billing credit limit you have given the customer, plus any money they have given you.

On invoice day – which is set in the customer page. It is now fixed as a permanent record for that month’s usage in terms of payments, charges and calls made, and of course TAX. The balance from that invoice is recorded, and a new preview invoice invojce, with the first line being the balance carried forward from the previous month.

The Balance carried forward comes from the total net charges, less the total net payments in the previous month. Then the whole process starts again. A record of the invoic and date that the new preview invoice is created is kept, so that only items after this x2billing and time are recorded on the new invoice. The key to this a2billinng that anything that changes the customer’s balance must be written to the customer’s preview invoice, or the system falls down, and you do not have an audit trail.

A2Billing – PostPay, Invoices and Customers Balances

Advantages I believe that this approach will have the following advantages: A unified approach to all charges of whatever nature that are applied to a customer’s account, making it easy to understand. Most people are familiar with a bank statement, so the concept will be familiar to most customers, as our system would work in the same way.

Remove complexity of paying money against invoices. Simply an outstanding balance maintained. Flexibility in whether a customer is pre-pay or post-pay, simply by changing the credit limit of the customer – e. No requirement to set payments against individual invoices, with the complexity and administration that this requires. A complete audit trail for every customer.

Finally, because all the core information is in one place – creating invoices, statements, or receipts in any format can be done from the same raw information from what we may call a transactions table, simply by running an appropriate query, and displaying the information as desired. Invoice items may not be edited in terms of amounts, as to change the amount would put it out of sync with the Outstanding balance.

Corrections can be made by adding a line credit or debit onto the invoice during the billing period, which is either negative or positive. No changes can be made to the outstanding balance unless a line is written to the transactions table listing that transaction that changed the balance.


Services are disconnected when the customer exceeds his credit limit – e. Effectively, each invoice sent out will replace the last invoice in terms of amount to pay, as it includes the balance carried forward. Payments can be made either in excess of the invoice, or less than the invoice and the system will cope.

Nice to have The preview invoice can be closed off at any time of the month by the admin, and a new preview invoice restarted with the current outstanding balance. This could be done on a customer by customer basis, or run by pressing a button, and invoicing a particular subset by filtering on customers first – a bulk update for instance.

This would allow a customer to have their final bill, as the balance would be reset to zero. Alternatively, the customer could close off their own invoice and pay it. In conclusion The key to understanding this is to regard the system like bank statement.

One disadvantage is that different types of service attract different levels of VAT, this will not be easy to include in the current version of A2Billing, as it is an accounts based system, but I am sure there are work arounds which can carry is through to the next version of A2Billing, where we can write this requirement in from the ground up. Can you help Please could you inspect the work flow above, and tell us if it is acceptable, and please pick holes in it, or ask any questions where it is not clear.

We do not want to be re-designing this again, and we are keen to get it right. Initial indications show that there is a lot of work in doing this.

We will come up with an estimate of how much work is involved after we get your comments.

Fri Invioce 22, 4: Joe, Implementation of invoicing in A2Billing is currently flawed and imperfect. This time you have presented “the right concept” of telecom invoicing.

I totally agree with your 2nd approach as this is the way telecom invoicing is implemented. Regarding customers closing off their own invoices, I believe this is flawed and can produce unwanted results in the long run. Moreover adding search facility by lastname, invoice date, invoice no, account no etc on invoices page would definitely make inovice even better. Fri Jan 22, 8: Hi Thank you for your attention and your reply. It is appreciated I was beginning to think that one or more of the following is true: You say that customers should jnvoice close off their own invoices – I was thinking along the lines of customers being able to settle their account to current date.

The only issue that I can see is that this may cause some unexpected load during the day for busy customers.

What are your thoughts on why it should not be allowed? We could do with more input as to whether this is the right or wrong approach, and whether anyone can see any flaws in the system, and finally, whether the system is easily understood. Fri Jan 22, 1: Hi, I am still digesting the post. However, I really do not want customers closing invoices. I think it will cause added support tickets requesting re-opening or correcting an invoice. More after further digestion. Sun Jan 24, 7: Joe, I believe, letting customers do their invoices will result in following 1 Increased business admin work e.

Regarding the understanding, It’s very similar to a bank statement and also I’ve seen invoices from well established telecom companies using the same format. So people already familiar with it.

A2billijg Jan 31, 2: The ability for a invoice to be closed by a billing cycle or the customer is simple and should stay. One can assume that if the customer pay the balance on the invoice they have ijvoice with the charges on it. I expect no one to pay an invoice that they have ingoice and a ticket will come if there are any. Since one can not make changes to a line item on it, a correction must be created to fix any discrepancy thus documenting every transaction.


I a2bbilling not sure I understand the diff from option 1 or 2. abilling

A2Billing : VOIP Billing, Softswitch & Calling Cards Software

One can still pay on that invoice a different amount where it should only mark the invoice is paid. Any difference is just forwarded as a line item in the next invoice. This would eliminate the need to have “postpaid” and “prepaid” customer. Sun Jan 31, 5: Tue Feb 02, 8: Hi There is a major difference between options 1 and 2 of how to create invokce invoice.

Option one expects an invoice to be created, and then paid in full. If a number of invoices are created, then the amount owed will be the total of all the invoices ever issued and not marked as paid. Option two creates an invoice, and the balance carried forward from all previous invoices, so to get an amount owed, one only has to look at the final invoice, as it will include the values from all other invoices.

In terms of maintenance – option one would require two processes – 1. Mark the invoice as paid, and 2, Show the amount credited. The system gets difficult to understand if a customer over pays, or under pays. Option two only requires that payments received are entered into A2Billing, a2biloing the system easily copes with under payments and over payments, as well as requiring less mouse clicks to maintain, and thus for a telecom billing system where the amounts owed by the customer, and the transactions made are happening almost on a minute by minute basis as calls are made, this is more suitable.

In respect of the customer being able to close their own invoice, and given the number of objections to that feature in invojce thread, I do not think that is necessary now, and and may cause support issues, particularly if they keep pressing the button, they will end up with dozens of invoices. However, for admin to have this ability to present an upto date final bill for someone who is say closing their account would be desirable. Les – your assessment is clear and correct, which to my mind validates the methodology, as you have clearly understood the process.

Our main concerns about rewriting this is the time it will take to implement this, and the level of instability that may be induced by what would appear to be minor changes on the surface, but in fact cause ripple effects elsewhere.

It is quite a big coding job, as every single item that changes the balance recurring service, DID, Subscription, charge, refill, payment, CDR, plus a few I may have forgotten has to write a record to a transaction table, and from that, the invoices can be generated, which is another big coding job. Before spending the time to do an assessment of hours and cost on this, nivoice really need more affirmation that this is invojce right way forward.

Tue Feb 02, Hi It is quite a big coding job, as every single item that changes the balance recurring service, DID, Subscription, charge, refill, payment, CDR, plus a few I may have forgotten has to write a record to a transaction table, and from that, the invoices can be generated, which is another big coding job.

Wed Feb 03, 5: