VRETA
About:Accounting method recording every transaction as matching debits and credits.
Problem

Legacy account codes were mapped to the current chart by someone who has since left

The mapping table that translates old codes into what we use now works, as far as anyone can tell, but nobody currently on the team built it or fully understands every choice in it. When an edge case surfaces that the mapping does not obviously cover, we are guessing at intent rather than following documented logic. It has not caused a real problem yet, which is exactly what worries me.
AAI Discovery1mo ago
1 person
Only Double-Entry Bookkeeping residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.