Stuart Hardman Director

When using Transfer Orders the Quantity to Ship and Quantity to Receive are automatically populated with the remaining Quantity. There is no option to prevent these values being auto filled.

For Sales & Purchases there are settings in the relevant setup that allow Default Quantity to Ship/Receive to be set to Blank or Remainder. The same option should be available on Inventory Setup for Transfer Orders.

When consuming Items against a Project/Job (via Inventory Picks or Job Journals) the generated Item Ledger Entry is recorded as a Negative Adjustment, from an audit perspective this give no easy visibility of what type of transaction has been posted. There should be a new Type on the Item Ledger Entry of Project Consumption (or Project Usage).

There should also be a new field on the General Posting Setup for Project Consumption/Usage to allow the value of the posting to go to a different G/L Account, currently it is posted the Inventory Adjustment account. For auditing purposes this causes concern because it is not an Inventory Adjustment it is a Project Cost.

The General Journal Batch allows you to specify Bal. Account Type and Bal. Account No. meaning these these fields are auto populated when lines are created. With the addition of several new account types to the journal (Employee, IC Partner & Allocation Accounts) it appears that the lookup hasn't been updated.

If you wanted to create a batch for expenses of a specific employee you are unable to set the Balancing Account No. on the General Journal Batch, meaning it has to be filled in manually on every line.

The new Copilot Suggest Sales Line functionality is useful when typing in text, however, it would be more useful if able to interpret files dropped into it.

OCR functionality might be too complicated but the ability to read a text file or a word document would greatly expand this functionality and remove the need for bespoke development in certain scenarios.

Item References can be added to sales & purchase documents allowing you to use alternate part numbers and pull through alternate descriptions. However, this functionality is not available on Project Planning Lines.

I suggest extending the functionality to include project planning lines so it is consistent throughout Business Central.

When Standard Purchase Codes are being created they can be used with General Ledger Account Codes and will default in Posting Groups (VAT Prod. Posting Group and Gen. Prod. Posting Group) from the G/L Account. You can specify Dimensions and Amounts Excl. VAT but there is no way to override the Posting Groups that default from the G/L Account. There are situations where for specific frequent purchases you might want to change the setup so it doesn't have to be changed manually every time.

For instance, you may have different types of subscriptions, some of which may be vatable and some which may not, rather than setting up two separate GL Accounts with different defaults or manually changing on every document it would be nice to be able to setup a Standard Purchase Code with a different VAT Prod. Posting Group.

When a Payment Method Code is set up with a Bal. Account No. specified an automatic payment is posted and matched to the invoiced value. This posted payment does not respect the Payment Terms of the invoice.

For instance, if a Vendor invoices and takes a payment via direct debit or standing order 7 days after the invoice date you should be able to create the invoice with Payment Terms of 7D and a Payment Method that has a Bal. Account specified. The payment that is posted should then be posted with a posting date 7 days after the Document Date.

A flag could be added to the Payment Methods saying "Respect Payment Terms" that is only editable if a Bal. Account No. is filled in.