Pages

Episode 486: Collaboration with Cloud Accounting (Part 1)

Indeed, there are some programmers who show "Allergic reaction" against "Finance and accounting terminology".

However, these are words which working adults should know. Even in the "Information Technology Engineers Examination", which certifies basic IT skills, these terms appear frequently.

Incidentally, there will be nothing wrong if you call them as "Left column, right column" in practice. Both of the column are merely a "breakdown table of assets". If you consist to describe concretely, it will be sufficient to consider that "Left column: Breakdown of cash and cash-like assets", "Right column: Breakdown of assets which must be paid (debt) and which are not needed to be paid."

So... How each of "Breakdown table of assets" (Balance sheet) will be transitioning, in a case that a Cloud service providing company

sold service provisioning for twelve months

agreed on April 1st, for 120,000 JPY

paid on May 30th

For example...

In April, it can be regarded as "increasing of asset for one month of service worth (10.000 JPY)" since they have already provided their service (not yet paid, though.) It is so-called "Selling on credit". (Account receivable) And it will keep on changing on and after May...

[Sales Reporting]

Eventually, the Increase and the decrease on each side will be as follows.

Obviously, only the "Right column: Debt and assets other than debt" is changing after June. "Unearned revenue" means payment in advance, and is treated as debt.

In the accounting department, these thirteen processings are managed creating thirteen sheets of "slip". (Not in paper, though.)

The workflow here is a mechanism that these slips will be generated automatically after the completion of "1. Sales Report" by a staff in Sales team. Slips have been generated already at the Step of "2. Bookkeeping" for accounting staffs.