Leaderboard

OK - I've coded up my own solution: Note the highly visible View Invoice button, plus I've tarted up those other links as well so the bank nobs know where to click. Only a very small hack to the client_invoices.pdt template. The View Invoice page shows full individual invoice in site chrome very similar to PDF version (but with more, as I've added my own terms and custom payment options data), with option to further open same inline invoice layout in new window as printable version without site chrome - shown below, with ubiquitous Print button. Fingers crossed, that should get me over the line with the bank.

Hi! In my Blesta install, the default currency is HUF. Under Active Currencies=>Edit Currencies I set it up in a format that it only shows whole numbers (1200 not 1200.25). In Hungary the sales tax is 27%, so when it adds tax on top of 20 HUF, on the invoice is 25.4. Can you tell me how can I set it up the invoice amount with rounding? Thank you for your help! Zoltan

To be safe, you will need to import your data into a fresh 3.0.3 install. Install with a trial key, and keep your other v3 install up and running. Then run down and compare the two after you import your data, and update the themes, email templates, and other settings with the changes you have made. Having them side by side should help.

No problem, but I didn't do much haha just said you could do most of them Good luck with your business, but you can't go wrong investing in Blesta, it's the best billing system out there in my opinion.

Yes. What I meant about late notices and auto-debit is that regardless of how an invoice was created (Automatically by Blesta, manually through the interface, or via the API) the invoice is treated the same way moving forward. There is a feature that can send up to 3 late notices / payment reminders, and a feature that can automatically charge a credit card x days before an invoice is due. These features can still be utilized, if you want, even when creating an invoice via the API. I mentioned this because in your original post you asked about a reminder.. so, those reminders, if you have them set up, will still be sent when creating an invoice via the API.

It's against Mastercard/Visa merchant rules to store CVV data in any way, shape, or form. The CVV data is passed along by Blesta when processed live via customer input, but never saved. This makes it impossible to send CVV data if using auto-debit. Cody or Tyson may be able to comment on sale vs preauth, however I'm not sure I see the correlation with CVV data. I wouldn't think a capture should take place if there is an issue with CVV or AVS. Don't most merchants automatically do a preauth, then capture? I guess the side affect here is that the immediate void BluePay is doing results in the funds being held up in the customers account for several days, and you are charged a processing fee?

You may wish to use the API to create the invoices on the 1st of the month, each month, based on your other systems evaluation of whether they owe $5 or more. I think this is where you're headed? In this case, the client would have no services in the system, and Blesta would not invoice on its own. Any invoices you create via the API will still work similarly however, with late notices being sent how they are configured, and auto-debit running if configured as well.

Invoices are sent out X days before a service renews. This value is configurable, so you can invoice someone 5 days before, 10 days, 30 days, etc etc. The due date of the invoice is always the date the service renews. Yes, virtually everything you can do in the interface, you can do via the API. Essentially all public method models are available through the API, including those for plugins. See http://docs.blesta.com/display/dev/API for information on the API. If you scroll to the bottom you'll see source code documentation which you'll need.

No, Blesta will only pull from the database referenced in the config file in config/blesta.php You will need a v2.5 license. If you purchased before Aug 14th and bought an owned license you should have a v2.5 license also. Open a ticket with us with the new domain so we can re-issue it to that. If it will be installed at the same domain/subdomain as before, regardless of sub-directory it will work. If you have a backup and might need to restore it, I would copy it down just in case. Did you verify your data was imported properly initially? Were there invoices prior to Aug 1st?

Whoa! That didn't take long.

... That's really nitpicking. Can't we stick to facts instead of using minor technicalities out of context to invalidate one another? Blesta v3 lacks proven stability in that it has had a fair amount of bugs and it's only been out a short time with limited use/testing, but what is there has proven to be sufficiently stable for me. It is my opinion based on years of experience that the Blesta v3 code is of high-quality, including security, especially when compared to the competition. If that weren't true then I wouldn't be having this conversation with you in the first place. I respectfully disagree. I have not the time to reiterate the shortcomings which have been reported and acknowledged by the developers. However, I will say that I do not think Blesta is yet as feature complete as it's competitors. It's also not yet as expensive, so that seems fair to me. In terms of these judgements, how much experience do you have with the competing software packages? How many PHP/MySQL applications on this scale have you built? Myself, I've worked with ModernBill (years ago, before it got bought up) and I use HostBill, ClientExec, Ubersmith and WHMCS nearly daily while working with our resellers, clients and vendors. As for PHP/MySQL applications I've built on similar scale... dozens. Try selling a dedicated server with Blesta, then try it with any of the aforementioned packages, without external modules for either, and then tell me if you think Blesta is more flexible. I actually just worked out an agreement with Paul to purchase 3 more licenses, with the plan to add 7 more soon. That should display my long-term confidence in Blesta.

This has been fixed in CORE-774 for v3.0.4. To patch yourself, update /app/models/invoices.php (line 885): Replace: // Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); return $invoice_id; With: // Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); // Update invoice totals $this->updateTotals($invoice_id); return $invoice_id;