Troubleshoot Notazz invoice issues
Notazz problems often come from credentials, tax fields, product mapping, or connection status rather than checkout itself. Invoice failures can worry finance teams even when Sales shows an approved purchase.
Use this guide when invoices are missing, integration status is degraded, or tax output does not match expectations.
Common symptoms
| Symptom | Likely cause |
|---|---|
| Integration status degraded | Credentials or Notazz account issue |
| Invoice not generated | Product mapping or sale status |
| Wrong tax output | Service description, CNAE, or ISS fields |
| Test invoice works, live fails | Test mode or mapping mismatch |
| Invoice delayed after approved sale | Sale context or external processing delay |
| Only some products fail | Product-specific mapping problem |
What Notazz integration depends on
| Area | Why it matters |
|---|---|
| Notazz credentials | Wrong account or expired auth breaks all invoice generation |
| Test mode setting | Live sales may not generate production invoices when test mode is on |
| Tax and service fields | Brazilian tax fields must match the sold service |
| Product mappings | Sold product must map to the correct Notazz configuration |
| Sale status | Invoice timing depends on the expected approved state |
| Business workspace | Integration belongs to one business operation |
Investigation workflow
- Confirm the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the Notazz integration settings.
[Screenshot: Notazz settings page — connection status visible.]
- Confirm credentials belong to the correct Notazz account.
[Screenshot: Credentials verified — correct Notazz account connected.]
- Check whether test mode is enabled when you expect live invoices.
[Screenshot: Test mode setting — matches live vs test expectation.]
- Review service description, CNAE, ISS, and related tax fields.
[Screenshot: Tax fields — service description and CNAE reviewed.]
- Confirm product mappings match the sold product and current offer.
[Screenshot: Product mapping — sold product linked to correct Notazz config.]
- Open the sale that should have generated the invoice in Sales.
[Screenshot: Sale detail — approved sale for missing invoice.]
- Verify purchase status, buyer data, and product context.
[Screenshot: Sale context — buyer and product data complete for invoicing.]
- Fix configuration and run a controlled test purchase.
[Screenshot: Config fixed — test purchase triggers invoice attempt.]
- Recheck integration status and invoice output after the fix.
[Screenshot: Healthy status — invoice generated after configuration fix.]
Finance and support coordination
| Question | Where to answer it |
|---|---|
| Did the sale actually approve? | Sales |
| Is the product mapping still valid after a pricing change? | Plans and offers |
| Did finance expect tax fields for this service type? | Notazz settings and internal tax review |
| Is this a checkout issue or invoice issue? | Checkout success with missing invoice usually points to integration config |
What to verify after fixing configuration
| Check | Why it matters |
|---|---|
| Integration status is healthy | Confirms connection before more sales |
| Test and live modes match expectation | Prevents accidental test invoices |
| Product mapping covers every live offer | New offers often need mapping updates |
| Finance reviewed tax fields | Reduces repeated invoice rejection |
| Support knows invoices may lag sale approval | Sets stakeholder expectations |
Best practices
- Review tax fields with finance before production invoice generation.
- Update product mappings whenever offers or products change materially.
- Monitor connection status after pricing or catalog updates.
- Keep a test sale checklist for invoice validation during onboarding.
- Document which products require invoices and which do not.
Common mistakes
- Troubleshooting checkout before confirming sale approval.
- Leaving test mode enabled during live sales.
- Changing product names or offers without updating mappings.
- Assuming every approved sale should instantly show an invoice.
- Editing Notazz credentials in the wrong workspace.
FAQ
Where is the main Notazz setup guide?
Can a refund or cancellation affect invoice expectations?
Yes. Review refunds and the sale record before assuming an invoice should still be generated.
What if only one product fails invoicing?
Focus on that product's mapping and tax fields first rather than global credentials.
Should I use webhooks for invoice troubleshooting?
Webhooks may help downstream systems, but invoice generation problems usually start in Notazz settings and sale context.