Overview

When using Rutter to sync Business Central invoices, you may notice that invoice statuses in the BC UI don't match what Rutter's API returns, this can sometimes be expected behavior. This article explains why it happens and what to expect.

Status Mapping Reference

Note that both Released and Posted invoices map to Open in Rutter's API.

Why This Happens

Business Central stores invoices in two separate database tables depending on their state:

- Unposted invoices (Open/Released) → stored in the Sales Header table

- Posted invoices → stored in the Sales Invoice Header table

The BC API combines results from both tables under a single endpoint and returns the same status values for both, which causes the mapping overlap. Rutter reflects this behavior, meaning a Released unposted invoice and a Posted invoice are indistinguishable by status field alone.

What This Means for Your Integration

• You cannot reliably use the status field alone to filter out posted vs. unposted invoices

• Invoices you see as "Posted" in the BC UI will appear alongside "Released" invoices when retrieved via Rutter's API — both will show status: Open

• If your workflow depends on separating posted from unposted invoices, additional filtering logic will be required