1. Availability commitment

EasyBRL will make the hosted validation API available at least 99.9% of each calendar month. Availability covers the production validation endpoint’s ability to authenticate a valid request, accept a supported package, and return an HTTP response. It does not guarantee that a customer file validates successfully.

2. Measurement

Monthly Availability Percentage equals total minutes in the month minus Unavailable Minutes, divided by total minutes in the month, multiplied by 100. A minute is unavailable when EasyBRL’s monitoring confirms the production API cannot serve valid requests and no exclusion applies. Partial degradation is unavailable only for materially affected requests or regions.

3. Service credits

Credits are capped at 50% of the affected monthly fee, have no cash value, and are applied to a future invoice or refunded if the subscription has ended. They are the exclusive remedy for failure to meet this availability commitment, without limiting remedies that cannot legally be excluded.

4. Claim process

Submit a claim to [email protected] within 30 days after the affected month. Include the organization, region, dates and times, request IDs if available, observed errors, and reasonable supporting information. EasyBRL will compare the claim with service monitoring and respond within 30 days.

5. Exclusions

• Scheduled maintenance announced at least 48 hours in advance.
• Emergency maintenance reasonably required to address an active or imminent security, legal, or stability risk.
• Customer applications, credentials, configuration, data, networks, systems, or failure to follow documentation.
• Self-hosted deployments, trials, previews, beta features, free services, and customer-requested test environments.
• Abuse, unsupported requests, exceeded quotas or rate limits, suspension permitted by the Terms, or force majeure.
• Public internet or third-party systems outside EasyBRL’s reasonable control, unless the third party is an API subprocessor whose failure should reasonably be mitigated by the service design.

6. Maintenance and status communication

EasyBRL schedules disruptive maintenance outside ordinary European business hours where practical and communicates material incidents and recovery through the portal, account contact, or designated status channel. Security work may proceed without advance notice when delay would create material risk.

7. Changes

EasyBRL will give at least 30 days’ notice before materially reducing this SLA for an active subscription, and a reduction will not apply before the next renewal unless the customer agrees. An order form may provide enhanced commitments.