Rizki Maulana

Please add an incoming document functionality to Recurring General Journal worksheet page, same as what already available in the General Journal.

So, the user can create Recurring Gen. Journal, attach the document and can see the file on incoming document on the General Ledger Entries, after the journal is posted.

Thank you.

Rizki

We know that in D365 Finance Operations, there is a function called "Ledger Settlement".

https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/ledger-settlements

is there any roadmap to build same function for Business Central? it will be nice to have and benefit to the end-user.

Thank you.

Rizki

There is a need for a partner or client to review all active workflow setup and details.

However, what we can do now is to open each workflow one by one.

Tried to create by using configuration package and vlookup in excel, but it's quite cumbersome.

It will be very helpful if there is a report or tools to extract the workflow setup details that contains following information:

• Workflow Code
• Workflow Description
• Enabled (TRUE/FALSE)
• Workflow Conditions (Text)
• Approver Type

> if the "Approver Type" is Workflow User Group, then show the workflow user group code and member information.

• Approver Limit Type

> if the "Approver Limit Type" is Specific Approver, then show the "Approver ID".

• Workflow user group code
• Workflow user group member
• Approver email address

Please let me know if there is a roadmap in the future and consider it for future development.

Thank you.

Rizki

BC Customer experienced an Outage on their Production environment, however we as partner and BC admin on client side didn't get any notification or any outage report.

it's very important to get early notification, and outage monitor which describe what happened, outage start date/time, outage end date/time, and solution.

With this information, we can also check and compare to the given SLA time for outages.

Thank you and please vote.

Hi Team,

in BC AU localization, there are 2 reports which does not have "Save Value" function on Request Page.

• Report ID 28025 "Income Statement"
• Report ID 28024 "Balance Sheet"

Please consider adding above function like the most of other standard reports.

Thank you.

Hi Team,

in case I have a Purchase Order but it's received and invoice partially, I think now we still need to do manual math to get the PO Outstanding amount.

By checking the total PO Amount and total invoices amount that has been posted.

it will be good, if in the PO factbox for example, we can see the Outstanding PO amount as a result of Total PO Amount - SUM(Total Invoiced amount).

Thank you.

Hi BC Team,

When a user creates a sales invoice and they are attaching some documents, the attachment date and time is recorded in the system.

However, when the sales invoice is posted, the attachment date and time in the Posted Invoice document for the same attachment record is replaced by Posting Date/Time.

it will be good, if the user has a reference of the original date/time on the Posted document.

it's also important for audit control, to understand the timing of document attachment.

Thank you for your support.

Hi Team,

Please consider enabling workflow for Vendor Bank Account as BC standard workflow.

Since Vendor Bank Account is quite sensitive data, it will be great if a user can send approval request after changing the information,

and the new information will be applied once it's approved.

Thank you.

Rizki

I think the logic for "Inventory" field is different between the Item Lookup and the Item List page for Non-Inventory items.

By rights, they should be equal, so that the system does not mislead the information.

It’s funny when a user creates the Purchase Order, then clicks the dropdown to see the Item Lookup page and finds the inventory there.

But, it is not showing any value in the Item List page.

Hi Team,

Please consider implementing a function that allows attachments to be carried forward from the source document to the final document and related ledger entries.

This enhancement would significantly improve traceability across transaction stages.

Ideally, the design could follow a similar approach to the 'Dimension Set ID' structure—where the attachment resides in a single table and is referenced across documents, rather than duplicating the file for each transaction.

This would help optimize database usage and maintain consistency.

For example:

1. PQ stage: user attach Doc. 1A & 1B > Make Order
2. PO stage: Doc. 1A & 1B auto populated, user add new attachment 2A > Post Receipt/ Create Warehouse Receipt (Get Source)
3. Posted Purchase Receipt: Doc. 1A, 1B, 2A auto populated. if possible, user can also add new attachment on the GR. user add document 3C
4. PI stage: user Get Receipt line, Doc 1A, 1B, 2A & 3C auto populated. User add new attachment 4B > Post Invoice
5. Posted Purchase Invoice: Doc. 1A, 1B, 2A, 3C and 4B auto populated. if possible, user can also add new attachment on the Posted Invoice. user add document 5B
6. Vendor Ledger Entry: the document attachment also carried forward to the ledger of invoice line.
7. Payment Journal: when user apply the payment line to the invoice, the user can navigate to the invoice and see all the attachment. (I think standard BC already covers point 7, with "Show Posted Document" function in the Apply Entries page)

Thank you.