> ## Documentation Index
> Fetch the complete documentation index at: https://help.sweeply.dk/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot accounting and Stripe connections

> Separate connection, setup, webhook, and synchronization problems before taking action.

Start by identifying whether the problem is connection health, missing configuration, one failed operation, or delayed synchronization. These require different fixes.

| Symptom                               | Meaning                                                         | First action                                                              |
| ------------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Error — action needed** on provider | Credentials or provider access are invalid or lost              | Restore or reconnect the provider                                         |
| Connected but not ready for invoicing | Required company or invoice mappings are missing                | Open the provider setup and complete required fields                      |
| Cash invoice fails                    | Cash account or provider journal mapping is missing             | Complete cash-payment setup                                               |
| Online payments need an account       | Stripe clearing account or e-conomic payment journal is missing | Review Stripe accounting mappings                                         |
| Stripe needs information              | Stripe requires company or representative details               | Continue in Stripe                                                        |
| Stripe is verifying                   | Stripe review is still in progress                              | Wait, then refresh status                                                 |
| Stripe is restricted                  | Card-payment capability is unavailable                          | Open Stripe and resolve the requirement                                   |
| Webhook needs attention               | Provider updates may not reach Sweeply reliably                 | Review webhook status; do not disconnect a healthy provider unnecessarily |
| One invoice or payment failed         | The connection may still be healthy                             | Open the order and review the specific issue                              |

## Safe troubleshooting sequence

<Steps>
  <Step title="Open Customer billing">
    Review accounting connection, invoice readiness, online-payment state, and payment-registration state separately.
  </Step>

  <Step title="Open the affected provider">
    Verify the selected company and every required resource mapping.
  </Step>

  <Step title="Check provider access">
    Confirm the app grant or token is still valid and has the roles required for the failing operation.
  </Step>

  <Step title="Review webhook status">
    Use the action shown in the provider settings to create or repair the webhook. A webhook issue does not necessarily mean provider access is invalid.
  </Step>

  <Step title="Try the affected action again">
    After fixing configuration, retry invoice synchronization or refresh the Stripe status from the relevant page.
  </Step>

  <Step title="Check an uncertain accounting result">
    If a payout or another accounting action has an uncertain result, check the accounting provider for an existing record before contacting Sweeply support with the order, invoice, payment, or payout reference.
  </Step>
</Steps>

## Disconnect only when necessary

Disconnecting allows another accounting provider to be connected or unlinks Stripe, but it does not delete existing provider records. It can also remove Sweeply's ability to retrieve historical documents or refresh records.

<Warning>
  Do not disconnect and reconnect as a first response to a missing account mapping or one failed invoice. Fix the narrow readiness or operation issue instead.
</Warning>