Winforms / SQL Server 应用程序的会计系统

发布于 2024-08-24 02:47:54 字数 617 浏览 9 评论 0原文

如果您要编写一个垂直市场 C# / WinForms / SQL Server 应用程序并需要一个会计“引擎”,您会选择什么软件包?

我所说的垂直市场,是指该应用程序旨在解决一组特定的业务问题,而不是通用的会计应用程序。因此,该程序的附加值是成品中 70% 的非会计相关功能。 30% 的会计功能仅用于满足企业的基本会计需求。

我所说的一切都是为了导致这一点:会计引擎需要是免版税的运行时许可证,并且不是非常昂贵。我发现了几个 C#/SQL Server 会计应用程序,可以使用源代码和免版税运行时间,价格为 15 万美元以上,对于由大量资金资助的绿地开发来说这很好,但对于较小的应用程序来说,这种情况资本支出是不可行的。免版税运行时间大约 5000 美元到 15000 美元会更合理。开源会更好。

通过会计引擎,我的意思是至少要处理的事情:

  • 总账
  • 发票
  • 报表
  • 账款
  • 应收
  • 付款/贷项

基本上,会计引擎应该让开发人员专注于增值(行业特定的业务最佳实践/流程)解决方案的一部分,而不必担心如何实施复式记账系统的低级细节。

理想情况下,会计引擎应该是在免版税运行时基础上获得许可的。

请提出建议?

If you were going to write a vertical market C# / WinForms / SQL Server application and needed an accounting "engine" for it, what software package would you chose ?

By vertical market, I mean the application is intended to solve a particular set of business problems, not be a generic accounting application. Thus the value add of the program is the 70% of non-accounting related functionality present in the finished product. The 30% of accounting functionality is merely to enable the basic accounting needs of the business.

I said all that to lead up to this: The accounting engine needs to be a royalty-free runtime license and not super expensive. I've found a couple C#/SQL Server accounting apps that can be had with source code and a royalty free run time for $150k+ and that would be fine for greenfield development funded by a large bankroll, but for smaller apps, that sort of capital outlay isn't feasible. Something along the lines of $5k to $15k for a royalty-free runtime would be more reasonable. Open-source would be even better.

By accounting engine, I mean something that takes care of at a minimum:

  • General
  • Ledger
  • Invoices
  • Statements
  • Accounts Receivable
  • Payments / Credits

Basically, an accounting engine should be something that lets the developer concentrate on the value added (industry specific business best practices / processes) part of the solution and not have to worry about how to implement the low level details of a double entry accounting system.

Ideally, the accounting engine would be something that is licensed on a royalty free run-time basis.

Suggestions, please ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(7

几味少女 2024-08-31 02:47:54

@Craig我知道这可能不是您问题的准确答案,但老实说您要求的开发并不那么复杂。复式记账本身就是一个非常简单的数据转换模型。您所需要的只是一个包含帐户的表格以及用于日记帐和分类帐的表格。编写代码以在这些表之间移动条目最多需要几天的时间来编写和测试。根据我的经验,大多数会计系统都是主要市场,因为大多数业务核心运营都依赖它们,因此它们会很昂贵。如果您无法编写核心功能,我建议您聘请合同人员来编写核心功能。

@Craig I know this may not be an exact answer to your question, but honestly what your asking for is not that complex to develop. Double entry book keeping is of itself a pretty simplistic data transformation model. All you need is a table with accounts, and tables for journals and ledgers. Writing code to move entries between those tables would take a couple days at most to write and test. In my experience, most accounting systems are prime markets since most business core operations rely on them, and so they will be expensive. I would recommend hiring someone on contract to write the core functionality if you are unable to.

莫言歌 2024-08-31 02:47:54

这是一个建议:www.objacct.com

Here is one suggestion: www.objacct.com

堇年纸鸢 2024-08-31 02:47:54

我想到了 Microsoft Dynamics GP
我还没有听说有人授权它进行重新包装,但是
我知道您可以对其进行调整并将其扩展到不同的市场。

它可能适合您让开发人员集中精力的需求
在价值广告上。

不过,对于您的需求来说,它可能有点重。
我提到它是因为我的很多客户都在使用它。

另一种可能更接近您需求的选择是
AdaptAccounts

Microsoft Dynamics GP comes to mind.
I have not heard of anyone licensing it for repackaging, but
I know you can adapt it and extend it for different markets.

It might fit your need of allowing the developers to concentrate
on the value ad.

It might be a bit heavy for your needs though.
I mention it since a lot of my clients are using it.

Another option which might be closer to your needs is
AdaptAccounts

逐鹿 2024-08-31 02:47:54

Sage Software Accpac 是一款出色且在全球享有盛誉的软件

Sage Accpac ERP 的 SDK 让一切变得简单通过 COM 对象进行集成,并且正在使用不同的 DBRM 引擎,例如 Pervasive SQL 和 SQL Server(仅举这两个)。

另外,您可以根据公司的需求选择购买的模块。现在,这一切都取决于您的预算,因为它是一种商业解决方案,众所周知,有点昂贵,但绝对可靠和稳定。

One that is excellent and of good reputation around the globe is Sage Software Accpac

The Sage Accpac ERP's SDK makes it simple to integrate via COM objects, and is working on different DBRM engines such as Pervasive SQL and SQL Server, just to name these two.

Plus, you may choose what module you buy for your company's needs. Now, it all depends on your budget as it is a commercial solution that is renown to be a little expensive, but definately reliable and stable.

许你一世情深 2024-08-31 02:47:54

Open Systems, Inc. 的 TRAVERSE 可能是一个选择。 .net、SQL、C# 会计和商业软件。轻松与第三方垂直行业集成。

TRAVERSE from Open Systems, Inc. may be an option. .net,SQL,C# Accounting and Business software. Integrates easily with third party verticals.

So尛奶瓶 2024-08-31 02:47:54

我过去曾四处寻找此类事情,并且总是得出使用商业会计包并进行尽可能多的集成的结论。造成这种情况的原因有几个,包括:

  1. 使用通用的商业会计软件包,您通常可以找到能够使用它而无需付出太多努力和/或培训成本的人。
  2. 如果您的垂直应用程序旨在与外部会计应用程序集成,并且成功,那么您可以构建与潜在客户可能已经拥有的其他软件包的集成。
  3. 一般来说,大多数公司的外部会计师 (CPA) 都希望能够知道其客户所使用的会计应用程序是众所周知且受支持的。这样做的原因有很多,包括节省执行年度任务的成本(例如公司税)。通过通用应用程序,注册会计师通常可以请求已经存在的非常具体的报告/信息。

还有很多优点,但我相信您已经了解了。

根据客户在会计方面的需求,您可以从 QuickBooks 开始,然后从那里开始升级。周围总有人知道如何在 QuickBooks 中工作,并且它有一个不错的集成 API。从那里您可以升级到许多 Sage 解决方案和/或 Microsoft 解决方案,因为它们非常常见且广泛使用。

我知道您说过您想要构建 API/引擎,但我强烈建议考虑与标准商业包的集成选项。

I have looked around in the past for this type of thing and have always came to the conclusion of using a commercial accounting package and doing as much integration as possible. There are several reasons for this including:

  1. With a common commercial accounting package, you can usually find someone who is able to use it without much effort and/or cost of training.
  2. If your vertical app is built to integrate with an external accounting app, and it is successfull, you can build integration to additional packages that potential customers may already have in place.
  3. Generally, external accountants (CPAs) for most companies like to be able to know that the accounting application that their client is using is well known and supported. There are a lot of reasons for this including cost savings on doing annual tasks (such as corporate taxes). With a common application, the CPA often can request very specific reports/info that already exist.

There are many more advantages, but I am sure you get the picture.

Depending on the needs of you clients in terms of accounting, you can start as basic as QuickBooks and go up from there. There is always someone around that knows how to work within QuickBooks and it has a decent integration API. From there you can step up to many of the Sage solutions and/or Microsoft solutions as they are very common and widely used.

I know that you stated that you want and API/Engine to build on, but I would highly suggest considering the integration option with a standard commercial package.

溇涏 2024-08-31 02:47:54

检查 XERP.Net @ http://xerpdotnet.codeplex.com ,它看起来很有前途(它是免费的,但依赖于XAF 最初将花费您每个开发人员 2,000 美元,一年后大约花费 800 美元,无论如何您都会获得一个完全加载的 DevExpress 工具)。

Check XERP.Net @ http://xerpdotnet.codeplex.com , It looks promising (It's free but rely on XAF which will cost you 2,000$ per developer initially and around 800$ a year later and you will get a fully loaded DevExpress tools anyways).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文