Microsoft Dynamics 365 Business Central Self-Help Place

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...

This is probably the question I get most from new Business Central users: "I forgot to print the Test Report before I posted my General Journal. Where can I reprint it?" Most finance teams print the Test Report and file it as their Journal Voucher . Usually nobody looks at it again — until the auditor picks a high-value adjustment and asks for the supporting voucher. You just need to print it from a different place: the G/L Register . Why You Can't Reprint the Test Report The Test Report only reads the lines that are still sitting in the journal , waiting to be posted. Once you click Post, Business Central moves those lines into the General Ledger and clears the journal. So after posting, there is nothing left for the Test Report to print. What Business Central does keep is a record of every posting run. Each time you post, BC creates one line in the G/L Registers page, with a running number, who posted it, when, and which journal batch it came from. That re...

In Business Central the purchase cycle produces three separate records. Together they are your three-way match . Purchase Order What we agreed to buy Posted Purchase Receipt What we actually received Posted Purchase Invoice What the vendor billed us Finance signs off on the invoice because the receipt proves the goods or service arrived, and the order proves the price was agreed beforehand. This post walks through one full cycle end to end, using a partial delivery, and finishes with the part everyone gets wrong — cancelling the small balance that will never arrive. The scenario We are buying a service — a purchase line of type G/L Account rather than a stocked item. This is very common for marketing, printing, subcontract labour and professional fees. Quantity 100 × RM 25.00 = RM 2,500.00 Delivery happens in stages: 80 first, then 15 , and the last 5 are cancelled by mutual agreement. Order 100 Receipt 1 80 Invoice 1 80...

This page is a running reference for the errors that come up most often in Microsoft Dynamics GP → Sales Transaction Entry ( Transactions >> Sales >> Sales Transaction Entry ). Each section lists the exact message you will see on screen, why GP raises it, and the steps to clear it. Find your message in the list below and jump straight to it. Jump to an issue One or more line items contain warnings or errors. / Distribution account(s) are missing or invalid The accounts receivable distribution(s) does not equal the actual amount Account is empty. Do you want to save changes with errors? Tax codes are not showing Issue 1 — One or more line items contain warnings or errors What you see One or more line items contain warnings or errors. On the edit list or when you click the warning icon beside the line, the detail reads: Distribution account(s) are missing or invalid. ERROR: Line accounts are missing or invalid. A small warning symbol appears again...