Reconciliation and dunning
How HyoNova compares subscriptions with the payment provider, repairs safe differences through the normal event path, and which attention items, dunning cases and settlements need a person.
On this page
Webhooks can be late, lost or fail. Reconciliation checks HyoNova's records against the payment provider so that nothing drifts silently.
When it runs#
- Every hour, automatically.
- On demand in Payments & billing › Reconciliation (all companies) or from one company's billing. Running it needs
billing.manage.
Each run records how many subscriptions it checked, the mismatches it found, how many it repaired and how many need attention.
What is compared#
For every card subscription renewed by a provider that supports reconciliation (up to 200 per run): the status (active, past due, ended), whether a cancellation is scheduled, and the end of the current period.
How differences are repaired#
A difference becomes a synthetic provider event and goes through exactly the same path as a webhook: duplicate protection, ordering, the company's billing timeline, notifications and an audit entry. Nothing is changed silently. If the event cannot be applied, the item is kept for attention instead.
Crypto payments are also checked: checkouts that passed their expiry, or have had no update for ten minutes, are asked to Triple-A before they expire.
Attention items#
| Item | What to do |
|---|---|
| Status mismatch not applied | Compare the subscription at the provider and in HyoNova; correct it at the provider |
| Provider unreachable | Check provider health and run again later |
| Payment pending too long | A payment pending for more than 24 hours: check it at the provider |
| Webhook failed | A received event failed processing: read its error in the provider event log; the provider's retry or the next run usually resolves it |
| Scheduled change failed | A period-end plan change could not be applied at the provider, often because the target price has no mapping: add it, then change the plan again |
Mark an item resolved with a reason once handled.
Dunning#
Payments & billing › Dunning lists companies whose subscription is past due, with the stage, since when, when the grace period ends, the provider and the method.
| Stage | Meaning |
|---|---|
| Retrying | A card renewal failed; the provider retries the charge |
| Grace | A renewal invoice (bank transfer, crypto) or a trial was not paid in time |
| Restricted | The grace period ended; the company's paid features are paused |
| Recovered | The payment arrived; shown on the subscription afterwards |
The grace period length is a billing setting (7 days by default). Company data is never deleted, and the company can always reach its billing pages to pay.
Settlements#
Payments & billing › Settlements lists payouts reported by providers, per currency, with gross, fees and net when the provider sends them. A value the provider did not send stays empty; it is never shown as zero.
Status#
| Feature | Status | Notes |
|---|---|---|
| Billing reconciliation | Requires setupBuilt, but works only after a supporting service is configured for your workspace. | Compare subscriptions with the payment provider, repair safe differences and list what needs a person. |
Was this page helpful?
Thanks. Page ratings are not collected yet, so nothing was sent. If something is missing or wrong, see the Get help page.