Edits to Australian Tax Invoices
The Australian government has requirements for tax invoices in Australia. All Australian issued invoices need the following: To say 'Tax Invoice' instead of just 'Invoice' say 'GST' not 'Tax'- in Australia we only use the standard 10% GST on all goods and services and it needs to appear as 'GST' on the tax invoices We need a space to include our own ABN (Australian Business Number- all Australian based businesses require one) details on the invoice (another Australian gov requirement) We need a space in the client profile to include each clients' individual ABN. This also needs to appear on the tax invoice
Adding Telephone numbers to bill
Would like to see all current DID's that the customer has currently on the monthly invoice listed.
Add your own SMTP Relay to the Marketplace
By default, QuotingBill will include all email notification sending. No delivery receipts, no tracking, and emails will go out using the @ quotingBill.com domain. QuotingBill uses Mailgun as the default SMTP Provider. Adding your own SMTP Relay will allow you to use your own domain when sending emails and also, have your SMTP Relay provider give you any kind of analytics, tracking, and delivery receipts based on their own feature list.
Provision Call Paths (Netsapiens)
Have QuotingBill provision Call Paths into the Netsapiens switch, along with its corresponding product mapping
Provision SIP Trunks (Netsapiens)
Have QuotingBill provision SIP trunks into the Netsapiens switch, along with its corresponding product mapping
BIlling Audits (Netsapiens)
This feature will serve to have a process run (either manually or automatically) an audit against your Netsapiens instance. This feature will serve mainly for two purposes. 1) For QuotingBill customers that give permissions to their end client to provision more "billable" items on their own. With this Audit, by the end of the month, QuotingBill will be able to invoice whatever was added by the end client. 2) Regular billing audits. This will enable any Service Provider to run these audits at any given time and invoice their end clients on whatever is provisioned being used and not being billed. Essentially QuotingBill will read all accounts created in the switch (domains), pull "billable" items there, and compare them with each corresponding end client, identifying if it's being billed or not. After this, there will be a manual process to approve generating the charges to the end client.
Shopping cart functionality in customer facing portal phase 2
Have a way to export this shopping cart, so it can be added to any web page as an embedded code
This feature goes around the possibility to have a place where to calculate and charge "fees" to your end users. Fees meaning, literally anything, for example: A fixed amount for every X product or a percentage of Y sold product. Here are some basic functionalities. 1) Fixed and percentage amounts 2) Associable to specific products. 3) Frequency (How many times it will be charged). 4) Exclusions. Exclude specific customers.
Channel Partners (external QuotingBill users)
Let's say you have partners that sell your product, but they are nor part of your organization, and you don't want them to have the same access your regular system users have. This is what this feature is all about, having a way to grant them access to specific modules, like Quoting for example. And also have them properly "tagged" so it's easy to identify them.