The issues that come up most often, the fastest paths to resolution, and the diagnostic steps to run before asking for help. Skim this when something seems broken — the answer is usually here.

Before you start: three quick checks #

1. Hard refresh the browser (Ctrl+Shift+R or Cmd+Shift+R). Roughly a third of “Bizuno is broken” reports resolve here.
2. Log out and back in. Refreshes your session and permissions cache.
3. Check the URL. Sometimes a menu link goes stale after an upgrade — typing the correct bizRt route in the address bar gets you back.

Login issues #

Forgot password #

Click Forgot password on the login screen. A reset email arrives within a minute. If it doesn’t, check spam, then verify your email address in Admin → Users (or ask your admin). SMTP misconfigurations are the usual culprit when password resets don’t send.

Locked out after failed attempts #

Bizuno’s default lockout is after 5 failed attempts. Wait 15 minutes, or have an admin unlock you (Admin → Users → user → Unlock).

2FA device lost #

An admin can reset your 2FA enrollment from your user record. Plan ahead: save recovery codes when you first enable 2FA.

Sales & invoicing issues #

Invoice won’t save — “Customer required” or similar #

A required field is missing. The field name is in the error message; the field usually has a red outline. Common culprits: blank customer, blank line SKU, zero-quantity line.

Inventory won’t deduct when I invoice #

Three possibilities:

• Item type is Non-Stock or Service — these don’t affect inventory by design.
• Item quantity on hand is already zero and the system is configured to block negative stock.
• Invoice is saved as Draft, not Posted. Draft invoices don’t move inventory.

Tax isn’t calculating on an invoice #

Check, in order:

1. Customer’s tax group — is one assigned?
2. Customer isn’t flagged Tax Exempt.
3. Item tax class isn’t Non-Taxable.
4. Ship-to address (for destination-based tax) is complete.

Invoice total is wrong #

Usually a rounding or tax-group mismatch. Compare line items + freight + tax to the total; the discrepancy usually sits at the tax line. Resolve by re-picking the tax group.

Banking issues #

Reconciliation won’t balance #

Systematic checklist:

1. Verify starting balance matches last month’s ending balance.
2. Every statement line is ticked exactly once.
3. Bank fees and interest posted before closing.
4. No duplicate receipts or payments.
5. Check the deposit total — does a $273.50 deposit on your books show as $275.30 on the statement?

Undeposited Funds keeps growing #

Receipts are being logged but not deposited. Run Banking → Deposits, bundle the open receipts, post the deposit. Aim for zero Undeposited Funds at end of week.

Check printed with wrong MICR / wrong check number #

The check numbering restart happens at the bank account level. Admin → Settings → Banking → the account → Next Check Number. Fix there; re-print the check.

Inventory issues #

On-hand quantity doesn’t match physical count #

Common causes:

• Shrinkage (theft, loss, damage) not adjusted.
• Receipts logged against the wrong SKU.
• Sales entered as a different SKU (lookup picked the wrong item).
• Assemblies built or un-built without updating component quantities.

Fix: Inventory → Adjustments → post a variance entry after a physical count. Resist the urge to “just fix it in SQL” — adjustments leave an audit trail.

Item search doesn’t find a known item #

The item may be marked Inactive. The default filter on the Items list hides Inactive; change the filter to show all.

Assembly build fails with “insufficient component quantity” #

A component SKU is below the required quantity. The error message names the component. Receive or transfer in, or reduce the build quantity.

General Ledger / period issues #

Trial Balance doesn’t equal zero #

Rare in practice because Bizuno only posts balanced entries. Causes:

• A transaction was directly edited in the database.
• A migration or import went wrong.
• A period was half-closed during a crash.

Fix: run the GL Detail report for a short date range and track the imbalance to a specific day, then to a specific record. Back up first.

Period is closed but I need to post to it #

• Best: post in the current period with a clear description referencing the intended prior period.
• If really needed and the return/statements haven’t gone out: Admin → Fiscal Periods → Reopen. Re-close after posting.

Year-end close failed halfway #

Restore from the pre-close backup. That’s exactly why you took it. Then resolve the underlying issue (out-of-balance account, unposted adjusting entry) and re-run close.

Email / document issues #

Invoice email not sending #

1. Admin → Settings → Email — confirm SMTP credentials, test from the settings screen.
2. Send yourself a test from the Email Templates screen.
3. Check your mail provider’s outbound limit — Bizuno hitting Google Workspace’s rate cap is a common trip-up during a monthly statement run.

PDF render is blank or garbled #

A PhreeForm template edit probably went wrong. Revert to a known-good version, or regenerate from the shipped template.

Logo prints wrong size on forms #

Re-upload at 600–1200 px wide, PNG or SVG. Very small logos upscale pixelated; very large ones may be sized oddly by the template.

Performance issues #

Bizuno is slow #

• Browser cache: hard refresh (Ctrl+Shift+R).
• Server load: ask your host to check CPU/RAM/disk.
• Database size: large attachments can bloat DB; Admin Dashboard shows DB size over time.
• Many concurrent users on a small instance: upgrade hosting or schedule heavy jobs overnight.

Reports time out #

• Narrow the date range.
• Filter by customer, category, or account.
• Export to CSV instead of in-browser HTML for very large results.

Integration issues #

Shopify / Woo sync stopped #

Integration status on Admin → Integrations goes red. Most common causes:

• API credentials expired — regenerate from the third-party dashboard and re-enter.
• Webhook URL changed — update in the third-party dashboard.
• Rate limit exceeded — spread your syncs or upgrade the third-party plan.

Payment gateway decline / error #

• Wrong API mode (test vs. live).
• Card processor declined for real reasons (insufficient funds, AVS mismatch) — show decline reason to customer, re-run.
• Webhook not reaching Bizuno — check firewall / URL / SSL cert.

Data diagnostic tools #

Audit log #

Admin → Audit Log. Filter by user, date, action. Finds who changed what and when.

Record history #

Most records have a “History” tab or panel showing edits. Diff two versions to see the exact change.

General Ledger detail #

Single best diagnostic for any “my numbers look off” question: GL Detail on the affected account for the date range in question.Important: Before any attempt to “fix” data — adjustments, voids, or direct-database operations — run a backup (Tools → Export & Backup). Two minutes of prep avoids the rare but painful “the fix broke something else” outcome.

When to ask for help #

• Bizuno stops responding entirely — host / admin.
• Login works but specific screens error out — grab the URL and error text; file a support issue.
• Your numbers look wrong but no obvious cause — stop editing, back up, ask your CPA or a Bizuno consultant to diagnose.
• A module or extension has a bug — file an issue on the Bizuno community site or GitHub.

Tips for Ridgeline Cycles #

• When you hit an odd issue, write down the exact steps that reproduced it and the URL. That note is 80% of a good support ticket.
• Screenshot the error message, including the full URL — don’t crop.
• Don’t try three fixes before asking. Try one, observe, document, ask. Cascading half-fixes turn diagnosable problems into mysteries.

Where to go next #

• Glossary — term definitions.
• URL & Journal Reference — deep-link for diagnostics.
• Getting Help & Community — where to file an issue.