Module guide
Workflow
Reports
Integrations & Sync Hub Guide
Use Integrations to understand sync logs, retries, mappings, API keys, webhooks, QBO checks, reconciliation, and escalation guidance.
Integrations connect AWRA with external tools such as accounting systems, communication providers, payment services, or other business systems. Integrations should be monitored because a record may be correct in AWRA but waiting, failed, skipped, or blocked during sync.
Integration Concepts
| Concept | Meaning For Users |
|---|---|
| Connector | The connection between AWRA and another system. |
| Mapping | How AWRA fields match external fields such as accounts, taxes, customers, items, or payment methods. |
| Sync run | One attempt to send or receive records. |
| Sync log | Status and message that explains whether a sync succeeded, failed, skipped, or needs retry. |
| Webhook | A system message sent when another service notifies AWRA about an event. |
| API key | A credential used by authorized systems; it should be handled carefully by admins or technical contacts. |
Sync Troubleshooting Workflow
- Open the record and confirm it is complete, approved, posted, or ready for sync.
- Check the sync log for status, timestamp, message, and retry count.
- Confirm required mappings such as customer, item, account, tax, payment method, or warehouse.
- Fix missing fields or ask an authorized admin to update mapping.
- Retry sync only when the cause is fixed.
- Compare AWRA and the external system after sync succeeds.
QBO Checks
- Confirm QBO connection is active before assuming invoices or payments will appear.
- Check whether customer, item, tax, account, and payment mappings exist.
- Confirm source records are approved, posted, or otherwise ready to sync.
- Review sync logs before creating duplicate records manually in QBO.
- Reconcile AWRA and QBO totals using the same dates, statuses, and account filters.
Common Integration Issues
- Missing account, tax, item, customer, vendor, or payment mapping.
- External system rejects a record because a required field is empty.
- User retries before fixing the original error.
- Record was created manually in both systems, causing duplicates.
- API key, connector permission, or external account authorization expired.
Escalation tip: Include connector name, record number, sync log message, timestamp, retry count, and what changed recently.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.