>I wouldn't try to separate bookkeeping from accounting too much.
I think of them as distinct and separate concepts:
bookkeeping: the recordkeeping of transactions. The "data entry". You can have lower wage data entry clerks tearing open envelopes to type in data from vendors' invoices and recording deposits of checks from customers. At this layer, the data needs to be recorded correctly.
accounting: literally the management of "accounts". This is a position of education (CPAs). Their value-added thinking happens above the layer of bookkeeping. They use professional judgement to set up a "chart of accounts" ... what kind of buckets to keep track of various money, how many buckets, etc. They are in charge of "closing the books" each month and preparing financial reports.
Yes, sometimes the activities blend into each other. Some bookkeepers do higher level "accounting" activities and some Certified Public Accountants also do grunt work of "bookkeeping" but they're still separate cognitive activities.
Lastly, there's finance. The finance layer sits above accounting and bookkeeping. Finance management (CFO, treasurer, etc) focuses on strategy of money. Should the company lease or buy the building, the tax implications of foreign earnings, stock buybacks, etc. The accountants & bookkeepers can report exactly how much money is sitting in the bank but they are not the ones who decide what the best strategy is for it.
It's the small businesses where "bookkeeping" and "accounting" are synonymous (e.g. using Intuit QuickBooks). In those mom & pop shops, the "finance" strategy is handled by the owner(s) of the company.
From your description, it sounds like bookkeeper:accountant as DB-user:DB-admin - the accountant/admin defines the schema, and the bookkeeper/user only gets to work at the data level, with no metadata level decisions. Is this analogy sound?
I believe this is a good analysis if you see the DB administrator in the role of scheme and report design, interpreting reports, and using those reports to plan for the future, and the DB user as inserting new rows (never updating!) and doing simple queries on the data.
I think of them as distinct and separate concepts:
bookkeeping: the recordkeeping of transactions. The "data entry". You can have lower wage data entry clerks tearing open envelopes to type in data from vendors' invoices and recording deposits of checks from customers. At this layer, the data needs to be recorded correctly.
accounting: literally the management of "accounts". This is a position of education (CPAs). Their value-added thinking happens above the layer of bookkeeping. They use professional judgement to set up a "chart of accounts" ... what kind of buckets to keep track of various money, how many buckets, etc. They are in charge of "closing the books" each month and preparing financial reports.
Yes, sometimes the activities blend into each other. Some bookkeepers do higher level "accounting" activities and some Certified Public Accountants also do grunt work of "bookkeeping" but they're still separate cognitive activities.
Lastly, there's finance. The finance layer sits above accounting and bookkeeping. Finance management (CFO, treasurer, etc) focuses on strategy of money. Should the company lease or buy the building, the tax implications of foreign earnings, stock buybacks, etc. The accountants & bookkeepers can report exactly how much money is sitting in the bank but they are not the ones who decide what the best strategy is for it.
It's the small businesses where "bookkeeping" and "accounting" are synonymous (e.g. using Intuit QuickBooks). In those mom & pop shops, the "finance" strategy is handled by the owner(s) of the company.