Accounting

Tight’s Accounting API is the special ingredient that differentiates the Tight API from other FinTech APIs. It underpins the Tight API as a whole, enabling an infinite amount of FinTech use cases.

​

1. How it works

As your user’s data flows into the Tight API, Tight’s “Invisible” Double-Entry Accounting is enabled in the background. Every expense, invoice, tax payment, etc. has the proper accrual basis, cash basis, and modified cash basis accounting transactions tracked in the background. Unlike most robust accounting software products available today, the “invisible” nature of this double entry accounting means that you can provide your users with all the robustness they need, without requiring your users to understand accounting. And, if you have power users (or bookkeepers) who want to get into the nitty gritty General Ledger (GL) transactions, they can absolutely do so, via your own UI or Tight’s Embedded experience for bookkeepers.

​

2. What it enables

The Accounting API enables you to build your product iteratively, without having to worry about infrastructure to support future use cases. For example, if you are building a simple expense tracking app, you can do so without worrying about future use cases such as printing balance sheets and filing taxes. Or, if you are building an invoicing app, you can focus on the user experience for just the invoicing portion of things, knowing that you will be covered if/when your product matures and your users start asking you for seemingly complex accounting functionality. The Tight Accounting API will have already kept track of their Accounts Receivable (A/R), and their Balance Sheet will have been kept up-to-date in real-time. You can focus on your immediate roadmap, while resting assured knowing that your future use cases will be supported due to the heavy back-end infrastructure that Tight is taking care of in the background.