Great meeting with both Eric and Steve. All three of us spent two hours going over a number of key points. Lots of drawings, running scenarios through financial flow calculators, and talking about options and needs.

- Math and logic for loyalty points
- Talks about costs of goods and when does this happen? Dealing with loyalty points?
- Some accountants are doing a bulk entry at the end of the year against cost of goods sold - we'd like to make ours more real-time
- Deferred revenue - lots of talks here - all kinds of deferred topics, deferred revenue, deferred COGS, deferred expenses, deferred liabilities, etc.
- New tax law changes
- Estimated redemption rates
- Things keep changing – laws, standards, needs
- We still offer user-maintained balance sheet item options
- Changing point redemption rates
- The value of a point? 
- We stamp points as is... (estimated value) – the value is determined when you want to redeem them
- Simple vs complex scenarios
- Booked value is at the current value level, if changed... what would that require? History and a physical entry that shows the value change
- If a change is made, we may need to create a dynamic entry to the transactions to show the change
- You don't want your values and actual cash values moving around
- We had some talks about not allowing manual changes
- If manual changes happen, what else do we need to clean-up?
- Cash vs accrual accounting – most companies really should be on the accrual accounting side
- So many companies track things on the side and then try to bring in and marry those things in the background. Super independent and separated systems and then trying to bring them back together.
- To overcome some of these separated systems and processes, many companies do lots of spreadsheets, sub accounts, and even paper and pencil.
- On balance sheet items, we would like a forth show amount option that ties out to the special accounts and the sub transactions.
- Lots of talks about ALE (assets, liabilities, and equity) and even allowing for information only or showing some phantom accounts - items play in but may not really show in the math or numbers - kinda like an information only account or a phantom account.
- There were some talks about adding in options to set a BSI to active (show), inactive (hide), or even phantom (show/info only).
- ACV – actual cash value
- Standalone declarations - these are things that happen that need to be recorded. The reason for the term standalone declaration deals with no background numbers or data. You are just stating a change or adjustment needs to be declared. There is more information in the developer's notebook on standalone declarations.
- Showing some greyed out fields and values -  smoke and mirrors
- Lots of talks about outside watchers, feeders, and triggers. Good stuff.

One of the other major topics was the law of deferring to something else that has more details. That could be a sub account, a one-to-many relationship with details, payments, line items, sub accounts, transactions, or other things that have sub dates, types, groupings, values, calculations, etc. Often, we defer to the item that has the best information and/or the best vantage point. That is part of what we are doing.