web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Posting a credit memo in demo data (cannot find vendor ledger entry 0)

(6) ShareShare
ReportReport
Posted on by 385
Hey Everyone:
 
Maybe it's just me having a continued Monday, but I'm having an issue in the DEMO DATA for Business Central (CRONUS USA, Inc.).  Every time that I try to post or preview-post a credit memo, I get the error:
 
"Problem: cannot find vendor ledger entry 0"
 
I've tried applying the document to existing documents; I've tried completely removing the apply records; I've tried generating a credit memo directly from the invoice; I've tried following tutorials online.  I've tried dang near everything that I know of to get this to post, but I seem incapable of it.  I've tried looking up this error - nothing that I could see.  I've tried troubleshooting with ChatGPT - it says it should post.
 
What am I doing wrong?
 
Thanks.
-J
 
I have the same question (0)
  • Suggested answer
    Ramesh Kumar Profile Picture
    7,555 Super User 2026 Season 1 on at
  • Verified answer
    Jeffrey Bulanadi Profile Picture
    9,121 Super User 2026 Season 1 on at

    Hi James,

    That error “cannot find vendor ledger entry 0” is sneaky — but it’s often related to how demo environments handle document applications and ledger integrity.

    Here’s how to break it down:

    Core Cause

    Vendor Ledger Entry ID 0 doesn’t exist — and BC doesn’t allow posting against non-existent entries. This usually stems from:

    • A credit memo attempting to apply or reference a cleared or deleted vendor ledger entry
    • Leftover apply records in the buffer that reference VendorLedgerEntry.ID = 0 (typically during copy-paste workflows or rapid testing)
    • Corrupted demo data or unfinished invoice posting logic

    What to Check

    • Remove Application References: Go to the credit memo, and ensure the Applies-to Doc. No. and application lines are completely removed. You may need to use Unapply or remove entries from Applies-to ID manually in the line table.
    • Review Vendor Ledger Entries: Navigate to the vendor → Ledger Entries. Ensure there’s at least one open entry for the credit memo to apply to, or post the credit memo as standalone (no application).
    • Validate Demo Data Integrity: In demo databases like CRONUS, background jobs may simulate application data. Restarting the web client or refreshing the database can fix ghost references.
    • Try Standalone Post: If it still fails, strip all application fields and post the credit memo as-is. This bypasses matching and avoids the system searching for entry ID 0.

    Advanced Tweak (for Developers)

    If you’re working in a sandbox with AL:
     

    al
    
    VendLedgEntry.SETRANGE("Entry No.", 0);
    IF VendLedgEntry.FINDSET THEN
      MESSAGE('Entry 0 exists — unexpected') // Rare
    ELSE
      MESSAGE('No entry 0 — as expected'); // Confirms issue

     

     

    If you consistently hit this in demo environments, you’re likely working with outdated or staged data. Consider resetting the CRONUS database or switching to a fresh company.

    Helpful References:
    Vendor Ledger Entries – Microsoft Learn
    Posting Credit Memos – Community Thread
    Troubleshooting Ghost Applications – Twitter Thread


    If this helps, feel free to mark this as verified or echo it for others facing the same ghost entry issue.

    Cheers
    Jeffrey

  • Suggested answer
    Sohail Ahmed Profile Picture
    11,175 Super User 2026 Season 1 on at
    Hi James,
     
    That error — "cannot find vendor ledger entry 0" — usually means that Business Central is trying to apply the credit memo to a vendor ledger entry, but no valid entry (or an invalid reference like ID 0) is selected.
     
    Here’s how to resolve it:
     
    ✅ Quick Fix:
     
    1. Open the Credit Memo you're working on.
     
     
    2. Go to "Applies-to Doc. No." field on the lines (or under "Apply Entries").
     
     
    3. Clear any applied entries manually if present, and re-select the correct vendor invoice.
     
     
    4. If you’re not intending to apply it, make sure it’s set to "Open" with no apply-to ID.
     
     
     
    Also, check:
     
    The vendor exists and has valid open entries.
     
    The credit memo type is correct (vendor or purchase).
     
    If created from the invoice directly, ensure nothing was changed in the apply fields afterward.
     
     
    Sometimes demo data has corrupted entries — so testing with a fresh vendor/invoice might help.
     
    ✅ Mark this answer as verified if it helps you.
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,002 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,255 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,217

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans