This plutus plugin is a Ruby on Rails Engine which provides a double entry accounting system for your application.
For the rails 2 version, you can go here:
https://github.com/mbulat/plutus/tree/rails2
Gems in RubyGems.org >= 0.5.0 support Rails 3
-
Add the gem to your Gemfile
gem "plutus" -
generate migration files
rails g plutus -
run migrations
rake db:migrate
The plutus plugin provides a complete double entry accounting system for use in any Ruby on Rails application. The plugin follows general Double Entry Bookkeeping practices. All calculations are done using BigDecimal in order to prevent floating point rounding errors. The plugin requires a decimal type on your database as well.
The system consists of a table that maintains your accounts and a table for recording transactions. Transactions are the recording of debits and credits to various accounts. The transaction table, which records your business transactions is, essentially, your accounting Journal
Posting to a Ledger can be considered to happen automatically, since Accounts have the reverse has_many relationship to either its credit or debit transactions
The Account class represents accounts in the system. The Account table uses single table inheritance to store information on each type of account (Asset, Liability, Equity, Revenue, Expense). Each account must be subclassed as one of the following types:
TYPE | NORMAL BALANCE | DESCRIPTION
--------------------------------------------------------------------------
Asset | Debit | Resources owned by the Business Entity
Liability | Credit | Debts owed to outsiders
Equity | Credit | Owners rights to the Assets
Revenue | Credit | Increases in owners equity
Expense | Debit | Assets or services consumed in the generation of revenue
Each account can also be marked as a "Contra Account". A contra account will have its normal balance swapped. For example, to remove equity, a "Drawing" account may be created as a contra equity account as follows:
Equity.create(:name => "Drawing", contra => true)
At all times the balance of all accounts should conform to the Accounting Equation
Assets = Liabilties + Owner's Equity
Every account object has a has_many association of credit and debit transactions, which means that each account object also acts as its own Ledger, and exposes a method to calculate the balance of the account.
See the {Account} and {Transaction} classes for more information.
Let's assume we're accounting on an Accrual basis. We've just taken a customer's order for some widgets, which we've also billed him for. At this point we've actually added a liability to the company until we deliver the goods. To record this transaction we'd need two accounts.
>> Liability.create(:name => "Unearned Revenue")
>> Asset.create(:name => "Cash")
We'd then record the following transaction.
>> Transaction.create(:description => "Order placed for widgets",
:credit_account => Liability.find_by_name("Unearned Revenue"),
:debit_account => Asset.find_by_name("Cash"),
:amount => 1000)
Although Plutus does not provide a mechanism for generating invoices or orders, it is possible to associate any such commercial document with a given transaction.
Suppose we pull up our latest invoice in order to generate a transaction for plutus (we'll assume you already have an Invoice model):
>> invoice = Invoice.last
We'll also assume that we have not yet received payment for the order, so we'll need an "Accounts Receivable" Asset:
>> Asset.create(:name => "Accounts Receivable")
Next, we'll go ahead and create a transaction for this invoice:
>> Transaction.create(:description => "Order placed for widgets",
:credit_account => Liability.find_by_name("Unearned Revenue"),
:debit_account => Asset.find_by_name("Accounts Receivable"),
:amount => invoice.amount,
:commercial_document => invoice)
The commercial document attribute on the transaction is a polymorphic association allowing you to associate any record from your models with a transaction (i.e. Bills, Invoices, Receipts, Returns, etc.)
Each account can report on its own balance. This number should normally be positive. If the number is negative, you may have a problem.
>> cash = Asset.find_by_name("Cash")
>> cash.balance
=> #<BigDecimal:103259bb8,'0.2E4',4(12)>
Each subclass of accounts can report on the total balance of all the accounts of that type. This number should normally be positive. If the number is negative, you may have a problem.
>> Asset.balance
=> #<BigDecimal:103259bb8,'0.2E4',4(12)>
The Trial Balance for all accounts on the system can be found through the abstract Account class. This value should be 0 unless there is an error in the system.
>> Account.trial_balance
=> #<BigDecimal:1031c0d28,'0.0',4(12)>
For complex transaction, you should always ensure that you are balancing your accounts via the Accounting Equation.
Assets = Liabilties + Owner's Equity
For example, let's assume the owner of a business wants to withdraw cash. First we'll assume that we have an asset account for "Cash" which the funds will be drawn from. We'll then need an Equity account to record where the funds are going, however, in this case, we can't simply create a regular Equity account. The "Cash" account must be credited for the decrease in its balance since it's an Asset. Likewise, Equity accounts are typically credited when there is an increase in their balance. Equity is considered an owner's rights to Assets in the business. In this case however, we are not simply increasing the owners right's to assets within the business; we are actually removing capital from the business altogether. Hence both sides of our accounting equation will see a decrease. In order to accomplish this, we need to create a Contra-Equity account we'll call "Drawings". Since Equity accounts normally have credit balances, a Contra-Equity account will have a debit balance, which is what we need for our transaction.
>> Equity.create(:name => "Drawing", :contra => true)
>> Asset.create(:name => "Cash")
We would then create the following transaction:
>> Transaction.create(:description => "Owner withdrawing cash",
:credit_account => Asset.find_by_name("Cash"),
:debit_account => Equity.find_by_name("Drawing"),
:amount => 1000.00)
To make the example clearer, imagine instead that the owner decides to invest his money into the business in exchange for some type of equity security. In this case we might have the following accounts:
>> Equity.create(:name => "Common Stock")
>> Asset.create(:name => "Cash")
And out transaction would be:
>> Transaction.create(:description => "Owner investing cash",
:credit_account => Equity.find_by_name("Common Stock"),
:debit_account => Asset.find_by_name("Cash"),
:amount => 1000.00)
In this case, we've increase our cash Asset, and simultaneously increased the other side of our accounting equation in Equity, keeping everything balanced.
The Engine provides controllers and views for viewing Accounts and Transactions via the {AccountsController} and {TransactionsController} classes. The controllers will render HTML, XML and JSON, and are compatible with ActiveResource
Routing is NOT supplied by the engine. You can add routes to your application in your config/routes.rb with something like the following
resources :transactions, :only => [:index, :show], :conditions => { :method => :get }
resources :accounts, :only => [:index, :show], :conditions => { :method => :get }
NOTE: If you enable routing, you should ensure that your ApplicationController enforces its own authentication and authorization, which this controller will inherit.
Rspec tests are provided. Install both the rpsec and rspec-rails gems, and install this plugin into a working rails application to run the tests.
- Better views, including paging and ledgers
- Reference for common accounting transactions
For a complete reference on Accounting principles, we recommend the following textbook
Copyright (c) 2010 Michael Bulat