Sage 200 UKI Ideas Portal
P/L transactions end up batched, even if the option is disabled - i.e. a result of a problem between POP and P/L invoicing
Users do not want to use batch processing but they do want to be able to post or delete transactions that end up in there - otherwise they cannot find the transactions and also can't e.g. generate suggested payments
| Idea Benefit | Current transactions cannot be cleared or posted as batch process is disabled |
| How do you solve for this problem today? | I set the Allow Batch Processing flag in SQL, post the transactions and then disable the option again - it is not practical to get all users to log of and change the flag in Sage |
| Product Variant | Sage 200 Professional |
I urge you to contact our customer services team to discuss this further. We have the concept of posted and pending transactions, pending is used by a number of processes. You mention in your notes that you solve for the problem by amending the flag in SQL. We do not recommend changes to SQL in this form and in fact its potentially quite dangerous. If you review the product terms its actually not permitted - clause 7.2.2 of part A. Based on this I will mark this as not an idea for now until this has been further evaluated.