Thank you so much.
Expand Post
bdo (Accounting Seed)
Hi Richa,
When creating a Payable for a Person Account, the lookup field that should be populated is not the Account field but instead the Contact field.
Thanks
Expand PostCraeted a Payable for a person Account . And the Payee field didn't populate.
Expand PostUnder "Please Note" above this doc says:
"After an account payable record has been paid, the system will not allow it to be un-posted. In order to un-post it, the associated cash disbursement must first be un-posted and deleted. This is a safety feature so that account payable amounts can't be edited after the record has been paid."
However, it seems like we used to be able to delete the APD record, leaving the Cash Disbursement and Payable intact, unpost the Payable to edit something, repost it and then reapply the Cash Disbursement. If that isn't possible, I would like to suggest that this capability be added. It would still be very safe, since all Cash Disbursements are ultimately reconciled to the bank statement.
Expand PostJust as a counterpoint, I worked with Oracle - where you couldn't change *anything* after it had been posted for a couple hours and the only way to fix anything was through a journal entry - so I really appreciate that - while sometimes arduous - it is *possible* to go back and fix stuff in the original transactions.
I tend to agree with Accounting Seed's current format which ensures that anything that affects/can change your financial reports is locked when the record is posted and the period is closed. Changing GL Accounts and GLAV Assignments will change your financial reports, and so it makes sense to me that there are a couple layers of security around changing these items once a record is posted and the period is closed.
That said, there are a couple things that could really help curb some frustration with the ability to go back and fix errors - because everyone makes errors.
- Projects & project tasks do not affect financials as they are not tracked in financial cubes, and I agree that it really would be nice to be able to edit those without unposting a record. But since they are written directly to the transaction record, I recognize the difficulty in implementing that change.
- It would be SO MUCH BETTER if you could unpost and fix data in a reconciled transaction as long as you don't change the amount. Having to unreconcile an item before fixing it is arduous (especially if you have to change many reconciled items at once) and prone to user error. It's too easy to forget to go back and re-reconcile, and if there are several records it can be challenging to know what has to be re-rec'ed.
- I think this is a work in progress & and has been somewhat addressed by recent releases - but the ability to fix a paid AP record without deleting the Cash Disbursement outright, can still be problematic.
- The ability to open and close multiple periods at a go instead of having to manually open/close each period manually after waiting for the previous period to open/close would be greatly appreciated - EDIT: OOOOH _ just saw this is a feature in the upcoming Daisy release! YAY!
Expand Post
jeanae.remala1.5641722734937903E12 (LionHeart Critical Power Specialists)
I would concur with Lloyd. The determination of what can be changed and by whom would work better for the users if this were determined through user permissions versus hard coded. I understand certain fields can not be changed, but Projects/Project Tasks, GL Variables, GL Accounts on Paybles, etc. sometimes need correcting due to data entry errors and it is difficult to do this in many cases in the Accounting Seed product.
Expand PostRyan - I understand the point about security in your May 24, 2017 post ("...this security is build in place so that users cannot easily change transactions") but each organization using Accounting Seed probably has slightly different needs for that kind of locking and it would be great if Accounting Seed would accommodate that variability.
For example, AS could enable a permission which would enable a super user to, perhaps, check a box, edit the values in a bunch of GLAVs, GL Accounts, Accounts, Projects and Project Tasks, then uncheck that box to prevent even that super user from editing those values. In our case, for example, we would like to reassign Project and Project Task to a lot of records, and will probably want to again as our thinking about the schema of our Projects and Project Tasks continues to evolve.
Expand PostHi Jeanae,
If you know how to create a custom report type, you can create a custom report type that pulls in ALL the good data from all of the related records using the edit layout feature, and then just use that as the basis for your GL reports instead of the standard transaction report type.
If you don't, I can point you in the right direction, or set one up for you depending on your level of comfort with the system.
I can be reached at rebeccaralls (at) gmail (dot) com.
Expand Post
Related Articles
Edit a Field Set 436Number of Views Accounting Seed Financial Analytics Frequently Asked Questions (FAQ) / Troubleshooting Guide 264Number of Views Receive Payments from Multiple Billings 569Number of Views Cash Out Features Overview 581Number of Views Cash In Features Overview 852Number of Views Introduction to Features Overview 889Number of Views Edit Standard Page Layouts Manually 685Number of Views Billing Field Descriptions 470Number of Views Receive Payment Directly from a Billing 747Number of Views PDF API Field Names 337Number of Views