DotNetInvoice Forums

I'm looking a solution that has all your features but a few more:

1. Allow credits to be given to a customer and the billing is adjusted accordingly. If the credit is greater than the outstanding balance, the client isn't sent an invoice.
2. Each invoice will show the accumulative balance in the event that a customer has missed a payment. So the amount to be paid is the balance rather than than a monthly recurring amount. When the client pays the oustanding amount all overdue invoices are reconciled.
3. Rather than creating and saving a monthly invoice is it possible to configure sallable items for a customer to be say monthly. This would be nice so then if we have other on-off items being billed to a client, they can be picked up by the monthly invoicing schedule and added to the monthly invoice?
4. Set the day of the month that an invoice will be sent off (Say day 1 of each calender month).

Am i asking too much and does it sound reasonable?

byoweb,

First of all, since you receive all of the source code with DotNetInvoice, it's definitely possible for you or your developers to make all of these changes exactly as you need.  It's also an option for us to do custom development for you.  Our standard rate is $125 / hour.

1. In our next release, our recurring invoices will handle positive and negative valued line items and have the option to roll the previous balance into the next generated invoice.  This balance is only per recurring invoice, not for all of the invoices that a client might have.

2. As noted above, balances will be carried forward to each recurring invoice that is generated.  This would not include creating one off invoices and if you had 2 recurring invoices for a customer, each would carry their own balance.

3. If I understand correctly, you would like to have a list of items that may be billed to a customer each month and you would like to check whether each is included before the next month's bill is created.  Currently, you could do this by removing items after one invoice is generated and then adding items as they apply during the month so that the correct invoice would be generated for the next month.  If all of this information is stored in another system of yours, it would be possible to export invoices monthly from your system and import them into DotNetInvoice.  You could also customize DotNetInvoice to look into your tables to create invoices or have your system add the items directly into DotNetInvoice.

4. DotNetInvoice currently allows you to select the date that invoices recur and how often you would like them to generate.  You can set an invoice to generate 7/1 and then every one month after that.  The next invoices would go out 8/1, 9/1, 10/1, etc.

For 1 and 2, if you need the credits to work over a client rather than just a recurring invoice, it is a more major change that we've had a few requests for in the past.  The database will need some changes in order to allow payments to apply to a customer rather than an invoice.  It is in our tracking system and will be considered when we look into features for the version after next.

For 3, we haven't had a request for something quite like this in the past.  We would need a few more details about how you would want to work with it before we look into it for our next version or develop a quote for us to do it as a custom add-on for you.

Please let us know if you have any other questions.

Jeremy,

Thanks for your extensive response. A few questions arise.

From a recurring billing point of view can we

1. configure it to occur x number of times at a periodic interval?
2. get notification when a credit card is close to expiry?

"For 1 and 2, if you need the credits to work over a client rather than just a recurring invoice, it is a more major change that we've had a few requests for in the past.  The database will need some changes in order to allow payments to apply to a customer rather than an invoice.  It is in our tracking system and will be considered when we look into features for the version after next."

This would be handy, especially if clients want a statement as well new billable items.

For point 3, I am happy to discuss over the phone. I'm in Sydney, Australia so we would need to organise a time that is convenient for both of us. If you PM me we could organise this offline.

Cheers

Paul

Paul,

Recurring invoices can be configured to generate every x days / months / years.  You can also set an end date to effectively limit the number of times they are generated.

Currently expired cards are deleted from the system, but there isn't an email triggered when it's in it's expiration month.  We'll add this to our feature tracking system.

The idea of statements has been brought up along with customer credits.  As of now, the new recurring invoice mechanism functions like this for the invoices within it.  When a customer logs in and has multiple open invoices, they will see all of them, the late ones highlighted in red.  They are allowed to pay each invoice one at a time.

We'll contact you directly to follow up about the list of items and adding them per month to invoices.