Microsoft Dynamics 365 Business Central Self-Help Place

Need a quick P&L by department or customer group, but don't want to set up a Financial Report or ask a developer? You can build one yourself in a few minutes from General Ledger Entries using Analysis mode . Important: new versions only. Analysis mode is available in Business Central 2023 release wave 2 (version 23) and later. Adding columns from related tables (Step 3) needs version 26.2 or later. If you don't see the icons below, your version is too old. Step 1: Open Analysis mode Search for General Ledger Entries , then click the Enter analysis mode icon next to the search icon. What you can do here: Group, filter and total your G/L entries without leaving Business Central Pivot the data like an Excel pivot table Save several analysis tabs for different reports Note: Analysis mode only reads data. Nothing you do here changes your postings. Step 2: Add or remove columns In the Columns pane on the right, tick the fields you want to see and untick ...

Scenario: a journal batch has 3 possible approvers. As soon as any 1 of them approves, the batch is approved. As soon as any 1 rejects, the batch is rejected. Nobody has to wait for all 3. Tested on Business Central version [fill in]. Works for General, Sales, Purchase, Cash Receipt and Payment Journals. Which setup do you need? Your rule What to follow Scenario A: any 1 approver is enough Steps 1 to 5 below, exactly as written. This is the main guide. Scenario B: all approvers must approve Go to the Scenario B box near the end. It reuses Steps 1 to 4 with its own settings. Each workflow handles one scenario only . Do not mix the settings. Scenario A in one line: put the 3 approvers in a Workflow User Group with the same Sequence No., set Pending Approvals to 2, and add the response Approve the approval request for the record . Before you start Every approver must exist in Approval User Setup . Do not put the ...

In Business Central, the name on a ledger entry is the person who posted it, not the person who keyed in the document. This surprises many users, especially when they open Page Inspection and see two different names on the same entry. The same rule applies to general ledger, customer, vendor and other ledger entries. This post explains what the two system fields mean, why they can show different people, and how to find the original creator when you need it. What the two fields mean Every table in Business Central has system fields that record who inserted a record and who last changed it. You can see them in Page Inspection (Ctrl+Alt+F1) under Table Fields. Field What it records Does it change? SystemCreatedBy The user who inserted the record. For a ledger entry, this is the user who posted. Never SystemCreatedAt The date and time of posting Never SystemModifi...

Posting a payment or applying vendor entries in Business Central stops with this error: Debit Rounding Account is missing in Vendor Posting Group Code: XXXX. G/L Account No. must have a value in G/L Entry: Entry No.=NNNNN. It cannot be zero or empty. The fix Open Vendor Posting Groups and find the code named in the error. Fill in both Debit Rounding Account and Credit Rounding Account . Post again. Which account? A profit and loss account, such as your rounding differences account or your realized exchange gain/loss account. Use the same account for both fields. Do not use the payables account. Why it happens You partly paid a foreign currency entry, and rounding left a one-cent gap in local currency. Business Central needs an account to post that cent to. Example: invoice of USD 302.00 at rate 4.2345, part-paid with USD 101.00. Step Calculation MYR Invoice 302.00 × 4....

A user opens the Vendor Ledger Entries, sees the same Document No. and the same External Document No. posted twice, and the first reaction is: "Business Central has a bug. It allowed a duplicate posting!" I have been asked this question several times. The answer is always the same: the system did exactly what it was told to do. The journal line was posted without a Document Type . Short answer Business Central only checks for a duplicate Document No. and External Document No. when the journal line's Document Type is a transaction document such as Invoice or Credit Memo . When the Document Type is blank, the duplicate check is skipped. This is standard design, not a bug. What the user sees A purchase invoice was posted earlier. Later, someone keys in a general journal line against the same vendor, types the same Document No. and External Document No., leaves the Document Type empty, and posts. Business Central accepts it. Entry Document Type Docu...

Overview Use G/L Currency Revaluation when you need unrealized forex gain or loss on foreign-currency balances kept in G/L accounts. The Exchange Rate Adjustment never sees these, because it only revalues customer, vendor and bank account balances. In my earlier post, How to Calculate Unrealized Forex Gain/Loss with Exchange Rate Adjustment in Business Central , I showed how BC revalues open customer, vendor and bank documents. Typical balances that need G/L Currency Revaluation instead are: Intercompany amounts due to or from related companies , which usually sit in G/L accounts rather than customer or vendor accounts. Other foreign-currency balances in G/L accounts , such as loans or deposits recorded directly in the general ledger. G/L Currency Revaluation revalues the foreign-currency balance of a G/L account, and you choose whether the result goes to the realized or the unrealized gain and loss accounts. A note on bank accounts. From BC 2025 release wave 1 (April ...

If you have tried to post a sales credit memo or sales invoice and been stopped by the message below. It is one of the posting errors due to data issue on the document itself, not a system fault. There is no Cust. Ledger Entry within the filter. Filters: Customer No.: xxx, Document Type: Credit Memo / Invoice, Document No.: xxx, Open: Yes What Business Central is actually telling you When a sales document has Applies-to Doc. Type and Applies-to Doc. No. filled in, Business Central tries to apply the new entry against that existing customer ledger entry as part of posting. To do that, it searches Customer Ledger Entries using the filters shown in the error. If no entry matches every filter, posting stops. So if you are posting a credit memo and the error says Document Type: Credit Memo , your credit memo is set to apply against another credit memo. That is almost always a sign the application fields are wrong. Common causes The target entry is already closed. The i...