首先编写多层设计，该设计应涉及多个物理服务器。一台包含客户发票/账单数据的数据库服务器。一台中间层业务服务器来存储您的业务逻辑。以及一台只能与业务层对话而不能与后台数据库对话的 Web 服务器！如果可能，请将数据库保留在不同的网络中。最好是没有通往外界的网关的网络。
Keep it secure! Make sure your users can get the information through a password-protected HTTPS connection! Let the users pick their own passwords. And be careful because billing/invoice information is considered very sensitive, thus be prepared someone will attempt to hack into this system. There will be people who will attempt to abuse this invoice system so one thing is important: Security!
Some companies have gone completely broke after having to pay for damages simply because a hacker gained access to their system!
Start with writing a multi-tier design, which should involve multiple, physical servers. One database server with customer invoice/billing data. One middle-tier business server to store your business logic. And one web server which can only talk to the business layer and not to the database in the background! If possible, keep the database in a different network. Preferably a network that has no gateways to the outside world.
您是否正确实施了计费/发票系统，或者只是创建 pdf 并发送链接的部分？如果是前者，您必须提供实际要求才能获得指导。如果是后者，像 SSRS 这样的东西就可以很好地工作。
Are you implementing the billing/invoicing system proper, or just the part that creates a pdf and sends out a link? If the former, you'd have to provide actual requirements to receive guidance. If the latter, something like SSRS could work well.
Unless you have a very small company or a very unique/niche business, it might be a lot less painful to look into purchasing a 3rd party billing/invoicing system and then customize it as needed.
A commercial product will probably have a lower cost of ownership in the long run, and they will already have thought out all the security issues and done a lot of numerical testing, which could save a lot of money in mistakes. An additional bonus would be industry-standard interfaces to link your billing/inviocing system with your accounting system, CRM, etc. If you write your own, you will have to work all of this out yourself.
Interface with your accounting software and let it do most, if not all, the work. On the two projects where we've done billing & invoicing, the one that was successful had several developer-years of work put into it; the other one worked but it was/is a maintenance nightmare.
If you still opt to do it all in-house, unit-testing (especially regression testing) is key. You have to be sure any fixes don't break anything else. With these tests, it's wise to have a very large test base.
发布评论
评论（6）
确保安全！确保您的用户可以通过受密码保护的 HTTPS 连接获取信息！让用户选择自己的密码。并且要小心，因为账单/发票信息被认为非常敏感，因此要做好有人试图侵入该系统的准备。会有人试图滥用这个发票系统，所以有一件事很重要：安全！
有些公司仅仅因为黑客入侵了他们的系统而不得不支付损失赔偿后就彻底破产了！
首先编写多层设计，该设计应涉及多个物理服务器。一台包含客户发票/账单数据的数据库服务器。一台中间层业务服务器来存储您的业务逻辑。以及一台只能与业务层对话而不能与后台数据库对话的 Web 服务器！如果可能，请将数据库保留在不同的网络中。最好是没有通往外界的网关的网络。
Keep it secure! Make sure your users can get the information through a password-protected HTTPS connection! Let the users pick their own passwords. And be careful because billing/invoice information is considered very sensitive, thus be prepared someone will attempt to hack into this system. There will be people who will attempt to abuse this invoice system so one thing is important: Security!
Some companies have gone completely broke after having to pay for damages simply because a hacker gained access to their system!
Start with writing a multi-tier design, which should involve multiple, physical servers. One database server with customer invoice/billing data. One middle-tier business server to store your business logic. And one web server which can only talk to the business layer and not to the database in the background! If possible, keep the database in a different network. Preferably a network that has no gateways to the outside world.
不要发送 0.00 美元的发票。我讨厌那样。 ;)
Don't send invoices for $0.00. I hate that. ;)
您是否正确实施了计费/发票系统，或者只是创建 pdf 并发送链接的部分？如果是前者，您必须提供实际要求才能获得指导。如果是后者，像 SSRS 这样的东西就可以很好地工作。
Are you implementing the billing/invoicing system proper, or just the part that creates a pdf and sends out a link? If the former, you'd have to provide actual requirements to receive guidance. If the latter, something like SSRS could work well.
除非您拥有一家非常小的公司或非常独特/利基的业务，否则考虑购买第 3 方计费/发票系统，然后根据需要对其进行自定义可能会轻松很多。
从长远来看，商业产品的拥有成本可能会较低，而且他们已经考虑了所有的安全问题并进行了大量的数值测试，这可以在错误中节省大量金钱。额外的好处是行业标准接口，可将您的计费/发票系统与会计系统、CRM 等连接起来。如果您自己编写，则必须自己解决所有这些问题。
Unless you have a very small company or a very unique/niche business, it might be a lot less painful to look into purchasing a 3rd party billing/invoicing system and then customize it as needed.
A commercial product will probably have a lower cost of ownership in the long run, and they will already have thought out all the security issues and done a lot of numerical testing, which could save a lot of money in mistakes. An additional bonus would be industry-standard interfaces to link your billing/inviocing system with your accounting system, CRM, etc. If you write your own, you will have to work all of this out yourself.
考虑使用 SSRS 或其他一些报告包来创建 PDF 并将其发送给您的客户。
Consider using SSRS, or some other reporting package, to create and send the PDFs to your customers.
与您的会计软件交互，让它完成大部分（如果不是全部）工作。在我们完成计费和计费的两个项目中发票方面，开发人员投入了数年的工作，取得了成功；另一个可以工作，但这是一场维护噩梦。
如果您仍然选择在内部完成所有工作，那么单元测试（尤其是回归测试）是关键。您必须确保任何修复都不会破坏其他任何内容。通过这些测试，拥有一个非常大的测试基地是明智的。
Interface with your accounting software and let it do most, if not all, the work. On the two projects where we've done billing & invoicing, the one that was successful had several developer-years of work put into it; the other one worked but it was/is a maintenance nightmare.
If you still opt to do it all in-house, unit-testing (especially regression testing) is key. You have to be sure any fixes don't break anything else. With these tests, it's wise to have a very large test base.