Nothing is more exasperating when doing the month-end close than to find that your Trial Balance (TB) does not reconcile to your subledgers. You have done your Trial Balance on your Microsoft Dynamics 365 Business Central system, and you review your AP or AR subledger summary, only to see a variance. This is something that gives an accountant or controller sleepless nights. When your general ledger (G/L) and your subledgers get out of alignment. This is usually caused by certain system setups, timing issues, or user processes in the Business Central system itself. Understanding what the root cause is will enable you to fix it. Here is why your Business Central Trial Balance does not reconcile with your subledgers, and how to fix it. 1. Direct Posting to G/L Control Accounts What happens most of the time to create a TB/subledger discrepancy? The answer lies in the practice of direct posting to G/L control accounts. In Business Central, control accounts are the G/L accounts that represent your AP, AR, or Inventory subledgers. These accounts are supposed to be posted only by the system after you have posted an invoice against a vendor/customer/transaction in your inventory. Yet, when the users can post their manual General Journal directly to these G/L control accounts, the balance in the account changes while the balance in the subledger remains the same. Solution: Check the “Direct Posting” option on your Chart of Accounts for all AP, AR, and Inventory control accounts. 2. Unposted Journals and Approval Workflows Time-related issues also contribute greatly to difficulties in reconciliation. Unposted General Journals or Sales/Purchase Journals left in the user queue or awaiting their approval can lead to your sub-ledger having transactions that have not yet been recorded in the General Ledger. For example, when a vendor invoice is entered and released in the Purchase Invoices window, it might not appear on the Trial Balance since it is not posted yet. On the other hand, when you post a General Journal to the General Ledger, but the posting for sub-ledger is wrong, you will find the difference. Solution: Prior to generating a Trial Balance at the end of the month, make sure to post all batches and there are no pending approval workflows. Make use of User Setup to enforce mandatory closing dates to prevent backdated transactions in the closed period. 3. The Inventory Costing Lag When your AP/AR ledger matches precisely, but not your Inventory sub-ledger with the GL ledger, then chances are very high that the problem is due to cost postings. In Business Central, inventory costing occurs on-the-fly. When receiving or delivering inventory, a business system makes use of “Expected Cost,” which goes into an intermediate G/L account. Once you have posted an invoice, Business Central will need to make cost adjustments. If “Adjust Cost – Item Entries” job is not run, and “Automatic Cost Posting” is disabled in your Inventory Setup, then the cost adjustments will get stuck in your sub-ledger and never be posted to your GL ledger. How to fix this problem? Go to Inventory Setup and set “Automatic Cost Posting” and “Automatic Cost Adjustment” to “Always.” Furthermore, you should schedule Adjust Cost – Item Entries job to run automatically in the Job Queue. 4. Discrepancies with Reconciliation of Bank Accounts In some cases, the discrepancy might be in Bank Accounts sub-ledger. In such cases, users have reconciled their bank accounts outside the Bank Account Reconciliation module or have posted fees and interest on their bank account straight to G/L without reflecting those transactions on the Bank Account ledger. Fix: Always post bank fees, interest, and other clearing accounts via the native Bank Account Reconciliation journals of Business Central application. This will ensure that both G/L and bank sub-ledger get updated at the same time. Conclusion If your Business Central Trial Balance doesn’t tie out with your subledgers. This usually is not because of a glitch in the software itself but rather a result of the way you manage it. By preventing postings to your control accounts. Posting within specific timeslots and automatically adjusting your inventories, you’ll make sure that your G/L and subledgers always match up.
When managing inventories in the Microsoft Dynamics 365 Business Central, you must have come across “Item Tracking” and “Reservation.” As a beginner, they may appear to be two similar concepts, since they both relate to having the right item reach its destination at the right time. Treating them as one may result in inflexible procedures, delays in fulfilling the order or compliance issues. So, what is the difference? It is simple; Item Tracking is about identifying while Reservation is about allocating. Now let us understand their operations and what could happen when you get them mixed up. What Is Item Tracking? In Dynamics 365 Business Central, the concept of item tracking is what enables your organization to assign an individual identity to its inventory. Item Tracking works with Serial Numbers (individually assigned per item) and Lot Numbers (per batch) to enable tracking of the real-life history of a product. Essentially, think about Item Tracking as the “passport” of your item. Should your organization sell medical equipment, electronic goods, or perishable foods, it needs to know for sure which item went to which customer. Should a product recall take place, you must identify the item instantly. However, it should be noted that Item Tracking itself does not mean assignment of a specific item to a specific customer. The key point is that it enables you to track all the history of an item when it left your warehouse, how long it stayed there, expiration date, or warranty start date. Without item tracking, your computer is just a computer. With item tracking, you know its serial number and, thus, owner. What is Reservation? Reservation, on the contrary, is a rigid connection between supply and demand. It is a commitment. Once you generate a Sales Order and make a reservation for an inventory, you are telling Business Central, “Reserve 50 units of Item A exclusively for this customer.” Reservation is a strong allocation technique to cater to VIP customers or to satisfy any production order. It ensures availability during the picking phase, irrespective of all other incoming orders in the warehouse. You can make reservations for available inventories as well as for expected supply such as Purchase Orders. In case your key client demands a huge quantity of products for the next month, making a reservation will ensure that regular walk-in customers do not reduce that inventory. Working Together Now here comes the fun part: Item Tracking and Reservation do not exclude each other. Quite often, the two go hand in hand. You can reserve a particular tracked item. If, for example, you need to deliver “Lot B” of a certain pharmaceutical product owing to its unique expiration date, then Item Tracking will help to find Lot B and Reservation to reserve it from any other order. But if you employ Item Tracking without Reservation, the system will allocate your lot to another customer who completes the transaction faster. It is one of the frequent mistakes made by people, who confuse Item Tracking with Reserving. An item, although being tracked, does not have to be reserved, otherwise some other order will be able to take it. On the other hand, you may want to reserve any untracked items just for the sake of ensuring their availability, not specifying which one exactly. Conclusion Proper use of each function is essential in having an effective supply chain. Apply Item Tracking when there is a need for compliance, traceability, and warranty management. Apply Reservation when there is a need to ensure that there are enough for certain requirements, prioritize priority customers, and secure inventory for a production batch. Avoid reserving all your stock because it will restrict your ability to manage other clients’ orders. Similarly, avoid applying item tracking on simple and low-value inventory that only requires additional data entry. Remember that Item Tracking is the “what” and Reservation is the “who.”
Has it ever happened to you that you have been sitting in front of your Microsoft Dynamics 365 Business Central screen, scratching your head? Your Item Ledger Entries are showing precisely 500 units of an item. Your physical inventory count is 100% accurate too. However, when you generate your financial report or even access your Power BI dashboards, your inventory is entirely wrong. You fee the system is lying. How is it possible that your inventory is spot on while your reports are just completely wrong? It’s an irritating situation, but it happens quite frequently. What normally messes up is not the physical inventory but the process of costing, timing, and data relationships in Business Central. Here is the list of the most common mistakes. “Adjust Cost – Item Entries” Batch Job Initially, Business Central does not immediately account for the financial valuation of items when they are either received or shipped. Based on your cost flow method be it FIFO, LIFO, Average, or Standard. BC calculated the actual cost of goods sold asynchronously. If the “Adjust Cost – Item Entries” batch job doesn’t complete, there will be discrepancies between your Value Entries, which system uses for financial reporting purposes. And also your Item Ledger Entries, which record the physical quantities. When using Average costing, clear the difference by using the “Adjust Cost – Item Entries” batch job. Item Ledger Entries versus Value Entries In addition, it is imperative that one can distinguish between Item Ledger Entries and Value Entries. While the former captures the physical movement of materials that is, the quantity moving in and out and the later captures the financial implication of such moves that is, the dollars entered the General Ledger. While examining the Item Card, one sees entries that have been dictated by the Item Ledger Entries. The financial statements, such as Trial Balance, and Inventory Valuation reports, however, depend entirely on Value Entries. When there is any difference, it normally means that while an Item Ledger Entry has been made, the related Value Entry was either blocked, incorrectly set up, or delayed because of costing issues. Date of posting as opposed to date of documentation is yet another reason for reporting confusion. As you receive or ship goods, you assign a posting date to these transactions. If you receive or ship the inventory on the last day of the month but receive the document five days after the month ends, BC accounts for this difference through “Expected Cost Posting.” While the actual inventory updates instantly, its value goes into an intermediate account in your accounting system. If you generate a report with a certain date filter, the posting of the transaction may fall outside the report range. Dimensions Missing Lastly, there may be incorrect report generation due to missing dimensions. This happens because of dimensions for segmenting the financial information for department/project reporting. If any item comes in without the correct global dimension value, the inventory value will exist in BC but not appear correctly in the dimensional report. The problem with dimensions is that there is correct global inventory but dimensionally it is incorrect. Make sure that default dimensions are set up properly on item cards and vendor cards to avoid incorrect data. Summary In conclusion, having correct physical inventory in Business Central does not mean that your financial report generation is correct. The discrepancy between physical inventory and accounting can be caused by costing batch jobs, the difference between ledger and value entries, correct date control and perfect dimension setup. If your report is wrong, do not recount the inventory. Instead, check the status of Adjust Cost batch job, value entries for missing amounts, dates used to produce the report and dimension setup.
Imagine this: You have just received an enormous update on your company’s vendor’s spreadsheet. It comes with hundreds of new codes, descriptions, and changing prices. Now, somebody needs to go through all of that information, check which items your company already has, change prices, and make sure that all these items are available for purchase. If the described scenario seems familiar to you, then you know the problem of vendor catalogue chaos first-hand. In Microsoft Dynamics 365 Business Central, however, managing such influxes of data from vendors doesn’t have to be such a pain. This is how to manage vendor catalogues in Business Central. The Core Problem: Different References The core problem in the realm of managing vendor catalogues is that of translation. Your Internal Item Card might have the name “Steel Hex Bolt M10x20” with a proprietary SKU (e.g., SHB-1020), with pieces being tracked in your system. The vendor, on the other hand, might have his own name for it: “HB10X20SS,” and his own part number, and he might sell it in boxes of 100. This language barrier is bridged by Business Central, without the need to change your internal nomenclature. Managing Item Cross References In terms of vendor catalogue management in Business Central, the absolute MVP is the Item Cross Reference table. In this feature, you may link a specific vendor’s part number to your internal Item Card. When your purchasing agent creates a Purchase Order, he does not have to remember your SKU, instead, he types the vendor’s part number in the “Cross Reference No.” field of the purchase order line. Business Central finds the internal item, inserts the proper vendor item number in the purchase order. Even puts the vendor’s unit of measure on the purchase order line. Simplifying Bulk Updating Using Excel If the vendor is giving you a full updated catalogue containing new price rates or part numbers. Then it’s not necessary that you should be entering these one-by-one. Business Central enables you to export your “Item Vendor” information (that contains specific part numbers, lead times, and prices of the items from vendors) in Excel. You can make use of Excel to match the vendor’s updated information with your existing data in just a few clicks. After that, again upload the updated Excel file to Business Central through configuration packages or Excel integration tool. Working With Non-Stock Items In some cases, vendor catalogue may include items that are not included in your usual stock of goods. Such parts are specifically ordered from vendors in response to requests from customers. Business Central solves the problem efficiently with “Non-Stock Items”. A Non-Stock Item catalogue may be created, which works as a virtual database of all the things that you can purchase, but do not stock in your warehouse. In case a customer requires one of those. Business Central offers an option to convert Non-Stock Item to a regular Item Card right away, with automatically included vendor catalogue number and price. Catalogue Management Best Practices Establish Data Governance: Define how you would like to receive vendor data. The more compatible with your Excel template is their spreadsheet, the less time will be required to perform import. Keep Cross References Neat: Do not save old and obsolete vendor part numbers in your cross-reference table. Archive them to speed up your searching capabilities. Item Attributes Use: Assign item (vendor catalogue) attributes such as “Material” or “Colour” to enable your purchasing department to find vendor item using specifications and not part numbers. Conclusion Vendor catalogue management in Business Central is all about bridging the gap between how your vendors categorize their goods and how you categorize them within your company. With proper use of Item Cross References, bulk updates using Excel files, and non-stock items. You take out all friction associated with your purchases. You end up with a shorter PO process, reduced receiving mistakes, and procurement people who spend more time procuring than keying in data.
Let’s take the case of your biggest client placing an order for buying 10,000 units of your product for a period of one year from now. But they do not want you to deliver 10,000 units at once but monthly in shipments of 830 units each. Preparing a dozen separate sales orders now will mess up your systems and forecasting as well. That is why Blanket Sales Orders of Microsoft Dynamics 365 Business Central can become your saviour. The Blanket Sales Order is neither a shipping document nor a financial transaction. On the other hand, it is an agreement that includes the negotiated price and quantity to be shipped in parts according to schedule. Look at how to handle Blanket Sales Orders in Business Central. The Advantages of Using Blanket Orders Before getting into the “how,” we first need to know the “why.” There are three reasons why using blanket orders makes sense: Price Security: This ensures that the negotiated price will be protected for the customer from any changes in price in the future. Forecasting: The quantities in a blanket order are known to the planning engine, giving you a forecast of what’s to come without making an inventory commitment at the present. Efficiency: It saves you the trouble of having to enter all that customer information, item numbers, and negotiated prices every time a partial shipment is made. How It Works in Business Central In the Business Central solution, blanket orders are managed using the following straightforward two-tier structure: Blanket Sales Order (agreement) and Standard Sales Order (implementation). While creating the standard sales order based on blanket order, Business Central will automatically calculate the remaining quantity of blanket order. Moreover, it reserves the quantity of “Blanket Order Quantity” on the item card for your supply chain. Workflow 1. Creating Blanket Sales Order Create a new Blanket Sales Order and provide the customer, delivery date(s), and line items. Enter the total agreed upon quantity on the lines. 2. Releasing the Order Like regular orders, you need to change the status of the Blanket Sales Order to Released from Open. It indicates that the order is now official and ready for a partial fulfilment. 3. Making the Order In case you want to deliver some part of the product, Make Order from already available blanket order with the quantity specification of the product that needs to be shipped. This way system automatically creates a regular Sales Order that will have all the necessary information about customer, item, and prices filled. Next, you just need to process this order normally. Best Practices for Success Keep Your Statuses Clear: Do not keep any active agreements in the “Open” status when they have blanket orders. Always release them so that the planning engine can recognize the demand. Use the Order Tracking Window: If you get notified by a customer that they want an increase in their monthly delivery of products, you can use the Order Tracking window in Business Central to identify the exact quantity allocated to blanket orders or other sale orders. Close Them out: After the final delivery the “Quantity to Receive” becomes zero, close the blanket order. Having old, completed blanket orders on your platform will make your sales pipeline cluttered. Make Use of Archiving: In case you need to see the original agreement details after several months, but you do not need them on your active list, take advantage of archiving functionality in Business Central instead of simply deleting them. Conclusion Handling long-term contracts does not necessarily mean trading off on day-to-day efficiency. Thanks to Blanket Sales Orders in Business Central, you will easily be able to separate the deal from its implementation. Not only does it keep your process from becoming inefficient, but it is also what will help the rest of your team in forecasting demands. Do you use blanket orders to their full extent in your existing ERP system? If your system obliges you to manually manage partial deliveries, then maybe it’s time to consider Business Central as your sales solution.