Magento Moneybird Invoices Grid: Sync & Statuses
Looking for Magento Moneybird Integration: Book Invoices, Credit Memos and Customers Automatically? View the full Magento Moneybird Integration: Book Invoices, Credit Memos and Customers Automatically page to explore features, configuration options, and pricing.
This is the queue: every Magento invoice the Moneybird Integration has picked up, what happened to it, and what you can still do about it. It is also where you look first when something did not arrive — a failed row carries its own reason in a column, so you rarely need a log file. This page covers the columns the module adds, the actions per row, the mass actions, and what each sync status actually means.
Location: Accounting → Data → Invoices
How an invoice gets here
An invoice is queued the moment Magento creates it, provided Auto add invoices and creditmemos is on under Stores → Configuration → Accounting → General → Automation. It sits on Pending until the cron run sends it, every fifteen minutes by default.
Invoices created before you installed the module are not queued retroactively. Select them and use Moneybird: Add to Queue.
Columns added by this module
| Column | What it tells you |
|---|---|
| Moneybird Sync | The status of this row: Pending, Synced, Error, Failed or Skipped |
| Moneybird Sync Result | Why it is not Synced — the platform's own message, not a code |
| Moneybird ID | The id of the booking in Moneybird, once it exists |
All three filter and sort, so "everything that failed this week" is two clicks.
What the statuses mean
Pending — queued, not sent yet. The next cron run picks it up.
Synced — booked. Moneybird ID points at it.
Error — it went wrong for a reason that may pass: an outage, a timeout, a rate limit. The row keeps its remaining attempts and the next run tries again. After three attempts it becomes Failed.
Failed — parked. Repeating this changes nothing until somebody changes something: an unmapped contact, a ledger account Moneybird will not accept, an administration the token cannot reach. Fix the cause, then Sync the row.
Skipped — deliberately excluded. It stays out of every run until you add it back.
Actions per row
Moneybird: Sync (DryRun) — builds the exact body and shows it, without sending anything. The fastest way to check a mapping.
Moneybird: Sync — sends this one now, without waiting for cron.
Moneybird: Remove from Moneybird — deletes the booking on the platform. Available only for a synced row.
Moneybird: Remove from Queue — drops the row here. The booking in Moneybird stays.
Moneybird: Add to Queue — queues an invoice that was never picked up.
Moneybird: Skip from Queue — excludes it from every run.
Mass actions
The same set, applied to a selection: Sync, Remove from Queue, Remove synced from Queue, Add to Queue and Skip from Queue.
Remove synced from Queue is the one to be careful with. It removes rows the module knows are booked, and the bookings themselves stay in Moneybird — so the link between the two is gone, and a later Add to Queue on the same invoice books it a second time.
When a row will not sync
Read Moneybird Sync Result first: it holds what Moneybird said. The three that come up most:
"contact"-something — the customer never reached Moneybird as a contact. The contact is pushed with the invoice, so this usually means the push itself failed; the reason is in that same column.
"ledger_account_id is not valid" — the ledger account you chose is not a revenue account.
"No access to this administration" — the selected administration does not match the token, usually after reconnecting with another account.
Need More Help?
Documentation:
- All Help Articles - Complete documentation overview
Support:
- Contact Support - Get help from our team
For a complete overview of features and configuration options, see Magento Moneybird Integration: Book Invoices, Credit Memos and Customers Automatically.